-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
Throw warning on changing val_loss #3010
Conversation
Hello @shivin7! Thanks for updating this PR. There are currently no PEP 8 issues detected in this Pull Request. Cheers! 🍻 Comment last updated at 2020-08-16 23:38:34 UTC |
Right now I'm throwing the same warning when the output of |
Codecov Report
@@ Coverage Diff @@
## master #3010 +/- ##
======================================
- Coverage 90% 90% -0%
======================================
Files 81 81
Lines 7644 7645 +1
======================================
- Hits 6878 6858 -20
- Misses 766 787 +21 |
@@ -343,6 +343,11 @@ def _evaluate( | |||
m = 'only EvalResults or dicts are allowed from validation_step' | |||
raise MisconfigurationException(m) | |||
|
|||
# throw warning if key other than 'val_loss' is used in output | |||
if not isinstance(output, EvalResult) or 'val_loss' not in output.keys(): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
that’s not what we meant.
the warning js when the word monitor changes in a callback AND you are using a result obj
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh I see.
So something like when EarlyStopping(monitor='not_val_loss')
AND using a Result
object?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
correct
this is time sensitive since we need to get the release out today. I'll take care of this one, but please give another issue a shot! |
What does this PR do?
Fixes #2868
Before submitting
PR review
Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in Github issues there's a high chance it will not be merged.
Did you have fun?
Make sure you had fun coding 🙃
Please note : I'm a little new with the tests so any comments are really helpful. Thanks!