Reverse time order Tracking

[wenyiwangbst]

Hi, Thanks for sharing the code. When I look into the tracking module, I notice that the default score threshold for first stage tracking is 0.1 while the detection output score threshold is 0.03. So for second stage only objects between 0.03 and 0.1 are considered. However in Reverse time order tracking it only run stage two which will only consider objects between 0.03 and 0.1. Is it what the detzero tracking designed for or it's a bug which originally should use two stage tracking as well or only use stage one tracking?

[PrinceVictor]

Thanks for your interest in our work. The Reverse Order Tracking is designed to utilize only stage two for data association and tracking. This is to avoid redundant bounding boxes and maintain tracking accuracy. In forward order tracking, any detection outputs with score greater than 0.1 have either already been created new track or updated during tracking.

[KoapT]

Thanks for your interest in our work. The Reverse Order Tracking is designed to utilize only stage two for data association and tracking. This is to avoid redundant bounding boxes and maintain tracking accuracy. In forward order tracking, any detection outputs with score greater than 0.1 have either already been created new track or updated during tracking.

that is to say, in the forward order tracking process, all the first-level detection boxes are definitely used to update or create a track. The reverse order tracking will not handle these 1st-level detection boxes, but only use second-level detection boxes to update the track. I had the same question before, thanks for your answer!