gate_implementation#
Implementing abstract quantum operations as instruction schedules.
Note
Note the conceptual difference between quantum operations
(ops) and
instruction schedules
. Ops represent abstract, ideal computational
operations, whereas instruction schedules represent concrete control signal sequences for the
quantum computer. One can (approximately) implement an op using a number of different
instruction schedules.
Full path: iqm.pulse.gate_implementation
Module Attributes
Sequence of QPU component physical names a quantum operation is acting on. |
|
Calibration data for a particular implementation of a particular quantum operation at a particular locus. |
|
For a particular implementation of a particular quantum operation, maps operation loci to their calibration data. |
|
For a particular quantum operation, maps implementation names to their calibration data. |
|
Maps |
|
Nested dict defining the parameters required by GateImplementation classes. |
|
Locus mapping name for mapping all components that have the drive operation defined. |
|
Locus mapping name for mapping all components that have the readout operation defined. |
|
Locus mapping name for mapping all components that have the flux operation defined and the flux controller has an AWG. |
|
Locus mapping name for mapping all probe lines. |
Functions
|
Parameters that are required to initialize the given Waveform class. |
Classes
Cache for CompositeGate TimeBoxes. |
|
Utility base class for creating gate implementations that are defined in terms of other gate implementations. |
|
Base class for GateImplementations using custom waveform definition with IQPulses. |
|
ABC for implementing quantum gates and other quantum operations using instruction schedules. |
|
Base class for GateImplementations that play a single pulse on a single channel. |
Inheritance
