-
Notifications
You must be signed in to change notification settings - Fork 230
ProgressMeter #442
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
Comments
Very nice! I like the first solution a lot more, because it does not pretend that the norm of the gradient is an accurate representation of progress (which it is usually not, unless you do gradient descent or a similarly "nice" method with a tight tolerance). Maybe displaying the value of the function to be optimized would be nice also? show_trace could become a flag: True prints to STDOUT, :progress does this, and False does nothing. |
yeah, the second one was more tongue in cheek. I think the first version with a little more information will be great |
Looks great! |
looks indeed great! |
I think this will probably be a callback thing if anything and thus up to the user. |
Reviving #84
printing the iteration history is useful when you are developing and experimenting, but as user you probably don't want to see it and still get some progress information?
Here are two variants I cooked up, which I both like, and both can probably be fine-tuned quite nicely.
The text was updated successfully, but these errors were encountered: