Technical glossary¶

On this page, you can find descriptions of the key terms used in QruiseOS and the Qruise Dashboard, listed alphabetically.

A¶

Analysis¶

An analysis processes the output of a measurement, usually by fitting a function. In QruiseOS, analyses are implemented as classes.

B¶

Batch group¶

Batch groups allow you to run the same task on multiple qubits concurrently using a single notebook, speeding up your workflow.

C¶

Concurrent execution¶

Concurrent execution is when multiple tasks run partly or entirely at the same time.

The Qruise dashboard is an easy-to-use interface that organises all your QruiseOS data. The Workflows tab allows you to view all workflow runs and jump into each experiment to see its results. The Experiment Database tab stores all your past data and analyses, so you can compare results over time and across qubits.

Dependency¶

When a task is dependent on another, it cannot be executed until both the measurement and analysis of the task it depends on have been completed successfully.

E¶

Experiment context¶

When saving results to the knowledge base, it's important to keep track of how and when those results were obtained. Experiment context is created using the ExperimentContext class so that these details are saved alongside the result. This means you always know the source of any results, making it easy to trace, reproduce, and understand past experiments.

Experiment Database¶

The Experiment Database contains the results of all past experiments, organised by qubit, experiment type, date, and time. The entry for each experiment includes an interactive plot of the results, the option to download the raw data, and links to the relevant task notebook and workflow.

K¶

Knowledge base¶

The knowledge base is a comprehensive record of all your QPU data – past and present – so you can track performance trends, reproduce experiments, and maintain a single source of truth. Its role is to preserve:

QPU configuration: an explicit record of device settings required to set up and run experiments (drive and readout frequencies, control-line bandwidths, etc.)
gate definitions and calibrations: the logical operations you can perform (e.g. X\(\pi\), iSWAP, CZ, ...), together with their calibrated parameters (pulse durations, phases, etc.)
experimental results: measured values such as resonance frequencies, \(\pi\)-pulse amplitudes, decay timescales, etc.

M¶

Measurement¶

A measurement is the code required to run a "job" on a QPU; for example, an experiment. In contrast to a task, it contains only the instructions to run the job and does not include any instructions for analysis or data storage.

In QruiseOS, measurement are classes that can be configured with different settings for a given task without needing to rewrite the code. Each measurement class includes a built-in data-formatting method that organises raw data into well-structured datasets for easier processing.

Measurement backend¶

QruiseOS connects to each QPU via a measurement backend (similar to Qiskit). The backend acts as a communication link, sending jobs to the QPU and returning the results.

S¶

Schema¶

The schema defines the structure for storing and organising data in QruiseOS. It describes the key components of your device, such as qubits and resonators, how they’re connected, and how experimental results (such as coherence times or fitted parameters) should be saved.

By using a schema, QruiseOS knows how to handle, link, and validate different types of information — from device layout to calibration results — making it easier to manage and reuse data across workflows.

Subflow¶

A subflow is a group of tasks within a larger workflow. Subflows help organise your workflow and allow you to repeat a specific set of experiments until a desired condition is met; for example, achieving a target fidelity.

T¶

Task¶

A task is a notebook containing all the instructions for running a measurement, analysing the output, and storing the data in the knowledge base. Because each task is self-contained, it can be easily combined with others in a workflow. Every task executed is assigned a unique ID, allowing you to track its execution, view its results, and return or refer to it later.

W¶

Workflow¶

A workflow is an ordered sequence of tasks executed on specified qubits. Workflows can be run as many times as desired and can also be scheduled.

Workflow run¶

A workflow run is a single execution of a workflow. Each run has a unique ID, is associated with a specific workflow, and includes the tasks executed with their status and results.