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

Questions about your ablation studies #1

Closed
pp00704831 opened this issue Jul 26, 2021 · 3 comments
Closed

Questions about your ablation studies #1

pp00704831 opened this issue Jul 26, 2021 · 3 comments

Comments

@pp00704831
Copy link

Hello,

I have some questions about your ablation studies of pyramid pooling.
Could you detail about your baseline version in Table 9?
First, you say that you replace P-MHSA with an MHSA with a single pooling operation, what is the detail about single pooling operation? Ex: Pooling Ratios?
Second, do you compared your method with original MHSA?

@yuhuan-wu
Copy link
Owner

We cannot directly train a model with the original MHSA. As described in the introduction of our paper, the computational cost and memory usage of original MHSA is quadratic to the image size. The memory usage can even exceed to the NVIDIA A100 limit. Maybe original MHSA can achieve better result, but it is impossible to implement it under the current hardware situation.
BTW, for comparison, we replace P-MHSA with a modified MHSA that uses average pooling operations for generating k and v, and the pooling ratios are the smallest one in the P-MHSA.

@pp00704831
Copy link
Author

Thank you for your reply.
So how about the strides for pooling?
For example, when pooling ratio equals to 12, it means that you use kernel size = 12, and strides = 12 ?

@yuhuan-wu
Copy link
Owner

Thank you for your reply.
So how about the strides for pooling?
For example, when pooling ratio equals to 12, it means that you use kernel size = 12, and strides = 12 ?

Almost right. However, this may cause that some pixels are not taken into account without padding. Regarding this issue, we use adaptive kernel size, stride, and padding to make sure that all pixels are for computation.

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