Skip to content

ROS2 Migration #2

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

Open
amock opened this issue Feb 25, 2025 · 1 comment
Open

ROS2 Migration #2

amock opened this issue Feb 25, 2025 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@amock
Copy link
Member

amock commented Feb 25, 2025

This repository needs to be migrated to ROS2. I expect to have time for this starting in April/May. If anyone gets to it sooner, please comment here to avoid duplicate efforts.

@amock amock self-assigned this Feb 25, 2025
@amock amock added the enhancement New feature or request label Feb 25, 2025
@amock
Copy link
Member Author

amock commented Apr 12, 2025

I've pushed the first attempt at migrating this to ROS 2 to the humble branch. In theory, it should work similarly to the ROS 1 version. However, we still need to verify this, and there are a few remaining ROS 2–specific issues:

  1. Test a few scenarios to check whether the results match those of the ROS 1 version.
  2. A slow TF rate between the map and odom frames causes delayed or missing point cloud rendering in RViz (when using the map frame). How can we fix this?
  3. Rendering the TSDF map in RViz2 consumes a lot of GPU resources. Check whether this was also the case in the ROS 1 version.
  4. Run more tests.

Once these issues are resolved, we can begin duplicating the branch for Jazzy, as it also compiles and runs there without changes. We can also add more example configurations at that point.

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

No branches or pull requests

1 participant