Noise simulation: Pauli channels, amplitude damping and readout error
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 55/100
Research direction
Start with the per-shot dynamic branch in src/circuit.rs and the measurement and renormalisation pattern in src/backend.rs; trace how apply_gate_kernel and probability_of_one are used. Implementing this spans gate execution, noise sampling, and fast-path behavior. Done means run supports the listed noise channels and the state inspection methods reject gate noise as specified.
Written by the indexing model from the issue text.
Description
What you want to do
Summary
Every result today comes from an ideal, noiseless device. Studying error mitigation, error correction or how an algorithm holds up on real hardware needs gate noise and readout error. Right now users have to switch to another simulator for that.
Implementation notes
- Use quantum trajectories (Monte Carlo wavefunction). The path that simulates each shot separately
(QuantumCircuit::run, dynamic branch insrc/circuit.rs) already does what this needs: one state
per shot, a random generator, andmeasure_qubit/reset_qubit. - Pauli channels: after a gate, draw a random Pauli with the channel's probabilities and apply it with
apply_gate_kernel. Single-qubit gate fusion has to stop at every noise point, or fuse only
between noise points. - Amplitude damping is not a mixture of unitaries. Its Kraus branch probabilities depend on the state,
p(jump) = γ · P(qubit = 1), andprobability_of_onealready computes that. Then apply the
non-unitary 2×2 matrix and renormalise, the same pattern asmeasure_qubitinsrc/backend.rs. - Readout error only flips classical bits after sampling, so circuits that only measure at the end
keep the fast path when readout is their only noise. statevector(),probabilities()andexpectation()should raise when given gate noise,
since the state is a mixture. A density-matrix backend could be a later issue.
What it could look like
noise = qsengine.NoiseModel(
depolarizing=1e-3, # after every single-qubit gate
depolarizing_2q=1e-2, # after every controlled gate, on each qubit it touches
amplitude_damping=5e-4, # T1-style decay after every gate
readout=0.02, # chance each measured bit is flipped
)
counts = qc.run(shots=4000, seed=1, noise=noise)
Contributing
- I would like to open a pull request for this (see CONTRIBUTING.md).
- Dominant language
- Rust
- Stars
- 1
- Forks
- 0
- Avg merge
- 12m
- Merged PRs (30d)
- 4
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from kaiwave/qsengine
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 55/100
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 55/100
All issues in kaiwave/qsengine
Similar issues
-
bug order-flow studies ui
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
userFRM/egui-charts#2417 ·
Maintainers usually reply within 1 day
-
In a plain-text message, Font, Font Size, Font Color and Text Highlight Color stay livePossibly taken @ragelfundionctrumnar claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
UCS-Care-Group/mailcraft#862 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
smoltcp-rs/smoltcp#1243 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 4 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day