Repository navigation
Troubleshooting
Confirm interpreter is Python 3.14, active venv and installed extras; inspect python --version, python -m pip show quantum-workflows and qw --help. An old environment or mixed provider extras can cause incompatible Qiskit/SciPy dependency resolutions. Start from a fresh isolated environment.
Check actual nvidia-smi in the allocated GPU node, container runtime, CUDA/driver versions, optional simulator wheel and GPU method support. A GPU-enabled Python package on a CPU-only workbench is not a GPU allocation. Do not force GPU simulator flags when the build cannot provide them.
Separate authentication, plan/allocation, backend selection, provider downtime, queueing, API/SDK compatibility and resource cap. Never post tokens. Reproduce the same circuit locally before escalating hardware service faults.
Inspect job name, partition, QOS, walltime and reservation policies. A site may allow only specific names and fixed walltimes; use facility-approved templates rather than altering application authorization. Confirm sacct exit code and artifact directory after completion.
Check seed/shot uncertainty, Hamiltonian convention, coupling units, time-step error, qubit ordering, normalization, backend noise and exact reference. An altered experiment can pass the execution smoke but fail scientific acceptance; report both.
See scientific checks and reference commands.
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