PyTorch 1.13 Compatibility #3828
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Check out this pull request on See visual diffs & provide feedback on Jupyter Notebooks. Powered by ReviewNB |
|
Thanks so much! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PyTorch 1.13 introduced a subclassed Tensor formatting issue. A potential workaround is pytorch/pytorch#82766 which I use for the fastai
TensorBasecompatibility patch intorch_core.PyTorch 1.13 also adds "differentiable" as another
optimhyperparameter and it looks like PyTorch 1.14 will add "fused" for at least a subset of optimizers. Since I modifiedOptimWrappernot to error out in #3821, I changed theOptimWrappertests to only check for the subset of hyperparameters fastai cares about.Tested locally running the cuda and slow flags without issue.