-
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
Adapt NeptuneLogger
to new neptune-client
api
#6867
Adapt NeptuneLogger
to new neptune-client
api
#6867
Conversation
Codecov Report
@@ Coverage Diff @@
## master #6867 +/- ##
=======================================
- Coverage 92% 89% -3%
=======================================
Files 179 180 +1
Lines 14904 15046 +142
=======================================
- Hits 13750 13358 -392
- Misses 1154 1688 +534 |
Hello @shnela! Thanks for updating this PR. There are currently no PEP 8 issues detected in this Pull Request. Cheers! 🍻 Comment last updated at 2021-05-13 09:09:34 UTC |
9c0bc40
to
4cfa2d0
Compare
@williamFalcon @awaelchli @Borda @SeanNaren @carmocca @tchaton @justusschock @kaushikb11 @edenlightning Hi guys. |
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 on a high level.
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, consider rather use a new name for this new logger than rename the old Legacy...
Ok, everything updated and ready to merge. |
Thanks a lot! We will follow up here as soon as 1.3 is released (May 5ish). We currently have feature freeze for stability testing and will not be able to merge new features and refactors. |
d9e6ca6
to
5b11de8
Compare
@awaelchli @tchaton so can we merge now? :p |
Co-authored-by: Adrian Wälchli <[email protected]>
Head branch was pushed to by a user without write access
Hey @shnela, Great work there ! Really excited about this :) Best, |
We to! Thank you for review and your help! Best, |
Hi! For the new |
Hi @aarzchan , In the new logger you can do it by parameterizing your Logger, like this (
There are more modes available. |
Thanks, @kamil-kaczmarek! |
Hi @shnela @kamil-kaczmarek , |
Hi @raman-rajarathinam, We are preparing an update to the neptune legacy-docs, where this use case will be supported and described. We are planning to release an update next week. |
Hi @kamil-kaczmarek after upgrading to pl==1.5.0 Neptune stopped working for me: When i start it it print the experiment multiple times and keeps printing the messege as below. https://app.neptune.ai/i008/bovine/e/BOV-575 |
Hey @i008, Did the same code worked well before upgrade to To confirm: is it training on many machines or single-machine with multiple processes? |
One local gpu. The (almost) same code worked. I had to adjust the init of the logger. |
Problem is that async processes write to the same place ( There are few strategies to mitigate that. Happy to chat online if it's ok for you. |
Hey @kamil-kaczmarek |
I did some further debugging and it seems that this i related to the CLI interface. The problem only occurs while using neptune like that:
If i do it the regular way ( trainer = , trainer.fit()) things work as expected. |
Great, thanks for the info. Let's discuss more online |
@shnela @kamil-kaczmarek The deprecated code can now be removed ( |
Adapt NeptuneLogger to changes in neptune-client api changes
NeptuneLogger
was moved to separate repoNeptuneLogger
which supports new neptune-client is createdNeptuneLogger
are implementedpiggyback:
proxy
support in oldNeptuneLogger
PyTorch Lightning Integration neptune-ai/neptune-client#413Before submitting
PR review
Anyone in the community is free to review the PR once the tests have passed.
Before you start reviewing make sure you have read Review guidelines. In short, see the following bullet-list:
Did you have fun?
I made sure I had fun coding 🙃