qiskit-ibm-runtime 0.28.0

Description:

qiskitibmruntime 0.28.0

Qiskit Runtime IBM Client






Qiskit is an open-source SDK for working with quantum computers at the level of extended quantum circuits, operators, and primitives.
Qiskit IBM Runtime is a new environment offered by IBM Quantum that streamlines quantum computations and provides optimal
implementations of the Qiskit primitives sampler and estimator for IBM Quantum hardware. It is designed to use additional classical compute resources to execute quantum circuits with more efficiency on quantum processors, by including near-time computations such as error suppression and error mitigation. Examples of error suppression include dynamical decoupling, noise-aware compilation, error mitigation including readout mitigation, zero-noise extrapolation (ZNE), and probabilistic error cancellation (PEC).
Using the runtime service, a research team at IBM Quantum was able to achieve a 120x speedup
in their lithium hydride simulation. For more information, see the
IBM Research blog.
This module provides the interface to access the Qiskit Runtime service on IBM Quantum Platform or IBM Cloud.
Installation
You can install this package using pip:
pip install qiskit-ibm-runtime

Account setup
Qiskit Runtime service on IBM Quantum Platform
You will need your IBM Quantum API token to authenticate with the runtime service:


Create an IBM Quantum account or log in to your existing account by visiting the IBM Quantum login page.


Copy (and optionally regenerate) your API token from your
IBM Quantum account page.


Qiskit Runtime service on IBM Cloud
The runtime service is now part of the IBM Quantum Services on IBM Cloud. To use this service, you'll
need to create an IBM Cloud account and a quantum service instance.
This guide
contains step-by-step instructions, including how to find your
IBM Cloud API key and Cloud Resource Name (CRN), which you will need for authentication.
Save your account on disk
Once you have the account credentials, you can save them on disk, so you won't have to input
them each time. The credentials are saved in the $HOME/.qiskit/qiskit-ibm.json file, where $HOME is your home directory.



:warning: Account credentials are saved in plain text, so only do so if you are using a trusted device.



from qiskit_ibm_runtime import QiskitRuntimeService

# Save an IBM Cloud account.
QiskitRuntimeService.save_account(channel="ibm_cloud", token="MY_IBM_CLOUD_API_KEY", instance="MY_IBM_CLOUD_CRN")

# Save an IBM Quantum account.
QiskitRuntimeService.save_account(channel="ibm_quantum", token="MY_IBM_QUANTUM_TOKEN")

Once the account is saved on disk, you can instantiate the service without any arguments:
from qiskit_ibm_runtime import QiskitRuntimeService
service = QiskitRuntimeService()

Loading account from environment variables
Alternatively, the service can discover credentials from environment variables:
export QISKIT_IBM_TOKEN="MY_IBM_CLOUD_API_KEY"
export QISKIT_IBM_INSTANCE="MY_IBM_CLOUD_CRN"
export QISKIT_IBM_CHANNEL="ibm_cloud"

Then instantiate the service without any arguments:
from qiskit_ibm_runtime import QiskitRuntimeService
service = QiskitRuntimeService()

Enabling account for current Python session
As another alternative, you can also enable an account just for the current session by instantiating the
service with your credentials.
from qiskit_ibm_runtime import QiskitRuntimeService

# For an IBM Cloud account.
ibm_cloud_service = QiskitRuntimeService(channel="ibm_cloud", token="MY_IBM_CLOUD_API_KEY", instance="MY_IBM_CLOUD_CRN")

# For an IBM Quantum account.
ibm_quantum_service = QiskitRuntimeService(channel="ibm_quantum", token="MY_IBM_QUANTUM_TOKEN")

Primitives
All quantum applications and algorithms level are fundamentally built using these steps:

Map classical inputs to a quantum problem
Translate problem for optimized quantum execution.
Execute the quantum circuits by using a primitive (Estimator or Sampler).
Post-process, return result in classical format.

Primitives are base-level functions that serve as building blocks for many quantum algorithms and applications.
Primitives accept vectorized inputs, where single circuits can be grouped with array-valued specifications. That is, one circuit can be executed for arrays of n parameter sets, n observables, or both (in the case of the estimator). Each group is called a Primitive Unified Bloc (PUB), and can be represented as a tuple.
The primitive interfaces are defined in Qiskit.
The IBM Runtime service offers these primitives with additional features, such as built-in error suppression and mitigation.
There are several different options you can specify when calling the primitives. See Primitive options for more information.
Primitive versions
Version 2 of the primitives is introduced by qiskit-ibm-runtime release 0.21.0. Version 1 of the primitives is no longer supported. Refer to Migrate to the V2 primitives on how to migratie to V2 primitives. The examples below all use V2 primitives.
Sampler
This primitive takes a list of user circuits (including measurements) as input and returns the sampling output. The type of the output is defined by the program (typically bit-arrays), and the output data is separated by the classical register names.
To invoke the Sampler primitive
from qiskit import QuantumCircuit
from qiskit.transpiler.preset_passmanagers import generate_preset_pass_manager
from qiskit_ibm_runtime import QiskitRuntimeService, SamplerV2 as Sampler

service = QiskitRuntimeService()

# 1. A quantum circuit for preparing the quantum state (|00> + |11>)/rt{2}
bell = QuantumCircuit(2)
bell.h(0)
bell.cx(0, 1)
bell.measure_all()

# 2: Optimize problem for quantum execution.
backend = service.least_busy(operational=True, simulator=False)
pm = generate_preset_pass_manager(backend=backend, optimization_level=1)
isa_circuit = pm.run(bell)

# 3. Execute using the Sampler primitive
sampler = Sampler(backend=backend)
sampler.options.default_shots = 1024 # Options can be set using auto-complete.
job = sampler.run([isa_circuit])
print(f"Job ID is {job.job_id()}")
pub_result = job.result()[0]
print(f"Counts for the meas output register: {pub_result.data.meas.get_counts()}")

Estimator
This primitive takes circuits and observables as input, to evaluate expectation values and standard error for a given parameter input. This Estimator allows users to efficiently calculate and interpret expectation values of quantum operators required for many algorithms.
To invoke the Estimator primitive:
from qiskit_ibm_runtime import QiskitRuntimeService, EstimatorV2 as Estimator
from qiskit.quantum_info import SparsePauliOp
from qiskit import QuantumCircuit
from qiskit.circuit import Parameter
import numpy as np

service = QiskitRuntimeService()

# 1. A quantum circuit for preparing the quantum state (|000> + e^{itheta} |111>)/rt{2}
theta = Parameter('θ')
circuit = QuantumCircuit(3)
circuit.h(0) # generate superposition
circuit.p(theta, 0) # add quantum phase
circuit.cx(0, 1) # condition 1st qubit on 0th qubit
circuit.cx(0, 2) # condition 2nd qubit on 0th qubit

# The observable to be measured
M1 = SparsePauliOp.from_list([("XXY", 1), ("XYX", 1), ("YXX", 1), ("YYY", -1)])

# batch of theta parameters to be executed
points = 50
theta1 = []
for x in range(points):
theta = [x*2.0*np.pi/50]
theta1.append(theta)

# 2: Optimize problem for quantum execution.
backend = service.least_busy(operational=True, simulator=False)
pm = generate_preset_pass_manager(backend=backend, optimization_level=1)
isa_circuit = pm.run(circuit)
isa_observables = M1.apply_layout(isa_circuit.layout)

# 3. Execute using the Estimator primitive
estimator = Estimator(backend)
estimator.options.resilience_level = 1 # Options can be set using auto-complete.
job = estimator.run([(isa_circuit, isa_observables, theta1)])
print(f"Job ID is {job.job_id()}")
pub_result = job.result()[0]
print(f"Expectation values: {pub_result.data.evs}")

This code batches together 50 parameters to be executed in a single job. If a user wanted to find the theta that optimized the observable, they could plot and observe it occurs at theta=np.pi/2. For speed we recommend batching results together (note that depending on your access, there may be limits on the number of circuits, objects, and parameters that you can send).
Session
In many algorithms and applications, an Estimator needs to be called iteratively without incurring queuing delays on each iteration. To solve this, the IBM Runtime service provides a Session. A session starts when the first job within the session is started, and subsequent jobs within the session are prioritized by the scheduler.
You can use the qiskit_ibm_runtime.Session class to start a
session. Consider the same example above and try to find the optimal theta. The following example uses the golden search method to iteratively find the optimal theta that maximizes the observable.
To invoke the Estimator primitive within a session:
from qiskit_ibm_runtime import QiskitRuntimeService, Session, EstimatorV2 as Estimator
from qiskit.quantum_info import SparsePauliOp
from qiskit import QuantumCircuit
from qiskit.circuit import Parameter
import numpy as np

service = QiskitRuntimeService()

# 1. A quantum circuit for preparing the quantum state (|000> + e^{itheta} |111>)/rt{2}
theta = Parameter('θ')
circuit = QuantumCircuit(3)
circuit.h(0) # generate superpostion
circuit.p(theta,0) # add quantum phase
circuit.cx(0, 1) # condition 1st qubit on 0th qubit
circuit.cx(0, 2) # condition 2nd qubit on 0th qubit

# The observable to be measured
M1 = SparsePauliOp.from_list([("XXY", 1), ("XYX", 1), ("YXX", 1), ("YYY", -1)])

gr = (np.sqrt(5) + 1) / 2 # golden ratio
thetaa = 0 # lower range of theta
thetab = 2*np.pi # upper range of theta
tol = 1e-1 # tol

# 2: Optimize problem for quantum execution.
backend = service.least_busy(operational=True, simulator=False)
pm = generate_preset_pass_manager(backend=backend, optimization_level=1)
isa_circuit = pm.run(circuit)
isa_observables = M1.apply_layout(isa_circuit.layout)

# 3. Execute iteratively using the Estimator primitive
with Session(service=service, backend=backend) as session:
estimator = Estimator(session=session)
estimator.options.default_precision = 0.03 # Options can be set using auto-complete.
#next test range
thetac = thetab - (thetab - thetaa) / gr
thetad = thetaa + (thetab - thetaa) / gr
while abs(thetab - thetaa) > tol:
print(f"max value of M1 is in the range theta = {[thetaa, thetab]}")
job = estimator.run([(isa_circuit, isa_observables, [[thetac],[thetad]])])
test = job.result()[0].data.evs
if test[0] > test[1]:
thetab = thetad
else:
thetaa = thetac
thetac = thetab - (thetab - thetaa) / gr
thetad = thetaa + (thetab - thetaa) / gr

# Final job to evaluate Estimator at midpoint found using golden search method
theta_mid = (thetab + thetaa) / 2
job = estimator.run([(isa_circuit, isa_observables, theta_mid)])
print(f"Session ID is {session.session_id}")
print(f"Final Job ID is {job.job_id()}")
print(f"Job result is {job.result()[0].data.evs} at theta = {theta_mid}")

This code returns Job result is [4.] at theta = 1.575674623307102 using only nine iterations. This is a very powerful extension to the primitives. However, using too much code between iterative calls can lock the QPU and use excessive QPU time, which is expensive. We recommend only using sessions when needed. The Sampler can also be used within a session, but there are not any well-defined examples for this.
Instances
Access to IBM Quantum Platform channel is controlled by the instances (previously called providers) to which you are assigned. An instance is defined by a hierarchical organization of hub, group, and project. A hub is the top level of a given hierarchy (organization) and contains within it one or more groups. These groups are in turn populated with projects. The combination of hub/group/project is called an instance. Users can belong to more than one instance at any time.

NOTE: IBM Cloud instances are different from IBM Quantum Platform instances. IBM Cloud does not use the hub/group/project structure for user management. To view and create IBM Cloud instances, visit the IBM Cloud Quantum Instances page.

To view a list of your instances, visit your account settings page or use the instances() method.
You can specify an instance when initializing the service or provider, or when picking a backend:
# Optional: List all the instances you can access.
service = QiskitRuntimeService(channel='ibm_quantum')
print(service.instances())

# Optional: Specify the instance at service level. This becomes the default unless overwritten.
service = QiskitRuntimeService(channel='ibm_quantum', instance="hub1/group1/project1")
backend1 = service.backend("ibmq_manila")

# Optional: Specify the instance at the backend level, which overwrites the service-level specification when this backend is used.
backend2 = service.backend("ibmq_manila", instance="hub2/group2/project2")

sampler1 = Sampler(backend=backend1) # this will use hub1/group1/project1
sampler2 = Sampler(backend=backend2) # this will use hub2/group2/project2

If you do not specify an instance, then the code will select one in the following order:

If your account only has access to one instance, it is selected by default.
If your account has access to multiple instances, but only one can access the requested backend, the instance with access is selected.
In all other cases, the code selects the first instance other than ibm-q/open/main that has access to the backend.

Access your IBM Quantum backends
A backend is a quantum device or simulator capable of running quantum circuits or pulse schedules.
You can query for the backends you have access to. Attributes and methods of the returned instances
provide information, such as qubit counts, error rates, and statuses, of the backends.
from qiskit_ibm_runtime import QiskitRuntimeService
service = QiskitRuntimeService()

# Display all backends you have access.
print(service.backends())

# Get a specific backend.
backend = service.backend('ibm_brisbane')

# Print backend coupling map.
print(backend.coupling_map)

Next Steps
Now you're set up and ready to check out some of the tutorials.
Contribution guidelines
If you'd like to contribute to qiskit-ibm-runtime, please take a look at our
contribution guidelines. This project adheres to Qiskit's code of conduct.
By participating, you are expected to uphold to this code.
We use GitHub issues for tracking requests and bugs. Please use our slack
for discussion and simple questions. To join our Slack community use the
invite link at ibm.com/quantum/qiskit. For questions that are more suited for a forum we
use the Qiskit tag in Stack Exchange.
Authors and Citation
Qiskit Runtime IBM Client is the work of many people who contribute to the project at different levels.
If you use Qiskit, please cite as per the included BibTeX file.
License
Apache License 2.0.