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

Results are not good for dota dataset #49

Open
heiyuxiaokai opened this issue Dec 3, 2018 · 5 comments
Open

Results are not good for dota dataset #49

heiyuxiaokai opened this issue Dec 3, 2018 · 5 comments

Comments

@heiyuxiaokai
Copy link

heiyuxiaokai commented Dec 3, 2018

The dataset is dota of whu
These images are cropped into (1200 x 1200) by step 900, about 8000 images.
1.The total mAP is about 0.38 when the global step is 80000, and some classes can not be detected, such as basketball_court, ground_track_field, soccer_ball_field
2.Total loss is declining from 8 to 0.4 when the global step is 260000(it seems to be the limit of this code?). But the mAP is 0.34 and some classes that can be detected in step 80000 can not be detected in step 260000.
I do some changes in the train.py for multi_gpus_train, and I have met the same problem when I use the origin code of one gpu.

@yangxue0827
Copy link
Owner

@WhiteSheep250
Copy link

@heiyuxiaokai
When you train the DOTA dataset, have you changed the parameters inside the cfgs.py? What are the specific changes? Thank you.

@heiyuxiaokai
Copy link
Author

Reference there: DetectionTeamUCAS/FPN_Tensorflow#59. @WhiteSheep250

@WhiteSheep250
Copy link

Ok, I will try that method. Thank you. @heiyuxiaokai

@WhiteSheep250
Copy link

Does the new method fit the DOTA dataset?

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