enums
tergite_autocalibration.utils.dto.enums
Classes:
| Name | Description |
|---|---|
ApplicationStatus |
Used to check in which state the application is as a whole. |
CalibrationResultStatus |
Used by check_data to indicate outcome |
DataStatus |
Used by check_data to indicate outcome |
MeasurementMode |
Used to set the cluster mode e.g. real cluster or re analyse |
QubitRole |
Defines whether a qubit is target or control for a given coupler |
SamplespaceStructure |
In most of the measurements, the settable quantities can be considered 'orthogonal' |
ApplicationStatus
CalibrationResultStatus
DataStatus
MeasurementMode
QubitRole
SamplespaceStructure
Bases: Enum
In most of the measurements, the settable quantities can be considered 'orthogonal' in the sense that all settable point combinations correspond to a particular measurement. For example in a typical spectroscopy you sweep frequencies and amplitudes. Every measurement M corresponds to a distinct (freq, ampl) pair:
In all the schedules this manifests as nested for loops:
However, in some particular nodes such as the coupler_dc_spectroscopy you cannot describe the samplespace
as 'orthogonal' at least not in a clean way.The main reason is that this consists of two disconnected measurements
one after the other. The samplespace looks 'parallel':
In the schedule this manifests as two decoupled for loops: