Migrate ROS 1 elevation_mapping_cupy to ROS 2 (Humble) with Existing pybind11 Integration #107
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This pull request continues the migration of
elevation_mapping_cupy
to ROS 2, including the already existingpybind11
functionality from the ROS 1. Below are the details of the migration effort:Changes Made
pybind11
Integration:pybind11
bindings to work seamlessly in the ROS 2 framework.core_param.yaml
. This is not desirable for modularity and maintainability.To-Do: Split parameters into separate YAML files specific to individual components or nodes to improve clarity and reusability.
CMakeLists.txt
andpackage.xml
to ensure compatibility with ROS 2 while preservingpybind11
dependencies.ament_cmake
for ROS 2 builds..launch
files with.py
launch files compatible with ROS 2.Testing and Validation
pybind11
Compatibility: Tested existingpybind11
bindings to ensure smooth integration with the migrated ROS 2 components..py
launch files initialize nodes and bindings correctly.