Add GARI support to decoder CLIs - #277
Open
arshpreetmaan wants to merge 16 commits into
Open
Conversation
arshpreetmaan
commented
Jul 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR adds C++ CLI support for consuming the GARI matrix and layout files produced by the Python utilities in #273.
--gari-layoutsupport to Tesseract and Simplex.Simplex applies the source-to-GARI detector mapping but does not otherwise interpret detector ordering.
Example
Generate a GARI matrix and layout from a circuit:
python src/py/_tesseract_py_util/gari.py \ --circuit circuit_file.stim \ --prior xor \ --out-dir gari_outputThis produces:
Tesseract can sample from the original circuit and decode using the GARI matrix:
We recommend using a smaller beam size (5 or 10 than usual longbeam 20) which provides a useful runtime/accuracy tradeoff while decoding with GARI dem as GARI reduces the row (check) weight by roughly 10 times for the tested BB codes and color codes circuits.
Detector-order options are omitted above, so Tesseract processes the GARI rows in their stored physical-then-virtual order. If explicit detector ordering is requested, Tesseract constructs the order from the source circuit, maps only the physical detector portion, and keeps the virtual detector portion in its natural order.
The same files can be used with Simplex:
./bazel-bin/src/simplex \ --circuit circuit_file.stim \ --dem gari_output/circuit_file_gari_xor.dem \ --gari-layout gari_output/circuit_file_gari_xor_layout.json \ --sample-num-shots 100 \ --sample-seed 1234 \ --threads 1 \ --stats-out simplex_gari_stats.jsonNote: The GARI DEM is a decoding representation and is never sampled. Detection-event data must either be sampled from the original source circuit or loaded from a file containing detector events in the original source-circuit detector order. The companion layout maps those source detector events into the physical GARI rows; virtual GARI rows are initialized to zero. When decoding source-circuit detection-event files against a GARI DEM,
--gari-layoutmust be supplied. Without the layout, the CLI interprets the records in the loaded DEM's detector space and cannot infer the source-to-GARI permutation. The .dem and _layout.json files must be the pair generated from the same source circuit.