You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I removed the boxes that are out of the range, the tracking id need to be changed too.
Now I merge the tracking id, score into the new Class NuScenesTrackingBox: https://github.com/a1600012888/MUTR3D/blob/main/plugin/track/dataset.py#L796.
Then the mismatch of tracking ids caused from removing boxes is fixed.
The text was updated successfully, but these errors were encountered:
Hi, I fixed a bug in the post processing step in
NuScenesTrackDataset._format_bbox
.This bug will produce mis-matched tracking indexs, results in a large drop in AMOTA, but leaves the RECALL not changed too much.
The bug is cuased by
MUTR3D/plugin/track/dataset.py
Line 871 in c2fde4e
MUTR3D/plugin/track/dataset.py
Line 588 in c2fde4e
When I removed the boxes that are out of the range, the tracking id need to be changed too.
Now I merge the tracking id, score into the new Class
NuScenesTrackingBox
: https://github.com/a1600012888/MUTR3D/blob/main/plugin/track/dataset.py#L796.Then the mismatch of tracking ids caused from removing boxes is fixed.
The text was updated successfully, but these errors were encountered: