Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How can I train on a dataset without lidar2cam matrix? #59

Open
Italian-PAO opened this issue Nov 1, 2022 · 3 comments
Open

How can I train on a dataset without lidar2cam matrix? #59

Italian-PAO opened this issue Nov 1, 2022 · 3 comments

Comments

@Italian-PAO
Copy link

Hi filaPro,
Thank you for your brilliant work in 3D detection.
I'm trying to train imvoxelnet on my own dataset which only has world2cam matrix, but no lidar2cam matrix compared with kitti dataset. Is lidar2cam matrix is necessary for training? If so, can I train with world2cam matrix?
Thank you!

@Italian-PAO
Copy link
Author

btw, I think there is a R0 matrix (3x3) in our custom dataset just like kitti, however it's in a vector format, like this
image
and as we can see, the translation matrix is extremely larger than that in kitti

@filaPro
Copy link
Contributor

filaPro commented Nov 2, 2022

Yes, I don't see difference between lidar2img and world2img. We only compute projection matrix here and use it here. Just check that your points from world coordinate system are projected to something reasonable in this function. Also be careful with world coordinate ranges for your custom dataset 1, 2.

Btw, we also implement ImVoxelNet in original mmdetection3d repo. The code may be more clean there.

@Italian-PAO
Copy link
Author

Thank you so much for your reply!
Actually, I am using mmdet3d repo, and I have used the roation (without the translation) above to formulate "world2img" matrix, but when I browse my dataset in mmdet3d, the dir angle seems to have pi/4 offset, like this
image
I think maybe it's caused by "LiDARInstance3DBoxes" in mmdet3d, because when I browse the dataset with other model's config using "CameraInstance3DBoxes", the visualization result is right.
I also tried to change the “dir_offset” in anchor3d_head.py, but it still does not help.
What could be the reason of this problem?Or will this problem affect the detection results except the wrong angle.
Thanks again

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants