Why is the number of FP, TP calculated by val.py for a certain class different from the number predicted by detect.py and then calculated?

[AFallDay]

Search before asking

• I have searched the YOLOv5 issues and discussions and found no similar questions.

Question

I set both confidence and iou to the same in both val.py and detect.py, and I find that the bbox results are the same during prediction, but when I use the results from detect.py to calculate tp and fp, I find that one category doesn't line up with val. In addition, I found that there are some errors when saving the label result of detect.py to txt file, will it cause the above situation when I use it to calculate? Please answer the question, thank you!

The specific case is that there is a class of val.py that calculates an FP of 48 and a TP of 53, whereas my calculations with detect result in an FP of 46 and a TP of 55, which will result in a higher MAP for this class than the val.py runs out.

Additional

No response

[AFallDay]

@jkocherhans @timstokman @akx @cgerum

[github-actions]

👋 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:

• Docs: https://docs.ultralytics.com
• HUB: https://hub.ultralytics.com
• Community: https://community.ultralytics.com

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 ⭐