Closed Yaziwel closed 3 years ago
Also, I am eager for your official implementation.
As your detection performance is reasonable, I guess there are some problems with the direction class setting, i.e., only the direction class is incorrect in your case. The overall performance is almost good enough. According to the implementation provided by the CenterPoint's authors, the one-stage CenterPoint should achieve the similar result with SECOND. You can refer to this repo.
Adding to the point, I think there are something different in mmdet3d's implementation and the aos will be better if you apply some transform to the rotation output (add 90 degree or sth, I don't remember exactly). Additionally, you can just ignore the aos number and only care about ap.
regarding two stage, you can see my comments here https://github.com/tianweiy/CenterPoint-KITTI/issues/20
I have meet same things before when I try to training centerpoint in KITTI dataset, and I find the roty of KITTI dataloader is different from centerpoint_head . You can just add pi in centerpoint_head.py file and aos will be fine.
Close due to inactivity. Feel free to reopen it if you have any further questions.
Traceback (most recent call last):
File "train.py", line 202, in
Hello,I tried to use it on openpcdet, but I encountered an error. Can you give me some suggestions base on GTX3070 cuda11.1 pytorch1.8.2
Hello, I have tried to implement Centerpoint on kitti dataset and the results are shown below: As you can see, it has reached reasonable results on most of the evaluation metrics except AOS. My first concern is that if it is related to the fact that the KITTI lidar frame is 90 degrees rotated from nuScenes lidar frame? If it is, what should I do to revise this error? Second, Centerpoint is a two-stage detector and I do not know if current reimplementation has achieved this?
Below is my config borrowed from SECOND and CENTERPOINT. In the meanwhile, I removed the velocity params in the model setting.