Documentation

QEC1.Remarks.Rem_22_GrossCodeGaugingExample

Rem_22: Gross Code Gauging Example #

Statement #

The gauging measurement for X̄_α in the Gross code provides a concrete example demonstrating the efficiency of the gauging approach.

Goal: Measure X̄_α = X(αf, 0) while keeping all new checks and qubits at Tanner graph degree at most 6 (the 12 qubits in X̄_α and 18 adjacent Z checks will become degree 7).

Graph construction:

  1. Vertices: The 12 monomials in f correspond to the 12 vertices of G
  2. Initial edges: Connect γ, δ ∈ f if qubits (γ, L) and (δ, L) participate in the same Z check, i.e., if γ = Bᵢᵀ Bⱼ δ for some i, j ∈ {1, 2, 3}. This gives 18 edges.
  3. Expansion edges: Add 4 additional edges to achieve distance 12: (x², x⁵y³), (x², x⁶), (x⁵y³, x¹¹y³), (x⁷y³, x¹¹y³)

Cycle basis: With 12 vertices and 22 edges, G has 22 - 12 + 1 = 11 independent cycles. Due to redundancy in the BB code's Z checks (4 redundant cycles), only 11 - 4 = 7 independent B_p checks are needed.

Overhead summary:

This is significantly more efficient than the O(Wd) = O(12 · 12) = O(144) overhead of previous schemes.

Main Results #

Corollaries #

Section 1: Logical Operator Parameters #

X̄_α = X(αf, 0) is supported on 12 qubits (the monomials of f). The Gross code has distance d = 12.

Weight of the logical operator X̄_α: the number of monomials in f.

Equations
Instances For

    The code distance of the Gross code.

    Equations
    Instances For

      The weight of X̄_α equals the code distance (a key property of the Gross code).

      Section 2: Graph Construction Parameters #

      The gauging graph G for the Gross code has specific structural parameters arising from the BB code's Z-check connectivity and additional expansion edges.

      The parameters of the gauging graph for X̄_α in the Gross code.

      • numVertices :

        Number of vertices: monomials in f

      • numInitialEdges :

        Number of initial edges from Z-check connectivity

      • numExpansionEdges :

        Number of expansion edges added for distance

      • numRedundantCycles :

        Number of redundant cycles from BB code Z-check structure

      • maxNewDegree :

        Maximum Tanner graph degree for new elements

      • maxAffectedDegree :

        Maximum Tanner graph degree for affected existing elements

      Instances For

        The concrete gauging graph for X̄_α in the Gross code.

        Equations
        Instances For

          Section 3: Basic Parameter Values #

          The vertices correspond to monomials in f, so numVertices = logicalWeight.

          Section 4: Edge Count Computation #

          Total edges = initial edges + expansion edges = 18 + 4 = 22.

          Section 5: Cycle Basis Computation #

          By Euler's formula for connected graphs: number of independent cycles = |E| - |V| + 1. With 22 edges and 12 vertices: 22 - 12 + 1 = 11.

          Section 6: Redundant Cycles and Flux Operator Count #

          The BB code's Z checks introduce 4 redundant cycles, so only 11 - 4 = 7 independent B_p checks are needed.

          Section 7: Overhead Summary #

          The total overhead consists of:

          Number of new X checks = number of vertices (one A_v per vertex).

          Equations
          Instances For

            Number of new qubits = number of edges (one gauge qubit per edge).

            Equations
            Instances For

              Section 8: Comparison with Previous Schemes #

              Previous schemes have O(Wd) overhead, where W is the logical operator weight and d is the code distance. For the Gross code: W = d = 12, so O(Wd) = O(144).

              The gauging overhead (41) is strictly less than the previous scheme overhead (144).

              The improvement ratio: the gauging overhead is less than 29% of the previous scheme.

              The gauging saves 103 = 144 - 41 elements compared to previous schemes.

              Section 9: Degree Bound Properties #

              New elements have Tanner graph degree ≤ 6. The 12 qubits in X̄_α and the 18 adjacent Z checks will become degree 7.

              The degree increase for affected elements is exactly 1 (from 6 to 7).

              Section 10: Expansion Edge Details #

              The 4 expansion edges connect specific monomials to achieve distance 12. We record these as pairs of monomials in ZMod 12 × ZMod 6.

              @[reducible, inline]

              Type alias for monomials in the Gross code group.

              Equations
              Instances For

                Expansion edge 2: (x², x⁶) = (x², 1) since x¹² = 1 and x⁶ in ZMod 12.

                Equations
                Instances For

                  All expansion edges are between distinct vertices.

                  Section 11: Monomials of f #

                  The polynomial f has 12 monomials, which correspond to the 12 vertices of G: f = 1 + x + x² + x³ + x⁶ + x⁷ + x⁸ + x⁹ + (x + x⁵ + x⁷ + x¹¹)y³

                  The monomials are: {(0,0), (1,0), (2,0), (3,0), (6,0), (7,0), (8,0), (9,0), (1,3), (5,3), (7,3), (11,3)}

                  The 12 monomials appearing in f, represented as elements of ZMod 12 × ZMod 6.

                  Equations
                  Instances For

                    Section 12: Initial Edge Construction #

                    Connect γ, δ ∈ f if γ = Bᵢᵀ Bⱼ δ for some i, j ∈ {1,2,3}. The polynomial B = y³ + x² + x, so B acts by shifting monomials. The matrices B₁ = y³, B₂ = x², B₃ = x give: Bᵢᵀ Bⱼ sends δ ↦ -Bᵢ + Bⱼ + δ

                    This connectivity gives exactly 18 edges.

                    The number of Z checks adjacent to X̄_α.

                    Equations
                    Instances For

                      The number of adjacent Z checks equals the number of initial edges.

                      Section 13: Target Distance #

                      The expansion edges are added to ensure the gauging graph achieves distance 12, matching the Gross code distance.

                      The target distance for the gauging graph matches the code distance.

                      Equations
                      Instances For

                        The target distance equals the Gross code distance.

                        The target distance equals the number of vertices (a coincidence for this code).

                        Section 14: Overhead Breakdown Verification #

                        Verify all components of the overhead.

                        The number of new X checks equals the number of vertices (Gauss's law: one A_v per vertex).

                        The number of new qubits equals the total edges (one gauge qubit per edge).

                        All three overhead components add to 41.

                        Section 15: Consistency with Gross Code Parameters #

                        The number of vertices matches the Gross code's grossCodeParams_d.

                        Section 16: Summary of Efficiency #

                        The gauging approach for the Gross code uses only 41 additional elements, compared to 144 for previous schemes — a reduction by a factor of > 3.5×.

                        The efficiency factor: gauging uses less than 1/3 of previous overhead.

                        The gauging overhead is strictly less than half the previous scheme overhead.