While using DeepOCSort algorithm failes with KeyError: 'last_measurement' about boxmot HOT 6 CLOSED

Fixed. I have reverted my changes. They need more testing...

from boxmot.

Hey, thanks, it worked after your fix but there seems to be 1 more bug in the repo.

I am on latest version, 10.0.73, and when I set the param new_kf_off=True I get the following error:

tracks = tracker.update(dets, im)
  File "/home/alaap/anaconda3/envs/env_py310/lib/python3.10/site-packages/boxmot/utils/__init__.py", line 81, in wrapper
    tracks = self.update(instance, dets, im)
  File "/home/alaap/anaconda3/envs/env_py310/lib/python3.10/site-packages/boxmot/trackers/deepocsort/deep_ocsort.py", line 497, in update
    trk = KalmanBoxTracker(
  File "/home/alaap/anaconda3/envs/env_py310/lib/python3.10/site-packages/boxmot/trackers/deepocsort/deep_ocsort.py", line 140, in __init__
    self.kf = OCSortKalmanFilterAdapter(dim_x=7, dim_z=4)
NameError: name 'OCSortKalmanFilterAdapter' is not defined

Let me know what I can do to fix this.
Thanks.

from boxmot.

Yup, on this.

from boxmot.

Thanks a lot, @mikel-brostrom

On another note, I also 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 and id is being properly tracked to 0.
Later he instantly chose to go in 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 diff in size and In different direction) tracker assign it a different id of 1.

Now what I cannot fathom is how just 1 missed det led to change in id. I checked the boxes, and IOU is > 0.3 and operator hasn't moved too far, only in opposite dir. The size of bbox changes de to angle so I fig crop could have diff features.

But I suspect association messed it up or could be kalman filter by I tried setting w_association_emb=0.99 to put more weight on ReID in hope that ReID will surely work but apparently that did not help.

I have tried playing with inertia, max age, and other params to diff values but problem persists.

How could we have solved this problem if we were to? it will be a common thing that object changed it's 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.

Thank you.

from boxmot.

Hey, thanks, it worked after your fix but there seems to be 1 more bug in the repo.

I am on latest version, 10.0.73, and when I set the param new_kf_off=True I get the following error:

tracks = tracker.update(dets, im)
  File "/home/alaap/anaconda3/envs/env_py310/lib/python3.10/site-packages/boxmot/utils/__init__.py", line 81, in wrapper
    tracks = self.update(instance, dets, im)
  File "/home/alaap/anaconda3/envs/env_py310/lib/python3.10/site-packages/boxmot/trackers/deepocsort/deep_ocsort.py", line 497, in update
    trk = KalmanBoxTracker(
  File "/home/alaap/anaconda3/envs/env_py310/lib/python3.10/site-packages/boxmot/trackers/deepocsort/deep_ocsort.py", line 140, in __init__
    self.kf = OCSortKalmanFilterAdapter(dim_x=7, dim_z=4)
NameError: name 'OCSortKalmanFilterAdapter' is not defined

Let me know what I can do to fix this. Thanks.

Should be fixed 🚀

from boxmot.

Thanks a lot, @mikel-brostrom

On another note, I also 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 and id is being properly tracked to 0. Later he instantly chose to go in 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 diff in size and In different direction) tracker assign it a different id of 1.

Now what I cannot fathom is how just 1 missed det led to change in id. I checked the boxes, and IOU is > 0.3 and operator hasn't moved too far, only in opposite dir. The size of bbox changes de to angle so I fig crop could have diff features.

But I suspect association messed it up or could be kalman filter by I tried setting w_association_emb=0.99 to put more weight on ReID in hope that ReID will surely work but apparently that did not help.

I have tried playing with inertia, max age, and other params to diff values but problem persists.

How could we have solved this problem if we were to? it will be a common thing that object changed it's 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.

Thank you.

Please open a new issue 😄 . As it is out of scope for this one. I will try to help you there

from boxmot.