SpinorioSpinorio
Documentation
Open Lab
Browse documentation

Docs / Spinorio Compiler / Compiler overview

Spinorio Compiler

Compile preserved Qiskit circuits for a manually selected hardware target, inspect source-to-compiled metrics, compare with a standard baseline, and reuse the compiled QPY output.


Compile tab

  1. 1
    Choose a source circuit

    The selector uses preserved circuit versions with saved QPY artifacts and shows notebook/cell provenance when available.

  2. 2
    Choose hardware manually

    Select a live IBM QPU, saved hardware configuration, or offline reference target. Live IBM targets require a connected provider account and explicit service-instance selection.

  3. 3
    Choose optimization

    The UI currently exposes Level 1 (Light), Level 2 (Balanced), and Level 3 (Intensive).

  4. 4
    Choose an optional project destination

    A compilation can remain in the personal workflow or be attached to one of your writable project branches.

  5. 5
    Compile Circuit

    The UI reports Submitting, Queued, Running, Completed, or Failed and prevents duplicate queued/running submissions for the same configuration.

Hardware targets

Target sourceMeaning
Live IBM Quantum QPUsCurrent device/configuration information discovered for the explicitly selected connected IBM service instance.
Saved hardware configurationsRecorded provider snapshots retained as compilation targets; they are not guaranteed to represent live current state.
Reference targets (offline)Built-in topology/configuration targets that do not require live IBM discovery.
Compilation is not execution

Choosing an IBM QPU here supplies a hardware target to the compiler. Spinorio Compiler does not submit a physical QPU job as part of compilation.

Compilation result

  • Source → compiled measurements include depth, total gates, two-qubit gates, two-qubit depth, and SWAP gates.
  • Compilation duration is recorded when the job completes.
  • Technical provenance can expose the internal engine identifier, Qiskit version, IBM transpiler version, and target ID.
  • A completed compiled circuit can be inserted back into the active notebook.
  • Compilation can be added to a project when the user has a writable branch.
Current optimization boundary

Calibration-based fidelity optimization is not available in this release.

Compare and History tabs

Compare can run a standard compilation baseline for the same source circuit, target, and optimization level, then display the same structural metrics side by side. Expected fidelity is not estimated by this comparison, and the measurements are not an equivalence proof.

History lists recorded compiler jobs with method, target, status, compiled depth, and creation time. Selecting an entry returns to its result in the Compile tab.

Python SDK


Previous

← Projects & collaboration

Next

Python SDK →