-
Notifications
You must be signed in to change notification settings - Fork 71
Replaced GroverOperator usage by grover_operator #253
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
Open
tnemoz
wants to merge
3
commits into
qiskit-community:main
Choose a base branch
from
tnemoz:fix_76
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 1 commit
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
9 changes: 9 additions & 0 deletions
9
releasenotes/notes/add-support-for-grover_operator-function-8221f7abca3b84d6.yaml
This file contains hidden or 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,9 @@ | ||
--- | ||
upgrade: | ||
- | | ||
:class:`AmplificationProblem` and :class:`EstimationProblem` now use the function | ||
:func:`~qiskit.circuit.library.grover_operator` to construct the Grover operator | ||
by default, instead of the class :class:`~qiskit.circuit.library.GroverOperator`, | ||
to follow with the latter's deprecation in Qiskit 2.1. In particular, if these classes | ||
are instantiated without providing a Grover operator, the new default construction | ||
is used, and it won't be possible to access the attributes of the deprecated class. |
This file contains hidden or 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
Oops, something went wrong.
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.
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.
We could use
qiskit.__version__
to check whether to returnGroverOperator
orgrover_operator
here. This should also be documented thenThere 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.
In order not to introduce a breaking change then, is it OK if the function uses
GroverOperator
if the Qiskit version is2.1.2
or older, and otherwise usesgrover_operator
? That way, it would prevent a breaking change from users upgradingqiskit-algorithms
without upgradingqiskit
.This of course assume that the next
qiskit-algorithms
release is done before Qiskit2.2.0
is out! Or we could test for< 3.0
, since this is whenGroverOperator
is removed if I'm not mistaken. What are your views on this?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.
Good questions -- my preference would be to use the
grover_operator
function whenever possible (i.e.qiskit>=1.3
) since it's more efficient than theGroverOperator
. But maybe it's safest to just sell this as bugfix and start usinggrover_operator
withqiskit>=2.1
since theGroverOperator
was deprecated in 2.1.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.
I went for the latter and thus updated the release note to categorize this as a bug fix. Does that work for you?