- Acquisition - `InstrumentCoordinator.retrieve_acquisition` returns an `xarray.Dataset` (!550, #362)
- Qblox backend - Set the `marker_ovr_en` QCoDeS parameter by default to `False` before schedule execution, so that the markers are always controlled using the `MarkerConfiguration` (!576)
- Visualization - Deprecate `visualization` module and its functions `circuit_diagram_matplotlib`, `pulse_diagram_matplotlib`, and `pulse_diagram_plotly`. Create `_visualization` submodule within `schedules`. Make plots via `ScheduleBase` methods (!599). Move visualization tests to `schedules` directory, and make tests for `ScheduleBase` plotting methods
from quantify_scheduler.visualization.circuit_diagram import circuit_diagram_matplotlib
# visualize the circuit
f, ax = circuit_diagram_matplotlib(sched)
f, ax = sched.plot_circuit_diagram()
```
@@ -152,15 +149,15 @@ Valid qubits are strings that appear in the {ref}`device configuration file<sec-
#### Visualization
A {class}`.Schedule` containing operations can be visualized using as a circuit diagram using {func}`~quantify_scheduler.visualization.circuit_diagram.circuit_diagram_matplotlib`.
A {class}`.Schedule` containing operations can be visualized using a circuit diagram by calling its method {meth}`.plot_circuit_diagram`.
Alternatively, one can plot the waveforms in schedules using {func}`~quantify_scheduler.visualization.pulse_diagram.pulse_diagram_matplotlib`:
Alternatively, one can plot the waveforms in schedules using {meth}`.plot_pulse_diagram` (the default plotting backend is `matplotlib`, but it is possible
to use `plotly` by adding the argument {code}`plot_backend='plotly'`):
```{code-cell} ipython3
from quantify_scheduler.operations.pulse_library import SquarePulse, RampPulse
from quantify_scheduler.compilation import determine_absolute_timing
from quantify_scheduler.visualization.pulse_diagram import pulse_diagram_matplotlib