The deciding runs found the readout kick on untouched qubits 3 to 4 couplings from the nearest measured qubit, with too few qubits further out to say where it stops. This run packs the 39 measured qubits in three central layouts so that 38 to 42 untouched qubits sit at each exact distance 3, 4, 5, 6 and 7, and 88 at 8 or more, on ibm_fez, ibm_kingston and ibm_marrakesh. Plan, circuits and analysis pushed before any job; results are read below by the committed analysis.
plan · reach.py · analyze_reach.py · synth_reach.py · synthetic test · plan SHA-256 · code SHA-256
Jobs: fez dbcvr0pgv2cc738h409g, kingston dbcvrgfi0auc7394ele0, marrakesh dbcvruoc77vs73874lg0 (fire log; job records job_reach_ibm_*.json in this folder). Kick size is the size of the readout kick (negative values of the kick count as positive size), in degrees per readout, by exact coupling distance from the nearest measured qubit. Combined means the three processors together, with their spread printed beside it in the full output.
The size at 4 couplings is about a tenth of the kick next to a measured qubit. Readings were not corrected for multiplicity: synthetic runs with no kick resolve 6.0 % of single-processor readings and 5.6 % of combined ones, so the resolutions at 5 couplings combined and at 6 couplings on marrakesh, whose lower ends are 0.002, are not distinguished from that floor. Consistent with zero is a bound, not a proof of none: the intervals above are the bounds.
Bones · Wayfinder · Sage · Shuttle · Nova
Heuremen LLC
“We found it.”