Guides erasure-aware Stim simulation using the local Erasure_qubit-1 repo, with explicit separation between latent-erasure sampling, approximate decoding circuits, posterior or multi-check processing, and small local smoke runs.
Use this skill when the task is to reproduce or adapt erasure-aware circuit simulations similar to the local Erasure_qubit-1 repo:
Stim circuits,Use this skill when the main issue is erasure information, erasure-detection events, or posterior-informed decoding.
Use building-stim-circuits when the task is generic Stim authoring with no erasure-specific logic.
Use when the detector model already exists and erasure modeling is not the active design problem.
decoding-with-ldpcExpected inputs:
Expected outputs:
Assumptions to make explicit:
H1, H2) or rotated-surface-code style,osd_0) or cluster performance (osd_cs with higher order).references/local-repo-workflow.md.src/ for HGP coloration plus sliding-window decoding, multi_check/ for true-process versus approximate-decoder separation, multi_check1/ for alternate or exact multi-check variants, or BP_multi_check/ for posterior and BP-assisted branches.Before closing work:
Problem: one circuit is treated as both the true noisy process and the decoding model.
Fix: follow the local repo pattern and separate them explicitly.
Problem: OSD settings change across runs without being tracked.
Fix: write down osd_method, order, window, commit, and check-count choices.
Problem: large multi-check runs start before a small local path works.
Fix: smoke test a tiny instance first.
Problem: the src/sinter_decoding.py path is launched from an inline stdin snippet and Python spawn workers fail to recover the entry script.
Fix: run the real script or module path directly, or reduce to a single-worker local smoke harness before scaling back up to the repo's sinter.collect(...) path.