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

Comparison to max-pooling #3

Closed
mys007 opened this issue Nov 24, 2021 · 3 comments
Closed

Comparison to max-pooling #3

mys007 opened this issue Nov 24, 2021 · 3 comments

Comments

@mys007
Copy link

mys007 commented Nov 24, 2021

Hi, interesting work! I was wondering what is the main difference of APS to simple max-pooling (resp. un-max-pooling for your follow-up paper): I guess max pooling is a special case of APS for single-channel tensors? So is the main point of your work that one can extend this concept to multi-channel tensors by choosing the pooling index based on the pixel norm over all channels? Thanks a lot!

@achaman2
Copy link
Owner

achaman2 commented Nov 27, 2021

Hello. Max-pooling and APS are actually very different operations.

Strided max-pooling divides a signal (or tensor) into a bunch of non-overlapping windows and returns the maximum intensity pixel from each. This is a very local operation since pixel selection in each window has nothing to do with the intensities in the other regions of the signal.

APS, on the other hand, considers different polyphase components of a signal—for eg. x(2n) and x(2n+1) for a 1-D signal x(n)—and returns the component with the highest norm as the downsampled output.

By selecting the sampling grid in this global fashion, APS obtains a downsampled output that is consistent to shifts, which is not the case with max-pooling.

Max-unpooling and APS-U from the followup paper can be compared in a similar manner.

I hope this answers your question! :)

@mys007
Copy link
Author

mys007 commented Nov 29, 2021

Thanks for the fast response and clarification! I understand now, a clever idea. I have re-read your paper and it's actually clearly written there as well, sorry for skimming it too fast earlier.

@achaman2
Copy link
Owner

Thank you and no problem at all!

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

No branches or pull requests

2 participants