Skip to content

QubitWire / Self-directed portfolio project

pyGSTi pathway: explain what gauge freedom changes in a characterization report

Show which changes in a tomography report come from data, model assumptions or representation.

Reviewed

Starting skills
Python, probability, linear algebra and model fitting
Portfolio output
Synthetic GST report with gauge and model-mismatch comparison
A useful completion check
Distinguish changed predictions from changed representation
Hardware needed
No
Data status
Explicitly synthetic; no real-device characterization claimed

pyGSTi’s documentation describes gate-set tomography as fitting a parameterized model to experimental data and provides tools for gauge optimisation. This pathway uses synthetic data to explore how equivalent representations can affect a characterization report. The goal is to produce an explanation that a reviewer can follow from data to model to reported metric. It is not an assertion that a particular device has been characterized, and it is not a current vacancy or a professional certification.

Begin with a small synthetic gate set and a clearly documented collection of circuits. Generate data under a stated sampling model and preserve the seed, number of shots and true model used for the exercise. Fit the model using an official tutorial path, then separate three questions: how well the fit reproduces the observed data, whether the chosen model family is adequate, and how the model is represented for comparison with a target. These questions can interact, but they should not be treated as the same diagnostic.

The core demonstration compares two gauge-optimisation choices while tracking quantities that should retain their operational meaning. The notebook must explain what changed in the representation and what did not change in the predicted observations. Avoid using a single attractive metric as the only evidence of a good characterization. A report can appear closer to a target under one representation while the underlying data and predictive content remain the same. The exercise should make that distinction visible rather than treating gauge optimisation as a mysterious improvement button.

Add a model-mismatch case. Generate a second synthetic data set that the original model does not describe well, and examine the fit diagnostics. State exactly which assumption was changed. This allows the portfolio to discuss the difference between representational freedom and a model that fails to capture the data. Keep the example small enough to reproduce on ordinary computing resources, and do not claim that a synthetic mismatch represents a specific laboratory’s noise. A careful negative result is useful when it identifies the limit of the chosen analysis.

Questions to take with you

Did gauge optimisation improve the hardware?

No. It changes how the estimated model is represented relative to a target. The physical device and observed data have not changed merely because that post-processing step was applied.

Why include model mismatch?

It tests whether the report can recognize a limit in its assumptions. That is different from choosing an equivalent representation of a model that already fits the data.

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)
  • pyGSTi gate-set tomography protocol ↗pyGSTi project · Accessed 2026-10-17

    Model fitting and gauge-optimisation parameters

    Development documentation; match installed release.

  • pyGSTi gauge optimisation ↗pyGSTi project · Accessed 2026-10-17

    Gauge-optimisation tools and choices

    Do not interpret a representation change as improved physical hardware.

Explore other portfolio projects