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

number labels is not same when i set different confidence #8004

Closed
1 task done
root12321 opened this issue May 27, 2022 · 5 comments · Fixed by #8005
Closed
1 task done

number labels is not same when i set different confidence #8004

root12321 opened this issue May 27, 2022 · 5 comments · Fixed by #8005
Labels
question Further information is requested

Comments

@root12321
Copy link

Search before asking

Question

in my session ,when i test map,precision,recall,the first time i set confidence is 0.001,the result is :
image
when i set set confidence is 0.2,the result is :
image
you can see the number of Labels is not same ,what is the reason for that ?
my code is the newest yolov5

Additional

No response

@root12321 root12321 added the question Further information is requested label May 27, 2022
@glenn-jocher
Copy link
Member

@root12321 as the code clearly states results for anything other than the default confidence are invalid:

yolov5/val.py

Lines 365 to 366 in a6e99e4

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.')

@root12321
Copy link
Author

@root12321 as the code clearly states results for anything other than the default confidence are invalid:

yolov5/val.py

Lines 365 to 366 in a6e99e4

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.')

it can not solve the question about the different of Labels number ,but in the code yolov5-6.0 version , diffierent confidence have same labels number, i dont know what changed in the newest code

@glenn-jocher
Copy link
Member

@root12321 thanks for the feedback! Unfortunately it's hard to narrow down the exact change that causes this difference, as there's about 500 PRs that have been pushed between now and v6.0 release.

@root12321
Copy link
Author

@glenn-jocher
may be you can not understand what i meaning
i test a dataset where have 10 images and 10 labels, one class.
in code yolov5-6.0 , i run the code val.py and result is :
微信截图_20220530090910

in code yolov5-6.1 , i run the code val.py and result is :
微信截图_20220530091008

you can see the diffference. in code yolov5-6.0,number of labels is 10,and it is right,but in yolov5-6.1,number of labels is 9, it is wrong , i dont know what happen in the new code of yolov5-6.1 , can you explain it , thank you !

@glenn-jocher
Copy link
Member

glenn-jocher commented May 30, 2022

@root12321 👋 hi, thanks for letting us know about this possible problem with YOLOv5 🚀. We've created a few short guidelines below to help users provide what we need in order to start investigating a possible problem.

How to create a Minimal, Reproducible Example

When asking a question, people will be better able to provide help if you provide code that they can easily understand and use to reproduce the problem. This is referred to by community members as creating a minimum reproducible example. Your code that reproduces the problem should be:

  • Minimal – Use as little code as possible to produce the problem
  • Complete – Provide all parts someone else needs to reproduce the problem
  • Reproducible – Test the code you're about to provide to make sure it reproduces the problem

For Ultralytics to provide assistance your code should also be:

  • Current – Verify that your code is up-to-date with GitHub master, and if necessary git pull or git clone a new copy to ensure your problem has not already been solved in master.
  • Unmodified – Your problem must be reproducible using official YOLOv5 code without changes. Ultralytics does not provide support for custom code ⚠️.

If you believe your problem meets all the above criteria, please close this issue and raise a new one using the 🐛 Bug Report template with a minimum reproducible example to help us better understand and diagnose your problem.

Thank you! 😃

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants