-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Fix approximation_degree
default in generate_preset_pass_maanger
#11695
Fix approximation_degree
default in generate_preset_pass_maanger
#11695
Conversation
This brings it inline with `transpile`, as was done in Qiskitgh-8595.
One or more of the the following people are requested to review this:
|
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'm ok with granting a freeze exception for this PR, it was a good catch by @chriseclectic to find this was mismatched with transpile()
. We definitely don't want this as the default and we should definitely get this in before rc1 tomorrow. Just one inline suggestion and then I think we can enqueue this for merging.
releasenotes/notes/preset-pass-manager-approximation-degree-503198b1974adf79.yaml
Outdated
Show resolved
Hide resolved
--- | ||
upgrade: | ||
- | | ||
The implicit use of ``approximation_degree!=1.0`` by default in the |
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.
FWIW, I think was only the case if a backend or target with error properties are set. The default of approximation_degree=None
was a short hand of approximate up to the error rate reported in the target. So if there was no error rate it wouldn't approximate the decomposition.
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.
tbh I just copied the first sentence of the note from #8595. Happy to change it to whatever you like
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.
It's fine this was more just me musing out loud. It's why I didn't leave a concrete suggestion.
Pull Request Test Coverage Report for Build 7733817763Warning: This coverage report may be inaccurate.We've detected an issue with your CI configuration that might affect the accuracy of this pull request's coverage report.
💛 - Coveralls |
Co-authored-by: Matthew Treinish <mtreinish@kortar.org>
Summary
This brings it inline with
transpile
, as was done in gh-8595.Details and comments
I'm proposing this as a candidate for 1.0 despite missing the deadline (needs another maintainer's sign-off) because this is really surprising behaviour, and we decided way back in #8595 that the default of "approximate away literally all of my Trotterisation" was a sufficiently poor default we ought to make the change as a sort-of bugfix. It's even more surprising for
generate_preset_pass_manager
to do this iftranspile
isn't.Fix #11693.