Submissions: Difference between revisions

184 bytes added ,  11 November 2018
m
no edit summary
mNo edit summary
Line 1: Line 1:
Submissions can be made to the google form provided in the link below. You can register a request to include their article as a "relevant paper" for a certain formal description. If you do not find any required functionality or think your protocol requires a new page, submit  *.tex/ *.txt/ *.html version of the protocol using instructions in the guidelines given below. Note that Quantum Protocol Zoo accepts only published articles. The final decision on a request resides with the Quantum Protocol Zoo team.
Submissions can be made to the google form provided in the link below. A request can be made to include an article as a "relevant paper" for a certain protocol. If you do not find any required functionality or think your protocol requires a new page, submit  *.tex/ *.txt/ *.html version of the protocol using instructions in the guidelines given below. Note that Quantum Protocol Zoo accepts only published articles. The final decision on a request resides with the Quantum Protocol Zoo team.


Link to Google Form: https://goo.gl/forms/UXhrqzQEVpm98Mkt1
Link to Google Form: https://goo.gl/forms/UXhrqzQEVpm98Mkt1


Comments are welcomed in order to make it more user-friendly and can be addressed in the Discussion.
Comments are welcomed in order to make it more user-friendly and can be addressed in the 'Discussion'.




Line 25: Line 25:
==Requirements==
==Requirements==
*Network Stage: See Network Stages in Categories (sidebar)
*Network Stage: See Network Stages in Categories (sidebar)
*Technological Readiness:
*Relevant network parameters: Only relevant network stage parameters to be listed here
 
*Benchmark values: Updated values for all the parameters if an experimental demonstration has been carried out.
==Example:Your Protocol==
==Example:Your Protocol==


Line 36: Line 36:
*Same as functionality description it should be lucid, but one is free to make this section lengthy (yet avoid redundancy)
*Same as functionality description it should be lucid, but one is free to make this section lengthy (yet avoid redundancy)
*Should give a rough picture of the protocol without any specific details like number of qubits used or threshold value if any.
*Should give a rough picture of the protocol without any specific details like number of qubits used or threshold value if any.
*In the end, this section can accommodate a figure of the protocol. An example can be seen on [[Prepare and Send-Universal Blind Quantum Computation|UBQC]].</br></br>
*In the end, this section can accommodate a figure of the protocol which describes the quantum and classical channels distribution for the protocol. See an example in Protocol Library (sidebar)
'''Notations''' The following sections on properties and pseudo code contain mathematical equations and hence to connect it with the wordy outline this section displays all notations used.
'''Notations''' The following sections on properties and pseudo code contain mathematical equations and hence to connect it with the wordy outline this section displays all notations used.
----
----
Write, autoreview, editor, reviewer
3,129

edits