Skip to content
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

Update Pytorch package to use Pytorch 2.0.1 #2143

Merged
merged 2 commits into from
Aug 26, 2023
Merged

Conversation

joeyballentine
Copy link
Member

@joeyballentine joeyballentine commented Aug 25, 2023

Supersedes #2139 and will fix #2138

I tested upscaling, face upscaling, and converting to onnx. Everything seems to work fine (i wouldn't really expect anything to break tbh).

This is required for #2092 to pass. However, since on python 3.9 Pytorch 2.0 is slower, we should update to 3.11 before we release this. But i don't think we should delay merging it, as the 3.11 migration will be the next thing i work on.

@joeyballentine joeyballentine changed the title Pytorch 2.0 Update Pytorch package to use Pytorch 2.0.1 Aug 25, 2023
@joeyballentine joeyballentine merged commit 4349b92 into main Aug 26, 2023
11 checks passed
@joeyballentine joeyballentine deleted the pytorch-2.0 branch August 26, 2023 12:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Black output image using 4x_NMKD-Superscale-SP_178000_G
2 participants