Write, autoreview, editor, reviewer
3,129
edits
Submissions: Difference between revisions
no edit summary
mNo edit summary |
No edit summary |
||
| Line 29: | Line 29: | ||
**It should be lucid, and one is free to make this section lengthy (yet avoid redundancy) such that it gives a rough picture of the protocol without any specific details like the number of qubits used or threshold value if any. | **It should be lucid, and one is free to make this section lengthy (yet avoid redundancy) such that it gives a rough picture of the protocol without any specific details like the number of qubits used or threshold value if any. | ||
*'''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. | ||
*'''Component Requirements''' Mentions implementation details like benchmark values, network stage, required parameters | *'''Component Requirements''' Mentions implementation details like benchmark values, network stage, required parameters. Also, it accommodates a figure on the decomposition of the protocol into various components required for implementation including the physical resources, nodal subroutines, and other protocols used. | ||
** The protocols are shown in a blue rectangular box. | |||
** The nodal subroutines are shown in a green rounded rectangular box. | |||
** The physical resources are shown in red ovals. | |||
*'''Properties''' This section is a list of all important details which were not given in the wordy outline. One could list all that one thinks is important for the reader to know and can be extracted from the protocol. e.g: | *'''Properties''' This section is a list of all important details which were not given in the wordy outline. One could list all that one thinks is important for the reader to know and can be extracted from the protocol. e.g: | ||
# List of parameters used e.g. threshold value etc. | # List of parameters used e.g. threshold value etc. | ||
| Line 35: | Line 38: | ||
# Advantages in terms of resources. e.g. no quantum memory needed etc. | # Advantages in terms of resources. e.g. no quantum memory needed etc. | ||
# Success probability of protocols (for entanglement routing and other building blocks protocols). | # Success probability of protocols (for entanglement routing and other building blocks protocols). | ||
# Mathematical equations or inequalities for security claims and other items mentioned above can | # Mathematical equations or inequalities for security claims and other items mentioned above can be accommodated here. | ||
be accommodated here. | |||
#If using a new term for any of the above, please explain it here itself and if needed, provide a link to the supplementary information page for a detailed explanation. E.g. Any property not defined in the functionality description already could be defined here. | #If using a new term for any of the above, please explain it here itself and if needed, provide a link to the supplementary information page for a detailed explanation. E.g. Any property not defined in the functionality description already could be defined here. | ||
*'''Pseudo Code''' This section contains an algorithm/ pseudo code of the protocol. | *'''Pseudo Code''' This section contains an algorithm/ pseudo code of the protocol. | ||