-
Notifications
You must be signed in to change notification settings - Fork 6.6k
Continuation of #942: additional float64 failure #996
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
Until #990 is addressed.
|
The documentation is not available anymore as the PR was closed or merged. |
|
Looks good to me, but @anton-l is the expert here :-) |
anton-l
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.
Oof, even I got confused by self.timesteps vs timesteps for a minute here, we'll probably need a better name at some point 😅
Going back to the PR's purpose: looks good, thanks Pedro!
Yes, the same thing happened to me :) We have |
…ace#996) * Add failing test for huggingface#940. * Do not use torch.float64 in mps. * style * Temporarily skip add_noise for IPNDMScheduler. Until huggingface#990 is addressed. * Fix additional float64 error in mps. * Improve add_noise test * Slight edit – I think it's clearer this way.
No description provided.