Tutorial: Operations and Qubits

See also

The complete source code of this tutorial can be found in

Operations and Qubits.ipynb

Gates, measurements and qubits

In the previous tutorials, experiments were created on the quantum-device level. On this level, operations are defined in terms of explicit signals and locations on chip, rather than the qubit and the intended operation. To allow working at a greater level of abstraction, quantify_scheduler allows creating operations on the quantum-circuit level. Instead of signals, clocks, and ports, operations are defined by the the effect they have on specific qubits. This representation of the schedules can be compiled to the quantum-device level to create the pulse schemes.

In this tutorial we show how to define operations on the quantum-circuit level, combine them into schedules, and show their circuit-level visualization. We go through the configuration file needed to compile the schedule to the quantum-device level and show how these configuration files can be created automatically and dynamically. Finally, we showcase the hybrid nature of quantify_scheduler, allowing the scheduling circuit-level and device-level operations side by side in the same schedule.

Many of the gates used in the circuit layer description are defined in gate_library such as Reset, X90 and Measure. Operations are instantiated by providing them with the name of the qubit(s) on which they operate:

from quantify_scheduler.operations.gate_library import CZ, Measure, Reset, X90

q0, q1 = ("q0", "q1")
CZ(q0, q1)
{'name': 'Reset q0', 'gate_info': {'unitary': None, 'tex': '$|0\\rangle$', 'plot_func': 'quantify_scheduler.visualization.circuit_diagram.reset', 'qubits': ['q0'], 'operation_type': 'reset'}, 'pulse_info': [], 'acquisition_info': [], 'logic_info': {}}

Let’s investigate the different components present in the circuit-level description of the operation. As an example, we create a 45 degree rotation operation over the x-axis.

from pprint import pprint
from quantify_scheduler.operations.gate_library import Rxy

rxy45 = Rxy(theta=45.0, phi=0.0, qubit=q0)
{'acquisition_info': [],
 'gate_info': {'operation_type': 'Rxy',
               'phi': 0.0,
               'plot_func': 'quantify_scheduler.visualization.circuit_diagram.gate_box',
               'qubits': ['q0'],
               'tex': '$R_{xy}^{45, 0}$',
               'theta': 45.0,
               'unitary': array([[0.92387953+0.j        , 0.        -0.38268343j],
       [0.        -0.38268343j, 0.92387953+0.j        ]])},
 'logic_info': {},
 'name': "Rxy(45, 0, 'q0')",
 'pulse_info': []}

As we can see, the structure of a circuit-level operation is similar to a pulse-level operation. However, the information is contained inside the gate_info entry rather than the pulse_info entry of the data dictionary. Importantly, there is no device-specific information coupled to the operation such that it represents the abstract notion of this qubit rotation, rather than how to perform it on any physical qubit implementation.

The entries present above are documented in the operation schema. Generally, these schemas are only important when defining custom operations, which is not part of this tutorial. This schema can be inspected via:

import importlib.resources
import json
from quantify_scheduler import schemas

operation_schema = json.loads(importlib.resources.read_text(schemas, "operation.json"))
{'operation_type': {'description': 'Defines what class of operations this gate '
                                   'refers to (e.g. Rxy, CZ etc.).',
                    'type': 'string'},
 'plot_func': {'description': 'reference to a function for plotting this '
                              'operation. If not specified, defaults to using '
               'type': ['string', 'null']},
 'qubits': {'description': 'A list of strings indicating the qubits the gate '
                           'acts on. Valid qubits are strings that appear in '
                           'the device_config.json file.',
            'type': 'array'},
 'symmetric': {'description': 'A boolean to indicate whether a two qubit gate '
                              'is symmetric. This is used in the device config '
                              'compilation stage. By default, it is set as '
               'type': 'boolean'},
 'tex': {'description': 'latex snippet for plotting', 'type': 'string'},
 'unitary': {'description': 'A unitary matrix describing the operation.'}}

Schedule creation from the circuit layer (Bell)

The circuit-level operations can be used to create a schedule within quantify_scheduler using the same method as for the pulse-level operations. This enables creating schedules on a more abstract level. We exemplify this extra layer of abstraction by creating a schedule for measuring Bell violations.


Within a single schedule, high-level circuit layer operations can be mixed with quantum-device level operations. This mixed representation is useful for experiments where some pulses cannot easily be represented as qubit gates. An example of this is given by the Chevron experiment given in Mixing pulse and circuit layer operations (Chevron).

As the first example, we want to create a schedule for performing the Bell experiment. The goal of the Bell experiment is to create a Bell state \(|\Phi ^+\rangle=\frac{1}{2}(|00\rangle+|11\rangle)\) which is a perfectly entangled state, followed by a measurement. By rotating the measurement basis, or equivalently one of the qubits, it is possible to observe violations of the CSHS inequality.

We create this experiment using the quantum-circuit level description. This allows defining the Bell schedule as:

import numpy as np
from quantify_scheduler import Schedule
from quantify_scheduler.operations.gate_library import CZ, Measure, Reset, Rxy, X90

sched = Schedule("Bell experiment")

for acq_idx, theta in enumerate(np.linspace(0, 360, 21)):
    sched.add(Reset(q0, q1))
    sched.add(X90(q1), ref_pt="start")  # Start at the same time as the other X90
    sched.add(CZ(q0, q1))
    sched.add(Rxy(theta=theta, phi=0, qubit=q0))

    sched.add(Measure(q0, acq_index=acq_idx), label="M q0 {:.2f} deg".format(theta))
    sched.add(  # Start at the same time as the other measure
        Measure(q1, acq_index=acq_idx),
        label="M q1 {:.2f} deg".format(theta),

Schedule "Bell experiment" containing (66) 147  (unique) operations.

By scheduling 7 operations for 21 different values for theta we indeed get a schedule containing 7*21=147 operations. To minimize the size of the schedule, identical operations are stored only once. For example, the CZ operation is stored only once but used 21 times, which leaves only 66 unique operations in the schedule.


The acquisitions are different for every iteration due to their different acq_index. The Rxy-gate rotates over a different angle every iteration and must therefore also be different for every iteration (except for the last since \(R^{360}=R^0\)). Hence the number of unique operations is 3*21-1+4=66.

Visualizing the quantum circuit

We can directly visualize the created schedule on the quantum-circuit level. This visualization shows every operation on a line representing the different qubits.

%matplotlib inline
import matplotlib.pyplot as plt

_, ax = sched.plot_circuit_diagram()
# all gates are plotted, but it doesn't all fit in a matplotlib figure.
# Therefore we use :code:`set_xlim` to limit the number of gates shown.
ax.set_xlim(-0.5, 9.5)

In previous tutorials, we visualized the schedules on the pulse level using plot_pulse_diagram() . Up until now, however, all gates have been defined on the quantum-circuit level without defining the corresponding pulse shapes. Therefore, trying to run plot_pulse_diagram() will raise an error which signifies no pulse_info is present in the schedule:

RuntimeError                              Traceback (most recent call last)
Cell In [6], line 1
----> 1 sched.plot_pulse_diagram()

File ~/checkouts/readthedocs.org/user_builds/quantify-quantify-scheduler/envs/latest/lib/python3.8/site-packages/quantify_scheduler/schedules/schedule.py:289, in ScheduleBase.plot_pulse_diagram(self, port_list, sampling_rate, modulation, modulation_if, plot_backend, plot_kwargs)
    282 if plot_backend == "mpl":
    283     # NB imported here to avoid circular import
    284     # pylint: disable=import-outside-toplevel
    285     from quantify_scheduler.visualization.pulse_diagram import (
    286         pulse_diagram_matplotlib,
    287     )
--> 289     return pulse_diagram_matplotlib(
    290         schedule=self,
    291         sampling_rate=sampling_rate,
    292         port_list=port_list,
    293         modulation=modulation,
    294         modulation_if=modulation_if,
    295         **plot_kwargs,
    296     )
    297 if plot_backend == "plotly":
    298     # NB imported here to avoid circular import
    299     # pylint: disable=import-outside-toplevel
    300     from quantify_scheduler.visualization.pulse_diagram import (
    301         pulse_diagram_plotly,
    302     )

File ~/checkouts/readthedocs.org/user_builds/quantify-quantify-scheduler/envs/latest/lib/python3.8/site-packages/quantify_scheduler/visualization/pulse_diagram.py:483, in pulse_diagram_matplotlib(schedule, port_list, sampling_rate, modulation, modulation_if, ax)
    449 def pulse_diagram_matplotlib(
    450     schedule: Union[Schedule, CompiledSchedule],
    451     port_list: Optional[List[str]] = None,
    455     ax: Optional[matplotlib.axes.Axes] = None,
    456 ) -> Tuple[matplotlib.figure.Figure, matplotlib.axes.Axes]:
    457     """
    458     Plots a schedule using matplotlib.
    481         The matplotlib ax.
    482     """
--> 483     times, pulses = sample_schedule(
    484         schedule,
    485         sampling_rate=sampling_rate,
    486         port_list=port_list,
    487         modulation=modulation,
    488         modulation_if=modulation_if,
    489     )
    490     if ax is None:
    491         _, ax = plt.subplots()

File ~/checkouts/readthedocs.org/user_builds/quantify-quantify-scheduler/envs/latest/lib/python3.8/site-packages/quantify_scheduler/visualization/pulse_diagram.py:384, in sample_schedule(schedule, port_list, modulation, modulation_if, sampling_rate)
    381 logger.debug(f"time_window {time_window}, port_map {port_map}")
    383 if time_window is None:
--> 384     raise RuntimeError(
    385         f"Attempting to sample schedule {schedule.name}, "
    386         "but the schedule does not contain any `pulse_info`. "
    387         "Please verify that the schedule has been populated and "
    388         "device compilation has been performed."
    389     )
    391 timestamps = np.arange(time_window[0], time_window[1], 1 / sampling_rate)
    392 waveforms = {key: np.zeros_like(timestamps) for key in port_map}

RuntimeError: Attempting to sample schedule Bell experiment, but the schedule does not contain any `pulse_info`. Please verify that the schedule has been populated and device compilation has been performed.

And similarly for the timing_table:

ValueError                                Traceback (most recent call last)
Cell In [7], line 1
----> 1 sched.timing_table

File ~/checkouts/readthedocs.org/user_builds/quantify-quantify-scheduler/envs/latest/lib/python3.8/site-packages/quantify_scheduler/schedules/schedule.py:364, in ScheduleBase.timing_table(self)
    361 for schedulable in self.schedulables.values():
    362     if "abs_time" not in schedulable:
    363         # when this exception is encountered
--> 364         raise ValueError("Absolute time has not been determined yet.")
    365     operation = self.operations[schedulable["operation_repr"]]
    367     # iterate over pulse information

ValueError: Absolute time has not been determined yet.

Device configuration

Up until now the schedule is not specific to any qubit implementation. The aim of this section is to add device specific information to the schedule. This knowledge is contained in the device configuration, which we introduce in this section. By compiling the schedule to the quantum-device layer, we incorporate the device configuration into the schedule (for example by adding pulse information to every gate) and thereby enable it to run on a specific qubit implementation.

To start this section, we will unpack the structure of the device configuration. Here we will use an example device configuration for a transmon-based system that is used in the quantify-scheduler test suite.

from quantify_scheduler.backends.circuit_to_device import DeviceCompilationConfig
from quantify_scheduler.schemas.examples.circuit_to_device_example_cfgs import (

device_cfg = DeviceCompilationConfig.parse_obj(example_transmon_cfg)

['backend', 'clocks', 'elements', 'edges']

Before explaining how this can be used to compile schedules, let us first investigate the contents of the device configuration.


The backend of the device configuration specifies what function will be used to add pulse information to the gates. In other words, it specifies how to interpret the qubit parameters present in the device configuration and achieve the required gates. Let us briefly investigate the backend function:

from quantify_scheduler.helpers.importers import import_python_object_from_string

Help on function compile_circuit_to_device in module quantify_scheduler.backends.circuit_to_device:

compile_circuit_to_device(schedule: quantify_scheduler.schedules.schedule.Schedule, device_cfg: Union[quantify_scheduler.backends.circuit_to_device.DeviceCompilationConfig, dict, NoneType]) -> quantify_scheduler.schedules.schedule.Schedule
    Adds the information required to represent operations on the quantum-device
    abstraction layer to operations that contain information on how to be represented
    on the quantum-circuit layer.
        The schedule to be compiled.
        Device specific configuration, defines the compilation step from
        the quantum-circuit layer to the quantum-device layer description.
        Note, if a dictionary is passed, it will be parsed to a

The device configuration also contains the parameters required by the backend for all qubits and edges.

['q0', 'q1']
['q0.01', 'q0.ro', 'q1.01', 'q1.ro']

For every qubit and edge we can investigate the contained parameters.

{'reset': OperationCompilationConfig(factory_func='quantify_scheduler.operations.pulse_library.IdlePulse', factory_kwargs={'duration': 0.0002}, gate_info_factory_kwargs=None), 'Rxy': OperationCompilationConfig(factory_func='quantify_scheduler.operations.pulse_factories.rxy_drag_pulse', factory_kwargs={'amp180': 0.32, 'motzoi': 0.45, 'port': 'q0:mw', 'clock': 'q0.01', 'duration': 2e-08}, gate_info_factory_kwargs=['theta', 'phi']), 'Z': OperationCompilationConfig(factory_func='quantify_scheduler.operations.pulse_library.SoftSquarePulse', factory_kwargs={'amp': 0.23, 'duration': 4e-09, 'port': 'q0:fl', 'clock': 'cl0.baseband'}, gate_info_factory_kwargs=None), 'measure': OperationCompilationConfig(factory_func='quantify_scheduler.operations.measurement_factories.dispersive_measurement', factory_kwargs={'port': 'q0:res', 'clock': 'q0.ro', 'pulse_type': 'SquarePulse', 'pulse_amp': 0.25, 'pulse_duration': 1.6e-07, 'acq_delay': 1.2e-07, 'acq_duration': 3e-07, 'acq_channel': 0}, gate_info_factory_kwargs=['acq_index', 'bin_mode', 'acq_protocol'])}
{'amp180': 0.32, 'motzoi': 0.45, 'port': 'q0:mw', 'clock': 'q0.01', 'duration': 2e-08}
{'q0_q1': {'CZ': OperationCompilationConfig(factory_func='quantify_scheduler.operations.pulse_factories.composite_square_pulse', factory_kwargs={'square_port': 'q0:fl', 'square_clock': 'cl0.baseband', 'square_amp': 0.5, 'square_duration': 2e-08, 'virt_z_parent_qubit_phase': 44, 'virt_z_parent_qubit_clock': 'q0.01', 'virt_z_child_qubit_phase': 63, 'virt_z_child_qubit_clock': 'q1.01'}, gate_info_factory_kwargs=None)}}
{'q0.01': 6020000000.0, 'q0.ro': 7040000000.0, 'q1.01': 5020000000.0, 'q1.ro': 6900000000.0}

Lastly, the complete example device configuration (also see DeviceCompilationConfig):

{'backend': 'quantify_scheduler.backends.circuit_to_device.compile_circuit_to_device',
 'clocks': {'q0.01': 6020000000.0,
            'q0.ro': 7040000000.0,
            'q1.01': 5020000000.0,
            'q1.ro': 6900000000.0},
 'edges': {'q0_q1': {'CZ': {'factory_func': 'quantify_scheduler.operations.pulse_factories.composite_square_pulse',
                            'factory_kwargs': {'square_amp': 0.5,
                                               'square_clock': 'cl0.baseband',
                                               'square_duration': 2e-08,
                                               'square_port': 'q0:fl',
                                               'virt_z_child_qubit_clock': 'q1.01',
                                               'virt_z_child_qubit_phase': 63,
                                               'virt_z_parent_qubit_clock': 'q0.01',
                                               'virt_z_parent_qubit_phase': 44}}}},
 'elements': {'q0': {'Rxy': {'factory_func': 'quantify_scheduler.operations.pulse_factories.rxy_drag_pulse',
                             'factory_kwargs': {'amp180': 0.32,
                                                'clock': 'q0.01',
                                                'duration': 2e-08,
                                                'motzoi': 0.45,
                                                'port': 'q0:mw'},
                             'gate_info_factory_kwargs': ['theta', 'phi']},
                     'Z': {'factory_func': 'quantify_scheduler.operations.pulse_library.SoftSquarePulse',
                           'factory_kwargs': {'amp': 0.23,
                                              'clock': 'cl0.baseband',
                                              'duration': 4e-09,
                                              'port': 'q0:fl'}},
                     'measure': {'factory_func': 'quantify_scheduler.operations.measurement_factories.dispersive_measurement',
                                 'factory_kwargs': {'acq_channel': 0,
                                                    'acq_delay': 1.2e-07,
                                                    'acq_duration': 3e-07,
                                                    'clock': 'q0.ro',
                                                    'port': 'q0:res',
                                                    'pulse_amp': 0.25,
                                                    'pulse_duration': 1.6e-07,
                                                    'pulse_type': 'SquarePulse'},
                                 'gate_info_factory_kwargs': ['acq_index',
                     'reset': {'factory_func': 'quantify_scheduler.operations.pulse_library.IdlePulse',
                               'factory_kwargs': {'duration': 0.0002}}},
              'q1': {'Rxy': {'factory_func': 'quantify_scheduler.operations.pulse_factories.rxy_drag_pulse',
                             'factory_kwargs': {'amp180': 0.4,
                                                'clock': 'q1.01',
                                                'duration': 2e-08,
                                                'motzoi': 0.25,
                                                'port': 'q1:mw'},
                             'gate_info_factory_kwargs': ['theta', 'phi']},
                     'measure': {'factory_func': 'quantify_scheduler.operations.measurement_factories.dispersive_measurement',
                                 'factory_kwargs': {'acq_channel': 1,
                                                    'acq_delay': 1.2e-07,
                                                    'acq_duration': 3e-07,
                                                    'clock': 'q1.ro',
                                                    'port': 'q1:res',
                                                    'pulse_amp': 0.21,
                                                    'pulse_duration': 1.6e-07,
                                                    'pulse_type': 'SquarePulse'},
                                 'gate_info_factory_kwargs': ['acq_index',
                     'reset': {'factory_func': 'quantify_scheduler.operations.pulse_library.IdlePulse',
                               'factory_kwargs': {'duration': 0.0002}}}}}

Device compilation

Now that we went through the different components of the configuration file, let’s use it to compile our previously defined schedule. The device_compile() function takes care of this task and adds pulse information based on the configuration file, as discussed above. It also determines the timing of the different pulses in the schedule. Also see Device and Hardware compilation combined.

from quantify_scheduler.compilation import device_compile

pulse_sched = device_compile(sched, device_cfg)

Now that the timings have been determined, we can show the first few rows of the timing_table:

pulse_sched.timing_table.hide(slice(11, None), axis="index").hide(
    "waveform_op_id", axis="columns"
  port clock is_acquisition abs_time duration operation wf_idx
0 None cl0.baseband False 0.0 ns 200,000.0 ns Reset('q0','q1') 0
1 None cl0.baseband False 0.0 ns 200,000.0 ns Reset('q0','q1') 1
2 q0:mw q0.01 False 200,000.0 ns 20.0 ns X90(qubit='q0') 0
3 q1:mw q1.01 False 200,000.0 ns 20.0 ns X90(qubit='q1') 0
4 q0:fl cl0.baseband False 200,020.0 ns 20.0 ns CZ(qC='q0',qT='q1') 0
5 None q0.01 False 200,020.0 ns 0.0 ns CZ(qC='q0',qT='q1') 1
6 None q1.01 False 200,020.0 ns 0.0 ns CZ(qC='q0',qT='q1') 2
7 q0:mw q0.01 False 200,040.0 ns 20.0 ns Rxy(theta=0, phi=0, qubit='q0') 0
8 q0:res q0.ro False 200,060.0 ns 160.0 ns Measure('q0', acq_channel=0, acq_index=0, acq_protocol="None", bin_mode=None) 0
9 q0:res q0.ro True 200,180.0 ns 300.0 ns Measure('q0', acq_channel=0, acq_index=0, acq_protocol="None", bin_mode=None) 0
10 q1:res q1.ro False 200,060.0 ns 160.0 ns Measure('q1', acq_channel=0, acq_index=0, acq_protocol="None", bin_mode=None) 0

And since all pulse information has been determined, we can show the pulse diagram as well:

f, ax = pulse_sched.plot_pulse_diagram()
ax.set_xlim(0.4005e-3, 0.4006e-3)
(0.0004005, 0.0004006)

Quantum Devices and Elements

The device configuration contains all knowledge of the physical device under test (DUT). To generate these device configurations on the fly, quantify_scheduler provides the QuantumDevice and DeviceElement classes.

These classes contain the information necessary to generate the device configs and allow changing their parameters on-the-fly. The QuantumDevice class represents the DUT containing different DeviceElement s. Currently, quantify_scheduler contains the BasicTransmonElement class to represent a fixed-frequency transmon qubit connected to a feedline. We show their interaction below:

from quantify_scheduler.device_under_test.quantum_device import QuantumDevice
from quantify_scheduler.device_under_test.transmon_element import BasicTransmonElement

# First create a device under test
dut = QuantumDevice("DUT")

# Then create a transmon element
qubit = BasicTransmonElement("qubit")

# Finally, add the transmon element to the QuantumDevice
dut, dut.components()
AttributeError                            Traceback (most recent call last)
Cell In [19], line 11
      8 qubit = BasicTransmonElement("qubit")
     10 # Finally, add the transmon element to the QuantumDevice
---> 11 dut.add_component(qubit)
     12 dut, dut.components()

File ~/checkouts/readthedocs.org/user_builds/quantify-quantify-scheduler/envs/latest/lib/python3.8/site-packages/qcodes/utils/helpers.py:439, in DelegateAttributes.__getattr__(self, key)
    436     except AttributeError:
    437         pass
--> 439 raise AttributeError(
    440     "'{}' object and its delegates have no attribute '{}'".format(
    441         self.__class__.__name__, key))

AttributeError: 'QuantumDevice' object and its delegates have no attribute 'add_component'

The different transmon properties can be set through attributes of the BasicTransmonElement class instance, e.g.:


for submodule_name, submodule in qubit.submodules.items():
    print(f"{qubit.name}.{submodule_name}: {list(submodule.parameters.keys())}")

The device configuration is now simply obtained using dut.generate_device_config(). In order for this command to provide a correct device configuration, the different parameters need to be specified in the BasicTransmonElement and QuantumDevice objects.


Mixing pulse and circuit layer operations (Chevron)

As well as defining our schedules in terms of gates, we can also mix the circuit layer representation with pulse-level operations. This can be useful for experiments involving pulses not easily represented by Gates, such as the Chevron experiment. In this experiment, we want to vary the length and amplitude of a square pulse between X gates on a pair of qubits.

from quantify_scheduler import Schedule
from quantify_scheduler.operations.gate_library import Measure, Reset, X, X90
from quantify_scheduler.operations.pulse_library import SquarePulse
from quantify_scheduler.resources import ClockResource

sched = Schedule("Chevron Experiment")
acq_idx = 0

# Multiples of 4 ns need to be used due to sampling rate of the Qblox modules
for duration in np.linspace(start=20e-9, stop=60e-9, num=6):
    for amp in np.linspace(start=0.1, stop=1.0, num=10):
        reset = sched.add(Reset("q0", "q1"))
        sched.add(X("q0"), ref_op=reset, ref_pt="end")  # Start at the end of the reset
        # We specify a clock for tutorial purposes, Chevron experiments do not necessarily use modulated square pulses
        square = sched.add(SquarePulse(amp, duration, "q0:mw", clock="q0.01"))
        sched.add(X90("q0"), ref_op=square)  # Start at the end of the square pulse
        sched.add(X90("q1"), ref_op=square)
        sched.add(Measure(q0, acq_index=acq_idx), label=f"M q0 {acq_idx}")
        sched.add(  # Start at the same time as the other measure
            Measure(q1, acq_index=acq_idx),
            label=f"M q1 {acq_idx}",

        acq_idx += 1

sched.add_resources([ClockResource("q0.01", 6.02e9)])  # Manually add the pulse clock
fig, ax = sched.plot_circuit_diagram()
ax.set_xlim(-0.5, 9.5)
for t in ax.texts:
    if t.get_position()[0] > 9.5:

This example shows that we add gates using the same interface as pulses. Gates are Operations, and as such support the same timing and reference operators as Pulses.


When adding a Pulse to a schedule, the clock is not automatically added to the resources of the schedule. It may be necessary to add this clock manually, as in the final line of the example above.

Device and Hardware compilation combined

Rather than first using device_compile() and subsequently hardware_compile(), the two function calls can be combined using qcompile().

from quantify_scheduler.compilation import qcompile
from quantify_scheduler.device_under_test.quantum_device import QuantumDevice
from quantify_scheduler.device_under_test.transmon_element import BasicTransmonElement

dut = QuantumDevice("DUT")
q0 = BasicTransmonElement("q0")
q1 = BasicTransmonElement("q1")

compiled_sched = qcompile(
    schedule=sched, device_cfg=dut.generate_device_config(), hardware_cfg=None

So, finally, we can show the timing table associated to the chevron schedule and plot its pulse diagram:

compiled_sched.timing_table.hide(slice(11, None), axis="index").hide(
    "waveform_op_id", axis="columns"
f, ax = compiled_sched.plot_pulse_diagram()
ax.set_xlim(200e-6, 200.4e-6)