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

Result mismatch in coco metrics #6953

Closed
2 tasks done
purvang3 opened this issue Mar 11, 2022 · 5 comments
Closed
2 tasks done

Result mismatch in coco metrics #6953

purvang3 opened this issue Mar 11, 2022 · 5 comments
Labels
bug Something isn't working Stale

Comments

@purvang3
Copy link

Search before asking

  • I have searched the YOLOv5 issues and found no similar bug report.

YOLOv5 Component

Validation

Bug

I see results are not same for mAP@0.50 and mAP@0.50:0.95 during training after each epoch. I have made changes in val.py
accordingly as I am using "xywh" format for bboxes.

I have commented line
#box[:, :2] -= box[:, 2:] / 2 # xy center to top-left corner as my gt in xywh format.

Screen Shot 2022-03-11 at 12 54 35 PM

Environment

YOLOv5 🚀 v6.0-144-gc9a46a6 torch 1.10.2 CUDA:0 (NVIDIA RTX A4000, 16116MiB)
os : Ubuntu 18.04

Minimal Reproducible Example

make save_json in val.run=True and start training.

Additional

No response

Are you willing to submit a PR?

  • Yes I'd like to help by submitting a PR!
@purvang3 purvang3 added the bug Something isn't working label Mar 11, 2022
@github-actions
Copy link
Contributor

github-actions bot commented Mar 11, 2022

👋 Hello @purvang3, thank you for your interest in YOLOv5 🚀! Please visit our ⭐️ Tutorials to get started, where you can find quickstart guides for simple tasks like Custom Data Training all the way to advanced concepts like Hyperparameter Evolution.

If this is a 🐛 Bug Report, please provide screenshots and minimum viable code to reproduce your issue, otherwise we can not help you.

If this is a custom training ❓ Question, please provide as much information as possible, including dataset images, training logs, screenshots, and a public link to online W&B logging if available.

For business inquiries or professional support requests please visit https://ultralytics.com or email support@ultralytics.com.

Requirements

Python>=3.7.0 with all requirements.txt installed including PyTorch>=1.7. To get started:

git clone https://github.com/ultralytics/yolov5  # clone
cd yolov5
pip install -r requirements.txt  # install

Environments

YOLOv5 may be run in any of the following up-to-date verified environments (with all dependencies including CUDA/CUDNN, Python and PyTorch preinstalled):

Status

CI CPU testing

If this badge is green, all YOLOv5 GitHub Actions Continuous Integration (CI) tests are currently passing. CI tests verify correct operation of YOLOv5 training (train.py), validation (val.py), inference (detect.py) and export (export.py) on MacOS, Windows, and Ubuntu every 24 hours and on every commit.

@glenn-jocher
Copy link
Member

@purvang3 yes mAP mismatch with pycocotools is a known issue, and there's actually an open competition to solve it in #2258

We also have a few PRs related to mAP updates from users that you could try:

@codingonion
Copy link

codingonion commented Mar 14, 2022

@purvang3 yes mAP mismatch with pycocotools is a known issue, and there's actually an open competition to solve it in #2258

We also have a few PRs related to mAP updates from users that you could try:

* [Improve mAP0.5-0.95 #6787](https://github.com/ultralytics/yolov5/pull/6787)

* [Fix mAP bug at a higher conf #6813](https://github.com/ultralytics/yolov5/pull/6813)

I had the same problem.
test.py in v4.0、v5.0 is OK.
val.py in v6.0、v6.1 is not OK.
Please see blow.
v5 0
v6 0

@glenn-jocher
Copy link
Member

@dotnet-rs-py we have a warning in place to advise users of incorrect settings. mAP should be calculated at --conf 0.0 for best results, we compute at --conf 0.001 for significant speed improvements at near identical results. Anything above that will not allow for a full integration of the PR curve from 0 to 1, which will result in incorrect mAP.

yolov5/val.py

Lines 352 to 353 in 99de551

if opt.conf_thres > 0.001: # https://github.com/ultralytics/yolov5/issues/1466
LOGGER.info(f'WARNING: confidence threshold {opt.conf_thres} >> 0.001 will produce invalid mAP values.')

@github-actions
Copy link
Contributor

github-actions bot commented Apr 14, 2022

👋 Hello, this issue has been automatically marked as stale because it has not had recent activity. Please note it will be closed if no further activity occurs.

Access additional YOLOv5 🚀 resources:

Access additional Ultralytics ⚡ resources:

Feel free to inform us of any other issues you discover or feature requests that come to mind in the future. Pull Requests (PRs) are also always welcomed!

Thank you for your contributions to YOLOv5 🚀 and Vision AI ⭐!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Stale
Projects
None yet
Development

No branches or pull requests

3 participants