-
Notifications
You must be signed in to change notification settings - Fork 26.3k
[C++ API] Add functional overloads for pixelshuffle, pooling, upsampling, vision #29359
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
…ling, vision" Add functional overloads for pixelshuffle, pooling, upsampling, vision gh-metadata: pytorch pytorch 29359 gh/yf225/38/head
…ling, vision" Add functional overloads for pixelshuffle, pooling, upsampling, vision gh-metadata: pytorch pytorch 29359 gh/yf225/38/head
CircleCI build failures summaryAs of commit e12d49a:
Here are the reasons each build failed. This comment was automatically generated by Dr. CI. Please report bugs/suggestions on the GitHub issue tracker. |
|
If |
…ng, upsampling, vision" Add functional overloads for pixelshuffle, pooling, upsampling, vision gh-metadata: pytorch pytorch 29359 gh/yf225/38/head
…ng, upsampling, vision" Add functional overloads for pixelshuffle, pooling, upsampling, vision gh-metadata: pytorch pytorch 29359 gh/yf225/38/head
…ng, upsampling, vision" Add functional overloads for pixelshuffle, pooling, upsampling, vision gh-metadata: pytorch pytorch 29359 gh/yf225/38/head
…ng, upsampling, vision" Add functional overloads for pixelshuffle, pooling, upsampling, vision gh-metadata: pytorch pytorch 29359 gh/yf225/38/head
Thanks a lot for the suggestion - I removed the default values from all of them. |
Stack from ghstack:
This PR adds functional overloads that take the full set of arguments (instead of just Options) for the following functionals:
These new functionals lives in the
torch::nn::functional::detailnamespace and they are only meant to be called from the module forward methods (i.e. they are not public API). This is in preparation for the future change where we make module Options and functional Options two different classes, because if the module forward method has to construct a new functional Options object every time it runs it will be pretty silly and bad performance.Differential Revision: D18376978