Research track · Quantum software
Quantum software testing & portability
Write once, validate against many backends.
Live todaySee a passport verified across backends
TodayUseful todayResearchResearch on noisy hardwareLaterFault-tolerant era
Why this horizon. Moving circuits between SDKs and backends is a day-to-day engineering need, independent of any advantage claim.
- The problem
- Code written for one SDK or backend rarely runs elsewhere without rework.
- Why quantum or hybrid methods may be relevant
- Portability reduces lock-in and makes comparisons fair.
- Classical baseline
- Manual ports between SDKs.
- What QAISS could provide
- A portable workload format and adapter certification tests.
- What evidence would count as success
- Same workload passes on multiple certified adapters with matching results.
- Limitations & open questions
- Native gate sets and compilers differ; some fidelity loss on translation is expected.
- Current status
- Planned No experiments have been published for this track yet.
Workflow on QAISS
From question to checkable result.
- STEP 1
Write the circuit once (Lab builder, OpenQASM or OriginIR).
- STEP 2
Export to the other formats and re-import.
- STEP 3
Run the same passport on several backends.
- STEP 4
Certify: identical output hashes on simulators, TVD within bounds on hardware.
Sources
Read the literature.
Cited for context. QAISS is not affiliated with the authors or publishers.
No quantum advantage, production savings, medical benefit, financial return, or security guarantee is claimed for this track.