qalgora-Q Docs Hub量子文档 ✦ Ask AI✦ 问问文档

Quantum Hardware Providers

◐ Design-level API
This page documents qalgora-Q API design, architecture, or adaptation workflows. Code examples illustrate intended usage and are not guaranteed to run in the current reference implementation.

The open reference build is local CPU NumPy simulation only; the cloud/QPU material describes adaptation/export/future workflows and does not provide native submission to real QPUs. The specification API plans to make the same kernel easier to export/adapt to many vendors' workflows; the open reference build will not natively submit to physical QPUs.

Vendor workflow adaptation (illustrative — not a reference-build capability)

import qalgora
# Planned vendor adapter — not in the open reference build (illustrative only):
# qalgora.set_target("ionq", machine="aria-1")
# job = qalgora.sample_async(bell, shots_count=1000)   # queued remotely
# counts = job.get()
Reference build runs locally — not real hardware
This example targets a remote cloud/QPU, but the open reference build does not submit to a real machine — it warns and falls back to the local CPU statevector simulator, returning simulated results. Submitting to an actual device (e.g. 天衍/TianYan, IBM, IonQ, Origin) requires the vendor’s own SDK and credentials.

Ecosystem provider examples

Listed only as ecosystem/adaptation-target examples — this does not imply completed integration, certification, or the ability to submit jobs.

ModalityProviders
Ion trapIonQ, Quantinuum
SuperconductingIQM, OQC, Quantum Circuits Inc.*, Anyon Systems
Neutral atomInfleqtion, Pasqal, QuEra
PhotonicORCA Computing
Cloud brokersAmazon Braket, Scaleway, qBraid

* Quantum Circuits Inc. status may change.

Beyond QPUs, quantum control systems (e.g. Quantum Machines OPX) connect through the real-time stack rather than as a sampling target: within the coherence window qalgora-Q issues pulses and reads measurements for feedback and error-correction loops.

Credentials
Real submission would use each vendor's own SDK and credentials (e.g. QALGORA_IONQ_API_KEY); the open reference build does not submit on your behalf.

量子硬件服务商

◐ 设计接口
本页描述的是 qalgora-Q 的接口设计、架构设计或适配工作流。相关代码用于说明预期用法,当前参考实现不保证可以直接运行。

开放参考实现仅本地 CPU NumPy 模拟;云端/QPU 描述的是适配/导出/未来工作流,不提供原生真实 QPU 提交。规范接口计划让同一内核更易导出/适配到多家厂商工作流;开放参考实现不会原生提交到物理 QPU。

厂商工作流适配示意(非开放参考实现能力)

import qalgora
# 规划中的厂商适配器,开放参考实现暂未包含(仅作示意):
# qalgora.set_target("ionq", machine="aria-1")
# job = qalgora.sample_async(bell, shots_count=1000)   # 在远端排队执行
# counts = job.get()
参考实现仅本地运行 · 非真机
此示例虽指向远程云端/QPU,但开放参考实现不会真正提交到真机 —— 它会给出告警并回退到本地 CPU 态矢量模拟器,返回模拟结果,不会真正提交到天衍等真机。真正提交真机需使用对应厂商的 SDK 与凭证。

生态服务商示例

仅作生态/适配对象示例,不代表已完成接入/认证/可提交。

技术路线服务商
离子阱IonQ, Quantinuum
超导IQM, OQC, Quantum Circuits Inc.*, Anyon Systems
中性原子Infleqtion, Pasqal, QuEra
光子ORCA Computing
云代理Amazon Braket, Scaleway, qBraid

* Quantum Circuits Inc. 状态可能变动。

除 QPU 外,量子控制系统(如 Quantum Machines OPX)走实时栈接入,而非作为采样目标:qalgora-Q 在相干时间窗内下发脉冲、读取测量,用于反馈与纠错回路。

凭据
真正提交真机需使用各厂商自己的 SDK 与凭据(如 QALGORA_IONQ_API_KEY);开放参考实现不会代你提交。