-
Notifications
You must be signed in to change notification settings - Fork 127
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
Remove reset from beginning of tomography experiments #1250
Conversation
Some backends do not implement reset but can be treated as having reset the qubits between circuits. It is also possible some backends implement reset but have a slower, higher fidelity reset between circuits than the in-circuit reset.
@chriseclectic Do you see a problem with this? It has come up a couple times recently with qiskit-dynamics backends and with experimental backends that are not fully calibrated. |
I don't understand the test failures (conditional tomography results slightly under the threshold). The tests are using |
I studied the test failures further and decided that there is something funny about AerSimulator when reset is used (see Qiskit/qiskit-aer#1916). As far as I can tell, the results are perfectly reasonable without reset, so the test failures just reflected the tolerances being set too tightly. I ran many seeds and then set the tolerances comfortably larger than the largest deviations I saw (.9409 so set the threshold to .935, and deviations of 1.2e-2 so set the tolerance to 2e-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.
LGTM, thanks!
### Summary This change removes the reset instruction from the beginning of tomography experiments. ### Details and comments Some backends do not implement reset but can be treated as having reset the qubits between circuits. It is also possible some backends implement reset but have a slower, higher fidelity reset between circuits than the in-circuit reset. (cherry picked from commit 1acc02d)
### Summary This change removes the reset instruction from the beginning of tomography experiments. ### Details and comments Some backends do not implement reset but can be treated as having reset the qubits between circuits. It is also possible some backends implement reset but have a slower, higher fidelity reset between circuits than the in-circuit reset. (cherry picked from commit 1acc02d)
#1258) This is an automatic backport of pull request #1250 done by [Mergify](https://mergify.com). --- <details> <summary>Mergify commands and options</summary> <br /> More conditions and actions can be found in the [documentation](https://docs.mergify.com/). You can also trigger Mergify actions by commenting on this pull request: - `@Mergifyio refresh` will re-evaluate the rules - `@Mergifyio rebase` will rebase this PR on its base branch - `@Mergifyio update` will merge the base branch into this PR - `@Mergifyio backport <destination>` will backport this PR on `<destination>` branch Additionally, on Mergify [dashboard](https://dashboard.mergify.com) you can: - look at your merge queues - generate the Mergify configuration with the config editor. Finally, you can contact us on https://mergify.com </details> Co-authored-by: Will Shanks <willshanks@us.ibm.com>
…ty#1250) ### Summary This change removes the reset instruction from the beginning of tomography experiments. ### Details and comments Some backends do not implement reset but can be treated as having reset the qubits between circuits. It is also possible some backends implement reset but have a slower, higher fidelity reset between circuits than the in-circuit reset.
Summary
This change removes the reset instruction from the beginning of tomography experiments.
Details and comments
Some backends do not implement reset but can be treated as having reset the qubits between circuits. It is also possible some backends implement reset but have a slower, higher fidelity reset between circuits than the in-circuit reset.