Repository navigation
Contributing
Before submitting a notebook, search issues and the master academy plan for an existing track. Contributions should include learning objectives, math/physics prerequisites, the native SDK/API used, reproducible local path, inputs/outputs, analytic/numerical checks, tolerances, license/attribution, exercise solutions or test oracle, scientific sources and limitations.
Code PRs require lint and non-hardware tests, explicit provider extras, artifact schema compatibility and updated examples/docs. Do not merge a new curriculum label if no actual notebook or test exists. A planned module remains labelled planned.
For help, provide a public reproducible minimal script/notebook, supported Python and SDK versions, expected physics, sanitized trace and output manifest. Report secrets privately. See Developer guide and Wiki policy.
Quantum Workflows
- Home
- Getting started
- Academy and learning paths
- Batch-first simulator academy
- Reference experiments
- Standalone workstation and GPU notebooks
- Execution environments
- Scientific provenance
- Ecosystem integration
- Developer guide
- Troubleshooting
- Security and responsible science
- Contributing
- Guide help and support Scientific engineering
- Slurm runner contract
- Quantum SDK and executor matrix
- Research curriculum design
- Science validation and benchmarks
- Notebook environments and reproducibility