Fix cvxpy qpt check #761
Merged
Fix cvxpy qpt check #761
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Fix error in QPT check for setting CVXPY trace preserving constraint. The check for qpt was always returning true, but the this wasn't causing an error because the modified CVXPY options werent actually being used.
nkanazawa1989
approved these changes
Apr 4, 2022
chriseclectic
added
the
Changelog: Bugfix
paco-ri
pushed a commit
to paco-ri/qiskit-experiments
that referenced
this pull request
Jul 11, 2022
Fix error in QPT check for setting CVXPY trace preserving constraint. The check for qpt was always returning true, but the this wasn't causing an error because the modified CVXPY options werent actually being used.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 error in QPT check for setting CVXPY trace preserving constraint. The check for qpt was always returning true, but the this wasn't causing an error because the modified CVXPY options weren't actually being used.
Details and comments