This notebook contains a list of frequently asked questions and their answers. If the answer is short, example code is given directly in this notebook; if not, then the reader is referred to other pyGSTi tutorials and examples.
"Gate Set Tomography" (GST) is a protocol that attempts to infer the quantum operations a device is performing by analyzing data generated by it. The device is viewed as a black box, so that physics-level details of its construction and operation are not needed. GST characterizes quantum gate operations, state preparations, and measurement operations simultaneously, avoiding the chicken-and-egg problem of state and process tomography, which has been shown to be problematic. For more information about the algorithms and theory of GST, please see Demonstration of qubit operations below a rigorous fault tolerance threshold with gate set tomography, Nature Communications 8 (2017)
PyGSTi is the name of (this) software, which implements the various parts of the GST protocol(s). It is written (almost) entirely in Python, and is released as an open-source software under the Apache License Version 2.0. "pyGSTi" stands for "python GST implementation".
Using pyGSTi, running GST is fairly simple. Single-qubit GST is demonstrated in full in the GST overview tutorial, and 2-qubit GST (though very similar to 1-qubit GST) is separately demonstrated in this 2Q-GST example. The core GST algorithm is run by calling
pygsti.do_stdpractice_gst. There are also example notebooks on creating 2-qubit GST models and generating error bars with 2Q-GST.
Constraint on the gates (and SPAM operations) in pyGSTi are imposed via the "parameterization" of
Model objects. Each
Model essentially knows how to map some vector of (real-valued) "parameters" to a full set of gate matrices and SPAM vectors - and whether a given set of matrices & vectors can be reached depends on whether there exists a set of parameters that maps onto it. The parameterization used by an
ExplicitOpModel object can be changed among commonly used parameterizations via the
set_all_parameterizations member function. To constrain gates and SPAM operations to be trace preserving, simply call
Similar to the above question, you simply set the parameterization of your target
Model to "CPTP" before calling
do_stdpractice_gst. Note that currenlty this only ensures that the gates are CPTP - not the SPAM operations. (Attempts to parameterize the SPAM operations as such have resulted in poor performance and are considered an experimental feature.)
A "gauge transformation" is a special type of mapping from one gate set to another which preserves all predicted physical outcomes (hence the name "gauge"). Thus, gauge transformations map between physically equivalent gate sets, and the set of all gauge transformations partitions the space of gate sets into physically-distinct equivalence classes. Gauge optimization refers to the process by which one finds the gate set within an equivalence class which optimizes some metric - typically the frobenius distance between the gate set and some "target gate set". In pyGSTi, gauge optimization is invoked using the
pygsti.gaugeopt_to_target method (which minimizes the distance between a
GateSet and a target
GateSet) or the
pygsti.gaugeopt_custom method (which accepts a user-defined objective function).
Specifying the "details" of gauge optimization is essentially specifying the objective function. The arguments of
gaugeopt_to_target (detailed in its docstring and pyGSTi's online docs) describe how to change which distance metric is used (the frobenius distance, process fidelity, or the Jamiolkowski trace distance) when comparing gates, and how to put different weighting factors on individual gates (via the
itemWeights argument). In higher-level functions, gauge-optimization details are specified by simply creating a dictionary of
gauge_opt_to_target's arguments. Adding a new gauge-optimization to an existing
pygsti.objects.Results object is demonstrated in the "adding new gauge optimizations" example. One particularly powerful way to control gauge optimization is by specifying an imperfect target
Model which includes the errors you expect to see in the gates. This is simple to do, and outlined in the "non-ideal gauge optimization targets" example.
There are two primary ways of speeding up the GST analysis within pyGSTi: 1) using more/multiple processors and 2) reducing the number of gate sequences being analyzed. The first option is achieved by passing the core pyGSTi routines (e.g.
mpi4py.MPI.Comm object (and often a per-core memory limit too), and is demonstrated in an example. The second option involves more of a tradeoff, as decreasing the number of sequences with reduce the accuracy of GST and/or its robustness. Restricting GST to shorter sequences (reducing the "max-lengths" used) will result in less accurate estimates, i.e. larger error bars. The use of "fiducial pair reduction" techniques, outlined in this tutorial, retains the accuracy of GST while eliminating sequences. This, however, results is less robustness and sensitivity to out-of-model errors.
Because their computation can be time-consuming, the process of computing error bars on report quantities has been split into more or less three pieces in pyGSTi:
In previous pyGSTi versions, simply doing step 3 would automatically trigger steps 1 and 2, but this is no longer the case. The reason for this is that steps 1 and 2 (especially 1) can take a long time, and one may want to run them on a separate machine with more processing power. As demonstrated in the 2Q-GST error bars example, you must first add a
ConfidenceRegionFactory object to your results, then call
project_hessian (perhaps on a large multiprocessor machine). After this, you can use
confidenceLevel=95, for instance, to create a report with 95% confidence interval error bars.
A note about Hessian projection:
After computing a Hessian you must specify how the Hessian is projected onto a space orthogonal to the manifold of gauge degrees of freedom. This is done via
ConfidenceRegionFactory.project_hessian(...). The basic idea here is that there is a choice, similar to the choice of which metric to use for gauge optimization, which defines the notion of "orthogonality" and thereby how error bars are constructed for the non-gauge degrees of freedom. There are several ways pyGSTi can do this, and you specify which way you want by the
projection_type argument to
"optimal gate CIs", is to optimize this metric so as to make the error bars as small as possible - the but this can sometimes take a long time. For faster run times, one can use the
"std" (standard) option which takes almost no time but just chooses an arbitrary gauge metric. A third
"intrinsic error" type attempts to balance speed with small confidence intervals, but is currently just experimental. Using either of the latter two options is fine, but may result in artificially large error bars. So if you use
"intrinsic error" and get error bars you're happy with, then great. If the error bars seem too large, it's probably worth setting the parameter to
"optimal gate CIs" and getting some coffee.
Currently there aren't many options for speeding up the core computation required to generate a report (using, e.g.
pygsti.report.construct_standard_report. One can, however, take advantage of the caching built into the pyGSTi
Report objects that can effectively speedup report-generation times.
Report objects cache the various tables and plots within a report. This can be used to generate multiple similar versions of the same report, but with different parameters. For instance, you might want to generate one "full" version (with
brevity=0, the default) and one "brief" version of the same report. Furthermore, report factory functions such as
construct_standard_report take an optional
Workspace as an argument that caches the various tables and plots within a report as an argument. This
Workspace can be stored and shared between multiple report factories to utilize the cache within that
Workspace. This is useful if you want to construct two version of the same, or similar, reports. For instance, you might want to generate one "full" report (with
brevity=0, the default) and one "brief" report from the same results. This functionality can be used to generate a
Workspace on a large and fast multi-processor machine (which ran the main GST analysis). For example, using a workspace as shown below would dramatically speed up the 2nd and 3rd
#On large & fast computer results = pygsti.do_long_sequence_gst(..., comm=my_comm) crfact = results.estimates['default'].add_confidence_region_factory('go0', 'final') crfact.compute_hessian(comm=comm) # use multiple processors for hessian calc crfact.project_hessian('intrinsic error') # see above ws = pygsti.report.Workspace() report = pygsti.report.construct_standard_report(results, "Dummy Title", confidenceLevel=95) report._build() # This method is used internally to build workspace components pickle.dump(report, open("my_saved_report.pkl","wb") ) #On small laptop report = pickle.load( open("my_saved_report.pkl","rb") ) report.write_html(results, "full_report.html") # FAST! report.write_html(results, "brief_report.html", brevity=3) # even FASTER!
One way of making germ selection faster is running it on muliple processors. Using
mpi4py to accelerate germ selection is demonstrated in this example. We also continue to make minor improvements to the germ selection routines, so that they should be (somewhat) faster in more recent versions of pyGSTi.
Context dependence is a broad category that includes many types of noise, and some types are easier to model than others within pyGSTi. One case that is easy to model is when a gate behaves differently when it precedes or follows another gate (e.g. due to ring-down from the preceding gate). Creating a model for this case and running GST to optimize the model is demonstrated in this example on context dependence.
Yes, pyGSTi's GST implementation is pretty much agnostic to the Hilbert-space dimension of system being characterized. When you have two ions but no independent readout this looks like a 3-level or qutrit system because you can only distinguish between "0 ions are bright", "1 ion is bright" and "2 ions are bright" (rather than a full 2-qubit space). Because this is a common case, pyGSTi has a specific routine (
make_qutrit_model) for forming qutrit models. Then running GST on the model follows the same pattern as any other model. Our example of running GST on a qutrit demonstrates this.
Linear Gate Set Tomography (LGST) provides a rough estimate of the gate (really layer) operations of a system. It's primary advantanges are that it doesn't require much data and it's very fast to compute. If all you're looking for is a rough estimate, it's useful to be able to visualize LGST results in, for example, a HTML report. This can now be easily done using
pygsti.do_linear_gst in a parallel fashion to how you would use
do_linear_gst generates a
Results object that can then be used to generate a report, as demonstrated in this example.
For certain types of "leakage", yes: PyGSTi can create models whose operations act on n-level state spaces. For instance, a 3-level space can be interpreted as a qubit plus a leakage level. Model operations must be constructed and interpreted accordingly, but apart from these nuances pyGSTi treats a system with leakage levels exactly as it would a larget (e.g. multi-qubit) system. See this example analyzing a qubit + leakage level.
Stay calm; don't panic. Version 0.9.7 brought with it a number of compatibility-breaking improvements (for instance, "gate sets" have turned into "models" and "gate strings" have become "circuits"). To help you transition from version 0.9.6 and below to version 0.9.7 we've built into the latter a few pieces of functionality:
scripts/upgrade2v0.9.7.py script automatically renames everything that has been renamed in pyGSTi. In many cases, this is all you need to upgrade your scripts and jupyter notebooks. You simply pass the script the names of files you want upgraded, e.g.
python path/to/pyGSTi/scripts/upgrade2v0.9.7.py myScript.py myNotebook.ipynb ...
The conversion will automatically create backup files with a
.bak extension, so there's no chance of it destroying your hard work.
pygsti.iocontains the context-manager
enable_old_object_unpickling, that can be used to temporarily enable the un-pickling of version 0.9.6 objects. You should then re-pickle the objects using version 0.9.7. Here's an example:
with pygsti.io.enable_old_object_unpickling(): # within this block you can load old pickles with open("pygsti0.9.6_gateset.pkl",'rb') as f: mdl = pickle.load(f) # works!