We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently only NMS and RoIAlign support autocast (introduced in PyTorch 1.6.0). We should extend support for autocast to all C++ ops in torchvision.
Mixed precision training is PyTorch is obtained via support for autocast (automatically casting between fp16 -> fp32 depending on the operation).
The work should follow what was done for the RoIAlign function in #2384 (as that PR also converted NMS to use the dispatcher).
Adding support for autocast means that the op should be registered via the dispatcher, so this is blocked by #2796
Out-of-the-box mixed precision support for all operators implemented in torchvision:
The text was updated successfully, but these errors were encountered:
Fixed via referenced issues, with last PR in #2938
Sorry, something went wrong.
datumbox
No branches or pull requests
🚀 Feature
Currently only NMS and RoIAlign support autocast (introduced in PyTorch 1.6.0). We should extend support for autocast to all C++ ops in torchvision.
Motivation
Mixed precision training is PyTorch is obtained via support for autocast (automatically casting between fp16 -> fp32 depending on the operation).
The work should follow what was done for the RoIAlign function in #2384 (as that PR also converted NMS to use the dispatcher).
Adding support for autocast means that the op should be registered via the dispatcher, so this is blocked by #2796
Pitch
Out-of-the-box mixed precision support for all operators implemented in torchvision:
The text was updated successfully, but these errors were encountered: