-
Notifications
You must be signed in to change notification settings - Fork 361
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
Fixed bug in sample_measure_using_probabilities #1132
Merged
Merged
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
…asure_with_probabilities
merav-aharoni
requested review from
atilag,
chriseclectic and
vvilpas
as code owners
February 14, 2021 17:04
vvilpas
suggested changes
Feb 15, 2021
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.
Looks good! Can we add a small test reproducing the fixed problem? That way we'll be sure it doesn't happen again.
chriseclectic
added
Changelog: Bugfix
Include in the Fixed section of the changelog
stable-backport-potential
The issue or PR might be minimal and/or import enough to backport to stable
labels
Feb 16, 2021
Closed
vvilpas
added a commit
to vvilpas/qiskit-aer
that referenced
this pull request
Mar 1, 2021
Fixes a bug in CopyIn/CopyOut operations where out of bounds array elemets were accessed. Qubitvector thrust has a number of qubits num_qubits. When move_to_vector or copy_to_vector functions are called a temporary array or vector of size (1 << num_qubits) is created and passed to chunk_ CopyOut function. There, a number of elements (1 << chunk_qubits_) of the underlying structure are copied to this array/vector. The problem is that chunk_qubits can be larger that num_qubits, accessing values in the array or vector out of bounds. This is what was making PR Qiskit#1132 failing in CI.
chriseclectic
pushed a commit
that referenced
this pull request
Mar 2, 2021
Fixes a bug in CopyIn/CopyOut operations where out of bounds array elemets were accessed. Qubitvector thrust has a number of qubits num_qubits. When move_to_vector or copy_to_vector functions are called a temporary array or vector of size (1 << num_qubits) is created and passed to chunk_ CopyOut function. There, a number of elements (1 << chunk_qubits_) of the underlying structure are copied to this array/vector. The problem is that chunk_qubits can be larger that num_qubits, accessing values in the array or vector out of bounds. This is what was making PR #1132 failing in CI.
vvilpas
approved these changes
Mar 3, 2021
mtreinish
pushed a commit
to mtreinish/qiskit-aer
that referenced
this pull request
Mar 3, 2021
Co-authored-by: Victor Villar <vvilpas@gmail.com> Co-authored-by: Christopher J. Wood <cjwood@us.ibm.com> (cherry picked from commit 7267429)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Changelog: Bugfix
Include in the Fixed section of the changelog
stable-backport-potential
The issue or PR might be minimal and/or import enough to backport to stable
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
Fixed bug reported in issue #1126
Details and comments
When measuring on a subset of the qubits, when converting the sampled measurement to register form, the result was widened to all qubits in the call to int2reg. The gives incorrect results in the final register. Instead, we should only widen to the number of measured qubits.
Closes #1126 #1165