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

Computation of TPs and FPs in COCOeval class #664

Open
CRISBAKH opened this issue Jan 8, 2024 · 0 comments
Open

Computation of TPs and FPs in COCOeval class #664

CRISBAKH opened this issue Jan 8, 2024 · 0 comments

Comments

@CRISBAKH
Copy link

CRISBAKH commented Jan 8, 2024

In the COCOeval class documentation, we find:

dtMatches - [TxD] matching gt id at each IoU or 0

gtMatches - [TxG] matching dt id at each IoU or 0

What if a matching happens for the first dt of gt objects that have 0 index ? Then a 0 in dtMatches or gtMatches will be wrongly interpreted during TP and FP computation no ? I'm talking about case like this

dtMatches = [1.0, 2.0, 0.0, 0.0, 0.0, 0.0, 0.0] --> we have 7 available detections with indices dtIds = [0, 1, 2, 3, 4, 5, 6]
gtMatches = [3.0, 0.0, 1.0, 0.0] --> we have 4 available ground truth with indices gtIds = [0, 1, 2, 3]

if we check both dtMatches and gtMatches, it seems that dt_matches[3]=0 is not a non matching indicator but more a matching with the gt object of index 0 where gtMatches[0] = 3. Then how to differentiate a 0-index matching from a 0 reflecting a non matching found ?

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

No branches or pull requests

1 participant