-
Notifications
You must be signed in to change notification settings - Fork 34
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 use of qasm simulator #589
Conversation
Closes #502.
backend_names_repeated = ["ibmq_qasm_simulator"] * len(subcircuits) | ||
least_busy = service.least_busy().name | ||
backend_names_repeated = [least_busy] * len(subcircuits) |
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.
Actually, I am going to change this to restore the old code path and just put a warning right before it. I am doing this with the typical persona of somebody using this (deprecated) code in mind. If I were using cutqc still, I'd be very surprised if I upgraded and my old code that used a cloud qasm simulator suddenly uses a hardware backend instead. Better is for the user to have an error occur, and to be able to deal with it as they see fit. With the warning, they'll have a bit more context for why the qasm simulator is suddenly failing and what to do to fix it (pass backend_names
).
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.
Updated accordingly in 2d27024.
Pull Request Test Coverage Report for Build 9099267395Details
💛 - Coveralls |
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!
* Remove use of qasm simulator Closes #502. * Replace default configuration change with a warning * Add `stacklevel` to warning (cherry picked from commit e3db27b) Co-authored-by: Jim Garrison <[email protected]>
Closes #502.
I had not noticed before, but the section on setting up the sampler primitive appears twice in the second cutqc tutorial. So I was able to remove the first appearance.