Track Objects (ByteTrack)

How it fits

Typical backends

Caveats

• I/O contractOutput is track-centric. Each frame emits the set of active CONFIRMED tracks, so the count is the number of live tracks, not the number of input detections.
• I/O contractThe [TrackedSegmentation] output arm is only selectable when the input is [Segmentation]; the carried mask comes from the input. With [BoundingBox] input it cannot be resolved and the worker errors at startup.
• I/O contractThe [Track] arm is the only one that fills each track's ``trajectory``; it holds the track's own past centre points, oldest first, capped at 64 samples.
• AccuracyByteTrack's second association pass matches detections between track_low_thresh and track_thresh to existing tracks, so a well-tracked object surviving on a weak detection is recovered rather than losing its id. Detections below track_low_thresh are dropped.
• State lifetimeA new track is tentative until matched on min_hits consecutive frames, then confirmed and emitted. A confirmed track unmatched for up to track_buffer frames coasts on its Kalman prediction; after that it is dropped and its id is never reused.
• AccuracyAssociation is IoU + Kalman motion only, with no appearance model. Add reidentify_objects_torchreid downstream when ids must survive long occlusions or identical-looking objects crossing.
• Parameter interactionmatch_thresh is the IoU-distance gate; track_thresh splits high/low detections and, with spawn_thresh, controls how readily new tracks spawn. Raise spawn_thresh to suppress spurious tracks from weak detections.