-
Notifications
You must be signed in to change notification settings - Fork 3.4k
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
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
Where is EarlyStopping searching for metrics? #670
Comments
Hi @kuynzereb, thanks! this was indeed the issue.
|
Well, I don't really know either, but it looks like you are right :) |
pip install git+https://github.com/williamFalcon/pytorch-lightning.git@master --upgrade |
|
I tried installing with both William's and Borda's methods but I still get an error that it can't find the
and as I understand that should be enough. Any ideas what might be wrong? |
You should also define |
That worked, thank you! I must say that from the documentation it is not clear to me that it is necessary to define
As for as I know I am not doing anything progress-bar related and I should not have to define validation end. What is it that I have misunderstood? |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Where is EarlyStopping search for metrics?
Code
if I attempt to early stop according to
val_acc
I get the following error:The metrics mentioned (loss,train_loss) are from
training_step
from what I could find.I guess I'm doing something wrong, could anyone point me in the correct direction?
Update #1: the same code works with version
0.5.1
. Bug in0.5.3
?Update #2:
I found that this line in
trainer/training_loop.py
:From what I see, before this line is executed,
self.callback_metrics
containsval_acc
. After this line values that were put incallback_metrics
after validation are gone, thereforeEarlyStopping
can't find them. Can anyone confirm this is an issue?The text was updated successfully, but these errors were encountered: