Browse documentation
Projects
Projects & collaborationHelp
TroubleshootingDocs / Quantum Workflow / Jobs & results
Jobs & Results
Inspect execution status, normalized results, detailed execution metrics, timing, expansion, calibration context, provenance, and workload details.
Results
Job pages include result inspection directly. When supported provider result data is available, Spinorio normalizes bounded Sampler outcomes or Estimator values/uncertainties and presents explicit states when data is absent, unsupported, incomplete, or unavailable.
- Sampler results can expose PUB/register selection and outcome charts or tables.
- Estimator results can expose captured expectation values and standard errors where the provider payload contains supported shapes.
- Large result payloads can be bounded; the UI does not invent missing values or treat unsupported shapes as valid empty results.
Execution analysis
- Execution metrics expose definitions, formulas, values, computation methods, and limitations.
- Execution timing separates observed wall-clock timing from provider-reported QPU usage/execution timing where available.
- Execution expansion shows the relationship between logical work units, physical circuits, requested samples, and physical shot executions when those quantities exist.
- Preflight validation keeps unsupported/not-applicable checks explicit rather than forcing a pass/fail interpretation.
- Workload breakdown scales from a simple single unit to multi-unit, parameterized, Sampler, or Estimator workloads.
Calibration, hardware, and provenance
When persisted evidence supports it, the Job page can show calibration interpretation, QPU hardware context, used-subgraph exposure, captured snapshot identity, and per-qubit calibration details.
Execution provenance is presented chronologically from notebook/cell through logical circuit, transpilation, submitted circuit, job, and result. Missing historical evidence remains labeled as unavailable instead of being reconstructed from unrelated current state.
IBM remote synchronization
If Spinorio has a connected IBM provider credential and an eligible IBM job identity was captured, the control plane can continue synchronizing lifecycle information after the notebook or kernel closes.
- The Job page exposes provider status and synchronization errors when present.
- Refresh from IBM can request another provider synchronization attempt for personal records.
- Shared project records remain read-only; project members do not receive the owner’s IBM credential.
Observed error-mitigation inspection
When supported mitigation evidence is observed, Jobs can include an Error Mitigation section for captured Qiskit Runtime resilience/ZNE information or supported M3 correction evidence.
Spinorio does not run M3, ZNE, PEC, TREX, postselection, or QEC on behalf of the researcher in this release, and the analysis does not claim that mitigation improved accuracy.