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

trian/test.prototxt #13

Closed
foralliance opened this issue May 9, 2018 · 2 comments
Closed

trian/test.prototxt #13

foralliance opened this issue May 9, 2018 · 2 comments

Comments

@foralliance
Copy link

@Robert-JunWang

I found that in the final prediction, stage4_tb/ext/pm2/res was used to make two predictions, except that the min_size and max_size settings in the "PriorBox" were different, all the others are same

Why do you make two predictions separately instead of merging them? What are the advantages of these two predictions?

@Robert-JunWang
Copy link
Owner

You can merge them, the result should be the same. The reason why I use two predictions separately is to make things easier to try different feature extraction networks. Also, It makes possible to try the unified prediction mentioned in RUN with the last 5 feature maps, but I do not see any improvement on mAP by using unified prediction.

@foralliance
Copy link
Author

many many thanks

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