- Starting skills
- Python, event-driven programming, probability
- Portfolio output
- Network trace and bottleneck diagnosis
- A useful completion check
- Every reported outcome traceable to events and measurement window
- Hardware needed
- No
- Model boundary
- Discrete-event simulation; real-device validation separate
SeQUeNCe’s official documentation describes an open-source discrete-event simulator for quantum networks. Its introductory chapters separate event scheduling, hardware components and network resource management. This pathway turns those resources into a diagnostic project: explain how a change in event ordering or resource lifetime affects an end-to-end network outcome. The result is a software and modelling portfolio, not an operational quantum network and not a verified job opening at Argonne or another institution.
Begin with a minimal topology and a short trace of scheduled events. Each trace row should include simulation time, event type, affected resource and the state change it causes. The goal is to make it possible to reconstruct why an attempt succeeded, failed or was retried. A final average rate hides that causal sequence. A small trace can reveal whether the model is waiting for a classical message, holding a memory resource or discarding a result that arrived too late for the chosen policy.
Choose one policy variable, such as a reservation rule or an explicitly modelled memory lifetime, and vary it while keeping the topology and random seed policy fixed. Report the resulting distribution rather than only its mean. Also record how much simulated time was spent in warm-up and whether incomplete attempts at the end were counted. Those bookkeeping decisions can change a reported rate without changing the physical model. The exercise should expose them so that a reviewer can distinguish a scientific effect from a measurement-window artifact.
A useful failure case is a network that appears connected in a diagram but cannot supply the requested service under the chosen timing and resource conditions. Explain the bottleneck through the event trace and then propose one bounded modification. Do not assume that the modification corresponds to a real device upgrade. It is a model intervention whose effect can be tested inside the simulator. If the intervention helps, state which assumptions would need experimental evidence before the conclusion could be applied to deployed infrastructure.
Questions to take with you
Why inspect a trace instead of only a throughput plot?
The trace explains which resource or message caused the outcome. It can reveal a scheduling or accounting issue that an average rate conceals.
What makes a model intervention credible?
Change one stated assumption, preserve the rest of the configuration and compare repeated outcomes. Then identify the physical evidence that would be required to apply the result outside the simulator.
Self-directed project; no vacancy, completed execution, certification or employer endorsement is implied. Pin the software environment before presenting runnable code.
Sources and what they show (2)
- SeQUeNCe introduction ↗SeQUeNCe project · Version 1.3.0 observed
Open-source discrete-event quantum-network simulator
Simulation parameters are not automatically calibrated to real hardware.
- SeQUeNCe discrete-event tutorial ↗SeQUeNCe project · Accessed 2026-10-17
Event scheduling and simulation foundation
Pin project version; mutable latest documentation may change.