MOVE_CustomWaveforms

Module: iqm.pulse.gates.move

class iqm.pulse.gates.move.MOVE_CustomWaveforms(parent, name, locus, calibration_data, builder)

Bases: FluxPulseGate

Qubit-resonator or qubit-qubit MOVE gate using flux pulses both on a qubit and the coupler.

This class implements the extra phase bookkeeping logic required to make the MOVE gates work as intended. Due to the unknown phase in the MOVE gate definition, the MOVEs need to be applied in pairs, i.e. the state is always moved back to the qubit it came from. Between a pair of MOVE gates, you can apply any number of other two-component gates (CZs for example) to entangle the component where the state was moved to with other qubits. This sequence of gates enclosed by two MOVE operations is called a MOVE sandwich. At the end of a sandwich we have to apply a local phase correction (z rotation) on the state that was moved back to the qubit.

The __call__() method of this class uses the MoveMarker annotation instruction to mark the beginning and end of each MOVE sandwich, in order to enable the calculation of the angle of the z rotation to be applied on the moved qubit at the end of the sandwich to counteract the phase accumulation during the sandwich relative to the computational frame of the qubit. The phase accumulation has two sources:

• Phase due to the frequency detuning between the two MOVE components, proportional to the time duration of the MOVE sandwich.

• Phase due to the virtual z rotations applied on the central components as gates are applied between it and another qubit, which need to be summed up. By convention the central component VirtualRZ angle of the MOVE implementation itself is currently always zero (since only the sum of the central component and qubit z rotation angles matters for MOVE), but we also include it in the sum for completeness.

The phases are calculated and applied on the qubits using apply_move_gate_phase_corrections().

Attributes

root_parameters	Include the detuning between the two MOVE components in the gate parameters for phase tracking.
id	Unique str identifier, needed for certain caching properties.
sub_implementations	Single-component sub-implementations for factorizable gates with len(locus) > 1, otherwise empty.

Methods

Parameters:

• parent (QuantumOp)

• name (str)

• locus (Locus)

• calibration_data (OILCalibrationData)

• builder (ScheduleBuilder)

root_parameters: dict[str, Parameter | Setting | dict] = {'detuning': Parameter(name='', label='Detuning of the computational components at parking', unit='Hz', data_type=<DataType.FLOAT: 1>, collection_type=<CollectionType.SCALAR: 0>, element_indices=None), 'duration': Parameter(name='', label='Gate duration', unit='s', data_type=<DataType.FLOAT: 1>, collection_type=<CollectionType.SCALAR: 0>, element_indices=None), 'rz': {'*': Parameter(name='', label='Z rotation angle', unit='rad', data_type=<DataType.FLOAT: 1>, collection_type=<CollectionType.SCALAR: 0>, element_indices=None)}}

Include the detuning between the two MOVE components in the gate parameters for phase tracking.

Inheritance