Fix optimizer verbosity in fixedpoint algorithm selector#175
Merged
Fix optimizer verbosity in fixedpoint algorithm selector#175
fixedpoint algorithm selector#175Conversation
Member
|
Just out of curiosity, and to check that we are consistent:
|
Collaborator
Author
|
In that case, PEPSKit is not really consistent with MPSKit and KrylovKit. Here, |
Codecov ReportAll modified and coverable lines are covered by tests ✅
... and 1 file with indirect coverage changes 🚀 New features to boost your workflow:
|
lkdvos
approved these changes
Apr 14, 2025
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
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.
Small fix for wrong relative verbosity in
select_algorithm(fixedpoint, ...): we want to have optimizer output for each iteration if the global verbosity is 1.