-
Notifications
You must be signed in to change notification settings - Fork 12
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
3D LiDAR -> .bag files -> lidar_bev ? #1
Comments
HI @Petros626 ,
Hope it helps |
Hey @beltransen, thank you for your quick response. I'm not that familiar with ROS and the terms yet, sorry. The online method is to be understood like a livestream of the LiDAR data, which were transformed in the BEV, I guess? So the important question I can only use the package in combination with these messages, i.e. other messages as input are not compatible? Or do I have to write some kind of converter, e.g. from int to double or something, because each input expects its own data type? is the package only suitable for the velodyne lidar or also for others? would i have to write my own launch file? Thank you very much for your help! |
Hi again, to use the package you should first understand how ROS works. Please, refer to the ROS tutorials. Regarding your questions:
Yes.
The inputs need to be of the defined data types. Therefore, if your sensor stream is published in a different format, you should write a converter node.
Any LiDAR model may be used, as long as the cloud is published in the desired format. However, you may need to modify the provided launch file to set the topic names accordingly. |
Hey @beltransen, thank you for your support and the quick answer. OK, I'll take a closer look at the launch file, thanks in any case. |
hey guys,
i am currently having problems understanding how the package works. as you listed, the package expects an input and gives an output.
Input: sensor_msgs/Pointcloud2 (binary_blob?)
Output: sensor_msgs/Image
is it possible to implement my streaming pipeline with this or are the conditions wrong.
Thanks for any kind of help
The text was updated successfully, but these errors were encountered: