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

Meaning of frame column in input and output files #6

Closed
billypeanut opened this issue Aug 11, 2020 · 4 comments
Closed

Meaning of frame column in input and output files #6

billypeanut opened this issue Aug 11, 2020 · 4 comments

Comments

@billypeanut
Copy link

Hi,

Just trying to understand what is meant by the 'frame'. I assume it means successive points in time where measurements are made, but I'm curious to know why they are defined as integers, and why time is not explicitly included. From the Kalman filter scripts, it doesn't look like any time step is included in the prediction, which seems a little limiting.

Danke,
BillyPeanut

@jonperdomo
Copy link
Owner

Hi @billypeanut this is a tracking-by-detection framework for visual multi-target tracking. Yes, the first column is an integer representing the frame index in the video. Please refer to this paper which describes the algorithm, although my implementation utilizes motion scoring only (no appearance scoring):
Kim et al., 2015

@jonperdomo
Copy link
Owner

I am not sure how including a time step in the prediction would be better since the data should have a constant frame rate

@billypeanut
Copy link
Author

I see. I was thinking of this from a slightly more general use case where the measurements might come in at irregular times. In your use case with constant frame rates then you obviously won't gain anything from including the time step. Thanks.

@jonperdomo
Copy link
Owner

No problem!

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