Skip to content
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

expanded verbose for all algorithms, made verbose a boolean for all algorithms #544

Merged
merged 1 commit into from
Jan 8, 2024

Conversation

vroulet
Copy link
Collaborator

@vroulet vroulet commented Oct 9, 2023

Replaced "Error" by specific name of error considered and added other information when verbose=True.
Should be useful for debugging more quickly.
All verbose are now boolean too (some were int).

@vroulet vroulet requested a review from mblondel October 9, 2023 18:15
@@ -224,7 +224,7 @@ class ArmijoSGD(base.StochasticSolver):
maxiter: int = 500
maxls: int = 15
tol: float = 1e-3
verbose: int = 0
verbose: bool = False
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The idea of using an int was that we could have several levels of verbosity:

  • 1: verbose
  • 2: very verbose
  • 3: very very verbose

For example, 2 could be used to print linesearch information.

Do you think it's unnecessary?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I did a two level verbose for the solvers with linesearch as you suggested.
I made all verbose types to be boolean or int to be consistent.
Thanks for the suggestion!

next_state,
error_name="Grad. Norm",
additional_info={
'Obj. Val.': next_state.value,
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would avoid abbreviations, e.g., I prefer Objective value here.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

@vroulet
Copy link
Collaborator Author

vroulet commented Nov 26, 2023

I changed the logging for the Zoom linesearch to partially fix the issue #555 (that is avoid printing errors when not required).
Previous comments (two levels printing, full wording) have also been tackled.

Copy link
Collaborator

@mblondel mblondel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks Vincent

@copybara-service copybara-service bot merged commit d50de94 into google:main Jan 8, 2024
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants