-
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
Enable NeptuneLogger to work with distributed_backend=ddp #1753
Enable NeptuneLogger to work with distributed_backend=ddp #1753
Conversation
Hello @pitercl! Thanks for updating this PR. There are currently no PEP 8 issues detected in this Pull Request. Cheers! 🍻 Comment last updated at 2020-05-08 14:34:24 UTC |
Codecov Report
@@ Coverage Diff @@
## master #1753 +/- ##
======================================
- Coverage 88% 88% -0%
======================================
Files 69 69
Lines 4158 4166 +8
======================================
+ Hits 3668 3675 +7
- Misses 490 491 +1 |
This pull request is now in conflict... :( |
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.
LGTM 🤖
Hi @Borda, thanks for the review. Since I'm conflicting with master, what is the workflow now? Should I rebase my branch onto master? Or maybe wait for more reviews before rebasing? (from what I see I need 3 approvals) |
Think you can rebase now =) |
a3d1fd4
to
9a501ff
Compare
9a501ff
to
a880802
Compare
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.
pls allow defining offline folder
@pitercl pls allow edit PR... |
just pls add a note to changelog :] |
Before submitting
What does this PR do?
Fixes #1683 (issue).
The main change in this PR is that Neptune experiment is created eagerly on NeptuneLogger instantiation. After it's created it can be retrieved in spawned Trainer process. This enables the logger to work in distrubuted trainings.
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 🙃