Browse documentation
Projects
Projects & collaborationHelp
TroubleshootingSpinorio Documentation
Product documentation audited against Spinorio Lab 0.11.1. Learn how the Lab, Quantum Workflow, Spinorio Compiler, IBM connection, exports, and projects work together.
Audited against Spinorio Lab 0.11.1
What Spinorio includes
Spinorio combines a JupyterLab-based research environment with automatic workflow capture, scientific inspection, hardware-aware compilation, and project collaboration.
| Area | Current role |
|---|---|
| Spinorio Lab | JupyterLab workspace with quantum SDKs and Spinorio integrations. |
| Quantum Workflow | Global inventory and inspectors for captured circuits, transpilations, jobs, results, provenance, and project views. |
| Spinorio Compiler | Hardware-targeted compilation with manual target selection, recorded outputs, comparison, history, and a notebook Python SDK. |
| Projects | Shared grouping/access layer for selected workflow records and source snapshots, with roles and branches. |
Start here
Getting Started
Run a first Qiskit example and locate the captured work in Spinorio.
Quantum Workflow
Understand the global Jobs, Circuits, and Transpilations workspace.
Spinorio Compiler
Compile a preserved circuit for a manually selected hardware target.
Connect IBM Quantum
Enable Spinorio server-side IBM job synchronization and live compiler target discovery.
Projects & collaboration
Share selected experiment records and preserved source versions with controlled access.
Python SDK
Use the compiler from an authenticated Spinorio Lab notebook.
Important product boundaries
- Automatic workflow tracking is implemented around supported Qiskit-family activity. Other quantum SDKs can be installed in the Lab without implying the same automatic capture coverage.
- Spinorio Compiler compiles for the selected target; selecting a QPU does not submit a physical quantum-hardware job.
- The IBM credential stored under Provider Connections remains server-side. Spinorio does not pass that credential into notebook code, so it is not a replacement for notebook-side Qiskit Runtime authentication.
- Project access does not grant another member access to the owner’s provider credentials.
- Circuit and transpilation comparisons are structural analyses. They do not by themselves prove functional equivalence.
- Project branches preserve separate experiment histories. Experiment/source merging and simultaneous collaborative editing are not implemented.