-
Notifications
You must be signed in to change notification settings - Fork 20
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
Comments
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): |
I am not sure how including a time step in the prediction would be better since the data should have a constant frame rate |
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. |
No problem! |
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
The text was updated successfully, but these errors were encountered: