-
Notifications
You must be signed in to change notification settings - Fork 29
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 unnecessary resets in generate_cutting_experiments
#458
Conversation
Pull Request Test Coverage Report for Build 6949706214
💛 - 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.
Cool! Thanks for setting this up. LGTM I'm sure we will continue to have more ideas for transpiler passes
I just had one question about the control flow stuff
ConsolidateResets(), | ||
DAGFixedPoint(), | ||
], | ||
do_while=lambda property_set: not property_set["dag_fixed_point"], |
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.
So you repeat these passes until this condition is False. What exactly triggers this? I haven't come up to speed on how control flow operations work yet.
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.
The DAGFixedPoint
pass sets this property. It's neat; I learned about it only by reading the tests for the RemoveResetInZeroState
pass in qiskit.
Transpiler passes (:mod:`circuit_knitting.utils.transpiler_passes`) | ||
=================================================================== | ||
|
||
.. automodule:: circuit_knitting.utils.transpiler_passes |
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.
👀 fancy
Fixes #452.
I'd still like to swap the tutorial and how-to as suggested in the second point at #452 (comment), but this can be done independently in a follow-up PR.