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

Different IOU thresholds #12717

Closed
1 task done
Ershebet opened this issue Feb 7, 2024 · 3 comments
Closed
1 task done

Different IOU thresholds #12717

Ershebet opened this issue Feb 7, 2024 · 3 comments
Labels
question Further information is requested Stale

Comments

@Ershebet
Copy link

Ershebet commented Feb 7, 2024

Search before asking

Question

Hello!
I've trained my model with iou_thres = 0.2 (ref to hyp.scratch-low.yaml)
Which iou threshold should I use for inference? I see 0.45 in detect.py and 0.6 in val.py. Should I use 0.2, 0.45 or 0.6?
Could you please explain the difference between this values.

Additional

No response

@Ershebet Ershebet added the question Further information is requested label Feb 7, 2024
Copy link
Contributor

github-actions bot commented Feb 7, 2024

👋 Hello @Ershebet, 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 a minimum reproducible example to help us debug it.

If this is a custom training ❓ Question, please provide as much information as possible, including dataset image examples and training logs, and verify you are following our Tips for Best Training Results.

Requirements

Python>=3.8.0 with all requirements.txt installed including PyTorch>=1.8. 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

YOLOv5 CI

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

Introducing YOLOv8 🚀

We're excited to announce the launch of our latest state-of-the-art (SOTA) object detection model for 2023 - YOLOv8 🚀!

Designed to be fast, accurate, and easy to use, YOLOv8 is an ideal choice for a wide range of object detection, image segmentation and image classification tasks. With YOLOv8, you'll be able to quickly and accurately detect objects in real-time, streamline your workflows, and achieve new levels of accuracy in your projects.

Check out our YOLOv8 Docs for details and get started with:

pip install ultralytics

@glenn-jocher
Copy link
Member

@Ershebet hello!

The IOU threshold used during training is for the NMS step to determine which detections to keep based on their overlap. For inference, you can start with the default value of 0.45 in detect.py. This value is a balance between precision and recall, but you can adjust it based on your specific needs:

  • Increase the IOU threshold if you want to reduce false positives (at the risk of missing some true positives).
  • Decrease the IOU threshold if you want to capture more true positives (but you might also increase false positives).

The 0.6 value in val.py is typically used for validation purposes to be more strict on the quality of the predictions.

It's often a good idea to experiment with different IOU thresholds during inference to find the best balance for your particular use case. Remember, the optimal value can vary depending on the characteristics of your dataset and the requirements of your application.

Happy experimenting! 😊 If you need more detailed explanations, please refer to our documentation.

Copy link
Contributor

github-actions bot commented Mar 9, 2024

👋 Hello there! We wanted to give you a friendly reminder that this issue has not had any recent activity and may be closed soon, but don't worry - you can always reopen it if needed. If you still have any questions or concerns, please feel free to let us know how we can help.

For additional resources and information, please see the links below:

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 YOLO 🚀 and Vision AI ⭐

@github-actions github-actions bot added the Stale label Mar 9, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested Stale
Projects
None yet
Development

No branches or pull requests

2 participants