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

Add --conf-thres >> 0.001 warning #5567

Merged
merged 1 commit into from
Nov 8, 2021
Merged

Conversation

glenn-jocher
Copy link
Member

@glenn-jocher glenn-jocher commented Nov 8, 2021

Partially addresses invalid mAPs at higher confidence threshold issue #1466.

🛠️ PR Summary

Made with ❤️ by Ultralytics Actions

🌟 Summary

Improved user warning for high confidence thresholds during validation.

📊 Key Changes

  • Added a warning message that triggers when the confidence threshold (conf_thres) is set higher than 0.001.

🎯 Purpose & Impact

  • Ensures Clarity: Alerts users to potential miscalculation of mean Average Precision (mAP) values when conf_thres is too high.
  • Enhances User Experience: Prevents users from unintentionally using a threshold that may lead to incorrect validation results.
  • Supports Best Practices: Encourages users to adhere to the recommended confidence threshold for accurate model validation.

Partially addresses invalid mAPs at higher confidence threshold issue #1466.
@glenn-jocher glenn-jocher self-assigned this Nov 8, 2021
@glenn-jocher glenn-jocher linked an issue Nov 8, 2021 that may be closed by this pull request
@glenn-jocher glenn-jocher merged commit 0de4a9c into master Nov 8, 2021
@glenn-jocher glenn-jocher deleted the add/invalid_map_warning branch November 8, 2021 15:04
BjarneKuehl pushed a commit to fhkiel-mlaip/yolov5 that referenced this pull request Aug 26, 2022
Partially addresses invalid mAPs at higher confidence threshold issue ultralytics#1466.
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

Successfully merging this pull request may close these issues.

mAP bug at higher --conf
1 participant