Deprecate num_steps in qml.evolve
#7954
Merged
Conversation
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
|
Hello. You may have forgotten to update the changelog!
|
PietropaoloFrisoni
changed the title
num_steps in qml.evolve and enforce analytic-only behaviour
PietropaoloFrisoni
changed the title
num_steps in qml.evolve and enforce analytic-only behaviournum_steps in qml.evolve
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #7954 +/- ##
==========================================
- Coverage 99.68% 99.68% -0.01%
==========================================
Files 542 542
Lines 55622 55628 +6
==========================================
+ Hits 55449 55454 +5
- Misses 173 174 +1 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
…o Deprecating_num_steps_evolution
JerryChen97
reviewed
Jul 24, 2025
There was a problem hiding this comment.
Would like to hear how people think about remove time @isaacdevlugt @Alex-Preciado
I would say let's just remove it 0.44, unless more concern regarding plugins etc coming up here
…o Deprecating_num_steps_evolution
isaacdevlugt
approved these changes
Jul 25, 2025
JerryChen97
approved these changes
Jul 25, 2025
Co-authored-by: Isaac De Vlugt <[email protected]>
github-merge-queue bot
pushed a commit
that referenced
this pull request
Aug 1, 2025
The `num_steps` argument of `qml.evolve` and `qml.ops.Evolution` has been deprecated ([here](#7954)). But, the deprecation warning was added to both functions, even though one unconditionally calls the other. So, this PR removes the deprecation warning from `qml.evolve` as the message was identical, and the deprecation warning from `Evolution` would be raised regardless. [sc-94755] [sc-96567] --------- Co-authored-by: Isaac De Vlugt <[email protected]>
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.
Context: Currently,
qml.evolveaccepts anum_stepskeyword argument, which is intended to control the Trotter decomposition of time evolution. However, on devices like default.qubit that support analytic evolution, this argument is silently ignored. This leads to ambiguous behaviour: users may assume that specifyingnum_stepsexplicitly forces Trotterization, but this is not the case.To resolve this ambiguity, we are remove support for the
num_stepsargument inqml.evolveandEvolution(makingqml.evolveanalytic-only).Note: this deprecation doesn't have a release scheduled for removal yet. Therefore, I just mention that this argument will be removed in a future version
Description of the Change: As above.
[sc-94755]