Why Two Scripts Are Required
A 40-44 qubit circuit (our production benchmark) exists in a 240 to 244 state space—over 1 trillion to 17 trillion amplitudes.
No classical machine can hold or manipulate that exact state vector efficiently, so vendors publish a
quantum run script plus a classical approximation.
- The quantum script executes natively on superposition + entanglement hardware.
- The classical script burns CPU/GPU cycles via dense matrices, sampling, and optimization to approximate the same workload.
- The two scripts express the same problem configuration (CONFIG), making results directly comparable.
- Note: The quantum script v2 has two profiles: "balanced" (default, 40 qubits) and "stress_test" (44 qubits) for different runtime requirements.
Legitimacy of the Comparison
This methodology mirrors what IBM, Google, and IonQ publish: a quantum circuit file plus a classical simulator.
As long as you disclose that the classical version is an approximation (and encourage customers to
run it with their maximum settings), the comparison is both honest and scientifically sound.
Customers can reproduce the delta by timing the classical script locally, then
running the quantum script in Production Hardware mode and comparing total runtime, energy savings,
and fidelity/variance metrics.
Download / Copy the Scripts
Quantum Production Script (v2)
- Default (balanced): 40 qubits, 32,768 shots, 12 context cycles
- Stress test: 44 qubits, 65,536 shots, 20 context cycles
- Use in the Quantum Playground (Production mode)
- Outputs JSON + verification hash + email-ready report
- Change PROFILE = "stress_test" in script for full benchmark
Download Quantum Script
Classical Heavy Benchmark
- State-vector + dense matrix simulation
- Default: 44 qubits, 65,536 shots, 20 context cycles
- Configurable states/precision/shots for any hardware
- CLI instructions provided below
Download Classical Script
How to Run & Compare
1. Classical Baseline
Run the heavy script on your machine:
Download Classical Script
Increase --states or --precision until runtime matches your hardware capacity.
2. Quantum Production Run
Download Quantum Script
Paste the script into the Playground, select Production Hardware,
and submit. The results panel & emailed report include the full CONFIG + metrics.
3. Compare Metrics
- Total execution time (classical vs quantum)
- Variance reduction, average energy, fidelity
- Energy/CO₂ savings (if you capture facility data)
Mac & Windows Quick Commands
Customers can copy/paste the following one-liners:
macOS / Linux
python3 classical_benchmark_script_heavy.py --states 24 --precision high --shots 65536 --cycles 20
Note: The classical script uses 44 qubits by default (configured in BASE_CONFIG).
The --states parameter controls the state-vector cutoff (2^states), not qubit count. Higher values increase memory usage and runtime.
Windows (PowerShell)
python classical_benchmark_script_heavy.py --states 22 --precision medium --shots 65536 --cycles 20
(Start with medium settings, confirm the script runs, then increase --states and --precision until the benchmark stresses the local CPU/GPU.)