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

Amazon Braket

◐ 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.

Amazon Braket is a managed service that brokers access to QPUs from several vendors under one AWS account. qalgora-Q documents an intended export workflow to Braket devices through the Braket SDK, addressed by ARN-style name; the open reference build does not submit directly.

Devices on Braket

VendorDeviceQubitsModalityRegion
IonQForte-1 / Forte-Enterprise-136 #AQTrapped ionus-east-1
IQMGarnet / Emerald20 / 54Superconductingeu-north-1
RigettiAnkaa-3 / Cepheus-1-108Q84 / 108Superconductingus-west-1
QuEraAquila256Neutral atom (analog)us-east-1
AQTIBEX-Q1Trapped ioneu-north-1

The device lineup shifts over time — OQC, Xanadu, and D-Wave have left; AQT IBEX-Q1 (a new ion-trap vendor) and Rigetti Cepheus-1-108Q are recent additions. For the current roster see the Amazon Braket supported devices page.

Credentials & submitting

Authenticate with standard AWS credentials (aws configure or an IAM role). Each device has an ARN; results land in an S3 bucket. Jobs queue — use the async API.

import qalgora
# Planned Braket submission — requires the Braket SDK + AWS credentials (aws configure / IAM role).
# The open reference build does not submit directly; lines below are illustrative.
# bell is a predefined example kernel; the device ARN includes its region.
# qalgora.set_target("braket",
#                    machine="arn:aws:braket:us-east-1::device/qpu/ionq/Forte-1",
#                    region="us-east-1")
# job = qalgora.sample_async(bell, shots_count=1000)
# print(job.status())
# print(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.

Regions, cost & simulators

ItemDetail
RegionsDevices are pinned (e.g. IQM/AQT in eu-north-1, IonQ/QuEra in us-east-1, Rigetti in us-west-1)
PricingA per-task fee plus a per-shot fee that vary by device — see Amazon Braket Pricing for current rates
On-demand simulatorsSV1 (statevector), DM1 (density matrix)
Program setsBundle up to 100 circuits (or a parametric sweep) in one task — 3×–24× faster on Rigetti / IQM
Braket DirectReserve a device by the hour, plus expert advice and experimental capabilities

Validate locally on qalgora-Q's runnable qpp-cpu reference target (or a managed Braket simulator) before paying for hardware shots.

Hybrid Jobs

Braket Hybrid Jobs run a classical-quantum loop next to the QPU. The same structure runs locally in qalgora-Q — iterate on the reference simulator, then (planned) submit the converged run to a Braket device.

qalgora.set_target("qpp-cpu")                              # develop locally (runnable reference target)
energy, params = qalgora.vqe(ansatz, hamiltonian, optimizer, parameter_count=n)
# Planned hardware submission (requires the Braket SDK + AWS credentials):
# qalgora.set_target("braket", machine="arn:aws:braket:eu-north-1::device/qpu/iqm/Garnet")
# final = qalgora.observe(ansatz, hamiltonian, params)     # validate on hardware
Specification API — not in the open reference build yet
This example shows a qalgora-Q specification API (or a third-party library) that the open reference build does not bundle today. It documents the intended interface; to run code now, use the reference build’s supported core API.
Multi-vendor under one account
Braket is the single account that reaches IonQ, IQM, Rigetti, QuEra, and AQT — see the Braket SDK interop page to bring existing Braket circuits in.
AWS's own hardware & roadmap
AWS's Ocelot cat-qubit chip (Feb 2025) is an error-correction research prototype — not yet a Braket device. Looking ahead, AWS and QuEra are building Libra, a fault-tolerant machine of hundreds of logical qubits, targeted by 2028.

References

Amazon Braket

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

Amazon Braket 是一项托管服务,在统一的 AWS 账户下代理访问多家厂商的 QPU。qalgora-Q 记录的是经 Braket SDK 的预期导出工作流,按 ARN 风格的名称寻址;开放参考实现不会直接提交。

Braket 上的设备

厂商设备量子比特数技术路线区域
IonQForte-1 / Forte-Enterprise-136 #AQ离子阱us-east-1
IQMGarnet / Emerald20 / 54超导eu-north-1
RigettiAnkaa-3 / Cepheus-1-108Q84 / 108超导us-west-1
QuEraAquila256中性原子(模拟式)us-east-1
AQTIBEX-Q1离子阱eu-north-1

设备阵容会随时间变化——OQC、Xanadu、D-Wave 已退出;AQT IBEX-Q1(新晋离子阱厂商)与 Rigetti Cepheus-1-108Q 是较新加入的设备。当前清单以 Amazon Braket supported devices 页面为准。

凭据与任务提交

使用标准 AWS 凭据(aws configure 或 IAM 角色)进行身份验证。每台设备都有对应的 ARN;结果存储在 S3 存储桶中。任务需要排队——请使用异步 API。

import qalgora
# 规划中的 Braket 提交——需要 Braket SDK + AWS 凭据(aws configure / IAM 角色)。
# 开放参考实现不会直接提交;以下为示意代码。
# bell 是预定义的示例内核;设备 ARN 含所在区域。
# qalgora.set_target("braket",
#                    machine="arn:aws:braket:us-east-1::device/qpu/ionq/Forte-1",
#                    region="us-east-1")
# job = qalgora.sample_async(bell, shots_count=1000)
# print(job.status())
# print(job.get())
参考实现仅本地运行 · 非真机
此示例虽指向远程云端/QPU,但开放参考实现不会真正提交到真机 —— 它会给出告警并回退到本地 CPU 态矢量模拟器,返回模拟结果,不会真正提交到天衍等真机。真正提交真机需使用对应厂商的 SDK 与凭证。

区域、费用与模拟器

项目详情
区域设备绑定特定区域(如 IQM/AQT 位于 eu-north-1,IonQ/QuEra 位于 us-east-1,Rigetti 位于 us-west-1
定价每任务费 + 按次采样费,因设备而异——当前价格以 Amazon Braket Pricing 为准
按需模拟器SV1(态矢量)、DM1(密度矩阵)
Program sets将最多 100 条电路(或一组参数扫描)打包为单个任务——在 Rigetti / IQM 上提速 3×–24×
Braket Direct可按小时预约设备,并获得专家咨询与实验性能力

在付费使用真实硬件之前,请先在 qalgora-Q 可运行的 qpp-cpu 参考目标后端(或 Braket 托管模拟器)上完成验证。

Hybrid Jobs

Braket Hybrid Jobs 在 QPU 旁运行经典-量子混合循环。qalgora-Q 本地也支持相同的结构——先在参考模拟器上迭代,再(规划中)将收敛后的任务提交到 Braket 设备。

qalgora.set_target("qpp-cpu")                              # 本地开发(可运行的参考目标后端)
energy, params = qalgora.vqe(ansatz, hamiltonian, optimizer, parameter_count=n)
# 规划中的硬件提交(需要 Braket SDK + AWS 凭据):
# qalgora.set_target("braket", machine="arn:aws:braket:eu-north-1::device/qpu/iqm/Garnet")
# final = qalgora.observe(ansatz, hamiltonian, params)     # validate on hardware
规范接口 · 参考实现暂未包含
此示例展示的是 qalgora-Q 规范中的接口(或第三方库),开放参考实现目前尚未内置,仅用于说明预期用法;如需立即运行,请使用参考实现已支持的核心 API。
一个账号 多家厂商
Braket 以单一账号统一接入 IonQ、IQM、Rigetti、QuEra 和 AQT——参阅 Braket SDK 互操作页面,将现有 Braket 电路导入 qalgora-Q。
AWS 自研硬件与路线图
AWS 的 Ocelot 猫态量子比特芯片(2025 年 2 月)是纠错研究原型——尚未成为 Braket 设备。展望未来,AWS 与 QuEra 正合作打造 Libra,一台数百个逻辑比特规模的容错机,目标 2028 年。

参考文献