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

Total number of objects calculation #164

Open
amm272 opened this issue Aug 18, 2022 · 3 comments
Open

Total number of objects calculation #164

amm272 opened this issue Aug 18, 2022 · 3 comments

Comments

@amm272
Copy link

amm272 commented Aug 18, 2022

Hello,

This issue is related to the 'num_objects' value, calculated as the num_matches + num_switches. I have a few questions:

  • Is num_objects supposed to be equal to the total number of ground truth objects within all the frames?
  • If so, why is the num_object metric not calculated from the ground truth data, instead of being the sum of switches plus matches?

I have an issue where the total num_objects counted is larger than the sum of all the ground truth objects. For example, I count 24 objects, but the total number reported is 30. Usually each frame has 6 objects, so the result is off by exactly one frame. What cold be the source of this error?

@cheind
Copy link
Owner

cheind commented Aug 19, 2022

@jvlmdr are you familiar with this?

@amm272
Copy link
Author

amm272 commented Aug 19, 2022

Thank you for raising this with @jvlmdr . Is there a way I could print the output of the accumulator per frame? Having the number of matches and switches at each stage could be helpful with debugging.

@cheind
Copy link
Owner

cheind commented Aug 20, 2022

yes. see the readme here
https://github.com/cheind/py-motmetrics#populating-the-accumulator

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

2 participants