Fix incorrect decoding of decision variables by MagicRounding
(backport #627)
#633
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
This is an automatic backport of pull request #627 done by Mergify.