September 09, 2024
New Packages for Iron Irwini 2024-09-09

Hello everyone!

We’re happy to announce 6 new packages and 285 updates are now available in ROS 2 Iron Irwini :iron: :irwini: .

This sync was tagged as iron/2024-09-09 .

Package Updates for iron

Added Packages [6]:

  • ros-iron-ffmpeg-encoder-decoder: 1.0.1-1
  • ros-iron-ffmpeg-encoder-decoder-dbgsym: 1.0.1-1
  • ros-iron-mrpt-libros-bridge: 2.13.7-3
  • ros-iron-mrpt-libros-bridge-dbgsym: 2.13.7-3
  • ros-iron-turtle-nest: 1.0.1-1
  • ros-iron-turtle-nest-dbgsym: 1.0.1-1

Updated Packages [285]:

  • ros-iron-ackermann-steering-controller: 3.26.1-1 → 3.26.2-1
  • ros-iron-ackermann-steering-controller-dbgsym: 3.26.1-1 → 3.26.2-1
  • ros-iron-admittance-controller: 3.26.1-1 → 3.26.2-1
  • ros-iron-admittance-controller-dbgsym: 3.26.1-1 → 3.26.2-1
  • ros-iron-bicycle-steering-controller: 3.26.1-1 → 3.26.2-1
  • ros-iron-bicycle-steering-controller-dbgsym: 3.26.1-1 → 3.26.2-1
  • ros-iron-controller-interface: 3.27.0-1 → 3.28.0-1
  • ros-iron-controller-interface-dbgsym: 3.27.0-1 → 3.28.0-1
  • ros-iron-controller-manager: 3.27.0-1 → 3.28.0-1
  • ros-iron-controller-manager-dbgsym: 3.27.0-1 → 3.28.0-1
  • ros-iron-controller-manager-msgs: 3.27.0-1 → 3.28.0-1
  • ros-iron-controller-manager-msgs-dbgsym: 3.27.0-1 → 3.28.0-1
  • ros-iron-costmap-queue: 1.2.9-1 → 1.2.10-1
  • ros-iron-costmap-queue-dbgsym: 1.2.9-1 → 1.2.10-1
  • ros-iron-depthai: 2.26.1-1 → 2.28.0-1
  • ros-iron-depthai-bridge: 2.9.0-1 → 2.10.0-1
  • ros-iron-depthai-bridge-dbgsym: 2.9.0-1 → 2.10.0-1
  • ros-iron-depthai-dbgsym: 2.26.1-1 → 2.28.0-1
  • ros-iron-depthai-descriptions: 2.9.0-1 → 2.10.0-1
  • ros-iron-depthai-examples: 2.9.0-1 → 2.10.0-1
  • ros-iron-depthai-examples-dbgsym: 2.9.0-1 → 2.10.0-1
  • ros-iron-depthai-filters: 2.9.0-1 → 2.10.0-1
  • ros-iron-depthai-filters-dbgsym: 2.9.0-1 → 2.10.0-1
  • ros-iron-depthai-ros: 2.9.0-1 → 2.10.0-1
  • ros-iron-depthai-ros-driver: 2.9.0-1 → 2.10.0-1
  • ros-iron-depthai-ros-driver-dbgsym: 2.9.0-1 → 2.10.0-1
  • ros-iron-depthai-ros-msgs: 2.9.0-1 → 2.10.0-1
  • ros-iron-depthai-ros-msgs-dbgsym: 2.9.0-1 → 2.10.0-1
  • ros-iron-diff-drive-controller: 3.26.1-1 → 3.26.2-1
  • ros-iron-diff-drive-controller-dbgsym: 3.26.1-1 → 3.26.2-1
  • ros-iron-dwb-core: 1.2.9-1 → 1.2.10-1
  • ros-iron-dwb-core-dbgsym: 1.2.9-1 → 1.2.10-1
  • ros-iron-dwb-critics: 1.2.9-1 → 1.2.10-1
  • ros-iron-dwb-critics-dbgsym: 1.2.9-1 → 1.2.10-1
  • ros-iron-dwb-msgs: 1.2.9-1 → 1.2.10-1
  • ros-iron-dwb-msgs-dbgsym: 1.2.9-1 → 1.2.10-1
  • ros-iron-dwb-plugins: 1.2.9-1 → 1.2.10-1
  • ros-iron-dwb-plugins-dbgsym: 1.2.9-1 → 1.2.10-1
  • ros-iron-effort-controllers: 3.26.1-1 → 3.26.2-1
  • ros-iron-effort-controllers-dbgsym: 3.26.1-1 → 3.26.2-1
  • ros-iron-eigenpy: 3.7.0-1 → 3.8.2-1
  • ros-iron-eigenpy-dbgsym: 3.7.0-1 → 3.8.2-1
  • ros-iron-examples-tf2-py: 0.31.7-1 → 0.31.8-1
  • ros-iron-force-torque-sensor-broadcaster: 3.26.1-1 → 3.26.2-1
  • ros-iron-force-torque-sensor-broadcaster-dbgsym: 3.26.1-1 → 3.26.2-1
  • ros-iron-forward-command-controller: 3.26.1-1 → 3.26.2-1
  • ros-iron-forward-command-controller-dbgsym: 3.26.1-1 → 3.26.2-1
  • ros-iron-geometry2: 0.31.7-1 → 0.31.8-1
  • ros-iron-gripper-controllers: 3.26.1-1 → 3.26.2-1
  • ros-iron-gripper-controllers-dbgsym: 3.26.1-1 → 3.26.2-1
  • ros-iron-gtsam: 4.2.0-5 → 4.2.0-6
  • ros-iron-gtsam-dbgsym: 4.2.0-5 → 4.2.0-6
  • ros-iron-hardware-interface: 3.27.0-1 → 3.28.0-1
  • ros-iron-hardware-interface-dbgsym: 3.27.0-1 → 3.28.0-1
  • ros-iron-hardware-interface-testing: 3.27.0-1 → 3.28.0-1
  • ros-iron-hardware-interface-testing-dbgsym: 3.27.0-1 → 3.28.0-1
  • ros-iron-imu-sensor-broadcaster: 3.26.1-1 → 3.26.2-1
  • ros-iron-imu-sensor-broadcaster-dbgsym: 3.26.1-1 → 3.26.2-1
  • ros-iron-joint-limits: 3.27.0-1 → 3.28.0-1
  • ros-iron-joint-state-broadcaster: 3.26.1-1 → 3.26.2-1
  • ros-iron-joint-state-broadcaster-dbgsym: 3.26.1-1 → 3.26.2-1
  • ros-iron-joint-trajectory-controller: 3.26.1-1 → 3.26.2-1
  • ros-iron-joint-trajectory-controller-dbgsym: 3.26.1-1 → 3.26.2-1
  • ros-iron-joy-teleop: 1.5.0-1 → 1.5.1-1
  • ros-iron-key-teleop: 1.5.0-1 → 1.5.1-1
  • ros-iron-kitti-metrics-eval: 1.1.0-1 → 1.1.3-1
  • ros-iron-kitti-metrics-eval-dbgsym: 1.1.0-1 → 1.1.3-1
  • ros-iron-mola: 1.1.0-1 → 1.1.3-1
  • ros-iron-mola-bridge-ros2: 1.1.0-1 → 1.1.3-1
  • ros-iron-mola-bridge-ros2-dbgsym: 1.1.0-1 → 1.1.3-1
  • ros-iron-mola-demos: 1.1.0-1 → 1.1.3-1
  • ros-iron-mola-imu-preintegration: 1.1.0-1 → 1.1.3-1
  • ros-iron-mola-imu-preintegration-dbgsym: 1.1.0-1 → 1.1.3-1
  • ros-iron-mola-input-euroc-dataset: 1.1.0-1 → 1.1.3-1
  • ros-iron-mola-input-euroc-dataset-dbgsym: 1.1.0-1 → 1.1.3-1
  • ros-iron-mola-input-kitti-dataset: 1.1.0-1 → 1.1.3-1
  • ros-iron-mola-input-kitti-dataset-dbgsym: 1.1.0-1 → 1.1.3-1
  • ros-iron-mola-input-kitti360-dataset: 1.1.0-1 → 1.1.3-1
  • ros-iron-mola-input-kitti360-dataset-dbgsym: 1.1.0-1 → 1.1.3-1
  • ros-iron-mola-input-mulran-dataset: 1.1.0-1 → 1.1.3-1
  • ros-iron-mola-input-mulran-dataset-dbgsym: 1.1.0-1 → 1.1.3-1
  • ros-iron-mola-input-paris-luco-dataset: 1.1.0-1 → 1.1.3-1
  • ros-iron-mola-input-paris-luco-dataset-dbgsym: 1.1.0-1 → 1.1.3-1
  • ros-iron-mola-input-rawlog: 1.1.0-1 → 1.1.3-1
  • ros-iron-mola-input-rawlog-dbgsym: 1.1.0-1 → 1.1.3-1
  • ros-iron-mola-input-rosbag2: 1.1.0-1 → 1.1.3-1
  • ros-iron-mola-input-rosbag2-dbgsym: 1.1.0-1 → 1.1.3-1
  • ros-iron-mola-kernel: 1.1.0-1 → 1.1.3-1
  • ros-iron-mola-kernel-dbgsym: 1.1.0-1 → 1.1.3-1
  • ros-iron-mola-launcher: 1.1.0-1 → 1.1.3-1
  • ros-iron-mola-launcher-dbgsym: 1.1.0-1 → 1.1.3-1
  • ros-iron-mola-lidar-odometry: 0.3.0-1 → 0.3.3-1
  • ros-iron-mola-lidar-odometry-dbgsym: 0.3.0-1 → 0.3.3-1
  • ros-iron-mola-metric-maps: 1.1.0-1 → 1.1.3-1
  • ros-iron-mola-metric-maps-dbgsym: 1.1.0-1 → 1.1.3-1
  • ros-iron-mola-msgs: 1.1.0-1 → 1.1.3-1
  • ros-iron-mola-msgs-dbgsym: 1.1.0-1 → 1.1.3-1
  • ros-iron-mola-navstate-fg: 1.1.0-1 → 1.1.3-1
  • ros-iron-mola-navstate-fg-dbgsym: 1.1.0-1 → 1.1.3-1
  • ros-iron-mola-navstate-fuse: 1.1.0-1 → 1.1.3-1
  • ros-iron-mola-navstate-fuse-dbgsym: 1.1.0-1 → 1.1.3-1
  • ros-iron-mola-pose-list: 1.1.0-1 → 1.1.3-1
  • ros-iron-mola-pose-list-dbgsym: 1.1.0-1 → 1.1.3-1
  • ros-iron-mola-relocalization: 1.1.0-1 → 1.1.3-1
  • ros-iron-mola-relocalization-dbgsym: 1.1.0-1 → 1.1.3-1
  • ros-iron-mola-traj-tools: 1.1.0-1 → 1.1.3-1
  • ros-iron-mola-traj-tools-dbgsym: 1.1.0-1 → 1.1.3-1
  • ros-iron-mola-viz: 1.1.0-1 → 1.1.3-1
  • ros-iron-mola-viz-dbgsym: 1.1.0-1 → 1.1.3-1
  • ros-iron-mola-yaml: 1.1.0-1 → 1.1.3-1
  • ros-iron-mola-yaml-dbgsym: 1.1.0-1 → 1.1.3-1
  • ros-iron-mouse-teleop: 1.5.0-1 → 1.5.1-1
  • ros-iron-mp2p-icp: 1.5.3-1 → 1.5.5-1
  • ros-iron-mp2p-icp-dbgsym: 1.5.3-1 → 1.5.5-1
  • ros-iron-mrpt-apps: 2.13.6-3 → 2.13.7-3
  • ros-iron-mrpt-apps-dbgsym: 2.13.6-3 → 2.13.7-3
  • ros-iron-mrpt-generic-sensor: 0.2.2-1 → 0.2.3-1
  • ros-iron-mrpt-generic-sensor-dbgsym: 0.2.2-1 → 0.2.3-1
  • ros-iron-mrpt-libapps: 2.13.6-3 → 2.13.7-3
  • ros-iron-mrpt-libapps-dbgsym: 2.13.6-3 → 2.13.7-3
  • ros-iron-mrpt-libbase: 2.13.6-3 → 2.13.7-3
  • ros-iron-mrpt-libbase-dbgsym: 2.13.6-3 → 2.13.7-3
  • ros-iron-mrpt-libgui: 2.13.6-3 → 2.13.7-3
  • ros-iron-mrpt-libgui-dbgsym: 2.13.6-3 → 2.13.7-3
  • ros-iron-mrpt-libhwdrivers: 2.13.6-3 → 2.13.7-3
  • ros-iron-mrpt-libhwdrivers-dbgsym: 2.13.6-3 → 2.13.7-3
  • ros-iron-mrpt-libmaps: 2.13.6-3 → 2.13.7-3
  • ros-iron-mrpt-libmaps-dbgsym: 2.13.6-3 → 2.13.7-3
  • ros-iron-mrpt-libmath: 2.13.6-3 → 2.13.7-3
  • ros-iron-mrpt-libmath-dbgsym: 2.13.6-3 → 2.13.7-3
  • ros-iron-mrpt-libnav: 2.13.6-3 → 2.13.7-3
  • ros-iron-mrpt-libnav-dbgsym: 2.13.6-3 → 2.13.7-3
  • ros-iron-mrpt-libobs: 2.13.6-3 → 2.13.7-3
  • ros-iron-mrpt-libobs-dbgsym: 2.13.6-3 → 2.13.7-3
  • ros-iron-mrpt-libopengl: 2.13.6-3 → 2.13.7-3
  • ros-iron-mrpt-libopengl-dbgsym: 2.13.6-3 → 2.13.7-3
  • ros-iron-mrpt-libposes: 2.13.6-3 → 2.13.7-3
  • ros-iron-mrpt-libposes-dbgsym: 2.13.6-3 → 2.13.7-3
  • ros-iron-mrpt-libslam: 2.13.6-3 → 2.13.7-3
  • ros-iron-mrpt-libslam-dbgsym: 2.13.6-3 → 2.13.7-3
  • ros-iron-mrpt-libtclap: 2.13.6-3 → 2.13.7-3
  • ros-iron-mrpt-map-server: 2.1.0-1 → 2.1.1-1
  • ros-iron-mrpt-map-server-dbgsym: 2.1.0-1 → 2.1.1-1
  • ros-iron-mrpt-msgs-bridge: 2.1.0-1 → 2.1.1-1
  • ros-iron-mrpt-nav-interfaces: 2.1.0-1 → 2.1.1-1
  • ros-iron-mrpt-nav-interfaces-dbgsym: 2.1.0-1 → 2.1.1-1
  • ros-iron-mrpt-navigation: 2.1.0-1 → 2.1.1-1
  • ros-iron-mrpt-path-planning: 0.1.2-1 → 0.1.4-1
  • ros-iron-mrpt-path-planning-dbgsym: 0.1.2-1 → 0.1.4-1
  • ros-iron-mrpt-pf-localization: 2.1.0-1 → 2.1.1-1
  • ros-iron-mrpt-pf-localization-dbgsym: 2.1.0-1 → 2.1.1-1
  • ros-iron-mrpt-pointcloud-pipeline: 2.1.0-1 → 2.1.1-1
  • ros-iron-mrpt-pointcloud-pipeline-dbgsym: 2.1.0-1 → 2.1.1-1
  • ros-iron-mrpt-rawlog: 2.1.0-1 → 2.1.1-1
  • ros-iron-mrpt-rawlog-dbgsym: 2.1.0-1 → 2.1.1-1
  • ros-iron-mrpt-reactivenav2d: 2.1.0-1 → 2.1.1-1
  • ros-iron-mrpt-reactivenav2d-dbgsym: 2.1.0-1 → 2.1.1-1
  • ros-iron-mrpt-sensor-bumblebee-stereo: 0.2.2-1 → 0.2.3-1
  • ros-iron-mrpt-sensor-bumblebee-stereo-dbgsym: 0.2.2-1 → 0.2.3-1
  • ros-iron-mrpt-sensor-gnss-nmea: 0.2.2-1 → 0.2.3-1
  • ros-iron-mrpt-sensor-gnss-nmea-dbgsym: 0.2.2-1 → 0.2.3-1
  • ros-iron-mrpt-sensor-gnss-novatel: 0.2.2-1 → 0.2.3-1
  • ros-iron-mrpt-sensor-gnss-novatel-dbgsym: 0.2.2-1 → 0.2.3-1
  • ros-iron-mrpt-sensor-imu-taobotics: 0.2.2-1 → 0.2.3-1
  • ros-iron-mrpt-sensor-imu-taobotics-dbgsym: 0.2.2-1 → 0.2.3-1
  • ros-iron-mrpt-sensorlib: 0.2.2-1 → 0.2.3-1
  • ros-iron-mrpt-sensors: 0.2.2-1 → 0.2.3-1
  • ros-iron-mrpt-tps-astar-planner: 2.1.0-1 → 2.1.1-1
  • ros-iron-mrpt-tps-astar-planner-dbgsym: 2.1.0-1 → 2.1.1-1
  • ros-iron-mrpt-tutorials: 2.1.0-1 → 2.1.1-1
  • ros-iron-mvsim: 0.9.4-1 → 0.10.0-1
  • ros-iron-mvsim-dbgsym: 0.9.4-1 → 0.10.0-1
  • ros-iron-nav-2d-msgs: 1.2.9-1 → 1.2.10-1
  • ros-iron-nav-2d-msgs-dbgsym: 1.2.9-1 → 1.2.10-1
  • ros-iron-nav-2d-utils: 1.2.9-1 → 1.2.10-1
  • ros-iron-nav-2d-utils-dbgsym: 1.2.9-1 → 1.2.10-1
  • ros-iron-nav2-amcl: 1.2.9-1 → 1.2.10-1
  • ros-iron-nav2-amcl-dbgsym: 1.2.9-1 → 1.2.10-1
  • ros-iron-nav2-behavior-tree: 1.2.9-1 → 1.2.10-1
  • ros-iron-nav2-behavior-tree-dbgsym: 1.2.9-1 → 1.2.10-1
  • ros-iron-nav2-behaviors: 1.2.9-1 → 1.2.10-1
  • ros-iron-nav2-behaviors-dbgsym: 1.2.9-1 → 1.2.10-1
  • ros-iron-nav2-bringup: 1.2.9-1 → 1.2.10-1
  • ros-iron-nav2-bt-navigator: 1.2.9-1 → 1.2.10-1
  • ros-iron-nav2-bt-navigator-dbgsym: 1.2.9-1 → 1.2.10-1
  • ros-iron-nav2-collision-monitor: 1.2.9-1 → 1.2.10-1
  • ros-iron-nav2-collision-monitor-dbgsym: 1.2.9-1 → 1.2.10-1
  • ros-iron-nav2-common: 1.2.9-1 → 1.2.10-1
  • ros-iron-nav2-constrained-smoother: 1.2.9-1 → 1.2.10-1
  • ros-iron-nav2-constrained-smoother-dbgsym: 1.2.9-1 → 1.2.10-1
  • ros-iron-nav2-controller: 1.2.9-1 → 1.2.10-1
  • ros-iron-nav2-controller-dbgsym: 1.2.9-1 → 1.2.10-1
  • ros-iron-nav2-core: 1.2.9-1 → 1.2.10-1
  • ros-iron-nav2-costmap-2d: 1.2.9-1 → 1.2.10-1
  • ros-iron-nav2-costmap-2d-dbgsym: 1.2.9-1 → 1.2.10-1
  • ros-iron-nav2-dwb-controller: 1.2.9-1 → 1.2.10-1
  • ros-iron-nav2-lifecycle-manager: 1.2.9-1 → 1.2.10-1
  • ros-iron-nav2-lifecycle-manager-dbgsym: 1.2.9-1 → 1.2.10-1
  • ros-iron-nav2-map-server: 1.2.9-1 → 1.2.10-1
  • ros-iron-nav2-map-server-dbgsym: 1.2.9-1 → 1.2.10-1
  • ros-iron-nav2-mppi-controller: 1.2.9-1 → 1.2.10-1
  • ros-iron-nav2-mppi-controller-dbgsym: 1.2.9-1 → 1.2.10-1
  • ros-iron-nav2-msgs: 1.2.9-1 → 1.2.10-1
  • ros-iron-nav2-msgs-dbgsym: 1.2.9-1 → 1.2.10-1
  • ros-iron-nav2-navfn-planner: 1.2.9-1 → 1.2.10-1
  • ros-iron-nav2-navfn-planner-dbgsym: 1.2.9-1 → 1.2.10-1
  • ros-iron-nav2-planner: 1.2.9-1 → 1.2.10-1
  • ros-iron-nav2-planner-dbgsym: 1.2.9-1 → 1.2.10-1
  • ros-iron-nav2-regulated-pure-pursuit-controller: 1.2.9-1 → 1.2.10-1
  • ros-iron-nav2-regulated-pure-pursuit-controller-dbgsym: 1.2.9-1 → 1.2.10-1
  • ros-iron-nav2-rotation-shim-controller: 1.2.9-1 → 1.2.10-1
  • ros-iron-nav2-rotation-shim-controller-dbgsym: 1.2.9-1 → 1.2.10-1
  • ros-iron-nav2-rviz-plugins: 1.2.9-1 → 1.2.10-1
  • ros-iron-nav2-rviz-plugins-dbgsym: 1.2.9-1 → 1.2.10-1
  • ros-iron-nav2-simple-commander: 1.2.9-1 → 1.2.10-1
  • ros-iron-nav2-smac-planner: 1.2.9-1 → 1.2.10-1
  • ros-iron-nav2-smac-planner-dbgsym: 1.2.9-1 → 1.2.10-1
  • ros-iron-nav2-smoother: 1.2.9-1 → 1.2.10-1
  • ros-iron-nav2-smoother-dbgsym: 1.2.9-1 → 1.2.10-1
  • ros-iron-nav2-system-tests: 1.2.9-1 → 1.2.10-1
  • ros-iron-nav2-system-tests-dbgsym: 1.2.9-1 → 1.2.10-1
  • ros-iron-nav2-theta-star-planner: 1.2.9-1 → 1.2.10-1
  • ros-iron-nav2-theta-star-planner-dbgsym: 1.2.9-1 → 1.2.10-1
  • ros-iron-nav2-util: 1.2.9-1 → 1.2.10-1
  • ros-iron-nav2-util-dbgsym: 1.2.9-1 → 1.2.10-1
  • ros-iron-nav2-velocity-smoother: 1.2.9-1 → 1.2.10-1
  • ros-iron-nav2-velocity-smoother-dbgsym: 1.2.9-1 → 1.2.10-1
  • ros-iron-nav2-voxel-grid: 1.2.9-1 → 1.2.10-1
  • ros-iron-nav2-voxel-grid-dbgsym: 1.2.9-1 → 1.2.10-1
  • ros-iron-nav2-waypoint-follower: 1.2.9-1 → 1.2.10-1
  • ros-iron-nav2-waypoint-follower-dbgsym: 1.2.9-1 → 1.2.10-1
  • ros-iron-navigation2: 1.2.9-1 → 1.2.10-1
  • ros-iron-pid-controller: 3.26.1-1 → 3.26.2-1
  • ros-iron-pid-controller-dbgsym: 3.26.1-1 → 3.26.2-1
  • ros-iron-pose-cov-ops: 0.3.11-1 → 0.3.12-1
  • ros-iron-pose-cov-ops-dbgsym: 0.3.11-1 → 0.3.12-1
  • ros-iron-position-controllers: 3.26.1-1 → 3.26.2-1
  • ros-iron-position-controllers-dbgsym: 3.26.1-1 → 3.26.2-1
  • ros-iron-range-sensor-broadcaster: 3.26.1-1 → 3.26.2-1
  • ros-iron-range-sensor-broadcaster-dbgsym: 3.26.1-1 → 3.26.2-1
  • ros-iron-robot-localization: 3.7.0-1 → 3.7.1-1
  • ros-iron-robot-localization-dbgsym: 3.7.0-1 → 3.7.1-1
  • ros-iron-robotraconteur: 1.1.1-1 → 1.2.2-1
  • ros-iron-robotraconteur-dbgsym: 1.1.1-1 → 1.2.2-1
  • ros-iron-ros2-control: 3.27.0-1 → 3.28.0-1
  • ros-iron-ros2-control-test-assets: 3.27.0-1 → 3.28.0-1
  • ros-iron-ros2-controllers: 3.26.1-1 → 3.26.2-1
  • ros-iron-ros2-controllers-test-nodes: 3.26.1-1 → 3.26.2-1
  • ros-iron-ros2controlcli: 3.27.0-1 → 3.28.0-1
  • ros-iron-rqt-controller-manager: 3.27.0-1 → 3.28.0-1
  • ros-iron-rqt-joint-trajectory-controller: 3.26.1-1 → 3.26.2-1
  • ros-iron-steering-controllers-library: 3.26.1-1 → 3.26.2-1
  • ros-iron-steering-controllers-library-dbgsym: 3.26.1-1 → 3.26.2-1
  • ros-iron-teleop-tools: 1.5.0-1 → 1.5.1-1
  • ros-iron-teleop-tools-msgs: 1.5.0-1 → 1.5.1-1
  • ros-iron-teleop-tools-msgs-dbgsym: 1.5.0-1 → 1.5.1-1
  • ros-iron-tf2: 0.31.7-1 → 0.31.8-1
  • ros-iron-tf2-bullet: 0.31.7-1 → 0.31.8-1
  • ros-iron-tf2-dbgsym: 0.31.7-1 → 0.31.8-1
  • ros-iron-tf2-eigen: 0.31.7-1 → 0.31.8-1
  • ros-iron-tf2-eigen-kdl: 0.31.7-1 → 0.31.8-1
  • ros-iron-tf2-eigen-kdl-dbgsym: 0.31.7-1 → 0.31.8-1
  • ros-iron-tf2-geometry-msgs: 0.31.7-1 → 0.31.8-1
  • ros-iron-tf2-kdl: 0.31.7-1 → 0.31.8-1
  • ros-iron-tf2-msgs: 0.31.7-1 → 0.31.8-1
  • ros-iron-tf2-msgs-dbgsym: 0.31.7-1 → 0.31.8-1
  • ros-iron-tf2-py: 0.31.7-1 → 0.31.8-1
  • ros-iron-tf2-py-dbgsym: 0.31.7-1 → 0.31.8-1
  • ros-iron-tf2-ros: 0.31.7-1 → 0.31.8-1
  • ros-iron-tf2-ros-dbgsym: 0.31.7-1 → 0.31.8-1
  • ros-iron-tf2-ros-py: 0.31.7-1 → 0.31.8-1
  • ros-iron-tf2-sensor-msgs: 0.31.7-1 → 0.31.8-1
  • ros-iron-tf2-tools: 0.31.7-1 → 0.31.8-1
  • ros-iron-transmission-interface: 3.27.0-1 → 3.28.0-1
  • ros-iron-transmission-interface-dbgsym: 3.27.0-1 → 3.28.0-1
  • ros-iron-tricycle-controller: 3.26.1-1 → 3.26.2-1
  • ros-iron-tricycle-controller-dbgsym: 3.26.1-1 → 3.26.2-1
  • ros-iron-tricycle-steering-controller: 3.26.1-1 → 3.26.2-1
  • ros-iron-tricycle-steering-controller-dbgsym: 3.26.1-1 → 3.26.2-1
  • ros-iron-velocity-controllers: 3.26.1-1 → 3.26.2-1
  • ros-iron-velocity-controllers-dbgsym: 3.26.1-1 → 3.26.2-1
  • ros-iron-warehouse-ros: 2.0.4-4 → 2.0.5-1
  • ros-iron-warehouse-ros-dbgsym: 2.0.4-4 → 2.0.5-1
  • ros-iron-warehouse-ros-sqlite: 1.0.3-3 → 1.0.5-1
  • ros-iron-warehouse-ros-sqlite-dbgsym: 1.0.3-3 → 1.0.5-1

Removed Packages [1]:

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:

  • Adam Serafin
  • Alejandro Hernandez Cordero
  • Alexey Merzlyakov
  • Bence Magyar
  • Bernd Pfrommer
  • Brian Wilcox
  • Carl Delsey
  • Carlos Orduno
  • David V. Lu!!
  • Denis Štogl
  • Enrique Fernandez
  • Frank Dellaert
  • Janne Karttunen
  • John Wason
  • Jose Luis Blanco-Claraco
  • Jose-Luis Blanco-Claraco
  • José Luis Blanco-Claraco
  • Justin Carpentier
  • Markus Bader
  • Matej Vargovcik
  • Michael Jeronimo
  • Mohammad Haghighipanah
  • MoveIt Release Team
  • Steve Macenski
  • Tom Moore
  • steve

1 post - 1 participant

Read full topic

by Yadunund on September 09, 2024 04:10 PM

September 06, 2024
ROS News for the Week of September 2nd, 2024

ROS News for the Week of September 2nd, 2024


The Indy Autonomous Challenge is happening RIGHT NOW at the Indianapolis Motor Speedway. You can watch the cars compete using the live stream link above. More coverage is available at the The Robot Report. All of the vehicles in the competition are running ROS / Autoware.



The Gazebo Ionic Test and Tutorial Party is also happening RIGHT NOW. We would love your help testing the next version of Gazebo.



The results from our survey of ROS Windows Users is now available. We would love your feedback on how ROS should support Windows 11.


41eff8975d53acee4bbb99ae615f1f50ae59a0b5_2_690x375

If you are a Fusion360 user, @ahb just released a Fusion 360 plugin to export CAD models in SDFormat, which makes them immediately available for simulation in Gazebo and visualization in RViz.



A team of ROS devs just released a ROS package for Mitsubishi line of Melfa robots.

Events

News

ROS

Got a minute? :mantelpiece_clock:

Please take a moment to try and answer a question on Robotics Stack Exchange! We really need everyone to help make the ROS community a better place!

1 post - 1 participant

Read full topic

by Katherine_Scott on September 06, 2024 08:35 PM

Research Study Participants Needed for Study on ROS Code Understanding

Are you interested in robotics and software development? Do you have experience with the Robot Operating System (ROS) and C++? We, researchers at Carnegie Mellon University, are seeking participants for a research study focused on understanding how developers comprehend the behavior of ROS components based on source code and visual diagrams.

Who Can Participate:

  • Individuals aged 18 and older living in the USA

  • Participants with a background in programming in C++ and robotics software development with the ROS framework

What Participation Involves:

  • Reading source code of open-source ROS components and/or visual diagrams

  • Answering questions regarding your understanding of the behavior of the components

  • Participating in a short interview to discuss your experience and feedback

  • The study will take approximately 60-90 min in total

  • Sessions are conducted online via Zoom

Benefits of Participation:

Contribute to research that aims to improve the robotics development experience

Receive an Amazon gift card of value 20 USD if you complete the study

How to Apply:

If you are interested in participating or would like more information, please contact Tobias Dürschmid at duerschmid@cmu.edu.

Thank you for considering this opportunity to contribute to advancements in robotics and software development. Your involvement is crucial to the success of this research!

Contact Information:

Tobias Dürschmid
duerschmid@cmu.edu
PhD Student
Software & Societal Systems Department
Carnegie Mellon University

1 post - 1 participant

Read full topic

by tobiasduerschmid on September 06, 2024 12:43 PM

New Packages for Noetic 2024-09-05

We’re happy to announce 16 new packages and 26 updates are now available in ROS Noetic. This sync was tagged as noetic/2024-09-05.

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

Package Updates for ROS Noetic

Added Packages [16]:

Updated Packages [26]:

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:

  • Adam Serafin
  • Austin Hendrix
  • Jose Luis Blanco-Claraco
  • Jose-Luis Blanco-Claraco
  • José Luis Blanco-Claraco
  • Justin Carpentier
  • Markus Bader
  • Martin Pecka
  • Nikos Koukis
  • Tom Moore
  • Vladislav Tananaev

5 posts - 3 participants

Read full topic

by sloretz on September 06, 2024 12:15 AM

Arabian Robotics and ROS Meetup - September 10th, 2024

🔧 Workshop 3: Session 3 - URDF: Joints and Plugins 🔧

Join us for Session 3 of Workshop 3, where we’ll dive into URDF(Unified Robot Description Format), beginning with a deep exploration of joints and their role in defining robot movements.

🗓� Date: 10th September 2024

� Time: 8 PM Cairo | 8 PM KSA | 9 PM Dubai

� Online at: https://buff.ly/3MUrpS5

✨ What You’ll Learn:

  1. Understanding Joints in URDF:
  • Explore the different types of joints and how they connect links to create movable parts in your robot model.
  1. Defining and Implementing Joints:
  • Learn how to accurately define and implement joints in URDF to simulate real-world robot movements.
  1. Integrating Plugins:
  • Discover how to enhance your URDF models with plugins that add advanced functionality to your robots.
  1. Practical URDF Examples:
  • Work through detailed examples, focusing on joint configurations for Skid Drive and Differential Drive Robots.

� Why Attend?

This session is designed for those who want to master the intricacies of URDF, starting with joints, which are essential for creating dynamic and realistic robot simulations in ROS. Whether you’re continuing from previous sessions or joining us now, you’ll gain practical insights and hands-on experience.

👉 Stay Connected:

📢 Don’t miss this chance to build your expertise in URDF and robot simulation! Share this with others who might be interested in advancing their robotics skills.

1 post - 1 participant

Read full topic

by khaledgabr77 on September 06, 2024 12:00 AM

September 04, 2024
Cloud Robotics Hub Launch and Next Meeting 2024-09-09

The Cloud Robotics Hub site is now live! The site is here: https://cloudroboticshub.github.io/

The site has these pages:

  • Blog, where the group links talks from guest speakers
  • Meetings, with a list of past meetings, upcoming meeting announcements, and links to group information
  • Resources, where the group keeps a curated list of Cloud Robotics resources
  • State of Cloud Robotics, where the group has published the survey results from the State of Cloud Robotics Survey

Take a look and let us know any feedback you have!

In addition, our next meeting will be 2024-09-09T17:00:00Z UTC→2024-09-09T18:00:00Z UTC, where we will discuss robotics news and any progress that group members have made towards improving cloud robotics for the whole community.

Last meeting, we agreed final tasks before the launch of the Cloud Robotics Hub website that the group is collaborating to build. The recording is here.

We are fortunate that two guest speakers have agreed to give talks in future meetings, which we will announce in the lead-up to each meeting. We are still looking for more guest speakers - if you are willing and able to give a talk on cloud robotics in future meetings, we would be happy to host you. Please reply here, message me directly, or sign up using the Guest Speaker Signup Sheet. We will record your talk and host it on YouTube as well!

The meeting link is here, and you can sign up to our calendar or our Google Group for meeting notifications.

Hopefully we will see you there!

1 post - 1 participant

Read full topic

by mikelikesrobots on September 04, 2024 09:44 PM

September 02, 2024
AGILEX robotic arm - ready to tackle any challenge!

by Agilex_Robotics on September 02, 2024 10:28 AM

August 29, 2024
🎉 Gazebo Ionic Test and Tutorial Party

Hi ROS community,

As mentioned previously we’ll be conducting a testing and tutorial party for the next Gazebo release, Ionic. If you missed the kickoff meeting for the tutorial party, here’s the video:

We’ll be partying from August 29th until Friday, September 13th, 2025. As a reminder, to sweeten the pot, we will once again be sending out Ionic t-shirts :tshirt: to the top ten tutorial party animals (those who finish reviewing the most tutorials as measured by closed tickets). Since the t-shirts will be distributed as gift codes to the Gazebo T-Spring store :point_right:you must fill out this form after you close your first ticket.:point_left: Participants must register no later than 2024-09-13T07:00:00Z UTC to be eligible for the swag give away. Additionally, every single one of the tutorial participants will be included in the Ionic release notes. Unfortunately, we’re still working on the Gazebo Ionic artwork, so our Gazebo store isn’t quite ready yet, but we should have that up before the end of the Tutorial Party.

Important Dates :calendar:

  • 2024-08-29 → 2023-09-13 Ionic Tutorial Party
  • 2024-09-16 → 2023-09-20 Internal Q&A
  • 2024-09-25 Community Meeting Demo
  • 2024-09-30 Official Release Announcement
  • 2024-10-07 Tutorial Party top contributors announced
    (potentially earlier)
  • 2024-09-30 Official Release Announcement
  • TBD Graphic Release and T-Shirt Sale – (T-shirt / art will be delayed)

You can find more details about the tutorial party and how to participate in the Gazebo community post.

2 posts - 2 participants

Read full topic

by azeey on August 29, 2024 06:32 PM

August 28, 2024
Interoperability Special Interest Group skipping September 2024

The September session of the Interoperability Special Interest group will be skipped since I’ll be travelling and won’t be available to organize the session this time.

We’ll resume as normal on the first Thursday of October, so I look forward to seeing everyone again then!

1 post - 1 participant

Read full topic

by grey on August 28, 2024 03:10 PM

[SLAM] New 3D LiDAR odometry, mapping and localization packages

Hi friends!

Today, all active ROS 2 distributions finally ship the brand-new mola_lidar_odometry package, featuring 3D LiDAR odometry & mapping from either, the most “famous” datasets (KITTI, MulRan,…) or your own ROS bags or a live robot. It can be run via a CLI, a custom GUI, or from RViz or FoxGlove.

That is just one package from an “ecosystem” of C++ libraries, ROS packages, and CLI and GUI tools, part of an attempt to “change the mindset” towards using view-based maps (dubbed simple-maps in our framework), which can then be used to generate metric maps of different types, filter them, etc. with pipelines defined as YAML files (no coding needed at all!). The core insight is: the same “simple map” should be used to generate different metric representations depending on the desired robotic task: navigation, manipulation, perception, and so on.

The LiDAR odometry algorithm itself can be fully reconfigured via a YAML file too, and extended via a plugins mechanism to define new metric map types, raw sensory data matching algorithms, etc.

This video summarizes some results and features of the project:

MOLA LiDAR odometry ROS packages - introduction 2024

Interested users should probably head to:

I’m thriving to see what feedback the ROS community gives about all these tools. Feel free of opening issues and/or pull requests in the project repos, and share your successes (or issues!) trying it with your own robotic projects! :fire::fire:

Of course, it’s an ongoing project and new features are planned for the short term, so stay tuned for more news.

JL

3 posts - 2 participants

Read full topic

by jlblancoc on August 28, 2024 02:43 PM

New packages for Humble Hawksbill 2024-08-28

Package Updates for Humble

Added Packages [62]:

  • ros-humble-andino-gz: 0.1.0-1
  • ros-humble-as2-behaviors-path-planning: 1.1.2-2
  • ros-humble-as2-behaviors-path-planning-dbgsym: 1.1.2-2
  • ros-humble-as2-core-dbgsym: 1.1.2-2
  • ros-humble-as2-external-object-to-tf: 1.1.2-2
  • ros-humble-as2-external-object-to-tf-dbgsym: 1.1.2-2
  • ros-humble-as2-geozones: 1.1.2-2
  • ros-humble-as2-geozones-dbgsym: 1.1.2-2
  • ros-humble-as2-map-server: 1.1.2-2
  • ros-humble-as2-map-server-dbgsym: 1.1.2-2
  • ros-humble-as2-platform-dji-psdk: 1.1.0-1
  • ros-humble-as2-platform-dji-psdk-dbgsym: 1.1.0-1
  • ros-humble-as2-platform-mavlink: 1.1.0-1
  • ros-humble-as2-platform-mavlink-dbgsym: 1.1.0-1
  • ros-humble-as2-platform-multirotor-simulator: 1.1.2-2
  • ros-humble-as2-platform-multirotor-simulator-dbgsym: 1.1.2-2
  • ros-humble-as2-rviz-plugins: 1.1.2-2
  • ros-humble-as2-rviz-plugins-dbgsym: 1.1.2-2
  • ros-humble-as2-visualization: 1.1.2-2
  • ros-humble-clearpath-mecanum-drive-controller: 0.1.0-1
  • ros-humble-clearpath-mecanum-drive-controller-dbgsym: 0.1.0-1
  • ros-humble-etsi-its-cam-ts-coding: 2.2.0-1
  • ros-humble-etsi-its-cam-ts-coding-dbgsym: 2.2.0-1
  • ros-humble-etsi-its-cam-ts-conversion: 2.2.0-1
  • ros-humble-etsi-its-cam-ts-msgs: 2.2.0-1
  • ros-humble-etsi-its-cam-ts-msgs-dbgsym: 2.2.0-1
  • ros-humble-kinematics-interface-pinocchio: 0.0.1-1
  • ros-humble-kinematics-interface-pinocchio-dbgsym: 0.0.1-1
  • ros-humble-mola-lidar-odometry: 0.3.1-1
  • ros-humble-mola-lidar-odometry-dbgsym: 0.3.1-1
  • ros-humble-mrpt-apps: 2.13.7-2
  • ros-humble-mrpt-apps-dbgsym: 2.13.7-2
  • ros-humble-mrpt-libapps: 2.13.7-2
  • ros-humble-mrpt-libapps-dbgsym: 2.13.7-2
  • ros-humble-mrpt-libbase: 2.13.7-2
  • ros-humble-mrpt-libbase-dbgsym: 2.13.7-2
  • ros-humble-mrpt-libgui: 2.13.7-2
  • ros-humble-mrpt-libgui-dbgsym: 2.13.7-2
  • ros-humble-mrpt-libhwdrivers: 2.13.7-2
  • ros-humble-mrpt-libhwdrivers-dbgsym: 2.13.7-2
  • ros-humble-mrpt-libmaps: 2.13.7-2
  • ros-humble-mrpt-libmaps-dbgsym: 2.13.7-2
  • ros-humble-mrpt-libmath: 2.13.7-2
  • ros-humble-mrpt-libmath-dbgsym: 2.13.7-2
  • ros-humble-mrpt-libnav: 2.13.7-2
  • ros-humble-mrpt-libnav-dbgsym: 2.13.7-2
  • ros-humble-mrpt-libobs: 2.13.7-2
  • ros-humble-mrpt-libobs-dbgsym: 2.13.7-2
  • ros-humble-mrpt-libopengl: 2.13.7-2
  • ros-humble-mrpt-libopengl-dbgsym: 2.13.7-2
  • ros-humble-mrpt-libposes: 2.13.7-2
  • ros-humble-mrpt-libposes-dbgsym: 2.13.7-2
  • ros-humble-mrpt-libros-bridge: 2.13.7-2
  • ros-humble-mrpt-libros-bridge-dbgsym: 2.13.7-2
  • ros-humble-mrpt-libslam: 2.13.7-2
  • ros-humble-mrpt-libslam-dbgsym: 2.13.7-2
  • ros-humble-mrpt-libtclap: 2.13.7-2
  • ros-humble-mrpt-tps-astar-planner: 2.1.0-1
  • ros-humble-mrpt-tps-astar-planner-dbgsym: 2.1.0-1
  • ros-humble-neo-nav2-bringup: 1.0.1-1
  • ros-humble-omni-base-rgbd-sensors: 2.2.1-1
  • ros-humble-pcl-ros-dbgsym: 2.4.5-2

Updated Packages [407]:

  • ros-humble-ackermann-steering-controller: 2.37.0-1 → 2.37.2-1
  • ros-humble-ackermann-steering-controller-dbgsym: 2.37.0-1 → 2.37.2-1
  • ros-humble-admittance-controller: 2.37.0-1 → 2.37.2-1
  • ros-humble-admittance-controller-dbgsym: 2.37.0-1 → 2.37.2-1
  • ros-humble-aerostack2: 1.0.9-1 → 1.1.2-2
  • ros-humble-as2-alphanumeric-viewer: 1.0.9-1 → 1.1.2-2
  • ros-humble-as2-alphanumeric-viewer-dbgsym: 1.0.9-1 → 1.1.2-2
  • ros-humble-as2-behavior: 1.0.9-1 → 1.1.2-2
  • ros-humble-as2-behavior-dbgsym: 1.0.9-1 → 1.1.2-2
  • ros-humble-as2-behavior-tree: 1.0.9-1 → 1.1.2-2
  • ros-humble-as2-behavior-tree-dbgsym: 1.0.9-1 → 1.1.2-2
  • ros-humble-as2-behaviors-motion: 1.0.9-1 → 1.1.2-2
  • ros-humble-as2-behaviors-motion-dbgsym: 1.0.9-1 → 1.1.2-2
  • ros-humble-as2-behaviors-perception: 1.0.9-1 → 1.1.2-2
  • ros-humble-as2-behaviors-perception-dbgsym: 1.0.9-1 → 1.1.2-2
  • ros-humble-as2-behaviors-platform: 1.0.9-1 → 1.1.2-2
  • ros-humble-as2-behaviors-platform-dbgsym: 1.0.9-1 → 1.1.2-2
  • ros-humble-as2-behaviors-trajectory-generation: 1.0.9-1 → 1.1.2-2
  • ros-humble-as2-behaviors-trajectory-generation-dbgsym: 1.0.9-1 → 1.1.2-2
  • ros-humble-as2-cli: 1.0.9-1 → 1.1.2-2
  • ros-humble-as2-core: 1.0.9-1 → 1.1.2-2
  • ros-humble-as2-gazebo-assets: 1.0.9-1 → 1.1.2-2
  • ros-humble-as2-gazebo-assets-dbgsym: 1.0.9-1 → 1.1.2-2
  • ros-humble-as2-keyboard-teleoperation: 1.0.9-1 → 1.1.2-2
  • ros-humble-as2-motion-controller: 1.0.9-1 → 1.1.2-2
  • ros-humble-as2-motion-controller-dbgsym: 1.0.9-1 → 1.1.2-2
  • ros-humble-as2-motion-reference-handlers: 1.0.9-1 → 1.1.2-2
  • ros-humble-as2-msgs: 1.0.9-1 → 1.1.2-2
  • ros-humble-as2-msgs-dbgsym: 1.0.9-1 → 1.1.2-2
  • ros-humble-as2-platform-crazyflie: 1.0.9-1 → 1.1.0-3
  • ros-humble-as2-platform-crazyflie-dbgsym: 1.0.9-1 → 1.1.0-3
  • ros-humble-as2-platform-dji-osdk: 1.0.9-1 → 1.1.0-1
  • ros-humble-as2-platform-dji-osdk-dbgsym: 1.0.9-1 → 1.1.0-1
  • ros-humble-as2-platform-gazebo: 1.0.9-1 → 1.1.2-2
  • ros-humble-as2-platform-gazebo-dbgsym: 1.0.9-1 → 1.1.2-2
  • ros-humble-as2-platform-tello: 1.0.9-1 → 1.1.0-4
  • ros-humble-as2-platform-tello-dbgsym: 1.0.9-1 → 1.1.0-4
  • ros-humble-as2-python-api: 1.0.9-1 → 1.1.2-2
  • ros-humble-as2-realsense-interface: 1.0.9-1 → 1.1.2-2
  • ros-humble-as2-realsense-interface-dbgsym: 1.0.9-1 → 1.1.2-2
  • ros-humble-as2-state-estimator: 1.0.9-1 → 1.1.2-2
  • ros-humble-as2-state-estimator-dbgsym: 1.0.9-1 → 1.1.2-2
  • ros-humble-as2-usb-camera-interface: 1.0.9-1 → 1.1.2-2
  • ros-humble-as2-usb-camera-interface-dbgsym: 1.0.9-1 → 1.1.2-2
  • ros-humble-bicycle-steering-controller: 2.37.0-1 → 2.37.2-1
  • ros-humble-bicycle-steering-controller-dbgsym: 2.37.0-1 → 2.37.2-1
  • ros-humble-camera-calibration: 3.0.5-1 → 3.0.6-1
  • ros-humble-clearpath-common: 0.2.10-1 → 0.2.11-1
  • ros-humble-clearpath-config: 0.2.10-1 → 0.2.11-1
  • ros-humble-clearpath-control: 0.2.10-1 → 0.2.11-1
  • ros-humble-clearpath-customization: 0.2.10-1 → 0.2.11-1
  • ros-humble-clearpath-description: 0.2.10-1 → 0.2.11-1
  • ros-humble-clearpath-generator-common: 0.2.10-1 → 0.2.11-1
  • ros-humble-clearpath-mounts-description: 0.2.10-1 → 0.2.11-1
  • ros-humble-clearpath-platform: 0.2.10-1 → 0.2.11-1
  • ros-humble-clearpath-platform-dbgsym: 0.2.10-1 → 0.2.11-1
  • ros-humble-clearpath-platform-description: 0.2.10-1 → 0.2.11-1
  • ros-humble-clearpath-sensors-description: 0.2.10-1 → 0.2.11-1
  • ros-humble-controller-interface: 2.42.0-1 → 2.43.0-1
  • ros-humble-controller-interface-dbgsym: 2.42.0-1 → 2.43.0-1
  • ros-humble-controller-manager: 2.42.0-1 → 2.43.0-1
  • ros-humble-controller-manager-dbgsym: 2.42.0-1 → 2.43.0-1
  • ros-humble-controller-manager-msgs: 2.42.0-1 → 2.43.0-1
  • ros-humble-controller-manager-msgs-dbgsym: 2.42.0-1 → 2.43.0-1
  • ros-humble-costmap-queue: 1.1.15-1 → 1.1.16-1
  • ros-humble-costmap-queue-dbgsym: 1.1.15-1 → 1.1.16-1
  • ros-humble-depth-image-proc: 3.0.5-1 → 3.0.6-1
  • ros-humble-depth-image-proc-dbgsym: 3.0.5-1 → 3.0.6-1
  • ros-humble-depthai: 2.26.1-1 → 2.28.0-1
  • ros-humble-depthai-dbgsym: 2.26.1-1 → 2.28.0-1
  • ros-humble-diff-drive-controller: 2.37.0-1 → 2.37.2-1
  • ros-humble-diff-drive-controller-dbgsym: 2.37.0-1 → 2.37.2-1
  • ros-humble-dwb-core: 1.1.15-1 → 1.1.16-1
  • ros-humble-dwb-core-dbgsym: 1.1.15-1 → 1.1.16-1
  • ros-humble-dwb-critics: 1.1.15-1 → 1.1.16-1
  • ros-humble-dwb-critics-dbgsym: 1.1.15-1 → 1.1.16-1
  • ros-humble-dwb-msgs: 1.1.15-1 → 1.1.16-1
  • ros-humble-dwb-msgs-dbgsym: 1.1.15-1 → 1.1.16-1
  • ros-humble-dwb-plugins: 1.1.15-1 → 1.1.16-1
  • ros-humble-dwb-plugins-dbgsym: 1.1.15-1 → 1.1.16-1
  • ros-humble-effort-controllers: 2.37.0-1 → 2.37.2-1
  • ros-humble-effort-controllers-dbgsym: 2.37.0-1 → 2.37.2-1
  • ros-humble-etsi-its-cam-coding: 2.1.0-1 → 2.2.0-1
  • ros-humble-etsi-its-cam-coding-dbgsym: 2.1.0-1 → 2.2.0-1
  • ros-humble-etsi-its-cam-conversion: 2.1.0-1 → 2.2.0-1
  • ros-humble-etsi-its-cam-msgs: 2.1.0-1 → 2.2.0-1
  • ros-humble-etsi-its-cam-msgs-dbgsym: 2.1.0-1 → 2.2.0-1
  • ros-humble-etsi-its-coding: 2.1.0-1 → 2.2.0-1
  • ros-humble-etsi-its-conversion: 2.1.0-1 → 2.2.0-1
  • ros-humble-etsi-its-conversion-dbgsym: 2.1.0-1 → 2.2.0-1
  • ros-humble-etsi-its-cpm-ts-coding: 2.1.0-1 → 2.2.0-1
  • ros-humble-etsi-its-cpm-ts-coding-dbgsym: 2.1.0-1 → 2.2.0-1
  • ros-humble-etsi-its-cpm-ts-conversion: 2.1.0-1 → 2.2.0-1
  • ros-humble-etsi-its-cpm-ts-msgs: 2.1.0-1 → 2.2.0-1
  • ros-humble-etsi-its-cpm-ts-msgs-dbgsym: 2.1.0-1 → 2.2.0-1
  • ros-humble-etsi-its-denm-coding: 2.1.0-1 → 2.2.0-1
  • ros-humble-etsi-its-denm-coding-dbgsym: 2.1.0-1 → 2.2.0-1
  • ros-humble-etsi-its-denm-conversion: 2.1.0-1 → 2.2.0-1
  • ros-humble-etsi-its-denm-msgs: 2.1.0-1 → 2.2.0-1
  • ros-humble-etsi-its-denm-msgs-dbgsym: 2.1.0-1 → 2.2.0-1
  • ros-humble-etsi-its-messages: 2.1.0-1 → 2.2.0-1
  • ros-humble-etsi-its-msgs: 2.1.0-1 → 2.2.0-1
  • ros-humble-etsi-its-msgs-utils: 2.1.0-1 → 2.2.0-1
  • ros-humble-etsi-its-primitives-conversion: 2.1.0-1 → 2.2.0-1
  • ros-humble-etsi-its-rviz-plugins: 2.1.0-1 → 2.2.0-1
  • ros-humble-etsi-its-rviz-plugins-dbgsym: 2.1.0-1 → 2.2.0-1
  • ros-humble-fields2cover: 2.0.0-10 → 2.0.0-11
  • ros-humble-fields2cover-dbgsym: 2.0.0-10 → 2.0.0-11
  • ros-humble-force-torque-sensor-broadcaster: 2.37.0-1 → 2.37.2-1
  • ros-humble-force-torque-sensor-broadcaster-dbgsym: 2.37.0-1 → 2.37.2-1
  • ros-humble-forward-command-controller: 2.37.0-1 → 2.37.2-1
  • ros-humble-forward-command-controller-dbgsym: 2.37.0-1 → 2.37.2-1
  • ros-humble-gripper-controllers: 2.37.0-1 → 2.37.2-1
  • ros-humble-gripper-controllers-dbgsym: 2.37.0-1 → 2.37.2-1
  • ros-humble-hardware-interface: 2.42.0-1 → 2.43.0-1
  • ros-humble-hardware-interface-dbgsym: 2.42.0-1 → 2.43.0-1
  • ros-humble-hardware-interface-testing: 2.42.0-1 → 2.43.0-1
  • ros-humble-hardware-interface-testing-dbgsym: 2.42.0-1 → 2.43.0-1
  • ros-humble-image-pipeline: 3.0.5-1 → 3.0.6-1
  • ros-humble-image-proc: 3.0.5-1 → 3.0.6-1
  • ros-humble-image-proc-dbgsym: 3.0.5-1 → 3.0.6-1
  • ros-humble-image-publisher: 3.0.5-1 → 3.0.6-1
  • ros-humble-image-publisher-dbgsym: 3.0.5-1 → 3.0.6-1
  • ros-humble-image-rotate: 3.0.5-1 → 3.0.6-1
  • ros-humble-image-rotate-dbgsym: 3.0.5-1 → 3.0.6-1
  • ros-humble-image-view: 3.0.5-1 → 3.0.6-1
  • ros-humble-image-view-dbgsym: 3.0.5-1 → 3.0.6-1
  • ros-humble-imu-sensor-broadcaster: 2.37.0-1 → 2.37.2-1
  • ros-humble-imu-sensor-broadcaster-dbgsym: 2.37.0-1 → 2.37.2-1
  • ros-humble-joint-limits: 2.42.0-1 → 2.43.0-1
  • ros-humble-joint-limits-dbgsym: 2.42.0-1 → 2.43.0-1
  • ros-humble-joint-state-broadcaster: 2.37.0-1 → 2.37.2-1
  • ros-humble-joint-state-broadcaster-dbgsym: 2.37.0-1 → 2.37.2-1
  • ros-humble-joint-trajectory-controller: 2.37.0-1 → 2.37.2-1
  • ros-humble-joint-trajectory-controller-dbgsym: 2.37.0-1 → 2.37.2-1
  • ros-humble-kitti-metrics-eval: 1.0.8-1 → 1.1.1-1
  • ros-humble-kitti-metrics-eval-dbgsym: 1.0.8-1 → 1.1.1-1
  • ros-humble-launch-pal: 0.1.15-1 → 0.3.0-1
  • ros-humble-mapviz: 2.2.1-1 → 2.4.2-1
  • ros-humble-mapviz-dbgsym: 2.2.1-1 → 2.4.2-1
  • ros-humble-mapviz-interfaces: 2.2.1-1 → 2.4.2-1
  • ros-humble-mapviz-interfaces-dbgsym: 2.2.1-1 → 2.4.2-1
  • ros-humble-mapviz-plugins: 2.2.1-1 → 2.4.2-1
  • ros-humble-mapviz-plugins-dbgsym: 2.2.1-1 → 2.4.2-1
  • ros-humble-marti-can-msgs: 1.5.2-1 → 1.6.0-1
  • ros-humble-marti-can-msgs-dbgsym: 1.5.2-1 → 1.6.0-1
  • ros-humble-marti-common-msgs: 1.5.2-1 → 1.6.0-1
  • ros-humble-marti-common-msgs-dbgsym: 1.5.2-1 → 1.6.0-1
  • ros-humble-marti-dbw-msgs: 1.5.2-1 → 1.6.0-1
  • ros-humble-marti-dbw-msgs-dbgsym: 1.5.2-1 → 1.6.0-1
  • ros-humble-marti-introspection-msgs: 1.5.2-1 → 1.6.0-1
  • ros-humble-marti-introspection-msgs-dbgsym: 1.5.2-1 → 1.6.0-1
  • ros-humble-marti-nav-msgs: 1.5.2-1 → 1.6.0-1
  • ros-humble-marti-nav-msgs-dbgsym: 1.5.2-1 → 1.6.0-1
  • ros-humble-marti-perception-msgs: 1.5.2-1 → 1.6.0-1
  • ros-humble-marti-perception-msgs-dbgsym: 1.5.2-1 → 1.6.0-1
  • ros-humble-marti-sensor-msgs: 1.5.2-1 → 1.6.0-1
  • ros-humble-marti-sensor-msgs-dbgsym: 1.5.2-1 → 1.6.0-1
  • ros-humble-marti-status-msgs: 1.5.2-1 → 1.6.0-1
  • ros-humble-marti-status-msgs-dbgsym: 1.5.2-1 → 1.6.0-1
  • ros-humble-marti-visualization-msgs: 1.5.2-1 → 1.6.0-1
  • ros-humble-marti-visualization-msgs-dbgsym: 1.5.2-1 → 1.6.0-1
  • ros-humble-message-filters: 4.3.4-1 → 4.3.5-1
  • ros-humble-message-filters-dbgsym: 4.3.4-1 → 4.3.5-1
  • ros-humble-mola: 1.0.8-1 → 1.1.1-1
  • ros-humble-mola-bridge-ros2: 1.0.8-1 → 1.1.1-1
  • ros-humble-mola-bridge-ros2-dbgsym: 1.0.8-1 → 1.1.1-1
  • ros-humble-mola-common: 0.3.1-1 → 0.4.0-1
  • ros-humble-mola-demos: 1.0.8-1 → 1.1.1-1
  • ros-humble-mola-imu-preintegration: 1.0.8-1 → 1.1.1-1
  • ros-humble-mola-imu-preintegration-dbgsym: 1.0.8-1 → 1.1.1-1
  • ros-humble-mola-input-euroc-dataset: 1.0.8-1 → 1.1.1-1
  • ros-humble-mola-input-euroc-dataset-dbgsym: 1.0.8-1 → 1.1.1-1
  • ros-humble-mola-input-kitti-dataset: 1.0.8-1 → 1.1.1-1
  • ros-humble-mola-input-kitti-dataset-dbgsym: 1.0.8-1 → 1.1.1-1
  • ros-humble-mola-input-kitti360-dataset: 1.0.8-1 → 1.1.1-1
  • ros-humble-mola-input-kitti360-dataset-dbgsym: 1.0.8-1 → 1.1.1-1
  • ros-humble-mola-input-mulran-dataset: 1.0.8-1 → 1.1.1-1
  • ros-humble-mola-input-mulran-dataset-dbgsym: 1.0.8-1 → 1.1.1-1
  • ros-humble-mola-input-paris-luco-dataset: 1.0.8-1 → 1.1.1-1
  • ros-humble-mola-input-paris-luco-dataset-dbgsym: 1.0.8-1 → 1.1.1-1
  • ros-humble-mola-input-rawlog: 1.0.8-1 → 1.1.1-1
  • ros-humble-mola-input-rawlog-dbgsym: 1.0.8-1 → 1.1.1-1
  • ros-humble-mola-input-rosbag2: 1.0.8-1 → 1.1.1-1
  • ros-humble-mola-input-rosbag2-dbgsym: 1.0.8-1 → 1.1.1-1
  • ros-humble-mola-kernel: 1.0.8-1 → 1.1.1-1
  • ros-humble-mola-kernel-dbgsym: 1.0.8-1 → 1.1.1-1
  • ros-humble-mola-launcher: 1.0.8-1 → 1.1.1-1
  • ros-humble-mola-launcher-dbgsym: 1.0.8-1 → 1.1.1-1
  • ros-humble-mola-metric-maps: 1.0.8-1 → 1.1.1-1
  • ros-humble-mola-metric-maps-dbgsym: 1.0.8-1 → 1.1.1-1
  • ros-humble-mola-msgs: 1.0.8-1 → 1.1.1-1
  • ros-humble-mola-msgs-dbgsym: 1.0.8-1 → 1.1.1-1
  • ros-humble-mola-navstate-fg: 1.0.8-1 → 1.1.1-1
  • ros-humble-mola-navstate-fg-dbgsym: 1.0.8-1 → 1.1.1-1
  • ros-humble-mola-navstate-fuse: 1.0.8-1 → 1.1.1-1
  • ros-humble-mola-navstate-fuse-dbgsym: 1.0.8-1 → 1.1.1-1
  • ros-humble-mola-pose-list: 1.0.8-1 → 1.1.1-1
  • ros-humble-mola-pose-list-dbgsym: 1.0.8-1 → 1.1.1-1
  • ros-humble-mola-relocalization: 1.0.8-1 → 1.1.1-1
  • ros-humble-mola-relocalization-dbgsym: 1.0.8-1 → 1.1.1-1
  • ros-humble-mola-traj-tools: 1.0.8-1 → 1.1.1-1
  • ros-humble-mola-traj-tools-dbgsym: 1.0.8-1 → 1.1.1-1
  • ros-humble-mola-viz: 1.0.8-1 → 1.1.1-1
  • ros-humble-mola-viz-dbgsym: 1.0.8-1 → 1.1.1-1
  • ros-humble-mola-yaml: 1.0.8-1 → 1.1.1-1
  • ros-humble-mola-yaml-dbgsym: 1.0.8-1 → 1.1.1-1
  • ros-humble-mp2p-icp: 1.5.2-1 → 1.5.3-1
  • ros-humble-mp2p-icp-dbgsym: 1.5.2-1 → 1.5.3-1
  • ros-humble-mrpt-generic-sensor: 0.2.1-1 → 0.2.2-1
  • ros-humble-mrpt-generic-sensor-dbgsym: 0.2.1-1 → 0.2.2-1
  • ros-humble-mrpt-map-server: 2.0.1-1 → 2.1.0-1
  • ros-humble-mrpt-map-server-dbgsym: 2.0.1-1 → 2.1.0-1
  • ros-humble-mrpt-msgs-bridge: 2.0.1-1 → 2.1.0-1
  • ros-humble-mrpt-nav-interfaces: 2.0.1-1 → 2.1.0-1
  • ros-humble-mrpt-nav-interfaces-dbgsym: 2.0.1-1 → 2.1.0-1
  • ros-humble-mrpt-navigation: 2.0.1-1 → 2.1.0-1
  • ros-humble-mrpt-pf-localization: 2.0.1-1 → 2.1.0-1
  • ros-humble-mrpt-pf-localization-dbgsym: 2.0.1-1 → 2.1.0-1
  • ros-humble-mrpt-pointcloud-pipeline: 2.0.1-1 → 2.1.0-1
  • ros-humble-mrpt-pointcloud-pipeline-dbgsym: 2.0.1-1 → 2.1.0-1
  • ros-humble-mrpt-rawlog: 2.0.1-1 → 2.1.0-1
  • ros-humble-mrpt-rawlog-dbgsym: 2.0.1-1 → 2.1.0-1
  • ros-humble-mrpt-reactivenav2d: 2.0.1-1 → 2.1.0-1
  • ros-humble-mrpt-reactivenav2d-dbgsym: 2.0.1-1 → 2.1.0-1
  • ros-humble-mrpt-sensor-bumblebee-stereo: 0.2.1-1 → 0.2.2-1
  • ros-humble-mrpt-sensor-bumblebee-stereo-dbgsym: 0.2.1-1 → 0.2.2-1
  • ros-humble-mrpt-sensor-gnss-nmea: 0.2.1-1 → 0.2.2-1
  • ros-humble-mrpt-sensor-gnss-nmea-dbgsym: 0.2.1-1 → 0.2.2-1
  • ros-humble-mrpt-sensor-gnss-novatel: 0.2.1-1 → 0.2.2-1
  • ros-humble-mrpt-sensor-gnss-novatel-dbgsym: 0.2.1-1 → 0.2.2-1
  • ros-humble-mrpt-sensor-imu-taobotics: 0.2.1-1 → 0.2.2-1
  • ros-humble-mrpt-sensor-imu-taobotics-dbgsym: 0.2.1-1 → 0.2.2-1
  • ros-humble-mrpt-sensorlib: 0.2.1-1 → 0.2.2-1
  • ros-humble-mrpt-sensors: 0.2.1-1 → 0.2.2-1
  • ros-humble-mrpt-tutorials: 2.0.1-1 → 2.1.0-1
  • ros-humble-mrpt2: 2.13.4-1 → 2.13.5-1
  • ros-humble-mrpt2-dbgsym: 2.13.4-1 → 2.13.5-1
  • ros-humble-mrt-cmake-modules: 1.0.9-3 → 1.0.10-1
  • ros-humble-multires-image: 2.2.1-1 → 2.4.2-1
  • ros-humble-multires-image-dbgsym: 2.2.1-1 → 2.4.2-1
  • ros-humble-nav-2d-msgs: 1.1.15-1 → 1.1.16-1
  • ros-humble-nav-2d-msgs-dbgsym: 1.1.15-1 → 1.1.16-1
  • ros-humble-nav-2d-utils: 1.1.15-1 → 1.1.16-1
  • ros-humble-nav-2d-utils-dbgsym: 1.1.15-1 → 1.1.16-1
  • ros-humble-nav2-amcl: 1.1.15-1 → 1.1.16-1
  • ros-humble-nav2-amcl-dbgsym: 1.1.15-1 → 1.1.16-1
  • ros-humble-nav2-behavior-tree: 1.1.15-1 → 1.1.16-1
  • ros-humble-nav2-behavior-tree-dbgsym: 1.1.15-1 → 1.1.16-1
  • ros-humble-nav2-behaviors: 1.1.15-1 → 1.1.16-1
  • ros-humble-nav2-behaviors-dbgsym: 1.1.15-1 → 1.1.16-1
  • ros-humble-nav2-bringup: 1.1.15-1 → 1.1.16-1
  • ros-humble-nav2-bt-navigator: 1.1.15-1 → 1.1.16-1
  • ros-humble-nav2-bt-navigator-dbgsym: 1.1.15-1 → 1.1.16-1
  • ros-humble-nav2-collision-monitor: 1.1.15-1 → 1.1.16-1
  • ros-humble-nav2-collision-monitor-dbgsym: 1.1.15-1 → 1.1.16-1
  • ros-humble-nav2-common: 1.1.15-1 → 1.1.16-1
  • ros-humble-nav2-constrained-smoother: 1.1.15-1 → 1.1.16-1
  • ros-humble-nav2-constrained-smoother-dbgsym: 1.1.15-1 → 1.1.16-1
  • ros-humble-nav2-controller: 1.1.15-1 → 1.1.16-1
  • ros-humble-nav2-controller-dbgsym: 1.1.15-1 → 1.1.16-1
  • ros-humble-nav2-core: 1.1.15-1 → 1.1.16-1
  • ros-humble-nav2-costmap-2d: 1.1.15-1 → 1.1.16-1
  • ros-humble-nav2-costmap-2d-dbgsym: 1.1.15-1 → 1.1.16-1
  • ros-humble-nav2-dwb-controller: 1.1.15-1 → 1.1.16-1
  • ros-humble-nav2-graceful-controller: 1.1.15-1 → 1.1.16-1
  • ros-humble-nav2-graceful-controller-dbgsym: 1.1.15-1 → 1.1.16-1
  • ros-humble-nav2-lifecycle-manager: 1.1.15-1 → 1.1.16-1
  • ros-humble-nav2-lifecycle-manager-dbgsym: 1.1.15-1 → 1.1.16-1
  • ros-humble-nav2-map-server: 1.1.15-1 → 1.1.16-1
  • ros-humble-nav2-map-server-dbgsym: 1.1.15-1 → 1.1.16-1
  • ros-humble-nav2-mppi-controller: 1.1.15-1 → 1.1.16-1
  • ros-humble-nav2-mppi-controller-dbgsym: 1.1.15-1 → 1.1.16-1
  • ros-humble-nav2-msgs: 1.1.15-1 → 1.1.16-1
  • ros-humble-nav2-msgs-dbgsym: 1.1.15-1 → 1.1.16-1
  • ros-humble-nav2-navfn-planner: 1.1.15-1 → 1.1.16-1
  • ros-humble-nav2-navfn-planner-dbgsym: 1.1.15-1 → 1.1.16-1
  • ros-humble-nav2-planner: 1.1.15-1 → 1.1.16-1
  • ros-humble-nav2-planner-dbgsym: 1.1.15-1 → 1.1.16-1
  • ros-humble-nav2-regulated-pure-pursuit-controller: 1.1.15-1 → 1.1.16-1
  • ros-humble-nav2-regulated-pure-pursuit-controller-dbgsym: 1.1.15-1 → 1.1.16-1
  • ros-humble-nav2-rotation-shim-controller: 1.1.15-1 → 1.1.16-1
  • ros-humble-nav2-rotation-shim-controller-dbgsym: 1.1.15-1 → 1.1.16-1
  • ros-humble-nav2-rviz-plugins: 1.1.15-1 → 1.1.16-1
  • ros-humble-nav2-rviz-plugins-dbgsym: 1.1.15-1 → 1.1.16-1
  • ros-humble-nav2-simple-commander: 1.1.15-1 → 1.1.16-1
  • ros-humble-nav2-smac-planner: 1.1.15-1 → 1.1.16-1
  • ros-humble-nav2-smac-planner-dbgsym: 1.1.15-1 → 1.1.16-1
  • ros-humble-nav2-smoother: 1.1.15-1 → 1.1.16-1
  • ros-humble-nav2-smoother-dbgsym: 1.1.15-1 → 1.1.16-1
  • ros-humble-nav2-system-tests: 1.1.15-1 → 1.1.16-1
  • ros-humble-nav2-system-tests-dbgsym: 1.1.15-1 → 1.1.16-1
  • ros-humble-nav2-theta-star-planner: 1.1.15-1 → 1.1.16-1
  • ros-humble-nav2-theta-star-planner-dbgsym: 1.1.15-1 → 1.1.16-1
  • ros-humble-nav2-util: 1.1.15-1 → 1.1.16-1
  • ros-humble-nav2-util-dbgsym: 1.1.15-1 → 1.1.16-1
  • ros-humble-nav2-velocity-smoother: 1.1.15-1 → 1.1.16-1
  • ros-humble-nav2-velocity-smoother-dbgsym: 1.1.15-1 → 1.1.16-1
  • ros-humble-nav2-voxel-grid: 1.1.15-1 → 1.1.16-1
  • ros-humble-nav2-voxel-grid-dbgsym: 1.1.15-1 → 1.1.16-1
  • ros-humble-nav2-waypoint-follower: 1.1.15-1 → 1.1.16-1
  • ros-humble-nav2-waypoint-follower-dbgsym: 1.1.15-1 → 1.1.16-1
  • ros-humble-navigation2: 1.1.15-1 → 1.1.16-1
  • ros-humble-omni-base-2dnav: 2.0.7-1 → 2.2.1-1
  • ros-humble-omni-base-bringup: 2.0.18-1 → 2.2.0-1
  • ros-humble-omni-base-controller-configuration: 2.0.18-1 → 2.2.0-1
  • ros-humble-omni-base-description: 2.0.18-1 → 2.2.0-1
  • ros-humble-omni-base-gazebo: 2.0.3-1 → 2.0.9-1
  • ros-humble-omni-base-laser-sensors: 2.0.7-1 → 2.2.1-1
  • ros-humble-omni-base-navigation: 2.0.7-1 → 2.2.1-1
  • ros-humble-omni-base-robot: 2.0.18-1 → 2.2.0-1
  • ros-humble-omni-base-simulation: 2.0.3-1 → 2.0.9-1
  • ros-humble-ouster-msgs: 0.4.2-1 → 0.4.3-1
  • ros-humble-ouster-msgs-dbgsym: 0.4.2-1 → 0.4.3-1
  • ros-humble-pal-gripper: 3.2.0-1 → 3.3.0-1
  • ros-humble-pal-gripper-controller-configuration: 3.2.0-1 → 3.3.0-1
  • ros-humble-pal-gripper-description: 3.2.0-1 → 3.3.0-1
  • ros-humble-pal-gripper-simulation: 3.2.0-1 → 3.3.0-1
  • ros-humble-pal-hey5: 4.1.0-1 → 4.2.0-1
  • ros-humble-pal-hey5-controller-configuration: 4.1.0-1 → 4.2.0-1
  • ros-humble-pal-hey5-description: 4.1.0-1 → 4.2.0-1
  • ros-humble-pal-robotiq-controller-configuration: 2.0.3-1 → 2.2.0-1
  • ros-humble-pal-robotiq-description: 2.0.3-1 → 2.2.0-1
  • ros-humble-pal-robotiq-gripper: 2.0.3-1 → 2.2.0-1
  • ros-humble-pcl-conversions: 2.4.0-6 → 2.4.5-2
  • ros-humble-pcl-ros: 2.4.0-6 → 2.4.5-2
  • ros-humble-perception-pcl: 2.4.0-6 → 2.4.5-2
  • ros-humble-pid-controller: 2.37.0-1 → 2.37.2-1
  • ros-humble-pid-controller-dbgsym: 2.37.0-1 → 2.37.2-1
  • ros-humble-pmb2-2dnav: 4.0.21-1 → 4.1.1-1
  • ros-humble-pmb2-bringup: 5.0.25-1 → 5.1.2-1
  • ros-humble-pmb2-controller-configuration: 5.0.25-1 → 5.1.2-1
  • ros-humble-pmb2-description: 5.0.25-1 → 5.1.2-1
  • ros-humble-pmb2-laser-sensors: 4.0.21-1 → 4.1.1-1
  • ros-humble-pmb2-navigation: 4.0.21-1 → 4.1.1-1
  • ros-humble-pmb2-robot: 5.0.25-1 → 5.1.2-1
  • ros-humble-position-controllers: 2.37.0-1 → 2.37.2-1
  • ros-humble-position-controllers-dbgsym: 2.37.0-1 → 2.37.2-1
  • ros-humble-range-sensor-broadcaster: 2.37.0-1 → 2.37.2-1
  • ros-humble-range-sensor-broadcaster-dbgsym: 2.37.0-1 → 2.37.2-1
  • ros-humble-realtime-tools: 2.5.0-1 → 2.6.0-1
  • ros-humble-realtime-tools-dbgsym: 2.5.0-1 → 2.6.0-1
  • ros-humble-ros2-control: 2.42.0-1 → 2.43.0-1
  • ros-humble-ros2-control-test-assets: 2.42.0-1 → 2.43.0-1
  • ros-humble-ros2-controllers: 2.37.0-1 → 2.37.2-1
  • ros-humble-ros2-controllers-test-nodes: 2.37.0-1 → 2.37.2-1
  • ros-humble-ros2-ouster: 0.4.2-1 → 0.4.3-1
  • ros-humble-ros2-ouster-dbgsym: 0.4.2-1 → 0.4.3-1
  • ros-humble-ros2controlcli: 2.42.0-1 → 2.43.0-1
  • ros-humble-rqt-controller-manager: 2.42.0-1 → 2.43.0-1
  • ros-humble-rqt-joint-trajectory-controller: 2.37.0-1 → 2.37.2-1
  • ros-humble-rt-usb-9axisimu-driver: 2.0.2-1 → 2.1.0-2
  • ros-humble-rt-usb-9axisimu-driver-dbgsym: 2.0.2-1 → 2.1.0-2
  • ros-humble-septentrio-gnss-driver: 1.4.0-2 → 1.4.1-1
  • ros-humble-septentrio-gnss-driver-dbgsym: 1.4.0-2 → 1.4.1-1
  • ros-humble-sick-safetyscanners-base: 1.0.2-1 → 1.0.3-1
  • ros-humble-sick-safetyscanners-base-dbgsym: 1.0.2-1 → 1.0.3-1
  • ros-humble-simple-actions: 0.3.0-1 → 0.4.0-1
  • ros-humble-steering-controllers-library: 2.37.0-1 → 2.37.2-1
  • ros-humble-steering-controllers-library-dbgsym: 2.37.0-1 → 2.37.2-1
  • ros-humble-stereo-image-proc: 3.0.5-1 → 3.0.6-1
  • ros-humble-stereo-image-proc-dbgsym: 3.0.5-1 → 3.0.6-1
  • ros-humble-tf-transformations: 1.0.1-3 → 1.1.0-1
  • ros-humble-tiago-2dnav: 4.1.2-1 → 4.1.7-1
  • ros-humble-tiago-bringup: 4.2.17-1 → 4.3.0-1
  • ros-humble-tiago-controller-configuration: 4.2.17-1 → 4.3.0-1
  • ros-humble-tiago-description: 4.2.17-1 → 4.3.0-1
  • ros-humble-tiago-gazebo: 4.1.8-1 → 4.1.9-1
  • ros-humble-tiago-gazebo-dbgsym: 4.1.8-1 → 4.1.9-1
  • ros-humble-tiago-laser-sensors: 4.1.2-1 → 4.1.7-1
  • ros-humble-tiago-moveit-config: 3.0.16-1 → 3.0.18-1
  • ros-humble-tiago-navigation: 4.1.2-1 → 4.1.7-1
  • ros-humble-tiago-robot: 4.2.17-1 → 4.3.0-1
  • ros-humble-tiago-simulation: 4.1.8-1 → 4.1.9-1
  • ros-humble-tile-map: 2.2.1-1 → 2.4.2-1
  • ros-humble-tile-map-dbgsym: 2.2.1-1 → 2.4.2-1
  • ros-humble-tracetools-image-pipeline: 3.0.5-1 → 3.0.6-1
  • ros-humble-tracetools-image-pipeline-dbgsym: 3.0.5-1 → 3.0.6-1
  • ros-humble-transmission-interface: 2.42.0-1 → 2.43.0-1
  • ros-humble-transmission-interface-dbgsym: 2.42.0-1 → 2.43.0-1
  • ros-humble-tricycle-controller: 2.37.0-1 → 2.37.2-1
  • ros-humble-tricycle-controller-dbgsym: 2.37.0-1 → 2.37.2-1
  • ros-humble-tricycle-steering-controller: 2.37.0-1 → 2.37.2-1
  • ros-humble-tricycle-steering-controller-dbgsym: 2.37.0-1 → 2.37.2-1
  • ros-humble-ur-description: 2.1.5-1 → 2.1.6-1
  • ros-humble-urdf: 2.6.0-2 → 2.6.1-1
  • ros-humble-urdf-dbgsym: 2.6.0-2 → 2.6.1-1
  • ros-humble-urdf-parser-plugin: 2.6.0-2 → 2.6.1-1
  • ros-humble-velocity-controllers: 2.37.0-1 → 2.37.2-1
  • ros-humble-velocity-controllers-dbgsym: 2.37.0-1 → 2.37.2-1
  • ros-humble-warehouse-ros-sqlite: 1.0.3-1 → 1.0.4-1
  • ros-humble-warehouse-ros-sqlite-dbgsym: 1.0.3-1 → 1.0.4-1
  • ros-humble-webots-ros2: 2023.1.2-1 → 2023.1.3-1
  • ros-humble-webots-ros2-control: 2023.1.2-1 → 2023.1.3-1
  • ros-humble-webots-ros2-control-dbgsym: 2023.1.2-1 → 2023.1.3-1
  • ros-humble-webots-ros2-driver: 2023.1.2-1 → 2023.1.3-1
  • ros-humble-webots-ros2-driver-dbgsym: 2023.1.2-1 → 2023.1.3-1
  • ros-humble-webots-ros2-epuck: 2023.1.2-1 → 2023.1.3-1
  • ros-humble-webots-ros2-importer: 2023.1.2-1 → 2023.1.3-1
  • ros-humble-webots-ros2-mavic: 2023.1.2-1 → 2023.1.3-1
  • ros-humble-webots-ros2-msgs: 2023.1.2-1 → 2023.1.3-1
  • ros-humble-webots-ros2-msgs-dbgsym: 2023.1.2-1 → 2023.1.3-1
  • ros-humble-webots-ros2-tesla: 2023.1.2-1 → 2023.1.3-1
  • ros-humble-webots-ros2-tests: 2023.1.2-1 → 2023.1.3-1
  • ros-humble-webots-ros2-tiago: 2023.1.2-1 → 2023.1.3-1
  • ros-humble-webots-ros2-turtlebot: 2023.1.2-1 → 2023.1.3-1
  • ros-humble-webots-ros2-universal-robot: 2023.1.2-1 → 2023.1.3-1

Removed Packages [2]:

  • ros-humble-as2-gazebo-classic-assets
  • ros-humble-simple-actions-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:

  • Adam Serafin
  • Aina Irisarri
  • Alberto Tudela
  • Alexey Merzlyakov
  • Andrea Capodacqua
  • Bence Magyar
  • Brian Wilcox
  • CVAR-UPM
  • Carl Delsey
  • Carlos Orduno
  • Chris Lalancette
  • Computer Vision And Aerial Robotics Group (UPM)
  • Cyberbotics
  • David V. Lu!!
  • Denis Štogl
  • Ethan Gao
  • Felix Exner
  • Gonzalo Mier
  • Jean-Pierre Busch
  • Jordan Palacios
  • Jordi Pages
  • José Luis Blanco-Claraco
  • Kevin Rösch
  • Lennart Puck
  • Leonardo Neumarkt
  • Luis Camero
  • Mabel Zhang
  • Markus Bader
  • Matej Vargovcik
  • Michael Jeronimo
  • Mohammad Haghighipanah
  • MoveIt Release Team
  • Paul Bovbel
  • Pradheep Padmanabhan
  • RT Corporation
  • Sai Kishor Kothakota
  • Saif Sidhik
  • Southwest Research Institute
  • Steve Macenski
  • TIAGo support team
  • Tibor Dome
  • Vincent Rabaud
  • Víctor Mayoral-Vilches
  • Yue Erro

1 post - 1 participant

Read full topic

by audrow on August 28, 2024 01:52 PM

🐥 ROSCon 2024 Birds of a Feather Sessions + More

:hatched_chick: ROSCon 2024 Birds of a Feather Sessions :hatched_chick:



Hi Everyone,

I’ve got a couple of ROSCon related announcements to share! The first announcement is that you have exactly one week to register for ROSCon at the early bird rate. The early bird rate is $100 off our regular rate, and it makes attending one of our seven ROSCon workshops virtually free. The last day for early registration is 2024-09-03T07:00:00Z UTC, so don’t delay. Also, if you would like to demo your product or robot at ROSCon, we just had a couple of sponsorship slots open up. More information about sponsorship can be found in our sponsorship prospectus.

The second announcement is that we are bringing back Birds of a Feather (BoF) sessions for ROSCon 2024. :tada:

We piloted BoF sessions at ROSCon 2023 and they were so successful that we’ve decided to bring them back this year with a few tweaks. The biggest change we’re making is that we are elevating BoFs to be part of the ROSCon workshop lineup. What this means in practice is that everyone who is not participating in a full day workshop can participate in a full day of BoF sessions during day zero of ROSCon. We’re making this change so our attendees don’t have to choose between attending BoF sessions, watching ROSCon talks, and visiting our sponsor’s booths! It is worth noting that you DO NOT need to be registered for a ROSCon workshop to attend BoF sessions, all ROSCon attendees are welcome to participate!

To host a BoF session all you need to do is fill out this form! After the ROSCon executive committee reviews your submission your slot will appear on the BoF section of the ROSCon webpage (this may take a couple of days). We recommend that all ROS community groups and major package maintainers take the time to hold a BoF session during ROSCon. ROSCon attendees are also more than welcome to propose BoF sessions on whatever topic they want! Our only rule about BoF session topics is that they should not be commercial in nature, but other than that we’re open to just about any topic! We recommend you reserve your BoF slot soon, space is limited and we’re anticipating that BoF sessions are going to be very popular this year!

7 posts - 4 participants

Read full topic

by Katherine_Scott on August 28, 2024 12:01 AM

August 27, 2024
ROS Meetup Buenos Aires - September 19th

Everything is ready for the first edition of ROS Meetup in Buenos Aires!

This major gathering of the robotics community is not only coming to Buenos Aires for the first time but also to all of LATAM. Here’s all the information you need:

:date: When? September 19th, from 5 to 9 p.m.
:round_pushpin: Where? At the Faculty of Engineering, University of Buenos Aires (FIUBA)
:bookmark_tabs: How do I register? Registration is free! We invite you to sign up at the following link: ROS MEET UP BUENOS AIRES · Luma

The countdown begins! See you there?

1 post - 1 participant

Read full topic

by Sofia_Venancio on August 27, 2024 08:58 PM

ROS Meetup Bogota- September 19th

The first edition of ROS Meetup in Bogotá is underway! This exciting robotics event is coming to Bogotá for the first time and to all of LATAM, and here’s all the information you need:

:date: When? September 19th, from 5 to 9 p.m.
:round_pushpin: Where? At Pontificia Universidad Javeriana IEEE RAS Javeriana
:bookmark_tabs: How do I register? Registration is free! We invite you to sign up at the following link: ROS MEETUP BOGOTÁ · Luma

The countdown has begun, and we hope to see you there!

1 post - 1 participant

Read full topic

by Sofia_Venancio on August 27, 2024 08:58 PM

AMD x Open Navigation - Nav2 Open-Source Urban, 3D-, and Indoor Long-Duration Demonstrations using Ryzen AI

Howdy everyone, its Your Friendly Neighborhood Navigator here with exciting news. AMD and Open Navigation have been collaborating over the last several months to create demonstrations of AMD’s powerful Ryzen AI, Embedded+, and Kria capabilities for the ROS 2 community!

We’ve started by showing how you can use Ryzen AI to power your autonomous robotics products in a variety of real-world and challenging situations. These devices contain the powerful, modern AMD x86 CPUs you know and love, married with a Radeon GPU, Neutral Processing Unit (NPU), and more to run hardware accelerated and AI applications on your robot products. We have benchmarked that all of autonomous navigation, 3D perception, localization, and autonomy applications can be performed with under 15% of total resource utilization, leaving plenty of room for many user applications, advanced AI, and more – all for an amazing price point & power budget. If you are working on robotics systems and need powerful x86 cores, we definitely recommend looking into Ryzen AI.

To this end, we’ve created 3 real-world demonstrations and released all of its source code and instructions to the community to get started from! We’ll be building on top of these in the future using the AI Acceleration and Hardware Acceleration capabilities of AMD’s technologies to make it easy to deploy AI and advanced robotics algorithms.

Check out GitHub - open-navigation/opennav_amd_demonstrations: Project containing demonstrations using AMD's Ryzen AI and other technologies with ROS 2 to see the videos, download datasets, learn how to setup and use ROS 2, Nav2 for Indoor, Urban, and 3D SLAM-based navigation!

Happy Ryzening!

Steve

P.S. as a bonus: We also include a series of guides for how to bootstrap a new robot: PC, software bringup, time synchronize multiple machines, and more!

2 posts - 1 participant

Read full topic

by smac on August 27, 2024 05:58 PM

August 26, 2024
[GSoC 2024]: Migrating the Project Dave and building Physics-based Sonar Simulation for Underwater Robotics

[GSoC 2024]: Migrating the Project Dave and building Physics-based Sonar Simulation for Underwater Robotics

Organization: Open Robotics

Mentors: Mabel Zhang, Woen-sug Choi

Student: Gaurav Kumar (GauravKumar9920 (Gaurav Kumar) 路 GitHub, https://www.linkedin.com/in/gaurav-kumar-b7298220a/)

Colleagues : Helena Moyen, Rakesh Vivekanandan

Link to GSoC Project: Google Summer of Code

Hello Everyone,

This summer I was selected to work on The Project Dave along with Rakesh and Helena as part of the Google Summer of Code Program 2024. My primary focus was to migrate Project dave to ROS 2 Jazzy and Gazebo Harmonic and to develop physics-based multi-beam sonar simulation, adapting it to ROS 2 and Gazebo environments.

Throughout the program, I worked closely with my esteemed mentors, Woen-sug choi and Mabel Zhang to make contributions to the Dave repository, we worked on a new branch for the project, documented and created demos that include most of the old DAVE plugins, such as the DVL, USBL and Sea Pressure sensor. Currently, we are working on the migration of the Multibeam Sonar Plugin and wrapping up the project.

My contribution included research about the various plugins available in open source and filtering out the important plugins and sensors we need to migrate during out GSoC journey. I also developed the Sea Pressure Sensor Plugin and underwater current plugin. The project documentation is available in Notion and includes details on Native and Docker installations for Ubuntu Noble, Windows WSL, and Mac OS X.

Documentation: GSoC 2024 - Open Robotics - Dave/Multibeam Sonar

Native installation: Installation Manual (Local)

Docker installation: Installation Manual (Docker)

About me

I am a final-year undergraduate student at VJTI, Mumbai, with a strong passion for robotics. I was first introduced to robotics during my freshman year, where I had the opportunity to work with ROS (Robot Operating System) and Gazebo. This experience sparked my enthusiasm for the field and inspired me to contribute to open-source projects related to robotics.

About the project dave

DAVE (Aquatic Virtual Environment - Home | Project DAVE) is a simulation platform designed for the rapid testing and evaluation of underwater robotic solutions, specifically autonomous underwater vehicles (AUVs/UUVs) that perform missions involving autonomous manipulation. Originally built on ROS 1 Noetic and Gazebo Classic, which are set to reach their end of life in 2025, the project aims to migrate DAVE and its Multibeam Sonar plugin to the new ROS 2 and the Harmonic framework. This transition will ensure continued support and development for the simulation environment.

Sea Sensor Plugin -

The Subsea Pressure Sensor Plugin is a sensor plugin designed to simulate the behavior of a subsea pressure sensor within a Gazebo simulation environment. The plugin integrates with Gazebo, using the Gazebo and ROS 2 interfaces to publish simulated sensor data. It can also Predict the Depth of the vehicle.

Ocean Current Plugin -

(in progress)
The Ocean Current Plugin is an advanced physics plugin designed to simulate the complex behavior of ocean currents in a virtual environment. It features multiple layers, each dedicated to accurately modeling various aspects of ocean currents, such as constant and stratified flows. Additionally, the plugin is capable of replicating tidal oscillations, providing a comprehensive and realistic simulation of oceanic movements.

Ocean Current Plugin

Multibeam Sonar Plugin

(in progress)

The Multibeam Sonar plugin offers a sophisticated simulation of sonar sensors by utilizing a ray-based method rather than traditional image processing techniques. This approach effectively models acoustic signal behaviors, including phase, reverberation, and raw intensity-range data. Currently, we are developing a custom sensor leveraging the capabilities of the Gazebo GPU-Lidar and DVL (Doppler Velocity Log) sensor. The point cloud data from this sensor is accessible in Rviz, enhancing visualization and analysis capabilities.

Future developments include implementing half-precision calculations in CUDA to achieve increased refresh rates and extending the simulation to support additional sonar types.

Some documentation of the work in progress:

Multibeam Sonar: Native Installation

Multibeam Sonar Plugin Migration Memo

PR: Multibeam Sonar Migration Template by woensug-choi 路 Pull Request #15 路 IOES-Lab/dave 路 GitHub

Conclusion

This summer has been an incredible journey for me, filled with opportunities to explore underwater robotics and enhance my coding skills. Overall, the project was a success, laying a solid foundation for future developments, such as migrating additional plugins and implementing robotic manipulators.

A heartfelt thank you to my mentors, Woen-Sug Choi and Mabel Zhang, for their invaluable guidance, and to my colleagues Rakesh, Helena, and Abhi for the collaboration and shared learning over these past few months. I am also grateful to Open Robotics for their warm reception and unwavering support throughout this experience.

1 post - 1 participant

Read full topic

by GauravKumar9920 on August 26, 2024 12:51 PM

New Packages for Jazzy Jalisco 2024-08-26

Hello there folks!

We’re happy to announce 65 new packages and 201 updates are now available in ROS 2 Jazzy Jalisco :jazzy: :jazzy: :jazzy: .

This sync was tagged as jazzy/2024-08-26.

Package Updates for jazzy

Note that package counts include dbgsym packages which have been filtered out from the list below

Added Packages [65]:

  • ros-jazzy-autoware-lanelet2-extension: 0.5.0-1
  • ros-jazzy-autoware-lanelet2-extension-python: 0.5.0-1
  • ros-jazzy-battery-state-broadcaster: 1.0.0-1
  • ros-jazzy-battery-state-rviz-overlay: 1.0.0-1
  • ros-jazzy-lanelet2: 1.2.1-1
  • ros-jazzy-lanelet2-examples: 1.2.1-1
  • ros-jazzy-lanelet2-projection: 1.2.1-1
  • ros-jazzy-lanelet2-python: 1.2.1-1
  • ros-jazzy-lanelet2-validation: 1.2.1-1
  • ros-jazzy-mola-lidar-odometry: 0.3.1-1
  • ros-jazzy-mrpt-apps: 2.13.6-3
  • ros-jazzy-mrpt-libapps: 2.13.6-3
  • ros-jazzy-mrpt-libbase: 2.13.6-3
  • ros-jazzy-mrpt-libgui: 2.13.6-3
  • ros-jazzy-mrpt-libhwdrivers: 2.13.6-3
  • ros-jazzy-mrpt-libmaps: 2.13.6-3
  • ros-jazzy-mrpt-libmath: 2.13.6-3
  • ros-jazzy-mrpt-libnav: 2.13.6-3
  • ros-jazzy-mrpt-libobs: 2.13.6-3
  • ros-jazzy-mrpt-libopengl: 2.13.6-3
  • ros-jazzy-mrpt-libposes: 2.13.6-3
  • ros-jazzy-mrpt-libros2bridge: 2.13.6-3
  • ros-jazzy-mrpt-libslam: 2.13.6-3
  • ros-jazzy-mrpt-libtclap: 2.13.6-3
  • ros-jazzy-mrpt-tps-astar-planner: 2.1.0-1
  • ros-jazzy-qml-ros2-plugin: 1.0.1-1
  • ros-jazzy-ros-babel-fish: 0.9.3-1
  • ros-jazzy-ros-babel-fish-test-msgs: 0.9.3-1
  • ros-jazzy-webots-ros2: 2023.1.3-1
  • ros-jazzy-webots-ros2-control: 2023.1.3-1
  • ros-jazzy-webots-ros2-driver: 2023.1.3-1
  • ros-jazzy-webots-ros2-epuck: 2023.1.3-1
  • ros-jazzy-webots-ros2-mavic: 2023.1.3-1
  • ros-jazzy-webots-ros2-tesla: 2023.1.3-1
  • ros-jazzy-webots-ros2-tests: 2023.1.3-1
  • ros-jazzy-webots-ros2-tiago: 2023.1.3-1
  • ros-jazzy-webots-ros2-turtlebot: 2023.1.3-1
  • ros-jazzy-webots-ros2-universal-robot: 2023.1.3-1

Updated Packages [201]:

  • ros-jazzy-ackermann-steering-controller: 4.12.0-1 → 4.12.1-1
  • ros-jazzy-admittance-controller: 4.12.0-1 → 4.12.1-1
  • ros-jazzy-azure-iot-sdk-c: 1.13.0-2 → 1.14.0-1
  • ros-jazzy-bicycle-steering-controller: 4.12.0-1 → 4.12.1-1
  • ros-jazzy-camera-calibration: 5.0.3-1 → 5.0.4-1
  • ros-jazzy-depth-image-proc: 5.0.3-1 → 5.0.4-1
  • ros-jazzy-depthai: 2.26.1-1 → 2.28.0-1
  • ros-jazzy-diff-drive-controller: 4.12.0-1 → 4.12.1-1
  • ros-jazzy-effort-controllers: 4.12.0-1 → 4.12.1-1
  • ros-jazzy-fields2cover: 2.0.0-9 → 2.0.0-10
  • ros-jazzy-force-torque-sensor-broadcaster: 4.12.0-1 → 4.12.1-1
  • ros-jazzy-forward-command-controller: 4.12.0-1 → 4.12.1-1
  • ros-jazzy-gripper-controllers: 4.12.0-1 → 4.12.1-1
  • ros-jazzy-gz-fuel-tools-vendor: 0.0.4-1 → 0.0.5-1
  • ros-jazzy-gz-sim-vendor: 0.0.4-1 → 0.0.5-1
  • ros-jazzy-image-pipeline: 5.0.3-1 → 5.0.4-1
  • ros-jazzy-image-proc: 5.0.3-1 → 5.0.4-1
  • ros-jazzy-image-publisher: 5.0.3-1 → 5.0.4-1
  • ros-jazzy-image-rotate: 5.0.3-1 → 5.0.4-1
  • ros-jazzy-image-view: 5.0.3-1 → 5.0.4-1
  • ros-jazzy-imu-sensor-broadcaster: 4.12.0-1 → 4.12.1-1
  • ros-jazzy-joint-state-broadcaster: 4.12.0-1 → 4.12.1-1
  • ros-jazzy-joint-trajectory-controller: 4.12.0-1 → 4.12.1-1
  • ros-jazzy-kitti-metrics-eval: 1.0.8-1 → 1.1.0-1
  • ros-jazzy-magic-enum: 0.9.5-3 → 0.9.6-1
  • ros-jazzy-mapviz-interfaces: 2.3.0-3 → 2.4.1-1
  • ros-jazzy-marti-can-msgs: 1.5.2-3 → 1.6.0-1
  • ros-jazzy-marti-common-msgs: 1.5.2-3 → 1.6.0-1
  • ros-jazzy-marti-dbw-msgs: 1.5.2-3 → 1.6.0-1
  • ros-jazzy-marti-introspection-msgs: 1.5.2-3 → 1.6.0-1
  • ros-jazzy-marti-nav-msgs: 1.5.2-3 → 1.6.0-1
  • ros-jazzy-marti-perception-msgs: 1.5.2-3 → 1.6.0-1
  • ros-jazzy-marti-sensor-msgs: 1.5.2-3 → 1.6.0-1
  • ros-jazzy-marti-status-msgs: 1.5.2-3 → 1.6.0-1
  • ros-jazzy-marti-visualization-msgs: 1.5.2-3 → 1.6.0-1
  • ros-jazzy-mola: 1.0.8-1 → 1.1.0-1
  • ros-jazzy-mola-bridge-ros2: 1.0.8-1 → 1.1.0-1
  • ros-jazzy-mola-common: 0.3.1-1 → 0.4.0-1
  • ros-jazzy-mola-demos: 1.0.8-1 → 1.1.0-1
  • ros-jazzy-mola-imu-preintegration: 1.0.8-1 → 1.1.0-1
  • ros-jazzy-mola-input-euroc-dataset: 1.0.8-1 → 1.1.0-1
  • ros-jazzy-mola-input-kitti-dataset: 1.0.8-1 → 1.1.0-1
  • ros-jazzy-mola-input-kitti360-dataset: 1.0.8-1 → 1.1.0-1
  • ros-jazzy-mola-input-mulran-dataset: 1.0.8-1 → 1.1.0-1
  • ros-jazzy-mola-input-paris-luco-dataset: 1.0.8-1 → 1.1.0-1
  • ros-jazzy-mola-input-rawlog: 1.0.8-1 → 1.1.0-1
  • ros-jazzy-mola-input-rosbag2: 1.0.8-1 → 1.1.0-1
  • ros-jazzy-mola-kernel: 1.0.8-1 → 1.1.0-1
  • ros-jazzy-mola-launcher: 1.0.8-1 → 1.1.0-1
  • ros-jazzy-mola-metric-maps: 1.0.8-1 → 1.1.0-1
  • ros-jazzy-mola-msgs: 1.0.8-1 → 1.1.0-1
  • ros-jazzy-mola-navstate-fg: 1.0.8-1 → 1.1.0-1
  • ros-jazzy-mola-navstate-fuse: 1.0.8-1 → 1.1.0-1
  • ros-jazzy-mola-pose-list: 1.0.8-1 → 1.1.0-1
  • ros-jazzy-mola-relocalization: 1.0.8-1 → 1.1.0-1
  • ros-jazzy-mola-traj-tools: 1.0.8-1 → 1.1.0-1
  • ros-jazzy-mola-viz: 1.0.8-1 → 1.1.0-1
  • ros-jazzy-mola-yaml: 1.0.8-1 → 1.1.0-1
  • ros-jazzy-mp2p-icp: 1.5.2-1 → 1.5.3-1
  • ros-jazzy-mrpt-generic-sensor: 0.2.1-1 → 0.2.2-1
  • ros-jazzy-mrpt-map-server: 2.0.0-1 → 2.1.0-1
  • ros-jazzy-mrpt-msgs-bridge: 2.0.0-1 → 2.1.0-1
  • ros-jazzy-mrpt-nav-interfaces: 2.0.0-1 → 2.1.0-1
  • ros-jazzy-mrpt-navigation: 2.0.0-1 → 2.1.0-1
  • ros-jazzy-mrpt-pf-localization: 2.0.0-1 → 2.1.0-1
  • ros-jazzy-mrpt-pointcloud-pipeline: 2.0.0-1 → 2.1.0-1
  • ros-jazzy-mrpt-rawlog: 2.0.0-1 → 2.1.0-1
  • ros-jazzy-mrpt-reactivenav2d: 2.0.0-1 → 2.1.0-1
  • ros-jazzy-mrpt-sensor-bumblebee-stereo: 0.2.1-1 → 0.2.2-1
  • ros-jazzy-mrpt-sensor-gnss-nmea: 0.2.1-1 → 0.2.2-1
  • ros-jazzy-mrpt-sensor-gnss-novatel: 0.2.1-1 → 0.2.2-1
  • ros-jazzy-mrpt-sensor-imu-taobotics: 0.2.1-1 → 0.2.2-1
  • ros-jazzy-mrpt-sensorlib: 0.2.1-1 → 0.2.2-1
  • ros-jazzy-mrpt-sensors: 0.2.1-1 → 0.2.2-1
  • ros-jazzy-mrpt-tutorials: 2.0.0-1 → 2.1.0-1
  • ros-jazzy-mrt-cmake-modules: 1.0.9-5 → 1.0.10-1
  • ros-jazzy-ompl: 1.5.2-2 → 1.6.0-1
  • ros-jazzy-openni2-camera: 2.2.0-2 → 2.2.1-1
  • ros-jazzy-parallel-gripper-controller: 4.12.0-1 → 4.12.1-1
  • ros-jazzy-pid-controller: 4.12.0-1 → 4.12.1-1
  • ros-jazzy-position-controllers: 4.12.0-1 → 4.12.1-1
  • ros-jazzy-range-sensor-broadcaster: 4.12.0-1 → 4.12.1-1
  • ros-jazzy-realtime-tools: 2.5.0-4 → 2.6.0-1
  • ros-jazzy-ros2-controllers: 4.12.0-1 → 4.12.1-1
  • ros-jazzy-ros2-controllers-test-nodes: 4.12.0-1 → 4.12.1-1
  • ros-jazzy-rqt-joint-trajectory-controller: 4.12.0-1 → 4.12.1-1
  • ros-jazzy-rviz-assimp-vendor: 14.1.3-1 → 14.1.4-1
  • ros-jazzy-rviz-common: 14.1.3-1 → 14.1.4-1
  • ros-jazzy-rviz-default-plugins: 14.1.3-1 → 14.1.4-1
  • ros-jazzy-rviz-ogre-vendor: 14.1.3-1 → 14.1.4-1
  • ros-jazzy-rviz-rendering: 14.1.3-1 → 14.1.4-1
  • ros-jazzy-rviz-rendering-tests: 14.1.3-1 → 14.1.4-1
  • ros-jazzy-rviz-visual-testing-framework: 14.1.3-1 → 14.1.4-1
  • ros-jazzy-rviz2: 14.1.3-1 → 14.1.4-1
  • ros-jazzy-sdformat-vendor: 0.0.5-1 → 0.0.6-1
  • ros-jazzy-simple-actions: 0.3.0-3 → 0.4.0-1
  • ros-jazzy-steering-controllers-library: 4.12.0-1 → 4.12.1-1
  • ros-jazzy-stereo-image-proc: 5.0.3-1 → 5.0.4-1
  • ros-jazzy-tf-transformations: 1.0.1-5 → 1.1.0-1
  • ros-jazzy-tracetools-image-pipeline: 5.0.3-1 → 5.0.4-1
  • ros-jazzy-tricycle-controller: 4.12.0-1 → 4.12.1-1
  • ros-jazzy-tricycle-steering-controller: 4.12.0-1 → 4.12.1-1
  • ros-jazzy-ur: 2.4.8-1 → 2.4.9-1
  • ros-jazzy-ur-calibration: 2.4.8-1 → 2.4.9-1
  • ros-jazzy-ur-controllers: 2.4.8-1 → 2.4.9-1
  • ros-jazzy-ur-dashboard-msgs: 2.4.8-1 → 2.4.9-1
  • ros-jazzy-ur-description: 2.4.0-1 → 2.4.2-1
  • ros-jazzy-ur-moveit-config: 2.4.8-1 → 2.4.9-1
  • ros-jazzy-ur-robot-driver: 2.4.8-1 → 2.4.9-1
  • ros-jazzy-velocity-controllers: 4.12.0-1 → 4.12.1-1
  • ros-jazzy-warehouse-ros-sqlite: 1.0.3-4 → 1.0.4-1
  • ros-jazzy-webots-ros2-importer: 2023.1.2-4 → 2023.1.3-1
  • ros-jazzy-webots-ros2-msgs: 2023.1.2-4 → 2023.1.3-1

Removed Packages [6]:

  • ros-jazzy-mapviz
  • ros-jazzy-mapviz-dbgsym
  • ros-jazzy-multires-image
  • ros-jazzy-multires-image-dbgsym
  • ros-jazzy-tile-map
  • ros-jazzy-tile-map-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:

  • Adam Serafin
  • Addisu Z. Taddese
  • Alejandro Hernandez Cordero
  • Bence Magyar
  • Cyberbotics
  • David V. Lu!!
  • Denis Stogl
  • Denis Štogl
  • Fabian Immel
  • Felix Exner
  • Gonzalo Mier
  • Jan-Hendrik Pauls
  • Jonas Otto
  • Jose Luis Blanco-Claraco
  • Jose-Luis Blanco-Claraco
  • José Luis Blanco-Claraco
  • Kevin Rösch
  • Mamoru Sobue
  • Mark Moll
  • Markus Bader
  • Michael Ferguson
  • MoveIt Release Team
  • Neargye
  • Southwest Research Institute
  • Stefan Fabian
  • Tim Clephas
  • Vincent Rabaud
  • Víctor Mayoral-Vilches
  • mitsudome-r

1 post - 1 participant

Read full topic

by marcogg on August 26, 2024 03:48 AM

August 23, 2024
New Packages for Iron Irwini 2024-08-23

Hello everyone!

We’re happy to announce 34 new packages and 180 updates are now available in ROS 2 Iron Irwini :iron: :irwini: .

This sync was tagged as iron/2024-08-23 .

Package Updates for iron

Added Packages [34]:

Updated Packages [180]:

  • ros-iron-ackermann-steering-controller: 3.26.0-1 → 3.26.1-1
  • ros-iron-ackermann-steering-controller-dbgsym: 3.26.0-1 → 3.26.1-1
  • ros-iron-admittance-controller: 3.26.0-1 → 3.26.1-1
  • ros-iron-admittance-controller-dbgsym: 3.26.0-1 → 3.26.1-1
  • ros-iron-azure-iot-sdk-c: 1.13.0-1 → 1.14.0-2
  • ros-iron-bicycle-steering-controller: 3.26.0-1 → 3.26.1-1
  • ros-iron-bicycle-steering-controller-dbgsym: 3.26.0-1 → 3.26.1-1
  • ros-iron-camera-calibration: 4.0.1-1 → 4.0.2-1
  • ros-iron-depth-image-proc: 4.0.1-1 → 4.0.2-1
  • ros-iron-depth-image-proc-dbgsym: 4.0.1-1 → 4.0.2-1
  • ros-iron-diff-drive-controller: 3.26.0-1 → 3.26.1-1
  • ros-iron-diff-drive-controller-dbgsym: 3.26.0-1 → 3.26.1-1
  • ros-iron-effort-controllers: 3.26.0-1 → 3.26.1-1
  • ros-iron-effort-controllers-dbgsym: 3.26.0-1 → 3.26.1-1
  • ros-iron-fields2cover: 2.0.0-11 → 2.0.0-12
  • ros-iron-fields2cover-dbgsym: 2.0.0-11 → 2.0.0-12
  • ros-iron-force-torque-sensor-broadcaster: 3.26.0-1 → 3.26.1-1
  • ros-iron-force-torque-sensor-broadcaster-dbgsym: 3.26.0-1 → 3.26.1-1
  • ros-iron-forward-command-controller: 3.26.0-1 → 3.26.1-1
  • ros-iron-forward-command-controller-dbgsym: 3.26.0-1 → 3.26.1-1
  • ros-iron-gripper-controllers: 3.26.0-1 → 3.26.1-1
  • ros-iron-gripper-controllers-dbgsym: 3.26.0-1 → 3.26.1-1
  • ros-iron-image-pipeline: 4.0.1-1 → 4.0.2-1
  • ros-iron-image-proc: 4.0.1-1 → 4.0.2-1
  • ros-iron-image-proc-dbgsym: 4.0.1-1 → 4.0.2-1
  • ros-iron-image-publisher: 4.0.1-1 → 4.0.2-1
  • ros-iron-image-publisher-dbgsym: 4.0.1-1 → 4.0.2-1
  • ros-iron-image-rotate: 4.0.1-1 → 4.0.2-1
  • ros-iron-image-rotate-dbgsym: 4.0.1-1 → 4.0.2-1
  • ros-iron-image-view: 4.0.1-1 → 4.0.2-1
  • ros-iron-image-view-dbgsym: 4.0.1-1 → 4.0.2-1
  • ros-iron-imu-sensor-broadcaster: 3.26.0-1 → 3.26.1-1
  • ros-iron-imu-sensor-broadcaster-dbgsym: 3.26.0-1 → 3.26.1-1
  • ros-iron-joint-state-broadcaster: 3.26.0-1 → 3.26.1-1
  • ros-iron-joint-state-broadcaster-dbgsym: 3.26.0-1 → 3.26.1-1
  • ros-iron-joint-trajectory-controller: 3.26.0-1 → 3.26.1-1
  • ros-iron-joint-trajectory-controller-dbgsym: 3.26.0-1 → 3.26.1-1
  • ros-iron-kitti-metrics-eval: 1.0.8-1 → 1.1.0-1
  • ros-iron-kitti-metrics-eval-dbgsym: 1.0.8-1 → 1.1.0-1
  • ros-iron-mapviz: 2.2.2-1 → 2.4.2-1
  • ros-iron-mapviz-dbgsym: 2.2.2-1 → 2.4.2-1
  • ros-iron-mapviz-interfaces: 2.2.2-1 → 2.4.2-1
  • ros-iron-mapviz-interfaces-dbgsym: 2.2.2-1 → 2.4.2-1
  • ros-iron-mapviz-plugins: 2.2.2-1 → 2.4.2-1
  • ros-iron-mapviz-plugins-dbgsym: 2.2.2-1 → 2.4.2-1
  • ros-iron-marti-can-msgs: 1.5.2-1 → 1.6.0-1
  • ros-iron-marti-can-msgs-dbgsym: 1.5.2-1 → 1.6.0-1
  • ros-iron-marti-common-msgs: 1.5.2-1 → 1.6.0-1
  • ros-iron-marti-common-msgs-dbgsym: 1.5.2-1 → 1.6.0-1
  • ros-iron-marti-dbw-msgs: 1.5.2-1 → 1.6.0-1
  • ros-iron-marti-dbw-msgs-dbgsym: 1.5.2-1 → 1.6.0-1
  • ros-iron-marti-introspection-msgs: 1.5.2-1 → 1.6.0-1
  • ros-iron-marti-introspection-msgs-dbgsym: 1.5.2-1 → 1.6.0-1
  • ros-iron-marti-nav-msgs: 1.5.2-1 → 1.6.0-1
  • ros-iron-marti-nav-msgs-dbgsym: 1.5.2-1 → 1.6.0-1
  • ros-iron-marti-perception-msgs: 1.5.2-1 → 1.6.0-1
  • ros-iron-marti-perception-msgs-dbgsym: 1.5.2-1 → 1.6.0-1
  • ros-iron-marti-sensor-msgs: 1.5.2-1 → 1.6.0-1
  • ros-iron-marti-sensor-msgs-dbgsym: 1.5.2-1 → 1.6.0-1
  • ros-iron-marti-status-msgs: 1.5.2-1 → 1.6.0-1
  • ros-iron-marti-status-msgs-dbgsym: 1.5.2-1 → 1.6.0-1
  • ros-iron-marti-visualization-msgs: 1.5.2-1 → 1.6.0-1
  • ros-iron-marti-visualization-msgs-dbgsym: 1.5.2-1 → 1.6.0-1
  • ros-iron-mola: 1.0.8-1 → 1.1.0-1
  • ros-iron-mola-bridge-ros2: 1.0.8-1 → 1.1.0-1
  • ros-iron-mola-bridge-ros2-dbgsym: 1.0.8-1 → 1.1.0-1
  • ros-iron-mola-common: 0.3.1-1 → 0.4.0-1
  • ros-iron-mola-demos: 1.0.8-1 → 1.1.0-1
  • ros-iron-mola-imu-preintegration: 1.0.8-1 → 1.1.0-1
  • ros-iron-mola-imu-preintegration-dbgsym: 1.0.8-1 → 1.1.0-1
  • ros-iron-mola-input-euroc-dataset: 1.0.8-1 → 1.1.0-1
  • ros-iron-mola-input-euroc-dataset-dbgsym: 1.0.8-1 → 1.1.0-1
  • ros-iron-mola-input-kitti-dataset: 1.0.8-1 → 1.1.0-1
  • ros-iron-mola-input-kitti-dataset-dbgsym: 1.0.8-1 → 1.1.0-1
  • ros-iron-mola-input-kitti360-dataset: 1.0.8-1 → 1.1.0-1
  • ros-iron-mola-input-kitti360-dataset-dbgsym: 1.0.8-1 → 1.1.0-1
  • ros-iron-mola-input-mulran-dataset: 1.0.8-1 → 1.1.0-1
  • ros-iron-mola-input-mulran-dataset-dbgsym: 1.0.8-1 → 1.1.0-1
  • ros-iron-mola-input-paris-luco-dataset: 1.0.8-1 → 1.1.0-1
  • ros-iron-mola-input-paris-luco-dataset-dbgsym: 1.0.8-1 → 1.1.0-1
  • ros-iron-mola-input-rawlog: 1.0.8-1 → 1.1.0-1
  • ros-iron-mola-input-rawlog-dbgsym: 1.0.8-1 → 1.1.0-1
  • ros-iron-mola-input-rosbag2: 1.0.8-1 → 1.1.0-1
  • ros-iron-mola-input-rosbag2-dbgsym: 1.0.8-1 → 1.1.0-1
  • ros-iron-mola-kernel: 1.0.8-1 → 1.1.0-1
  • ros-iron-mola-kernel-dbgsym: 1.0.8-1 → 1.1.0-1
  • ros-iron-mola-launcher: 1.0.8-1 → 1.1.0-1
  • ros-iron-mola-launcher-dbgsym: 1.0.8-1 → 1.1.0-1
  • ros-iron-mola-metric-maps: 1.0.8-1 → 1.1.0-1
  • ros-iron-mola-metric-maps-dbgsym: 1.0.8-1 → 1.1.0-1
  • ros-iron-mola-msgs: 1.0.8-1 → 1.1.0-1
  • ros-iron-mola-msgs-dbgsym: 1.0.8-1 → 1.1.0-1
  • ros-iron-mola-navstate-fg: 1.0.8-1 → 1.1.0-1
  • ros-iron-mola-navstate-fg-dbgsym: 1.0.8-1 → 1.1.0-1
  • ros-iron-mola-navstate-fuse: 1.0.8-1 → 1.1.0-1
  • ros-iron-mola-navstate-fuse-dbgsym: 1.0.8-1 → 1.1.0-1
  • ros-iron-mola-pose-list: 1.0.8-1 → 1.1.0-1
  • ros-iron-mola-pose-list-dbgsym: 1.0.8-1 → 1.1.0-1
  • ros-iron-mola-relocalization: 1.0.8-1 → 1.1.0-1
  • ros-iron-mola-relocalization-dbgsym: 1.0.8-1 → 1.1.0-1
  • ros-iron-mola-traj-tools: 1.0.8-1 → 1.1.0-1
  • ros-iron-mola-traj-tools-dbgsym: 1.0.8-1 → 1.1.0-1
  • ros-iron-mola-viz: 1.0.8-1 → 1.1.0-1
  • ros-iron-mola-viz-dbgsym: 1.0.8-1 → 1.1.0-1
  • ros-iron-mola-yaml: 1.0.8-1 → 1.1.0-1
  • ros-iron-mola-yaml-dbgsym: 1.0.8-1 → 1.1.0-1
  • ros-iron-mp2p-icp: 1.5.2-1 → 1.5.3-1
  • ros-iron-mp2p-icp-dbgsym: 1.5.2-1 → 1.5.3-1
  • ros-iron-mrpt-generic-sensor: 0.2.1-1 → 0.2.2-1
  • ros-iron-mrpt-generic-sensor-dbgsym: 0.2.1-1 → 0.2.2-1
  • ros-iron-mrpt-map-server: 2.0.0-1 → 2.1.0-1
  • ros-iron-mrpt-map-server-dbgsym: 2.0.0-1 → 2.1.0-1
  • ros-iron-mrpt-msgs-bridge: 2.0.0-1 → 2.1.0-1
  • ros-iron-mrpt-nav-interfaces: 2.0.0-1 → 2.1.0-1
  • ros-iron-mrpt-nav-interfaces-dbgsym: 2.0.0-1 → 2.1.0-1
  • ros-iron-mrpt-navigation: 2.0.0-1 → 2.1.0-1
  • ros-iron-mrpt-pf-localization: 2.0.0-1 → 2.1.0-1
  • ros-iron-mrpt-pf-localization-dbgsym: 2.0.0-1 → 2.1.0-1
  • ros-iron-mrpt-pointcloud-pipeline: 2.0.0-1 → 2.1.0-1
  • ros-iron-mrpt-pointcloud-pipeline-dbgsym: 2.0.0-1 → 2.1.0-1
  • ros-iron-mrpt-rawlog: 2.0.0-1 → 2.1.0-1
  • ros-iron-mrpt-rawlog-dbgsym: 2.0.0-1 → 2.1.0-1
  • ros-iron-mrpt-reactivenav2d: 2.0.0-1 → 2.1.0-1
  • ros-iron-mrpt-reactivenav2d-dbgsym: 2.0.0-1 → 2.1.0-1
  • ros-iron-mrpt-sensor-bumblebee-stereo: 0.2.1-1 → 0.2.2-1
  • ros-iron-mrpt-sensor-bumblebee-stereo-dbgsym: 0.2.1-1 → 0.2.2-1
  • ros-iron-mrpt-sensor-gnss-nmea: 0.2.1-1 → 0.2.2-1
  • ros-iron-mrpt-sensor-gnss-nmea-dbgsym: 0.2.1-1 → 0.2.2-1
  • ros-iron-mrpt-sensor-gnss-novatel: 0.2.1-1 → 0.2.2-1
  • ros-iron-mrpt-sensor-gnss-novatel-dbgsym: 0.2.1-1 → 0.2.2-1
  • ros-iron-mrpt-sensor-imu-taobotics: 0.2.1-1 → 0.2.2-1
  • ros-iron-mrpt-sensor-imu-taobotics-dbgsym: 0.2.1-1 → 0.2.2-1
  • ros-iron-mrpt-sensorlib: 0.2.1-1 → 0.2.2-1
  • ros-iron-mrpt-sensors: 0.2.1-1 → 0.2.2-1
  • ros-iron-mrpt-tutorials: 2.0.0-1 → 2.1.0-1
  • ros-iron-mrt-cmake-modules: 1.0.9-4 → 1.0.10-1
  • ros-iron-multires-image: 2.2.2-1 → 2.4.2-1
  • ros-iron-multires-image-dbgsym: 2.2.2-1 → 2.4.2-1
  • ros-iron-ompl: 1.6.0-1 → 1.6.0-2
  • ros-iron-ompl-dbgsym: 1.6.0-1 → 1.6.0-2
  • ros-iron-pid-controller: 3.26.0-1 → 3.26.1-1
  • ros-iron-pid-controller-dbgsym: 3.26.0-1 → 3.26.1-1
  • ros-iron-position-controllers: 3.26.0-1 → 3.26.1-1
  • ros-iron-position-controllers-dbgsym: 3.26.0-1 → 3.26.1-1
  • ros-iron-range-sensor-broadcaster: 3.26.0-1 → 3.26.1-1
  • ros-iron-range-sensor-broadcaster-dbgsym: 3.26.0-1 → 3.26.1-1
  • ros-iron-realtime-tools: 2.5.0-3 → 2.6.0-1
  • ros-iron-realtime-tools-dbgsym: 2.5.0-3 → 2.6.0-1
  • ros-iron-ros2-controllers: 3.26.0-1 → 3.26.1-1
  • ros-iron-ros2-controllers-test-nodes: 3.26.0-1 → 3.26.1-1
  • ros-iron-rqt-joint-trajectory-controller: 3.26.0-1 → 3.26.1-1
  • ros-iron-sick-safetyscanners-base: 1.0.2-1 → 1.0.3-1
  • ros-iron-sick-safetyscanners-base-dbgsym: 1.0.2-1 → 1.0.3-1
  • ros-iron-simple-actions: 0.3.0-1 → 0.4.0-1
  • ros-iron-steering-controllers-library: 3.26.0-1 → 3.26.1-1
  • ros-iron-steering-controllers-library-dbgsym: 3.26.0-1 → 3.26.1-1
  • ros-iron-stereo-image-proc: 4.0.1-1 → 4.0.2-1
  • ros-iron-stereo-image-proc-dbgsym: 4.0.1-1 → 4.0.2-1
  • ros-iron-tf-transformations: 1.0.1-4 → 1.1.0-1
  • ros-iron-tile-map: 2.2.2-1 → 2.4.2-1
  • ros-iron-tile-map-dbgsym: 2.2.2-1 → 2.4.2-1
  • ros-iron-tracetools-image-pipeline: 4.0.1-1 → 4.0.2-1
  • ros-iron-tracetools-image-pipeline-dbgsym: 4.0.1-1 → 4.0.2-1
  • ros-iron-tricycle-controller: 3.26.0-1 → 3.26.1-1
  • ros-iron-tricycle-controller-dbgsym: 3.26.0-1 → 3.26.1-1
  • ros-iron-tricycle-steering-controller: 3.26.0-1 → 3.26.1-1
  • ros-iron-tricycle-steering-controller-dbgsym: 3.26.0-1 → 3.26.1-1
  • ros-iron-ur: 2.3.9-1 → 2.3.10-1
  • ros-iron-ur-calibration: 2.3.9-1 → 2.3.10-1
  • ros-iron-ur-calibration-dbgsym: 2.3.9-1 → 2.3.10-1
  • ros-iron-ur-controllers: 2.3.9-1 → 2.3.10-1
  • ros-iron-ur-controllers-dbgsym: 2.3.9-1 → 2.3.10-1
  • ros-iron-ur-dashboard-msgs: 2.3.9-1 → 2.3.10-1
  • ros-iron-ur-dashboard-msgs-dbgsym: 2.3.9-1 → 2.3.10-1
  • ros-iron-ur-description: 2.3.0-1 → 2.3.1-1
  • ros-iron-ur-moveit-config: 2.3.9-1 → 2.3.10-1
  • ros-iron-ur-robot-driver: 2.3.9-1 → 2.3.10-1
  • ros-iron-ur-robot-driver-dbgsym: 2.3.9-1 → 2.3.10-1
  • ros-iron-velocity-controllers: 3.26.0-1 → 3.26.1-1
  • ros-iron-velocity-controllers-dbgsym: 3.26.0-1 → 3.26.1-1

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:

  • Bence Magyar
  • David V. Lu!!
  • Denis Stogl
  • Denis Štogl
  • Felix Exner
  • Gonzalo Mier
  • Jonas Otto
  • Jose Luis Blanco-Claraco
  • Jose-Luis Blanco-Claraco
  • José Luis Blanco-Claraco
  • Kevin Rösch
  • Lennart Puck
  • Mark Moll
  • Markus Bader
  • Southwest Research Institute
  • Tim Clephas
  • Vincent Rabaud
  • Víctor Mayoral-Vilches

1 post - 1 participant

Read full topic

by Yadunund on August 23, 2024 11:38 PM

ROS News for the Week of August 19th, 2024

ROS News for the Week of August 19th, 2024



ROSCon India 2024 was announced this week. The save the date announcement can be found here. More details and a proper website should be available shortly.


e3ba6007ac67bca8c31aa3f6981fc5b7eb571b07_2_615x500
There are lots of things in the ROS ecosystem that could be better, and package creation is certainly one of them. We really appreciate that @jak has taken the time to build and maintain a ROS package called Turtle Nest that simplifies that package creation process. All ROS users are more than welcome to help improve the tools they use every day!


f8af73bfc587cc2bedfbf5341863abbf0734589d_2_690x388
d88ee43354b38b939637bbba8268d99bdb67959a_2_517x291

We have four different ROS events next week! We would love to see you there!

Want to put together your own local ROS event? @gbiggs gave some great advice on how to put together a ROS meetup here.



:clap: ROSCon :clap: 2024 :clap: early :clap: registration :clap: ends :clap: on :clap: 2024-09-03T07:00:00Z UTC :clap:
Early registration prices are $100 off, making it free to attend one of our seven fantastic workshops. We also have a handful of sponsor booths remaining. Given our current trajectory ROSCon 2024 might sell out, so I recommend you register as soon as possible.

Events

News

ROS

Got some spare time? :mantelpiece_clock:

We need ROS users to help make the ROS ecosystem better! Why not scratch your own itch by fixing an issue in the ROS 2 CLI? Most CLI issues are fairly easy to fix and your change will get used by the entire ROS community!

1 post - 1 participant

Read full topic

by Katherine_Scott on August 23, 2024 08:13 PM

Autoware Meetup in the Bay Area next week!

We are holding an Autoware meetup in the Bay Area next week at Arm Office in San Jose, on August 27th at 5:30pm PDT!

We will deliver presentations to catch up with old friends and make new friends, and tell them all about what have been changed since the last time Autoware meetup was held in the Bay Area!

Register for the meetup on the event page.

We will also be present with a booth at the ADAS & Autonomous Vehicle Technology Expo at San Jose McEnery Convention Center USA between August 28 & 29.

If you want to visit us at the expo, register at the official webpage (it’s free of charge).

Hope to see you there!

1 post - 1 participant

Read full topic

by sametkutuk on August 23, 2024 04:28 PM

Using Mojo with ROS

Recently a company called Modular created a programming language called Mojo (Mojo 🔥: Programming language for all of AI) which essentially does to Python what Typescript does to Javascript. Has anyone experimented with using Mojo for ROS development? What is your experience?

I’m curious to see if Mojo can overcome some of the performance hurdles that is dissuading a lot of companies from using Python in robotics applications.

4 posts - 4 participants

Read full topic

by snwu on August 23, 2024 05:44 AM

August 22, 2024
Cloud Robotics WG Meetings 2024-08-26

Please come and join us for this coming meeting at 2024-08-26T17:00:00Z UTC→2024-08-26T18:00:00Z UTC, where we will discuss robotics news and any progress that group members have made towards improving cloud robotics for the whole community.

Last meeting, we talked about the state of the Cloud Robotics Hub website that the group is collaborating to build. The members agreed to divide tasks up to get the website ready for publishing. You can watch our meeting recording to find out more.

If you are willing and able to give a talk on cloud robotics in future meetings, we would be happy to host you - please reply here, message me directly, or sign up using the Guest Speaker Signup Sheet. We will record your talk and host it on Vimeo with our other meeting recordings too!

The meeting link is here, and you can sign up to our calendar or our Google Group for meeting notifications.

Hopefully we will see you there!

1 post - 1 participant

Read full topic

by mikelikesrobots on August 22, 2024 06:22 PM

Organizing a Significant ROS Event at Porto Digital 06-09 November 2024– Looking for Community Guidance

Hello ROS Community,

I’m excited to share that we’re planning an event that will take place at Porto Digital, the largest technology park in Latin America, located in Recife, from November 6th to 9th. The event will bring together key figures and companies from the technology sector, and it will be broadcast by Rede Globo, the largest television network in Brazil. Our team has been given the responsibility to organize the robotics segment, and we see this as a great opportunity to connect with others, form partnerships, and share knowledge through talks and workshops.

RNP RECAP 2023

However, as we are relatively new to organizing an event of this scale, especially in the context of international standards, we’re reaching out to the ROS community for advice and support. We want to ensure that our event aligns with the expectations and quality that ROS Meetups and Summits are known for.

Our event will focus on the latest advancements in ROS, and we’ve already confirmed a few talks and workshops, including:

  • Title: Robotics as a Service Aiming at Reducing HHER
    Speaker: Doglas Negri
    Description: A practical approach to reducing human exposure to risks through innovative non-conventional robotic solutions across various industries.
  • Title: Integrating CANopen Controllers with ROS 2 Control
    Speaker: Lucas Matana Luza
    Description: A workshop to explore integrating CANopen controllers with ROS2 for controlling anthropomorphic robotic arms.
  • Title: Autonomous Truck Path Planning in Agricultural Environments Using Open Source Software
    Speaker: Marcus Vinicius Leal de Carvalho
    Description: Customizing the Navigation2 Stack for autonomous vehicles in agricultural settings, focusing on obstacle detection, braking, and collision avoidance.
  • Title: Introduction to Moveit 2 (Robotic Manipulation Platform for ROS 2)
    Speaker: Rodrigo Formiga Farias
    Description: A minicourse covering basic robotic manipulator control concepts, introduction to the Moveit platform, and hands-on practice with the Panda robot arm.

We would greatly appreciate any advice on the following:

  1. Should we categorize this event as a ROS Meetup, ROS Summit, or something else entirely?
  2. What are the necessary steps to officially align this event with the ROS community’s standards, especially considering the guidelines set by OSRF and organizations like The Construct?
  3. Are there specific guidelines or best practices we should follow to ensure the event meets the community’s expectations?
  4. How can we encourage more universities, companies, and speakers to join and contribute?

We’re eager to learn from those with more experience and to make this event a success with your help. Any guidance or suggestions from the community would be invaluable as we continue planning.

@Katherine_Scott @tfoote @dirk-thomas @jackie @ricardotellez Could you please provide some guidance on how we should approach organizing this event to ensure it aligns with the standards and expectations of the ROS community? We are particularly interested in knowing whether we should categorize it as a ROS Meetup, ROS Summit, or something else, and what steps we should take to officially align it with the community’s best practices.

Thank you in advance for your support!

Best regards

14 posts - 8 participants

Read full topic

by Marcus_Vinicius_Leal on August 22, 2024 04:59 PM

Introducing Turtle Nest: GUI for ROS 2 package creation

Hi everyone,

I’m here to announce Turtle Nest - a GUI application to create ROS 2 packages.

I started this project recently to make ROS 2 package creation easier and to reduce the likelihood of user-made errors. I believe Turtle Nest will help the beginners to get started faster with ROS 2, while also helping professional developers to create new packages.

For instance, I often found myself reviewing the documentation to refresh my memory of ros2 pkg create command and its possible options. I also needed to check how to create new nodes and launch files, and how to add them to CMakeLists.txt or setup.py files. This whole process has many potential pitfalls and places for possible mistakes, especially for new users.

With Turtle Nest, you can just simply run turtle-nest command and let the application guide you through the package creation.

Here are some key advantages of using Turtle Nest instead of the ‘ros2 pkg create’ command:

  • Easy to use - no need to dig through the ROS 2 documentation for the right commands or manually add things to CMakeLists.txt or setup.py.
  • Create C++ and/or Python nodes - which are ready for further development.
  • Automatically adds necessary dependencies - rclpy, rclcpp, and std_msgs.
  • Option to create a launch file - that launches the created node.
  • Create C++ and Python nodes within the same package - combine languages that typically require separate packages.
  • Naming conventions enforced - no more failing builds due to incorrect package or node names.
  • Remembers the important details - workspace path, maintainer name, and maintainer email for the future packages.

Future enhancements may include:

  • Easy creation of _msgs -packages
  • Adding parameter files
  • Including more dependencies
  • Adding nodes, launch files, etc., to existing packages

I plan to release this package via apt, but before that I wanted to post it here to hear your thoughts and have you try it out first. All feedback is greatly appreciated!

:link: GitHub - Jannkar/turtle_nest: Ros 2 Package Creator

17 posts - 11 participants

Read full topic

by jak on August 22, 2024 03:13 PM

ROS-ON: Event for Ontario ROS Developers

Oh hey there, eh.

Canada has long been an integral part of the ROS ecosystem, and I’m excited to announce the formation of ROS-ON, a user group specifically for ROS developers in and around Ontario. And we’re having our first event with the biggest name in the Ontario ROS ecosystem: Clearpath Robotics.

  • When: September 17, 2024, 6pm
  • Where: Clearpath Robotics, Waterloo Office
  • Who: Anyone and Everyone
  • What: Socialization, pizza and some invited talks (TBA). Plus free stickers

Please RSVP via this link*. Attendance won’t cost you a Toonie, but RSVPing will help ensure enough space/food for everyone.

Albeit, Ontario is pretty big [citation needed], so going forward, we will change up the location to reflect where people are. We might start some local chapters if there ends up being a lot of users in Fort Severn.

Don’t pass up this opportunity to learn everything about ROS from A to Zed!

*The Google Form will be replaced by a Discourse group once things get rolling.

3 posts - 2 participants

Read full topic

by DLu on August 22, 2024 02:02 PM


Powered by the awesome: Planet