-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Removed 2pi wrapping for global phase parameter #10631
Conversation
Thank you for opening a new pull request. Before your PR can be merged it will first need to pass continuous integration tests and be reviewed. Sometimes the review process can be slow, so please be patient. While you're waiting, please feel free to review other open PRs. While only a subset of people are authorized to approve pull requests for merging, everyone is encouraged to review open pull requests. Doing reviews helps reduce the burden on the core team and helps make the project's code better for everyone. One or more of the the following people are requested to review this:
|
Pull Request Test Coverage Report for Build 5874648858
💛 - Coveralls |
|
I assume you're on windows, this is caused by the fact that |
releasenotes/notes/fix-param-global-phase-31547267f6124552.yaml
Outdated
Show resolved
Hide resolved
The changes LGTM, could you add a test to check the fix? You could e.g use the example from #10569 and ensure that it now runs as expected. |
Pull Request Test Coverage Report for Build 6771583945
💛 - Coveralls |
PadDynamicalDecoupling(self.durations, dd_sequence), | ||
] | ||
) | ||
try: |
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'd suggest replacing this block with an assertion. Either just on pm.run(qc)
, or perhaps on qc.global_phase
equal to that of the output circuit
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 have replaced it with following code block:
self.assertEqual(qc.global_phase + 3.14159265358979, pm.run(qc).global_phase)
But getting following error while testing:
AssertionError: ParameterExpression(a + 3.14159265358979) != ParameterExpression(a + 3.14159265358979)
Can you please help me in debugging 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.
how about self.assertEqual(qc.global_phase + np.pi, pm.run(qc).global_phase)
?
As of deprecation in 0.21 |
Added PadDynamicalDecoupling class & kept higher level. Co-authored-by: Julien Gacon <[email protected]>
9b53f11
to
8c1ec8e
Compare
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 for this. I've just force-pushed some changes to this to fix up the merge-conflict resolution commits that had gone a bit wrong, but it looks ok to me now.
It fixes #10569
Summary
Removed
_mod_2pi
function.Details and comments
It is similiar to Qiskit/qiskit-ibm-provider#689