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 not use 200, Was it a clerical error? #14

Open
jiangxb98 opened this issue May 17, 2023 · 1 comment
Open

Why not use 200, Was it a clerical error? #14

jiangxb98 opened this issue May 17, 2023 · 1 comment

Comments

@jiangxb98
Copy link

https://github.com/LiWentomng/BoxInstSeg/blob/main/configs/boxinst/boxinst_r50_fpn_1x_coco.py#L88
max_per_img = 2000, but in other framework configurations it's 200.

@LiWentomng
Copy link
Owner

@jiangxb98 The parameter for max_per_img = 2000 or max_per_img = 200 have the similar performance for general coco and voc dataset. For the scene with the very dense objects, like remote sensing image, max_per_img = 2000 could have the better performance.

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