You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are moving the Researchers program from IQP to IBM Cloud. Since researchers are likely to be interested in functionalities provided by backend.run (e.g. dynamic circuits), we want to support backend.run() on the IBM Cloud channel as well.
Since backend.runinputs are changing, backend.run in qiskit-ibm-runtime should just accept new inputs only. People who want to use the old can continue to use qiskit-ibm-provider.
Note that backend.run() may become a third primitive, and the interface may change
The text was updated successfully, but these errors were encountered:
kt474
changed the title
An IBM Cloud channel user can invoke backend.run() to run circuits using qiskit-ibm-runtime
Support backend.run() in IBM Cloud channel
Sep 29, 2023
@jyu00 - was there any discussion on what the interface should look like? Similar to backend.run() in qiskit-ibm-provider? More like circuit_runner? Wrapped as a primitive? other?
tldr, it'll just be like backend.run in qiskit-ibm-provider. We may wrap it as a primitive eventually, but it'd still need to go through a deprecation period if/when that happens.
We are moving the Researchers program from IQP to IBM Cloud. Since researchers are likely to be interested in functionalities provided by backend.run (e.g. dynamic circuits), we want to support
backend.run()
on the IBM Cloud channel as well.Since
backend.run
inputs are changing,backend.run
inqiskit-ibm-runtime
should just accept new inputs only. People who want to use the old can continue to useqiskit-ibm-provider
.Note that
backend.run()
may become a third primitive, and the interface may changeThe text was updated successfully, but these errors were encountered: