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

Why are you feeding the prorposal region again through the encoder? #73

Open
pfjaeger opened this issue Mar 20, 2018 · 2 comments
Open

Comments

@pfjaeger
Copy link

Hi,

i was wondering what the benefit is of feeding the proposed region of the input image again through the encoder to the 3rd layer (where x/y = 24/24). These exact features have been computed in the first pass and you could crop the respective region in the feature map out using the normalized proposal coordinates. You could go straight to the 2x2x2 max pooling layer.

Or am i getting something wrong?
Thanks for your answer!

@lfz
Copy link
Owner

lfz commented Mar 20, 2018 via email

@pfjaeger
Copy link
Author

pfjaeger commented Mar 20, 2018

right so this is due to the alternating training procedure you use. What if you would train the two losses simultaneously? You could take features and proposal coordinates from one single pass. Similar to the "approximate-joint training" described in the Faster RCNN paper. Does this make results worse in your case?

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