-
Notifications
You must be signed in to change notification settings - Fork 516
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
Precision, Recall and mAP seems incoherent #80
Comments
I have changed the metrics.py according to https://github.com/ultralytics/yolov5/blob/master/utils/metrics.py and the mAP are very different. Which one is wrong and why? |
I also open an issue in YOLOv5 repo: ultralytics/yolov5#4546 Lines 125 to 126 in 2fa3a31
To new metrics.py from YOLOv5: https://github.com/ultralytics/yolov5/blob/8b18b66304317276f4bfc7cc7741bd535dc5fa7a/utils/metrics.py#L94-L95 Thank you |
thanks, i change these two lines with your suggestion, but i think two metrics.py will still output different results. |
Hello,
I am training YOLOR-D6, I obtain precision, recall and mAP results from test.py with following command using paper branch:
python3 test.py --weights ./runs/train/yolor-d6-1280size-multiGPU/weights/best.pt --img 1280 --verbose --data data/dtld_test.yaml --batch 32 --task test --conf 0.4 --iou 0.5
Here is the result:
![image](https://user-images.githubusercontent.com/6302128/130422296-d396cac6-ca9a-47ee-92a5-c858bbea18f6.png)
I think the mAP0.5 is very high with those recall values. Is there a mistake in metrics.py? Or do I have to run test.py with different options?
Thank you.
The text was updated successfully, but these errors were encountered: