Closed tdzdog closed 2 years ago
Well, the official kitti's evaluate_object.cpp [download their devkit_object] doesn't have this if metric == 0:
check. They rather use the overlap corresponding to the metric: bev_box_overlap and d3_box_overlap (which is passed through a function pointer). So, indeed the code needs a fixing. It should not be a difficult task correcting it though.
A very simple fix can be something like this:
Well, the official kitti's evaluate_object.cpp [download their devkit_object] doesn't have this
if metric == 0:
check. They rather use the overlap corresponding to the metric: bev_box_overlap and d3_box_overlap (which is passed through a function pointer). So, indeed the code needs a fixing. It should not be a difficult task correcting it though.A very simple fix can be something like this:
Thanks very much!
This issue is stale because it has been open for 30 days with no activity.
This issue was closed because it has been inactive for 14 days since being marked as stale.
Recently, I studied the Kitti evaluation code in _kitti_object_evalpython. But I find a confusing thing. When handling the DontCare dt, there is a judgment of "metric == 0" a shown in the codes (line 249 in kitti_object_eval_python/eval.py)
This leads to that the fp predictions in DontCare are are ignored only for 2D bbox detection. Hence there are more fp for 3D object detection. Is this a bug or I missed something?