This repository has been archived by the owner on Oct 11, 2023. It is now read-only.
Replies: 3 comments
-
List of problem
|
Beta Was this translation helpful? Give feedback.
0 replies
-
made with https://www.mindmeister.com/ |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
After reviewing QuNetSim, SeQUeNCe, netqasm, SimulaQron, ProjectQ, quisp
I think it should roughly look something like this, so we can continuously work on other ideas #12 :
components: specify the node variable(example: location, type of node, etc), create a new timeline, Network for building all the node connection, protocols doing all the sendiing message, qubit, etc, we will look into all the related good library to be use, for example PyKMIP for key management, which includes all kind of symmetric key algorithms.
Channel: different types of connection could be wireless or Optical fiber for classicalchannel or quantumchannel(free space(like quantum satellite) or high q cavity of microwave devices)
utils: protocols, entanglements, tools for developing quantum network #14
visual: visualization tools for node, Basemap, coupling map, etc
backend: prepare for qiskit-metal custom backend
kernel: where the timeline, logging
Kernel is the environment (just like a video editor timeline bar, reference from SeQUeNCe parallel timeline):
Timeline is the time length of the whole simulation or instructions.
Event storing instruction for a specific timeline (store quantum circuit, qiskit pulse calibration or classical request)
EventList is to specify the type of instruction in a subset of nodes. (a set of an event in a different group of set qubit)
utils include:
Packet: the things to send
Routing Packet: Packet that will be delete in a time
....still in planning
Beta Was this translation helpful? Give feedback.
All reactions