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

Include option to use PointCloud Transport #4042

Open
SteveMacenski opened this issue Jan 9, 2024 · 4 comments
Open

Include option to use PointCloud Transport #4042

SteveMacenski opened this issue Jan 9, 2024 · 4 comments
Labels
enhancement New feature or request good first issue Good for newcomers gsoc

Comments

@SteveMacenski
Copy link
Member

Per https://github.com/ros-perception/point_cloud_transport, we can now use compressed pointcloud streams in ROS 2. We can enable those in the Costmap layers that ingest pointcloud sensor streams (i.e. obstacle, voxel) and the collision monitor and show that this reduces network traffic without composed nodes to keep up better (and CPU impacts).

We would want sensor drivers and depth pipelines to have the option to output this as well to be able to ingest in Nav2 out of the box. Rviz2 + Gazebo would be ideal as well to publish PC2 from Gazebo into Rviz without as much latency

CC @ahcorde

@SteveMacenski SteveMacenski changed the title Include option to use PointCloud Transport in Costmap2D Include option to use PointCloud Transport Jan 9, 2024
@SteveMacenski SteveMacenski added good first issue Good for newcomers enhancement New feature or request labels Aug 21, 2024
@Combuster54
Copy link

Hi, could you provide more info? I would like to contribute if it´s possible.

@xFranv8
Copy link

xFranv8 commented Sep 25, 2024

I'm taking this issue. Thanks!

@SteveMacenski
Copy link
Member Author

@xFranv8 any updates?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers gsoc
Projects
None yet
Development

No branches or pull requests

4 participants