Planet ROS
Planet ROS - http://planet.ros.org
Planet ROS - http://planet.ros.org http://planet.ros.org
ROS Discourse General: ROS News for the Week of February 19th, 2024
ROS News for the Week of February 19th, 2024
Open Robotics will be participating in Google Summer of Code 2024. We’re looking for a few interns to help us out! See the post for all the details.
Our next Gazebo Community meeting is next Wednesday, February 28th. Sikiru Salau, a competitor in the Pan-African Robotics Competition, will be joining us to talk about simulating robots for agriculture.
Hello Robot is having a great month! Last week they released their third gen robot. This week they are at the top of the orange website with this “OK Robot” paper from NYU
Check out the AutoNav robot by Jatin Patil. Hats off to the developer, this is a really well put together personal project!
Just a reminder: Gazebo Classic goes End-Of-Life in January 2025 and ROS 2 Jazzy will not support Gazebo Classic. We put together some guidance for those of you that need to make the switch!
Events
- February Aerial Robotics Meetings
- 2024-02-28 Gazebo Community Meeting wsg Sikiru Salau of Pan-African Robotics Competition
- 2024-03-06 Boulder is for Robots Meetup
- 2024-03-14 TU Delft ROS MOOC (FREE!)
- 2024-03-27 ROS Industrial Annual Meeting
- 2024-03-27 Robotics Happy Hour Pittsburgh
- 2024-04-21 Robots on Ice
- 2024-05-03 Open Hardware Summit Montreal
- 2024-05-13 Bots & Bento @ ICRA 2024
- 2024-06-04 → 2024-06-08 ACM SIGSOFT Summer School on Software Engineering for Robotics
- 2024-06-?? Workshop on Agriculture Vision at CVPR 2024
- 2024-06-16 Food Topping Challenge at ICRA 2024
- 2024-06-19 => 2024-06-20 ROSCon France
- 2024-08-05 Autonomous Systems Bootcam at Univ. Deleware– Video
- 2024-09-25 ROSConJP
News
- MoveIt Pro Released – The Robot Report
- Intuitive Machines Lands on the Moon! – IEEE Spectrum
- SWRI’s Novel Lunar Rover Navigation System
- YOLO v. 9 Paper–Source
- Real Time S-Graphs for Robot Pose – Paper
- Influence of Camera-LiDAR Configuration on 3D Object Detection for Autonomous Driving
- An open, modular framework for zero-shot, language conditioned pick-and-drop tasks in arbitrary homes.
- DINOBot: Robot Manipulation via Retrieval and Alignment with Vision Foundation Models
- Cool: Fit-NGP: Fitting Object Models to Neural Graphics Primitives – Video
- Khronos: Spatio-Temporal Metric-Semantic SLAM
- VisFusion: Visibility-aware Online 3D Scene Reconstruction from Videos
- Lidar With Velocity: Correcting Moving Objects Point Cloud Distortion From Oscillating Scanning Lidars by Fusion With Camera
- Dutch startup Monumental is using robots to lay bricks
- Olis and Kawasaki Land Ink Deal for Remote Support
- Video Friday
ROS
- Open Robotics @ GSoC 2024
- Gazebo Classic End-Of-Life and ROS 2 Jazzy
- 42 New and 280 Updated Packages for Humble
- 2 New and 75 Updated Packages for Iron
- 0 New and 136 Updated Packages for Noetic
- ROS 2 Migration Guide using TurtleBot 2
- REP Proposal: Coordinate Frames for Maritime Robots
- ROS 2 DJI Drone PSDK Bridge
- Learn ROS 2 with LIMO Robot
- Highlights from NVIDIA GTC for ROS Developers
- Handle Unique Paramers for Robot Instances
- Thoughts on Websockets with ROS Messaging
- Maritime Robotics Working Group wsg HoloOcean
- Plot Juggler 3.9.1 Release
- Devops for Robotics Certificate Training
- Rolling out 24.04 for Rolling
- MCAP File Editor from @facontidavide
- Diff Drive ROS 2 Robot with ESP32
- Swerve Drive Motor Limitations ← This personal blog is
- New AutoNav ROS Robot – Video
- ROS Intro Workshop @ Purdue – Materials
- Robotics at Compile Time: Optimizing Robotics Algorithms With C++'s Compile-Time Features - CppCon23
- MyCobot280 for MoveIt
- Ziobot ROS Robot
ROS Questions
Got a minute to spare? Pay it forward by answering a few ROS questions on Robotics Stack Exchange.
3 posts - 3 participants
https://discourse.ros.org/t/ros-news-for-the-week-of-february-19th-2024/36297ROS Discourse General: New Packages for Iron Irwini 2024-02-23
We’re happy to announce 2 new packages and 75 updates are now available in ROS 2 Iron Irwini . This sync was tagged as iron/2024-02-23
.
Package Updates for iron
Added Packages [2]:
- ros-iron-apriltag-detector: 1.2.0-1
- ros-iron-multidim-rrt-planner: 0.0.8-1
Updated Packages [75]:
- ros-iron-ackermann-steering-controller: 3.21.0-1 → 3.22.0-1
- ros-iron-ackermann-steering-controller-dbgsym: 3.21.0-1 → 3.22.0-1
- ros-iron-admittance-controller: 3.21.0-1 → 3.22.0-1
- ros-iron-admittance-controller-dbgsym: 3.21.0-1 → 3.22.0-1
- ros-iron-azure-iot-sdk-c: 1.10.1-4 → 1.12.0-1
- ros-iron-bicycle-steering-controller: 3.21.0-1 → 3.22.0-1
- ros-iron-bicycle-steering-controller-dbgsym: 3.21.0-1 → 3.22.0-1
- ros-iron-bno055: 0.4.1-4 → 0.5.0-1
- ros-iron-diff-drive-controller: 3.21.0-1 → 3.22.0-1
- ros-iron-diff-drive-controller-dbgsym: 3.21.0-1 → 3.22.0-1
- ros-iron-draco-point-cloud-transport: 2.0.3-1 → 2.0.4-1
- ros-iron-draco-point-cloud-transport-dbgsym: 2.0.3-1 → 2.0.4-1
- ros-iron-effort-controllers: 3.21.0-1 → 3.22.0-1
- ros-iron-effort-controllers-dbgsym: 3.21.0-1 → 3.22.0-1
- ros-iron-force-torque-sensor-broadcaster: 3.21.0-1 → 3.22.0-1
- ros-iron-force-torque-sensor-broadcaster-dbgsym: 3.21.0-1 → 3.22.0-1
- ros-iron-forward-command-controller: 3.21.0-1 → 3.22.0-1
- ros-iron-forward-command-controller-dbgsym: 3.21.0-1 → 3.22.0-1
- ros-iron-gripper-controllers: 3.21.0-1 → 3.22.0-1
- ros-iron-gripper-controllers-dbgsym: 3.21.0-1 → 3.22.0-1
- ros-iron-imu-sensor-broadcaster: 3.21.0-1 → 3.22.0-1
- ros-iron-imu-sensor-broadcaster-dbgsym: 3.21.0-1 → 3.22.0-1
- ros-iron-joint-state-broadcaster: 3.21.0-1 → 3.22.0-1
- ros-iron-joint-state-broadcaster-dbgsym: 3.21.0-1 → 3.22.0-1
- ros-iron-joint-trajectory-controller: 3.21.0-1 → 3.22.0-1
- ros-iron-joint-trajectory-controller-dbgsym: 3.21.0-1 → 3.22.0-1
- ros-iron-leo: 2.0.0-1 → 2.0.1-1
- ros-iron-leo-description: 2.0.0-1 → 2.0.1-1
- ros-iron-leo-msgs: 2.0.0-1 → 2.0.1-1
- ros-iron-leo-msgs-dbgsym: 2.0.0-1 → 2.0.1-1
- ros-iron-leo-teleop: 2.0.0-1 → 2.0.1-1
- ros-iron-mp2p-icp: 1.1.0-1 → 1.2.0-1
- ros-iron-mp2p-icp-dbgsym: 1.1.0-1 → 1.2.0-1
- ros-iron-mrpt2: 2.11.7-1 → 2.11.9-1
- ros-iron-mrpt2-dbgsym: 2.11.7-1 → 2.11.9-1
- ros-iron-plotjuggler-ros: 2.1.0-1 → 2.1.1-1
- ros-iron-plotjuggler-ros-dbgsym: 2.1.0-1 → 2.1.1-1
- ros-iron-point-cloud-interfaces: 2.0.3-1 → 2.0.4-1
- ros-iron-point-cloud-interfaces-dbgsym: 2.0.3-1 → 2.0.4-1
- ros-iron-point-cloud-transport: 2.0.3-1 → 2.0.4-1
- ros-iron-point-cloud-transport-dbgsym: 2.0.3-1 → 2.0.4-1
- ros-iron-point-cloud-transport-plugins: 2.0.3-1 → 2.0.4-1
- ros-iron-point-cloud-transport-py: 2.0.3-1 → 2.0.4-1
- ros-iron-position-controllers: 3.21.0-1 → 3.22.0-1
- ros-iron-position-controllers-dbgsym: 3.21.0-1 → 3.22.0-1
- ros-iron-range-sensor-broadcaster: 3.21.0-1 → 3.22.0-1
- ros-iron-range-sensor-broadcaster-dbgsym: 3.21.0-1 → 3.22.0-1
- ros-iron-rcpputils: 2.6.2-1 → 2.6.3-1
- ros-iron-rcpputils-dbgsym: 2.6.2-1 → 2.6.3-1
- ros-iron-robotraconteur: 1.0.0-1 → 1.0.0-2
- ros-iron-robotraconteur-dbgsym: 1.0.0-1 → 1.0.0-2
- ros-iron-ros2-controllers: 3.21.0-1 → 3.22.0-1
- ros-iron-ros2-controllers-test-nodes: 3.21.0-1 → 3.22.0-1
- ros-iron-rqt: 1.3.3-1 → 1.3.4-1
- ros-iron-rqt-gauges: 0.0.1-1 → 0.0.2-1
- ros-iron-rqt-gui: 1.3.3-1 → 1.3.4-1
- ros-iron-rqt-gui-cpp: 1.3.3-1 → 1.3.4-1
- ros-iron-rqt-gui-cpp-dbgsym: 1.3.3-1 → 1.3.4-1
- ros-iron-rqt-gui-py: 1.3.3-1 → 1.3.4-1
- ros-iron-rqt-joint-trajectory-controller: 3.21.0-1 → 3.22.0-1
- ros-iron-rqt-py-common: 1.3.3-1 → 1.3.4-1
- ros-iron-steering-controllers-library: 3.21.0-1 → 3.22.0-1
- ros-iron-steering-controllers-library-dbgsym: 3.21.0-1 → 3.22.0-1
- ros-iron-tricycle-controller: 3.21.0-1 → 3.22.0-1
- ros-iron-tricycle-controller-dbgsym: 3.21.0-1 → 3.22.0-1
- ros-iron-tricycle-steering-controller: 3.21.0-1 → 3.22.0-1
- ros-iron-tricycle-steering-controller-dbgsym: 3.21.0-1 → 3.22.0-1
- ros-iron-velocity-controllers: 3.21.0-1 → 3.22.0-1
- ros-iron-velocity-controllers-dbgsym: 3.21.0-1 → 3.22.0-1
- ros-iron-vrpn-mocap: 1.0.3-3 → 1.1.0-1
- ros-iron-vrpn-mocap-dbgsym: 1.0.3-3 → 1.1.0-1
- ros-iron-zlib-point-cloud-transport: 2.0.3-1 → 2.0.4-1
- ros-iron-zlib-point-cloud-transport-dbgsym: 2.0.3-1 → 2.0.4-1
- ros-iron-zstd-point-cloud-transport: 2.0.3-1 → 2.0.4-1
- ros-iron-zstd-point-cloud-transport-dbgsym: 2.0.3-1 → 2.0.4-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:
- Alejandro Hernandez Cordero
- Alejandro Hernández
- Alvin Sun
- Bence Magyar
- Bernd Pfrommer
- Brandon Ong
- Davide Faconti
- Denis Štogl
- Dharini Dutia
- Eloy Bricneo
- Fictionlab
- John Wason
- Jose-Luis Blanco-Claraco
- Martin Pecka
- Tim Clephas
- david
- flynneva
1 post - 1 participant
https://discourse.ros.org/t/new-packages-for-iron-irwini-2024-02-23/36283ROS Discourse General: New packages and patch release for Humble Hawksbill 2024-02-22
We’re happy to announce a new Humble release!
This sync brings several new packages and some updates to ROS 2 core packages. (I’m not including the project board because it was empty.)
Package Updates for Humble
Added Packages [42]:
- ros-humble-apriltag-detector: 1.1.0-1
- ros-humble-as2-gazebo-assets: 1.0.8-1
- ros-humble-as2-gazebo-assets-dbgsym: 1.0.8-1
- ros-humble-as2-platform-dji-osdk: 1.0.8-1
- ros-humble-as2-platform-dji-osdk-dbgsym: 1.0.8-1
- ros-humble-as2-platform-gazebo: 1.0.8-1
- ros-humble-as2-platform-gazebo-dbgsym: 1.0.8-1
- ros-humble-caret-analyze: 0.5.0-1
- ros-humble-caret-msgs: 0.5.0-6
- ros-humble-caret-msgs-dbgsym: 0.5.0-6
- ros-humble-data-tamer-cpp: 0.9.3-2
- ros-humble-data-tamer-cpp-dbgsym: 0.9.3-2
- ros-humble-data-tamer-msgs: 0.9.3-2
- ros-humble-data-tamer-msgs-dbgsym: 0.9.3-2
- ros-humble-hardware-interface-testing: 2.39.1-1
- ros-humble-hardware-interface-testing-dbgsym: 2.39.1-1
- ros-humble-hri-msgs: 2.0.0-1
- ros-humble-hri-msgs-dbgsym: 2.0.0-1
- ros-humble-mocap4r2-dummy-driver: 0.0.7-1
- ros-humble-mocap4r2-dummy-driver-dbgsym: 0.0.7-1
- ros-humble-mocap4r2-marker-viz: 0.0.7-1
- ros-humble-mocap4r2-marker-viz-dbgsym: 0.0.7-1
- ros-humble-mocap4r2-marker-viz-srvs: 0.0.7-1
- ros-humble-mocap4r2-marker-viz-srvs-dbgsym: 0.0.7-1
- ros-humble-motion-capture-tracking: 1.0.3-1
- ros-humble-motion-capture-tracking-dbgsym: 1.0.3-1
- ros-humble-motion-capture-tracking-interfaces: 1.0.3-1
- ros-humble-motion-capture-tracking-interfaces-dbgsym: 1.0.3-1
- ros-humble-psdk-interfaces: 1.0.0-1
- ros-humble-psdk-interfaces-dbgsym: 1.0.0-1
- ros-humble-psdk-wrapper: 1.0.0-1
- ros-humble-psdk-wrapper-dbgsym: 1.0.0-1
- ros-humble-qb-softhand-industry-description: 2.1.2-4
- ros-humble-qb-softhand-industry-msgs: 2.1.2-4
- ros-humble-qb-softhand-industry-msgs-dbgsym: 2.1.2-4
- ros-humble-qb-softhand-industry-ros2-control: 2.1.2-4
- ros-humble-qb-softhand-industry-ros2-control-dbgsym: 2.1.2-4
- ros-humble-qb-softhand-industry-srvs: 2.1.2-4
- ros-humble-qb-softhand-industry-srvs-dbgsym: 2.1.2-4
- ros-humble-ros2caret: 0.5.0-2
- ros-humble-sync-parameter-server: 1.0.1-2
- ros-humble-sync-parameter-server-dbgsym: 1.0.1-2
Updated Packages [280]:
- ros-humble-ament-cmake: 1.3.7-1 → 1.3.8-1
- ros-humble-ament-cmake-auto: 1.3.7-1 → 1.3.8-1
- ros-humble-ament-cmake-core: 1.3.7-1 → 1.3.8-1
- ros-humble-ament-cmake-export-definitions: 1.3.7-1 → 1.3.8-1
- ros-humble-ament-cmake-export-dependencies: 1.3.7-1 → 1.3.8-1
- ros-humble-ament-cmake-export-include-directories: 1.3.7-1 → 1.3.8-1
- ros-humble-ament-cmake-export-interfaces: 1.3.7-1 → 1.3.8-1
- ros-humble-ament-cmake-export-libraries: 1.3.7-1 → 1.3.8-1
- ros-humble-ament-cmake-export-link-flags: 1.3.7-1 → 1.3.8-1
- ros-humble-ament-cmake-export-targets: 1.3.7-1 → 1.3.8-1
- ros-humble-ament-cmake-gen-version-h: 1.3.7-1 → 1.3.8-1
- ros-humble-ament-cmake-gmock: 1.3.7-1 → 1.3.8-1
- ros-humble-ament-cmake-google-benchmark: 1.3.7-1 → 1.3.8-1
- ros-humble-ament-cmake-gtest: 1.3.7-1 → 1.3.8-1
- ros-humble-ament-cmake-include-directories: 1.3.7-1 → 1.3.8-1
- ros-humble-ament-cmake-libraries: 1.3.7-1 → 1.3.8-1
- ros-humble-ament-cmake-nose: 1.3.7-1 → 1.3.8-1
- ros-humble-ament-cmake-pytest: 1.3.7-1 → 1.3.8-1
- ros-humble-ament-cmake-python: 1.3.7-1 → 1.3.8-1
- ros-humble-ament-cmake-target-dependencies: 1.3.7-1 → 1.3.8-1
- ros-humble-ament-cmake-test: 1.3.7-1 → 1.3.8-1
- ros-humble-ament-cmake-vendor-package: 1.3.7-1 → 1.3.8-1
- ros-humble-ament-cmake-version: 1.3.7-1 → 1.3.8-1
- ros-humble-as2-alphanumeric-viewer: 1.0.6-1 → 1.0.8-1
- ros-humble-as2-alphanumeric-viewer-dbgsym: 1.0.6-1 → 1.0.8-1
- ros-humble-as2-behavior: 1.0.6-1 → 1.0.8-1
- ros-humble-as2-behavior-dbgsym: 1.0.6-1 → 1.0.8-1
- ros-humble-as2-behavior-tree: 1.0.6-1 → 1.0.8-1
- ros-humble-as2-behavior-tree-dbgsym: 1.0.6-1 → 1.0.8-1
- ros-humble-as2-behaviors-motion: 1.0.6-1 → 1.0.8-1
- ros-humble-as2-behaviors-motion-dbgsym: 1.0.6-1 → 1.0.8-1
- ros-humble-as2-behaviors-perception: 1.0.6-1 → 1.0.8-1
- ros-humble-as2-behaviors-perception-dbgsym: 1.0.6-1 → 1.0.8-1
- ros-humble-as2-behaviors-platform: 1.0.6-1 → 1.0.8-1
- ros-humble-as2-behaviors-platform-dbgsym: 1.0.6-1 → 1.0.8-1
- ros-humble-as2-behaviors-trajectory-generation: 1.0.6-1 → 1.0.8-1
- ros-humble-as2-behaviors-trajectory-generation-dbgsym: 1.0.6-1 → 1.0.8-1
- ros-humble-as2-cli: 1.0.6-1 → 1.0.8-1
- ros-humble-as2-core: 1.0.6-1 → 1.0.8-1
- ros-humble-as2-keyboard-teleoperation: 1.0.6-1 → 1.0.8-1
- ros-humble-as2-motion-controller: 1.0.6-1 → 1.0.8-1
- ros-humble-as2-motion-controller-dbgsym: 1.0.6-1 → 1.0.8-1
- ros-humble-as2-motion-reference-handlers: 1.0.6-1 → 1.0.8-1
- ros-humble-as2-msgs: 1.0.6-1 → 1.0.8-1
- ros-humble-as2-msgs-dbgsym: 1.0.6-1 → 1.0.8-1
- ros-humble-as2-platform-crazyflie: 1.0.6-1 → 1.0.8-1
- ros-humble-as2-platform-crazyflie-dbgsym: 1.0.6-1 → 1.0.8-1
- ros-humble-as2-platform-tello: 1.0.6-1 → 1.0.8-1
- ros-humble-as2-platform-tello-dbgsym: 1.0.6-1 → 1.0.8-1
- ros-humble-as2-python-api: 1.0.6-1 → 1.0.8-1
- ros-humble-as2-realsense-interface: 1.0.6-1 → 1.0.8-1
- ros-humble-as2-realsense-interface-dbgsym: 1.0.6-1 → 1.0.8-1
- ros-humble-as2-state-estimator: 1.0.6-1 → 1.0.8-1
- ros-humble-as2-state-estimator-dbgsym: 1.0.6-1 → 1.0.8-1
- ros-humble-as2-usb-camera-interface: 1.0.6-1 → 1.0.8-1
- ros-humble-as2-usb-camera-interface-dbgsym: 1.0.6-1 → 1.0.8-1
- ros-humble-camera-calibration: 3.0.0-1 → 3.0.3-1
- ros-humble-controller-interface: 2.37.0-1 → 2.39.1-1
- ros-humble-controller-interface-dbgsym: 2.37.0-1 → 2.39.1-1
- ros-humble-controller-manager: 2.37.0-1 → 2.39.1-1
- ros-humble-controller-manager-dbgsym: 2.37.0-1 → 2.39.1-1
- ros-humble-controller-manager-msgs: 2.37.0-1 → 2.39.1-1
- ros-humble-controller-manager-msgs-dbgsym: 2.37.0-1 → 2.39.1-1
- ros-humble-costmap-queue: 1.1.12-1 → 1.1.13-1
- ros-humble-depth-image-proc: 3.0.0-1 → 3.0.3-1
- ros-humble-depth-image-proc-dbgsym: 3.0.0-1 → 3.0.3-1
- ros-humble-depthai-bridge: 2.8.2-1 → 2.9.0-1
- ros-humble-depthai-bridge-dbgsym: 2.8.2-1 → 2.9.0-1
- ros-humble-depthai-descriptions: 2.8.2-1 → 2.9.0-1
- ros-humble-depthai-examples: 2.8.2-1 → 2.9.0-1
- ros-humble-depthai-examples-dbgsym: 2.8.2-1 → 2.9.0-1
- ros-humble-depthai-filters: 2.8.2-1 → 2.9.0-1
- ros-humble-depthai-filters-dbgsym: 2.8.2-1 → 2.9.0-1
- ros-humble-depthai-ros: 2.8.2-1 → 2.9.0-1
- ros-humble-depthai-ros-driver: 2.8.2-1 → 2.9.0-1
- ros-humble-depthai-ros-driver-dbgsym: 2.8.2-1 → 2.9.0-1
- ros-humble-depthai-ros-msgs: 2.8.2-1 → 2.9.0-1
- ros-humble-depthai-ros-msgs-dbgsym: 2.8.2-1 → 2.9.0-1
- ros-humble-dwb-core: 1.1.12-1 → 1.1.13-1
- ros-humble-dwb-core-dbgsym: 1.1.12-1 → 1.1.13-1
- ros-humble-dwb-critics: 1.1.12-1 → 1.1.13-1
- ros-humble-dwb-critics-dbgsym: 1.1.12-1 → 1.1.13-1
- ros-humble-dwb-msgs: 1.1.12-1 → 1.1.13-1
- ros-humble-dwb-msgs-dbgsym: 1.1.12-1 → 1.1.13-1
- ros-humble-dwb-plugins: 1.1.12-1 → 1.1.13-1
- ros-humble-dwb-plugins-dbgsym: 1.1.12-1 → 1.1.13-1
- ros-humble-event-camera-codecs: 1.1.2-1 → 1.1.3-1
- ros-humble-event-camera-codecs-dbgsym: 1.1.2-1 → 1.1.3-1
- ros-humble-event-camera-py: 1.1.3-1 → 1.1.4-1
- ros-humble-event-camera-renderer: 1.1.2-1 → 1.1.3-1
- ros-humble-event-camera-renderer-dbgsym: 1.1.2-1 → 1.1.3-1
- ros-humble-examples-tf2-py: 0.25.5-1 → 0.25.6-1
- ros-humble-geometry2: 0.25.5-1 → 0.25.6-1
- ros-humble-hardware-interface: 2.37.0-1 → 2.39.1-1
- ros-humble-hardware-interface-dbgsym: 2.37.0-1 → 2.39.1-1
- ros-humble-image-pipeline: 3.0.0-1 → 3.0.3-1
- ros-humble-image-proc: 3.0.0-1 → 3.0.3-1
- ros-humble-image-proc-dbgsym: 3.0.0-1 → 3.0.3-1
- ros-humble-image-publisher: 3.0.0-1 → 3.0.3-1
- ros-humble-image-publisher-dbgsym: 3.0.0-1 → 3.0.3-1
- ros-humble-image-rotate: 3.0.0-1 → 3.0.3-1
- ros-humble-image-rotate-dbgsym: 3.0.0-1 → 3.0.3-1
- ros-humble-image-view: 3.0.0-1 → 3.0.3-1
- ros-humble-image-view-dbgsym: 3.0.0-1 → 3.0.3-1
- ros-humble-joint-limits: 2.37.0-1 → 2.39.1-1
- ros-humble-joint-limits-dbgsym: 2.37.0-1 → 2.39.1-1
- ros-humble-launch: 1.0.4-1 → 1.0.5-1
- ros-humble-launch-pytest: 1.0.4-1 → 1.0.5-1
- ros-humble-launch-testing: 1.0.4-1 → 1.0.5-1
- ros-humble-launch-testing-ament-cmake: 1.0.4-1 → 1.0.5-1
- ros-humble-launch-xml: 1.0.4-1 → 1.0.5-1
- ros-humble-launch-yaml: 1.0.4-1 → 1.0.5-1
- ros-humble-leo: 1.2.0-1 → 1.2.1-1
- ros-humble-leo-description: 1.2.0-1 → 1.2.1-1
- ros-humble-leo-msgs: 1.2.0-1 → 1.2.1-1
- ros-humble-leo-msgs-dbgsym: 1.2.0-1 → 1.2.1-1
- ros-humble-leo-teleop: 1.2.0-1 → 1.2.1-1
- ros-humble-microstrain-inertial-driver: 3.2.0-2 → 3.2.1-1
- ros-humble-microstrain-inertial-driver-dbgsym: 3.2.0-2 → 3.2.1-1
- ros-humble-microstrain-inertial-examples: 3.2.0-2 → 3.2.1-1
- ros-humble-microstrain-inertial-examples-dbgsym: 3.2.0-2 → 3.2.1-1
- ros-humble-microstrain-inertial-msgs: 3.2.0-2 → 3.2.1-1
- ros-humble-microstrain-inertial-msgs-dbgsym: 3.2.0-2 → 3.2.1-1
- ros-humble-microstrain-inertial-rqt: 3.2.0-2 → 3.2.1-1
- ros-humble-mocap4r2-control: 0.0.6-1 → 0.0.7-1
- ros-humble-mocap4r2-control-dbgsym: 0.0.6-1 → 0.0.7-1
- ros-humble-mocap4r2-control-msgs: 0.0.6-1 → 0.0.7-1
- ros-humble-mocap4r2-control-msgs-dbgsym: 0.0.6-1 → 0.0.7-1
- ros-humble-mocap4r2-marker-publisher: 0.0.6-1 → 0.0.7-1
- ros-humble-mocap4r2-marker-publisher-dbgsym: 0.0.6-1 → 0.0.7-1
- ros-humble-mocap4r2-robot-gt: 0.0.6-1 → 0.0.7-1
- ros-humble-mocap4r2-robot-gt-dbgsym: 0.0.6-1 → 0.0.7-1
- ros-humble-mocap4r2-robot-gt-msgs: 0.0.6-1 → 0.0.7-1
- ros-humble-mocap4r2-robot-gt-msgs-dbgsym: 0.0.6-1 → 0.0.7-1
- ros-humble-mp2p-icp: 1.0.0-1 → 1.2.0-1
- ros-humble-mp2p-icp-dbgsym: 1.0.0-1 → 1.2.0-1
- ros-humble-mrpt2: 2.11.6-1 → 2.11.9-1
- ros-humble-mrpt2-dbgsym: 2.11.6-1 → 2.11.9-1
- ros-humble-nav-2d-msgs: 1.1.12-1 → 1.1.13-1
- ros-humble-nav-2d-msgs-dbgsym: 1.1.12-1 → 1.1.13-1
- ros-humble-nav-2d-utils: 1.1.12-1 → 1.1.13-1
- ros-humble-nav-2d-utils-dbgsym: 1.1.12-1 → 1.1.13-1
- ros-humble-nav2-amcl: 1.1.12-1 → 1.1.13-1
- ros-humble-nav2-amcl-dbgsym: 1.1.12-1 → 1.1.13-1
- ros-humble-nav2-behavior-tree: 1.1.12-1 → 1.1.13-1
- ros-humble-nav2-behavior-tree-dbgsym: 1.1.12-1 → 1.1.13-1
- ros-humble-nav2-behaviors: 1.1.12-1 → 1.1.13-1
- ros-humble-nav2-behaviors-dbgsym: 1.1.12-1 → 1.1.13-1
- ros-humble-nav2-bringup: 1.1.12-1 → 1.1.13-1
- ros-humble-nav2-bt-navigator: 1.1.12-1 → 1.1.13-1
- ros-humble-nav2-bt-navigator-dbgsym: 1.1.12-1 → 1.1.13-1
- ros-humble-nav2-collision-monitor: 1.1.12-1 → 1.1.13-1
- ros-humble-nav2-collision-monitor-dbgsym: 1.1.12-1 → 1.1.13-1
- ros-humble-nav2-common: 1.1.12-1 → 1.1.13-1
- ros-humble-nav2-constrained-smoother: 1.1.12-1 → 1.1.13-1
- ros-humble-nav2-constrained-smoother-dbgsym: 1.1.12-1 → 1.1.13-1
- ros-humble-nav2-controller: 1.1.12-1 → 1.1.13-1
- ros-humble-nav2-controller-dbgsym: 1.1.12-1 → 1.1.13-1
- ros-humble-nav2-core: 1.1.12-1 → 1.1.13-1
- ros-humble-nav2-costmap-2d: 1.1.12-1 → 1.1.13-1
- ros-humble-nav2-costmap-2d-dbgsym: 1.1.12-1 → 1.1.13-1
- ros-humble-nav2-dwb-controller: 1.1.12-1 → 1.1.13-1
- ros-humble-nav2-lifecycle-manager: 1.1.12-1 → 1.1.13-1
- ros-humble-nav2-lifecycle-manager-dbgsym: 1.1.12-1 → 1.1.13-1
- ros-humble-nav2-map-server: 1.1.12-1 → 1.1.13-1
- ros-humble-nav2-map-server-dbgsym: 1.1.12-1 → 1.1.13-1
- ros-humble-nav2-mppi-controller: 1.1.12-1 → 1.1.13-1
- ros-humble-nav2-mppi-controller-dbgsym: 1.1.12-1 → 1.1.13-1
- ros-humble-nav2-msgs: 1.1.12-1 → 1.1.13-1
- ros-humble-nav2-msgs-dbgsym: 1.1.12-1 → 1.1.13-1
- ros-humble-nav2-navfn-planner: 1.1.12-1 → 1.1.13-1
- ros-humble-nav2-navfn-planner-dbgsym: 1.1.12-1 → 1.1.13-1
- ros-humble-nav2-planner: 1.1.12-1 → 1.1.13-1
- ros-humble-nav2-planner-dbgsym: 1.1.12-1 → 1.1.13-1
- ros-humble-nav2-regulated-pure-pursuit-controller: 1.1.12-1 → 1.1.13-1
- ros-humble-nav2-regulated-pure-pursuit-controller-dbgsym: 1.1.12-1 → 1.1.13-1
- ros-humble-nav2-rotation-shim-controller: 1.1.12-1 → 1.1.13-1
- ros-humble-nav2-rotation-shim-controller-dbgsym: 1.1.12-1 → 1.1.13-1
- ros-humble-nav2-rviz-plugins: 1.1.12-1 → 1.1.13-1
- ros-humble-nav2-rviz-plugins-dbgsym: 1.1.12-1 → 1.1.13-1
- ros-humble-nav2-simple-commander: 1.1.12-1 → 1.1.13-1
- ros-humble-nav2-smac-planner: 1.1.12-1 → 1.1.13-1
- ros-humble-nav2-smac-planner-dbgsym: 1.1.12-1 → 1.1.13-1
- ros-humble-nav2-smoother: 1.1.12-1 → 1.1.13-1
- ros-humble-nav2-smoother-dbgsym: 1.1.12-1 → 1.1.13-1
- ros-humble-nav2-theta-star-planner: 1.1.12-1 → 1.1.13-1
- ros-humble-nav2-theta-star-planner-dbgsym: 1.1.12-1 → 1.1.13-1
- ros-humble-nav2-util: 1.1.12-1 → 1.1.13-1
- ros-humble-nav2-util-dbgsym: 1.1.12-1 → 1.1.13-1
- ros-humble-nav2-velocity-smoother: 1.1.12-1 → 1.1.13-1
- ros-humble-nav2-velocity-smoother-dbgsym: 1.1.12-1 → 1.1.13-1
- ros-humble-nav2-voxel-grid: 1.1.12-1 → 1.1.13-1
- ros-humble-nav2-voxel-grid-dbgsym: 1.1.12-1 → 1.1.13-1
- ros-humble-nav2-waypoint-follower: 1.1.12-1 → 1.1.13-1
- ros-humble-nav2-waypoint-follower-dbgsym: 1.1.12-1 → 1.1.13-1
- ros-humble-navigation2: 1.1.12-1 → 1.1.13-1
- ros-humble-pcl-conversions: 2.4.0-4 → 2.4.0-6
- ros-humble-pcl-ros: 2.4.0-4 → 2.4.0-6
- ros-humble-perception-pcl: 2.4.0-4 → 2.4.0-6
- ros-humble-plotjuggler: 3.8.8-3 → 3.9.0-1
- ros-humble-plotjuggler-dbgsym: 3.8.8-3 → 3.9.0-1
- ros-humble-plotjuggler-ros: 2.0.0-3 → 2.1.0-1
- ros-humble-plotjuggler-ros-dbgsym: 2.0.0-3 → 2.1.0-1
- ros-humble-rclpy: 3.3.11-1 → 3.3.12-1
- ros-humble-rcpputils: 2.4.1-1 → 2.4.2-1
- ros-humble-rcpputils-dbgsym: 2.4.1-1 → 2.4.2-1
- ros-humble-rcutils: 5.1.4-1 → 5.1.5-1
- ros-humble-rcutils-dbgsym: 5.1.4-1 → 5.1.5-1
- ros-humble-robotraconteur: 1.0.0-1 → 1.0.0-2
- ros-humble-robotraconteur-dbgsym: 1.0.0-1 → 1.0.0-2
- ros-humble-ros2-control: 2.37.0-1 → 2.39.1-1
- ros-humble-ros2-control-test-assets: 2.37.0-1 → 2.39.1-1
- ros-humble-ros2action: 0.18.8-1 → 0.18.9-1
- ros-humble-ros2cli: 0.18.8-1 → 0.18.9-1
- ros-humble-ros2cli-test-interfaces: 0.18.8-1 → 0.18.9-1
- ros-humble-ros2cli-test-interfaces-dbgsym: 0.18.8-1 → 0.18.9-1
- ros-humble-ros2component: 0.18.8-1 → 0.18.9-1
- ros-humble-ros2controlcli: 2.37.0-1 → 2.39.1-1
- ros-humble-ros2doctor: 0.18.8-1 → 0.18.9-1
- ros-humble-ros2interface: 0.18.8-1 → 0.18.9-1
- ros-humble-ros2lifecycle: 0.18.8-1 → 0.18.9-1
- ros-humble-ros2lifecycle-test-fixtures: 0.18.8-1 → 0.18.9-1
- ros-humble-ros2lifecycle-test-fixtures-dbgsym: 0.18.8-1 → 0.18.9-1
- ros-humble-ros2multicast: 0.18.8-1 → 0.18.9-1
- ros-humble-ros2node: 0.18.8-1 → 0.18.9-1
- ros-humble-ros2param: 0.18.8-1 → 0.18.9-1
- ros-humble-ros2pkg: 0.18.8-1 → 0.18.9-1
- ros-humble-ros2run: 0.18.8-1 → 0.18.9-1
- ros-humble-ros2service: 0.18.8-1 → 0.18.9-1
- ros-humble-ros2topic: 0.18.8-1 → 0.18.9-1
- ros-humble-rqt: 1.1.6-2 → 1.1.7-1
- ros-humble-rqt-console: 2.0.2-3 → 2.0.3-1
- ros-humble-rqt-controller-manager: 2.37.0-1 → 2.39.1-1
- ros-humble-rqt-gui: 1.1.6-2 → 1.1.7-1
- ros-humble-rqt-gui-cpp: 1.1.6-2 → 1.1.7-1
- ros-humble-rqt-gui-cpp-dbgsym: 1.1.6-2 → 1.1.7-1
- ros-humble-rqt-gui-py: 1.1.6-2 → 1.1.7-1
- ros-humble-rqt-mocap4r2-control: 0.0.6-1 → 0.0.7-1
- ros-humble-rqt-mocap4r2-control-dbgsym: 0.0.6-1 → 0.0.7-1
- ros-humble-rqt-py-common: 1.1.6-2 → 1.1.7-1
- ros-humble-rviz-assimp-vendor: 11.2.10-1 → 11.2.11-1
- ros-humble-rviz-common: 11.2.10-1 → 11.2.11-1
- ros-humble-rviz-common-dbgsym: 11.2.10-1 → 11.2.11-1
- ros-humble-rviz-default-plugins: 11.2.10-1 → 11.2.11-1
- ros-humble-rviz-default-plugins-dbgsym: 11.2.10-1 → 11.2.11-1
- ros-humble-rviz-ogre-vendor: 11.2.10-1 → 11.2.11-1
- ros-humble-rviz-ogre-vendor-dbgsym: 11.2.10-1 → 11.2.11-1
- ros-humble-rviz-rendering: 11.2.10-1 → 11.2.11-1
- ros-humble-rviz-rendering-dbgsym: 11.2.10-1 → 11.2.11-1
- ros-humble-rviz-rendering-tests: 11.2.10-1 → 11.2.11-1
- ros-humble-rviz-visual-testing-framework: 11.2.10-1 → 11.2.11-1
- ros-humble-rviz2: 11.2.10-1 → 11.2.11-1
- ros-humble-rviz2-dbgsym: 11.2.10-1 → 11.2.11-1
- ros-humble-sick-scan-xd: 3.1.11-1 → 3.1.11-3
- ros-humble-sick-scan-xd-dbgsym: 3.1.11-1 → 3.1.11-3
- ros-humble-stereo-image-proc: 3.0.0-1 → 3.0.3-1
- ros-humble-stereo-image-proc-dbgsym: 3.0.0-1 → 3.0.3-1
- ros-humble-tf2: 0.25.5-1 → 0.25.6-1
- ros-humble-tf2-bullet: 0.25.5-1 → 0.25.6-1
- ros-humble-tf2-dbgsym: 0.25.5-1 → 0.25.6-1
- ros-humble-tf2-eigen: 0.25.5-1 → 0.25.6-1
- ros-humble-tf2-eigen-kdl: 0.25.5-1 → 0.25.6-1
- ros-humble-tf2-eigen-kdl-dbgsym: 0.25.5-1 → 0.25.6-1
- ros-humble-tf2-geometry-msgs: 0.25.5-1 → 0.25.6-1
- ros-humble-tf2-kdl: 0.25.5-1 → 0.25.6-1
- ros-humble-tf2-msgs: 0.25.5-1 → 0.25.6-1
- ros-humble-tf2-msgs-dbgsym: 0.25.5-1 → 0.25.6-1
- ros-humble-tf2-py: 0.25.5-1 → 0.25.6-1
- ros-humble-tf2-py-dbgsym: 0.25.5-1 → 0.25.6-1
- ros-humble-tf2-ros: 0.25.5-1 → 0.25.6-1
- ros-humble-tf2-ros-dbgsym: 0.25.5-1 → 0.25.6-1
- ros-humble-tf2-ros-py: 0.25.5-1 → 0.25.6-1
- ros-humble-tf2-sensor-msgs: 0.25.5-1 → 0.25.6-1
- ros-humble-tf2-tools: 0.25.5-1 → 0.25.6-1
- ros-humble-tracetools-image-pipeline: 3.0.0-1 → 3.0.3-1
- ros-humble-tracetools-image-pipeline-dbgsym: 3.0.0-1 → 3.0.3-1
- ros-humble-transmission-interface: 2.37.0-1 → 2.39.1-1
- ros-humble-transmission-interface-dbgsym: 2.37.0-1 → 2.39.1-1
- ros-humble-vrpn-mocap: 1.0.4-1 → 1.1.0-1
- ros-humble-vrpn-mocap-dbgsym: 1.0.4-1 → 1.1.0-1
Removed Packages [4]:
- ros-humble-as2-ign-gazebo-assets
- ros-humble-as2-ign-gazebo-assets-dbgsym
- ros-humble-as2-platform-ign-gazebo
- ros-humble-as2-platform-ign-gazebo-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
- Aditya Pande
- Alexey Merzlyakov
- Alvin Sun
- Bence Magyar
- Bernd Pfrommer
- Bianca Bendris
- Brian Wilcox
- CVAR-UPM
- Carl Delsey
- Carlos Orduno
- Chris Lalancette
- David V. Lu!!
- Davide Faconti
- Dirk Thomas
- Dorian Scholz
- Fictionlab
- Francisco Martín
- Francisco Martín Rico
- Jacob Perron
- John Wason
- Jose-Luis Blanco-Claraco
- Matej Vargovcik
- Michael Jeronimo
- Mohammad Haghighipanah
- Paul Bovbel
- Rob Fisher
- Sachin Guruswamy
- Shane Loretz
- Steve Macenski
- Support Team
- Séverin Lemaignan
- Tatsuro Sakaguchi
- Vincent Rabaud
- Víctor Mayoral-Vilches
- Wolfgang Hönig
- fmrico
- rostest
- sachin
- steve
- ymski
5 posts - 4 participants
https://discourse.ros.org/t/new-packages-and-patch-release-for-humble-hawksbill-2024-02-22/36275ROS Discourse General: GTC March 18-21 highlights for ROS & AI robotics
NVIDIA GTC is happening live on March 18–21, with registration open for the event in San Jose, CA.
There are multiple inspiring robotics sessions following the kickoff with CEO Jensen Huang’s must-see keynote at the SAP Center which will share the latest breakthroughs affecting every industry.
Listing some highlight robotics sessions, hands-on-labs, and developers sessions there are:
Hands-on training Labs
- DLIT61534 Elevate Your Robotics Game: Unleash High Performance with Isaac ROS & Isaac Sim
- DLIT61899 Simulating Custom Robots: A Hands-On Lab Using Isaac Sim and ROS 2
- DLIT61523 Unlocking Local LLM Inference with Jetson AGX Orin: A Hands-On Lab
- DLIT61797 Training an Autonomous Mobile Race Car with Open USD and Isaac Sim
Jetson and Robotics Developer Day
- SE62934 Introduction to AI-Based Robot Development With Isaac ROS
- SE62675 Meet Jetson: The Platform for Edge AI and Robotics
- SE62933 Overview of Jetson Software and Developer Tools
Robotics focused sessions
- S63374 (Disney Research) Breathing Life into Disney’s Robotic Characters with Deep Reinforcement Learning
- S62602 (Boston Dynamics) Come See an Unlocked Ecosystem in the Robotics World
- S62315 (The AI Institute) Robotics and the Role of AI: Past, Present, and Future
- S61182 (Google DeepMind) Robotics in the Age of Generative AI
- S63034 Panel Discussion on the Impact of Generative AI on Robotics
This is a great opportunity to connect, learn, and share with industry luminaries, robotics companies, NVIDIA experts, and peers face-to-face.
Thanks.
2 posts - 2 participants
https://discourse.ros.org/t/gtc-march-18-21-highlights-for-ros-ai-robotics/36274ROS Discourse General: New Packages for Noetic 2024-02-22
We’re happy to announce 0 new packages and 136 updates are now available in ROS Noetic. This sync was tagged as noetic/2024-02-22
.
Thank you to every maintainer and contributor who made these updates available!
Package Updates for ROS Noetic
Added Packages [0]:
Updated Packages [136]:
- ros-noetic-care-o-bot: 0.7.10-1 → 0.7.11-1
- ros-noetic-care-o-bot-desktop: 0.7.10-1 → 0.7.11-1
- ros-noetic-care-o-bot-robot: 0.7.10-1 → 0.7.11-1
- ros-noetic-care-o-bot-simulation: 0.7.10-1 → 0.7.11-1
- ros-noetic-cob-3d-mapping-msgs: 0.6.19-1 → 0.6.20-1
- ros-noetic-cob-actions: 0.7.9-1 → 0.7.10-1
- ros-noetic-cob-android: 0.1.10-1 → 0.1.11-1
- ros-noetic-cob-android-msgs: 0.1.10-1 → 0.1.11-1
- ros-noetic-cob-android-resource-server: 0.1.10-1 → 0.1.11-1
- ros-noetic-cob-android-script-server: 0.1.10-1 → 0.1.11-1
- ros-noetic-cob-android-settings: 0.1.10-1 → 0.1.11-1
- ros-noetic-cob-base-controller-utils: 0.8.22-1 → 0.8.23-1
- ros-noetic-cob-base-drive-chain: 0.7.15-1 → 0.7.16-2
- ros-noetic-cob-base-velocity-smoother: 0.8.22-1 → 0.8.23-1
- ros-noetic-cob-bms-driver: 0.7.15-1 → 0.7.16-2
- ros-noetic-cob-bringup: 0.7.9-1 → 0.7.10-1
- ros-noetic-cob-bringup-sim: 0.7.7-1 → 0.7.8-1
- ros-noetic-cob-calibration-data: 0.6.18-1 → 0.6.19-1
- ros-noetic-cob-cam3d-throttle: 0.6.19-1 → 0.6.20-1
- ros-noetic-cob-canopen-motor: 0.7.15-1 → 0.7.16-2
- ros-noetic-cob-cartesian-controller: 0.8.22-1 → 0.8.23-1
- ros-noetic-cob-collision-monitor: 0.7.8-1 → 0.7.9-1
- ros-noetic-cob-collision-velocity-filter: 0.8.22-1 → 0.8.23-1
- ros-noetic-cob-command-gui: 0.6.33-1 → 0.6.34-1
- ros-noetic-cob-command-tools: 0.6.33-1 → 0.6.34-1
- ros-noetic-cob-common: 0.7.9-1 → 0.7.10-1
- ros-noetic-cob-control: 0.8.22-1 → 0.8.23-1
- ros-noetic-cob-control-mode-adapter: 0.8.22-1 → 0.8.23-1
- ros-noetic-cob-control-msgs: 0.8.22-1 → 0.8.23-1
- ros-noetic-cob-dashboard: 0.6.33-1 → 0.6.34-1
- ros-noetic-cob-default-env-config: 0.6.13-1 → 0.6.14-1
- ros-noetic-cob-default-robot-behavior: 0.7.9-1 → 0.7.10-1
- ros-noetic-cob-default-robot-config: 0.7.9-1 → 0.7.10-1
- ros-noetic-cob-description: 0.7.9-1 → 0.7.10-1
- ros-noetic-cob-docker-control: 0.6.12-1 → 0.6.13-1
- ros-noetic-cob-driver: 0.7.15-1 → 0.7.16-2
- ros-noetic-cob-elmo-homing: 0.7.15-1 → 0.7.16-2
- ros-noetic-cob-environments: 0.6.13-1 → 0.6.14-1
- ros-noetic-cob-extern: 0.6.18-1 → 0.6.19-1
- ros-noetic-cob-footprint-observer: 0.8.22-1 → 0.8.23-1
- ros-noetic-cob-frame-tracker: 0.8.22-1 → 0.8.23-1
- ros-noetic-cob-gazebo: 0.7.7-1 → 0.7.8-1
- ros-noetic-cob-gazebo-objects: 0.7.7-1 → 0.7.8-1
- ros-noetic-cob-gazebo-plugins: 0.7.7-1 → 0.7.8-1
- ros-noetic-cob-gazebo-ros-control: 0.7.7-1 → 0.7.8-1
- ros-noetic-cob-gazebo-tools: 0.7.7-1 → 0.7.8-1
- ros-noetic-cob-gazebo-worlds: 0.7.7-1 → 0.7.8-1
- ros-noetic-cob-generic-can: 0.7.15-1 → 0.7.16-2
- ros-noetic-cob-grasp-generation: 0.7.8-1 → 0.7.9-1
- ros-noetic-cob-hand: 0.6.10-1 → 0.6.11-1
- ros-noetic-cob-hand-bridge: 0.6.10-1 → 0.6.11-1
- ros-noetic-cob-hardware-config: 0.7.9-1 → 0.7.10-1
- ros-noetic-cob-hardware-emulation: 0.8.22-1 → 0.8.23-1
- ros-noetic-cob-helper-tools: 0.6.33-1 → 0.6.34-1
- ros-noetic-cob-image-flip: 0.6.19-1 → 0.6.20-1
- ros-noetic-cob-light: 0.7.15-1 → 0.7.16-2
- ros-noetic-cob-linear-nav: 0.6.14-1 → 0.6.15-1
- ros-noetic-cob-lookat-action: 0.7.8-1 → 0.7.9-1
- ros-noetic-cob-manipulation: 0.7.8-1 → 0.7.9-1
- ros-noetic-cob-manipulation-msgs: 0.7.8-1 → 0.7.9-1
- ros-noetic-cob-map-accessibility-analysis: 0.6.14-1 → 0.6.15-1
- ros-noetic-cob-mapping-slam: 0.6.14-1 → 0.6.15-1
- ros-noetic-cob-mecanum-controller: 0.8.22-1 → 0.8.23-1
- ros-noetic-cob-mimic: 0.7.15-1 → 0.7.16-2
- ros-noetic-cob-model-identifier: 0.8.22-1 → 0.8.23-1
- ros-noetic-cob-monitoring: 0.6.33-1 → 0.6.34-1
- ros-noetic-cob-moveit-bringup: 0.7.8-1 → 0.7.9-1
- ros-noetic-cob-moveit-config: 0.7.9-1 → 0.7.10-1
- ros-noetic-cob-moveit-interface: 0.7.8-1 → 0.7.9-1
- ros-noetic-cob-msgs: 0.7.9-1 → 0.7.10-1
- ros-noetic-cob-navigation: 0.6.14-1 → 0.6.15-1
- ros-noetic-cob-navigation-config: 0.6.14-1 → 0.6.15-1
- ros-noetic-cob-navigation-global: 0.6.14-1 → 0.6.15-1
- ros-noetic-cob-navigation-local: 0.6.14-1 → 0.6.15-1
- ros-noetic-cob-navigation-slam: 0.6.14-1 → 0.6.15-1
- ros-noetic-cob-object-detection-msgs: 0.6.19-1 → 0.6.20-1
- ros-noetic-cob-object-detection-visualizer: 0.6.19-1 → 0.6.20-1
- ros-noetic-cob-obstacle-distance: 0.8.22-1 → 0.8.23-1
- ros-noetic-cob-omni-drive-controller: 0.8.22-1 → 0.8.23-1
- ros-noetic-cob-perception-common: 0.6.19-1 → 0.6.20-1
- ros-noetic-cob-perception-msgs: 0.6.19-1 → 0.6.20-1
- ros-noetic-cob-phidget-em-state: 0.7.15-1 → 0.7.16-2
- ros-noetic-cob-phidget-power-state: 0.7.15-1 → 0.7.16-2
- ros-noetic-cob-phidgets: 0.7.15-1 → 0.7.16-2
- ros-noetic-cob-reflector-referencing: 0.6.12-1 → 0.6.13-1
- ros-noetic-cob-relayboard: 0.7.15-1 → 0.7.16-2
- ros-noetic-cob-robots: 0.7.9-1 → 0.7.10-1
- ros-noetic-cob-safety-controller: 0.6.12-1 → 0.6.13-1
- ros-noetic-cob-scan-unifier: 0.7.15-1 → 0.7.16-2
- ros-noetic-cob-script-server: 0.6.33-1 → 0.6.34-1
- ros-noetic-cob-sick-lms1xx: 0.7.15-1 → 0.7.16-2
- ros-noetic-cob-sick-s300: 0.7.15-1 → 0.7.16-2
- ros-noetic-cob-simulation: 0.7.7-1 → 0.7.8-1
- ros-noetic-cob-sound: 0.7.15-1 → 0.7.16-2
- ros-noetic-cob-srvs: 0.7.9-1 → 0.7.10-1
- ros-noetic-cob-substitute: 0.6.12-1 → 0.6.13-1
- ros-noetic-cob-supported-robots: 0.6.17-1 → 0.6.18-1
- ros-noetic-cob-teleop: 0.6.33-1 → 0.6.34-1
- ros-noetic-cob-trajectory-controller: 0.8.22-1 → 0.8.23-1
- ros-noetic-cob-tricycle-controller: 0.8.22-1 → 0.8.23-1
- ros-noetic-cob-twist-controller: 0.8.22-1 → 0.8.23-1
- ros-noetic-cob-undercarriage-ctrl: 0.7.15-1 → 0.7.16-2
- ros-noetic-cob-utilities: 0.7.15-1 → 0.7.16-2
- ros-noetic-cob-vision-utils: 0.6.19-1 → 0.6.20-1
- ros-noetic-cob-voltage-control: 0.7.15-1 → 0.7.16-2
- ros-noetic-generic-throttle: 0.6.33-1 → 0.6.34-1
- ros-noetic-ipa-3d-fov-visualization: 0.6.19-1 → 0.6.20-1
- ros-noetic-ipa-differential-docking: 0.6.12-1 → 0.6.13-1
- ros-noetic-jackal-control: 0.8.8-1 → 0.8.9-1
- ros-noetic-jackal-description: 0.8.8-1 → 0.8.9-1
- ros-noetic-jackal-msgs: 0.8.8-1 → 0.8.9-1
- ros-noetic-jackal-navigation: 0.8.8-1 → 0.8.9-1
- ros-noetic-jackal-tutorials: 0.8.8-1 → 0.8.9-1
- ros-noetic-laser-scan-densifier: 0.7.15-1 → 0.7.16-2
- ros-noetic-libdlib: 0.6.18-1 → 0.6.19-1
- ros-noetic-libntcan: 0.6.18-1 → 0.6.19-1
- ros-noetic-libpcan: 0.6.18-1 → 0.6.19-1
- ros-noetic-libphidgets: 0.6.18-1 → 0.6.19-1
- ros-noetic-mrpt2: 2.11.7-1 → 2.11.9-1
- ros-noetic-opengm: 0.6.18-1 → 0.6.19-1
- ros-noetic-plotjuggler: 3.9.0-1 → 3.9.1-1
- ros-noetic-plotjuggler-ros: 2.1.0-1 → 2.1.1-2
- ros-noetic-qb-softhand-industry: 1.0.9-1 → 1.2.5-1
- ros-noetic-qb-softhand-industry-bringup: 1.0.9-1 → 1.2.5-1
- ros-noetic-qb-softhand-industry-control: 1.0.9-1 → 1.2.5-1
- ros-noetic-qb-softhand-industry-description: 1.0.9-1 → 1.2.5-1
- ros-noetic-qb-softhand-industry-driver: 1.0.9-1 → 1.2.5-1
- ros-noetic-qb-softhand-industry-hardware-interface: 1.0.9-1 → 1.2.5-1
- ros-noetic-qb-softhand-industry-msgs: 1.0.9-1 → 1.2.5-1
- ros-noetic-qb-softhand-industry-srvs: 1.0.9-1 → 1.2.5-1
- ros-noetic-qb-softhand-industry-utils: 1.0.9-1 → 1.2.5-1
- ros-noetic-raw-description: 0.7.9-1 → 0.7.10-1
- ros-noetic-scenario-test-tools: 0.6.33-1 → 0.6.34-1
- ros-noetic-service-tools: 0.6.33-1 → 0.6.34-1
- ros-noetic-sick-visionary-ros: 1.1.1-1 → 1.1.2-1
- ros-noetic-urg-stamped: 0.0.17-1 → 0.1.0-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:
- Alexander Bubeck
- Atsushi Watanabe
- Benjamin Maidel
- Davide Faconti
- Felipe Garcia Lopez
- Felix Messmer
- Felix Zeltner
- Florenz Graf
- Florian Weisshardt
- Jannik Abbenseth
- Jose-Luis Blanco-Claraco
- Joshua Hampp
- Loy van Beek
- Matthias Gruhler
- Mike Purvis
- Richard Bormann
- SICK AG TechSupport 3D Snapshot
- Support Team
1 post - 1 participant
https://discourse.ros.org/t/new-packages-for-noetic-2024-02-22/36273ROS Discourse General: Attention Students: Open Robotics Google Summer of Code 2024 Projects
Attention Students,
It is time to get ready for Google Summer of Code (GSoC) 2024! If you are not familiar with GSoC, it is a remote summer internship program where students contribute to open source software projects. GSoC is a great opportunity for graduate and undergraduate students to gain experience developing software and contribute to open source projects. GSoC is an international program, and a great opportunity for students of every background to work with professional software engineers from around the globe. Specific details about this year’s program can be found on the GSoC website. If you are curious about what GSoC looks like at Open Robotics you can find out more about our past programs on the Open Robotics website.
This year the Open-RMF and Gazebo communities will be taking on multiple projects and enhancements, which you can read about here. The application period starts on Monday, 2024-03-18T07:00:00Z UTC , and ends Tuesday, 2024-04-02T07:00:00Z UTC so don’t delay! If you are interested in robotics but don’t see any projects that suit your interests you may also want to consider applying to some of our sibling organizations like OpenCV, MoveIt, and ArduPilot.
Students often ask how they can improve their chances of being accepted to GSoC. We always recommend starting off with a strong application. Other than that here are a few recommendations:
- Familiarize yourself with the project you want to work on. Pull down the latest version, build it from source, and try to do something interesting with it. Try adding a feature or fixing a bug. Many Open Robotics projects have a “Good First Issue” tag. We often select students who are already contributors to our projects as our GSoC students.
- Lend our project maintainers a hand but don’t get over your head. Small pull requests, that address minor issues, are a great way to start! We want to see that you can put together a complete pull request and work well remotely.
- Do cool and interesting stuff and write about it! It doesn’t have to involve ROS or Gazebo, and can be a school project. What we’re looking for is that you have the basics of software development down and that you are working to improve your written communication skills.
- Remember that we’re not looking for perfection. We’re looking for students who work hard, try new things, and learn from their mistakes
One final note, please use the correct channels to talk about GSoC. Questions about GSoC 2024 should be kept on the ROS and Gazebo Discourse forums, the OSRF Discord, or by emailing our mentors directly at gsoc@openrobotics.org.
3 posts - 2 participants
https://discourse.ros.org/t/attention-students-open-robotics-google-summer-of-code-2024-projects/36271ROS Discourse General: [offtopic] Can anything stop ROS?
For ROS Con2023, I put together this audio abstract as a talk proposal. It was not accepted.
spoilers (click for more details)5 posts - 3 participants
https://discourse.ros.org/t/offtopic-can-anything-stop-ros/36261ROS Discourse General: Gazebo Classic End-Of-Life & ROS 2 Jazzy
Gazebo Classic End-Of-Life & ROS 2 Jazzy
tl;dr: Gazebo Classic goes end-of-life in January of 2025 and ROS 2 Jazzy will not support Gazebo Classic. We strongly recommend all users migrate from Gazebo 11 (Classic) to modern Gazebo (formerly known as Ignition) before January 2025. If you are still using Gazebo Classic with ROS 2 you will need to upgrade to a modern Gazebo release to use ROS 2 Jazzy Jalisco.
Late last year Gazebo Classic 11 was removed from Debian Testing and Unstable when it stopped building from source in their distribution. With this change in Debian, future releases of Debian and Ubuntu will not have Gazebo Classic available, including the upcoming Debian Bookworm and Ubuntu 24.04 Nobel Numba releasest. OSRF will maintain Gazebo Classic 11 support on Ubuntu 20.04 (Focal) until the Gazebo 11 end of life in January 2025. Gazebo 11.10.2 is also available in Ubuntu Jammy directly from Ubuntu repositories. A full list of Gazebo Classic versions, and their support lifetimes, can be found on the Gazebo Downloads page.
ROS 2 Iron Irwini on Ubuntu 22.04 will be the last ROS release with an associated version of Gazebo Classic (Gazebo 11). ROS 2 Iron has official binary support for Gazebo Fortress, but due to conflicts with the Ubuntu version of Gazebo Classic, Gazebo Harmonic and Gazebo Garden are only supported when built from source. For more information see the Gazebo and ROS 2 compatibility matrix. For more information regarding what versions of ROS are supported on which operating systems please refer to REP-2000.
The next ROS 2 LTS release, Jazzy Jalisco, is scheduled for release on May 23rd, 2024. ROS 2 Jazzy will target Gazebo Harmonic, and there will be no official Gazebo Classic support. Package maintainers depending on Gazebo Classic should consider a deprecation plan for Gazebo Classic support in ROS 2 Iron.
We understand that migration can be a difficult process. To aid the ROS & Gazebo communities with upgrading we’ve created a migration guide that walks you step-by-step through the process. The Gazebo core maintenance team will hold regular Gazebo migration office hours to assist the community with migration. If you need help planning your migration, or have a specific question about migration, please swing by our office hours. Details for the next office hours are below:
2024-03-12T16:00:00Z UTC
Video call link: https://meet.google.com/fes-rgpj-fpv 4
Or dial: (US) +1 952-243-1467 PIN: 561 935 002#
1 post - 1 participant
https://discourse.ros.org/t/gazebo-classic-end-of-life-ros-2-jazzy/36239ROS Discourse General: Announcing MoveIt Pro Runtime and Developer Platform (previously MoveIt Studio)
Hi ROS Community!
We are excited to announce our commercial grade solution for robot arms, that is 100% built on ROS 2 and MoveIt 2: MoveIt Pro. Previously known as MoveIt Studio, we have recently changed the product’s name to MoveIt Pro to better align with the capabilities and value that it delivers. Read the full blog post to learn more about the rebranding.
What is MoveIt Pro?
MoveIt Pro is both a runtime engine that integrates tightly into your ROS 2 codebase, as well as an optional developer platform. MoveIt Pro simplifies the development of ROS-based robotics applications by providing an extensive library of drop in capabilities for ML, perception, grasping, admittance control, and of course motion planning & control. It’s pre-integrated with BehaviorTree.cpp, the popular decision making framework, and features a fully integrated development environment for editing behavior trees, debugging, and introspection. And it’s fully expandable, allowing you to create your own “Behavior” plugins that compile in your regular colcon workspace using ROS 2. This makes it easy to continue leveraging your existing ROS 2 nodes and user interfaces.
What is MoveIt Pro used for?
MoveIt Pro is designed for deploying robotic arms in unstructured environments, outside of factories, and is based on PickNik’s 8 years of working with customers solving some of the hardest problems with robot arms. Example applications currently include strawberry picking, deep sea robotics, construction, medical surgery, and low gravity space applications. New use cases are only limited by your imagination!
How we are supporting open source
PickNik is making more open source contributions than ever before to ROS 2, MoveIt 2, ROS 2 Control, roslibjs, and Gazebo. We are proud of our continued commitment to our community and as we have deployed MoveIt Pro to production environments, we have worked hard to ensure that ROS 2 (and yes, DDS) is robust.
How it helps your company
MoveIt Pro accelerates ROI and time-to-market, reducing software engineering time from ideation to prototype to production. We also provide the necessary support, warranties, certifications, and uptime guarantees that critical applications need. We’ve helped many companies avoid the years of R&D when leveraging robot arms, and can work with your team to co-develop an MVP in a matter of weeks.
Checkout our MoveIt Pro product page and don’t hesitate to reach out to me! I’d love to hear your feedback - positive or negative.
Thanks,
davetcoleman
dave@picknik.ai
1 post - 1 participant
https://discourse.ros.org/t/announcing-moveit-pro-runtime-and-developer-platform-previously-moveit-studio/36235ROS Discourse General: ROS 2 Meeting Minutes 2024-02-15
ROS 2 TSC Contribution Report 2024-02-15 - Google Docs.pdf (107.4 KB)
ROS 2 TSC Meeting Minutes 2024-02-15
-
Attendees
- TSC Members
- OSRF / Geoff Biggs
- Community / Francisco Martin Rico
- Robotis / Will Son
- Intrinsic.ai / Chris Lalancette
- Intrinsic.ai / Katherine Scott
- Canonical / Mirko Ferrati
- Community / David Lu!!
- Picknik / Henning Kayser
- Foxglove / Adrian Macneil
- eProsima / Jaime Martin Losa
- iRobot / Alberto Soragna
- Apex.AI / Lyle Johnson, Michael Orlovlov
- Bosch / Christian Henkel
- Bosch / Christian Henkel
- Sony / Tomoya Fujita
- Toyota Research Institute / Ian McMahon
- ROS Industrial / Matt Robinson
- Amazon / Matt Hansen
- Devcom / Jerry Towler
- Wind River / Andrei Kholodnyi
- TSC Observers
- Bence Magyar
- Absent (Please move to TSC Members Line):
- Intel / Harold Lang
- Microsoft / Lou Amadio
- Zettascale / Angelo Corsaro
- Community / Steve Macenski
- TSC Members
-
Preliminaries
- You should only have comment access to this document.
- [Kat ][1 min] Please remember to fill out your contribution report at the bottom of this document prior to the meeting.
- ROSCon Diversity Scholarships out today. Sponsorship in the next few weeks.
-
Old business
-
New business
- [Kat][20min] 2023 Metrics Report
- [David][20min] metrics.ros.org supplement.
- Tentative: REP-145 Amendment Discussion
- Steve – work stopped after Samsung
- Notes from ROS 2 Meeting [2-13-2024]
- Given other pressing business we may move this discussion to the end.
- Chris – given Steve’s feelings we should close the REP.
- TODO: Next meeting REP-2017
- [Kat][20min] 2023 Metrics Report
-
Confidential Business
- [STOP] – ALL NON-TSC MEMBERS MUST LEAVE THE HANGOUT
- [Geoff][20] Discussion
- [Mirko][20min] Discussion
- [STOP] – ALL NON-TSC MEMBERS MUST LEAVE THE HANGOUT
-
Recurring business
- Next ROS 2 distro release
- rmw_zenoh_cpp
- Development still moving along
- Support for services, QoS landed
- Working on events now
- Opened up Items to finish before Jazzy release · Issue #110 · ros2/rmw_zenoh · GitHub to track remaining issues for Jazzy (subject to change)
- Jazzy
- Working on some changes to the way python is found
- Should make ROS 2 builds with venvs work better
- Transition to Ubuntu 24.04 is continuing
- Last meeting said transition Feb 5
- We didn’t do this because Python 3.12 default still hasn’t landed
- Transition now dependent on when that lands, with drop-dead date of March 8
- Working on two major problems
- uncrustify - new version isn’t totally compatible with old version
- Working on making them as compatible as possible
- But some downstream code is likely to have to change
- pycodestyle is incompatible with flake8
- Seems to be a bug in Ubuntu 24.04
- We’ll open a bug about this shortly
- uncrustify - new version isn’t totally compatible with old version
- Last meeting said transition Feb 5
- Reminder that RMW freeze date is April 8th, overall freeze is April 15
- Working on some changes to the way python is found
- rmw_zenoh_cpp
- Working groups [<=5 mins each]
-
[Bence] Control
- Latest Humble sync issues breaking webots compilation, fixed in latest release to Humble
- New concept for gripper controllers using JointState message
- All CI now hosted in a single place, ros2_control_ci as reusable workflows
- Discussions on robot_description strategies for Humble vs Rolling
- Lots and lots of Gazebo (& Gz Classic) bugfixes and improvements
- set_hardware_component_state rolled out Humble to Rolling
- Discussions on std::variant in ros2_control interface handles
- Windows support PRs coming in, beware! (robostack community)
- generate_parameter_library for all controllers also in Humble
- RHEL(8,9) and Debian(11,12) CI on PRs
-
[Martin Losa] Embedded
- Farhang Naderi, Co-Founder & Chief Tech Officer at Caretta Robotics, will presented two exciting projects. The first combines PX4 Autopilot, ROS2, Pixhawk 6X, and Micro XRCE-DDS for precise drone positioning. The second uses Pixhawk, Raspberry Pi CM4, ROS2, and Micro XRCE-DDS to enable drones to track and follow objects in real-time. These projects showcase significant advancements in drone operations and interactions with their environment.
- EWG Video
-
[Kayser] Manipulation
- Applying as GSoC 2024 org - Projects Page
- Preparing for Jazzy migration
- Starting to phase out Gazebo Classic in tutorials and resources
-
[Woodall] Middleware
-
[Macenski] Navigation
-
[Andrei] Real-Time
- REP2017
- Working on RPI5 PREEMPT_RT
-
[Biggs] Client libraries
-
[Mirko] Security
- The group discussed the PR for PKCS#11, and gave input to resolve the most recent points brought up by the maintainers.
-
[Soragna] Production
- Meeting notes: Meeting Agenda - Google Docs
- Discussed project management tasks and how to start working
- Easy to use build and package tool for a custrom forks of ros2 · Issue #7 · bpwilcox/ros2-production-working-group · GitHub It should be easy to build custom versions of ROS 2 (e.g. to cherry-pick fixes/features). Every company is using a different approach and none of them feels great
- Summarize how to research licenses · Issue #10 · bpwilcox/ros2-production-working-group · GitHub Enforcing correctness of license files
-
[Orlov] Rosbag2 and Tooling
- Fixed race condition in
rosbag2_storage_mcap
package Use rw_lock to protect mcap metadata lists (rosbag2#1561) - Made progress on the following PRs:
- Support service 2/2 — rosbag2 service play (rosbag2#1481)
- Use middleware receive timestamp instead of now (rosbag2#1531) Decided to store
send_timestamp
in a dedicated field in the mcap we already have a special field for that.
- Discussed how to store message’s sequence numbers. The problem is that there could be multiple publishers per topic and the sequence number will not be unique per topic and will jump around and repeat in this case. One option would be to store the publisher ID or encode it to the sequence number. However, we can’t afford this because the publisher ID type is defined as 16 bytes long. The more appropriate solution would be to be able to store stream from each publisher as a separate topic_id aka channels. However, we will need to make significant structural changes in the rosbag2 to be able to differentiate topics by ID instead of name Use topic_id instead of topic_name in inner rosbag2 buffers and data structures #1553
- Fixed race condition in
-
- Next ROS 2 distro release
2 posts - 2 participants
https://discourse.ros.org/t/ros-2-meeting-minutes-2024-02-15/36221ROS Discourse General: PlotJuggler 3.9.1 is out! And few more things you should know
New version
PlotJuggler 3.9.1 and plotjuggler-ros-plugins 2.1.1 are available and they both fix some important bugs in both ROS1 and ROS2.
As explained in the README you are encouraged to use snap, since the next release of the ROS Debian packages may take a while.
A word about the latest unstable releases
I should apologize for the fact that PlotJuggler has been unstable/broken in the last few releases
I know it was annoying for a lot of you, but unfortunately this was an undesired consequence of a number of refactorings that I have been doing, to remove code duplication in the ROS plugins.
Finally, there is a single message parser that can decode both ROS1, ROS2, raw MCAP files and DataTamer.
This latest release should fix most of the regressions, but if you see anything suspicious, let me know.
It is worth mentioning that I am still maintain PlotJuggler in my spare (AKA “unpaid”) time and despite some PR that I appreciate a LOT, most of the work falls on my shoulders (this is true for other libraries, that I am developing and supporting, being Behaviortree.CPP a notable example).
Your company can help !!!
And this brings me to my second topic!
Nothing would make me happier to give you a tool that you can rely on, and reduce the time you spend debugging your robots.
In many ways, I believe (hope?) I did that, but it is also discouraging to see that very few companies have decided to support this effort in any meaningful way.
It turns out that now is a particular good time (for personal reasons not worth mentioning here) for your company to support the future of PlotJuggler.
This can happen through sponsorship, but I know that this might be a tough call (“paying for open source software?”).
So my pragmatic question is: is there any feature that YOU (not “someone”, I mean YOU) would pay for, if implemented in PlotJuggler?
If you can figure out any improvement in PlotJuggler that can save you time (and money), let me know!
Shoutout to Dexory, that paid recently to implement an exciting feature that I hope to release soon!
7 posts - 4 participants
https://discourse.ros.org/t/plotjuggler-3-9-1-is-out-and-few-more-things-you-should-know/36210ROS Discourse General: We use websockets and ROS messaging together in our robot software stack, should you?
At PickNik we use both websockets and ROS networks. I’ve started to see many others doing the same and so I wrote a blog post about it here.
Let me know what you think.
8 posts - 4 participants
https://discourse.ros.org/t/we-use-websockets-and-ros-messaging-together-in-our-robot-software-stack-should-you/36199ROS Discourse General: MCAP file editor (GUI)... in your browser!
Hi,
this is a small weekend project that I would like to share with the community (it might be a bit rough around the edges).
It is a graphical editor to modify your MCAP files. It allows you to:
- Remove topics.
- Cut the time range.
- Change the compression method.
And you can try it right now in your browser!
https://mcap-editor.netlify.app/
The source code can be found here: GitHub - facontidavide/mcap_editor: MCAP editor (GUI)
1 post - 1 participant
https://discourse.ros.org/t/mcap-file-editor-gui-in-your-browser/36198PAL Robotics blog: PRO-CARED pilots: robot ARI as education robot helping students with Catalan language
Integrating robots into education brings a number of potential benefits to the sector, such as enhancing the learning experience for students, and helping users prepare for a changing and advancing technological landscape. Here we talk more about the PRO-CARED project for robots in education that PAL Robotics partners in, and the upcoming project pilots where
The post PRO-CARED pilots: robot ARI as education robot helping students with Catalan language appeared first on PAL Robotics Blog.
https://blog.pal-robotics.com/pro-cared-pilots-robot-ari-as-education-robot-with-catalan-language/ROS Discourse General: Improving Search for ROS Docs - Technical
Topic
This is in continuation with: this ticket
My finds so far
Pagefind:
Pagefind is a fully static search library that aims to perform well on large sites, while using as little of your users’ bandwidth as possible, and without hosting any infrastructure.
Pagefind runs after Hugo, Eleventy, Jekyll, Next, Astro, SvelteKit, or any other website framework. The installation process is always the same: Pagefind only requires a folder containing the built static files of your website, so in most cases no configuration is needed to get started.
Nextra
I don’t know how they implement search but this is what I found:
They support mermaind and latex
8 posts - 4 participants
https://discourse.ros.org/t/improving-search-for-ros-docs-technical/36153ROS Discourse General: ROS News for the Week of February 12th, 2024
ROS News for the Week of February 12th, 2024
ROSCon 2024 in Odense, Denmark was announced this week! We also kicked off our 2024 Diversity Scholarship Program.
This week our friends at Hello Robot released version 3 of their Stretch robot. Stretch is a lower cost mobile manipulator and they’ve been absolutely killing it in the research world lately. Robot Report – Tech Crunch – IEEE Spectrum
Following from this discussion on the, “Growing issues with ROS Documentation” I want to point out this article from the ReadMe project over at Github. As a project contributor, some weeks are very frustrating, and it feels like we can’t win, no matter what we do. It would really help the project if people kept in mind that the core team is just a two-person non-profit, and about a dozen core maintainers, many of whom can only work on the project part time. It would really help us if everyone was a little bit more thoughtful and aware of the situation.
If there is something you would like to see improved, please feel free to pitch in! All big changes start with small changes, and you don’t need anyone’s permission or some grand initiative to get started. The best places to start are with the things you are already using. The best way to learn is by doing! A little pull request is the best way to get familiar with package, so please, try and help improve the project for the next person who comes along.
Leading by example, a few of us did just that this week! @mikeferguson helped out by updating the image proc docs this week. In between everything else I did this week I wrote a tutorial on migrating ROS Wiki documentation to docs.ros.org. @azeey wrote a whole Gazebo migration guide. @tfoote and @gonzodepedro landed Mermaid.js chart support in the docs. We even had someone from the community toss in a nice little improvement on the TF docs. Despite all this there’s still a lot that could be done and little bit of help would be appreciated.
Events
- 2024-02-20 Maritime Working Group Meeting
- 2024-02-22 Manipulation Working Group Meeting
- 2024-03-14 TU Delft ROS MOOC (FREE!)
- 2024-03-27 ROS Industrial Annual Meeting
- 2024-04-21 Robots on Ice – Save the Date
- 2024-05-03 Open Hardware Summit Montreal
- 2024-05-13 Bots & Bento @ ICRA 2024
- 2024-06-04 → 2024-06-08 ACM SIGSOFT Summer School on Software Engineering for Robotics
- 2024-06-?? Workshop on Agriculture Vision at CVPR 2024
- 2024-06-16 Food Topping Challenge at ICRA 2024
- 2024-06-19 => 2024-06-20 ROSCon France
- 2024-08-05 Autonomous Systems Bootcam at Univ. Deleware– Video
- 2024-09-25 ROSConJP
News
- Non-Code Contributions are the Secret to Open Source Success
- Hello Robot Stretch V. 3 – Tech Crunch – IEEE Spectrum
- North American Robot Orders Drop 30%
- Hippo Harvest Lands $21M Series B
- Jaco Deep Grasp
- Kudan Mobile Robot Dev Kit
- Making Disruptive Tech Not Disruptive: Exciting Uses for Robots on Farms
- ICRA Workshop on Unconventional Robots
- What is ROS? Why it is important for Robotics Software Engineers
- Matrix Lie Groups & Lie Algebra for Robotic
- LIDAR Point Labeler
- Marine Pipe Dataset
- eProsima Fast DDS Monitor
- OpenCV 5 Project Board
- X-ICP: Localizability-Aware LiDAR Registration for Robust Localization in Extreme Environments
- ROS Japan UG #54 関西ROSJP
- Optimizing Robotics Algorithms With C++'s Compile-Time Features
- Video Friday
ROS
- ROSConDE 2023 Videos
- Raspberry Pi for Robotics with ROS2 : Headless Development Setup
- ROS / Gazebo Project Template
- ROS 2 Image Pipeline Docs
- ROS MoveIt Servo with Kinova Arm
- Beluga: Monte Carlo Localization (MCL) algorithms written in C++17 for ROS
- Issac ROS 2 Control
- Humble on RISC-V?
- Handling Per-Robot Parameters?
- Documentation Pile On
- COOL Gazebo Classic Migration Guide + Office Hours
- Pkl (“pickle”) - new configuration language developed by Apple
- ROS 2 Fast-DDS Discovery Server with Kubernetes
- Rerun 0.13 Release
- Robot Climate Jobs
- Proposal Restrict DDS to Localhost by Default
- ROS2Webots
- SpaceROS Humble
- Improving the Autoware Developer Experience
- Autoware Challenge Presentations
- ROS 2 on M1 Mac
ROS Questions
Please, help out your fellow developers by taking an hour to go answer a few questions over on Robotics Stack Exchange.
3 posts - 3 participants
https://discourse.ros.org/t/ros-news-for-the-week-of-february-12th-2024/36135ROS Discourse General: Announcing ROSCon 2024 in Odense, Denmark + Diversity Scholarships :tada:
Announcing ROSCon 2024 in Odense, Denmark + Diversity Scholarships
I am happy to announce that we just launched the ROSCon 2024 website! This year’s ROSCon will take place in Odense, Denmark 2024-10-20T22:00:00Z UTC through 2024-10-22T22:00:00Z UTC.
Odense is an adorable city, with an outsized robotics industry, located on the island of Funen in Denmark. Odense is a fairytale location for a robotics conference, and we’re working with the city of Odense to roll out the red carpet for ROSCon 2024! We’re going to be taking over a good chunk of Odense’s central city, and providing lots of opportunities to meet with the local robotics community. If you are worried about travel, don’t despair, thanks to the Danish rail system Odense is just a short rail trip from Copenhagen airport. Speaking of trains, we might be potentially planning a trip to the Danish Railway Museum.
If you’re a ROS developer you won’t want to miss ROSCon 2024; we’ll have most of the ROS core developers and contributors all in one place for three days for talks, workshops, birds-of-a-feather sessions, robot demonstrations, and vendor exhibitions. Last year all of our workshops sold out, so this year we’re increasing the number of available workshop seats along with the total number of workshops. We’re also making birds-of-a-feather sessions a first-class function for 2024 such that individual working groups and projects can set aside dedicated time to meet. As in previous years we’re planning two full days of talks from all your favorite developers, along with two developer focused panels, and two of our world famous ROSCon lightning talk sessions. Just like ROSCon 2023 and ROSCon 2022 we’ll have an exhibition space with 40-60 exhibitors and a dedicated area for robot demos.
ROSCon 2024 Diversity Scholarships
For ROSCon 2024 we’ve had some changes to our Diversity Committee. We’re proud to welcome a new Diversity Co-Chair to the ROSCon Diversity Committee, @KimMcG , who runs our Aerial Robotics Working Group. Kimberly is replacing @mjcarroll, who is retiring after a number of years of service. We would like to thank Michael Carroll for his many years of service on the ROSCon diversity committee. This year Kimberly is joined by returning Diversity Committee Co-Chair @Belen_Torres (Belen Torres).
Our diversity committee has their work cut out for them this year! Thanks to the generous support of the ROS community, and Clearpath Robotics CTO Ryan Gariepy (@rgariepy) in particular, this year’s ROSCon Diversity Scholarship program is going to be one of our largest yet. To accommodate all of our Diversity Scholars we’ve greatly accelerated the application schedule; these changes should provide more time for students to plan their travel and apply for visas. As such, we’re happy to announce that the Diversity Scholarship application form is already live, and full scholarship details are on the ROSCon 2024 website. The deadline for scholarship applications is 2024-04-06T06:59:00Z UTC, but we encourage applicants to apply as soon as possible. If you are considering submitting a ROSCon 2024 talk and you require travel assistance please make sure to apply, you won’t be able to submit an application with your talk proposal.
ROSCon CFP and Important Dates
In the next few weeks we’ll put out the call for talks and workshops along with our prospectus for ROSCon 2024 sponsorship. If you happen to work at a larger robotics company, you may want to give your HR & marketing departments a heads up that the ROSCon website is now live. To aid everyone with planning I’ve included all of the important dates for ROSCon 2024 below; I suggest putting them in your calendar so they don’t sneak up on you. If you are considering putting together a ROSCon 2024 workshop you should start planning your workshop proposal now, as the workshop and talk CFP opens up in just one month!
- Call for Proposals circulated- March 15th, 2024 2024-03-15T07:00:00Z UTC
- Diversity Scholarship application deadline - 2024-04-05T07:00:00Z UTC
- Workshop submission deadline - 2024-05-07T07:00:00Z UTC
- Proposal submission deadline - 2024-06-03T07:00:00Z UTC
- Early registration deadline - 2024-06-03T07:00:00Z UTC
- Proposal acceptance notification - 2024-07-08T07:00:00Z UTC
- Late registration starts - - 2024-10-01T07:00:00Z UTC
I hope to see all of you in Odense this October !
3 posts - 2 participants
https://discourse.ros.org/t/announcing-roscon-2024-in-odense-denmark-diversity-scholarships/36107ROS Discourse General: X-Post: Gazebo Migration Guide and Gazebo Migration Office Hours
Hi Everyone,
Quick cross-post from the GazeboSim community. As you should already be aware, Gazebo Classic goes end-of-life in about a year. To help people transition to modern Gazebo @azeey has put together a migration guide. If you are currently using Gazebo Classic, and would like to learn how to migrate to modern Gazebo, please take a look. We’re also planning to host regular office hours to answer questions about the migration process.
The original post can be found here
1 post - 1 participant
https://discourse.ros.org/t/x-post-gazebo-migration-guide-and-gazebo-migration-office-hours/36091ROS Discourse General: Growing issue with ROS Documentation
Growing issues with the ROS 2 documentation ecosystem
I previously brough this issue up for the ROS Noetic where the documentation can be improved.
This has only further worsened for ROS2, There have been several pitfalls
Key pit falls:
- Poor SEO for Iron, most documentation points to humble or foxy
- Poor full text search responses (Algolia would really help here)
Example 1:
Example 2 (I’d understand why DL frameworks like Torch isn’t documented but this is not the way to go)
- Lack of migration guides
- Lack of instructions on how to mitigate failing ROS2 builds for ecosystems beyond Ubuntu/Debian
- Poor explanation of how to use it in the cloud
With all these points in hand, I strongly feel there is a stronger need for a more consolidated effort that focuses on documentation
94 posts - 25 participants
https://discourse.ros.org/t/growing-issue-with-ros-documentation/36075ROS Discourse General: Handle unique parameters for robot instances
We have a software with a lot of parameters and have multiple versions of the same robot. Most the parameters are “general”, meaning they are the same for all of of the robots, some of them are “per series”, meaning each robot series will share the same values (e.g. joint limits, feature flags, etc…), and some of them are “per instance”, meaning each physical robot will have a unique value (e.g. calibration values).
I tried to architecture something that allows us this flexibility while not increasing the maintenance cost of changing a value.
We use ROS1 (for now). I created a hierarchy of YAML file and use YTT. YTT allows to “code” inside the YAML file, and most importantly for us, to merge and override values.
It roughly looks like this:
./acme_config
./global
./domain.yaml
./limits.yaml
./controllers.yaml
./series
./1.0
./limits.yaml
./1.1
./limits.yaml
./domain.yaml
# On the robot itself
/etc/acme
./calibration.yaml
./limits.yaml
I run YTT on this to output a single YAML file that I load using the rosparam
directive of roslaunch.
I’ve simplified a bit, for example YTT allow two layers, one called “data-values” that can then be accessed in the more regular YAML file, which I try to use to keep the values separated from the “structure” of the parameters. Also, I can make it so the 1.1 series inherits from the 1.0 series values.
What I don’t like about this architecture is that it adds distance between the parameters and their actual use in the rosnodes. Also, using the “data-values” I can handle backward-compatibility but it’s not always easy.
Did someone else encountered this problem? What are your findings? Any clue how ROS2 would make this easier/more difficult? I guess the Python launch files would add a bit of flexibility.
18 posts - 9 participants
https://discourse.ros.org/t/handle-unique-parameters-for-robot-instances/36074ROS Discourse General: Robotics/ROS Arab Meetup
Exciting News Alert!
Thrilled to share that we’re hosting the inaugural Robotics/ROS Arab Meetup! Join us as we welcome Professor Anis Koubaa to dive deep into “Leveraging the Unseen: Exploring Generative AI with Robotics.”
This groundbreaking discussion will explore the transformative potential of Generative AI in robotics, unlocking unparalleled creativity and autonomy in machines. From revolutionizing decision-making to fostering adaptive, self-improving robots, discover how this fusion is reshaping the robotics landscape, setting new standards in efficiency, innovation, and opportunities.
Stay tuned for more updates and save the date for this enlightening conversation!
save time on the calendar:
https://buff.ly/48i238X
You can find the meeting link here:
https://buff.ly/49bQOA8
1 post - 1 participant
https://discourse.ros.org/t/robotics-ros-arab-meetup/36062ROS Discourse General: ROS News for the Week of February 5th, 2024
ROS News for the Week of February 5th, 2024
Autonomous Systems Bootcamp - Welcome
This was the week of robotics workshops and classes. There are a bunch of great events planned for the next few months including a free ROS MOOC at TU Delft, an ACM summer school on software engineering for robotics, and an autonomous systems bootcamp at University of Deleware.
While there have been a lot of robotics companies holding layoffs and shutting down it appears robotics investments are still up. For December 2023 there were $749M in robotics investments.
The first ROS Meetup in Lagos, Nigeria was a resounding success! I was super excited to see the social media posts roll in over the weekend. Here’s to many more events to come Image source
ICRA2024 - A Method for Multi-Robot Asynchronous Trajectory Execution in MoveIt2
Brace yourself, the ICRA 2024 pre-print papers are starting to come out! Above is the video for, “A Method for Multi-Robot Asynchronous Trajectory Execution in MoveIt2.” Also checkout, “CrazySim A Software-In-The-Loop Simulator for CrazyFly Drones.”
Events
- 2024-02-13 Pittsburgh Robotics and Tech Happy Hour
- 2024-02-20 Maritime Working Group Meeting
- 2024-02-22 Manipulation Working Group Meeting
- 2024-03-14 TU Delft ROS MOOC (FREE!)
- 2024-03-27 ROS Industrial Annual Meeting
- 2024-04-21 Robots on Ice – Save the Date
- 2024-05-03 Open Hardware Summit Montreal
- 2024-05-13 Bots & Bento @ ICRA 2024
- 2024-06-04 → 2024-06-08 ACM SIGSOFT Summer School on Software Engineering for Robotics
- 2024-06-?? Workshop on Agriculture Vision at CVPR 2024
- 2024-06-16 Food Topping Challenge at ICRA 2024
- 2024-06-19 => 2024-06-20 ROSCon France
- 2024-08-05 Autonomous Systems Bootcam at Univ. Deleware– Video
- 2024-09-25 ROSConJP
News
- $749M in Robotics Investment in December 2023
- Dexory’s massive shelf-scanning robot comes to North America
- RAP-SAM:Towards Real-Time All-Purpose Segment Anything
- Daedalus Raises $21M for Precision Manufacturing
- Starship Raises another $91M – Robot Report
- New Mass Robotics Accelerator Class
- Waymo Hits Cyclist in SF
- Video Friday
- Robot Tongues for Robot Geckos
- AutoNavSim2D: 2D simulation environment designed for the development and testing of path planning algorithms.
- Weekly Robotics
- BBC on Indy Autonomous Challenge
- Iridescence: Rapid Prototyping for 3D Algorithms
- Dave Builds Real Life GLaDOS
ROS
- Space ROS Humble Release
- 0 New and 19 Updated Packages for ROS 1 Noetic
- 3 New and 209 Updated Packages for ROS 2 Iron
- 70 New and 721 Updated Packages for ROS 2 Rolling
- ROS MicroPy
- NE-Five Upgraded, ROSSerial and RP2040 Based Boards
- How to build full ROS2 deb packages for debian distribution which are built from source code
- Announcing New ROS 2 Driver for the AR4 robot arm
- NAV2 Support for TwistStamped Available (rolling, jazzy)
- Video: Interoperability SIG February Meeting
- ROS Coding Retreat?
- Presentation on skill based architecture and discussion of our REP draft
- First ROS Meetup in Lagos Nigeria
- ICRA2024 - A Method for Multi-Robot Asynchronous Trajectory Execution in MoveIt2
- ICRA 2024 CrazySim A Software-In-The-Loop Simulator for CrazyFly
- Footstep Planning for Humanoid Robots Using Perception-based Feasible Footsteps in Cluttered Environments
- Mermaid JS Charts and Graphs in docs.ros.org
- ROS 2 Basics Video List
- YOLOv4 on TurtleBot3
- Process of ROS2 for Computer Vision Pipelines
- ROS 2 Cookbook
- Articulated Robotics on Foxglove Controller PlugIn
- Autonomous Power Wheels
- Image Proc for ROS 2 now in docs.ros.org
- Omni Wheel Controller Example
- CPPCon: Robotics at Compile Time: Optimizing Robotics Algorithms With C++'s Compile-Time Features
ROS Questions
If you have a spare 30 minutes please consider answering a question on Robotics Stack Exchange. Newcomers to the community need your help!
3 posts - 2 participants
https://discourse.ros.org/t/ros-news-for-the-week-of-february-5th-2024/36011ROS Discourse General: New Packages for Noetic 2024-02-09
We’re happy to announce 0 new packages and 19 updates are now available in ROS Noetic. This sync was tagged as noetic/2024-02-09
.
Thank you to every maintainer and contributor who made these updates available!
Package Updates for ROS Noetic
Added Packages [0]:
Updated Packages [19]:
- ros-noetic-camera-aravis: 4.0.4-1 → 4.0.5-3
- ros-noetic-cras-laser-geometry: 1.2.0-1 → 1.2.1-1
- ros-noetic-depthai-bridge: 2.8.2-1 → 2.9.0-1
- ros-noetic-depthai-descriptions: 2.8.2-1 → 2.9.0-1
- ros-noetic-depthai-examples: 2.8.2-1 → 2.9.0-1
- ros-noetic-depthai-filters: 2.8.2-1 → 2.9.0-1
- ros-noetic-depthai-ros: 2.8.2-1 → 2.9.0-1
- ros-noetic-depthai-ros-driver: 2.8.2-1 → 2.9.0-1
- ros-noetic-depthai-ros-msgs: 2.8.2-1 → 2.9.0-1
- ros-noetic-microstrain-inertial-driver: 3.2.0-3 → 3.2.1-1
- ros-noetic-microstrain-inertial-examples: 3.2.0-3 → 3.2.1-1
- ros-noetic-microstrain-inertial-msgs: 3.2.0-3 → 3.2.1-1
- ros-noetic-microstrain-inertial-rqt: 3.2.0-3 → 3.2.1-1
- ros-noetic-mrpt2: 2.11.4-1 → 2.11.7-1
- ros-noetic-novatel-oem7-driver: 4.2.0-1 → 4.3.0-5
- ros-noetic-novatel-oem7-msgs: 4.2.0-1 → 4.3.0-5
- ros-noetic-plotjuggler: 3.8.8-3 → 3.9.0-1
- ros-noetic-plotjuggler-ros: 2.0.0-1 → 2.1.0-1
- ros-noetic-xacro: 1.14.16-1 → 1.14.17-2
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
- Boitumelo Ruf, Fraunhofer IOSB
- Davide Faconti
- Jose-Luis Blanco-Claraco
- Martin Pecka
- NovAtel Support
- Rob Fisher
- Robert Haschke
- Sachin Guruswamy
- sachin
1 post - 1 participant
https://discourse.ros.org/t/new-packages-for-noetic-2024-02-09/36007ROS Discourse General: Patch Release 4 and New Packages for Iron Irwini 2024-02-09
We’re happy to announce a new Iron release
The latest sync brings 3 new packages and 209 updates to ROS 2 Iron Irwini. This sync was tagged as iron/2024-02-09
.
Package Updates for iron
Added Packages [3]:
- ros-iron-event-camera-py: 1.2.4-1
- ros-iron-hardware-interface-testing: 3.23.0-1
- ros-iron-hardware-interface-testing-dbgsym: 3.23.0-1
Updated Packages [209]:
- ros-iron-ament-clang-format: 0.14.2-1 → 0.14.3-1
- ros-iron-ament-clang-tidy: 0.14.2-1 → 0.14.3-1
- ros-iron-ament-cmake: 2.0.3-1 → 2.0.4-1
- ros-iron-ament-cmake-auto: 2.0.3-1 → 2.0.4-1
- ros-iron-ament-cmake-clang-format: 0.14.2-1 → 0.14.3-1
- ros-iron-ament-cmake-clang-tidy: 0.14.2-1 → 0.14.3-1
- ros-iron-ament-cmake-copyright: 0.14.2-1 → 0.14.3-1
- ros-iron-ament-cmake-core: 2.0.3-1 → 2.0.4-1
- ros-iron-ament-cmake-cppcheck: 0.14.2-1 → 0.14.3-1
- ros-iron-ament-cmake-cpplint: 0.14.2-1 → 0.14.3-1
- ros-iron-ament-cmake-export-definitions: 2.0.3-1 → 2.0.4-1
- ros-iron-ament-cmake-export-dependencies: 2.0.3-1 → 2.0.4-1
- ros-iron-ament-cmake-export-include-directories: 2.0.3-1 → 2.0.4-1
- ros-iron-ament-cmake-export-interfaces: 2.0.3-1 → 2.0.4-1
- ros-iron-ament-cmake-export-libraries: 2.0.3-1 → 2.0.4-1
- ros-iron-ament-cmake-export-link-flags: 2.0.3-1 → 2.0.4-1
- ros-iron-ament-cmake-export-targets: 2.0.3-1 → 2.0.4-1
- ros-iron-ament-cmake-flake8: 0.14.2-1 → 0.14.3-1
- ros-iron-ament-cmake-gen-version-h: 2.0.3-1 → 2.0.4-1
- ros-iron-ament-cmake-gmock: 2.0.3-1 → 2.0.4-1
- ros-iron-ament-cmake-google-benchmark: 2.0.3-1 → 2.0.4-1
- ros-iron-ament-cmake-gtest: 2.0.3-1 → 2.0.4-1
- ros-iron-ament-cmake-include-directories: 2.0.3-1 → 2.0.4-1
- ros-iron-ament-cmake-libraries: 2.0.3-1 → 2.0.4-1
- ros-iron-ament-cmake-lint-cmake: 0.14.2-1 → 0.14.3-1
- ros-iron-ament-cmake-mypy: 0.14.2-1 → 0.14.3-1
- ros-iron-ament-cmake-pclint: 0.14.2-1 → 0.14.3-1
- ros-iron-ament-cmake-pep257: 0.14.2-1 → 0.14.3-1
- ros-iron-ament-cmake-pycodestyle: 0.14.2-1 → 0.14.3-1
- ros-iron-ament-cmake-pyflakes: 0.14.2-1 → 0.14.3-1
- ros-iron-ament-cmake-pytest: 2.0.3-1 → 2.0.4-1
- ros-iron-ament-cmake-python: 2.0.3-1 → 2.0.4-1
- ros-iron-ament-cmake-target-dependencies: 2.0.3-1 → 2.0.4-1
- ros-iron-ament-cmake-test: 2.0.3-1 → 2.0.4-1
- ros-iron-ament-cmake-uncrustify: 0.14.2-1 → 0.14.3-1
- ros-iron-ament-cmake-vendor-package: 2.0.3-1 → 2.0.4-1
- ros-iron-ament-cmake-version: 2.0.3-1 → 2.0.4-1
- ros-iron-ament-cmake-xmllint: 0.14.2-1 → 0.14.3-1
- ros-iron-ament-copyright: 0.14.2-1 → 0.14.3-1
- ros-iron-ament-cppcheck: 0.14.2-1 → 0.14.3-1
- ros-iron-ament-cpplint: 0.14.2-1 → 0.14.3-1
- ros-iron-ament-flake8: 0.14.2-1 → 0.14.3-1
- ros-iron-ament-lint: 0.14.2-1 → 0.14.3-1
- ros-iron-ament-lint-auto: 0.14.2-1 → 0.14.3-1
- ros-iron-ament-lint-cmake: 0.14.2-1 → 0.14.3-1
- ros-iron-ament-lint-common: 0.14.2-1 → 0.14.3-1
- ros-iron-ament-mypy: 0.14.2-1 → 0.14.3-1
- ros-iron-ament-pclint: 0.14.2-1 → 0.14.3-1
- ros-iron-ament-pep257: 0.14.2-1 → 0.14.3-1
- ros-iron-ament-pycodestyle: 0.14.2-1 → 0.14.3-1
- ros-iron-ament-pyflakes: 0.14.2-1 → 0.14.3-1
- ros-iron-ament-uncrustify: 0.14.2-1 → 0.14.3-1
- ros-iron-ament-xmllint: 0.14.2-1 → 0.14.3-1
- ros-iron-camera-calibration-parsers: 4.2.2-1 → 4.2.3-1
- ros-iron-camera-calibration-parsers-dbgsym: 4.2.2-1 → 4.2.3-1
- ros-iron-camera-info-manager: 4.2.2-1 → 4.2.3-1
- ros-iron-camera-info-manager-dbgsym: 4.2.2-1 → 4.2.3-1
- ros-iron-controller-interface: 3.22.0-1 → 3.23.0-1
- ros-iron-controller-interface-dbgsym: 3.22.0-1 → 3.23.0-1
- ros-iron-controller-manager: 3.22.0-1 → 3.23.0-1
- ros-iron-controller-manager-dbgsym: 3.22.0-1 → 3.23.0-1
- ros-iron-controller-manager-msgs: 3.22.0-1 → 3.23.0-1
- ros-iron-controller-manager-msgs-dbgsym: 3.22.0-1 → 3.23.0-1
- ros-iron-cyclonedds: 0.10.3-2 → 0.10.4-1
- ros-iron-cyclonedds-dbgsym: 0.10.3-2 → 0.10.4-1
- ros-iron-depthai-bridge: 2.8.2-1 → 2.9.0-1
- ros-iron-depthai-bridge-dbgsym: 2.8.2-1 → 2.9.0-1
- ros-iron-depthai-descriptions: 2.8.2-1 → 2.9.0-1
- ros-iron-depthai-examples: 2.8.2-1 → 2.9.0-1
- ros-iron-depthai-examples-dbgsym: 2.8.2-1 → 2.9.0-1
- ros-iron-depthai-filters: 2.8.2-1 → 2.9.0-1
- ros-iron-depthai-filters-dbgsym: 2.8.2-1 → 2.9.0-1
- ros-iron-depthai-ros: 2.8.2-1 → 2.9.0-1
- ros-iron-depthai-ros-driver: 2.8.2-1 → 2.9.0-1
- ros-iron-depthai-ros-driver-dbgsym: 2.8.2-1 → 2.9.0-1
- ros-iron-depthai-ros-msgs: 2.8.2-1 → 2.9.0-1
- ros-iron-depthai-ros-msgs-dbgsym: 2.8.2-1 → 2.9.0-1
- ros-iron-event-camera-codecs: 1.2.3-1 → 1.2.4-1
- ros-iron-event-camera-codecs-dbgsym: 1.2.3-1 → 1.2.4-1
- ros-iron-event-camera-renderer: 1.2.2-1 → 1.2.3-1
- ros-iron-event-camera-renderer-dbgsym: 1.2.2-1 → 1.2.3-1
- ros-iron-fastrtps: 2.10.2-1 → 2.10.3-1
- ros-iron-fastrtps-dbgsym: 2.10.2-1 → 2.10.3-1
- ros-iron-hardware-interface: 3.22.0-1 → 3.23.0-1
- ros-iron-hardware-interface-dbgsym: 3.22.0-1 → 3.23.0-1
- ros-iron-image-common: 4.2.2-1 → 4.2.3-1
- ros-iron-image-transport: 4.2.2-1 → 4.2.3-1
- ros-iron-image-transport-dbgsym: 4.2.2-1 → 4.2.3-1
- ros-iron-joint-limits: 3.22.0-1 → 3.23.0-1
- ros-iron-launch-ros: 0.24.0-2 → 0.24.1-1
- ros-iron-launch-testing-ros: 0.24.0-2 → 0.24.1-1
- ros-iron-mcap-vendor: 0.22.5-1 → 0.22.6-1
- ros-iron-mcap-vendor-dbgsym: 0.22.5-1 → 0.22.6-1
- ros-iron-microstrain-inertial-driver: 3.2.0-1 → 3.2.1-1
- ros-iron-microstrain-inertial-driver-dbgsym: 3.2.0-1 → 3.2.1-1
- ros-iron-microstrain-inertial-examples: 3.2.0-1 → 3.2.1-1
- ros-iron-microstrain-inertial-examples-dbgsym: 3.2.0-1 → 3.2.1-1
- ros-iron-microstrain-inertial-msgs: 3.2.0-1 → 3.2.1-1
- ros-iron-microstrain-inertial-msgs-dbgsym: 3.2.0-1 → 3.2.1-1
- ros-iron-microstrain-inertial-rqt: 3.2.0-1 → 3.2.1-1
- ros-iron-mp2p-icp: 1.0.0-1 → 1.1.0-1
- ros-iron-mp2p-icp-dbgsym: 1.0.0-1 → 1.1.0-1
- ros-iron-mrpt2: 2.11.6-1 → 2.11.7-1
- ros-iron-mrpt2-dbgsym: 2.11.6-1 → 2.11.7-1
- ros-iron-plotjuggler: 3.8.9-1 → 3.9.0-1
- ros-iron-plotjuggler-dbgsym: 3.8.9-1 → 3.9.0-1
- ros-iron-plotjuggler-ros: 2.0.0-1 → 2.1.0-1
- ros-iron-plotjuggler-ros-dbgsym: 2.0.0-1 → 2.1.0-1
- ros-iron-python-qt-binding: 1.2.3-2 → 1.2.4-1
- ros-iron-qt-dotgraph: 2.4.2-2 → 2.4.3-1
- ros-iron-qt-gui: 2.4.2-2 → 2.4.3-1
- ros-iron-qt-gui-app: 2.4.2-2 → 2.4.3-1
- ros-iron-qt-gui-core: 2.4.2-2 → 2.4.3-1
- ros-iron-qt-gui-cpp: 2.4.2-2 → 2.4.3-1
- ros-iron-qt-gui-cpp-dbgsym: 2.4.2-2 → 2.4.3-1
- ros-iron-qt-gui-py-common: 2.4.2-2 → 2.4.3-1
- ros-iron-rcl: 6.0.4-1 → 6.0.5-1
- ros-iron-rcl-action: 6.0.4-1 → 6.0.5-1
- ros-iron-rcl-action-dbgsym: 6.0.4-1 → 6.0.5-1
- ros-iron-rcl-dbgsym: 6.0.4-1 → 6.0.5-1
- ros-iron-rcl-lifecycle: 6.0.4-1 → 6.0.5-1
- ros-iron-rcl-lifecycle-dbgsym: 6.0.4-1 → 6.0.5-1
- ros-iron-rcl-yaml-param-parser: 6.0.4-1 → 6.0.5-1
- ros-iron-rcl-yaml-param-parser-dbgsym: 6.0.4-1 → 6.0.5-1
- ros-iron-rclcpp: 21.0.4-1 → 21.0.5-1
- ros-iron-rclcpp-action: 21.0.4-1 → 21.0.5-1
- ros-iron-rclcpp-action-dbgsym: 21.0.4-1 → 21.0.5-1
- ros-iron-rclcpp-components: 21.0.4-1 → 21.0.5-1
- ros-iron-rclcpp-components-dbgsym: 21.0.4-1 → 21.0.5-1
- ros-iron-rclcpp-dbgsym: 21.0.4-1 → 21.0.5-1
- ros-iron-rclcpp-lifecycle: 21.0.4-1 → 21.0.5-1
- ros-iron-rclcpp-lifecycle-dbgsym: 21.0.4-1 → 21.0.5-1
- ros-iron-rmw-fastrtps-cpp: 7.1.2-1 → 7.1.3-1
- ros-iron-rmw-fastrtps-cpp-dbgsym: 7.1.2-1 → 7.1.3-1
- ros-iron-rmw-fastrtps-dynamic-cpp: 7.1.2-1 → 7.1.3-1
- ros-iron-rmw-fastrtps-dynamic-cpp-dbgsym: 7.1.2-1 → 7.1.3-1
- ros-iron-rmw-fastrtps-shared-cpp: 7.1.2-1 → 7.1.3-1
- ros-iron-rmw-fastrtps-shared-cpp-dbgsym: 7.1.2-1 → 7.1.3-1
- ros-iron-robot-state-publisher: 3.2.0-2 → 3.2.1-1
- ros-iron-robot-state-publisher-dbgsym: 3.2.0-2 → 3.2.1-1
- ros-iron-ros2-control: 3.22.0-1 → 3.23.0-1
- ros-iron-ros2-control-test-assets: 3.22.0-1 → 3.23.0-1
- ros-iron-ros2action: 0.25.4-1 → 0.25.5-1
- ros-iron-ros2bag: 0.22.5-1 → 0.22.6-1
- ros-iron-ros2cli: 0.25.4-1 → 0.25.5-1
- ros-iron-ros2cli-test-interfaces: 0.25.4-1 → 0.25.5-1
- ros-iron-ros2cli-test-interfaces-dbgsym: 0.25.4-1 → 0.25.5-1
- ros-iron-ros2component: 0.25.4-1 → 0.25.5-1
- ros-iron-ros2controlcli: 3.22.0-1 → 3.23.0-1
- ros-iron-ros2doctor: 0.25.4-1 → 0.25.5-1
- ros-iron-ros2interface: 0.25.4-1 → 0.25.5-1
- ros-iron-ros2launch: 0.24.0-2 → 0.24.1-1
- ros-iron-ros2lifecycle: 0.25.4-1 → 0.25.5-1
- ros-iron-ros2lifecycle-test-fixtures: 0.25.4-1 → 0.25.5-1
- ros-iron-ros2lifecycle-test-fixtures-dbgsym: 0.25.4-1 → 0.25.5-1
- ros-iron-ros2multicast: 0.25.4-1 → 0.25.5-1
- ros-iron-ros2node: 0.25.4-1 → 0.25.5-1
- ros-iron-ros2param: 0.25.4-1 → 0.25.5-1
- ros-iron-ros2pkg: 0.25.4-1 → 0.25.5-1
- ros-iron-ros2run: 0.25.4-1 → 0.25.5-1
- ros-iron-ros2service: 0.25.4-1 → 0.25.5-1
- ros-iron-ros2topic: 0.25.4-1 → 0.25.5-1
- ros-iron-rosbag2: 0.22.5-1 → 0.22.6-1
- ros-iron-rosbag2-compression: 0.22.5-1 → 0.22.6-1
- ros-iron-rosbag2-compression-dbgsym: 0.22.5-1 → 0.22.6-1
- ros-iron-rosbag2-compression-zstd: 0.22.5-1 → 0.22.6-1
- ros-iron-rosbag2-compression-zstd-dbgsym: 0.22.5-1 → 0.22.6-1
- ros-iron-rosbag2-cpp: 0.22.5-1 → 0.22.6-1
- ros-iron-rosbag2-cpp-dbgsym: 0.22.5-1 → 0.22.6-1
- ros-iron-rosbag2-examples-cpp: 0.22.5-1 → 0.22.6-1
- ros-iron-rosbag2-examples-cpp-dbgsym: 0.22.5-1 → 0.22.6-1
- ros-iron-rosbag2-examples-py: 0.22.5-1 → 0.22.6-1
- ros-iron-rosbag2-interfaces: 0.22.5-1 → 0.22.6-1
- ros-iron-rosbag2-interfaces-dbgsym: 0.22.5-1 → 0.22.6-1
- ros-iron-rosbag2-performance-benchmarking: 0.22.5-1 → 0.22.6-1
- ros-iron-rosbag2-performance-benchmarking-msgs: 0.22.5-1 → 0.22.6-1
- ros-iron-rosbag2-py: 0.22.5-1 → 0.22.6-1
- ros-iron-rosbag2-storage: 0.22.5-1 → 0.22.6-1
- ros-iron-rosbag2-storage-dbgsym: 0.22.5-1 → 0.22.6-1
- ros-iron-rosbag2-storage-default-plugins: 0.22.5-1 → 0.22.6-1
- ros-iron-rosbag2-storage-mcap: 0.22.5-1 → 0.22.6-1
- ros-iron-rosbag2-storage-mcap-dbgsym: 0.22.5-1 → 0.22.6-1
- ros-iron-rosbag2-storage-sqlite3: 0.22.5-1 → 0.22.6-1
- ros-iron-rosbag2-storage-sqlite3-dbgsym: 0.22.5-1 → 0.22.6-1
- ros-iron-rosbag2-test-common: 0.22.5-1 → 0.22.6-1
- ros-iron-rosbag2-test-msgdefs: 0.22.5-1 → 0.22.6-1
- ros-iron-rosbag2-test-msgdefs-dbgsym: 0.22.5-1 → 0.22.6-1
- ros-iron-rosbag2-tests: 0.22.5-1 → 0.22.6-1
- ros-iron-rosbag2-transport: 0.22.5-1 → 0.22.6-1
- ros-iron-rosbag2-transport-dbgsym: 0.22.5-1 → 0.22.6-1
- ros-iron-rqt-controller-manager: 3.22.0-1 → 3.23.0-1
- ros-iron-rviz-assimp-vendor: 12.4.5-2 → 12.4.6-1
- ros-iron-rviz-common: 12.4.5-2 → 12.4.6-1
- ros-iron-rviz-common-dbgsym: 12.4.5-2 → 12.4.6-1
- ros-iron-rviz-default-plugins: 12.4.5-2 → 12.4.6-1
- ros-iron-rviz-default-plugins-dbgsym: 12.4.5-2 → 12.4.6-1
- ros-iron-rviz-ogre-vendor: 12.4.5-2 → 12.4.6-1
- ros-iron-rviz-ogre-vendor-dbgsym: 12.4.5-2 → 12.4.6-1
- ros-iron-rviz-rendering: 12.4.5-2 → 12.4.6-1
- ros-iron-rviz-rendering-dbgsym: 12.4.5-2 → 12.4.6-1
- ros-iron-rviz-rendering-tests: 12.4.5-2 → 12.4.6-1
- ros-iron-rviz-visual-testing-framework: 12.4.5-2 → 12.4.6-1
- ros-iron-rviz2: 12.4.5-2 → 12.4.6-1
- ros-iron-rviz2-dbgsym: 12.4.5-2 → 12.4.6-1
- ros-iron-shared-queues-vendor: 0.22.5-1 → 0.22.6-1
- ros-iron-sqlite3-vendor: 0.22.5-1 → 0.22.6-1
- ros-iron-transmission-interface: 3.22.0-1 → 3.23.0-1
- ros-iron-transmission-interface-dbgsym: 3.22.0-1 → 3.23.0-1
- ros-iron-zstd-vendor: 0.22.5-1 → 0.22.6-1
Removed Packages [5]:
- ros-iron-generate-parameter-library-example
- ros-iron-generate-parameter-library-example-dbgsym
- ros-iron-generate-parameter-module-example
- ros-iron-mola-demos
- ros-iron-rrt-planner
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
- Aditya Pande
- Alejandro Hernandez Cordero
- Audrow Nash
- Bence Magyar
- Bernd Pfrommer
- Chris Lalancette
- Davide Faconti
- Dirk Thomas
- Dorian Scholz
- Eclipse Foundation, Inc.
- Foxglove
- Geoffrey Biggs
- Ivan Paunovic
- Jose-Luis Blanco-Claraco
- Michael Jeronimo
- Michael Orlov
- Miguel Company
- ROS Tooling Working Group
- Rob Fisher
- Sachin Guruswamy
- Shane Loretz
- geoff
- sachin
1 post - 1 participant
https://discourse.ros.org/t/patch-release-4-and-new-packages-for-iron-irwini-2024-02-09/36006ROS Discourse General: Installing ROS2 humble on RISC-V Ubuntu
Hi all!
I’m new to ROS 2, and I’m trying to install it on a RISC-V Ubuntu 22.04.3 using QEMU. I’m following these isntructions:
https://docs.ros.org/en/humble/Installation/Alternatives/Ubuntu-Development-Setup.html
The main issue is that ROS repository does not support riscv targets, and I wonder how difficult it is to add support to this architecture or how to build it from source without using ROS repo. Can anyone send me a few pointers to achieve this?
7 posts - 4 participants
https://discourse.ros.org/t/installing-ros2-humble-on-risc-v-ubuntu/35988