locus_mappings#
Full path: iqm.pulse.locus_mappings
Locus mapping creation and caching.
A locus mapping defines all the possible loci a particular gate implementation can be applied on, on a specific station. It is determined from the QPU topology and the available control channels of the station.
For operations with zero arity, the locus mapping must consist of single-qubit loci,
and a multiqubit locus is valid if all its components are valid single-qubit loci.
The functions in this module build locus mappings for various GateImplementation subclasses,
and are shared by them. Each function caches the mappings it creates.
Module Attributes
Sequence of QPU component names a quantum operation is acting on. |
|
Mapping from the possible loci of a particular GateImplementation subclass to the QPU components used by the implementation on that locus, for a specific station. |
Functions
|
One-component loci. |
One-component loci that have at least one channel. |
|
One-component loci with drive. |
|
One-component loci (qubits and couplers) with fast flux. |
|
One-component loci with virtual drive capability. |
|
|
One-qubit loci. |
One-qubit loci with physical drive and readout. |
|
|
One-qubit loci with fast flux. |
One-qubit loci with readout. |
|
One-qubit loci with readout and fast flux. |
|
|
One-component loci on probe lines. |
|
Connected (qubit, coupler) pairs. |
Defined for components that have no probe line and that are qubits or resonators. |
|
Two-component loci (qubits + resonators), connected through a coupler with fast flux, symmetric. |
|
Two-component loci connected through a coupler where the coupler and at least one component has fast flux. |
|
|
Two-qubit loci connected through coupler-resonator-coupler. |
Two-qubit loci, connected through a coupler with fast flux, both qubits have drive. |
|
Two-qubit loci connected through a coupler, where the coupler and both qubits have fast flux. |
Classes
Static properties of a station. |
Inheritance
