-
Notifications
You must be signed in to change notification settings - Fork 6k
fix vae dtype when accelerate config using --mixed_precision="fp16" #9601
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
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.
Thanks! Just left a comment.
vae.to(accelerator.device, dtype=torch.float32) | ||
vae.to(accelerator.device, dtype=weight_dtype) |
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 think it should be like:
if args.upcast_vae:
vae.to(accelerator.device, dtype=torch.float32)
else:
vae.to(accelerator.device, dtype=weight_dtype)
With upcast_vae
being added to the arguments?
Thanks for the comment, I have modified the code. |
The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update. |
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.
Thanks!
…uggingface#9601) * fix vae dtype when accelerate config using --mixed_precision="fp16" * Add param for upcast vae
…9601) * fix vae dtype when accelerate config using --mixed_precision="fp16" * Add param for upcast vae
What does this PR do?
Issue #9560
Fix vae dtype when accelerate config using --mixed_precision="fp16".
Who can review?
Anyone in the community is free to review the PR once the tests have passed. Feel free to tag
members/contributors who may be interested in your PR.
@sayakpaul