Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support backend.run() in IBM Cloud channel #1117

Closed
kt474 opened this issue Sep 29, 2023 · 2 comments · Fixed by #1138
Closed

Support backend.run() in IBM Cloud channel #1117

kt474 opened this issue Sep 29, 2023 · 2 comments · Fixed by #1138
Assignees
Milestone

Comments

@kt474
Copy link
Member

kt474 commented Sep 29, 2023

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

@kt474 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
@merav-aharoni
Copy link
Contributor

@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?

@jyu00
Copy link
Collaborator

jyu00 commented Oct 2, 2023

Yes, the epic has more details.

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.

@kt474 kt474 closed this as not planned Won't fix, can't repro, duplicate, stale Oct 5, 2023
@kt474 kt474 reopened this Oct 26, 2023
@kt474 kt474 modified the milestones: 0.14.1, 0.15.0 Nov 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants