-
Notifications
You must be signed in to change notification settings - Fork 140
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 incorrect decoding of decision variables by MagicRounding
#627
Conversation
|
Pull Request Test Coverage Report for Build 10277826007Details
💛 - Coveralls |
Co-authored-by: Takashi Imamichi <[email protected]>
Co-authored-by: Takashi Imamichi <[email protected]>
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.
Thank you for your contribution. LGTM
* Minor fixes * Add files via upload * Add files via upload * simplify iterator expression Co-authored-by: Takashi Imamichi <[email protected]> * modify releasenotes Co-authored-by: Takashi Imamichi <[email protected]> --------- Co-authored-by: Takashi Imamichi <[email protected]> (cherry picked from commit 807d481)
…) (#633) * Minor fixes * Add files via upload * Add files via upload * simplify iterator expression Co-authored-by: Takashi Imamichi <[email protected]> * modify releasenotes Co-authored-by: Takashi Imamichi <[email protected]> --------- Co-authored-by: Takashi Imamichi <[email protected]> (cherry picked from commit 807d481) Co-authored-by: Yuki Sato <[email protected]>
Summary
Fix
MagicRounding
so that the decision variables can be decoded correctly.Fix #626.
Details and comments
The iteration order of
var2op
in the method,_unpack_measurement_outcome
in :class:~qiskit_optimization.algorithms.qrao.MagicRounding
has been modified so that it can correctly run in the order of the decision variables.✅ I have added the tests to cover my changes.
✅ I have updated the documentation accordingly.
✅ I have read the CONTRIBUTING document.