-
Notifications
You must be signed in to change notification settings - Fork 85
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
Wildcard: allow running our notebooks with simulators? #1174
Comments
@beckykd had the idea of overwriting the
Here's the patched function: https://github.com/frankharkins/qiskit-ibm-runtime/blob/fake-runtime/qiskit_ibm_runtime/qiskit_runtime_service.py#L1108-L1132 UPDATE: I tried this out on #1157 and it gets a bit hairier. TranspilerError: "The control-flow construct 'if_else' is not supported by the backend." Maybe we still run some notebooks in the fortnightly cron job, but the well-behaved notebooks can use the patched package? |
@frankharkins it may be desirable for us to always try to have the notebooks work without issue with local simulators, and even communicate to users that they can swap out Re: implementation, we could maybe have
|
This uses the approach discussed in #1174 to test notebooks that submit jobs to IBM Quantum. The script behaviour has changed a bit: * We now have a list of `notebooks_no_mock`, these could include notebooks with large circuits or that demonstrate features not available on the fake backend. Future work could partially test these using the approach in [#1173](#1173). * By default, it runs all notebooks except `notebooks_no_mock`, with the patched package. * `--submit-jobs` will run **all** notebooks, without the patched package. * `--only-unmockable` will run only `notebooks_no_mock`, without the patched package. The following notebooks do **not** work with this patch, but some of them might not have worked anyway. * `tutorials/variational-quantum-eigensolver/notebook.ipynb` * `tutorials/submitting-transpiled-circuits/notebook.ipynb` * `tutorials/build-repitition-codes/notebook.ipynb` --------- Co-authored-by: Eric Arellano <14852634+Eric-Arellano@users.noreply.github.com>
This uses the approach discussed in Qiskit#1174 to test notebooks that submit jobs to IBM Quantum. The script behaviour has changed a bit: * We now have a list of `notebooks_no_mock`, these could include notebooks with large circuits or that demonstrate features not available on the fake backend. Future work could partially test these using the approach in [Qiskit#1173](Qiskit#1173). * By default, it runs all notebooks except `notebooks_no_mock`, with the patched package. * `--submit-jobs` will run **all** notebooks, without the patched package. * `--only-unmockable` will run only `notebooks_no_mock`, without the patched package. The following notebooks do **not** work with this patch, but some of them might not have worked anyway. * `tutorials/variational-quantum-eigensolver/notebook.ipynb` * `tutorials/submitting-transpiled-circuits/notebook.ipynb` * `tutorials/build-repitition-codes/notebook.ipynb` --------- Co-authored-by: Eric Arellano <14852634+Eric-Arellano@users.noreply.github.com>
We are using more hardware rather than simulators in our notebooks. This is meant to help users by showing real-world workflows, where the emphasis is running on actual hardware rather than simulators.
We don't want to complicate the notebooks by showing both simulators and hardware.
However, that poses a challenge for our docs writing pipeline:
This issue is to explore the idea of allowing us to dynamically rewrite our notebooks to use simulators rather than hardware when using our tool
nb-tester
. It would, for example, rewrite the backend to useFakeManilaV2
. We'd need to figure out the rewriting of the code, along with reckoning with simulators not working when the qubit count is too high.The text was updated successfully, but these errors were encountered: