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

Hi, I am kinda confused about pseudo lidar points from depth map ? #12

Open
nile649 opened this issue Aug 4, 2019 · 4 comments
Open

Comments

@nile649
Copy link

nile649 commented Aug 4, 2019

can I use depth map from any architecture to create pseudo lidar points? GT lidar points are required to train model to predict pseudo lidar points from generated depth map?

@mileyan
Copy link
Owner

mileyan commented Aug 4, 2019

Yes, you can I use depth map from any architecture to create pseudo lidar points. But if you fine tune your model on the KITTI training set LIDAR points, you will get a better result. But the difference should be less than 5%.

@nile649
Copy link
Author

nile649 commented Aug 4, 2019

My question is how can I create pseudo lidar points, if I don't have velodyne ground truth for the training dataset. I am planning to test on custom dataset. Thanks

@mileyan
Copy link
Owner

mileyan commented Aug 5, 2019

You need the calib, image_2(left image) and image_3(right image) folders. And you need to generate the calibration files as the same format as KITTI object detection dataset.

@ghost
Copy link

ghost commented Nov 13, 2019

@mileyan so when using a custom dataset, what transformation matrix should I use for Tr_velo_to_cam in the absence of any LiDAR device at all?

EDIT:
Sorry, wasn't thinking clearly last night! It's just a rotation and translation matrix. So would need to figure out where my camera would be relative road surface and camera2 on KITTI, then translate it to the KITTI LiDAR position. Correct?

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