Skip to content

measurement module

qubex.measurement is the module that assembles hardware-backed execution flows from the models exposed by the measurement layer. It sits between system and backend: it consumes loaded system state and turns schedules into capture/readout and sweep execution flows.

This page sits under Low-level APIs.

Use measurement when

  • You want to work directly with MeasurementSchedule, capture/readout, sweeps, and measurement results
  • You want to work with Measurement, MeasurementSchedule, or sweep executors directly
  • You want backend-neutral execution flows before dropping to backend-specific controllers

Key objects

  • Measurement: facade for the overall measurement execution flow
  • MeasurementSchedule, MeasurementResult, and sweep result models: canonical contracts in the measurement module
  • Builders and executors: MeasurementScheduleBuilder, SweepMeasurementBuilder, and SweepMeasurementExecutor
  • Services and adapters: execution/classification services plus MeasurementBackendAdapter implementations

Relationship to the other modules

  • system: provides ConfigLoader, ExperimentSystem, targets, and parameter state that Measurement depends on
  • backend: provides the controller contracts and concrete QuEL-1/QuEL-3 runtimes that measurement adapters target
  1. Read the section overview: Low-level APIs
  2. Learn the shared pulse-sequence model if needed: Build pulse sequences with PulseSchedule
  3. Start with curated notebooks: measurement example workflows
  4. Move to system when configuration or synchronization is the main issue
  5. Move to backend when controller-level payloads or execution paths are the main issue

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 without centering measurement-module vocabulary

See Experiment for that path.