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

regarding track id matching and tracker results #131

Open
benhgm opened this issue Apr 24, 2023 · 0 comments
Open

regarding track id matching and tracker results #131

benhgm opened this issue Apr 24, 2023 · 0 comments

Comments

@benhgm
Copy link

benhgm commented Apr 24, 2023

hi, I am using this repo on my own tracker and I have some questions about the usage.

  1. the ground truth MOT20 data gives track ids from 1, 2, 3, etc. In my custom tracker, I output track ids in a different format, eg, 2000, 1001, 1000, etc. As per the mot_challenge_2d_box.py script, it says that the preprocessing function calculates the number of gt and tracker detections and unique track ids and relabels them to make them contiguous. Does this mean that it does not matter that my track id is in a different format compared to the gt track ids?
  2. my tracker is probably not performing so well, so there may be some frames where there is zero detections. in this case, is it ok to leave that frame empty in my .txt tracker output files? For example, if my tracker detects nothing in frame 2, then there will not be any line entry for frame 2.
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