iqm.cpc.compiler.station_settings

iqm.cpc.compiler.station_settings#

Mapping calibration observations to station settings.

Calibration observations#

Observations are physical quantities stored in the EXA database. CPC uses them to represent the calibrated values of various instrument settings and gate parameters, needed to execute quantum circuits. The following iqm.station_control.interface.models.observation.ObservationLite fields are needed for this purpose:

  • dut_field: identifies the quantity, and possibly the QPU component(s) it is associated with

  • value: value of the quantity

  • unit: unit of the quantity (currently only base SI units are used, e.g. Hz instead of GHz)

The calibration observations come from two conceptually different sources.

  • ConfigurationSource observations determine the base operating point of the station (in principle an arbitrary choice), and form the input of the calibration procedure.

  • AnalysisSource observations are the output of the calibration procedure.

Mapping to station settings#

When EXA saves its settings as observations, it maps the settings tree paths directly to observation dut_field paths. CPC uses the same direct mapping, with a single minor modification (“options.end_delay”), to map observation dut_field paths to Station Control controller settings paths.

Quantum operation parameters are stored in the EXA settings tree under the top-level branch gates. This data is only used in building the instruction schedules.

  • The controller settings paths may change whenever Station Control is updated, since it consumes the settings. Hence, this may break old calibration sets.

  • New paths may be introduced into the calibration set when the calibration procedure changes, or a new gate implementation is introduced.

CPC only consumes observations created by the calibration process, stored explicitly as calibration sets in the database.

Static station settings#

In addition to the station settings obtained from the calibration set, circuit execution also requires some static settings that typically change only when Station Control is updated, or the station itself is physically modified. The settings that depend on the makeup of a particular station, e.g. the types of the control instruments, are set in the station.yml configuration file if possible. Examples of such settings are the input and output ranges and powers of various instruments. Note that these settings can also be considered a part of the definition of the basic operating point.

For some station settings, the default value is already good.

Finally, there are some static station settings that are defined in this module, mostly because if they were set in station.yml they might negatively interfere with running EXA experiments on the station.

Functions

build_station_settings(*, circuit_qubits, ...)

Build the station settings for executing a batch of quantum circuits using the given QPU elements and calibration data.

find_observation(observation_path, ...[, ...])

Return the value of the given calibration observation, or raise an error.

Classes

Map(parameter, observation_path_template[, ...])

Mapping from a calibration observation path to a corresponding station settings path.

Inheritance

digraph inheritance81eaa59416 { bgcolor=transparent; rankdir=LR; size="8.0, 12.0"; "Map" [URL="iqm.cpc.compiler.station_settings.Map.html#iqm.cpc.compiler.station_settings.Map",fillcolor=white,fontname="Vera Sans, DejaVu Sans, Liberation Sans, Arial, Helvetica, sans",fontsize=10,height=0.25,shape=box,style="setlinewidth(0.5),filled",target="_top",tooltip="Mapping from a calibration observation path to a corresponding station settings path."]; }