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

Regarding lidar2image #2

Open
W6WM9M opened this issue Nov 23, 2023 · 1 comment
Open

Regarding lidar2image #2

W6WM9M opened this issue Nov 23, 2023 · 1 comment

Comments

@W6WM9M
Copy link

W6WM9M commented Nov 23, 2023

Hello! Thank you for the work.

If I am correct, BEVFusion uses the depth information during inference which is derived from the lidar2image transformation matrix. However, as the lidar and images are taken at different timestamps, the lidar2image transformation matrix shouldn't always be the same since the vehicle is moving.

However, in your code, I do not see a ROS node that subscribes to the vehicle's pose and that the lidar2image is only initialized once in the model. As such, may I kindly check if you assume that the lidar2image transformation matrix is approximately constant?

@linClubs
Copy link
Owner

hi, The code uses message_filters of ros。the default lidar and camera data have very close timestamps and are considered synchronized. the camera and lidar are rigidly connected and the acquisition time is also synchronized, lidar2cam considered unchanged When the carrier is in motion.

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