-
Notifications
You must be signed in to change notification settings - Fork 217
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
[Python] Handle more conditions in MidCircuitMeasurementAnalyzer
#2701
[Python] Handle more conditions in MidCircuitMeasurementAnalyzer
#2701
Conversation
Signed-off-by: Pradnya Khalate <[email protected]>
CUDA Quantum Docs Bot: A preview of the documentation can be found here. |
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.
This LGTM ... thanks, @khalatepradnya!
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.
What happened with using the quake metadata pass?
I am working on it in a branch which isn't ready yet. It also makes one major workflow change in Python which has potential side-effects on capturing values from parent scope. This PR is attempt to mitigate issues for demos next week. |
MidCircuitMeasurementAnalyzer
MidCircuitMeasurementAnalyzer
CUDA Quantum Docs Bot: A preview of the documentation can be found here. |
Ideally this logic should be replaced with
quake-add-metadata
pass, see issue # 2000.This PR enhances the checks in the current logic to account for cases when a measurement result is assigned to new value, or is used with boolean operators.