QubitLab
IDELearnPlaygroundDocsCommunity
Log in
QubitLab
IDELearnPlaygroundDocsCommunity
Log in
HomeLearnCatalogRanksPlaygroundDocs
  1. Docs
  2. Simulators, noise, T1/T2 and fake backends
Learn
  • Quantum basics
  • OpenQASM 3 cheat sheet
  • All gates, with the math
  • Every gate, interactive
  • Entanglement: how CNOT connects qubits
Circuits
  • Dynamic circuits: if/else, loops and conditions
Lessons
  • Learning path: from one qubit to algorithms
  • Quantum machine learning by hand
Run
  • Compile (transpile): levels, basis gates, topology
  • Simulators, noise, T1/T2 and fake backends
  • Python in the Playground
  • GitHub and git in the Playground
  • Articles and sharing
Analyze
  • Metrics: comparing distributions
  • Q-sphere and Bloch spheres
Hardware
  • Real IBM Quantum hardware
  • Device topology and calibration heat maps
  • Benchmark circuits: MQT Bench and QASMBench
Advanced
  • Circuit cutting, in depth
Story
  • The story of quantum computing
  • The Hamiltonian: where gates come from
  • What to expect next
Documentation/Run/Simulators, noise, T1/T2 and fake backends

Simulators, noise, T1/T2 and fake backends

Simulators compute what an ideal or noisy quantum computer would output. QubitLab offers four ideal methods and 68 noisy models of real IBM machines.

Simulation targets

TargetMethodLimitUse it for
ideal_statevectorExact amplitudes; probabilities without shot noise. Memory 2ⁿ complex numbers.4 qubitsThe reference every metric is compared against.
ideal_shotsAer 'automatic' sampling: exact state, then random shots.4 qubitsSeeing statistical (shot) noise alone.
mpsMatrix product state: compresses weakly entangled states.4 qubitsWide but shallow circuits, chains, low entanglement.
density_matrixTracks ρ (2ⁿ×2ⁿ) so mixed states and noise are exact.4 qubitsStudying decoherence precisely.
fake:<name>AerSimulator built from a snapshot of a real backend: its coupling map, basis gates and calibrated noise.4 qubitsPredicting what hardware will do, for free.

Noise: T1 and T2

Where does noise come from? A qubit is a tiny physical system (a superconducting circuit at 15 mK) that interacts with its environment. Two timescales summarize how fast it forgets:

p∣1⟩​(t)=e−t/T1​
T1 (relaxation, energy decay): an excited |1⟩ decays to |0⟩. After time T1 only 37 % of the population remains. Typical IBM values: 100–400 µs.
ρ01​(t)=ρ01​(0)e−t/T2​,T2​≤2T1​
T2 (dephasing, coherence time): the off-diagonal element of ρ, which carries the phase of a superposition, decays. The Bloch vector shrinks toward the Z axis. Pure dephasing adds 1/T2 = 1/(2T1) + 1/Tφ.

A circuit of depth d with gate time τ takes about d·τ. Errors grow roughly like 1 − e^{−dτ/T2}, which is why depth matters so much. A CNOT takes ~300–500 ns, a √X ~30–60 ns, and readout ~1 µs.

Error channels

Error channelModelTypical size
Depolarizing (gate error)ρ → (1−p)ρ + p·I/2ⁿ1q: 2–5 ×10⁻⁴ · 2q: 3–10 ×10⁻³
Thermal relaxationT1, T2, gate durationDepends on depth
Readout errorP(read 1 | was 0), P(read 0 | was 1)1–3 % per qubit

Fake backends

Fake backends (FakeProviderForBackendV2) bundle a real device's snapshot: name, number of qubits, coupling map, basis gates, and calibration data (T1, T2, gate errors and durations, readout errors). AerSimulator.from_backend(...) turns that into a noise model, so fake_sherbrooke behaves like ibm_sherbrooke did on the snapshot day. Calibration changes daily on real hardware, so treat fake results as a forecast, not a measurement.

Shots and seeds

Shots and seed. More shots reduce statistical error as 1/√shots: 1024 shots give about ±1.5 % on a 50 % outcome, 4096 give ±0.8 %. Fixing a seed makes a simulation reproducible and lets QubitLab cache the result for 24 hours.

σp^​​=shotsp(1−p)​​
← Previous
Compile (transpile): levels, basis gates, topology
Next →
Python in the Playground
On this page
  • Simulation targets
  • Noise: T1 and T2
  • Error channels
  • Fake backends
  • Shots and seeds
Try it in the IDE →
QubitLab
IDELearnPlaygroundDocsCommunity
Log in
QubitLab
IDELearnPlaygroundDocsCommunity
Log in