-
Notifications
You must be signed in to change notification settings - Fork 24
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
Remap point topic for fusion purposes #139
Comments
@mitchellsayer is this a viable solution? or is "/velodyne_point_cloud" a topic that some other node subscribes to? If it is not, we can write a node to simply copy the data to another topic. |
http://wiki.ros.org/topic_tools/relay @drofp |
@menson168 is there a way to embed that in a launch file so I don't need to add an extra command step to the initialization process? |
@menson168 have we found any way to automate this process? or else we may need an extra step upon startup. otherwise, we'd probably need to modify @mitchellsayer's code |
@Francisco-Ibarra07 might be easier just have a shell script as the official startup script to include the remapper and the startup launch file |
Sorry, I completely forgot to investigate. I will take a look into the remapper tonight if it’s still needed.
Thanks,
Menson
…Sent from my iPhone
On Jan 2, 2019, at 5:24 PM, DRP ***@***.***> wrote:
@Francisco-Ibarra07 might be easier just have a shell script as the official startup script to include the remapper and the startup launch file
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
I think we're good for now! This is relatively low priority at the moment |
Problem
Autoware's calibration tool expects the Lidar to publish to "/points_raw", but our current driver publishes to "/velodyne_point_cloud"
Solution
Remap "/velodyne_point_cloud" to "/points_raw" in the decoder launch file
Relevant issue in Autoware can be found here
The text was updated successfully, but these errors were encountered: