-
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 log_save_interval, row_log_interval #3748
Conversation
How about just |
@rohitgr7 I believe this is what we decided on (cc @edenlightning). We can put up a poll in slack if people want though. |
Codecov Report
@@ Coverage Diff @@
## master #3748 +/- ##
=======================================
+ Coverage 83% 90% +8%
=======================================
Files 108 108
Lines 8807 8388 -419
=======================================
+ Hits 7284 7584 +300
+ Misses 1523 804 -719 |
Codecov Report
@@ Coverage Diff @@
## master #3748 +/- ##
=======================================
+ Coverage 83% 88% +4%
=======================================
Files 117 115 -2
Lines 9106 8913 -193
=======================================
+ Hits 7587 7799 +212
+ Misses 1519 1114 -405 |
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.
If you guys already decided, then I'm happy with it. Though if there was a vote, I would vote for a shorter name with fewer underscores.
interval is not clear enough sadly... interval could be interpreted as: [1, 5] or 5 or 0.2 steps shows it's about steps |
log_save_interval -> flush_logs_every_n_steps
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.
add test for deprecated API, that with calling old ones the warning is raised...
https://github.com/PyTorchLightning/pytorch-lightning/blob/master/tests/test_deprecated.py
also, move deprecated API to a particular class
https://github.com/PyTorchLightning/pytorch-lightning/blob/master/pytorch_lightning/trainer/deprecated_api.py
@teddykoker the label ready-to-go in meant for reliever not for PR author :] |
This pull request is now in conflict... :( |
Co-authored-by: Jirka Borovec <[email protected]>
Co-authored-by: Jirka Borovec <[email protected]>
Hello @teddykoker! Thanks for updating this PR. There are currently no PEP 8 issues detected in this Pull Request. Cheers! 🍻 Comment last updated at 2020-10-06 09:33:23 UTC |
This pull request is now in conflict... :( |
This pull request is now in conflict... :( |
need to update in #3881 files in case it gets merged. |
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.
still, some deprecation/compatibility is missing
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.
fixed, shall be fine now :]
Thanks @Borda :) |
Ugh I updated everything at the time of the PR, there must have been extra additions |
I'll need to open a new PR i guess |
maybe keep that open until the release to avoid this. |
What does this PR do?
Fixes #3690
row_log_interval -> log_every_n_steps
log_save_interval -> flush_logs_every_n_steps
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 🙃