Planet ROS

Planet ROS - http://planet.ros.org

Planet ROS - http://planet.ros.org[WWW] http://planet.ros.org

ROS Discourse General: New packages for ROS 2 Rolling Ridley 2024-04-17

We’re happy to announce another sync into Rolling. This is the last Rolling sync before we branch off for Jazzy. This sync has been tagged as rolling/2024-04-17.

Package Updates for rolling

Added Packages [273]:

Updated Packages [622]:

  • ros-rolling-ackermann-steering-controller: 4.6.0-2 → 4.7.0-1
  • ros-rolling-ackermann-steering-controller-dbgsym: 4.6.0-2 → 4.7.0-1
  • ros-rolling-action-msgs: 2.0.1-2 → 2.0.2-1
  • ros-rolling-action-msgs-dbgsym: 2.0.1-2 → 2.0.2-1
  • ros-rolling-action-tutorials-cpp: 0.33.1-2 → 0.33.2-1
  • ros-rolling-action-tutorials-cpp-dbgsym: 0.33.1-2 → 0.33.2-1
  • ros-rolling-action-tutorials-interfaces: 0.33.1-2 → 0.33.2-1
  • ros-rolling-action-tutorials-interfaces-dbgsym: 0.33.1-2 → 0.33.2-1
  • ros-rolling-action-tutorials-py: 0.33.1-2 → 0.33.2-1
  • ros-rolling-actionlib-msgs: 5.3.0-2 → 5.3.4-1
  • ros-rolling-actionlib-msgs-dbgsym: 5.3.0-2 → 5.3.4-1
  • ros-rolling-admittance-controller: 4.6.0-2 → 4.7.0-1
  • ros-rolling-admittance-controller-dbgsym: 4.6.0-2 → 4.7.0-1
  • ros-rolling-ament-clang-format: 0.16.3-2 → 0.17.0-1
  • ros-rolling-ament-clang-tidy: 0.16.3-2 → 0.17.0-1
  • ros-rolling-ament-cmake: 2.3.2-3 → 2.5.0-1
  • ros-rolling-ament-cmake-auto: 2.3.2-3 → 2.5.0-1
  • ros-rolling-ament-cmake-clang-format: 0.16.3-2 → 0.17.0-1
  • ros-rolling-ament-cmake-clang-tidy: 0.16.3-2 → 0.17.0-1
  • ros-rolling-ament-cmake-copyright: 0.16.3-2 → 0.17.0-1
  • ros-rolling-ament-cmake-core: 2.3.2-3 → 2.5.0-1
  • ros-rolling-ament-cmake-cppcheck: 0.16.3-2 → 0.17.0-1
  • ros-rolling-ament-cmake-cpplint: 0.16.3-2 → 0.17.0-1
  • ros-rolling-ament-cmake-export-definitions: 2.3.2-3 → 2.5.0-1
  • ros-rolling-ament-cmake-export-dependencies: 2.3.2-3 → 2.5.0-1
  • ros-rolling-ament-cmake-export-include-directories: 2.3.2-3 → 2.5.0-1
  • ros-rolling-ament-cmake-export-interfaces: 2.3.2-3 → 2.5.0-1
  • ros-rolling-ament-cmake-export-libraries: 2.3.2-3 → 2.5.0-1
  • ros-rolling-ament-cmake-export-link-flags: 2.3.2-3 → 2.5.0-1
  • ros-rolling-ament-cmake-export-targets: 2.3.2-3 → 2.5.0-1
  • ros-rolling-ament-cmake-flake8: 0.16.3-2 → 0.17.0-1
  • ros-rolling-ament-cmake-gen-version-h: 2.3.2-3 → 2.5.0-1
  • ros-rolling-ament-cmake-gmock: 2.3.2-3 → 2.5.0-1
  • ros-rolling-ament-cmake-google-benchmark: 2.3.2-3 → 2.5.0-1
  • ros-rolling-ament-cmake-gtest: 2.3.2-3 → 2.5.0-1
  • ros-rolling-ament-cmake-include-directories: 2.3.2-3 → 2.5.0-1
  • ros-rolling-ament-cmake-libraries: 2.3.2-3 → 2.5.0-1
  • ros-rolling-ament-cmake-lint-cmake: 0.16.3-2 → 0.17.0-1
  • ros-rolling-ament-cmake-mypy: 0.16.3-2 → 0.17.0-1
  • ros-rolling-ament-cmake-pclint: 0.16.3-2 → 0.17.0-1
  • ros-rolling-ament-cmake-pep257: 0.16.3-2 → 0.17.0-1
  • ros-rolling-ament-cmake-pycodestyle: 0.16.3-2 → 0.17.0-1
  • ros-rolling-ament-cmake-pyflakes: 0.16.3-2 → 0.17.0-1
  • ros-rolling-ament-cmake-pytest: 2.3.2-3 → 2.5.0-1
  • ros-rolling-ament-cmake-python: 2.3.2-3 → 2.5.0-1
  • ros-rolling-ament-cmake-target-dependencies: 2.3.2-3 → 2.5.0-1
  • ros-rolling-ament-cmake-test: 2.3.2-3 → 2.5.0-1
  • ros-rolling-ament-cmake-uncrustify: 0.16.3-2 → 0.17.0-1
  • ros-rolling-ament-cmake-vendor-package: 2.3.2-3 → 2.5.0-1
  • ros-rolling-ament-cmake-version: 2.3.2-3 → 2.5.0-1
  • ros-rolling-ament-cmake-xmllint: 0.16.3-2 → 0.17.0-1
  • ros-rolling-ament-copyright: 0.16.3-2 → 0.17.0-1
  • ros-rolling-ament-cppcheck: 0.16.3-2 → 0.17.0-1
  • ros-rolling-ament-cpplint: 0.16.3-2 → 0.17.0-1
  • ros-rolling-ament-flake8: 0.16.3-2 → 0.17.0-1
  • ros-rolling-ament-index-cpp: 1.7.0-2 → 1.8.0-1
  • ros-rolling-ament-index-cpp-dbgsym: 1.7.0-2 → 1.8.0-1
  • ros-rolling-ament-index-python: 1.7.0-2 → 1.8.0-1
  • ros-rolling-ament-lint: 0.16.3-2 → 0.17.0-1
  • ros-rolling-ament-lint-auto: 0.16.3-2 → 0.17.0-1
  • ros-rolling-ament-lint-cmake: 0.16.3-2 → 0.17.0-1
  • ros-rolling-ament-lint-common: 0.16.3-2 → 0.17.0-1
  • ros-rolling-ament-mypy: 0.16.3-2 → 0.17.0-1
  • ros-rolling-ament-pclint: 0.16.3-2 → 0.17.0-1
  • ros-rolling-ament-pep257: 0.16.3-2 → 0.17.0-1
  • ros-rolling-ament-pycodestyle: 0.16.3-2 → 0.17.0-1
  • ros-rolling-ament-pyflakes: 0.16.3-2 → 0.17.0-1
  • ros-rolling-ament-uncrustify: 0.16.3-2 → 0.17.0-1
  • ros-rolling-ament-xmllint: 0.16.3-2 → 0.17.0-1
  • ros-rolling-aruco-opencv: 4.1.1-2 → 4.2.0-1
  • ros-rolling-aruco-opencv-dbgsym: 4.1.1-2 → 4.2.0-1
  • ros-rolling-aruco-opencv-msgs: 4.1.1-2 → 4.2.0-1
  • ros-rolling-aruco-opencv-msgs-dbgsym: 4.1.1-2 → 4.2.0-1
  • ros-rolling-bicycle-steering-controller: 4.6.0-2 → 4.7.0-1
  • ros-rolling-bicycle-steering-controller-dbgsym: 4.6.0-2 → 4.7.0-1
  • ros-rolling-builtin-interfaces: 2.0.1-2 → 2.0.2-1
  • ros-rolling-builtin-interfaces-dbgsym: 2.0.1-2 → 2.0.2-1
  • ros-rolling-camera-calibration: 5.0.0-2 → 5.0.1-1
  • ros-rolling-camera-calibration-parsers: 5.1.0-2 → 5.1.2-1
  • ros-rolling-camera-calibration-parsers-dbgsym: 5.1.0-2 → 5.1.2-1
  • ros-rolling-camera-info-manager: 5.1.0-2 → 5.1.2-1
  • ros-rolling-camera-info-manager-dbgsym: 5.1.0-2 → 5.1.2-1
  • ros-rolling-canopen-interfaces: 0.2.8-2 → 0.2.9-1
  • ros-rolling-canopen-interfaces-dbgsym: 0.2.8-2 → 0.2.9-1
  • ros-rolling-canopen-utils: 0.2.8-2 → 0.2.9-1
  • ros-rolling-cartographer-ros-msgs: 2.0.9001-2 → 2.0.9003-1
  • ros-rolling-cartographer-ros-msgs-dbgsym: 2.0.9001-2 → 2.0.9003-1
  • ros-rolling-cascade-lifecycle-msgs: 1.0.3-5 → 2.0.0-1
  • ros-rolling-cascade-lifecycle-msgs-dbgsym: 1.0.3-5 → 2.0.0-1
  • ros-rolling-catch-ros2: 0.2.0-2 → 0.2.1-1
  • ros-rolling-catch-ros2-dbgsym: 0.2.0-2 → 0.2.1-1
  • ros-rolling-common-interfaces: 5.3.0-2 → 5.3.4-1
  • ros-rolling-composition: 0.33.1-2 → 0.33.2-1
  • ros-rolling-composition-dbgsym: 0.33.1-2 → 0.33.2-1
  • ros-rolling-composition-interfaces: 2.0.1-2 → 2.0.2-1
  • ros-rolling-composition-interfaces-dbgsym: 2.0.1-2 → 2.0.2-1
  • ros-rolling-compressed-depth-image-transport: 3.2.0-2 → 4.0.0-1
  • ros-rolling-compressed-depth-image-transport-dbgsym: 3.2.0-2 → 4.0.0-1
  • ros-rolling-compressed-image-transport: 3.2.0-2 → 4.0.0-1
  • ros-rolling-compressed-image-transport-dbgsym: 3.2.0-2 → 4.0.0-1
  • ros-rolling-control-msgs: 5.0.0-2 → 5.1.0-1
  • ros-rolling-control-msgs-dbgsym: 5.0.0-2 → 5.1.0-1
  • ros-rolling-controller-interface: 4.5.0-2 → 4.8.0-1
  • ros-rolling-controller-interface-dbgsym: 4.5.0-2 → 4.8.0-1
  • ros-rolling-controller-manager: 4.5.0-2 → 4.8.0-1
  • ros-rolling-controller-manager-dbgsym: 4.5.0-2 → 4.8.0-1
  • ros-rolling-controller-manager-msgs: 4.5.0-2 → 4.8.0-1
  • ros-rolling-controller-manager-msgs-dbgsym: 4.5.0-2 → 4.8.0-1
  • ros-rolling-cv-bridge: 3.4.0-3 → 4.0.0-1
  • ros-rolling-cv-bridge-dbgsym: 3.4.0-3 → 4.0.0-1
  • ros-rolling-demo-nodes-cpp: 0.33.1-2 → 0.33.2-1
  • ros-rolling-demo-nodes-cpp-dbgsym: 0.33.1-2 → 0.33.2-1
  • ros-rolling-demo-nodes-cpp-native: 0.33.1-2 → 0.33.2-1
  • ros-rolling-demo-nodes-cpp-native-dbgsym: 0.33.1-2 → 0.33.2-1
  • ros-rolling-demo-nodes-py: 0.33.1-2 → 0.33.2-1
  • ros-rolling-depth-image-proc: 5.0.0-2 → 5.0.1-1
  • ros-rolling-depth-image-proc-dbgsym: 5.0.0-2 → 5.0.1-1
  • ros-rolling-diagnostic-msgs: 5.3.0-2 → 5.3.4-1
  • ros-rolling-diagnostic-msgs-dbgsym: 5.3.0-2 → 5.3.4-1
  • ros-rolling-diff-drive-controller: 4.6.0-2 → 4.7.0-1
  • ros-rolling-diff-drive-controller-dbgsym: 4.6.0-2 → 4.7.0-1
  • ros-rolling-dummy-map-server: 0.33.1-2 → 0.33.2-1
  • ros-rolling-dummy-map-server-dbgsym: 0.33.1-2 → 0.33.2-1
  • ros-rolling-dummy-robot-bringup: 0.33.1-2 → 0.33.2-1
  • ros-rolling-dummy-sensors: 0.33.1-2 → 0.33.2-1
  • ros-rolling-dummy-sensors-dbgsym: 0.33.1-2 → 0.33.2-1
  • ros-rolling-effort-controllers: 4.6.0-2 → 4.7.0-1
  • ros-rolling-effort-controllers-dbgsym: 4.6.0-2 → 4.7.0-1
  • ros-rolling-examples-rclcpp-async-client: 0.19.1-2 → 0.19.3-1
  • ros-rolling-examples-rclcpp-async-client-dbgsym: 0.19.1-2 → 0.19.3-1
  • ros-rolling-examples-rclcpp-cbg-executor: 0.19.1-2 → 0.19.3-1
  • ros-rolling-examples-rclcpp-cbg-executor-dbgsym: 0.19.1-2 → 0.19.3-1
  • ros-rolling-examples-rclcpp-minimal-action-client: 0.19.1-2 → 0.19.3-1
  • ros-rolling-examples-rclcpp-minimal-action-client-dbgsym: 0.19.1-2 → 0.19.3-1
  • ros-rolling-examples-rclcpp-minimal-action-server: 0.19.1-2 → 0.19.3-1
  • ros-rolling-examples-rclcpp-minimal-action-server-dbgsym: 0.19.1-2 → 0.19.3-1
  • ros-rolling-examples-rclcpp-minimal-client: 0.19.1-2 → 0.19.3-1
  • ros-rolling-examples-rclcpp-minimal-client-dbgsym: 0.19.1-2 → 0.19.3-1
  • ros-rolling-examples-rclcpp-minimal-composition: 0.19.1-2 → 0.19.3-1
  • ros-rolling-examples-rclcpp-minimal-composition-dbgsym: 0.19.1-2 → 0.19.3-1
  • ros-rolling-examples-rclcpp-minimal-publisher: 0.19.1-2 → 0.19.3-1
  • ros-rolling-examples-rclcpp-minimal-publisher-dbgsym: 0.19.1-2 → 0.19.3-1
  • ros-rolling-examples-rclcpp-minimal-service: 0.19.1-2 → 0.19.3-1
  • ros-rolling-examples-rclcpp-minimal-service-dbgsym: 0.19.1-2 → 0.19.3-1
  • ros-rolling-examples-rclcpp-minimal-subscriber: 0.19.1-2 → 0.19.3-1
  • ros-rolling-examples-rclcpp-minimal-subscriber-dbgsym: 0.19.1-2 → 0.19.3-1
  • ros-rolling-examples-rclcpp-minimal-timer: 0.19.1-2 → 0.19.3-1
  • ros-rolling-examples-rclcpp-minimal-timer-dbgsym: 0.19.1-2 → 0.19.3-1
  • ros-rolling-examples-rclcpp-multithreaded-executor: 0.19.1-2 → 0.19.3-1
  • ros-rolling-examples-rclcpp-multithreaded-executor-dbgsym: 0.19.1-2 → 0.19.3-1
  • ros-rolling-examples-rclcpp-wait-set: 0.19.1-2 → 0.19.3-1
  • ros-rolling-examples-rclcpp-wait-set-dbgsym: 0.19.1-2 → 0.19.3-1
  • ros-rolling-examples-rclpy-executors: 0.19.1-2 → 0.19.3-1
  • ros-rolling-examples-rclpy-guard-conditions: 0.19.1-2 → 0.19.3-1
  • ros-rolling-examples-rclpy-minimal-action-client: 0.19.1-2 → 0.19.3-1
  • ros-rolling-examples-rclpy-minimal-action-server: 0.19.1-2 → 0.19.3-1
  • ros-rolling-examples-rclpy-minimal-client: 0.19.1-2 → 0.19.3-1
  • ros-rolling-examples-rclpy-minimal-publisher: 0.19.1-2 → 0.19.3-1
  • ros-rolling-examples-rclpy-minimal-service: 0.19.1-2 → 0.19.3-1
  • ros-rolling-examples-rclpy-minimal-subscriber: 0.19.1-2 → 0.19.3-1
  • ros-rolling-examples-rclpy-pointcloud-publisher: 0.19.1-2 → 0.19.3-1
  • ros-rolling-examples-tf2-py: 0.36.0-2 → 0.36.2-1
  • ros-rolling-fastcdr: 1.1.0-3 → 2.2.1-1
  • ros-rolling-fastcdr-dbgsym: 1.1.0-3 → 2.2.1-1
  • ros-rolling-fastrtps: 2.13.2-3 → 2.14.0-1
  • ros-rolling-fastrtps-cmake-module: 3.4.0-2 → 3.6.0-1
  • ros-rolling-fastrtps-dbgsym: 2.13.2-3 → 2.14.0-1
  • ros-rolling-ffmpeg-image-transport: 1.0.0-2 → 1.0.1-1
  • ros-rolling-ffmpeg-image-transport-dbgsym: 1.0.0-2 → 1.0.1-1
  • ros-rolling-filters: 2.1.0-5 → 2.1.2-1
  • ros-rolling-filters-dbgsym: 2.1.0-5 → 2.1.2-1
  • ros-rolling-force-torque-sensor-broadcaster: 4.6.0-2 → 4.7.0-1
  • ros-rolling-force-torque-sensor-broadcaster-dbgsym: 4.6.0-2 → 4.7.0-1
  • ros-rolling-forward-command-controller: 4.6.0-2 → 4.7.0-1
  • ros-rolling-forward-command-controller-dbgsym: 4.6.0-2 → 4.7.0-1
  • ros-rolling-generate-parameter-library: 0.3.7-3 → 0.3.8-3
  • ros-rolling-generate-parameter-library-py: 0.3.7-3 → 0.3.8-3
  • ros-rolling-geodesy: 1.0.5-2 → 1.0.6-1
  • ros-rolling-geographic-info: 1.0.5-2 → 1.0.6-1
  • ros-rolling-geographic-msgs: 1.0.5-2 → 1.0.6-1
  • ros-rolling-geographic-msgs-dbgsym: 1.0.5-2 → 1.0.6-1
  • ros-rolling-geometry-msgs: 5.3.0-2 → 5.3.4-1
  • ros-rolling-geometry-msgs-dbgsym: 5.3.0-2 → 5.3.4-1
  • ros-rolling-geometry2: 0.36.0-2 → 0.36.2-1
  • ros-rolling-gmock-vendor: 1.11.9000-2 → 1.14.9000-1
  • ros-rolling-google-benchmark-vendor: 0.4.0-2 → 0.5.0-1
  • ros-rolling-google-benchmark-vendor-dbgsym: 0.4.0-2 → 0.5.0-1
  • ros-rolling-gps-msgs: 1.0.4-5 → 2.0.3-1
  • ros-rolling-gps-msgs-dbgsym: 1.0.4-5 → 2.0.3-1
  • ros-rolling-gripper-controllers: 4.6.0-2 → 4.7.0-1
  • ros-rolling-gripper-controllers-dbgsym: 4.6.0-2 → 4.7.0-1
  • ros-rolling-gtest-vendor: 1.11.9000-2 → 1.14.9000-1
  • ros-rolling-hardware-interface: 4.5.0-2 → 4.8.0-1
  • ros-rolling-hardware-interface-dbgsym: 4.5.0-2 → 4.8.0-1
  • ros-rolling-hardware-interface-testing: 4.5.0-2 → 4.8.0-1
  • ros-rolling-hardware-interface-testing-dbgsym: 4.5.0-2 → 4.8.0-1
  • ros-rolling-image-common: 5.1.0-2 → 5.1.2-1
  • ros-rolling-image-geometry: 3.4.0-3 → 4.0.0-1
  • ros-rolling-image-geometry-dbgsym: 3.4.0-3 → 4.0.0-1
  • ros-rolling-image-pipeline: 5.0.0-2 → 5.0.1-1
  • ros-rolling-image-proc: 5.0.0-2 → 5.0.1-1
  • ros-rolling-image-proc-dbgsym: 5.0.0-2 → 5.0.1-1
  • ros-rolling-image-publisher: 5.0.0-2 → 5.0.1-1
  • ros-rolling-image-publisher-dbgsym: 5.0.0-2 → 5.0.1-1
  • ros-rolling-image-rotate: 5.0.0-2 → 5.0.1-1
  • ros-rolling-image-rotate-dbgsym: 5.0.0-2 → 5.0.1-1
  • ros-rolling-image-tools: 0.33.1-2 → 0.33.2-1
  • ros-rolling-image-tools-dbgsym: 0.33.1-2 → 0.33.2-1
  • ros-rolling-image-transport: 5.1.0-2 → 5.1.2-1
  • ros-rolling-image-transport-dbgsym: 5.1.0-2 → 5.1.2-1
  • ros-rolling-image-transport-plugins: 3.2.0-2 → 4.0.0-1
  • ros-rolling-image-view: 5.0.0-2 → 5.0.1-1
  • ros-rolling-image-view-dbgsym: 5.0.0-2 → 5.0.1-1
  • ros-rolling-imu-sensor-broadcaster: 4.6.0-2 → 4.7.0-1
  • ros-rolling-imu-sensor-broadcaster-dbgsym: 4.6.0-2 → 4.7.0-1
  • ros-rolling-interactive-markers: 2.5.3-2 → 2.5.4-1
  • ros-rolling-interactive-markers-dbgsym: 2.5.3-2 → 2.5.4-1
  • ros-rolling-intra-process-demo: 0.33.1-2 → 0.33.2-1
  • ros-rolling-intra-process-demo-dbgsym: 0.33.1-2 → 0.33.2-1
  • ros-rolling-joint-state-broadcaster: 4.6.0-2 → 4.7.0-1
  • ros-rolling-joint-state-broadcaster-dbgsym: 4.6.0-2 → 4.7.0-1
  • ros-rolling-joint-trajectory-controller: 4.6.0-2 → 4.7.0-1
  • ros-rolling-joint-trajectory-controller-dbgsym: 4.6.0-2 → 4.7.0-1
  • ros-rolling-keyboard-handler: 0.3.0-2 → 0.3.1-1
  • ros-rolling-keyboard-handler-dbgsym: 0.3.0-2 → 0.3.1-1
  • ros-rolling-lanelet2-core: 1.2.1-5 → 1.2.1-6
  • ros-rolling-lanelet2-core-dbgsym: 1.2.1-5 → 1.2.1-6
  • ros-rolling-lanelet2-io: 1.2.1-5 → 1.2.1-6
  • ros-rolling-lanelet2-io-dbgsym: 1.2.1-5 → 1.2.1-6
  • ros-rolling-lanelet2-maps: 1.2.1-5 → 1.2.1-6
  • ros-rolling-lanelet2-matching: 1.2.1-5 → 1.2.1-6
  • ros-rolling-lanelet2-matching-dbgsym: 1.2.1-5 → 1.2.1-6
  • ros-rolling-lanelet2-routing: 1.2.1-5 → 1.2.1-6
  • ros-rolling-lanelet2-routing-dbgsym: 1.2.1-5 → 1.2.1-6
  • ros-rolling-lanelet2-traffic-rules: 1.2.1-5 → 1.2.1-6
  • ros-rolling-lanelet2-traffic-rules-dbgsym: 1.2.1-5 → 1.2.1-6
  • ros-rolling-launch: 3.4.0-2 → 3.4.2-1
  • ros-rolling-launch-pytest: 3.4.0-2 → 3.4.2-1
  • ros-rolling-launch-ros: 0.26.4-2 → 0.26.5-1
  • ros-rolling-launch-testing: 3.4.0-2 → 3.4.2-1
  • ros-rolling-launch-testing-ament-cmake: 3.4.0-2 → 3.4.2-1
  • ros-rolling-launch-testing-examples: 0.19.1-2 → 0.19.3-1
  • ros-rolling-launch-testing-ros: 0.26.4-2 → 0.26.5-1
  • ros-rolling-launch-xml: 3.4.0-2 → 3.4.2-1
  • ros-rolling-launch-yaml: 3.4.0-2 → 3.4.2-1
  • ros-rolling-libcurl-vendor: 3.4.0-2 → 3.4.1-1
  • ros-rolling-libphidget22: 2.3.2-2 → 2.3.3-1
  • ros-rolling-libphidget22-dbgsym: 2.3.2-2 → 2.3.3-1
  • ros-rolling-libstatistics-collector: 1.7.0-2 → 1.7.1-1
  • ros-rolling-libstatistics-collector-dbgsym: 1.7.0-2 → 1.7.1-1
  • ros-rolling-libyaml-vendor: 1.6.2-2 → 1.6.3-1
  • ros-rolling-lifecycle: 0.33.1-2 → 0.33.2-1
  • ros-rolling-lifecycle-dbgsym: 0.33.1-2 → 0.33.2-1
  • ros-rolling-lifecycle-msgs: 2.0.1-2 → 2.0.2-1
  • ros-rolling-lifecycle-msgs-dbgsym: 2.0.1-2 → 2.0.2-1
  • ros-rolling-lifecycle-py: 0.33.1-2 → 0.33.2-1
  • ros-rolling-logging-demo: 0.33.1-2 → 0.33.2-1
  • ros-rolling-logging-demo-dbgsym: 0.33.1-2 → 0.33.2-1
  • ros-rolling-lttngpy: 8.0.0-2 → 8.2.0-1
  • ros-rolling-map-msgs: 2.4.0-2 → 2.4.1-1
  • ros-rolling-map-msgs-dbgsym: 2.4.0-2 → 2.4.1-1
  • ros-rolling-mcap-vendor: 0.24.0-3 → 0.26.1-1
  • ros-rolling-mcap-vendor-dbgsym: 0.24.0-3 → 0.26.1-1
  • ros-rolling-message-filters: 4.11.0-2 → 4.11.1-1
  • ros-rolling-message-filters-dbgsym: 4.11.0-2 → 4.11.1-1
  • ros-rolling-microstrain-inertial-driver: 3.2.1-2 → 4.2.0-1
  • ros-rolling-microstrain-inertial-driver-dbgsym: 3.2.1-2 → 4.2.0-1
  • ros-rolling-microstrain-inertial-examples: 3.2.1-2 → 4.2.0-1
  • ros-rolling-microstrain-inertial-msgs: 3.2.1-2 → 4.2.0-1
  • ros-rolling-microstrain-inertial-msgs-dbgsym: 3.2.1-2 → 4.2.0-1
  • ros-rolling-microstrain-inertial-rqt: 3.2.1-2 → 4.2.0-1
  • ros-rolling-mimick-vendor: 0.6.0-3 → 0.6.1-1
  • ros-rolling-mola-test-datasets: 0.3.0-2 → 0.3.1-1
  • ros-rolling-nao-lola: 1.2.0-2 → 1.3.0-1
  • ros-rolling-nao-lola-client: 1.2.0-2 → 1.3.0-1
  • ros-rolling-nao-lola-client-dbgsym: 1.2.0-2 → 1.3.0-1
  • ros-rolling-nao-lola-command-msgs: 1.2.0-2 → 1.3.0-1
  • ros-rolling-nao-lola-command-msgs-dbgsym: 1.2.0-2 → 1.3.0-1
  • ros-rolling-nao-lola-dbgsym: 1.2.0-2 → 1.3.0-1
  • ros-rolling-nao-lola-sensor-msgs: 1.2.0-2 → 1.3.0-1
  • ros-rolling-nao-lola-sensor-msgs-dbgsym: 1.2.0-2 → 1.3.0-1
  • ros-rolling-nav-msgs: 5.3.0-2 → 5.3.4-1
  • ros-rolling-nav-msgs-dbgsym: 5.3.0-2 → 5.3.4-1
  • ros-rolling-novatel-gps-msgs: 4.1.0-4 → 4.1.2-1
  • ros-rolling-novatel-gps-msgs-dbgsym: 4.1.0-4 → 4.1.2-1
  • ros-rolling-ntrip-client-node: 0.5.2-2 → 0.5.3-1
  • ros-rolling-ntrip-client-node-dbgsym: 0.5.2-2 → 0.5.3-1
  • ros-rolling-parameter-traits: 0.3.7-3 → 0.3.8-3
  • ros-rolling-pcl-conversions: 2.4.0-5 → 2.6.1-2
  • ros-rolling-pcl-ros: 2.4.0-5 → 2.6.1-2
  • ros-rolling-pendulum-control: 0.33.1-2 → 0.33.2-1
  • ros-rolling-pendulum-control-dbgsym: 0.33.1-2 → 0.33.2-1
  • ros-rolling-pendulum-msgs: 0.33.1-2 → 0.33.2-1
  • ros-rolling-pendulum-msgs-dbgsym: 0.33.1-2 → 0.33.2-1
  • ros-rolling-perception-pcl: 2.4.0-5 → 2.6.1-2
  • ros-rolling-phidgets-accelerometer: 2.3.2-2 → 2.3.3-1
  • ros-rolling-phidgets-accelerometer-dbgsym: 2.3.2-2 → 2.3.3-1
  • ros-rolling-phidgets-analog-inputs: 2.3.2-2 → 2.3.3-1
  • ros-rolling-phidgets-analog-inputs-dbgsym: 2.3.2-2 → 2.3.3-1
  • ros-rolling-phidgets-analog-outputs: 2.3.2-2 → 2.3.3-1
  • ros-rolling-phidgets-analog-outputs-dbgsym: 2.3.2-2 → 2.3.3-1
  • ros-rolling-phidgets-api: 2.3.2-2 → 2.3.3-1
  • ros-rolling-phidgets-api-dbgsym: 2.3.2-2 → 2.3.3-1
  • ros-rolling-phidgets-digital-inputs: 2.3.2-2 → 2.3.3-1
  • ros-rolling-phidgets-digital-inputs-dbgsym: 2.3.2-2 → 2.3.3-1
  • ros-rolling-phidgets-digital-outputs: 2.3.2-2 → 2.3.3-1
  • ros-rolling-phidgets-digital-outputs-dbgsym: 2.3.2-2 → 2.3.3-1
  • ros-rolling-phidgets-drivers: 2.3.2-2 → 2.3.3-1
  • ros-rolling-phidgets-gyroscope: 2.3.2-2 → 2.3.3-1
  • ros-rolling-phidgets-gyroscope-dbgsym: 2.3.2-2 → 2.3.3-1
  • ros-rolling-phidgets-high-speed-encoder: 2.3.2-2 → 2.3.3-1
  • ros-rolling-phidgets-high-speed-encoder-dbgsym: 2.3.2-2 → 2.3.3-1
  • ros-rolling-phidgets-ik: 2.3.2-2 → 2.3.3-1
  • ros-rolling-phidgets-magnetometer: 2.3.2-2 → 2.3.3-1
  • ros-rolling-phidgets-magnetometer-dbgsym: 2.3.2-2 → 2.3.3-1
  • ros-rolling-phidgets-motors: 2.3.2-2 → 2.3.3-1
  • ros-rolling-phidgets-motors-dbgsym: 2.3.2-2 → 2.3.3-1
  • ros-rolling-phidgets-msgs: 2.3.2-2 → 2.3.3-1
  • ros-rolling-phidgets-msgs-dbgsym: 2.3.2-2 → 2.3.3-1
  • ros-rolling-phidgets-spatial: 2.3.2-2 → 2.3.3-1
  • ros-rolling-phidgets-spatial-dbgsym: 2.3.2-2 → 2.3.3-1
  • ros-rolling-phidgets-temperature: 2.3.2-2 → 2.3.3-1
  • ros-rolling-phidgets-temperature-dbgsym: 2.3.2-2 → 2.3.3-1
  • ros-rolling-pluginlib: 5.4.1-2 → 5.4.2-1
  • ros-rolling-point-cloud-transport: 3.0.4-2 → 4.0.0-1
  • ros-rolling-point-cloud-transport-dbgsym: 3.0.4-2 → 4.0.0-1
  • ros-rolling-point-cloud-transport-py: 3.0.4-2 → 4.0.0-1
  • ros-rolling-position-controllers: 4.6.0-2 → 4.7.0-1
  • ros-rolling-position-controllers-dbgsym: 4.6.0-2 → 4.7.0-1
  • ros-rolling-pybind11-vendor: 3.1.1-2 → 3.1.2-1
  • ros-rolling-python-cmake-module: 0.11.0-2 → 0.11.1-1
  • ros-rolling-python-qt-binding: 2.1.1-2 → 2.2.0-1
  • ros-rolling-qt-dotgraph: 2.7.2-2 → 2.7.4-1
  • ros-rolling-qt-gui: 2.7.2-2 → 2.7.4-1
  • ros-rolling-qt-gui-app: 2.7.2-2 → 2.7.4-1
  • ros-rolling-qt-gui-core: 2.7.2-2 → 2.7.4-1
  • ros-rolling-qt-gui-cpp: 2.7.2-2 → 2.7.4-1
  • ros-rolling-qt-gui-cpp-dbgsym: 2.7.2-2 → 2.7.4-1
  • ros-rolling-qt-gui-py-common: 2.7.2-2 → 2.7.4-1
  • ros-rolling-quality-of-service-demo-cpp: 0.33.1-2 → 0.33.2-1
  • ros-rolling-quality-of-service-demo-cpp-dbgsym: 0.33.1-2 → 0.33.2-1
  • ros-rolling-quality-of-service-demo-py: 0.33.1-2 → 0.33.2-1
  • ros-rolling-range-sensor-broadcaster: 4.6.0-2 → 4.7.0-1
  • ros-rolling-range-sensor-broadcaster-dbgsym: 4.6.0-2 → 4.7.0-1
  • ros-rolling-rcl: 9.1.0-2 → 9.2.1-1
  • ros-rolling-rcl-action: 9.1.0-2 → 9.2.1-1
  • ros-rolling-rcl-action-dbgsym: 9.1.0-2 → 9.2.1-1
  • ros-rolling-rcl-dbgsym: 9.1.0-2 → 9.2.1-1
  • ros-rolling-rcl-interfaces: 2.0.1-2 → 2.0.2-1
  • ros-rolling-rcl-interfaces-dbgsym: 2.0.1-2 → 2.0.2-1
  • ros-rolling-rcl-lifecycle: 9.1.0-2 → 9.2.1-1
  • ros-rolling-rcl-lifecycle-dbgsym: 9.1.0-2 → 9.2.1-1
  • ros-rolling-rcl-logging-interface: 3.0.0-2 → 3.1.0-1
  • ros-rolling-rcl-logging-interface-dbgsym: 3.0.0-2 → 3.1.0-1
  • ros-rolling-rcl-logging-noop: 3.0.0-2 → 3.1.0-1
  • ros-rolling-rcl-logging-noop-dbgsym: 3.0.0-2 → 3.1.0-1
  • ros-rolling-rcl-logging-spdlog: 3.0.0-2 → 3.1.0-1
  • ros-rolling-rcl-logging-spdlog-dbgsym: 3.0.0-2 → 3.1.0-1
  • ros-rolling-rcl-yaml-param-parser: 9.1.0-2 → 9.2.1-1
  • ros-rolling-rcl-yaml-param-parser-dbgsym: 9.1.0-2 → 9.2.1-1
  • ros-rolling-rclcpp: 27.0.0-2 → 28.1.0-1
  • ros-rolling-rclcpp-action: 27.0.0-2 → 28.1.0-1
  • ros-rolling-rclcpp-action-dbgsym: 27.0.0-2 → 28.1.0-1
  • ros-rolling-rclcpp-cascade-lifecycle: 1.0.3-5 → 2.0.0-1
  • ros-rolling-rclcpp-cascade-lifecycle-dbgsym: 1.0.3-5 → 2.0.0-1
  • ros-rolling-rclcpp-components: 27.0.0-2 → 28.1.0-1
  • ros-rolling-rclcpp-components-dbgsym: 27.0.0-2 → 28.1.0-1
  • ros-rolling-rclcpp-dbgsym: 27.0.0-2 → 28.1.0-1
  • ros-rolling-rclcpp-lifecycle: 27.0.0-2 → 28.1.0-1
  • ros-rolling-rclcpp-lifecycle-dbgsym: 27.0.0-2 → 28.1.0-1
  • ros-rolling-rclpy: 7.0.1-2 → 7.1.1-1
  • ros-rolling-rcpputils: 2.10.0-2 → 2.11.0-1
  • ros-rolling-rcpputils-dbgsym: 2.10.0-2 → 2.11.0-1
  • ros-rolling-rcss3d-nao: 1.1.0-2 → 1.2.0-2
  • ros-rolling-rcss3d-nao-dbgsym: 1.1.0-2 → 1.2.0-2
  • ros-rolling-rcutils: 6.5.2-2 → 6.7.0-1
  • ros-rolling-rcutils-dbgsym: 6.5.2-2 → 6.7.0-1
  • ros-rolling-resource-retriever: 3.4.0-2 → 3.4.1-1
  • ros-rolling-resource-retriever-dbgsym: 3.4.0-2 → 3.4.1-1
  • ros-rolling-rmf-charging-schedule: 2.5.0-2 → 2.6.0-1
  • ros-rolling-rmf-task-ros2: 2.5.0-2 → 2.6.0-1
  • ros-rolling-rmf-task-ros2-dbgsym: 2.5.0-2 → 2.6.0-1
  • ros-rolling-rmf-traffic-ros2: 2.5.0-2 → 2.6.0-1
  • ros-rolling-rmf-traffic-ros2-dbgsym: 2.5.0-2 → 2.6.0-1
  • ros-rolling-rmf-websocket: 2.5.0-2 → 2.6.0-1
  • ros-rolling-rmf-websocket-dbgsym: 2.5.0-2 → 2.6.0-1
  • ros-rolling-rmw-connextdds: 0.20.1-1 → 0.22.0-1
  • ros-rolling-rmw-connextdds-common: 0.20.1-1 → 0.22.0-1
  • ros-rolling-rmw-connextdds-common-dbgsym: 0.20.1-1 → 0.22.0-1
  • ros-rolling-rmw-connextdds-dbgsym: 0.20.1-1 → 0.22.0-1
  • ros-rolling-rmw-cyclonedds-cpp: 2.1.0-2 → 2.2.0-1
  • ros-rolling-rmw-cyclonedds-cpp-dbgsym: 2.1.0-2 → 2.2.0-1
  • ros-rolling-rmw-dds-common: 3.0.0-2 → 3.1.0-1
  • ros-rolling-rmw-dds-common-dbgsym: 3.0.0-2 → 3.1.0-1
  • ros-rolling-rmw-fastrtps-cpp: 8.2.0-2 → 8.4.0-1
  • ros-rolling-rmw-fastrtps-cpp-dbgsym: 8.2.0-2 → 8.4.0-1
  • ros-rolling-rmw-fastrtps-dynamic-cpp: 8.2.0-2 → 8.4.0-1
  • ros-rolling-rmw-fastrtps-dynamic-cpp-dbgsym: 8.2.0-2 → 8.4.0-1
  • ros-rolling-rmw-fastrtps-shared-cpp: 8.2.0-2 → 8.4.0-1
  • ros-rolling-rmw-fastrtps-shared-cpp-dbgsym: 8.2.0-2 → 8.4.0-1
  • ros-rolling-rmw-implementation: 2.15.0-3 → 2.15.1-1
  • ros-rolling-rmw-implementation-dbgsym: 2.15.0-3 → 2.15.1-1
  • ros-rolling-ros2-control-test-assets: 4.5.0-2 → 4.8.0-1
  • ros-rolling-ros2-controllers-test-nodes: 4.6.0-2 → 4.7.0-1
  • ros-rolling-ros2action: 0.31.1-2 → 0.32.0-1
  • ros-rolling-ros2bag: 0.24.0-3 → 0.26.1-1
  • ros-rolling-ros2cli: 0.31.1-2 → 0.32.0-1
  • ros-rolling-ros2cli-test-interfaces: 0.31.1-2 → 0.32.0-1
  • ros-rolling-ros2cli-test-interfaces-dbgsym: 0.31.1-2 → 0.32.0-1
  • ros-rolling-ros2component: 0.31.1-2 → 0.32.0-1
  • ros-rolling-ros2controlcli: 4.5.0-2 → 4.8.0-1
  • ros-rolling-ros2doctor: 0.31.1-2 → 0.32.0-1
  • ros-rolling-ros2interface: 0.31.1-2 → 0.32.0-1
  • ros-rolling-ros2launch: 0.26.4-2 → 0.26.5-1
  • ros-rolling-ros2lifecycle: 0.31.1-2 → 0.32.0-1
  • ros-rolling-ros2lifecycle-test-fixtures: 0.31.1-2 → 0.32.0-1
  • ros-rolling-ros2lifecycle-test-fixtures-dbgsym: 0.31.1-2 → 0.32.0-1
  • ros-rolling-ros2multicast: 0.31.1-2 → 0.32.0-1
  • ros-rolling-ros2node: 0.31.1-2 → 0.32.0-1
  • ros-rolling-ros2param: 0.31.1-2 → 0.32.0-1
  • ros-rolling-ros2pkg: 0.31.1-2 → 0.32.0-1
  • ros-rolling-ros2run: 0.31.1-2 → 0.32.0-1
  • ros-rolling-ros2service: 0.31.1-2 → 0.32.0-1
  • ros-rolling-ros2topic: 0.31.1-2 → 0.32.0-1
  • ros-rolling-ros2trace: 8.0.0-2 → 8.2.0-1
  • ros-rolling-rosbag2: 0.24.0-3 → 0.26.1-1
  • ros-rolling-rosbag2-compression: 0.24.0-3 → 0.26.1-1
  • ros-rolling-rosbag2-compression-dbgsym: 0.24.0-3 → 0.26.1-1
  • ros-rolling-rosbag2-compression-zstd: 0.24.0-3 → 0.26.1-1
  • ros-rolling-rosbag2-compression-zstd-dbgsym: 0.24.0-3 → 0.26.1-1
  • ros-rolling-rosbag2-cpp: 0.24.0-3 → 0.26.1-1
  • ros-rolling-rosbag2-cpp-dbgsym: 0.24.0-3 → 0.26.1-1
  • ros-rolling-rosbag2-examples-cpp: 0.24.0-3 → 0.26.1-1
  • ros-rolling-rosbag2-examples-cpp-dbgsym: 0.24.0-3 → 0.26.1-1
  • ros-rolling-rosbag2-examples-py: 0.24.0-3 → 0.26.1-1
  • ros-rolling-rosbag2-interfaces: 0.24.0-3 → 0.26.1-1
  • ros-rolling-rosbag2-interfaces-dbgsym: 0.24.0-3 → 0.26.1-1
  • ros-rolling-rosbag2-performance-benchmarking: 0.24.0-3 → 0.26.1-1
  • ros-rolling-rosbag2-performance-benchmarking-msgs: 0.24.0-3 → 0.26.1-1
  • ros-rolling-rosbag2-py: 0.24.0-3 → 0.26.1-1
  • ros-rolling-rosbag2-storage: 0.24.0-3 → 0.26.1-1
  • ros-rolling-rosbag2-storage-dbgsym: 0.24.0-3 → 0.26.1-1
  • ros-rolling-rosbag2-storage-default-plugins: 0.24.0-3 → 0.26.1-1
  • ros-rolling-rosbag2-storage-mcap: 0.24.0-3 → 0.26.1-1
  • ros-rolling-rosbag2-storage-mcap-dbgsym: 0.24.0-3 → 0.26.1-1
  • ros-rolling-rosbag2-storage-sqlite3: 0.24.0-3 → 0.26.1-1
  • ros-rolling-rosbag2-storage-sqlite3-dbgsym: 0.24.0-3 → 0.26.1-1
  • ros-rolling-rosbag2-test-common: 0.24.0-3 → 0.26.1-1
  • ros-rolling-rosbag2-test-msgdefs: 0.24.0-3 → 0.26.1-1
  • ros-rolling-rosbag2-test-msgdefs-dbgsym: 0.24.0-3 → 0.26.1-1
  • ros-rolling-rosbag2-tests: 0.24.0-3 → 0.26.1-1
  • ros-rolling-rosbag2-transport: 0.24.0-3 → 0.26.1-1
  • ros-rolling-rosbag2-transport-dbgsym: 0.24.0-3 → 0.26.1-1
  • ros-rolling-rosgraph-msgs: 2.0.1-2 → 2.0.2-1
  • ros-rolling-rosgraph-msgs-dbgsym: 2.0.1-2 → 2.0.2-1
  • ros-rolling-rosidl-adapter: 4.5.1-2 → 4.6.0-1
  • ros-rolling-rosidl-cli: 4.5.1-2 → 4.6.0-1
  • ros-rolling-rosidl-cmake: 4.5.1-2 → 4.6.0-1
  • ros-rolling-rosidl-generator-c: 4.5.1-2 → 4.6.0-1
  • ros-rolling-rosidl-generator-cpp: 4.5.1-2 → 4.6.0-1
  • ros-rolling-rosidl-generator-py: 0.21.1-2 → 0.22.0-1
  • ros-rolling-rosidl-generator-type-description: 4.5.1-2 → 4.6.0-1
  • ros-rolling-rosidl-parser: 4.5.1-2 → 4.6.0-1
  • ros-rolling-rosidl-pycommon: 4.5.1-2 → 4.6.0-1
  • ros-rolling-rosidl-runtime-c: 4.5.1-2 → 4.6.0-1
  • ros-rolling-rosidl-runtime-c-dbgsym: 4.5.1-2 → 4.6.0-1
  • ros-rolling-rosidl-runtime-cpp: 4.5.1-2 → 4.6.0-1
  • ros-rolling-rosidl-runtime-py: 0.13.0-2 → 0.13.1-1
  • ros-rolling-rosidl-typesupport-c: 3.2.0-2 → 3.2.1-1
  • ros-rolling-rosidl-typesupport-c-dbgsym: 3.2.0-2 → 3.2.1-1
  • ros-rolling-rosidl-typesupport-cpp: 3.2.0-2 → 3.2.1-1
  • ros-rolling-rosidl-typesupport-cpp-dbgsym: 3.2.0-2 → 3.2.1-1
  • ros-rolling-rosidl-typesupport-fastrtps-c: 3.4.0-2 → 3.6.0-1
  • ros-rolling-rosidl-typesupport-fastrtps-c-dbgsym: 3.4.0-2 → 3.6.0-1
  • ros-rolling-rosidl-typesupport-fastrtps-cpp: 3.4.0-2 → 3.6.0-1
  • ros-rolling-rosidl-typesupport-fastrtps-cpp-dbgsym: 3.4.0-2 → 3.6.0-1
  • ros-rolling-rosidl-typesupport-interface: 4.5.1-2 → 4.6.0-1
  • ros-rolling-rosidl-typesupport-introspection-c: 4.5.1-2 → 4.6.0-1
  • ros-rolling-rosidl-typesupport-introspection-c-dbgsym: 4.5.1-2 → 4.6.0-1
  • ros-rolling-rosidl-typesupport-introspection-cpp: 4.5.1-2 → 4.6.0-1
  • ros-rolling-rosidl-typesupport-introspection-cpp-dbgsym: 4.5.1-2 → 4.6.0-1
  • ros-rolling-rqt: 1.5.0-2 → 1.6.0-1
  • ros-rolling-rqt-bag: 1.5.1-2 → 1.5.2-1
  • ros-rolling-rqt-bag-plugins: 1.5.1-2 → 1.5.2-1
  • ros-rolling-rqt-controller-manager: 4.5.0-2 → 4.8.0-1
  • ros-rolling-rqt-gauges: 0.0.2-2 → 0.0.3-1
  • ros-rolling-rqt-graph: 1.5.2-2 → 1.5.3-1
  • ros-rolling-rqt-gui: 1.5.0-2 → 1.6.0-1
  • ros-rolling-rqt-gui-cpp: 1.5.0-2 → 1.6.0-1
  • ros-rolling-rqt-gui-cpp-dbgsym: 1.5.0-2 → 1.6.0-1
  • ros-rolling-rqt-gui-py: 1.5.0-2 → 1.6.0-1
  • ros-rolling-rqt-image-view: 1.2.0-3 → 1.3.0-1
  • ros-rolling-rqt-image-view-dbgsym: 1.2.0-3 → 1.3.0-1
  • ros-rolling-rqt-joint-trajectory-controller: 4.6.0-2 → 4.7.0-1
  • ros-rolling-rqt-plot: 1.3.2-2 → 1.4.0-1
  • ros-rolling-rqt-publisher: 1.7.1-2 → 1.7.2-1
  • ros-rolling-rqt-py-common: 1.5.0-2 → 1.6.0-1
  • ros-rolling-rqt-shell: 1.2.1-2 → 1.2.2-1
  • ros-rolling-rqt-topic: 1.7.1-2 → 1.7.2-1
  • ros-rolling-rti-connext-dds-cmake-module: 0.20.1-1 → 0.22.0-1
  • ros-rolling-rviz-assimp-vendor: 13.4.0-2 → 14.1.0-1
  • ros-rolling-rviz-common: 13.4.0-2 → 14.1.0-1
  • ros-rolling-rviz-common-dbgsym: 13.4.0-2 → 14.1.0-1
  • ros-rolling-rviz-default-plugins: 13.4.0-2 → 14.1.0-1
  • ros-rolling-rviz-default-plugins-dbgsym: 13.4.0-2 → 14.1.0-1
  • ros-rolling-rviz-ogre-vendor: 13.4.0-2 → 14.1.0-1
  • ros-rolling-rviz-ogre-vendor-dbgsym: 13.4.0-2 → 14.1.0-1
  • ros-rolling-rviz-rendering: 13.4.0-2 → 14.1.0-1
  • ros-rolling-rviz-rendering-dbgsym: 13.4.0-2 → 14.1.0-1
  • ros-rolling-rviz-rendering-tests: 13.4.0-2 → 14.1.0-1
  • ros-rolling-rviz-visual-testing-framework: 13.4.0-2 → 14.1.0-1
  • ros-rolling-rviz2: 13.4.0-2 → 14.1.0-1
  • ros-rolling-rviz2-dbgsym: 13.4.0-2 → 14.1.0-1
  • ros-rolling-sensor-msgs: 5.3.0-2 → 5.3.4-1
  • ros-rolling-sensor-msgs-dbgsym: 5.3.0-2 → 5.3.4-1
  • ros-rolling-sensor-msgs-py: 5.3.0-2 → 5.3.4-1
  • ros-rolling-service-msgs: 2.0.1-2 → 2.0.2-1
  • ros-rolling-service-msgs-dbgsym: 2.0.1-2 → 2.0.2-1
  • ros-rolling-shape-msgs: 5.3.0-2 → 5.3.4-1
  • ros-rolling-shape-msgs-dbgsym: 5.3.0-2 → 5.3.4-1
  • ros-rolling-shared-queues-vendor: 0.24.0-3 → 0.26.1-1
  • ros-rolling-soccer-interfaces: 0.2.0-3 → 1.0.0-1
  • ros-rolling-soccer-vision-2d-msgs: 0.2.0-3 → 1.0.0-1
  • ros-rolling-soccer-vision-2d-msgs-dbgsym: 0.2.0-3 → 1.0.0-1
  • ros-rolling-soccer-vision-3d-msgs: 0.2.0-3 → 1.0.0-1
  • ros-rolling-soccer-vision-3d-msgs-dbgsym: 0.2.0-3 → 1.0.0-1
  • ros-rolling-soccer-vision-3d-rviz-markers: 0.0.1-3 → 1.0.0-1
  • ros-rolling-soccer-vision-attribute-msgs: 0.2.0-3 → 1.0.0-1
  • ros-rolling-soccer-vision-attribute-msgs-dbgsym: 0.2.0-3 → 1.0.0-1
  • ros-rolling-spdlog-vendor: 1.5.1-2 → 1.6.0-1
  • ros-rolling-sqlite3-vendor: 0.24.0-3 → 0.26.1-1
  • ros-rolling-statistics-msgs: 2.0.1-2 → 2.0.2-1
  • ros-rolling-statistics-msgs-dbgsym: 2.0.1-2 → 2.0.2-1
  • ros-rolling-std-msgs: 5.3.0-2 → 5.3.4-1
  • ros-rolling-std-msgs-dbgsym: 5.3.0-2 → 5.3.4-1
  • ros-rolling-std-srvs: 5.3.0-2 → 5.3.4-1
  • ros-rolling-std-srvs-dbgsym: 5.3.0-2 → 5.3.4-1
  • ros-rolling-steering-controllers-library: 4.6.0-2 → 4.7.0-1
  • ros-rolling-steering-controllers-library-dbgsym: 4.6.0-2 → 4.7.0-1
  • ros-rolling-stereo-image-proc: 5.0.0-2 → 5.0.1-1
  • ros-rolling-stereo-image-proc-dbgsym: 5.0.0-2 → 5.0.1-1
  • ros-rolling-stereo-msgs: 5.3.0-2 → 5.3.4-1
  • ros-rolling-stereo-msgs-dbgsym: 5.3.0-2 → 5.3.4-1
  • ros-rolling-test-msgs: 2.0.1-2 → 2.0.2-1
  • ros-rolling-test-msgs-dbgsym: 2.0.1-2 → 2.0.2-1
  • ros-rolling-tf2: 0.36.0-2 → 0.36.2-1
  • ros-rolling-tf2-bullet: 0.36.0-2 → 0.36.2-1
  • ros-rolling-tf2-dbgsym: 0.36.0-2 → 0.36.2-1
  • ros-rolling-tf2-eigen: 0.36.0-2 → 0.36.2-1
  • ros-rolling-tf2-eigen-kdl: 0.36.0-2 → 0.36.2-1
  • ros-rolling-tf2-eigen-kdl-dbgsym: 0.36.0-2 → 0.36.2-1
  • ros-rolling-tf2-geometry-msgs: 0.36.0-2 → 0.36.2-1
  • ros-rolling-tf2-kdl: 0.36.0-2 → 0.36.2-1
  • ros-rolling-tf2-msgs: 0.36.0-2 → 0.36.2-1
  • ros-rolling-tf2-msgs-dbgsym: 0.36.0-2 → 0.36.2-1
  • ros-rolling-tf2-py: 0.36.0-2 → 0.36.2-1
  • ros-rolling-tf2-py-dbgsym: 0.36.0-2 → 0.36.2-1
  • ros-rolling-tf2-ros: 0.36.0-2 → 0.36.2-1
  • ros-rolling-tf2-ros-dbgsym: 0.36.0-2 → 0.36.2-1
  • ros-rolling-tf2-ros-py: 0.36.0-2 → 0.36.2-1
  • ros-rolling-tf2-sensor-msgs: 0.36.0-2 → 0.36.2-1
  • ros-rolling-tf2-tools: 0.36.0-2 → 0.36.2-1
  • ros-rolling-theora-image-transport: 3.2.0-2 → 4.0.0-1
  • ros-rolling-theora-image-transport-dbgsym: 3.2.0-2 → 4.0.0-1
  • ros-rolling-topic-monitor: 0.33.1-2 → 0.33.2-1
  • ros-rolling-topic-statistics-demo: 0.33.1-2 → 0.33.2-1
  • ros-rolling-topic-statistics-demo-dbgsym: 0.33.1-2 → 0.33.2-1
  • ros-rolling-tracetools: 8.0.0-2 → 8.2.0-1
  • ros-rolling-tracetools-dbgsym: 8.0.0-2 → 8.2.0-1
  • ros-rolling-tracetools-image-pipeline: 5.0.0-2 → 5.0.1-1
  • ros-rolling-tracetools-image-pipeline-dbgsym: 5.0.0-2 → 5.0.1-1
  • ros-rolling-tracetools-launch: 8.0.0-2 → 8.2.0-1
  • ros-rolling-tracetools-read: 8.0.0-2 → 8.2.0-1
  • ros-rolling-tracetools-test: 8.0.0-2 → 8.2.0-1
  • ros-rolling-tracetools-trace: 8.0.0-2 → 8.2.0-1
  • ros-rolling-trajectory-msgs: 5.3.0-2 → 5.3.4-1
  • ros-rolling-trajectory-msgs-dbgsym: 5.3.0-2 → 5.3.4-1
  • ros-rolling-transmission-interface: 4.5.0-2 → 4.8.0-1
  • ros-rolling-transmission-interface-dbgsym: 4.5.0-2 → 4.8.0-1
  • ros-rolling-tricycle-controller: 4.6.0-2 → 4.7.0-1
  • ros-rolling-tricycle-controller-dbgsym: 4.6.0-2 → 4.7.0-1
  • ros-rolling-tricycle-steering-controller: 4.6.0-2 → 4.7.0-1
  • ros-rolling-tricycle-steering-controller-dbgsym: 4.6.0-2 → 4.7.0-1
  • ros-rolling-turtlesim: 1.8.1-2 → 1.8.2-1
  • ros-rolling-turtlesim-dbgsym: 1.8.1-2 → 1.8.2-1
  • ros-rolling-type-description-interfaces: 2.0.1-2 → 2.0.2-1
  • ros-rolling-type-description-interfaces-dbgsym: 2.0.1-2 → 2.0.2-1
  • ros-rolling-ublox-dgnss: 0.5.2-2 → 0.5.3-1
  • ros-rolling-ublox-dgnss-node: 0.5.2-2 → 0.5.3-1
  • ros-rolling-ublox-dgnss-node-dbgsym: 0.5.2-2 → 0.5.3-1
  • ros-rolling-ublox-nav-sat-fix-hp-node: 0.5.2-2 → 0.5.3-1
  • ros-rolling-ublox-nav-sat-fix-hp-node-dbgsym: 0.5.2-2 → 0.5.3-1
  • ros-rolling-ublox-ubx-interfaces: 0.5.2-2 → 0.5.3-1
  • ros-rolling-ublox-ubx-interfaces-dbgsym: 0.5.2-2 → 0.5.3-1
  • ros-rolling-ublox-ubx-msgs: 0.5.2-2 → 0.5.3-1
  • ros-rolling-ublox-ubx-msgs-dbgsym: 0.5.2-2 → 0.5.3-1
  • ros-rolling-uncrustify-vendor: 2.2.1-2 → 3.0.0-1
  • ros-rolling-ur-calibration: 2.4.3-2 → 2.4.4-1
  • ros-rolling-ur-calibration-dbgsym: 2.4.3-2 → 2.4.4-1
  • ros-rolling-ur-client-library: 1.3.5-2 → 1.3.6-1
  • ros-rolling-ur-client-library-dbgsym: 1.3.5-2 → 1.3.6-1
  • ros-rolling-ur-controllers: 2.4.3-2 → 2.4.4-1
  • ros-rolling-ur-controllers-dbgsym: 2.4.3-2 → 2.4.4-1
  • ros-rolling-ur-dashboard-msgs: 2.4.3-2 → 2.4.4-1
  • ros-rolling-ur-dashboard-msgs-dbgsym: 2.4.3-2 → 2.4.4-1
  • ros-rolling-ur-description: 2.2.4-2 → 2.2.5-1
  • ros-rolling-ur-robot-driver: 2.4.3-2 → 2.4.4-1
  • ros-rolling-ur-robot-driver-dbgsym: 2.4.3-2 → 2.4.4-1
  • ros-rolling-velocity-controllers: 4.6.0-2 → 4.7.0-1
  • ros-rolling-velocity-controllers-dbgsym: 4.6.0-2 → 4.7.0-1
  • ros-rolling-vision-opencv: 3.4.0-3 → 4.0.0-1
  • ros-rolling-visualization-msgs: 5.3.0-2 → 5.3.4-1
  • ros-rolling-visualization-msgs-dbgsym: 5.3.0-2 → 5.3.4-1
  • ros-rolling-vrpn: 7.35.0-14 → 7.35.0-15
  • ros-rolling-webots-ros2-importer: 2023.1.1-3 → 2023.1.2-1
  • ros-rolling-webots-ros2-msgs: 2023.1.1-3 → 2023.1.2-1
  • ros-rolling-webots-ros2-msgs-dbgsym: 2023.1.1-3 → 2023.1.2-1
  • ros-rolling-xacro: 2.0.10-2 → 2.0.11-1
  • ros-rolling-yaml-cpp-vendor: 8.3.1-2 → 9.0.0-1
  • ros-rolling-zbar-ros: 0.4.0-3 → 0.5.0-1
  • ros-rolling-zbar-ros-dbgsym: 0.4.0-3 → 0.5.0-1
  • ros-rolling-zstd-vendor: 0.24.0-3 → 0.26.1-1

Removed Packages [24]:

Thanks to all ROS maintainers who make packages available to the ROS community. The above list of packages was made possible by the work of the following maintainers:

  • Addisu Taddese
  • Addisu Z. Taddese
  • Aditya Pande
  • Alejandro Hernandez Cordero
  • Alejandro Hernández
  • Alexander Gutenkunst
  • Alvin Sun
  • Andrea Sorbini
  • Anthony Baker
  • Apex AI, Inc.
  • Armin Hornung
  • Audrow Nash
  • Bence Magyar
  • Bernd Pfrommer
  • Blake Anderson
  • Brandon Ong
  • Chittaranjan Srinivas Swaminathan
  • Chris Lalancette
  • Christian Henkel
  • Christoph Hellmann Santos
  • Christoph Sprunk
  • Christophe Bedard
  • Cyberbotics
  • Daniel Stonier
  • Dave Coleman
  • David V. Lu!!
  • Denis Stogl
  • Denis Štogl
  • Dharini Dutia
  • Dirk Thomas
  • Dorian Scholz
  • Eloy Bricneo
  • Emerson Knapp
  • Erik Boasson
  • Fabian Immel
  • Felix Exner
  • Felix Ruess
  • Fictionlab
  • Foxglove
  • Francisco Martin Rico
  • Francois Pomerleau
  • Geoff Sokoll
  • Geoffrey Biggs
  • Gonzalo Mier
  • Grey
  • Henning Kayser
  • Ivan Paunovic
  • Jack O’Quin
  • Jacob Perron
  • John D’Angelo
  • Jose-Luis Blanco-Claraco
  • Joseph Mirabel
  • José Luis Blanco-Claraco
  • Kenji Brameld
  • Kenji Miyake
  • Laura Lindzey
  • Lennart Reiher
  • Luis Camero
  • Mabel Zhang
  • Martin Günther
  • Michael Carroll
  • Michael Ferguson
  • Michael Görner
  • Michael Orlov
  • Miguel Company
  • MoveIt Release Team
  • Nick Hortovanyi
  • Nick Morales
  • P. J. Reed
  • Paul Bovbel
  • Paul Gesel
  • Peter David Fagan
  • ROS Tooling Working Group
  • Rob Fisher
  • Robert Haschke
  • Scott K Logan
  • Shane Loretz
  • Stéphane Magnenat
  • TRACLabs Robotics
  • Team Spatzenhirn
  • Tully Foote
  • Tyler Weaver
  • Vincent Rabaud
  • Víctor Mayoral-Vilches
  • William Woodall
  • Wolfgang Merkt
  • Yadunund
  • fmrico
  • geoff
  • ijnek
  • methylDragon
  • michael
  • paul

1 post - 1 participant

Read full topic

[WWW] https://discourse.ros.org/t/new-packages-for-ros-2-rolling-ridley-2024-04-17/37252

ROS Discourse General: Arab Meetup

Exciting news! We’re gearing up for our fourth session of the first workshop, and it’s all about diving into the world of Git and Vscode. :rocket:

✅Version Control (GIT): Learn how to effectively track and manage changes in your robot project using Git.

▶Git’s data model: Understand the graphical data model of Git and how it operates.

â–¶Git command-line interface Basics: Master the basics of using Git via the command line.

â–¶Branching and merging: Explore the processes of branching and merging in Git.

â–¶Remotes: Get acquainted with remote repositories and how to interact with them in Git.

â–¶Undo: Learn the commands for undoing changes in Git.

✅VSCode: Install and utilize the popular development environment VSCode for advanced robot programming.

â–¶Install VScode using terminal: Step-by-step guide on installing VSCode using the terminal.

▶VSCode important extensions (ros, urdf, …): Discover key extensions in VSCode relevant to robot programming.

â–¶GitHub on VSCode: Harness the power of GitHub directly within VSCode.

â–¶Shortcuts for text editing: Handy shortcuts for faster and more efficient text editing in VSCode.

💡You can find the meeting link here:
https://buff.ly/49bQOA8

image

1 post - 1 participant

Read full topic

[WWW] https://discourse.ros.org/t/arab-meetup/37242

ROS Discourse General: New Tutorial: Creating Custom RViz Displays

Hey ROStronauts,
Here’s a new tutorial on How to Build a Custom RViz Display!

You can use this tutorial to display new types of ROS Messages in RViz, which I’ve used in the polygon_ros repo, or for useless things like the snowbot_operating_system

If you have any issues, open them on the Github repo: GitHub - MetroRobots/rviz_plugin_tutorial: A tutorial on how to make rviz plugins

-David!!

1 post - 1 participant

Read full topic

[WWW] https://discourse.ros.org/t/new-tutorial-creating-custom-rviz-displays/37225

ROS Discourse General: SAVE THE DATE: Jazzy Jalisco Testing and Tutorial Party 2024-05-01

SAVE THE DATE: Jazzy Jalisco Testing and Tutorial Party, 2024-05-01T16:00:00Z UTC


Jazzy Jalsico (1)


As many of you are already aware, the ROS Jazzy Jalisco release is just around the corner: 2024-05-23T18:00:00Z UTC, to be exact! We want this to be our best ROS 2 release yet, and to get there we need to make sure that we thoroughly test Jazzy before it is released to the general public. We also want to make sure that the ROS documentation on docs.ros.org continues to be clear, concise, and correct. That’s where we need your help! We’re looking for community volunteers to join us for our annual ROS Testing and Tutorial Party. If you are looking to start dipping your toes into ROS development this is a great place to start.

Following the Gazebo team’s successfull history of tutorial parties, and the results from last year’s Iron Irwini Tutorial Party, we’re bringing back the tutorial party of ROS 2 Jazzy Jalisco. We want to replicate for Jazzy the success we had with the Iron Irwini Testing and Tutorial Party. So, what is a testing and tutorial party you may ask? Well, it is a chance for the community to meet and systematically review all of the current ROS tutorials while also testing the latest ROS release. What we attempt to do at the party is to test every ROS tutorial for every “flavor” of ROS user, or in other words, every combination of operating system (Ubuntu Linux, RedHat Linux, Windows, etc.), RMW implementation (FastDDS, Cyclone DDS, etc.), installation method, and CPU architecture (amd64, aarch64, etc.).

Now that we’ve frozen the Jazzy release, the core developer team is working on generating a set of “early release” binary and source packages for Jazzy Jalisco. We plan to make these pre-release binaries publicly available before the Testing and Tutorial Party. During the party we’ll release our testing repository with a long list of tests we would like to run on the testing version of Jazzy Jalisco. These tests will first ask contributors to pick a particular release “setup”, and then run either the test suite or work through one or more of the existing ROS 2 tutorials on docs.ros.org. Each “setup” is a specific combination of RMW vendor (FastDDS/Cyclone DDS/Connext DDS), build type (binary tarball/packages/source), host operating system (Ubuntu Nobel/RHEL-9/Windows), and architecture (amd64/aarch64). For each setup, we would like to perform a number of tests that validate our tutorials, core ROS functionality, and important features. With dozens possible setup configurations, testing each and every one internally just isn’t feasible. To ensure reproducibility of the tests it’s also valuable to get multiple evaluations of each test, which is why we need your help!

Tutorial party participants are asked to perform the tests they sign up for and report back the results. If you happen to find an issue or bug while participating in the tutorial party you’ll need to report it to us so it can get corrected before the Jazzy release.

We are planning to kick-off the tutorial party off at 2024-05-01T16:00:00Z UTC with a meeting where we explain the whole Testing and Tutorial Party Process. That meeting can be found on the OSRF Official Events Calendar. We’ll record the meeting and post instructions on Discourse for those who can’t make the meeting. To help motivate participants, we will be giving away ROS Jazzy Jalisco swag to the testers who complete the most tests during the tutorial party. Every time you complete a test or tutorial you will need to close the Github issue, and then fill out a short Google form. The Testing and Tutorial party participants with the most completed tests during the tutorial party will receive a credit to Zazzle to pick out some Jazzy swag. We’ll post more details about the tutorial party in about two weeks when we kick things off. For now, we’re outlining a rough sequence of events so everyone can set aside some time to participate. Here are the key dates you’ll want to remember:

  • 2024-05-01T07:00:00Z UTC Tutorial & Testing Party begins Jazzy Jalisco
  • 2024-05-01T16:00:00Z UTC Tutorial & Testing Party Hangout + Q&A
  • 2024-05-08T07:00:00Z UTC ROS 2 Jazzy Jalisco logo and swag sale begins (tentative)
  • 2024-05-15T07:00:00Z UTC Tutorial and Testing Party ends
  • 2024-05-23T07:00:00Z UTC ROS 2 Jazzy Jalisco released

We have added these events to the OSRF Official Events Calendar, but the big one that you won’t want to miss is the kick-off event on 2024-05-01T16:00:00Z UTC. At this tutorial party kickoff meeting we’ll walk everyone through the steps involved in participation. In the meantime we would like your help spreading the word about the Testing and Tutorial Party. We hope to see you there on May 1st!

Finally, if you would like to help support Open Robotics, and events like these, consider making a donation or joining the OSRA.

15 posts - 7 participants

Read full topic

[WWW] https://discourse.ros.org/t/save-the-date-jazzy-jalisco-testing-and-tutorial-party-2024-05-01/37155

ROS Discourse General: Freeze of ROS 2 Base Packages, Upcoming Branch, and Tutorial Party for Jazzy Jalisco

Hello everyone,

:snowflake: :snowflake: :snowflake:
As we reach the end of today 15 April 2024 (2359 PST), all rolling branches on all ROS 2 base packages will be frozen . This is to branch into jazzy from rolling in preparation for the the upcoming release on 23rd May.

We will begin branching into jazzy over the course of this week to help ensure that the jazzy pre-release packages are available for testing during the Tutorial Party (as we did for the Iron Tutorial Party), this time happening on 1st of May. On that note, we hope to get even more community members to partake in the tutorial party and support the testing efforts!

Kind request to all base package maintainers to enforce the freeze after today by no longer merging any changes into rolling until further notice. Once the branching is complete, we will unfreeze rolling so that feature and API changes can be merged in once again. Stay tuned for that announcement on Discourse.

You may find more information on the Jazzy Jalisco release timeline here: ROS 2 Jazzy Jalisco (codename ‘jazzy’; May, 2024) .

2 posts - 2 participants

Read full topic

[WWW] https://discourse.ros.org/t/freeze-of-ros-2-base-packages-upcoming-branch-and-tutorial-party-for-jazzy-jalisco/37191

ROS Discourse General: Introducing flywheel: an easy to use remote teleop for ROS robots

Hi everyone, I recently have been working on flywheel (https://app.flywheelrobotics.com), which lets you visualize and control your robots remotely over the internet.

flywheel_webapp_peak

It is free to use and can be installed on any robot, either using ROS 1 or ROS 2.

Apart from techniques like UMI gripper and kinesthesis, I think teleoperation can be a good way to collect datasets and incorporate edges cases handling into autonomy, and that’s where flywheel can be quite useful.

1 post - 1 participant

Read full topic

[WWW] https://discourse.ros.org/t/introducing-flywheel-an-easy-to-use-remote-teleop-for-ros-robots/37150

ROS Discourse General: Release (v1.0.0) - A full-fledged light weight traversability mapping library which can seamlessly be integrated with any SLAM system!

Hello everyone!

At the beginning of this year I had started this fun project. A global traversability mapping library which generates 3D traversability maps with 3D Pointclouds. This can be seamlessly integrated with any SLAM (Visual or LiDAR based) to generate a global map in real-time simply by providing a constant stream of Pointclouds along with the KeyFrame Poses.
This library also seamlessly handles loop closing and optimization of keyframe poses from the SLAM. I started writing this with ORB-SLAM3 as the backend so as a plus point, this also has the feature to merge multiple traversability maps into one in case there is a loss of tracking and a new local map is made.
I’m so pleased to release this as an open-source project. Hope this is useful to you all :smiley:
Here is the link for the code and instructions to use: https://github.com/suchetanrs/traversability_mapping
map

11 posts - 4 participants

Read full topic

[WWW] https://discourse.ros.org/t/release-v1-0-0-a-full-fledged-light-weight-traversability-mapping-library-which-can-seamlessly-be-integrated-with-any-slam-system/37148

ROS Discourse General: Simulate Mobile Aloha in Gazebo

AgileX simulated Mobile Aloha in Gazebo :clap:

aloha

Project environment

ubuntu 20.04

ros noetic

gazebo version 11

Compile

Run the commands in order.

mkdir src
cd src
git clone https://github.com/agilexrobotics/mobile_aloha_sim
cd ..
catkin_make

File directory

The file directory is shown below.

├── aloha_description
│   ├── aloha
│   ├── arx5_description
│   ├── arx5-urdf
│   │   ├── arx5
│   │   └── arx5p2
│   ├── livox_laser_simulation
│   └── tracer
│       ├── image
│       ├── tracer_description
│       └── tracer_gazebo_sim
├── aloha_mujoco
|   └── aloha
|       ├── CMakeLists.txt
|       ├── meshes_mujoco
|       │   ├── aloha_v1.xml
|       │   └── meshes_mujoco
|       ├── package.xml
|       └── scripts
|           ├── aloha_ctrl.py
|           └── aloha_ctrl_test.py
├── arx5_moveit_config
│   ├── config
│   └── launch
└── doc

Among them, aloha_mujoco is the implementation under mujoco simulation. For details, please refer to the aloha_mujoco folder.README

Start Gazebo

Start gazebo simulation

Run the command:

roslaunch arx5_moveit_config demo_gazebo.launch

You can see a mobile aloha model.

aloha_gazebo

aloha_rviz

Gazebo introduction

After starting the gazebo simulation, there are two windows, one is the gazebo physical simulation window, and the other is the rviz window. In the rviz window, the moveit component can be called to plan the robotic arm.

In the gazebo simulation window, the right side of the screen displays the real-time physical simulation environment. The position information and kinematic simulation information of the robotic arm are displayed here. Gazebo will also feedback the simulated robotic arm status and execute the control angle sent by the planner.

In the rviz simulation window, the UI interface of the moveit component is displayed on the lower left side. Here you can select different planning groups (Planning Group) to control different robotic arms and grippers. The right window displays the real-time robot arm position, which is provided by gazebo simulation.

Move the mobile base

rosrun teleop_twist_keyboard teleop_twist_keyboard.py

This is to start the mobile base control node. You can control the mobile base movement by sending the velocity.

Move the robotic arm

Drag the ‘teaching ball’ in the rviz interface and operate as shown in the figure. The robot arm will calculate the joint angle and robot arm trajectory based on the target end gripper position.

aloha_moveit_1

Note: After clicking Plan to start planning, the system takes time to calculate. When the Execute button changes from gray to black, click to execute the trajectory just planned.

Rviz simulation

The only difference between rviz simulation and gazebo simulation is that the physics simulation engine gazebo is not started, but only the data visualization platform rviz is started.

roslaunch arx5_moveit_config demo.launch

After startup, it will be the same as the rviz interface in gazebo simulation, just follow the above steps.

2 posts - 2 participants

Read full topic

[WWW] https://discourse.ros.org/t/simulate-mobile-aloha-in-gazebo/37144

ROS Discourse General: ROS News for the Week of April 8th, 2024

ROS News for the Week of April 8th, 2024

2024 RBR50 Highlights

The Robot Reports RBR 50 awards came out this week!. It is always interesting to see all of the new robotics companies and technologies. By my count close to half of the listed organizations use ROS.



Clearpath Robotics CTO, Open Robotics Board member, and all around cool dude Ryan Gariepy was on the ROS Developers Podcast to discuss the motivation behind the formation of the OSRA and what it means for the projects.


image

The ROS 2 Jazzy Jalisco feature freeze is next Monday, 2024-04-15T07:00:00Z UTC. If you have a pull request you want merged it is now or never. We’ll have full details about the release process, including our annual tutorial party, next week.

(I have succumb to using AI images, this one was from Bard, or Gemini, or whatever they call it now, The real Jazzy Jalisco distro graphic will come out in a couple of weeks).


image

Check out this article I came across this week, “Efficient Global Navigational Planning in 3D Structures based on Point Cloud Tomography”. The author uses the PCT Planner to navigation in complex multi-level environments. The best part? There is a ROS Noetic wrapper! I know a lot of people struggle with 3D / 2.5D path planning, so I wanted to pass this information along.


Events

News

ROS

Got a minute?

Why not send docs.ros.org a pull request? We could really use more contributors.

1 post - 1 participant

Read full topic

[WWW] https://discourse.ros.org/t/ros-news-for-the-week-of-april-8th-2024/37128

ROS Industrial: Open Source Improvements from Recently Completed Robotic Blending M5

A Focused Technical Project (FTP), championed by the Steel Founders’ Society of America (SFSA), sponsored by the DLA-Troop Support, Philadelphia, PA, and the Defense Logistics Agency Information Operations, J68, Research & Development, Ft. Belvoir, VA, within the ROS-Industrial Consortium (RIC), has recently completed the Focused Technical Project (FTP) Robotic Blending Milestone 5. The team included RIC team members consisting of Yaskawa America, PushCorp and Southwest Research Institute, along with SFSA member university, Iowa State University. This work culminated in a deployed system at a SFSA member foundry site.

The project built on the prior Robotic Blending Milestone 4, which demonstrated high-mix material surface finishing and edge processing of arbitrarily shaped and contouring parts, largely targeting piece-parts to be welded. This work sought to extend that work, adding new features and incorporating additional SFSA funded work to realize human in the loop high-mix casting finishing for foundry operations.

During the development process, we have contributed the following improvements to the foundational Scan-N-Plan framework that served as a starting point for the FTP. This framework is maintained as a workshop repository within the RIC GitHub repository and is used in whole or in parts for developer instruction in ROS 2 for industrial robotics.

Scan-N-Plan Updates

ROS 2 Control:

We have added ros2_control code to the Scan-N-Plan example implementations to preview the robot’s motion during a simulated motion execution.

Constant TCP Velocity Time Parameterization:

We have added a time parameterization algorithm for maintaining constant TCP speed during motion planning. The approach works by first calculating forward kinematics at each trajectory waypoint to get the pose of the TCP. Then, we create a line path between adjacent TCP poses and parameterize the line with a trapezoidal velocity profile. The joint velocity and acceleration at each waypoint are computed given the TCP Cartesian velocity and acceleration. These obtained velocities and accelerations are then validated to be within the limits of the robot.

Docker Images:

To make the deployment and development of Scan-N-Plan more efficient and standardized, we have created Docker images for ROS 2 Foxy, Humble, and Rolling that can be found here.

Selectable Representation for Collision Object:

In addition to the default behavior of converting the scan mesh into a convex hull, the collision object can now be represented as a detailed mesh or as an octree.

Default behavior: Converts the scan mesh into a convex hull. This generally results in the fastest motion plans, especially with TrajOpt, but can be too conservative and may cause motion planning failures if the scan object is not actually convex or nearly convex.

Convex Hull Representation of Collision Object

Mesh: Represents the collision object as the exact “detailed” mesh represented by the mesh file. With the contact test type CLOSEST for TrajOpt, this representation results in a somewhat slower planning time than convex_mesh, but not significantly longer.

Mesh Representation of Collision Object

Octree: Represents the collision object as an octree comprised of spheres with a diameter specified by the octree_resolution parameter. With the contact test type CLOSEST for TrajOpt, this representation results in slightly faster planning times than mesh but slower than convex_mesh.

Octree Representation of Collision Object

Simplified Raster Planner

Simplified Raster Planner Widget

The parameters exposed in the raster planner GUI widget were modified to only show commonly tuned parameters during raster planning such as rotation offset (degrees), point spacing, line spacing, minimum segment length. This declutters the raster planner to improve usability.

Python Scanning and Execution Nodes

For ease of development and debugging during deployment efforts, we have converted the mesh reconstruction and motion execution simulator nodes from C++ to Python.

Service for Generating Scan Motion Plans

A separate service for generating scan motion plans has been made as an intermediate step to support creating dynamic scan trajectories in the future. This service will be called to create scan trajectory patterns that originate from a specified starting location.

Behavior Tree and Reactive GUI

The custom application back-end logic has been replaced with a behavior tree to improve workflow modularity and customizability. The behavior tree can change the GUI appearance based on the current behavior executed. Widgets are exposed and hidden during the workflow to guide the user’s focus to actions and settings relevant to the process at hand. A progress bar and preview motion bar have been made more accessible to inform the user where they are in the process.

Noether Updates

Tool path and Mesh Visualization Tool

Mesh/Tool path Viewer Widget

When developing and debugging tool path and mesh modifiers, it is helpful to visualize the original tool path, the modified tool path, the original mesh, and the modified mesh. Previously, there was no way to view the unmodified sub-mesh after applying a mesh modifier.

We have added a widget in the Noether application to toggle the view of the mesh and tool path VTK objects. We replaced the concatenated mesh viewer using a vtkAssembly and using vtkSmartPointers instead of using raw pointers for internal objects.

From Left to Right: Modified Tool path and Modified Mesh, Modified Tool path and Original Mesh, Original Tool path and Original Mesh, Tool path Hidden and Modified Mesh

Approach and Departure Tool Paths

To better stay within selected regions during processing, we added linear approach and departure tool paths (see below for the linear approach tool path). A modified version of these tool paths (circular approach/departure) creates an approach/departure curve of specified radius.

Linear approach tool path modifier

Plane Projection Mesh Modifier

We added a mesh modifier that fits a plane to the input mesh using random sample consensus and projects the inlier points onto the plane. This modifier prevents tool paths from being generated on an unintended inner or outer surface near the edge of a complex part, where the desired processing surface should be flat.

We hope developers and those interested in experimenting with ROS 2 for their industrial robotics application development have found this resource helpful. If you have questions, comments, or have observed an issue, please do not hesitate to either engage with the ROS-Industrial community or leave an issue over at the GitHub repository.

Thanks to Michael Ripperger, ROS-I Consortium Americas Tech Lead, SwRI Sr. Research Engineer, for his contributions to the Scan-N-Plan Workshop and the FTP program and this blog post.

[WWW] https://rosindustrial.org/news/2024/4/12/open-source-improvements-from-recently-completed-robotic-blending-m5

ROS Discourse General: Released v1.0.0. FreeCAD - OVERCROSS (generating ROS 2 package by CAD)

FreeCAD OVERCROSS
is a fork of FreeCAD CROSS.

Main additions of OVERCROSS are:

  1. Material selection of link or whole robot
  2. Auto calculation of mass and inertia
  3. Launcher for Gazebo
  4. New some icons and icons reordering
  5. Bug fixes
  6. Others

5 posts - 2 participants

Read full topic

[WWW] https://discourse.ros.org/t/released-v1-0-0-freecad-overcross-generating-ros-2-package-by-cad/37127

ROS Discourse General: Client Library WG meeting April 12 2024

Hi, just a reminder that tomorrow we will have a meeting of the Client Library Working Group.

This is the last meeting before the Jazzy feature freeze.
So again the focus will be on PR and backlog review.

We will meet at 8AM Pacific Time.
Find here the Meeting Link https://meet.google.com/oij-atzj-znw

1 post - 1 participant

Read full topic

[WWW] https://discourse.ros.org/t/client-library-wg-meeting-april-12-2024/37115

ROS Discourse General: New Packages for Noetic 2024-04-11

We’re happy to announce 2 new packages and 42 updates are now available in ROS Noetic. This sync was tagged as noetic/2024-04-11.

Thank you to every maintainer and contributor who made these updates available!

Package Updates for ROS Noetic

Added Packages [2]:

Updated Packages [42]:

Removed Packages [0]:

Thanks to all ROS maintainers who make packages available to the ROS community. The above list of packages was made possible by the work of the following maintainers:

  • Atsushi Watanabe
  • Felix Exner
  • G.A. vd. Hoorn
  • G.A. vd. Hoorn (TU Delft Robotics Institute)
  • Gaurav Gupta
  • Gonzalo Mier
  • Jose-Luis Blanco-Claraco
  • Kei Okada
  • Martin Pecka
  • Rob Fisher
  • Robert Haschke
  • Vincenzo Di Pentima
  • Wolfgang Merkt

1 post - 1 participant

Read full topic

[WWW] https://discourse.ros.org/t/new-packages-for-noetic-2024-04-11/37114

ROS Discourse General: Vote Now – ROS Awards 2024

ros awards 2024 website image

Dear ROS community,

The ROS Awards 2024 voting is now open.Cast your votes for the best projects and contributors in the ROS community. Visit Vote Now – ROS Awards 2024 and make your voice count!

About ROS Awards

The ROS Awards aim to be the Oscars of the ROS world. We intend to recognize contributions to the ROS community and the development of the ROS-based robot industry, and to help them gain awareness.

ROS Awards is a yearly award voted by the ROS community. Vote for the ROS contributions that inspired you and are shaping the future of robotics.

Voting policy

  • Everyone in the ROS community can vote.
  • Voting can only be done once from the same device and IP address.
  • We have provided a few options for reference, but voting for each category is open. You can nominate the best in your mind (We ask that you give as much detail as possible when voting to avoid confusion with other votes).
  • Since The Construct organized the awards, none of its products or developers can be nominated.
  • On June 28, 2024, one week before the ROSDevDay (July 5, 2024), voting will close and three finalists in each category will be announced.
  • Winners will be announced at the ROS Developers Day 2024, and all voting results will be published to the public on July 30, 2024.
  • The ROS Awards create awareness for new contributors from the ROS community. Therefore, last year’s winners will not be eligible for nomination this year. However, The Construct will announce the number of votes past winners received this year, along with this year’s winners, on July 30, 2024.

We hope you can cast a vote for good contributions.
The Construct Team

1 post - 1 participant

Read full topic

[WWW] https://discourse.ros.org/t/vote-now-ros-awards-2024/37101

ROS Industrial: Cartesian Waypoints with Tolerance in TrajOpt

When translating a robot trajectory from a motion plan in a ROS system to an actual executed motion, there is an inherent loss of precision. In general, trajectories are sent to a controller that adheres to the exact position and timing constraints to the best of its ability, but compromises must be made to execute the trajectory. Additionally, robots cannot achieve infinite precision in positional accuracy because the kinematics of the system cannot be known with infinite precision. We have participated in work to maximize position and velocity accuracy, but not every process requires this level of precision. The process planning component should match the level of precision required by the application, but, traditionally, motion planners work assuming infinite precision. That is why we have now introduced tolerance into our motion planning pipeline when using Cartesian waypoints in TrajOpt.

TrajOpt is an optimization-based motion planner that uses a seed trajectory along with costs and constraints to refine towards a better trajectory. This process typically involves avoiding collisions and smoothing the motion. Previously, whenever we specified a Cartesian waypoint, the tool frame needed to adhere to the desired waypoint exactly. The total error across all six degrees of freedom (6DOF) could deviate by 1e-4 meters/radians, or it would be considered a constraint violation. In applications where we allowed free rotation or motion about an axis, the coefficient associated with that constraint could be set to zero, but users were not able to set bounds on the motion. For example, a common ROS-I application would allow free rotation about the Z-axis, so we would set the last coefficient in our waypoint coefficient vector to zero. An example of this process can be seen in the Scan N Plan Workshop.

Both the extremely high precision requirements and all-or-nothing approach to 6DOF Cartesian freedom of motion do not fit most applications. Additionally, these tight constraints can often cause unnecessary motion planning failures when a small freedom of motion would enable success. With the new tolerance parameters available in TrajOpt, we can more closely match the requirements of the system while reducing the number of motion planning failures. Now available in the trajopt_default_plan_profile are various settings to tailor the various waypoint requirements to the system’s needs.

Below are two example gifs. The first shows a failed plan when no tolerance was allowed (except for free rotation about the z-axis), and the second example illustrates a successful plan when tolerance was enabled: 15 mm in X and Y, 1.5 mm in Z, and 0.01 radians in rotation around X and Y (again, free rotation about Z was allowed). Visually, these two motions look almost identical, and infinite precision would not be required for this buffing process. Using tolerance in this application will enable the robot systems to align with the process requirements and improve overall success at incorporating robotics into various processes.

failed plan when no tolerance was allowed (except for free rotation about the z-axis)

successful plan when tolerance was enabled: 15 mm in X and Y, 1.5 mm in Z, and 0.01 radians in rotation around X and Y (again, free rotation about Z was allowed)

[WWW] https://rosindustrial.org/news/2024/4/9/cartesian-waypoint-with-tolerance-in-trajopt

ROS Discourse General: ROS 2 launch file mixins round 2

Sorry as the old topic was closed (ROS 2 launch files as Mixins) here round 2.

Played some more with launch mixins, GitHub - mhubii/demo_launch: ROS 2 launch files as mixins.

In fact, every ROS 2 launch package could be structured such that launch files can be imported via

from launch_mixins.my_amazing_package import AmazingLaunch

E.g. using include launch descriptions

from launch.actions import IncludeLaunchDescription
from launch.launch_description_sources import PythonLaunchDescriptionSource
from launch.substitutions import PathJoinSubstitution
from launch_ros.substitutions import FindPackageShare

turns into

from launch_mixins.demo_launch import TurtleSimMixin, HelloWorldMixin

And then nodes can be launch a la

ld = LaunchDescription()

# add turtlesim
ld.add_action(TurtleSimMixin.arg_node_name())
ld.add_action(TurtleSimMixin.node_turtlesim())

Or mixed and matched

class MyNewLaunch(HelloWorldMixin, TurtleSimMixin):
    pass

This works for ament_python and ament_cmake, and if many people would default to launch_mixins.package_name, think this might help launch flexible projects.

Wonder how other people structure their launch files, or if this suggestion is not scalable. Happy to learn more!

5 posts - 2 participants

Read full topic

[WWW] https://discourse.ros.org/t/ros-2-launch-file-mixins-round-2/37083

ROS Discourse General: Upcoming Feature Freeze for ROS 2 Jazzy Jalisco on 15th April 2024

Hello everyone!

On 2024-04-15T07:00:00Z UTC, Monday, we will freeze all the ROS 2 base packages for the upcoming Jazzy release on May 23rd.

Once this freeze goes into effect, we will no longer accept additional features to packages in the ROS 2 Base packages, which includes rcl, rclcpp, rclpy, rosbag2, ros2cli, and geometry2. You can see the entire list of included packages here: REP 2001 – ROS 2 Variants (ROS.org) . Keep in mind the ROS Base packages includes all of the ROS Core packages .

Bug fixes will still be accepted after the freeze date.

You may find more information on the Jazzy Jalisco release timeline here: ROS 2 Jazzy Jalisco (codename ‘jazzy’; May, 2024) .

2 posts - 2 participants

Read full topic

[WWW] https://discourse.ros.org/t/upcoming-feature-freeze-for-ros-2-jazzy-jalisco-on-15th-april-2024/37075

ROS Discourse General: RMW Feature Freeze for ROS 2 Jazzy Jalisco

Hello everyone!

As we reach midnight 2024-04-08T07:00:00Z UTC all RMW packages will be feature frozen in preparation for the upcoming Jazzy Jalisco release on May 23rd. This means that we will no longer be accepting additional features to the RMWs, which include rmw_fastrtps, rmw_cyclonedds , rmw_connextdds; as well as their vendor packages, Fast-DDS, Fast-CDR, cyclonedds , and iceoryx.

Bug fixes to the RMWs will still be accepted.

We are still accepting features in the ROS 2 base packages until April 15th, when we’ll do an overall feature freeze.

You may find more information on the Jazzy Jalisco release timeline here: ROS 2 Jazzy Jalisco (codename ‘jazzy’; May, 2024) .

2 posts - 2 participants

Read full topic

[WWW] https://discourse.ros.org/t/rmw-feature-freeze-for-ros-2-jazzy-jalisco/37074

ROS Discourse General: ROS News for the Week of April 1st, 2024

ROS News for the Week of April 1st, 2024

mola3
This week saw the release of MOLA, a Modular System for Localization and Mapping into ROS 2 Iron. The source code can be found here. The MOLA binary packages are available in the latest update to ROS 2 Iron Irwini.


mustrard
NVIDIA labs teased their new Foundation Pose Library for CVPR 2024 a few months back. This week they released the source code for Foundation Pose. Word on the street is that they’ll have ROS hooks for it really soon.


image

Who doesn’t like piping hot and freshly baked ROS Docker container? :cookie: @sloretz has been in the kitchen cooking up a pipeline to build ROS Docker Images every week!


2024ROSConDiversityScholarship

:clap: ROSCon :clap: Diversity :clap: Scholarship :clap: Applications :clap: are :clap: by :clap: 2024-04-06T06:59:00Z UTC :clap:

Events

News

ROS

Got a minute?

Why not anwer a ROS question on Robotics Stack Exchange?

1 post - 1 participant

Read full topic

[WWW] https://discourse.ros.org/t/ros-news-for-the-week-of-april-1st-2024/37037

ROS Discourse General: Cloud Robotics WG Meeting - Starting to Gather Data

Our next meeting will be 2024-04-08T17:00:00Z UTC→2024-04-08T18:00:00Z UTC, using this Google Meet room.

Last week, we created a set of slides containing our initial structure for organizing our data. These are the slides from that meeting.

We will use the full hour for discussion again, covering:

  1. How we record and analyze data on cloud robotics
  2. Volunteers for creating initial versions of the database/analysis pages
  3. Volunteers for adding our current basic structure to the database page
  4. Ideas for how we can gather the most data going forwards - for example:
    1. Invite guest speakers to also be interviewed by the group
    2. Contact other cloud robotics companies to request speakers/interviewees
    3. Build questionnaire that can be made public for anyone to fill out

Please think of your own ideas as part of 4 to bring to the meeting, and I hope to see you there!

2 posts - 2 participants

Read full topic

[WWW] https://discourse.ros.org/t/cloud-robotics-wg-meeting-starting-to-gather-data/37030

ROS Discourse General: Mobile/VR/AR Application UI/UX Community Group

Hi Everyone,

I want to introduce myself - my name is Ronaldson Bellande, I’m a PhD Student/Founder CEO/CTO/Director of Research Organizations and a Startup. Can find information more about me in my linkedin and Github Profile . The organization we will be working on is Mobile/VR/AR Application UI/UX.

I wanted to create a monthly meeting community group, where we would meet monthly and discuss about mobile/vr/ar application ui/ux for robotics and other related fields, Where we discuss what everyone is working on? Are looking for and are excited for? Anything Interested you are working in? and more in the space of humanoid robotics.

If there is interest I will start a Community Group, If there is interest, it would greatly benefit to share with other individuals that would be interested.

1 post - 1 participant

Read full topic

[WWW] https://discourse.ros.org/t/mobile-vr-ar-application-ui-ux-community-group/37023

ROS Discourse General: New Packages for Iron Irwini 2024-04-05

We’re happy to announce 49 new packages and 123 updates are now available in ROS 2 Iron Irwini :iron: :irwini: . This sync was tagged as iron/2024-04-05 .

Package Updates for iron

Added Packages [49]:

Updated Packages [123]:

  • ros-iron-aruco-opencv: 5.0.0-1 → 5.1.0-1
  • ros-iron-aruco-opencv-dbgsym: 5.0.0-1 → 5.1.0-1
  • ros-iron-aruco-opencv-msgs: 5.0.0-1 → 5.1.0-1
  • ros-iron-aruco-opencv-msgs-dbgsym: 5.0.0-1 → 5.1.0-1
  • ros-iron-camera-calibration: 4.0.0-1 → 4.0.1-1
  • ros-iron-camera-calibration-parsers: 4.2.3-1 → 4.2.4-1
  • ros-iron-camera-calibration-parsers-dbgsym: 4.2.3-1 → 4.2.4-1
  • ros-iron-camera-info-manager: 4.2.3-1 → 4.2.4-1
  • ros-iron-camera-info-manager-dbgsym: 4.2.3-1 → 4.2.4-1
  • ros-iron-depth-image-proc: 4.0.0-1 → 4.0.1-1
  • ros-iron-depth-image-proc-dbgsym: 4.0.0-1 → 4.0.1-1
  • ros-iron-fields2cover: 1.2.1-2 → 1.2.1-3
  • ros-iron-fields2cover-dbgsym: 1.2.1-2 → 1.2.1-3
  • ros-iron-flir-camera-description: 2.2.14-1 → 2.2.15-1
  • ros-iron-flir-camera-msgs: 2.2.14-1 → 2.2.15-1
  • ros-iron-flir-camera-msgs-dbgsym: 2.2.14-1 → 2.2.15-1
  • ros-iron-gazebo-ros2-control: 0.6.4-1 → 0.6.5-1
  • ros-iron-gazebo-ros2-control-dbgsym: 0.6.4-1 → 0.6.5-1
  • ros-iron-gazebo-ros2-control-demos: 0.6.4-1 → 0.6.5-1
  • ros-iron-gazebo-ros2-control-demos-dbgsym: 0.6.4-1 → 0.6.5-1
  • ros-iron-gz-ros2-control: 1.1.4-2 → 1.1.5-1
  • ros-iron-gz-ros2-control-dbgsym: 1.1.4-2 → 1.1.5-1
  • ros-iron-gz-ros2-control-demos: 1.1.4-2 → 1.1.5-1
  • ros-iron-gz-ros2-control-demos-dbgsym: 1.1.4-2 → 1.1.5-1
  • ros-iron-image-common: 4.2.3-1 → 4.2.4-1
  • ros-iron-image-pipeline: 4.0.0-1 → 4.0.1-1
  • ros-iron-image-proc: 4.0.0-1 → 4.0.1-1
  • ros-iron-image-proc-dbgsym: 4.0.0-1 → 4.0.1-1
  • ros-iron-image-publisher: 4.0.0-1 → 4.0.1-1
  • ros-iron-image-publisher-dbgsym: 4.0.0-1 → 4.0.1-1
  • ros-iron-image-rotate: 4.0.0-1 → 4.0.1-1
  • ros-iron-image-rotate-dbgsym: 4.0.0-1 → 4.0.1-1
  • ros-iron-image-transport: 4.2.3-1 → 4.2.4-1
  • ros-iron-image-transport-dbgsym: 4.2.3-1 → 4.2.4-1
  • ros-iron-image-view: 4.0.0-1 → 4.0.1-1
  • ros-iron-image-view-dbgsym: 4.0.0-1 → 4.0.1-1
  • ros-iron-microstrain-inertial-driver: 3.2.1-1 → 4.1.0-1
  • ros-iron-microstrain-inertial-driver-dbgsym: 3.2.1-1 → 4.1.0-1
  • ros-iron-microstrain-inertial-examples: 3.2.1-1 → 4.1.0-1
  • ros-iron-microstrain-inertial-msgs: 3.2.1-1 → 4.1.0-1
  • ros-iron-microstrain-inertial-msgs-dbgsym: 3.2.1-1 → 4.1.0-1
  • ros-iron-microstrain-inertial-rqt: 3.2.1-1 → 4.1.0-1
  • ros-iron-mola-test-datasets: 0.3.0-1 → 0.3.1-1
  • ros-iron-mvsim: 0.9.1-1 → 0.9.2-1
  • ros-iron-mvsim-dbgsym: 0.9.1-1 → 0.9.2-1
  • ros-iron-ntrip-client-node: 0.5.2-1 → 0.5.3-1
  • ros-iron-ntrip-client-node-dbgsym: 0.5.2-1 → 0.5.3-1
  • ros-iron-point-cloud-transport: 2.0.4-1 → 2.0.5-1
  • ros-iron-point-cloud-transport-dbgsym: 2.0.4-1 → 2.0.5-1
  • ros-iron-point-cloud-transport-py: 2.0.4-1 → 2.0.5-1
  • ros-iron-rmf-charger-msgs: 3.1.1-1 → 3.1.2-1
  • ros-iron-rmf-charger-msgs-dbgsym: 3.1.1-1 → 3.1.2-1
  • ros-iron-rmf-dispenser-msgs: 3.1.1-1 → 3.1.2-1
  • ros-iron-rmf-dispenser-msgs-dbgsym: 3.1.1-1 → 3.1.2-1
  • ros-iron-rmf-door-msgs: 3.1.1-1 → 3.1.2-1
  • ros-iron-rmf-door-msgs-dbgsym: 3.1.1-1 → 3.1.2-1
  • ros-iron-rmf-fleet-msgs: 3.1.1-1 → 3.1.2-1
  • ros-iron-rmf-fleet-msgs-dbgsym: 3.1.1-1 → 3.1.2-1
  • ros-iron-rmf-ingestor-msgs: 3.1.1-1 → 3.1.2-1
  • ros-iron-rmf-ingestor-msgs-dbgsym: 3.1.1-1 → 3.1.2-1
  • ros-iron-rmf-lift-msgs: 3.1.1-1 → 3.1.2-1
  • ros-iron-rmf-lift-msgs-dbgsym: 3.1.1-1 → 3.1.2-1
  • ros-iron-rmf-obstacle-msgs: 3.1.1-1 → 3.1.2-1
  • ros-iron-rmf-obstacle-msgs-dbgsym: 3.1.1-1 → 3.1.2-1
  • ros-iron-rmf-scheduler-msgs: 3.1.1-1 → 3.1.2-1
  • ros-iron-rmf-scheduler-msgs-dbgsym: 3.1.1-1 → 3.1.2-1
  • ros-iron-rmf-site-map-msgs: 3.1.1-1 → 3.1.2-1
  • ros-iron-rmf-site-map-msgs-dbgsym: 3.1.1-1 → 3.1.2-1
  • ros-iron-rmf-task: 2.2.4-1 → 2.2.5-1
  • ros-iron-rmf-task-dbgsym: 2.2.4-1 → 2.2.5-1
  • ros-iron-rmf-task-msgs: 3.1.1-1 → 3.1.2-1
  • ros-iron-rmf-task-msgs-dbgsym: 3.1.1-1 → 3.1.2-1
  • ros-iron-rmf-task-sequence: 2.2.4-1 → 2.2.5-1
  • ros-iron-rmf-task-sequence-dbgsym: 2.2.4-1 → 2.2.5-1
  • ros-iron-rmf-traffic-msgs: 3.1.1-1 → 3.1.2-1
  • ros-iron-rmf-traffic-msgs-dbgsym: 3.1.1-1 → 3.1.2-1
  • ros-iron-rmf-visualization: 2.1.1-1 → 2.1.2-1
  • ros-iron-rmf-visualization-building-systems: 2.1.1-1 → 2.1.2-1
  • ros-iron-rmf-visualization-fleet-states: 2.1.1-1 → 2.1.2-1
  • ros-iron-rmf-visualization-fleet-states-dbgsym: 2.1.1-1 → 2.1.2-1
  • ros-iron-rmf-visualization-floorplans: 2.1.1-1 → 2.1.2-1
  • ros-iron-rmf-visualization-floorplans-dbgsym: 2.1.1-1 → 2.1.2-1
  • ros-iron-rmf-visualization-navgraphs: 2.1.1-1 → 2.1.2-1
  • ros-iron-rmf-visualization-navgraphs-dbgsym: 2.1.1-1 → 2.1.2-1
  • ros-iron-rmf-visualization-obstacles: 2.1.1-1 → 2.1.2-1
  • ros-iron-rmf-visualization-obstacles-dbgsym: 2.1.1-1 → 2.1.2-1
  • ros-iron-rmf-visualization-rviz2-plugins: 2.1.1-1 → 2.1.2-1
  • ros-iron-rmf-visualization-rviz2-plugins-dbgsym: 2.1.1-1 → 2.1.2-1
  • ros-iron-rmf-visualization-schedule: 2.1.1-1 → 2.1.2-1
  • ros-iron-rmf-visualization-schedule-dbgsym: 2.1.1-1 → 2.1.2-1
  • ros-iron-rmf-workcell-msgs: 3.1.1-1 → 3.1.2-1
  • ros-iron-rmf-workcell-msgs-dbgsym: 3.1.1-1 → 3.1.2-1
  • ros-iron-rviz-assimp-vendor: 12.4.6-1 → 12.4.7-1
  • ros-iron-rviz-common: 12.4.6-1 → 12.4.7-1
  • ros-iron-rviz-common-dbgsym: 12.4.6-1 → 12.4.7-1
  • ros-iron-rviz-default-plugins: 12.4.6-1 → 12.4.7-1
  • ros-iron-rviz-default-plugins-dbgsym: 12.4.6-1 → 12.4.7-1
  • ros-iron-rviz-ogre-vendor: 12.4.6-1 → 12.4.7-1
  • ros-iron-rviz-ogre-vendor-dbgsym: 12.4.6-1 → 12.4.7-1
  • ros-iron-rviz-rendering: 12.4.6-1 → 12.4.7-1
  • ros-iron-rviz-rendering-dbgsym: 12.4.6-1 → 12.4.7-1
  • ros-iron-rviz-rendering-tests: 12.4.6-1 → 12.4.7-1
  • ros-iron-rviz-visual-testing-framework: 12.4.6-1 → 12.4.7-1
  • ros-iron-rviz2: 12.4.6-1 → 12.4.7-1
  • ros-iron-rviz2-dbgsym: 12.4.6-1 → 12.4.7-1
  • ros-iron-simple-launch: 1.9.1-1 → 1.9.2-1
  • ros-iron-spinnaker-camera-driver: 2.2.14-1 → 2.2.15-1
  • ros-iron-spinnaker-camera-driver-dbgsym: 2.2.14-1 → 2.2.15-1
  • ros-iron-spinnaker-synchronized-camera-driver: 2.2.14-1 → 2.2.15-1
  • ros-iron-spinnaker-synchronized-camera-driver-dbgsym: 2.2.14-1 → 2.2.15-1
  • ros-iron-stereo-image-proc: 4.0.0-1 → 4.0.1-1
  • ros-iron-stereo-image-proc-dbgsym: 4.0.0-1 → 4.0.1-1
  • ros-iron-tracetools-image-pipeline: 4.0.0-1 → 4.0.1-1
  • ros-iron-tracetools-image-pipeline-dbgsym: 4.0.0-1 → 4.0.1-1
  • ros-iron-ublox-dgnss: 0.5.2-1 → 0.5.3-1
  • ros-iron-ublox-dgnss-node: 0.5.2-1 → 0.5.3-1
  • ros-iron-ublox-dgnss-node-dbgsym: 0.5.2-1 → 0.5.3-1
  • ros-iron-ublox-nav-sat-fix-hp-node: 0.5.2-1 → 0.5.3-1
  • ros-iron-ublox-nav-sat-fix-hp-node-dbgsym: 0.5.2-1 → 0.5.3-1
  • ros-iron-ublox-ubx-interfaces: 0.5.2-1 → 0.5.3-1
  • ros-iron-ublox-ubx-interfaces-dbgsym: 0.5.2-1 → 0.5.3-1
  • ros-iron-ublox-ubx-msgs: 0.5.2-1 → 0.5.3-1
  • ros-iron-ublox-ubx-msgs-dbgsym: 0.5.2-1 → 0.5.3-1

Removed Packages [1]:

  • ros-iron-microstrain-inertial-examples-dbgsym

Thanks to all ROS maintainers who make packages available to the ROS community. The above list of packages was made possible by the work of the following maintainers:

  • Aaron Chong
  • Alejandro Hernandez
  • Alejandro Hernandez Cordero
  • Alejandro Hernández
  • Arjo Chakravarty
  • Bernd Pfrommer
  • Fictionlab
  • Geoff Sokoll
  • Gonzalo Mier
  • Grey
  • Jose-Luis Blanco-Claraco
  • José Luis Blanco-Claraco
  • Luis Camero
  • Marco A. Gutiérrez
  • Morgan Quigley
  • Nick Hortovanyi
  • Olivier Kermorgant
  • Pedro Soares
  • Rob Fisher
  • Rushyendra Maganty
  • Vincent Rabaud
  • Víctor Mayoral-Vilches
  • Yadunund

1 post - 1 participant

Read full topic

[WWW] https://discourse.ros.org/t/new-packages-for-iron-irwini-2024-04-05/37010

ROS Discourse General: Client Library WG meeting April 5 2024

Hi, just a reminder that tomorrow we will have a meeting of the Client Library Working Group.

As in the past meetings, the focus will almost entirely be on reviewing and discussing PRs before the Jazzy features freeze.

We will meet at 8AM Pacific Time.
Find here the Meeting Link https://meet.google.com/oij-atzj-znw

One of the main discussion topics is definitely around bugs and expected behaviors of ROS 2 actions goal handles: Callback after cancel by jmachowinski · Pull Request #2281 · ros2/rclcpp · GitHub
See the ticket for more details: we identified some bugs and inconsistencies in how goal handles are kept in scope and how they can be dropped and we are trying to fix them for Jazzy.

1 post - 1 participant

Read full topic

[WWW] https://discourse.ros.org/t/client-library-wg-meeting-april-5-2024/36998

ROS Discourse General: Discuss: Tools and Best Practices for 3D Robot Assets (URDF, SDFormat, CAD, etc)

Hi Everyone,

After answering a question about URDF exporters for the umpteenth time, and having half a dozen relevant tabs open on my desktop, I put together a short guide on URDF exporters for docs.ros.org. There’s some really great discussion in the pull request that’s worth checking out. If you haven’t noticed lately we’re making some - slow - and steady - progress on docs.ros.org, and we really appreciate the community’s help!

The CAD to robot simulation / visualization part of ROS has always seemed like black magic, and I wanted to see if we could shine some light on the process. My question for the community is this: What does your CAD to simulation / visualization pipeline look like? How do you handle updating your robot’s geometry? What tools do you use to translate your robot’s CAD files into simulation / visualization assets? How do you handle differences between hardware versions? Are there other tools or guides that you use all the time that we should we add to the list?

If you are interested in expanding on this topic we would love to have your contributions over on docs.ros.org.

26 posts - 15 participants

Read full topic

[WWW] https://discourse.ros.org/t/discuss-tools-and-best-practices-for-3d-robot-assets-urdf-sdformat-cad-etc/36997

ROS Discourse General: Nomenclature of tf_echo and tf_listener

I did an issue in ROS documentation 2 weeks ago, but I got no answer. Yesterday, in the ROS Meetup Barcelona, I commented it with my colleagues and I did not get any consensus. It is a question of nomenclature and probably the ROS documentation is written by people from different areas (Vision, classic robotics, etc.) that have a different background.

Let me put this question here, and maybe we can clarify the concept.

The tool tf2_echo help says:

tf2_echo source_frame target_frame [echo_rate]

This will echo the transform from the coordinate frame of the source_frame
to the coordinate frame of the target_frame.
Note: This is the transform to get data from target_frame into the source_frame.

For me is clear, if I have a frame, for instance, “grasp_01”, and another frame “base”, and I execute:

ros2 run tf2_ros tf2_echo base grasp_01

I would obtain the transformation that comes from base to grasp_01. Easily, I can see the distance between the origin of “base” to the origin of “grasp_01” expressed in the “base” frame.

But, in the documentation, for example the turtle, the sentence says:

Let’s look at the transform of the turtle2 frame with respect to turtle1 frame which is equivalent to:
ros2 run tf2_ros tf2_echo turtle2 turtle1

To me is the opposite, I got the transformation from turtle2 to turtle1, that is the same the frame turtle1 w.r.t. turtle2, not the opposite as claims the documentation.

Also, I got another issue, the tf_buffer class has the method

lookupTransform (const std::string &target_frame, const std::string &source_frame, const tf2::TimePoint &time, const tf2::Duration timeout) const override

where you gets the transform between two frames by frame ID. With:

  • target_frame = The frame to which data should be transformed
  • source_frame = The frame where the data originated
    …

If I create a listener in C++, and I call the function with:

tfs = tf_buffer_->lookupTransform(“base”, “grasp_01”, tf2::TimePointZero);

I would obtain the same value as using tf2_echo.

It is curious, because I asked several people and many times I got the answer: “First, I try it with tfA and after tfB, but if I don’t get the data I want, I change to tfB and later tfA”.

So, please, could you explain what should I understand as source_frame, target_frame in the ROS context?

7 posts - 5 participants

Read full topic

[WWW] https://discourse.ros.org/t/nomenclature-of-tf-echo-and-tf-listener/36985

Wiki: TullyFoote/TestPlanetRSS (last edited 2014-09-25 22:49:53 by TullyFoote)

Except where otherwise noted, the ROS wiki is licensed under the
Creative Commons Attribution 3.0