-
Notifications
You must be signed in to change notification settings - Fork 6
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
Early stopping features for calibrate and optimize? #579
Comments
@djinnome , could you please break this out into smaller atomic issues for each feature request. This could be decomposed into intermediate results for calibrate, intermediate results for optimize, early stopping features for calibrate, and early stopping features for optimize. Also, could you clarify how this request differs from #477 and #362 . |
djinnome
changed the title
intermediate results and early stopping features for calibrate and optimize?
Early stopping features for calibrate and optimize?
Jun 5, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For calibrate, a nice intermediate result is the current loss.
For optimize, would a duality gap or optimal value be a useful intermediate value? @anirban-chaudhuri what would make sense as input to the progress hook like what we do for calibrate.
Right now, Terarium kills the process if we want to stop early, but if there is a more hygenic way to do this?
The text was updated successfully, but these errors were encountered: