Skip to content

Fuse -> ROS 2 Rolling Porting Progress #276

@methylDragon

Description

@methylDragon

Description

This issue tracks the progress of the ROS 2 port for Fuse, targeting the rolling release of ROS 2.
Some of the work here will be based off the work mentioned in #257.

Architectural Decisions

I will be prioritising API consistency between the ROS 1 and ROS 2 versions of Fuse. This means I won't be looking at high level architectural changes at this time.

Approach

PRs will be sent against the rolling branch on fuse and tf2_2d, working up the dependency graph and doubling back as necessary. (Or more likely, finding features to port as I work up the dependency graph, and port them for downstream packages as well.)

Changes in dependent packages that have to be made as a result of a change in a dependency packages will be made on a best effort basis, but can't be confirmed until they're buildable, so expect bugs in those PRs.

I fully expect fuse_core to take up the bulk of the migration effort. And I also fully expect needing to circle back after things finally build and run.

image

Progress

General

BONUS (if time permits)

  • (Probably bonus, too many parts to shake up) Port the pluginlib usage to rclcpp_components
  • "Dynamic reconfigure" for params

Down (Up?) The Dependency Tree

Additional Notes

  • I've tried to migrate away from boost as much as possible (into std), but there aren't equivalents for everything (e.g. serialization).

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions