Skip to content

Low-level APIs

The low-level API section is for developers who need module-level control beneath Experiment. It is organized around three modules: measurement, system, and backend.

Most Qubex users should start with Experiment on real hardware or QuantumSimulator for offline work. Come here when measurement execution flows, system models, or backend controllers are the primary abstraction.

Module map

Module Responsibility Start here when
measurement Sessions, schedules, capture/readout, sweeps, and result conversion You want to build or run measurement-centric execution flows
system Configuration loading, in-memory system models, and software/hardware synchronization You want to inspect one system definition or coordinate runtime state
backend Backend controller contracts and QuEL-specific implementations You want to work with controller-level execution or backend-specific payloads

How the modules fit together

  1. system loads configuration files and assembles the software-side ExperimentSystem.
  2. measurement builds MeasurementSchedule objects, capture/readout, and sweep flows on top of that state.
  3. backend controllers execute the prepared requests on concrete QuEL runtimes.

Choose Experiment instead when

  • You want the recommended user-facing workflow for most hardware-backed experiments
  • You want built-in characterization, calibration, and benchmarking routines
  • You prefer one facade for setup, execution, and analysis