uniqc.backend_adapter.task.adapters.ibm_adapter module¶
IBM Quantum backend adapter using QiskitRuntimeService.
Uses QiskitRuntimeService from qiskit-ibm-runtime to list backends
and submit/query tasks. This is the recommended IBM approach as of 2024+,
superseding the raw REST API which is blocked by Cloudflare on quantum.ibm.com.
- QiskitRuntimeService reference:
- class uniqc.backend_adapter.task.adapters.ibm_adapter.IBMAdapter(proxy=None)[source]¶
Bases:
QuantumAdapterDeprecated: delegates to QiskitAdapter.
Deprecated since version IBMAdapter: is deprecated. Use
QiskitAdapterinstead, which usesqiskit-ibm-runtimefor task submission.This class is kept for backwards compatibility and delegates all operations to an internal QiskitAdapter instance.
- get_chip_characterization(backend_name)[source]¶
Return per-qubit and per-pair calibration data for an IBM backend.
Delegates to
QiskitAdapter.- Parameters:
backend_name (str) – IBM backend name, e.g.
"ibm_brisbane".- Return type:
ChipCharacterization or None
- is_available()[source]¶
Return True if the required packages / credentials are configured.
Defaults to
Falseso that subclasses must explicitly opt-in, avoiding the risk of an unconfigured adapter incorrectly reporting availability.- Return type:
- query(taskid)[source]¶
Query a single task’s status and result.
- Parameters:
taskid (str) – Task identifier.
- Returns:
status:'success'|'failed'|'running'result: execution result (present when status is'success'or'failed')
- Return type:
dict with keys
- query_batch(taskids)[source]¶
Query multiple tasks’ status and merge results.
Overall status is the worst case:
'failed'>'running'>'success'.
- submit(circuit, *, shots=1000, **kwargs)[source]¶
Submit a circuit to the backend and return a task ID.