-
Notifications
You must be signed in to change notification settings - Fork 307
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
how to calculate the flops for pixelshuffle operation? #67
Comments
Hi sovrasov , may I know that would pixel shuffle consume floating point operation? |
I've reviewed the original paper that introduced PixelShuffle and agree that it's rather a memory rearrangement operator, so the current behavior is correct. |
Thanks for the clarifcation. Is that the memory rearrangement operator will not be considered as floating point operation? |
Yep, memory rearrangement always consumes time, but it is out of scope for flops metric. I'd rather keep the straightforward flops definition to avoid misunderstanding. For such operations like PixelShuffle or even ReLU we should think about a different metric. |
Thanks. As you said there is a paper that introduced PixelShuffle, may I have the name of it? |
Thanks. |
I have fit a model with pixelshuffle operation to this flops calculation.
However, it cannot calculate the flops in pixelshuffle layer.
PixelShuffle(0.0 M, 0.000% Params, 0.0 GMac, 0.000% MACs, upscale_factor=2)
Can anyone help?
The text was updated successfully, but these errors were encountered: