Track Objects (OC SORT)

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.
• AccuracyOC-SORT's observation-centric re-update recovers a track after occlusion by correcting its Kalman filter along the virtual path between the last and current observations, and observation momentum keeps its heading consistent, reducing id switches versus plain SORT.
• 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 motion 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 is the high-confidence gate that drives association and is the only score allowed to start a new track. Raise track_thresh to suppress spurious tracks from weak detections.