-
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
Fix ComposedOp.to_matrix
#9316
Fix ComposedOp.to_matrix
#9316
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 3875649126
💛 - Coveralls |
* Fix ComposedOp.to_matrix * lint Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
* Fix ComposedOp.to_matrix * lint Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
Summary
Fixes #9283.
Details and comments
The
to_matrix
method previously applied the global coefficient to each element in theComposedOp
-- which it shouldn't have as the combo function is multiplicative. Also, the dot-product should be taken of individual numpy arrays, not of one massive numpy array with all operators inside, which fixed the Matrix-Vector product bug.