Transpilations

Inspect captured transpilation input/output states, structural changes, validation, layout, compiler plan, QPU mapping, and hardware evidence.

What Spinorio captures

The current sensor recognizes supported Qiskit transpilation boundaries including qiskit.transpile(), preset pass-manager creation, and PassManager.run(). It records the observed transpilation context and links exact input/final output circuit versions when that evidence is available.

Intermediate passes are not automatically captured

Spinorio records the exact observed input and final output around supported transpilation boundaries. It does not inject callbacks or capture every intermediate pass state.

Outcome and circuit transformation

Outcome cards summarize depth, two-qubit gates, total gates, and two-qubit depth changes.
The Circuit transformation viewer switches between the captured Input and Transpiled states.
Source actions can navigate to the input circuit source cell and the recorded transpilation cell when provenance is available.
Gate-composition and full metric tables retain input, output, delta, and relative-change evidence.

Compilation and hardware evidence

Circuit Structure Profile compares input and output using the same normalization rule.
Compilation Quality can appear when required calibration and structural evidence is available. Calibration-derived success/fidelity values are estimates, not measured algorithm accuracy.
Compiled QPU mapping overlays observed compiled-circuit usage on provider geometry when exact geometry is available; otherwise the UI labels a connectivity-derived schematic.
The inspector can expose compiler-plan observations, interface validation, layout evidence, operation changes, and estimated execution timeline when those data were captured.

Do not interpret structural improvement as correctness

Lower depth or fewer gates can be useful, but these metrics alone do not establish that input and output circuits are functionally equivalent.

← Circuits

Jobs & results →