Skip to content

Why QruiseOS?

QruiseOS provides a single unified solution for developers of quantum computing hardware to easily manage testing, operation, and maintenance of their devices. It's meant for both R&D labs (in academia or industry) performing deep characterisation of their next-generation devices, as well as for service providers undertaking autonomous calibration of their cloud-hosted QPUs.

QruiseOS helps developers and users increase their productivity and extract maximum utility from their QPUs by offering automated access to:

  • relevant information for running experiments and workflows
  • a platform that can be reliably built upon (automatic bring-up, monitoring, etc.)

More precisely, QruiseOS is a managed backend (database/storage/orchestration) meant to provide consolidated and traceable data, offering QPU users hassle-free and shared access to:

  • QPU configuration
  • experiment/workflow definitions
  • raw outputs from experiment and workflow execution
  • analysis output that contributes to the knowledge about QPU
  • monitoring dashboards for workflows, QPU state, and past experiments

Tip

The key technical terms used in QruiseOS and its documentation are described in the Technical glossary.

Transitioning from measurements to tasks

QruiseOS fills the gap between a measurement and a task. Let us briefly explain why we make a clear distinction between these two concepts.

A measurement defines the code to run on a QPU, while a task consists of a notebook carrying out the measurement and data persistence. In other words, the task notebook holds the logic of setting QPU and measurement configuration, running the measurement, carrying out the analysis of the measurement, and persisting the measurement and analysis data (see tutorial 01_overview_single_measurement). Crucially, a task provides the relevant context and specifies what to do with the new data.

This distinction clarifies that they are two well-separated codebases:

  1. The measurement code itself, which:

  2. provides the definition of actual commands/circuits sent to the QPU

  3. is QPU specific

  4. is the responsibility of the user

  5. The backend code and assets, which:

  6. are Qruise's responsibility

  7. enable access to the (latest) analysis output and QPU configuration
  8. enable persistence of the data from measurements and analysis

The concept of tasks integrates these two elements into a user-friendly experience, with Qruise providing an architecture and templates to swiftly go from user-defined measurements to tasks. Tasks encapsulate all the needed context beyond the mere measurement and can then be orchestrated into workflows.

As we have just seen, transitioning from measurements to tasks is absolutely necessary to enable a mature QPU user platform. This is what QruiseOS provides.