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

Question regarding proposal feature #77

Open
abeyang00 opened this issue Mar 10, 2021 · 4 comments
Open

Question regarding proposal feature #77

abeyang00 opened this issue Mar 10, 2021 · 4 comments

Comments

@abeyang00
Copy link

abeyang00 commented Mar 10, 2021

I have a question regarding proposal feature.

In DETR paper, reshaped feature map (HW x C) is given as input to transformer encoder to learn correlation between each pixels.
However, in your paper, you use C size vector (named 'prop_feats') instead of reshaped feature map.

How does this C size vector learn the correlation among each pixels?
In my understanding this does not contain the feature information for each pixel position.

I saw your reply in one of the previous issues where you replied
'don't understand dynamic head as Q,K,V'. How should i understand this concept then??

Thank you in advance!

@PeizeSun
Copy link
Owner

Hi~
The proposal features contains information about its corresponding object. The proposal feature updates itself by interacting with RoI feature.
We don't need feature information for each pixel position.

@abeyang00
Copy link
Author

so roi feature can be regarded as Query and proposal features as Key?

@PeizeSun
Copy link
Owner

PeizeSun commented Mar 11, 2021

I guess Query is proposal features [100 x C], roi feature is Key [100 x (7 x 7 x C)] .
Think about DETR, Query is object query [100 x C], Key is 100 times reshaped image feature map [100 x (HW x C)], where each (HW x C) is the same.

@HYUNJS
Copy link

HYUNJS commented Mar 11, 2021

@PeizeSun
Isn't that Q and K must have the same hidden dimension to process matrix multiplication, like in DETR Q is [100 x C] and K is [HW x C] instead of [100 x (HWC)]?

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

3 participants