-
-
Notifications
You must be signed in to change notification settings - Fork 16.7k
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
Documentation on aspect ratio threshold #2521
Comments
@ml5ah thanks for the feedback! Yes perhaps box candidate thresholds should be included in the hyperparameters used for training to make them easier to modify and easier to spot. Can you submit a PR for this to help others? I will add a TODO here to update the Custom Training Tutorial with this information. In general you should also be aware that the default architecture is not optimized for high aspect ratio objects, and the models would benefit from changes targeted specifically to this domain, which may include elongation of the convolution kernels in the C3 layers, i.e. perhaps alternate 5x1 and 1x5 convolutions in place of, or in addition to, the current 3x3 and 1x1 sequences. TODO: Update Train Custom Data Tutorial with label candidate criteria section, as well as NMS settings section. |
Very good note 👍👍 |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
@glenn-jocher Can we revive this issue? I'd be happy to draft a PR. |
@MrinalJain17 could yo please review this PR? #2869 |
@ml5ah Oh, I didn't realize there was already a PR on this. Thanks of the info. Hope this feature gets merged soon. |
TODO removed, default AR threshold increased to 100 in #5556 |
🚀 Feature
Hi @glenn-jocher
Thanks for the amazing work with yolov5
This feature is related to documentation on the aspect ratio threshold in utils/datasets.py that is used for custom training.
Motivation
I have been working on object detection projects and using YOLOv5 frequently for some of the training tasks at hand. However, most of the time, mAP performance did not match my expectations set seeing the mAP scores on the COCO dataset. My dataset has mostly rectangular objects, and about 10-15% of them being either very wide or very tall. Going through one of the issues on GitHub, I realized that there is an aspect ratio threshold that discards all objects having an aspect ratio > 20 by default.
Pitch
It would be great to make this clear in the train custom dataset (https://github.com/ultralytics/yolov5/wiki/Train-Custom-Data)
so that we can adjust this parameter from the get go during experimentation. Thanks for the help!
The text was updated successfully, but these errors were encountered: