-
Notifications
You must be signed in to change notification settings - Fork 2.8k
Fixing python passes and docstrings related to approximation_degree #16006
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
Open
alexanderivrii
wants to merge
1
commit into
Qiskit:main
Choose a base branch
from
alexanderivrii:fix-approximation-degree-docs
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
If
Nonejust immediately defaults to 1.0, why would we change to supportingNoneas input? The current interface seems complete without it, no? (Same question forCommutativeOptimization& co)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 am not sure I fully understand the question. Calling
CommutativeOptimization(approximation_degree=None)is not the same as callingCommutativeOptimization(), as in the former caseapproximation_degreewill beNone, and in the latter case it will the default value of1.0, do you agree?In other transpiler passes, passing
approximation_degree=Nonemeans "compute approximation degree based on the target", so this option has a special meaning that I want to expose here as well. This will also allow a more consistent story: in all user-facing functions (Python and C)approximation_degreeis of typefloat | None.Having said the above,
CommutativeOptimizationcurrently does not taketargetas an argument (so internally we do setapproximation_degreeto1.0), however we want to change this in the future.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 saying that
CommutativeOptimization(approximation_degree=None)is not a valid input, so we don't have to support it. If we add aTargetsupport in the future we can enable setting it toNone-- or is there a reason to add it 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 can remove it. But I think it would be nice to have the same convention for what approximation degree is across the 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.
I agree it would be nice, but for that we'd need to have the
Target-specific behavior implemented 🙂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.
Note that we already have a similar workaround in
ConsolidateBlocks:qiskit/qiskit/transpiler/passes/optimization/consolidate_blocks.py
Line 123 in 0d63a93
More importantly, since we allow
approximation_degreeto beNonewhen generating preset pass managers, defining plugins, etc., we need to explicitly remember to overwriteNonewith1.0when callingCommutativeOptimizationandSubstitute4PiRotations, or else we will hit python type errors. The only reason we don't get these errors now is because we currently only enable these passes in the Clifford+T pipeline and because I forgot to pass theapproximation_degreeto these passes 😅.