-
Notifications
You must be signed in to change notification settings - Fork 86
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
Port migration guide for Runtime 0.15 #374
Conversation
Co-authored-by: merav-aharoni <merav@il.ibm.com>
"title": "qiskit_ibm_provider to qiskit_ibm_runtime", | ||
"url": "/api/migration-guides/qiskit-runtime-from-provider" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The page title, URL title, and left sidebar position are all up for debate.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Bump @abbycross @beckykd , are you sure we like the values I set? I'm not certain they're the best. Cc @jyu00 and @kt474 if you have thoughts.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Page title works for me
Qiskit IBM Provider (the [`qiskit_ibm_provider`](../qiskit-ibm-provider) package) and | ||
Qiskit IBM Runtime (the [`qiskit_ibm_runtime`](../qiskit-ibm-runtime) package). Until now, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I added these URLs
were run in Runtime. Custom circuits that were manually transpiled and used `IBMBackend.run()` | ||
were run in Provider. | ||
|
||
In the `qiskit-ibm-runtime` 0.15 release, we added support for running custom circuits using `IBMBackend.run()` in Runtime, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I clarified when the release was that made this possible.
from qiskit.compiler import transpile, assemble | ||
|
||
circuit = QuantumCircuit(2, 2) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I added spaces between imports and code.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
Thanks! |
Brings over Qiskit/qiskit-ibm-runtime#1214. I did this by: 1. Copying and pasting the RST file 2. Running `st2myst convert docs/api/migration-guides/qiskit-runtime-backend-run.rst`, which generated a MD file 3. Renaming the file to end in `.mdx` and adding "front matter" (metadata) 4. Manually tweaking any issues 5. Attributing the original author in the Git commit with `git log --pretty="%an <%ae>" -- docs/migrate/backend_run_migration_guide.rst | sort -u | awk '{print "Co-authored-by: " $0}'` run in the qiskit-ibm-runtime repo I'll set up a redirect in Qiskit#216 for Nov 29. Co-authored-by: merav-aharoni <merav@il.ibm.com>
Brings over Qiskit/qiskit-ibm-runtime#1214. I did this by:
st2myst convert docs/api/migration-guides/qiskit-runtime-backend-run.rst
, which generated a MD file.mdx
and adding "front matter" (metadata)git log --pretty="%an <%ae>" -- docs/migrate/backend_run_migration_guide.rst | sort -u | awk '{print "Co-authored-by: " $0}'
run in the qiskit-ibm-runtime repoI'll set up a redirect in #216 for Nov 29.