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

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? #12992

Open
1 task done
AFallDay opened this issue May 9, 2024 · 1 comment
Labels
question Further information is requested

Comments

@AFallDay
Copy link

AFallDay commented May 9, 2024

Search before asking

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 AFallDay added the question Further information is requested label May 9, 2024
@AFallDay
Copy link
Author

AFallDay commented May 9, 2024

@jkocherhans @timstokman @akx @cgerum

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

No branches or pull requests

1 participant