Skip to content

Doped Clifford Sampling #245

Closed
Closed

Description

@ajavadia

Circuit ID

ibm_boston_dcs_nq64_depth73_checks12

Circuit file

dcs_nq64_depth73_checks12_t314.qasm.zip

Qubits

64 logical (76 physical)

Gates

2,336 logical CZ (2,644 physical CZ), 314 logical T

Problem category

Active candidates

Problem description

Doped Clifford Sampling

We demonstrate doped Clifford sampling on a 64-qubit, depth-73 circuit with 314 T gates. The qubits are arranged on a ring. The circuit is protected in the quantum experiment by spacetime codes using 12 ancilla qubits, yielding a fidelity of 0.38(1) after post-selection on the zero-syndrome of the code.

Image

Verification process

Verification is by lower-bounding the fidelity of the prepared state, even when it is beyond simulation.
An encoded Clifford circuit’s state fidelity F1 and its syndrome distributions S1 are measured efficiently. The circuit is doped with T gates that commute with code stabilizers, yielding statistically indistinguishable syndromes S2. This leads to a lower bound on the fidelity F2 of the (hard) doped circuit. The code projects both states to the same subspace, and doping only rotates within this subspace. A lower bound on F2 can be efficiently estimated from the classification of Pauli faults affecting the Clifford circuit. The set of rejected faults and the no-fault probability remain invariant with doping. Any loss in fidelity is only possible due to the conversion of harmless faults, which are rare in random Cliffords.

Image

Experimental results

We see experimentally that the (easy) Clifford and the (hard) doped circuits have the same post-selection probability.. we can also numerically bound the probability of harmless faults in our circuit instance. We therefore obtain a lower bound of 0.349 with 95% confidence.

Image

We can also validate this further by doping with lower amounts of magic such that the circuit remains simulable. We observe a fidelity consistent with our estimated lower bound across these doping regimes, as well as consistent code syndromes.

Image

Classical simulation cost

We explored many classical simulation methods, including tensor network contraction, Clifford+T simulation, and hybrid methods combining the two. The best classical runtime estimate is shown below.

We ran Cotengra’s hyper optimizer on our circuit truncated at various depths and compared the contraction cost (in FLOPs, left panel) and contraction memory (in number of complex scalars, right panel) with those of the deterministic paths. In a first run, we imposed no memory limitation (w = ∞). At depth 73, the deterministic and Cotengra paths have maximum tensor sizes of 264 and 271 scalars, respectively. In a second run, we limited the maximum memory footprint to 243 scalars (w = 43), resulting in higher contraction costs. Solid lines show the deterministic paths, plus markers show the best completed cotengra paths, and open circles show the exact minimum unsliced widths certified by Ratcatcher.

Image

Name

ibm_boston_dcs_nq64_depth73_checks12

Value

0.38

Method

Quantum

Method proof

Preprint: https://arxiv.org/abs/2607.25941

Quantum runtime (seconds)

870

Classical runtime (seconds)

No response

Compute resources (quantum)

IBM Heron r3 (ibm_boston)

Compute resources (classical)

No response

Notes

No response

Authors

Simon Martiel, Jay-U Chung, Alireza Seif, Soumik Ghosh, Ian Hincks, Abhinav Deshpande, Hidetaka Manabe, Hanfeng Gu, Feng Pan, Bill Fefferman, Jay M. Gambetta, and Ali Javadi-Abhari

Institutions

IBM, UChicago, Singapore University of Technology and Design, Nvidia

Activity

  1. ajavadia commented on Sep 11, 2026

    @ajavadia
    ContributorAuthor

    This is the same problem as #228 but the circuit geometry in this new experiment is slightly altered to have periodic boundary conditions rather than an open boundary. This closes a loophole identified in #242 for the earlier experiment.

  2. n-e-sherman commented on Oct 20, 2026

    @n-e-sherman
    Contributor

    Hi @ajavadia, thank you for the submission. I have one small request, could you include a link to the data and samples? In particular, mention where to find the specific samples you generated from the circuit. Otherwise, given the similarity to #228, I am happy to accept the submission.

  3. ajavadia commented on Nov 2, 2026

    @ajavadia
    ContributorAuthor

    Thanks @n-e-sherman. The experimental data and actual measured bitstrings for our 64-qubit, depth-73, 314-T circuit (ibm_boston_dcs_nq64_depth73_checks12) are publicly available here:

    Zenodo: https://zenodo.org/records/22233383

  4. moved this from Backlog to In review in Quantum Advantage Trackeron Nov 3, 2026
  5. n-e-sherman commented on Nov 3, 2026

    @n-e-sherman
    Contributor

    Great, thanks @ajavadia. I'm happy to accept the submission. We'll see if @Roland-Farrell has any comments, and we can verify the submission if not.

  6. Roland-Farrell commented on Nov 3, 2026

    @Roland-Farrell

    Looks good to me too.
    I verified this submission

  7. moved this from In review to Verified in Quantum Advantage Trackeron Nov 3, 2026
  8. github-actions commented on Nov 3, 2026

    @github-actions
    Contributor

    Submission verified by @Roland-Farrell. Review the parsed submission below; tick Apply to push it, or Regenerate if you fixed the issue body and want to re-parse.

    {
      "createdAt": "2026-09-11T17:12:33Z",
      "url": "https://github.com/quantum-advantage-tracker/quantum-advantage-tracker.github.io/issues/245",
      "circuit": "ibm_boston_dcs_nq64_depth73_checks12",
      "name": "ibm_boston_dcs_nq64_depth73_checks12",
      "value": "0.38",
      "method": "Quantum",
      "runtimeQuantum": 870,
      "computeResourcesQuantum": "IBM Heron r3 (ibm_boston)",
      "authors": "Simon Martiel, Jay-U Chung, Alireza Seif, Soumik Ghosh, Ian Hincks, Abhinav Deshpande, Hidetaka Manabe, Hanfeng Gu, Feng Pan, Bill Fefferman, Jay M. Gambetta, and Ali Javadi-Abhari",
      "institutions": "IBM, UChicago, Singapore University of Technology and Design, Nvidia"
    }

    ✅ Applied in 4d27f88

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions