Change in motion of object and 1 missed det led to change in tracking ID.

[alaap001]

Search before asking

• [X] I have searched the Yolo Tracking issues and found no similar bug report.

Question

Hey @mikel-brostrom Thanks for the great repo an help so far.

I have a curious case related to association(if I am not wrong) I have been thinking about how to solve it, and any advice from an expert would be appreciated.

Brief of issue:

I have a human walking in 1 direction to load some goods on a truck and the ID is being properly tracked to 0.

Later he instantly chose to go in the opposite direction, and as he does that, the detector misses detection for 1 frame and 1 frame only. As soon as I get the new bbox (which is different in size and in different direction) the tracker assigns it a different id of 1.

Now what I cannot fathom is how just 1 missed det led to a change in id. I checked the boxes, and IOU is > 0.3 and human hasn't moved too far, only in the opposite dir. The size of bbox changes due to the angle so I figured crop could have different features that ReId failed to associate.

But I suspect it could be kalman filter but I tried setting w_association_emb=0.99 to put more weight on ReID in hope that ReID will surely work but that did not help either. Different REID models also not helping. [Clip to osnet x1]

I have tried playing with inertia, max-age, and other params with different values but the problem persists.

How could we have solved this problem if we were to? it will be a common thing that object changes its motion and in btw missed 1 or 2 dets, new det should still be assigned the same id but here in this case it is not.

I created a reference image to make it easier to understand:

Thank you.