- Starting skills
- Python, binary parity and simple probability
- Portfolio output
- Detector-model parser or round-trip audit with exhaustive reference
- A useful completion check
- Detector and logical-observable distributions preserved in a small enumerated case
- Hardware needed
- No
- Scope boundary
- Format semantics and interoperability; no decoder speed claim
Stim’s detector-error-model format describes error mechanisms through their probabilities, detector symptoms and changes to logical observables. Its official format document provides a precise starting point for an interoperability project. This pathway asks whether a small model retains its meaning when a parser, exporter or downstream analysis handles it. The deliverable is a format and semantics audit, not a decoder speed benchmark or a claim about the performance of real error-corrected hardware. The exercise uses deliberately small synthetic examples.
Begin with a hand-readable model containing only a few detectors and one logical observable. For each error mechanism, state which detector outcomes change and whether the logical observable changes. Then construct a tiny exhaustive reference that enumerates combinations of those mechanisms. The reference should make parity explicit: two flips of the same binary symptom cancel. This small model becomes an independent check on the parser’s interpretation and a way to explain why a list of detector identifiers is more than a collection of labels.
The second stage introduces indexing and repetition. Choose an example in which repeated blocks shift detector references, and write the expanded interpretation beside the compact input. Confirm that a transformation preserves the intended identities and total mechanism structure. Coordinates can help a reader visualize a model, but a coordinate convention should not be confused with the detector’s logical definition. The report should identify which fields affect sampled outcomes and which describe geometry or presentation. Keep each claim tied to the exact format version used.
Add an intentionally malformed or semantically altered example. A shifted detector index, missing observable reference or mistaken repetition count can produce a file that looks plausible while changing its meaning. Show the diagnostic that catches the alteration. If the downstream tool accepts only a restricted class of models, record that capability boundary explicitly. Do not convert unsupported mechanisms silently merely to make the import succeed. An honest incompatibility report is more useful than a pipeline that runs while changing the scientific question.
Questions to take with you
Why keep logical-observable references?
They distinguish errors that produce the same detector symptoms but differ in their effect on the tracked logical quantity. Dropping them can preserve a superficial syndrome view while changing the task.
Does an accepted file prove compatibility?
Only syntactic acceptance. The report must also check the interpretation of repetition, indices, mechanisms and any restrictions imposed by the receiving tool.
Self-directed project; no vacancy, completed execution, certification or employer endorsement is implied. Pin the software environment before presenting runnable code.
Sources and what they show (2)
- Stim detector-error-model file format ↗Stim project / quantumlib · Accessed 2026-10-17
Detector symptoms, logical observables, indexing and repeat semantics
Main-branch format; pin a compatible release before coding.
- Stim project documentation ↗Stim project / quantumlib · Accessed 2026-10-17
Stabilizer simulation and supported-operation boundaries
Not a general non-Clifford simulator or a complete physical noise model.