-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
rename Model steps #1051
rename Model steps #1051
Conversation
Hello @williamFalcon! Thanks for updating this PR.
Comment last updated at 2020-03-05 17:32:23 UTC |
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.
Minor comment in the docs, everything else looks great, and should be backwards compatible :)
@@ -34,11 +34,11 @@ Log metrics | |||
|
|||
To plot metrics into whatever logger you passed in (tensorboard, comet, neptune, etc...) | |||
|
|||
1. Training_end, validation_end, test_end will all log anything in the "log" key of the return dict. | |||
1. training_step_end, validation_end, test_end will all log anything in the "log" key of the return dict. | |||
|
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.
Perhaps these should say validation_epoch_end
or validation_step_end
?
Will validation_end be renamed to validation_epoch_end? Validation can be done multiple times per epoch by setting the flag in the trainer, so renaming that would be confusing. |
yes, but validation_epoch_end is called at the end of a validation epoch NOT training epoch. the general new pattern is: ___step __step_end is only necessary if you use dp and need full batch loss or something (ie: negative sampling) |
* training_end renamed to training_step_end * training_end renamed to training_step_end * training_end renamed to training_step_end * training_end renamed to training_step_end * training_end to training_step_end * training_end to training_step_end * training_end to training_step_end * training_end to training_step_end * fix lost model reference * training_end to training_step_end * training_end to training_step_end * training_end to training_step_end * training_end to training_step_end * training_end to training_step_end * training_end to training_step_end * training_end to training_step_end * training_end to training_step_end * training_end to training_step_end * training_end to training_step_end * training_end to training_step_end * training_end to training_step_end * training_end to training_step_end * training_end to training_step_end * training_end to training_step_end * training_end to training_step_end * training_end to training_step_end * training_end to training_step_end * training_end to training_step_end * training_end to training_step_end * training_end to training_step_end * training_end to training_step_end * training_end to training_step_end * training_end to training_step_end * training_end to training_step_end * training_end to training_step_end * training_end to training_step_end * training_end to training_step_end
What does this PR do?
Fixes # (issue).
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 🙃