Skip to content

Release Notes - Latest Stable Version

Stable Release 26.7.0

Release date 30.07.2026

Requires: LabOne 26.7

Requires: ZQCS Host Software 26.7.0b6 (when using ZQCS)

Supports: Applications Library 26.7.0

DSL

  • Functionality Added the quantum_element_uids property to the QPU class, which returns the list of quantum element UIDs in the QPU.
  • Functionality Added reset_oscillator_phase to laboneq.simple.dsl namespace, which resets the phase of the oscillator associated with a given logical signal. This function existed already but was not directly exposed.

  • Functionality Added an option for the caller of a quantum operation to override the pulse name used by create_pulse.

    The create_pulse function used inside many quantum operations allows the implementation of the quantum operation to directly supply a pulse name, which is used to identify the pulse and forms part of the pulse UID. However, this was not exposed via quantum operations.

    A user may wish to generate different pulse objects even when using the same quantum operations. For example, in an experiment with M measure operations, a user may wish to replace a specific subset of those measurements with new pulses.

    To enable this, create_pulse now accepts a new special key named name in the dictionary of pulse options. This allows the user to override the supplied name by passing, for example, qop.measure(q, handle, readout_pulse={"name": "my-special-tag"}) when calling a quantum operation.

  • Documentation Added documentation for the list of real-time sweepable parameters vs near-time only parameters.

  • Documentation Added reference documentation for for_each and sweep_range.
  • Bug Fix Fixed a bug where runtime type validation for FIR precompensation coefficients failed with NumPy 2.5.
  • Bug Fix Fixed a bug where a SweepParameter/LinearSweepParameter arithmetic expression that re-used one of its own operands (e.g. 2 * param - param) produced a corrupted parameter whose values could not be compiled, raising TypeError: 'SweepParameter' object is not subscriptable.

Compiler

  • Functionality Changed exception type from RuntimeError to LabOneQException when an invalid device combination is provided.
  • Functionality The compiler now raises an exception when an SHF oscillator intermediate frequency (IF) has an absolute value >= 1 GHz. SHF instruments do not support IF frequencies in this range.
  • Functionality Removed FIRCompensation.strict. This had effect only for ZQCS users, and now it is made redundant by a more actionable error message. When waveform memory is exhausted and pulse merging occurred (due to FIR precompensation tail or overlapping pulses), the error now includes a note identifying the merged pulses and their combined size.
  • Bug Fix Fixed a bug where compilation would fail when a chunked sweep contained both the driving parameter and the derived parameter.
  • Bug Fix Fixed a bug where differences in comments produced excessively long, uncompressed SeqC.
  • Bug Fix Fixed a bug where a minor rounding error biased phase increments by up to +0.3 µrad.
  • Bug Fix Fixed a bug where explicitly setting PortMode.RF on a QA channel had no effect and the hardware used the LF path instead.
  • Bug Fix Fixed a bug where automute was not correctly applied when multiplexing output.
  • Bug Fix Fixed a bug where a compiler error occurred in experiments with near-time sweeps and a static SHFPPC configuration.
  • Bug Fix Fixed a bug where a compiler error occurred when sweeping a pulse parameter that overrides a value already defined on the pulse itself, and the pulse is used multiple times with different parameter values.
  • Deprecation Added runtime deprecation warnings for properties deprecated long ago: CompiledExperiment.src, CompiledExperiment.waves, CompiledExperiment.recipe, CompiledExperiment.wave_indices, CompiledExperiment.command_tables, CompiledExperiment.schedule. These will be removed in v26.10. As an end user, you do not need to use these properties, however for debugging or learning purposes you can still access the same information through the artifacts in the compiled experiment at your own risk (they do not come with backward compatibility promise).
  • Deprecation Previously deprecated methods CompiledExperiment.replace_pulse and CompiledExperiment.replace_phase_increment will be removed in v26.10. NOTE: the methods RuntimeContext.replace_pulse and RuntimeContext.replace_phase_increment are not deprecated and will remain available for applying replacements in NT callbacks (these methods leave the compiled experiment unchanged).
  • Deprecation Deprecated support for Python object types not supported by JSON serializer in pulse parameter values and callback functions. Users requiring wider range of types can e.g. serialize the data into bytes and pass that instead.
  • Removal Removed LabOneQInstrumentor traces: laboneq.compiler.schedule and laboneq.compiler.generate-code. Capturing compiler traces from Python now requires laboneq.instrumentation.tracing.laboneq_tracing().

Controller

  • Functionality Changed the device setup compatibility verification between compilation and execution. Experiments compiled with previous versions of LabOne Q may need recompilation.
  • Bug Fix Fixed a bug where the assignment vector calculation for multi-state discrimination on SHFQA was incorrect. The calculation is now delegated to zhinst-utils. For 2-state discrimination, this change essentially flips the state assignment. If using calculate_integration_kernels_thresholds, no change is needed. Otherwise users are recommended to update their integration kernel calculation to adapt for the new state assignment.
  • Bug Fix Fixed a bug where a timeout error could occur during experiments using pipelined execution (chunked) with large result sizes. The timeout calculation now accounts for the GW-to-FW result transfer time, which was previously unaccounted for and could cause premature timeouts on experiments with many jobs and long readout blocks.
  • Bug Fix Fixed a bug where "zi:fw:19" execution errors occurred with (auto-)chunking on HDAWG.
  • Bug Fix Fixed a bug where outputs on different AWG cores of a single HDAWG were not synchronized (e.g. channels 1 and 3 out of sync).
  • Removal Removed device setup hot-reloading.

Automation

  • Functionality Added error tracking and visualization for failed layer executions. The exceptions from run_layer_executable are recorded via a new AutomationStatus.ERROR status and error attribute, with errored nodes blinking yellow-to-red in the web viewer and displaying the error message in the info panel on click.
  • Functionality Multiple automation web viewers can now run simultaneously. Each start_web_viewer call launches an independent server on its own port for a separate Automation instance.
  • Functionality Improved the "Node results" image discovery for nodes with multiple quantum elements. We now search for the target quantum element UID in the results image file names if the node key string is not found.
  • Functionality Added a skip_passed argument/attribute to the AutomationLayer class that makes it possible to skip running passed nodes.
  • Functionality The automation web viewer now implements CSRF protection by rejecting state-changing requests (non-GET/HEAD) whose Origin or Referer header does not match the request host. Requests without Origin or Referrer header are rejected.
  • Functionality Improved the performance of the automation web viewer so that it runs smoothly with up to 200 quantum elements per layer. The front end has been simplified and all transitions are now entirely done natively by the browser.
  • Bug Fix Fixed a bug in the automation web viewer, where the "Node results" section of the node info panel sometimes displayed the results of the previously-clicked node.

Workflows

  • Bug Fix Fixed a bug where passing workflow OptionBuilder options directly to a task called outside a workflow context raised a ValueError.

Serializer

  • Functionality Updated the Experiment serializer to support a richer set of values as pulse parameters.

    Previously the Experiment serializer supported only a limited basic set of pulse parameter types:

    • float, int, str, bool, complex
    • SweepParameter, LinearSweepParameter
    • list[SweepParameter], list[LinearSweepParameter]

    This set of types proved too restrictive for some use cases.

    Now the Experiment serializer supports an extended set of types for pulse parameters:

    • int, float, complex, str, bytes, bool, None, SweepParameter or LinearSweepParameter
    • lists of the above
    • dictionaries of the above with str keys

    The lists and dictionaries may be nested and need not have homogeneous element types.

    The previous Experiment serializer format was version 4. The new format is version 5.

  • Bug Fix Fixed a bug where deserialization of compiled experiments that use an SHFPCC device with null amplifier pump parameters would fail.

  • Bug Fix Fixed a bug where attempting to serialize an experiment containing reset_oscillator_phase would raise an error. ResetOscillatorPhase operations are now correctly serialized and deserialized.
  • Bug Fix Fixed a bug where a single-shot result of the form np.array(X + jY) was deserialized as np.array([X + jY]).
  • Bug Fix Fixed a bug where an experiment using SHFPPC failed to execute after a JSON serialization round trip.

Applications Library

  • Functionality Added the following experiment and analysis workflows to contrib, useful for two-qubit tune-up: single-qubit phase correction for parametric CZ calibration (para_cz_corr_sq_phases_tc), parametric CZ flux frequency vs amplitude calibration (para_cz_flux_freq_vs_amp_tc), parametric CZ flux frequency vs duration calibration (para_cz_flux_freq_vs_dur_tc), parametric CZ pulse-duration calibration (para_cz_flux_pulse_dur_tc), parametric CZ frequency vs RZ phase (para_cz_freq_vs_phase), two-qubit randomized benchmarking (two_qubit_rb). To achieve this, we added the necessary parameters (CzParameters), operations (TunableCouplerOperations with cz method), and pulses (modulated_flux) for the tunable coupler.
  • Breaking change: Changed the name of the ZZ coupling strength experiment workflow from zz_coupling_strength_exp to zz_coupling_strength.
  • Functionality Added the bosonic qubit type, quantum operations, and demo platform, along with a selection of experiments, including: displacement calibration, memory spectroscopy, selective transmon Rx calibration, SNAP gate calibration, SWAP gate calibration, and Wigner tomography.

  • Functionality Updated the VQE example to use QPU, QuantumOperations, and OpenQASMTranspiler.

    Previously the VQE example used GateStore and exp_from_qasm_list, which are deprecated interfaces to the LabOne Q OpenQASMTranspiler. The GateStore is replaced with a QPU and a QuantumOperations class. exp_from_qasm_list is replaced by calling OpenQASMTranspiler.batch_experiment directly instead.

  • Bug Fix The behavior of numpy.linalg.eig changed in version 2.5.0 of NumPy (https://numpy.org/doc/stable/release/2.5.0-notes.html#linalg-eig-and-linalg-eigvals-now-always-return-complex-arrays). The code was updated to handle the change.

  • Removal Removed support for qubit/qubits/parametric_amplifier arguments of type QuantumElement/QuantumElements/TWPA in experiment workflows. Removed support for quantum_elements arguments of type QuantumElements in the temporary_quantum_elements_from_qpu task. Please pass the quantum element UIDs instead of the quantum element instances.
  • Removal Removed the deprecated update_qubits task (use update_qpu instead) and the deprecated temporary_modify task (use temporary_qpu instead).

Known Issues

  • Running Gen1 experiments can produce controller warnings indicating RT start conditions on follower devices are not fulfilled (e.g., UHFQA:dev2801: AWG 0 didn't start after 5s); experiments may still execute correctly, but affected Gen1 experiments may take ~20%+ longer due to the additional wait/retry behavior. We are working on a fix and will release it as a patch to 26.1.0 as soon as it is available.
  • Using the reset_signal_oscillator_phase() on signals of type rf_signal is currently not supported.
  • Using OpenQASMTranspiler.batch_experiment with QASM programs that contain native measurement operations will lead to an unexpected shape of the returned data. To ensure the correct shape, measurement operations should be removed from the OpenQASM program, and .batch_experiment should be called with the option field add_measurement=True, which will add the measurement operations to the LabOne Q Experiment during the import step (see our tutorial for more details).
  • Using the internal scope to acquire raw traces on multiple channels of an SHFQA in a single experiment is only possible if the timing of all acquisitions is equal between instrument channels.
  • Using runtime checks of the sequencer playback through the disable_runtime_checks=False argument of session.connect(), is currently not possible when the experiment contains real-time feedback or is using the on-device PRNG. In the latter case, unintended error messages may be produced if the option is used.
  • When using the pipeliner in an experiment by specifying a chunk_count parameter in a sweep, the number of acquire commands in each chunk currently needs to be equal. Typically, this means that the number of sweep steps within each chunk has to be the same.
  • When using OutputSimulator or pulse sheet viewer with an experiment using the pipeliner or near-time sweeping, currently only the first sequence step will be displayed.
  • When delaying logical signal lines of type rf_signal via the delay_signal calibration property, all rf_signals on the same sequencer core must be set to the same delay.
  • When delaying logical signal lines on the SHFQA via the delay_signal calibration property, the delays for the measure and acquire line must be the same; the measure pulse delay is not added to the acquire pulse delay as on the UHFQA. We recommend to use port_delay for now.
  • When creating a section with very short content (below the device's minimum waveform length), the compiler may fail to map the experiment to valid SeqC, and will generate an error. As a workaround in these cases, manually add delays to the sequence.

Pre-Release versions

Previous versions