Backends¶
The divi.backends module provides interfaces for running quantum circuits on
different backends, from local simulators to cloud-based quantum hardware.
All backends implement the CircuitRunner interface,
providing a consistent API for circuit execution. This abstraction allows
switching between different execution environments without changing quantum
program code.
All submit_circuits() methods return an
ExecutionResult object, which provides a unified
interface for handling both synchronous and asynchronous backend responses.
Functions¶
|
One-call QUBO/HUBO characterization with rich notebook display. |
|
Convert raw counts to probability distributions. |
|
Create a populated GenericBackendV2 from a BackendProperties dictionary. |
|
Re-fetch a previous characterization result by job ID. |
|
Reverse endianness of all bitstrings in a dictionary of probability distributions. |
Classes¶
|
Backend that runs circuits as an asynchronous remote job. |
|
Configuration for |
|
Result container for QUBO/HUBO characterization. |
|
A generic interface for anything that can "run" quantum circuits. |
|
Execution configuration for a Qoro Service job. |
|
Result container for circuit execution. |
|
Configuration for a Qoro Service job. |
Status of a job on the Qoro Service. |
|
|
Type of job to execute on the Qoro Service. |
|
Configuration object for |
|
A CircuitRunner backend powered by qoro-maestro, Qoro's C++ quantum simulator. |
|
Represents a single Quantum Processing Unit (QPU). |
|
Represents a collection of QPUs that form a quantum computing system. |
|
A parallel wrapper around Qiskit's AerSimulator using Qiskit's built-in parallelism. |
|
A client for interacting with the Qoro Quantum Service API. |
Simulation method for execution configuration. |
|
Simulator backend type for execution configuration. |
|
|
Represents a simulator cluster for cloud-based quantum simulation. |
|
Capability protocol for backends that resolve parametric QASM templates server-side. |