-
Notifications
You must be signed in to change notification settings - Fork 3
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
EarlyStopper(NumberSinceBest(3), PQ()) errors immediately #28
Comments
Great catch and diagnosis!
That would be awesome. |
awadell1
added a commit
to awadell1/EarlyStopping.jl
that referenced
this issue
Oct 21, 2021
Expands existing test set by adding `test_criteria` macro for testing functionality of a Stopping Criterion Detects: JuliaAI#28
awadell1
added a commit
to awadell1/EarlyStopping.jl
that referenced
this issue
Oct 21, 2021
Expands existing test set by adding `test_criteria` macro for testing functionality of a Stopping Criterion Detects: JuliaAI#28
awadell1
added a commit
to awadell1/EarlyStopping.jl
that referenced
this issue
Oct 21, 2021
Expands existing test set by adding `test_criteria` macro for testing functionality of a Stopping Criterion Detects: JuliaAI#28
awadell1
added a commit
to awadell1/EarlyStopping.jl
that referenced
this issue
Oct 22, 2021
Expands existing test set by adding `test_criteria` macro for testing functionality of a Stopping Criterion Detects: JuliaAI#28
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issues apears to be:
update_training(::NumberSinceBest, loss)
dispatches toupdate_training(::StoppingCriterion, loss) = nothing
Related to #5 but not caught by
stopping_time
, which check if training before callingdone(criteria, state)
I can take a stab at fixing this / adding in new tests tomorrow
Best,
Alex
The text was updated successfully, but these errors were encountered: