-
Notifications
You must be signed in to change notification settings - Fork 237
detach losses when logging #1254
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
Conversation
fba83e9 to
d345902
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1254 +/- ##
==========================================
+ Coverage 87.73% 87.75% +0.01%
==========================================
Files 20 20
Lines 2716 2720 +4
==========================================
+ Hits 2383 2387 +4
Misses 333 333
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
3cc27e5 to
893adca
Compare
57a0954 to
034dc85
Compare
42ad6e8 to
3e84a0a
Compare
3e84a0a to
4f09db1
Compare
4f09db1 to
04fb3d1
Compare
bw4sz
left a comment
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.
I agree that pytorch lightning should be doing this, but I don't see a downside for us to be sure.
Description
detachlosses when logging. It's probable thatlightningdoes this for us under the hood, but good to be clear.@bw4sz want to try these fixes with your bird model branch?
I have also tried garbage collection, but I'm not sure it's necessary. Better to identify where we might be leaking.
Related Issue(s)
#1247
AI-Assisted Development
Some sanity checking with Claude Code, and an assisted review of where we might be missing resets etc.