A couple of additional reminders for those following the WG:
Hardware acceleration in ROS 2 and Gazebo survey is still open! 
The hardware acceleration survey for the ROS and Gazebo communities is still open. Data is still coming in. Let us know what are your preferences!
Updated list of WG goals for 2022 
During last meeting we updated the list of goals for the WG.
| Target | Goal |
|---|---|
2021 |
 1) Design tools and conventions to seamlessly integrate acceleration kernels and related embedded binaries into the ROS 2 computational graphs leveraging its existing build system (ament_acceleration extensions) [1], meta build tools (colcon-acceleration extension) and a new firmware layer (acceleration_firmware) [2]. |
2021 |
2) Provide reference examples and blueprints for acceleration architectures used in ROS 2 and Gazebo. |
2022 |
3) Facilitate testing environments that allow to benchmark accelerators with special focus on power consumption and time spent on computations (see HAWG benchmarking approach, community#9, tracetools_acceleration, ros2_kria) |
2022 |
 4) Survey the community interests on acceleration for ROS 2 and Gazebo (see discourse announcement, survey). |
2022 |
5) Produce demonstrators with robot components, real robots and fleets that include acceleration to meet their targets (see acceleration_examples). |
2022 |
 7) Acceleration of complete ROS 2 computational graphs |
2022 |
8) Merge first hardware accelerators (kernels) into upstream packages (candidate: image_pipeline, see image_pipeline instrumented at #717 ) |
2022 |
9) Documentation and a “methodology to hardware accelerate a ROS 2 package”
|
2022 |
10) Organize workshops on robotics and ROS 2 Hardware Acceleration
|
Complete details available in the community repository of the Hardware Acceleration WG.
-
See ament_vitis ↩︎
-
See acceleration_firmware_kv260 for an exemplary vendor extension of the
acceleration_firmwarepackage ↩︎