Skip to content

ROS 2 Jazzy Migration#70

Open
karlkurzer wants to merge 1 commit intomasterfrom
ros2-migration-13208419609819799497
Open

ROS 2 Jazzy Migration#70
karlkurzer wants to merge 1 commit intomasterfrom
ros2-migration-13208419609819799497

Conversation

@karlkurzer
Copy link
Copy Markdown
Owner

This pull request performs a comprehensive migration of the codebase from ROS 1 to ROS 2 Jazzy.

Highlights:

  1. Architecture Preserved: The original structural components such as Planner, CollisionDetection, and DynamicVoronoi remained fully intact.
  2. Build Updates: The system now natively builds under ament_cmake.
  3. Core APIs Ported: Upgraded components from ros:: abstractions to their rclcpp equivalents (including rclcpp::Node, publisher/subscriptions, timing components, and execution flows). TF has also been completely moved to tf2_ros.
  4. Validation Test suite: Integrated an automated parity checker inside test_parity.cpp evaluating end-to-end functionality via gtest verifying that planner path calculation remains viable in the upgraded context.
  5. Bug Fixes: A significant amount of unhandled heap corruption, C-style casts, and raw array issues embedded in the legacy source (ex. nested binMap array ownership conflicts, non-deterministic tf2::TransformListener threading) have been systematically resolved ensuring stable ASAN execution profiles.

PR created automatically by Jules for task 13208419609819799497 started by @karlkurzer

- Updated build system to ament_cmake and updated package.xml dependencies.
- Converted all ROS 1 nodes, subscribers, and publishers to rclcpp in C++.
- Ported all TF transformations and logic from tf/tf_ros to tf2/tf2_ros.
- Translated XML launch files to modern ROS 2 Python LaunchDescription.
- Addressed multiple dynamic allocation heap errors and memory corruption bugs (double-frees).
- Created a robust gtest validation suite ensuring C++ parity and stability.

Co-authored-by: karlkurzer <10877966+karlkurzer@users.noreply.github.com>
@google-labs-jules
Copy link
Copy Markdown
Contributor

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

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

Successfully merging this pull request may close these issues.

1 participant