Skip to content

Meaning of lost_track_buffer in ByteTrack #1805

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

Open
1 task done
amaletzk opened this issue Mar 21, 2025 · 0 comments
Open
1 task done

Meaning of lost_track_buffer in ByteTrack #1805

amaletzk opened this issue Mar 21, 2025 · 0 comments
Labels
question Further information is requested

Comments

@amaletzk
Copy link

Search before asking

  • I have searched the Supervision issues and found no similar feature requests.

Question

Hi,

I do not understand the precise meaning of lost_track_buffer in the ByteTrack class. It is only used to initialize max_time_lost, which, however, seems to refer to a number of frames rather than a time (and so is a misnomer, IMHO). Furthermore, that variable is initialized as

self.max_time_lost = int(frame_rate / 30.0 * lost_track_buffer)

which does not make sense to me: why is there a division by 30?

Instead, I would understand either of the following possibilities:

  • Remove the division by 30. In that case, lost_frame_buffer refers to the time (in seconds) a track is retained.
  • Initialize max_time_lost with int(lost_track_buffer). In that case, lost_track_buffer refers to the number of frames directly, in agreement with the current docstring.

Thanks for clarifying this, and thanks for your great work!

Additional

No response

@amaletzk amaletzk added the question Further information is requested label Mar 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant