Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Could there be a bug in mixed precision?
See original GitHub issueWhen I use torch 1.6.0 & accelerate 0.3.0 and set mixed precision as yes in accelerate config, nothing happens (still full precision training). If I set in the code Accelerator(fp16=True) then amp is triggered, but the loss becomes inf right away.
But if I use the pytorch way (i.e. autocast in the code myself), the training is normal and amp is enabled.
So I wonder if there is a possible bug in accelerate.
My enviroment is single 2080 Ti, local machine. The code with this problem is here.
Issue Analytics
- State:
- Created 2 years ago
- Comments:24 (9 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I was able to investigate this more and I think I found the problem. The PR above should fix the issue, would you mind giving it a try?
Thanks for the analysis and the example you provided. I’ll try to dig more into the differences tomorrow.