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 June 17th, 2024
ROS News for the week of June 17th, 2024
ROSCon France was this week in Nantes, here’s a group shot of the sold out conference!
CVPR was this week. I’ve dropped a list of robotics related CVPR papers below. Pictured above is “GARField Group Anything with Radiance Fields” from UC Berkeley and Luma.ai.
Our friends at PickNik have been awarded three NASA SBIR grants for SpaceROS!
After a successful Open Sauce pre-party last Friday I ended up getting a loaner badge for Open Sauce. Here’s a photo dump of robots from the event. Pictured is Kev from Kev’s robots. I am going to try and put together an OSRF booth next year!
Events
- 2024-06-25 Hamlyn Symposium on Open-Source Software for Surgical Technology
- 2024-06-26 Master Multi-Robot Fleet Management: Open-RMF
- 2024-06-26 Gazebo Community Meeting
- 2024-06-19 => 2024-06-20 ROSCon France
- 2024-07-02 Medical Community Group Meeting
- 2024-07-29 => 2024-08-02 IEEE RAS Multi-Robot Summer School Prague
- 2024-08-05 Autonomous Systems Bootcam at Univ. Deleware– Video
- 2024-08-16 => 2024-08-17 Ubucon Latin America
- 2024-09-07 Silicon Valley Robotics Robot Block Partyq`
- 2024-09-18 Foxglove Actuate San Francisco
- 2024-09-19 ==> 2024-09-20 ROSCon Spain
- 2024-09-25 ROSConJP
- 2024-10-22 → 2024-10-24 AgRobot FIRA in Sacramento
- 2024-10-23 → 2024-10-25 16th International Conference on Social Robotics +AI
- 2024-11-02 → 2024-11-03 ROSCon China in Shenzhen
- 2024-12-03 ROSCon Germany
News
- NASA Funding for SpaceROS at PickNik
- Labor shortages are still fueling growth at automation firms like GrayMatter – Robot Report
- DiffLoc: Diffusion Model for Outdoor LiDAR Localization
- LEAP-VO: Long-term Effective Any Point Tracking for Visual Odometry
- CFP: IEEE Transactions on Field Robotics Special Issue on Space Robotics
- SPIN: Simultaneous Perception, Interaction and Navigation
- GARField Group Anything with Radiance Fields
- Waabi’s GenAI promises to do so much more than power self-driving trucks
- GM invests another $850M into Cruise as it expands manual operations
- Vecna Robotics raises more than $100M
- coboworx raises $12M to make robotics more accessible
- Korechi Innovations Pik’r-1500 robot retrieves golf balls at the U.S. Open
- Honoring the Legacy of Chip Design Innovator Lynn Conway
- Here’s the Most Buglike Robot Bug Yet
- Kuka Medical Innovation Award
ROS
- 62 New and 63 Updated Packages for Humble
- 4 New and 20 Updated Packages for Noetic
- 68 New and 196 Updated Packages for Jazzy
- ROS2: How to achieve visual recognition with AgileX Limo ROS 2?
- ROS2_documentation provides HTML artifacts via Github action
- F1Tenth Lecture Playlist
- ROSCon Spain Workshops
- Sam Rossiter’s Rosmo Aims to Deliver an Easy-to-Build Robot Platform for ROS 2 and MicroBlocks
- PyRoboPlan 1.1
- Design and Evaluation of Motion Planners for Quadrotors
- Bidirectional ROS to gstreamer bridge and utilities for dynamic pipelines
Got a minute? ![:timer_clock: :timer_clock:](https://emoji.discourse-cdn.com/twitter/timer_clock.png?v=12)
Why not help us answer a few questions on ROS Discord? You can find a link to ROS Discord and all of our other websites here.
1 post - 1 participant
![[WWW] [WWW]](./rostheme/img/moin-www.png)
ROS Discourse General: New Packages for Noetic 2024-06-20
We’re happy to announce 4 new packages and 20 updates are now available in ROS Noetic. This sync was tagged as noetic/2024-06-20
.
Thank you to every maintainer and contributor who made these updates available!
Package Updates for ROS Noetic
Added Packages [4]:
- ros-noetic-depthai-bridge: 2.9.0-1
- ros-noetic-depthai-examples: 2.9.0-1
- ros-noetic-depthai-ros: 2.9.0-1
- ros-noetic-depthai-ros-driver: 2.9.0-1
Updated Packages [20]:
- ros-noetic-aruco-opencv: 0.4.0-1 → 0.4.1-1
- ros-noetic-aruco-opencv-msgs: 0.4.0-1 → 0.4.1-1
- ros-noetic-bosch-locator-bridge: 1.0.10-1 → 1.0.11-2
- ros-noetic-cartesian-interface: 0.1.5-1 → 0.1.6-1
- ros-noetic-cartesian-trajectory-controller: 0.1.5-1 → 0.1.6-1
- ros-noetic-cartesian-trajectory-interpolation: 0.1.5-1 → 0.1.6-1
- ros-noetic-depthai: 2.26.0-1 → 2.26.1-1
- ros-noetic-eigenpy: 3.1.4-5 → 3.7.0-1
- ros-noetic-hpp-fcl: 2.4.0-1 → 2.4.4-1
- ros-noetic-libmavconn: 1.18.0-1 → 1.19.0-1
- ros-noetic-mavlink: 2024.3.3-1 → 2024.6.6-1
- ros-noetic-mavros: 1.18.0-1 → 1.19.0-1
- ros-noetic-mavros-extras: 1.18.0-1 → 1.19.0-1
- ros-noetic-mavros-msgs: 1.18.0-1 → 1.19.0-1
- ros-noetic-ros-controllers-cartesian: 0.1.5-1 → 0.1.6-1
- ros-noetic-test-mavros: 1.18.0-1 → 1.19.0-1
- ros-noetic-twist-controller: 0.1.5-1 → 0.1.6-1
- ros-noetic-ur-calibration: 2.1.4-1 → 2.1.5-1
- ros-noetic-ur-dashboard-msgs: 2.1.4-1 → 2.1.5-1
- ros-noetic-ur-robot-driver: 2.1.4-1 → 2.1.5-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:
- Adam Serafin
- Felix Exner
- Fictionlab
- Joseph Mirabel
- Justin Carpentier
- Sachin Guruswamy
- Stefan Laible
- Stefan Scherzinger
- Vladimir Ermakov
- sachin
1 post - 1 participant
![[WWW] [WWW]](./rostheme/img/moin-www.png)
ROS Discourse General: New packages for Humble Hawksbill 2024-06-20
Package Updates for Humble
Added Packages [62]:
- ros-humble-ecl-command-line: 1.2.1-1
- ros-humble-ecl-command-line-dbgsym: 1.2.1-1
- ros-humble-ecl-concepts: 1.2.1-1
- ros-humble-ecl-config: 1.2.0-1
- ros-humble-ecl-config-dbgsym: 1.2.0-1
- ros-humble-ecl-console: 1.2.0-1
- ros-humble-ecl-containers: 1.2.1-1
- ros-humble-ecl-containers-dbgsym: 1.2.1-1
- ros-humble-ecl-converters: 1.2.1-1
- ros-humble-ecl-converters-dbgsym: 1.2.1-1
- ros-humble-ecl-converters-lite: 1.2.0-1
- ros-humble-ecl-core: 1.2.1-1
- ros-humble-ecl-core-apps: 1.2.1-1
- ros-humble-ecl-core-apps-dbgsym: 1.2.1-1
- ros-humble-ecl-devices: 1.2.1-1
- ros-humble-ecl-devices-dbgsym: 1.2.1-1
- ros-humble-ecl-eigen: 1.2.1-1
- ros-humble-ecl-errors: 1.2.0-1
- ros-humble-ecl-errors-dbgsym: 1.2.0-1
- ros-humble-ecl-exceptions: 1.2.1-1
- ros-humble-ecl-exceptions-dbgsym: 1.2.1-1
- ros-humble-ecl-filesystem: 1.2.1-1
- ros-humble-ecl-filesystem-dbgsym: 1.2.1-1
- ros-humble-ecl-formatters: 1.2.1-1
- ros-humble-ecl-formatters-dbgsym: 1.2.1-1
- ros-humble-ecl-geometry: 1.2.1-1
- ros-humble-ecl-geometry-dbgsym: 1.2.1-1
- ros-humble-ecl-io: 1.2.0-1
- ros-humble-ecl-io-dbgsym: 1.2.0-1
- ros-humble-ecl-ipc: 1.2.1-1
- ros-humble-ecl-ipc-dbgsym: 1.2.1-1
- ros-humble-ecl-linear-algebra: 1.2.1-1
- ros-humble-ecl-linear-algebra-dbgsym: 1.2.1-1
- ros-humble-ecl-lite: 1.2.0-1
- ros-humble-ecl-manipulators: 1.2.1-1
- ros-humble-ecl-manipulators-dbgsym: 1.2.1-1
- ros-humble-ecl-math: 1.2.1-1
- ros-humble-ecl-mobile-robot: 1.2.1-1
- ros-humble-ecl-mobile-robot-dbgsym: 1.2.1-1
- ros-humble-ecl-mpl: 1.2.1-1
- ros-humble-ecl-sigslots: 1.2.1-1
- ros-humble-ecl-sigslots-dbgsym: 1.2.1-1
- ros-humble-ecl-sigslots-lite: 1.2.0-1
- ros-humble-ecl-sigslots-lite-dbgsym: 1.2.0-1
- ros-humble-ecl-statistics: 1.2.1-1
- ros-humble-ecl-statistics-dbgsym: 1.2.1-1
- ros-humble-ecl-streams: 1.2.1-1
- ros-humble-ecl-streams-dbgsym: 1.2.1-1
- ros-humble-ecl-threads: 1.2.1-1
- ros-humble-ecl-threads-dbgsym: 1.2.1-1
- ros-humble-ecl-time: 1.2.1-1
- ros-humble-ecl-time-dbgsym: 1.2.1-1
- ros-humble-ecl-time-lite: 1.2.0-1
- ros-humble-ecl-time-lite-dbgsym: 1.2.0-1
- ros-humble-ecl-type-traits: 1.2.1-1
- ros-humble-ecl-type-traits-dbgsym: 1.2.1-1
- ros-humble-ecl-utilities: 1.2.1-1
- ros-humble-ecl-utilities-dbgsym: 1.2.1-1
- ros-humble-kobuki-core: 1.4.1-1
- ros-humble-kobuki-core-dbgsym: 1.4.1-1
- ros-humble-ortools-vendor: 9.9.0-7
- ros-humble-ortools-vendor-dbgsym: 9.9.0-7
Updated Packages [63]:
- ros-humble-apriltag-ros: 3.2.1-1 → 3.2.2-3
- ros-humble-apriltag-ros-dbgsym: 3.2.1-1 → 3.2.2-3
- ros-humble-control-msgs: 4.5.0-1 → 4.6.0-1
- ros-humble-control-msgs-dbgsym: 4.5.0-1 → 4.6.0-1
- ros-humble-depthai: 2.24.0-1 → 2.26.1-1
- ros-humble-depthai-dbgsym: 2.24.0-1 → 2.26.1-1
- ros-humble-eigenpy: 3.1.4-1 → 3.7.0-1
- ros-humble-eigenpy-dbgsym: 3.1.4-1 → 3.7.0-1
- ros-humble-hpp-fcl: 2.4.0-1 → 2.4.4-1
- ros-humble-hpp-fcl-dbgsym: 2.4.0-1 → 2.4.4-1
- ros-humble-libmavconn: 2.7.0-1 → 2.8.0-1
- ros-humble-libmavconn-dbgsym: 2.7.0-1 → 2.8.0-1
- ros-humble-mavlink: 2024.3.3-1 → 2024.6.6-1
- ros-humble-mavros: 2.7.0-1 → 2.8.0-1
- ros-humble-mavros-dbgsym: 2.7.0-1 → 2.8.0-1
- ros-humble-mavros-extras: 2.7.0-1 → 2.8.0-1
- ros-humble-mavros-extras-dbgsym: 2.7.0-1 → 2.8.0-1
- ros-humble-mavros-msgs: 2.7.0-1 → 2.8.0-1
- ros-humble-mavros-msgs-dbgsym: 2.7.0-1 → 2.8.0-1
- ros-humble-mp2p-icp: 1.4.2-1 → 1.4.3-1
- ros-humble-mp2p-icp-dbgsym: 1.4.2-1 → 1.4.3-1
- ros-humble-off-highway-can: 0.6.1-1 → 0.6.2-1
- ros-humble-off-highway-can-dbgsym: 0.6.1-1 → 0.6.2-1
- ros-humble-off-highway-general-purpose-radar: 0.6.1-1 → 0.6.2-1
- ros-humble-off-highway-general-purpose-radar-dbgsym: 0.6.1-1 → 0.6.2-1
- ros-humble-off-highway-general-purpose-radar-msgs: 0.6.1-1 → 0.6.2-1
- ros-humble-off-highway-general-purpose-radar-msgs-dbgsym: 0.6.1-1 → 0.6.2-1
- ros-humble-off-highway-premium-radar-sample: 0.6.1-1 → 0.6.2-1
- ros-humble-off-highway-premium-radar-sample-dbgsym: 0.6.1-1 → 0.6.2-1
- ros-humble-off-highway-premium-radar-sample-msgs: 0.6.1-1 → 0.6.2-1
- ros-humble-off-highway-premium-radar-sample-msgs-dbgsym: 0.6.1-1 → 0.6.2-1
- ros-humble-off-highway-radar: 0.6.1-1 → 0.6.2-1
- ros-humble-off-highway-radar-dbgsym: 0.6.1-1 → 0.6.2-1
- ros-humble-off-highway-radar-msgs: 0.6.1-1 → 0.6.2-1
- ros-humble-off-highway-radar-msgs-dbgsym: 0.6.1-1 → 0.6.2-1
- ros-humble-off-highway-sensor-drivers: 0.6.1-1 → 0.6.2-1
- ros-humble-off-highway-sensor-drivers-examples: 0.6.1-1 → 0.6.2-1
- ros-humble-off-highway-sensor-drivers-examples-dbgsym: 0.6.1-1 → 0.6.2-1
- ros-humble-off-highway-uss: 0.6.1-1 → 0.6.2-1
- ros-humble-off-highway-uss-dbgsym: 0.6.1-1 → 0.6.2-1
- ros-humble-off-highway-uss-msgs: 0.6.1-1 → 0.6.2-1
- ros-humble-off-highway-uss-msgs-dbgsym: 0.6.1-1 → 0.6.2-1
- ros-humble-openeb-vendor: 1.1.1-1 → 1.1.2-1
- ros-humble-openeb-vendor-dbgsym: 1.1.1-1 → 1.1.2-1
- ros-humble-proxsuite: 0.3.6-2 → 0.6.5-1
- ros-humble-rc-genicam-driver: 0.3.0-1 → 0.3.1-1
- ros-humble-rc-genicam-driver-dbgsym: 0.3.0-1 → 0.3.1-1
- ros-humble-rqt-tf-tree: 1.0.4-1 → 1.0.5-1
- ros-humble-simple-launch: 1.9.2-1 → 1.10.0-1
- ros-humble-sophus: 1.3.2-1 → 1.22.9102-2
- ros-humble-teleop-twist-joy: 2.4.5-1 → 2.4.6-1
- ros-humble-teleop-twist-joy-dbgsym: 2.4.5-1 → 2.4.6-1
- ros-humble-ur: 2.2.12-1 → 2.2.13-1
- ros-humble-ur-bringup: 2.2.12-1 → 2.2.13-1
- ros-humble-ur-calibration: 2.2.12-1 → 2.2.13-1
- ros-humble-ur-calibration-dbgsym: 2.2.12-1 → 2.2.13-1
- ros-humble-ur-controllers: 2.2.12-1 → 2.2.13-1
- ros-humble-ur-controllers-dbgsym: 2.2.12-1 → 2.2.13-1
- ros-humble-ur-dashboard-msgs: 2.2.12-1 → 2.2.13-1
- ros-humble-ur-dashboard-msgs-dbgsym: 2.2.12-1 → 2.2.13-1
- ros-humble-ur-moveit-config: 2.2.12-1 → 2.2.13-1
- ros-humble-ur-robot-driver: 2.2.12-1 → 2.2.13-1
- ros-humble-ur-robot-driver-dbgsym: 2.2.12-1 → 2.2.13-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:
- Adam Serafin
- Bence Magyar
- Bernd Pfrommer
- Chris Lalancette
- Christian Rauch
- Daniel Stonier
- Denis Stogl
- Felix Exner
- Felix Ruess
- Gonzalo Mier
- Isaac I.Y. Saito
- Jose-Luis Blanco-Claraco
- Joseph Mirabel
- Justin Carpentier
- Olivier Kermorgant
- Robin Petereit
- Sarah Huber
- Vladimir Ermakov
Difference between ‘file:///var/repos/ubuntu/main/dists/jammy/main/binary-arm64/Packages’ and ‘file:///var/repos/ubuntu/testing/dists/jammy/main/binary-arm64/Packages’ computed at 2024-06-20-21:16:48
Package Updates for humble
Added Packages [62]:
- ros-humble-ecl-command-line: 1.2.1-1
- ros-humble-ecl-command-line-dbgsym: 1.2.1-1
- ros-humble-ecl-concepts: 1.2.1-1
- ros-humble-ecl-config: 1.2.0-1
- ros-humble-ecl-config-dbgsym: 1.2.0-1
- ros-humble-ecl-console: 1.2.0-1
- ros-humble-ecl-containers: 1.2.1-1
- ros-humble-ecl-containers-dbgsym: 1.2.1-1
- ros-humble-ecl-converters: 1.2.1-1
- ros-humble-ecl-converters-dbgsym: 1.2.1-1
- ros-humble-ecl-converters-lite: 1.2.0-1
- ros-humble-ecl-core: 1.2.1-1
- ros-humble-ecl-core-apps: 1.2.1-1
- ros-humble-ecl-core-apps-dbgsym: 1.2.1-1
- ros-humble-ecl-devices: 1.2.1-1
- ros-humble-ecl-devices-dbgsym: 1.2.1-1
- ros-humble-ecl-eigen: 1.2.1-1
- ros-humble-ecl-errors: 1.2.0-1
- ros-humble-ecl-errors-dbgsym: 1.2.0-1
- ros-humble-ecl-exceptions: 1.2.1-1
- ros-humble-ecl-exceptions-dbgsym: 1.2.1-1
- ros-humble-ecl-filesystem: 1.2.1-1
- ros-humble-ecl-filesystem-dbgsym: 1.2.1-1
- ros-humble-ecl-formatters: 1.2.1-1
- ros-humble-ecl-formatters-dbgsym: 1.2.1-1
- ros-humble-ecl-geometry: 1.2.1-1
- ros-humble-ecl-geometry-dbgsym: 1.2.1-1
- ros-humble-ecl-io: 1.2.0-1
- ros-humble-ecl-io-dbgsym: 1.2.0-1
- ros-humble-ecl-ipc: 1.2.1-1
- ros-humble-ecl-ipc-dbgsym: 1.2.1-1
- ros-humble-ecl-linear-algebra: 1.2.1-1
- ros-humble-ecl-linear-algebra-dbgsym: 1.2.1-1
- ros-humble-ecl-lite: 1.2.0-1
- ros-humble-ecl-manipulators: 1.2.1-1
- ros-humble-ecl-manipulators-dbgsym: 1.2.1-1
- ros-humble-ecl-math: 1.2.1-1
- ros-humble-ecl-mobile-robot: 1.2.1-1
- ros-humble-ecl-mobile-robot-dbgsym: 1.2.1-1
- ros-humble-ecl-mpl: 1.2.1-1
- ros-humble-ecl-sigslots: 1.2.1-1
- ros-humble-ecl-sigslots-dbgsym: 1.2.1-1
- ros-humble-ecl-sigslots-lite: 1.2.0-1
- ros-humble-ecl-sigslots-lite-dbgsym: 1.2.0-1
- ros-humble-ecl-statistics: 1.2.1-1
- ros-humble-ecl-statistics-dbgsym: 1.2.1-1
- ros-humble-ecl-streams: 1.2.1-1
- ros-humble-ecl-streams-dbgsym: 1.2.1-1
- ros-humble-ecl-threads: 1.2.1-1
- ros-humble-ecl-threads-dbgsym: 1.2.1-1
- ros-humble-ecl-time: 1.2.1-1
- ros-humble-ecl-time-dbgsym: 1.2.1-1
- ros-humble-ecl-time-lite: 1.2.0-1
- ros-humble-ecl-time-lite-dbgsym: 1.2.0-1
- ros-humble-ecl-type-traits: 1.2.1-1
- ros-humble-ecl-type-traits-dbgsym: 1.2.1-1
- ros-humble-ecl-utilities: 1.2.1-1
- ros-humble-ecl-utilities-dbgsym: 1.2.1-1
- ros-humble-kobuki-core: 1.4.1-1
- ros-humble-kobuki-core-dbgsym: 1.4.1-1
- ros-humble-ortools-vendor: 9.9.0-7
- ros-humble-ortools-vendor-dbgsym: 9.9.0-7
Updated Packages [63]:
- ros-humble-apriltag-ros: 3.2.1-1 → 3.2.2-3
- ros-humble-apriltag-ros-dbgsym: 3.2.1-1 → 3.2.2-3
- ros-humble-control-msgs: 4.5.0-1 → 4.6.0-1
- ros-humble-control-msgs-dbgsym: 4.5.0-1 → 4.6.0-1
- ros-humble-depthai: 2.24.0-1 → 2.26.1-1
- ros-humble-depthai-dbgsym: 2.24.0-1 → 2.26.1-1
- ros-humble-eigenpy: 3.1.4-1 → 3.7.0-1
- ros-humble-eigenpy-dbgsym: 3.1.4-1 → 3.7.0-1
- ros-humble-hpp-fcl: 2.4.0-1 → 2.4.4-1
- ros-humble-hpp-fcl-dbgsym: 2.4.0-1 → 2.4.4-1
- ros-humble-libmavconn: 2.7.0-1 → 2.8.0-1
- ros-humble-libmavconn-dbgsym: 2.7.0-1 → 2.8.0-1
- ros-humble-mavlink: 2024.3.3-1 → 2024.6.6-1
- ros-humble-mavros: 2.7.0-1 → 2.8.0-1
- ros-humble-mavros-dbgsym: 2.7.0-1 → 2.8.0-1
- ros-humble-mavros-extras: 2.7.0-1 → 2.8.0-1
- ros-humble-mavros-extras-dbgsym: 2.7.0-1 → 2.8.0-1
- ros-humble-mavros-msgs: 2.7.0-1 → 2.8.0-1
- ros-humble-mavros-msgs-dbgsym: 2.7.0-1 → 2.8.0-1
- ros-humble-mp2p-icp: 1.4.2-1 → 1.4.3-1
- ros-humble-mp2p-icp-dbgsym: 1.4.2-1 → 1.4.3-1
- ros-humble-off-highway-can: 0.6.1-1 → 0.6.2-1
- ros-humble-off-highway-can-dbgsym: 0.6.1-1 → 0.6.2-1
- ros-humble-off-highway-general-purpose-radar: 0.6.1-1 → 0.6.2-1
- ros-humble-off-highway-general-purpose-radar-dbgsym: 0.6.1-1 → 0.6.2-1
- ros-humble-off-highway-general-purpose-radar-msgs: 0.6.1-1 → 0.6.2-1
- ros-humble-off-highway-general-purpose-radar-msgs-dbgsym: 0.6.1-1 → 0.6.2-1
- ros-humble-off-highway-premium-radar-sample: 0.6.1-1 → 0.6.2-1
- ros-humble-off-highway-premium-radar-sample-dbgsym: 0.6.1-1 → 0.6.2-1
- ros-humble-off-highway-premium-radar-sample-msgs: 0.6.1-1 → 0.6.2-1
- ros-humble-off-highway-premium-radar-sample-msgs-dbgsym: 0.6.1-1 → 0.6.2-1
- ros-humble-off-highway-radar: 0.6.1-1 → 0.6.2-1
- ros-humble-off-highway-radar-dbgsym: 0.6.1-1 → 0.6.2-1
- ros-humble-off-highway-radar-msgs: 0.6.1-1 → 0.6.2-1
- ros-humble-off-highway-radar-msgs-dbgsym: 0.6.1-1 → 0.6.2-1
- ros-humble-off-highway-sensor-drivers: 0.6.1-1 → 0.6.2-1
- ros-humble-off-highway-sensor-drivers-examples: 0.6.1-1 → 0.6.2-1
- ros-humble-off-highway-sensor-drivers-examples-dbgsym: 0.6.1-1 → 0.6.2-1
- ros-humble-off-highway-uss: 0.6.1-1 → 0.6.2-1
- ros-humble-off-highway-uss-dbgsym: 0.6.1-1 → 0.6.2-1
- ros-humble-off-highway-uss-msgs: 0.6.1-1 → 0.6.2-1
- ros-humble-off-highway-uss-msgs-dbgsym: 0.6.1-1 → 0.6.2-1
- ros-humble-openeb-vendor: 1.1.1-1 → 1.1.2-1
- ros-humble-openeb-vendor-dbgsym: 1.1.1-1 → 1.1.2-1
- ros-humble-proxsuite: 0.3.6-2 → 0.6.5-1
- ros-humble-rc-genicam-driver: 0.3.0-1 → 0.3.1-1
- ros-humble-rc-genicam-driver-dbgsym: 0.3.0-1 → 0.3.1-1
- ros-humble-rqt-tf-tree: 1.0.4-1 → 1.0.5-1
- ros-humble-simple-launch: 1.9.2-1 → 1.10.0-1
- ros-humble-sophus: 1.3.2-1 → 1.22.9102-2
- ros-humble-teleop-twist-joy: 2.4.5-1 → 2.4.6-1
- ros-humble-teleop-twist-joy-dbgsym: 2.4.5-1 → 2.4.6-1
- ros-humble-ur: 2.2.12-1 → 2.2.13-1
- ros-humble-ur-bringup: 2.2.12-1 → 2.2.13-1
- ros-humble-ur-calibration: 2.2.12-1 → 2.2.13-1
- ros-humble-ur-calibration-dbgsym: 2.2.12-1 → 2.2.13-1
- ros-humble-ur-controllers: 2.2.12-1 → 2.2.13-1
- ros-humble-ur-controllers-dbgsym: 2.2.12-1 → 2.2.13-1
- ros-humble-ur-dashboard-msgs: 2.2.12-1 → 2.2.13-1
- ros-humble-ur-dashboard-msgs-dbgsym: 2.2.12-1 → 2.2.13-1
- ros-humble-ur-moveit-config: 2.2.12-1 → 2.2.13-1
- ros-humble-ur-robot-driver: 2.2.12-1 → 2.2.13-1
- ros-humble-ur-robot-driver-dbgsym: 2.2.12-1 → 2.2.13-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:
- Adam Serafin
- Bence Magyar
- Bernd Pfrommer
- Chris Lalancette
- Christian Rauch
- Daniel Stonier
- Denis Stogl
- Felix Exner
- Felix Ruess
- Gonzalo Mier
- Isaac I.Y. Saito
- Jose-Luis Blanco-Claraco
- Joseph Mirabel
- Justin Carpentier
- Olivier Kermorgant
- Robin Petereit
- Sarah Huber
- Vladimir Ermakov
2 posts - 2 participants
![[WWW] [WWW]](./rostheme/img/moin-www.png)
ROS Discourse General: BNO055 I2C node in C++ for ROS1/ROS2 -- how to avoid dual CMakeLists.txt?
I’ve been MIA in the robotics/ROS scene for a while, just coming back to revive some old work and port it to ROS2.
I have, in the past, created dual ROS1+ROS2 packages (that work in both colcon and catkin), e.g.
I’m however having trouble figuring out a way to do the same for a C++ node since I can’t use the same conditionals in CMakeLists.txt. Here’s my best shot at an update of my BNO055 I2C node in C++:
As you can see there are two CMakeLists.txt files, one for ROS1 and one for ROS2. Copying the correct one to “CMakeLists.txt” will enable this repo to work in ROS1 or ROS2 respectively.
Is there any way to combine these two into one CMakeLists.txt and avoid the extra step?
6 posts - 4 participants
![[WWW] [WWW]](./rostheme/img/moin-www.png)
ROS Discourse General: Next Client Library WG meeting: Friday 21st June 8 AM PT
Hi,
this post is a reminder that the next meeting of the client library working group will be this Friday: 21st June 2024 at 8 AM Pacific Time.
- Meeting link: https://meet.google.com/oij-atzj-znw
- Calendar invite: https://calendar.app.google/zArSBuxFXJnmBdsV6
- Google group if you want to be notified of future meetings: https://groups.google.com/g/ros-2-client-library-wg
During the last meetings we started discussing some very interesting topics such as the executors, memory allocators and performance, both for rclcpp and rclpy
We are coordinating the review of some important bug-fixes and new features.
Everyone is welcome to join and propose their topics.
3 posts - 2 participants
![[WWW] [WWW]](./rostheme/img/moin-www.png)
ROS Discourse General: ROS2: How to achieve visual recognition with AgileX Limo ROS2?
Limo is a smart educational robot published by AgileX Robotics. More details please visit: https://global.agilex.ai/
Vision-based Line Following
Logic
- Firstly, the camera needs to be initialized. The image information is obtained by subscribing to the messages published by the camera, and the image is converted to the OpenCV format.
- The obtained image is preprocessed, including operations such as grayscale conversion, Gaussian blur, and edge detection.
- The preprocessed image is binarized to convert it into a black and white binary image.
- Morphological operations, such as dilation, erosion, and opening, are applied to the binary image to enhance line detection.
- Hough transform is used to detect lines, which are then drawn on the image.
- By analyzing the slope and position of the detected lines, the direction in which the robot needs to turn is determined, and the robot is controlled to move towards the target direction.
Implementation
Launch the camera.
ros2 launch astra_camera dabai.launch.py
Place the robot in the simulation table and activate the vision-based line following function.
ros2 run limo_visions detect_line
The lane on the simulation table will be recognized.
Color Tracking
Visual color tracking is an object detection and tracking technique based on image processing, which allows real-time tracking and localization of objects of specific colors.
Logic
- Initialize ROS node and camera subscriber: First, you need to initialize a ROS node using the rclcpp library in ROS2, and create a subscriber to subscribe to image messages. Convert the image messages from ROS to OpenCV format using the cv_bridge library.
- Define color range and mask: In this code, we will take the blue color target as an example for tracking. First, define a range object in OpenCV to represent the color range. Then, use the inRange function in OpenCV to convert the image to a binary mask, which filters out the target region for further processing.
- Detect and draw bounding boxes: The target region in the mask may contain noise and other non-target regions. To identify the exact position of the target region, you can use the findContours function in OpenCV to find the contours and use the boundingRect function to calculate the bounding box of the target region. Then, use the rectangle function to draw the bounding box on the original image.
- Publish the target position: Lastly, you can use a publisher in ROS2 to publish the target position to other nodes for further control and navigation.
Implementation
Launch the camera.
ros2 launch astra_camera dabai.launch.py
Place the colored block within the view range of the limo and activate the color tracking function:
ros2 run limo_visions object_detect
QR Code Tracking
A QR code is a graphic composed of black and white elements, which records data and symbol information. It is arranged on a plane according to specific rules and geometric shapes in a two-dimensional direction. In its encoding, it cleverly utilizes the concepts of “0” and “1” bit streams, which form the fundamental basis of internal computer logic. Several geometric shapes corresponding to binary are used to represent textual and numerical information, enabling automatic reading through image input devices or photoelectric scanning equipment to achieve automated information processing.
QR code shares common features with barcode technology, such as each coding system having its own specific character set, each character occupying a designated width, and incorporating specific verification functions. Additionally, it has the capability to automatically identify different lines of information and process changes resulting from graphic rotation.
In ROS2, the aruco_ros function package is utilized for QR code identification. aruco_ros is a function package developed based on OpenCV, written in C++, and provides a C++ interface.
Generate QR code:
URL to generate QR code: Online ArUco markers generator; you can generate different QR codes according to your own needs
The QR code used in this example is:
Implementation
Launch the camera.
ros2 launch astra_camera dabai.launch.py
Place the QR code within the field of view of Limo, and activate the QR code recognition function.
ros2 launch aruco_ros single.launch.py
Launch the QR code recognition function.
ros2 run limo_visions move_to_ar
Traffic light recognition
Logic:
- Initialize the ROS2 node and create an image subscriber and image publisher.
- Read the image and convert it to HSV color space.
- Define the color range of red and green and apply it to the image through the inRange function to obtain a binary image.
- Perform morphological operations on binary images to remove noise and fill holes.
- Find the contours in the image through the findContours function, and find the circumscribed circle of each contour through the minEnclosingCircle function.
- For each circumscribed circle, calculate its area and center coordinates. If the area is larger than the threshold and the center of the circle is within the predefined traffic light area, it can be marked as a traffic light.
- Draw the circumscribed circle of the traffic light in the original image and publish it to the ROS2 topic.
- Repeat the above steps in a loop and wait for the next image to arrive.
Implementation:
Launch the camera.
ros2 launch astra_camera dabai.launch.py
Place the QR code within the field of view of Limo, and activate the traffic light recognition function.
ros2 run limo_visions detect_traffic
About Limo
If you are interested in Limo or have some technical questions about it, feel free to join AgileX Robotics . We can talk about it!
1 post - 1 participant
![[WWW] [WWW]](./rostheme/img/moin-www.png)
ROS Discourse General: NASA Funding PickNik for ROS Development
PickNik had been awarded three new NASA SBIR opportunities to further the development of MoveIt and ROS for space applications! This is a great win for our open source community and the long-term viability of ROS deployment in real-world operational environments!
Progress updates and more on our blog: PickNik Awarded SBIR Opportunities | PickNik
2 posts - 2 participants
![[WWW] [WWW]](./rostheme/img/moin-www.png)
ROS Discourse General: New packages for Jazzy Jalisco 2024-06-18
We’re happy to announce 68 new packages and 196 updates are now available in ROS 2 Jzzy Jalisco . This sync was tagged as jazzy/2024-06-18.
Package Updates for Jazzy
Added Packages [68]:
- ros-jazzy-autoware-internal-msgs: 1.0.1-1
- ros-jazzy-azure-iot-sdk-c: 1.13.0-2
- ros-jazzy-beluga: 2.0.1-1
- ros-jazzy-beluga-amcl: 2.0.1-1
- ros-jazzy-beluga-ros: 2.0.1-1
- ros-jazzy-depthai: 2.26.1-1
- ros-jazzy-flexbe-behavior-engine: 3.0.3-1
- ros-jazzy-flexbe-core: 3.0.3-1
- ros-jazzy-flexbe-input: 3.0.3-1
- ros-jazzy-flexbe-mirror: 3.0.3-1
- ros-jazzy-flexbe-msgs: 3.0.3-1
- ros-jazzy-flexbe-onboard: 3.0.3-1
- ros-jazzy-flexbe-states: 3.0.3-1
- ros-jazzy-flexbe-testing: 3.0.3-1
- ros-jazzy-flexbe-widget: 3.0.3-1
- ros-jazzy-libcamera: 0.3.0-3
- ros-jazzy-libmavconn: 2.8.0-1
- ros-jazzy-mavlink: 2024.6.6-1
- ros-jazzy-mavros: 2.8.0-1
- ros-jazzy-mavros-extras: 2.8.0-1
- ros-jazzy-mola: 1.0.5-1
- ros-jazzy-mrpt-map-server: 2.0.0-1
- ros-jazzy-mrpt-msgs-bridge: 2.0.0-1
- ros-jazzy-mrpt-nav-interfaces: 2.0.0-1
- ros-jazzy-mrpt-navigation: 2.0.0-1
- ros-jazzy-mrpt-pf-localization: 2.0.0-1
- ros-jazzy-mrpt-pointcloud-pipeline: 2.0.0-1
- ros-jazzy-mrpt-rawlog: 2.0.0-1
- ros-jazzy-mrpt-reactivenav2d: 2.0.0-1
- ros-jazzy-mrpt-tutorials: 2.0.0-1
- ros-jazzy-nav2-minimal-tb3-sim: 1.0.0-1
- ros-jazzy-nav2-minimal-tb4-description: 1.0.0-1
- ros-jazzy-nav2-minimal-tb4-sim: 1.0.0-1
- ros-jazzy-octomap-mapping: 2.2.0-1
- ros-jazzy-octomap-server: 2.2.0-1
- ros-jazzy-openeb-vendor: 1.3.1-1
- ros-jazzy-proxsuite: 0.6.5-1
- ros-jazzy-py-binding-tools: 2.0.0-1
- ros-jazzy-rmf-building-sim-gz-plugins: 2.3.2-1
- ros-jazzy-rmf-robot-sim-common: 2.3.2-1
- ros-jazzy-rmf-robot-sim-gz-plugins: 2.3.2-1
- ros-jazzy-rtabmap: 0.21.5-1
- ros-jazzy-rviz-satellite: 4.0.0-1
- ros-jazzy-septentrio-gnss-driver: 1.4.0-3
Updated Packages [196]:
- ros-jazzy-ackermann-steering-controller: 4.8.0-1 → 4.9.0-1
- ros-jazzy-admittance-controller: 4.8.0-1 → 4.9.0-1
- ros-jazzy-apriltag-ros: 3.1.1-5 → 3.2.2-1
- ros-jazzy-aruco-opencv: 6.0.0-1 → 6.0.1-1
- ros-jazzy-aruco-opencv-msgs: 6.0.0-1 → 6.0.1-1
- ros-jazzy-bicycle-steering-controller: 4.8.0-1 → 4.9.0-1
- ros-jazzy-camera-calibration: 5.0.1-2 → 5.0.1-3
- ros-jazzy-camera-calibration-parsers: 5.1.2-2 → 5.1.3-1
- ros-jazzy-camera-info-manager: 5.1.2-2 → 5.1.3-1
- ros-jazzy-control-msgs: 5.1.0-2 → 5.2.0-1
- ros-jazzy-depth-image-proc: 5.0.1-2 → 5.0.1-3
- ros-jazzy-diff-drive-controller: 4.8.0-1 → 4.9.0-1
- ros-jazzy-draco-point-cloud-transport: 3.0.3-3 → 4.0.0-1
- ros-jazzy-effort-controllers: 4.8.0-1 → 4.9.0-1
- ros-jazzy-eigenpy: 3.1.4-3 → 3.7.0-1
- ros-jazzy-event-camera-codecs: 1.0.4-3 → 1.3.5-1
- ros-jazzy-event-camera-msgs: 1.0.5-3 → 1.3.6-1
- ros-jazzy-event-camera-py: 1.0.4-3 → 1.3.6-1
- ros-jazzy-event-camera-renderer: 1.0.3-3 → 1.3.4-1
- ros-jazzy-examples-tf2-py: 0.36.3-1 → 0.36.4-1
- ros-jazzy-fields2cover: 2.0.0-8 → 2.0.0-9
- ros-jazzy-force-torque-sensor-broadcaster: 4.8.0-1 → 4.9.0-1
- ros-jazzy-forward-command-controller: 4.8.0-1 → 4.9.0-1
- ros-jazzy-foxglove-bridge: 0.7.6-3 → 0.7.7-1
- ros-jazzy-geometric-shapes: 2.1.3-5 → 2.2.0-1
- ros-jazzy-geometry2: 0.36.3-1 → 0.36.4-1
- ros-jazzy-gripper-controllers: 4.8.0-1 → 4.9.0-1
- ros-jazzy-gtsam: 4.2.0-1 → 4.2.0-2
- ros-jazzy-hpp-fcl: 2.4.4-2 → 2.4.4-3
- ros-jazzy-image-common: 5.1.2-2 → 5.1.3-1
- ros-jazzy-image-pipeline: 5.0.1-2 → 5.0.1-3
- ros-jazzy-image-proc: 5.0.1-2 → 5.0.1-3
- ros-jazzy-image-publisher: 5.0.1-2 → 5.0.1-3
- ros-jazzy-image-rotate: 5.0.1-2 → 5.0.1-3
- ros-jazzy-image-transport: 5.1.2-2 → 5.1.3-1
- ros-jazzy-image-view: 5.0.1-2 → 5.0.1-3
- ros-jazzy-imu-sensor-broadcaster: 4.8.0-1 → 4.9.0-1
- ros-jazzy-irobot-create-msgs: 2.1.0-4 → 3.0.0-1
- ros-jazzy-joint-state-broadcaster: 4.8.0-1 → 4.9.0-1
- ros-jazzy-joint-trajectory-controller: 4.8.0-1 → 4.9.0-1
- ros-jazzy-kinematics-interface: 1.0.0-3 → 1.1.0-1
- ros-jazzy-kinematics-interface-kdl: 1.0.0-3 → 1.1.0-1
- ros-jazzy-kitti-metrics-eval: 1.0.2-2 → 1.0.5-1
- ros-jazzy-libcaer-driver: 1.0.0-3 → 1.3.3-1
- ros-jazzy-mavros-msgs: 2.6.0-3 → 2.8.0-1
- ros-jazzy-menge-vendor: 1.2.0-3 → 1.2.1-1
- ros-jazzy-message-tf-frame-transformer: 1.1.1-2 → 1.1.2-1
- ros-jazzy-mola-bridge-ros2: 1.0.2-2 → 1.0.5-1
- ros-jazzy-mola-common: 0.3.0-3 → 0.3.1-1
- ros-jazzy-mola-demos: 1.0.2-2 → 1.0.5-1
- ros-jazzy-mola-imu-preintegration: 1.0.2-2 → 1.0.5-1
- ros-jazzy-mola-input-euroc-dataset: 1.0.2-2 → 1.0.5-1
- ros-jazzy-mola-input-kitti-dataset: 1.0.2-2 → 1.0.5-1
- ros-jazzy-mola-input-kitti360-dataset: 1.0.2-2 → 1.0.5-1
- ros-jazzy-mola-input-mulran-dataset: 1.0.2-2 → 1.0.5-1
- ros-jazzy-mola-input-paris-luco-dataset: 1.0.2-2 → 1.0.5-1
- ros-jazzy-mola-input-rawlog: 1.0.2-2 → 1.0.5-1
- ros-jazzy-mola-input-rosbag2: 1.0.2-2 → 1.0.5-1
- ros-jazzy-mola-kernel: 1.0.2-2 → 1.0.5-1
- ros-jazzy-mola-launcher: 1.0.2-2 → 1.0.5-1
- ros-jazzy-mola-metric-maps: 1.0.2-2 → 1.0.5-1
- ros-jazzy-mola-navstate-fuse: 1.0.2-2 → 1.0.5-1
- ros-jazzy-mola-pose-list: 1.0.2-2 → 1.0.5-1
- ros-jazzy-mola-relocalization: 1.0.2-2 → 1.0.5-1
- ros-jazzy-mola-test-datasets: 0.3.1-2 → 0.3.3-1
- ros-jazzy-mola-traj-tools: 1.0.2-2 → 1.0.5-1
- ros-jazzy-mola-viz: 1.0.2-2 → 1.0.5-1
- ros-jazzy-mola-yaml: 1.0.2-2 → 1.0.5-1
- ros-jazzy-moveit-msgs: 2.4.0-3 → 2.5.0-1
- ros-jazzy-mp2p-icp: 1.3.1-2 → 1.4.3-1
- ros-jazzy-mqtt-client: 2.2.1-1 → 2.3.0-1
- ros-jazzy-mqtt-client-interfaces: 2.2.1-1 → 2.3.0-1
- ros-jazzy-mrpt-path-planning: 0.1.1-2 → 0.1.3-1
- ros-jazzy-mrpt2: 2.12.1-1 → 2.13.1-1
- ros-jazzy-mvsim: 0.9.2-2 → 0.9.4-1
- ros-jazzy-ortools-vendor: 9.9.0-5 → 9.9.0-6
- ros-jazzy-pid-controller: 4.8.0-1 → 4.9.0-1
- ros-jazzy-point-cloud-interfaces: 3.0.3-3 → 4.0.0-1
- ros-jazzy-point-cloud-transport: 4.0.0-2 → 4.0.1-1
- ros-jazzy-point-cloud-transport-plugins: 3.0.3-3 → 4.0.0-1
- ros-jazzy-point-cloud-transport-py: 4.0.0-2 → 4.0.1-1
- ros-jazzy-position-controllers: 4.8.0-1 → 4.9.0-1
- ros-jazzy-range-sensor-broadcaster: 4.8.0-1 → 4.9.0-1
- ros-jazzy-rc-genicam-driver: 0.3.0-4 → 0.3.1-1
- ros-jazzy-ros2-controllers: 4.8.0-1 → 4.9.0-1
- ros-jazzy-ros2-controllers-test-nodes: 4.8.0-1 → 4.9.0-1
- ros-jazzy-rqt-joint-trajectory-controller: 4.8.0-1 → 4.9.0-1
- ros-jazzy-rqt-tf-tree: 1.0.4-4 → 1.0.5-1
- ros-jazzy-sophus: 1.22.9100-2 → 1.22.9102-2
- ros-jazzy-steering-controllers-library: 4.8.0-1 → 4.9.0-1
- ros-jazzy-stereo-image-proc: 5.0.1-2 → 5.0.1-3
- ros-jazzy-tf2: 0.36.3-1 → 0.36.4-1
- ros-jazzy-tf2-bullet: 0.36.3-1 → 0.36.4-1
- ros-jazzy-tf2-eigen: 0.36.3-1 → 0.36.4-1
- ros-jazzy-tf2-eigen-kdl: 0.36.3-1 → 0.36.4-1
- ros-jazzy-tf2-geometry-msgs: 0.36.3-1 → 0.36.4-1
- ros-jazzy-tf2-kdl: 0.36.3-1 → 0.36.4-1
- ros-jazzy-tf2-msgs: 0.36.3-1 → 0.36.4-1
- ros-jazzy-tf2-py: 0.36.3-1 → 0.36.4-1
- ros-jazzy-tf2-ros: 0.36.3-1 → 0.36.4-1
- ros-jazzy-tf2-ros-py: 0.36.3-1 → 0.36.4-1
- ros-jazzy-tf2-sensor-msgs: 0.36.3-1 → 0.36.4-1
- ros-jazzy-tf2-tools: 0.36.3-1 → 0.36.4-1
- ros-jazzy-tracetools-image-pipeline: 5.0.1-2 → 5.0.1-3
- ros-jazzy-tricycle-controller: 4.8.0-1 → 4.9.0-1
- ros-jazzy-tricycle-steering-controller: 4.8.0-1 → 4.9.0-1
- ros-jazzy-ur-client-library: 1.3.6-2 → 1.3.7-1
- ros-jazzy-velocity-controllers: 4.8.0-1 → 4.9.0-1
- ros-jazzy-zlib-point-cloud-transport: 3.0.3-3 → 4.0.0-1
- ros-jazzy-zstd-point-cloud-transport: 3.0.3-3 → 4.0.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:
- Adam Serafin
- Alberto Soragna
- Alejandro Hernandez Cordero
- Alejandro Hernández
- Andre Schröder
- Bence Magyar
- Berkay Karaman
- Bernd Pfrommer
- Christian Rauch
- Daniel Stonier
- Dave Coleman
- Denis Štogl
- Felix Exner
- Felix Ruess
- Fictionlab
- Frank Dellaert
- Gerardo Puga
- Gonzalo Mier
- Isaac I.Y. Saito
- John Hurliman
- Jose Luis Blanco-Claraco
- Jose-Luis Blanco-Claraco
- Joseph Mirabel
- José Luis Blanco-Claraco
- Justin Carpentier
- Lennart Reiher
- Luca Della Vedova
- Markus Bader
- Martin Pecka
- Mathieu Labbe
- Philipp Schillinger
- Robert Haschke
- Shao Guoliang
- Steve Macenski
- Tibor Dome
- Tim Clephas
- Tyler Weaver
- Vincent Rabaud
- Vladimir Ermakov
- Víctor Mayoral-Vilches
- Wolfgang Merkt
1 post - 1 participant
![[WWW] [WWW]](./rostheme/img/moin-www.png)
ROS Discourse General: Ros2_documentation provides html artifacts via github action
Hi ROS developers and maintainers,
Just a quick announcement for documentation development.
Now ros2_documentation provides html artifacts via github action for every commit of Pull Request.
Click on html-artifacts
to download html files built with incoming changes.
What was the problem?
It is kinda burden for developers and maintainers to build the html from incoming PR to make sure how it looks like during review process. besides, this happens several times for each PR…
Solution
Using github action artifacts to upload the html files in every commit. So that we can see html files with incoming changes only with downloading.
What’s in it for us?
for developers, they can see the html artifacts built with proposed PR to verify.
for maintainers, it makes easier to check how the final html files look like with downloading the artifacts.
Originally issued: prebuilt html artifacts can help the review for each PR? · Issue #4543 · ros2/ros2_documentation · GitHub
always welcome further improvement and ideas, please share your thoughts.
thanks,
Tomoya
1 post - 1 participant
![[WWW] [WWW]](./rostheme/img/moin-www.png)
ROS Discourse General: ROS News for the Week of June 10th, 2024
ROS News for the Week of June 10th, 2024
We’re adding another regional ROSCon this year! ROSCon China will be happening 2024-11-11T08:00:00Z UTC→2024-11-12T08:00:00Z UTC in Shenzhen! I am really excited for this event and I can’t wait to see what our Chinese ROS community is working on!
Our next Gazebo Community Meeting is scheduled for 2024-06-26T16:00:00Z UTC. Our own Ian Chen will be presenting on, “building and optimizing Gazebo simulation environments.” It should be a really good talk!
CVPR is next week and all of the publications and code from the event are starting to get released. I’ve included a few relevant ones below. I know OpenCV plans to have a booth at CVPR and you should drop by if you are attending.
CVPR also provides all of their papers and workshop materials free online! FREE Papers – FREE Workshop Materials
![:tada: :tada:](https://emoji.discourse-cdn.com/twitter/tada.png?v=12)
Events
- 2024-06-13 IEEE Manufacturing Workshop for Robotics Startups
- 2024-06-14 Source @ Open Sauce After Party in San Francisco
- 2024-06-?? Workshop on Agriculture Vision at CVPR 2024
- 2024-06-11 Warehouse Automation with ROS 2 Open Class
- 2024-06-12 Women in Robotics Boulder @ PickNik
- 2024-06-13 ROS Meetup Munich
- 2024-06-16 Food Topping Challenge at ICRA 2024
- 2024-06-20 ARM Institute Coffee, Robots, and Collaboration
- 2024-06-25 Hamlyn Symposium on Open-Source Software for Surgical Technology
- 2024-06-26 Master Multi-Robot Fleet Management: Open-RMF
- 2024-06-26 Gazebo Community Meeting
- 2024-06-19 => 2024-06-20 ROSCon France
- 2024-07-02 Medical Community Group Meeting
- 2024-07-29 => 2024-08-02 IEEE RAS Multi-Robot Summer School Prague
- 2024-08-05 Autonomous Systems Bootcam at Univ. Deleware– Video
- 2024-08-16 => 2024-08-17 Ubucon Latin America
- 2024-09-07 Silicon Valley Robotics Robot Block Party
- 2024-09-18 Foxglove Actuate San Francisco
- 2024-09-19 ==> 2024-09-20 ROSCon Spain
- 2024-09-25 ROSConJP
- 2024-10-22 → 2024-10-24 AgRobot FIRA in Sacramento
- 2024-10-23 → 2024-10-25 16th International Conference on Social Robotics +AI
- 2024-11-02 → 2024-11-03 ROSCon China in Shenzhen
- 2024-12-03 ROSCon Germany
News
- ROSCon China in Shenzhen!!!
- ROSCon JP Workshops
- CVPR – OpenVLA: An Open-Source Vision-Language-Action Model
- CVPR – SuperPrimitive: Scene Reconstruction at a Primitive Level
- CVPR – Real2Code: Reconstruct Articulated Objects via Code Generation
- CVPR – NeRF-MAE: Masked AutoEncoders for Self-Supervised 3D Representation Learning for Neural Radiance Fields
- FREE: CVPR 2024 Papers
- FREE: CVPR 2024 Workshops
- Open Hardware Summit Keynote: Danielle Boyer – From Bytes to Bright Futures: The Robots Changing the World
- Open Source Hardware Certifications for May 2024
- LEGO Mechanism but BIG
- This humanoid robot can drive cars — sort of
- Generative AI takes robots a step closer to general purpose
- IEEE launches study group to explore and develop humanoid robot standards
- ROBOTIS and Realbotix become official development partners
- igus acquires Atronia, invests in smart plastics sensors for Industry 4.0
- Floatic raises $3.8M for AMRs to tackle e-commerce picking
- Waymo updates software after robotaxi drives into telephone pole
- Leading tractor manufacturers hosting annual hacking week
- Simbe end user survey validates that Tally can transform inventory management
- Video Friday
- The Mythical Non-Roboticist Wouldn’t it be great if everyone could do robotics?
- Red Hat joins the Autoware Foundation!
- Podcast on the History of F1Tenth
- MoveIt GSoC Contributors
ROS
- 30 New and 217 Updated Packages for Iron Irwini
- 62 New and 255 Updated Packages for Rolling Ridley
- 88 New and 326 Updated Packages for Humble Hawksbill
- 3 New and 85 Updated Packages for Noetic Ninjemys
- Rate Control Subscription? Any other work-around or ideas?
- arm_api2 - simple interface for robot manipulation
- ABI/API Compliance Checking Github Workflow
- Action Introspection & Rosbag2 Action Record/Replay Support
- RoboCup Home challenge solved with BT-Studio
- ROS 2 Driver for Kinect V 2
- ROS 2 Intro Videos in Korean
- ROS Steering Functions for Car-Like Robots
Inverse Kinematics for leader-follower arms in ROS 2
- Implementation of A Fast, Lightweight, and Dynamic Octree for Proximity Search
Got a minute
?
Every Friday the former OSRF crew takes 30 minutes to catch up on ROS maintance work! We would really appreciate if everyone spent 30 minutes on Friday doing one small thing to improve the ROS ecosystem. Review a pull request! Answer a question on Robotics Stack Exchange. Send a PR to the ROS 2 Documentation.
We
need
your
contributions!
1 post - 1 participant
![[WWW] [WWW]](./rostheme/img/moin-www.png)
ROS Discourse General: New Packages for Iron Irwini 2024-06-14
We’re happy to announce 30 new packages and 217 updates are now available in ROS 2 Iron Irwini
. This sync was tagged as
iron/2024-06-14
.
Package Updates for iron
Added Packages [30]:
- ros-iron-fast-gicp: 0.0.0-1
- ros-iron-fast-gicp-dbgsym: 0.0.0-1
- ros-iron-mrpt-map-server: 2.0.0-1
- ros-iron-mrpt-map-server-dbgsym: 2.0.0-1
- ros-iron-mrpt-msgs-bridge: 2.0.0-1
- ros-iron-mrpt-nav-interfaces: 2.0.0-1
- ros-iron-mrpt-nav-interfaces-dbgsym: 2.0.0-1
- ros-iron-mrpt-navigation: 2.0.0-1
- ros-iron-mrpt-pf-localization: 2.0.0-1
- ros-iron-mrpt-pf-localization-dbgsym: 2.0.0-1
- ros-iron-mrpt-pointcloud-pipeline: 2.0.0-1
- ros-iron-mrpt-pointcloud-pipeline-dbgsym: 2.0.0-1
- ros-iron-mrpt-rawlog: 2.0.0-1
- ros-iron-mrpt-rawlog-dbgsym: 2.0.0-1
- ros-iron-mrpt-reactivenav2d: 2.0.0-1
- ros-iron-mrpt-reactivenav2d-dbgsym: 2.0.0-1
- ros-iron-mrpt-tutorials: 2.0.0-1
- ros-iron-ndt-omp: 0.0.0-2
- ros-iron-ndt-omp-dbgsym: 0.0.0-2
- ros-iron-openeb-vendor: 1.2.1-1
- ros-iron-openeb-vendor-dbgsym: 1.2.1-1
- ros-iron-ortools-vendor: 9.9.0-12
- ros-iron-ortools-vendor-dbgsym: 9.9.0-12
- ros-iron-pcl-ros-dbgsym: 2.5.4-1
- ros-iron-proxsuite: 0.6.5-1
- ros-iron-py-binding-tools: 2.0.0-1
- ros-iron-py-binding-tools-dbgsym: 2.0.0-1
- ros-iron-situational-graphs-msgs: 0.0.1-1
- ros-iron-situational-graphs-msgs-dbgsym: 0.0.1-1
- ros-iron-steering-functions: 0.3.0-1
Updated Packages [217]:
- ros-iron-aruco-opencv: 5.2.0-1 → 5.2.1-1
- ros-iron-aruco-opencv-dbgsym: 5.2.0-1 → 5.2.1-1
- ros-iron-aruco-opencv-msgs: 5.2.0-1 → 5.2.1-1
- ros-iron-aruco-opencv-msgs-dbgsym: 5.2.0-1 → 5.2.1-1
- ros-iron-beluga: 2.0.0-1 → 2.0.1-1
- ros-iron-beluga-amcl: 2.0.0-1 → 2.0.1-1
- ros-iron-beluga-amcl-dbgsym: 2.0.0-1 → 2.0.1-1
- ros-iron-beluga-ros: 2.0.0-1 → 2.0.1-1
- ros-iron-control-msgs: 5.1.0-1 → 5.2.0-1
- ros-iron-control-msgs-dbgsym: 5.1.0-1 → 5.2.0-1
- ros-iron-costmap-queue: 1.2.7-1 → 1.2.9-1
- ros-iron-costmap-queue-dbgsym: 1.2.7-1 → 1.2.9-1
- ros-iron-depthai: 2.24.0-1 → 2.26.1-1
- ros-iron-depthai-dbgsym: 2.24.0-1 → 2.26.1-1
- ros-iron-dwb-core: 1.2.7-1 → 1.2.9-1
- ros-iron-dwb-core-dbgsym: 1.2.7-1 → 1.2.9-1
- ros-iron-dwb-critics: 1.2.7-1 → 1.2.9-1
- ros-iron-dwb-critics-dbgsym: 1.2.7-1 → 1.2.9-1
- ros-iron-dwb-msgs: 1.2.7-1 → 1.2.9-1
- ros-iron-dwb-msgs-dbgsym: 1.2.7-1 → 1.2.9-1
- ros-iron-dwb-plugins: 1.2.7-1 → 1.2.9-1
- ros-iron-dwb-plugins-dbgsym: 1.2.7-1 → 1.2.9-1
- ros-iron-eigenpy: 3.1.4-1 → 3.6.0-1
- ros-iron-eigenpy-dbgsym: 3.1.4-1 → 3.6.0-1
- ros-iron-etsi-its-cam-coding: 2.0.1-1 → 2.0.2-1
- ros-iron-etsi-its-cam-coding-dbgsym: 2.0.1-1 → 2.0.2-1
- ros-iron-etsi-its-cam-conversion: 2.0.1-1 → 2.0.2-1
- ros-iron-etsi-its-cam-msgs: 2.0.1-1 → 2.0.2-1
- ros-iron-etsi-its-cam-msgs-dbgsym: 2.0.1-1 → 2.0.2-1
- ros-iron-etsi-its-coding: 2.0.1-1 → 2.0.2-1
- ros-iron-etsi-its-conversion: 2.0.1-1 → 2.0.2-1
- ros-iron-etsi-its-conversion-dbgsym: 2.0.1-1 → 2.0.2-1
- ros-iron-etsi-its-denm-coding: 2.0.1-1 → 2.0.2-1
- ros-iron-etsi-its-denm-coding-dbgsym: 2.0.1-1 → 2.0.2-1
- ros-iron-etsi-its-denm-conversion: 2.0.1-1 → 2.0.2-1
- ros-iron-etsi-its-denm-msgs: 2.0.1-1 → 2.0.2-1
- ros-iron-etsi-its-denm-msgs-dbgsym: 2.0.1-1 → 2.0.2-1
- ros-iron-etsi-its-messages: 2.0.1-1 → 2.0.2-1
- ros-iron-etsi-its-msgs: 2.0.1-1 → 2.0.2-1
- ros-iron-etsi-its-msgs-utils: 2.0.1-1 → 2.0.2-1
- ros-iron-etsi-its-primitives-conversion: 2.0.1-1 → 2.0.2-1
- ros-iron-etsi-its-rviz-plugins: 2.0.1-1 → 2.0.2-1
- ros-iron-etsi-its-rviz-plugins-dbgsym: 2.0.1-1 → 2.0.2-1
- ros-iron-event-camera-msgs: 1.2.5-1 → 1.2.6-1
- ros-iron-event-camera-msgs-dbgsym: 1.2.5-1 → 1.2.6-1
- ros-iron-event-camera-py: 1.2.5-1 → 1.2.6-1
- ros-iron-examples-tf2-py: 0.31.6-1 → 0.31.7-1
- ros-iron-fastrtps: 2.10.3-1 → 2.10.4-1
- ros-iron-fastrtps-dbgsym: 2.10.3-1 → 2.10.4-1
- ros-iron-fields2cover: 2.0.0-10 → 2.0.0-11
- ros-iron-fields2cover-dbgsym: 2.0.0-10 → 2.0.0-11
- ros-iron-flexbe-behavior-engine: 3.0.0-1 → 3.0.2-1
- ros-iron-flexbe-core: 3.0.0-1 → 3.0.2-1
- ros-iron-flexbe-input: 3.0.0-1 → 3.0.2-1
- ros-iron-flexbe-mirror: 3.0.0-1 → 3.0.2-1
- ros-iron-flexbe-msgs: 3.0.0-1 → 3.0.2-1
- ros-iron-flexbe-msgs-dbgsym: 3.0.0-1 → 3.0.2-1
- ros-iron-flexbe-onboard: 3.0.0-1 → 3.0.2-1
- ros-iron-flexbe-states: 3.0.0-1 → 3.0.2-1
- ros-iron-flexbe-testing: 3.0.0-1 → 3.0.2-1
- ros-iron-flexbe-widget: 3.0.0-1 → 3.0.2-1
- ros-iron-geometry2: 0.31.6-1 → 0.31.7-1
- ros-iron-hpp-fcl: 2.4.0-1 → 2.4.4-1
- ros-iron-hpp-fcl-dbgsym: 2.4.0-1 → 2.4.4-1
- ros-iron-kitti-metrics-eval: 1.0.4-1 → 1.0.5-1
- ros-iron-kitti-metrics-eval-dbgsym: 1.0.4-1 → 1.0.5-1
- ros-iron-kobuki-core: 1.4.0-3 → 1.4.1-1
- ros-iron-kobuki-core-dbgsym: 1.4.0-3 → 1.4.1-1
- ros-iron-libcaer-driver: 1.2.1-1 → 1.2.3-1
- ros-iron-libcaer-driver-dbgsym: 1.2.1-1 → 1.2.3-1
- ros-iron-libmavconn: 2.7.0-1 → 2.8.0-1
- ros-iron-libmavconn-dbgsym: 2.7.0-1 → 2.8.0-1
- ros-iron-mavlink: 2024.3.3-1 → 2024.6.6-1
- ros-iron-mavros: 2.7.0-1 → 2.8.0-1
- ros-iron-mavros-dbgsym: 2.7.0-1 → 2.8.0-1
- ros-iron-mavros-extras: 2.7.0-1 → 2.8.0-1
- ros-iron-mavros-extras-dbgsym: 2.7.0-1 → 2.8.0-1
- ros-iron-mavros-msgs: 2.7.0-1 → 2.8.0-1
- ros-iron-mavros-msgs-dbgsym: 2.7.0-1 → 2.8.0-1
- ros-iron-mola: 1.0.4-1 → 1.0.5-1
- ros-iron-mola-bridge-ros2: 1.0.4-1 → 1.0.5-1
- ros-iron-mola-bridge-ros2-dbgsym: 1.0.4-1 → 1.0.5-1
- ros-iron-mola-demos: 1.0.4-1 → 1.0.5-1
- ros-iron-mola-imu-preintegration: 1.0.4-1 → 1.0.5-1
- ros-iron-mola-imu-preintegration-dbgsym: 1.0.4-1 → 1.0.5-1
- ros-iron-mola-input-euroc-dataset: 1.0.4-1 → 1.0.5-1
- ros-iron-mola-input-euroc-dataset-dbgsym: 1.0.4-1 → 1.0.5-1
- ros-iron-mola-input-kitti-dataset: 1.0.4-1 → 1.0.5-1
- ros-iron-mola-input-kitti-dataset-dbgsym: 1.0.4-1 → 1.0.5-1
- ros-iron-mola-input-kitti360-dataset: 1.0.4-1 → 1.0.5-1
- ros-iron-mola-input-kitti360-dataset-dbgsym: 1.0.4-1 → 1.0.5-1
- ros-iron-mola-input-mulran-dataset: 1.0.4-1 → 1.0.5-1
- ros-iron-mola-input-mulran-dataset-dbgsym: 1.0.4-1 → 1.0.5-1
- ros-iron-mola-input-paris-luco-dataset: 1.0.4-1 → 1.0.5-1
- ros-iron-mola-input-paris-luco-dataset-dbgsym: 1.0.4-1 → 1.0.5-1
- ros-iron-mola-input-rawlog: 1.0.4-1 → 1.0.5-1
- ros-iron-mola-input-rawlog-dbgsym: 1.0.4-1 → 1.0.5-1
- ros-iron-mola-input-rosbag2: 1.0.4-1 → 1.0.5-1
- ros-iron-mola-input-rosbag2-dbgsym: 1.0.4-1 → 1.0.5-1
- ros-iron-mola-kernel: 1.0.4-1 → 1.0.5-1
- ros-iron-mola-kernel-dbgsym: 1.0.4-1 → 1.0.5-1
- ros-iron-mola-launcher: 1.0.4-1 → 1.0.5-1
- ros-iron-mola-launcher-dbgsym: 1.0.4-1 → 1.0.5-1
- ros-iron-mola-metric-maps: 1.0.4-1 → 1.0.5-1
- ros-iron-mola-metric-maps-dbgsym: 1.0.4-1 → 1.0.5-1
- ros-iron-mola-navstate-fuse: 1.0.4-1 → 1.0.5-1
- ros-iron-mola-navstate-fuse-dbgsym: 1.0.4-1 → 1.0.5-1
- ros-iron-mola-pose-list: 1.0.4-1 → 1.0.5-1
- ros-iron-mola-pose-list-dbgsym: 1.0.4-1 → 1.0.5-1
- ros-iron-mola-relocalization: 1.0.4-1 → 1.0.5-1
- ros-iron-mola-relocalization-dbgsym: 1.0.4-1 → 1.0.5-1
- ros-iron-mola-traj-tools: 1.0.4-1 → 1.0.5-1
- ros-iron-mola-traj-tools-dbgsym: 1.0.4-1 → 1.0.5-1
- ros-iron-mola-viz: 1.0.4-1 → 1.0.5-1
- ros-iron-mola-viz-dbgsym: 1.0.4-1 → 1.0.5-1
- ros-iron-mola-yaml: 1.0.4-1 → 1.0.5-1
- ros-iron-mola-yaml-dbgsym: 1.0.4-1 → 1.0.5-1
- ros-iron-mp2p-icp: 1.4.1-1 → 1.4.3-1
- ros-iron-mp2p-icp-dbgsym: 1.4.1-1 → 1.4.3-1
- ros-iron-mqtt-client: 2.2.1-1 → 2.3.0-1
- ros-iron-mqtt-client-dbgsym: 2.2.1-1 → 2.3.0-1
- ros-iron-mqtt-client-interfaces: 2.2.1-1 → 2.3.0-1
- ros-iron-mqtt-client-interfaces-dbgsym: 2.2.1-1 → 2.3.0-1
- ros-iron-mrpt2: 2.13.0-1 → 2.13.1-1
- ros-iron-mrpt2-dbgsym: 2.13.0-1 → 2.13.1-1
- ros-iron-nav-2d-msgs: 1.2.7-1 → 1.2.9-1
- ros-iron-nav-2d-msgs-dbgsym: 1.2.7-1 → 1.2.9-1
- ros-iron-nav-2d-utils: 1.2.7-1 → 1.2.9-1
- ros-iron-nav-2d-utils-dbgsym: 1.2.7-1 → 1.2.9-1
- ros-iron-nav2-amcl: 1.2.7-1 → 1.2.9-1
- ros-iron-nav2-amcl-dbgsym: 1.2.7-1 → 1.2.9-1
- ros-iron-nav2-behavior-tree: 1.2.7-1 → 1.2.9-1
- ros-iron-nav2-behavior-tree-dbgsym: 1.2.7-1 → 1.2.9-1
- ros-iron-nav2-behaviors: 1.2.7-1 → 1.2.9-1
- ros-iron-nav2-behaviors-dbgsym: 1.2.7-1 → 1.2.9-1
- ros-iron-nav2-bringup: 1.2.7-1 → 1.2.9-1
- ros-iron-nav2-bt-navigator: 1.2.7-1 → 1.2.9-1
- ros-iron-nav2-bt-navigator-dbgsym: 1.2.7-1 → 1.2.9-1
- ros-iron-nav2-collision-monitor: 1.2.7-1 → 1.2.9-1
- ros-iron-nav2-collision-monitor-dbgsym: 1.2.7-1 → 1.2.9-1
- ros-iron-nav2-common: 1.2.7-1 → 1.2.9-1
- ros-iron-nav2-constrained-smoother: 1.2.7-1 → 1.2.9-1
- ros-iron-nav2-constrained-smoother-dbgsym: 1.2.7-1 → 1.2.9-1
- ros-iron-nav2-controller: 1.2.7-1 → 1.2.9-1
- ros-iron-nav2-controller-dbgsym: 1.2.7-1 → 1.2.9-1
- ros-iron-nav2-core: 1.2.7-1 → 1.2.9-1
- ros-iron-nav2-costmap-2d: 1.2.7-1 → 1.2.9-1
- ros-iron-nav2-costmap-2d-dbgsym: 1.2.7-1 → 1.2.9-1
- ros-iron-nav2-dwb-controller: 1.2.7-1 → 1.2.9-1
- ros-iron-nav2-lifecycle-manager: 1.2.7-1 → 1.2.9-1
- ros-iron-nav2-lifecycle-manager-dbgsym: 1.2.7-1 → 1.2.9-1
- ros-iron-nav2-map-server: 1.2.7-1 → 1.2.9-1
- ros-iron-nav2-map-server-dbgsym: 1.2.7-1 → 1.2.9-1
- ros-iron-nav2-mppi-controller: 1.2.7-1 → 1.2.9-1
- ros-iron-nav2-mppi-controller-dbgsym: 1.2.7-1 → 1.2.9-1
- ros-iron-nav2-msgs: 1.2.7-1 → 1.2.9-1
- ros-iron-nav2-msgs-dbgsym: 1.2.7-1 → 1.2.9-1
- ros-iron-nav2-navfn-planner: 1.2.7-1 → 1.2.9-1
- ros-iron-nav2-navfn-planner-dbgsym: 1.2.7-1 → 1.2.9-1
- ros-iron-nav2-planner: 1.2.7-1 → 1.2.9-1
- ros-iron-nav2-planner-dbgsym: 1.2.7-1 → 1.2.9-1
- ros-iron-nav2-regulated-pure-pursuit-controller: 1.2.7-1 → 1.2.9-1
- ros-iron-nav2-regulated-pure-pursuit-controller-dbgsym: 1.2.7-1 → 1.2.9-1
- ros-iron-nav2-rotation-shim-controller: 1.2.7-1 → 1.2.9-1
- ros-iron-nav2-rotation-shim-controller-dbgsym: 1.2.7-1 → 1.2.9-1
- ros-iron-nav2-rviz-plugins: 1.2.7-1 → 1.2.9-1
- ros-iron-nav2-rviz-plugins-dbgsym: 1.2.7-1 → 1.2.9-1
- ros-iron-nav2-simple-commander: 1.2.7-1 → 1.2.9-1
- ros-iron-nav2-smac-planner: 1.2.7-1 → 1.2.9-1
- ros-iron-nav2-smac-planner-dbgsym: 1.2.7-1 → 1.2.9-1
- ros-iron-nav2-smoother: 1.2.7-1 → 1.2.9-1
- ros-iron-nav2-smoother-dbgsym: 1.2.7-1 → 1.2.9-1
- ros-iron-nav2-system-tests: 1.2.7-1 → 1.2.9-1
- ros-iron-nav2-system-tests-dbgsym: 1.2.7-1 → 1.2.9-1
- ros-iron-nav2-theta-star-planner: 1.2.7-1 → 1.2.9-1
- ros-iron-nav2-theta-star-planner-dbgsym: 1.2.7-1 → 1.2.9-1
- ros-iron-nav2-util: 1.2.7-1 → 1.2.9-1
- ros-iron-nav2-util-dbgsym: 1.2.7-1 → 1.2.9-1
- ros-iron-nav2-velocity-smoother: 1.2.7-1 → 1.2.9-1
- ros-iron-nav2-velocity-smoother-dbgsym: 1.2.7-1 → 1.2.9-1
- ros-iron-nav2-voxel-grid: 1.2.7-1 → 1.2.9-1
- ros-iron-nav2-voxel-grid-dbgsym: 1.2.7-1 → 1.2.9-1
- ros-iron-nav2-waypoint-follower: 1.2.7-1 → 1.2.9-1
- ros-iron-nav2-waypoint-follower-dbgsym: 1.2.7-1 → 1.2.9-1
- ros-iron-navigation2: 1.2.7-1 → 1.2.9-1
- ros-iron-pcl-conversions: 2.4.0-5 → 2.5.4-1
- ros-iron-pcl-ros: 2.4.0-5 → 2.5.4-1
- ros-iron-perception-pcl: 2.4.0-5 → 2.5.4-1
- ros-iron-rc-genicam-driver: 0.3.0-3 → 0.3.1-1
- ros-iron-rc-genicam-driver-dbgsym: 0.3.0-3 → 0.3.1-1
- ros-iron-realsense2-camera: 4.54.1-2 → 4.55.1-1
- ros-iron-realsense2-camera-dbgsym: 4.54.1-2 → 4.55.1-1
- ros-iron-realsense2-camera-msgs: 4.54.1-2 → 4.55.1-1
- ros-iron-realsense2-camera-msgs-dbgsym: 4.54.1-2 → 4.55.1-1
- ros-iron-realsense2-description: 4.54.1-2 → 4.55.1-1
- ros-iron-septentrio-gnss-driver: 1.3.2-1 → 1.4.0-3
- ros-iron-septentrio-gnss-driver-dbgsym: 1.3.2-1 → 1.4.0-3
- ros-iron-sophus: 1.3.2-1 → 1.22.9102-2
- ros-iron-tf2: 0.31.6-1 → 0.31.7-1
- ros-iron-tf2-bullet: 0.31.6-1 → 0.31.7-1
- ros-iron-tf2-dbgsym: 0.31.6-1 → 0.31.7-1
- ros-iron-tf2-eigen: 0.31.6-1 → 0.31.7-1
- ros-iron-tf2-eigen-kdl: 0.31.6-1 → 0.31.7-1
- ros-iron-tf2-eigen-kdl-dbgsym: 0.31.6-1 → 0.31.7-1
- ros-iron-tf2-geometry-msgs: 0.31.6-1 → 0.31.7-1
- ros-iron-tf2-kdl: 0.31.6-1 → 0.31.7-1
- ros-iron-tf2-msgs: 0.31.6-1 → 0.31.7-1
- ros-iron-tf2-msgs-dbgsym: 0.31.6-1 → 0.31.7-1
- ros-iron-tf2-py: 0.31.6-1 → 0.31.7-1
- ros-iron-tf2-py-dbgsym: 0.31.6-1 → 0.31.7-1
- ros-iron-tf2-ros: 0.31.6-1 → 0.31.7-1
- ros-iron-tf2-ros-dbgsym: 0.31.6-1 → 0.31.7-1
- ros-iron-tf2-ros-py: 0.31.6-1 → 0.31.7-1
- ros-iron-tf2-sensor-msgs: 0.31.6-1 → 0.31.7-1
- ros-iron-tf2-tools: 0.31.6-1 → 0.31.7-1
- ros-iron-ur-client-library: 1.3.6-1 → 1.3.7-1
- ros-iron-ur-client-library-dbgsym: 1.3.6-1 → 1.3.7-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:
- Adam Serafin
- Alejandro Hernandez Cordero
- Alexey Merzlyakov
- Bence Magyar
- Bernd Pfrommer
- Brian Wilcox
- Carl Delsey
- Carlos Orduno
- Daniel Stonier
- David V. Lu!!
- Felix Exner
- Felix Ruess
- Fictionlab
- Gerardo Puga
- Gonzalo Mier
- Holger Banzhaf
- Jean-Pierre Busch
- Jose Luis Blanco-Claraco
- Jose-Luis Blanco-Claraco
- Joseph Mirabel
- José Luis Blanco-Claraco
- Justin Carpentier
- Lennart Reiher
- LibRealSense ROS Team
- Markus Bader
- Matej Vargovcik
- Michael Jeronimo
- Miguel Company
- Mohammad Haghighipanah
- Paul Bovbel
- Philipp Schillinger
- Robert Haschke
- Steve Macenski
- Tibor Dome
- Vladimir Ermakov
- hriday
- k.koide
- koide
- steve
1 post - 1 participant
![[WWW] [WWW]](./rostheme/img/moin-www.png)
ROS Discourse General: What do you use instead of rosmon for ROS2?
I find myself wanting a tool like rosmon for my ROS2 projects. Looking at the rosmon github repo, the maintainer has no explicit plans to swap to ROS2 in the foreseeable future. So my question is what does the ROS community use for node management in ROS2?
I am aware of ROS2 node lifecylces, however a clean interface like rosmon gives would be nice, instead of using CLI commands.
4 posts - 4 participants
![[WWW] [WWW]](./rostheme/img/moin-www.png)
ROS Discourse General: RoboCup Home challenge solved with BT-Studio
Hi folks,
a new (complex) robot challenge has been solved using BT-Studio, the JdeRobot web tool for creating BehaviorTree based robotics applications.
This new demo, called recepcionist, is a combination of various challenges from the 2022 edition of the RoboCup@Home that have been simplified in order to get a simple yet complex demo. Recepcionist consist of robot acting as a party host, it greets the guests at the door, accompanies them to the couch, brings them drinks and continues. It is made by combining nodes that interact with the blackboard, others that do not and also nodes that call actions, nav2 that is used to control the movement of the robot. This shows that the possibilities of what can be created using BT-Studio are endless.
This is a step forward beyond simple applications such as Person Following .
@facontidavide @miccol @ct2034
BT Studio 0.3 Recepcionist Demo
1 post - 1 participant
![[WWW] [WWW]](./rostheme/img/moin-www.png)
ROS Discourse General: ABI/API Compliance Checker in github workflow
Hi ROS users and developers,
i would like to open discussion and have feedback from community.
Problem
- Development and Operation Burden: maintainer and developer burden to check ABI compatibility for backport.
- Quality: we sometimes miss backporting for released distribution unless requested. (bug fixes basically should be backported to available distribution to keep the consistent quality for all supported distribution.)
Proposal
Integrate ABI/API compliance checker in github workflow to check ABI compatibility for every PR to see if the fix can be backported automatically with label.
What’s in it for us?
- User: Quality Improvement, potentially all bug fixes that ABI compatible with can backport to already released distribution.
- Developer/Maintainer: Cost Effective, automatically determine if the fix is backport-able for already released distribution. (automatically labeled.)
Comments and feedbacks are welcome!!! Please share your thoughts!
Best,
Tomoya
6 posts - 5 participants
![[WWW] [WWW]](./rostheme/img/moin-www.png)
ROS Discourse General: New Packages for Noetic 2024-06-07
We’re happy to announce 3 new packages and 85 updates are now available in ROS Noetic. This sync was tagged as noetic/2024-06-07
.
Thank you to every maintainer and contributor who made these updates available!
Package Updates for ROS Noetic
Added Packages [3]:
- ros-noetic-beluga: 2.0.1-1
- ros-noetic-beluga-amcl: 2.0.1-1
- ros-noetic-beluga-ros: 2.0.1-1
Updated Packages [85]:
- ros-noetic-ackermann-steering-controller: 0.21.2-1 → 0.22.0-1
- ros-noetic-chomp-motion-planner: 1.1.13-2 → 1.1.14-1
- ros-noetic-costmap-cspace-rviz-plugins: 0.11.7-1 → 0.17.1-1
- ros-noetic-depthai: 2.24.0-2 → 2.26.0-1
- ros-noetic-diff-drive-controller: 0.21.2-1 → 0.22.0-1
- ros-noetic-effort-controllers: 0.21.2-1 → 0.22.0-1
- ros-noetic-etsi-its-cam-coding: 2.0.1-1 → 2.0.2-2
- ros-noetic-etsi-its-cam-conversion: 2.0.1-1 → 2.0.2-2
- ros-noetic-etsi-its-cam-msgs: 2.0.1-1 → 2.0.2-2
- ros-noetic-etsi-its-coding: 2.0.1-1 → 2.0.2-2
- ros-noetic-etsi-its-conversion: 2.0.1-1 → 2.0.2-2
- ros-noetic-etsi-its-denm-coding: 2.0.1-1 → 2.0.2-2
- ros-noetic-etsi-its-denm-conversion: 2.0.1-1 → 2.0.2-2
- ros-noetic-etsi-its-denm-msgs: 2.0.1-1 → 2.0.2-2
- ros-noetic-etsi-its-messages: 2.0.1-1 → 2.0.2-2
- ros-noetic-etsi-its-msgs: 2.0.1-1 → 2.0.2-2
- ros-noetic-etsi-its-msgs-utils: 2.0.1-1 → 2.0.2-2
- ros-noetic-etsi-its-primitives-conversion: 2.0.1-1 → 2.0.2-2
- ros-noetic-etsi-its-rviz-plugins: 2.0.1-1 → 2.0.2-2
- ros-noetic-force-torque-sensor-controller: 0.21.2-1 → 0.22.0-1
- ros-noetic-forward-command-controller: 0.21.2-1 → 0.22.0-1
- ros-noetic-four-wheel-steering-controller: 0.21.2-1 → 0.22.0-1
- ros-noetic-gripper-action-controller: 0.21.2-1 → 0.22.0-1
- ros-noetic-imu-sensor-controller: 0.21.2-1 → 0.22.0-1
- ros-noetic-jackal-control: 0.8.9-1 → 0.8.10-1
- ros-noetic-jackal-description: 0.8.9-1 → 0.8.10-1
- ros-noetic-jackal-msgs: 0.8.9-1 → 0.8.10-1
- ros-noetic-jackal-navigation: 0.8.9-1 → 0.8.10-1
- ros-noetic-jackal-tutorials: 0.8.9-1 → 0.8.10-1
- ros-noetic-joint-state-controller: 0.21.2-1 → 0.22.0-1
- ros-noetic-joint-trajectory-controller: 0.21.2-1 → 0.22.0-1
- ros-noetic-microstrain-inertial-description: 4.2.0-1 → 4.3.0-1
- ros-noetic-microstrain-inertial-driver: 4.2.0-1 → 4.3.0-1
- ros-noetic-microstrain-inertial-examples: 4.2.0-1 → 4.3.0-1
- ros-noetic-microstrain-inertial-msgs: 4.2.0-1 → 4.3.0-1
- ros-noetic-microstrain-inertial-rqt: 4.2.0-1 → 4.3.0-1
- ros-noetic-moveit: 1.1.13-2 → 1.1.14-1
- ros-noetic-moveit-chomp-optimizer-adapter: 1.1.13-2 → 1.1.14-1
- ros-noetic-moveit-commander: 1.1.13-2 → 1.1.14-1
- ros-noetic-moveit-core: 1.1.13-2 → 1.1.14-1
- ros-noetic-moveit-fake-controller-manager: 1.1.13-2 → 1.1.14-1
- ros-noetic-moveit-kinematics: 1.1.13-2 → 1.1.14-1
- ros-noetic-moveit-planners: 1.1.13-2 → 1.1.14-1
- ros-noetic-moveit-planners-chomp: 1.1.13-2 → 1.1.14-1
- ros-noetic-moveit-planners-ompl: 1.1.13-2 → 1.1.14-1
- ros-noetic-moveit-plugins: 1.1.13-2 → 1.1.14-1
- ros-noetic-moveit-ros: 1.1.13-2 → 1.1.14-1
- ros-noetic-moveit-ros-benchmarks: 1.1.13-2 → 1.1.14-1
- ros-noetic-moveit-ros-control-interface: 1.1.13-2 → 1.1.14-1
- ros-noetic-moveit-ros-manipulation: 1.1.13-2 → 1.1.14-1
- ros-noetic-moveit-ros-move-group: 1.1.13-2 → 1.1.14-1
- ros-noetic-moveit-ros-occupancy-map-monitor: 1.1.13-2 → 1.1.14-1
- ros-noetic-moveit-ros-perception: 1.1.13-2 → 1.1.14-1
- ros-noetic-moveit-ros-planning: 1.1.13-2 → 1.1.14-1
- ros-noetic-moveit-ros-planning-interface: 1.1.13-2 → 1.1.14-1
- ros-noetic-moveit-ros-robot-interaction: 1.1.13-2 → 1.1.14-1
- ros-noetic-moveit-ros-visualization: 1.1.13-2 → 1.1.14-1
- ros-noetic-moveit-ros-warehouse: 1.1.13-2 → 1.1.14-1
- ros-noetic-moveit-runtime: 1.1.13-2 → 1.1.14-1
- ros-noetic-moveit-servo: 1.1.13-2 → 1.1.14-1
- ros-noetic-moveit-setup-assistant: 1.1.13-2 → 1.1.14-1
- ros-noetic-moveit-simple-controller-manager: 1.1.13-2 → 1.1.14-1
- ros-noetic-mqtt-client: 2.2.1-1 → 2.3.0-1
- ros-noetic-mqtt-client-interfaces: 2.2.1-1 → 2.3.0-1
- ros-noetic-mrpt-ekf-slam-2d: 0.1.16-1 → 0.1.17-1
- ros-noetic-mrpt-ekf-slam-3d: 0.1.16-1 → 0.1.17-1
- ros-noetic-mrpt-graphslam-2d: 0.1.16-1 → 0.1.17-1
- ros-noetic-mrpt-icp-slam-2d: 0.1.16-1 → 0.1.17-1
- ros-noetic-mrpt-rbpf-slam: 0.1.16-1 → 0.1.17-1
- ros-noetic-mrpt-slam: 0.1.16-1 → 0.1.17-1
- ros-noetic-mrpt2: 2.12.2-1 → 2.13.1-1
- ros-noetic-neonavigation-rviz-plugins: 0.11.7-1 → 0.17.1-1
- ros-noetic-pilz-industrial-motion-planner: 1.1.13-2 → 1.1.14-1
- ros-noetic-pilz-industrial-motion-planner-testutils: 1.1.13-2 → 1.1.14-1
- ros-noetic-position-controllers: 0.21.2-1 → 0.22.0-1
- ros-noetic-robot-controllers: 0.7.0-1 → 0.7.1-4
- ros-noetic-robot-controllers-interface: 0.7.0-1 → 0.7.1-4
- ros-noetic-robot-controllers-msgs: 0.7.0-1 → 0.7.1-4
- ros-noetic-ros-controllers: 0.21.2-1 → 0.22.0-1
- ros-noetic-rqt-joint-trajectory-controller: 0.21.2-1 → 0.22.0-1
- ros-noetic-rviz: 1.14.23-1 → 1.14.25-1
- ros-noetic-septentrio-gnss-driver: 1.3.2-1 → 1.4.0-5
- ros-noetic-trajectory-tracker-rviz-plugins: 0.11.7-1 → 0.17.1-1
- ros-noetic-ur-client-library: 1.3.6-1 → 1.3.7-1
- ros-noetic-velocity-controllers: 0.21.2-1 → 0.22.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:
- Adam Serafin
- Alexander Gutenkunst
- Atsushi Watanabe
- Bence Magyar
- Blake Anderson
- Chittaranjan Srinivas Swaminathan
- Dave Coleman
- Eric Relson
- Felix Exner
- Gerardo Puga
- Isaac I. Y. Saito
- Jean-Pierre Busch
- Jon Binney
- Jose Luis Blanco-Claraco
- Jose-Luis Blanco-Claraco
- Lennart Reiher
- Masaru Morita
- Mathias Lüdtke
- Michael Ferguson
- Michael Görner
- Mike Purvis
- Nikos Koukis
- Raghavender Sahdev
- Rob Fisher
- Robert Haschke
- Sachin Chitta
- Tibor Dome
- Vincent Rousseau
- Vladislav Tananaev
1 post - 1 participant
![[WWW] [WWW]](./rostheme/img/moin-www.png)
ROS Discourse General: ROS News for the week of June 3rd, 2024
ROS News for the week of June 3rd, 2024
ROSCon 2024 Registration is now open! This year we’ve doubled the number of ROSCon workshops, and we’re adding dedicated spaces for birds of a feather gatherings and community group meetings. The city of Odense is going to be rolling out the red carpet for our visit, and there will a number of scheduled lab visits, walking tours, and mixers before and after ROSCon. We are recommending ROSCon attendees plan to arrive early and plan to stay for a few days after the conference.
Give a warm welcome to our 2024 ROS / Gazebo Google Summer of Code Students. Find out more about they will be working on this summer on the Open Robotics Blog.
The Open Sauce conference is happening in San Francisco next weekend. A bunch of robotics YouTubers will be speaking at the event. Myself and Phil Nelson, the developer advocate over at OpenCV, have put together an open source at Open Sauce after party for next Friday at the new Studio 45 co-working space in SOMA. If you are in the area please come by, all are welcome, regardless if you are attending Open Sauce.
NVIDIA released Issac ROS 3.0 this week.There are lots of goodies in there, including the FoundationPose detection module I’ve been posting about for the past year.
Check out this TurtleSim Pong demo written with ROS 2 Humble!
Events
- 2024-06-13 ROS Meetup Munich
- 2024-06-13 IEEE Manufacturing Workshop for Robotics Startups
2024-06-14 Source @ Open Sauce After Party in San Francisco
- 2024-06-?? Workshop on Agriculture Vision at CVPR 2024
- 2024-06-11 Warehouse Automation with ROS 2 Open Class
- 2024-06-12 Women in Robotics Boulder @ PickNik
- 2024-06-13 ROS Meetup Munich
- 2024-06-16 Food Topping Challenge at ICRA 2024
- 2024-06-20 ARM Institute Coffee, Robots, and Collaboration
- 2024-06-25 Hamlyn Symposium on Open-Source Software for Surgical Technology
- 2024-06-26 Master Multi-Robot Fleet Management: Open-RMF
- 2024-06-19 => 2024-06-20 ROSCon France
- 2024-07-02 Medical Community Group Meeting
- 2024-07-29 => 2024-08-02 IEEE RAS Multi-Robot Summer School Prague
- 2024-08-05 Autonomous Systems Bootcam at Univ. Deleware– Video
- 2024-08-16 => 2024-08-17 Ubucon Latin America
- 2024-09-07 Silicon Valley Robotics Robot Block Party
- 2024-09-18 Foxglove Actuate San Francisco
- 2024-09-19 ==> 2024-09-20 ROSCon Spain
- 2024-09-25 ROSConJP
- 2024-10-22 → 2024-10-24 AgRobot FIRA in Sacramento
- 2024-10-23 → 2024-10-25 16th International Conference on Social Robotics +AI
- 2024-12-03 ROSCon Germany
News
- ROSCon 2024 Registration Open / Workshops Announced
- 2024 ROS / Gazebo Google Summer of Code Students – Open Robotics Blog
- ROS 2 Jazzy Jalisco Released
- BotSync Raises $5.2M
- Arduino Alvik Robot – It can run MicroROS
- Inside Apple’s efforts to build a better recycling robot
- Industries may be ready for humanoid robots, but are the robots ready for them?
- NVIDIA highlights Omniverse, Isaac adoption by robot market leaders
- Asensus Surgical agrees to merger with KARL STORZ
- Video Friday
- 2024 ROS Awards
- 2024 Autonomous Driving Challenge (Japanese)
- SLCF-Net: Sequential LiDAR-Camera Fusion for Semantic Scene Completion using a 3D Recurrent U-Net
ROS
- Five New ROS Python Tools
- Ping Pong in TurtleSim
- Isaac ROS May Update: 3.0 Release / Lots of Goodies
- 88 New and 326 Updated Packages for ROS 2 Humble Hawksbill
- A lightweight wrapper around the Catch2 testing framework for use with ROS 2
- Colcon in-container can now generate a Debian and runs on Linux, macOS and Windows
- 4 State of the Art Quadrupedal Robot Walking Controllers
- Nav2 Docking Server
- 2024-06-06 Interoperability Working Group Meeting Recording
- 2024-06-03 Cloud Robotics Community Group Meeting Recording
- June Aerial Robotics Meetings
- OGC GeoPose Package
- ROS 2 Jazzy + ROS 2 Control + Hoverboard Demo
- Isaac ROS Jetson Stats
- NVIDIA Jetson Nano: Publish TF Between Object and Camera Frames with ROS 2
- MicroROS Control of a 6DoF Robot Arm by HiWonder with Raspberry Pi Pico
- Radar Layer: RADAR Plugin for Nav2 CostMap2D
- A modular sensing system with CANBUS communication for assisted navigation of an agricultural mobile robot
- IsaacSim ROS 2 Control Example
- LIDAR Cross-Calibration ion ROS 2
- ROSBag Anonymizer
- Applying robot operating system drivers for motor controllers
Got a minute?!
We would really love some help answering ROS questions over on Robotics Stack Exchange!
1 post - 1 participant
![[WWW] [WWW]](./rostheme/img/moin-www.png)
ROS Discourse General: New packages for Humble Hawksbill 2024-06-07
Package Updates for Humble
Added Packages [88]:
- ros-humble-autoware-internal-msgs: 1.0.1-1
- ros-humble-autoware-internal-msgs-dbgsym: 1.0.1-1
- ros-humble-beluga: 2.0.1-1
- ros-humble-beluga-amcl: 2.0.1-1
- ros-humble-beluga-amcl-dbgsym: 2.0.1-1
- ros-humble-beluga-ros: 2.0.1-1
- ros-humble-bosch-locator-bridge: 2.1.11-1
- ros-humble-bosch-locator-bridge-dbgsym: 2.1.11-1
- ros-humble-bosch-locator-bridge-utils: 2.1.11-1
- ros-humble-bosch-locator-bridge-utils-dbgsym: 2.1.11-1
- ros-humble-fast-gicp: 0.0.0-1
- ros-humble-fast-gicp-dbgsym: 0.0.0-1
- ros-humble-franka-description: 0.2.0-1
- ros-humble-kuka-external-control-sdk: 1.3.1-1
- ros-humble-kuka-external-control-sdk-examples: 1.3.1-1
- ros-humble-libcaer-vendor: 1.1.0-2
- ros-humble-libcaer-vendor-dbgsym: 1.1.0-2
- ros-humble-mrpt-map-server: 2.0.1-1
- ros-humble-mrpt-map-server-dbgsym: 2.0.1-1
- ros-humble-mrpt-msgs-bridge: 2.0.1-1
- ros-humble-mrpt-nav-interfaces: 2.0.1-1
- ros-humble-mrpt-nav-interfaces-dbgsym: 2.0.1-1
- ros-humble-mrpt-navigation: 2.0.1-1
- ros-humble-mrpt-pf-localization: 2.0.1-1
- ros-humble-mrpt-pf-localization-dbgsym: 2.0.1-1
- ros-humble-mrpt-pointcloud-pipeline: 2.0.1-1
- ros-humble-mrpt-pointcloud-pipeline-dbgsym: 2.0.1-1
- ros-humble-mrpt-rawlog: 2.0.1-1
- ros-humble-mrpt-rawlog-dbgsym: 2.0.1-1
- ros-humble-mrpt-reactivenav2d: 2.0.1-1
- ros-humble-mrpt-reactivenav2d-dbgsym: 2.0.1-1
- ros-humble-mrpt-sensor-imu-taobotics: 0.2.0-1
- ros-humble-mrpt-sensor-imu-taobotics-dbgsym: 0.2.0-1
- ros-humble-mrpt-tutorials: 2.0.1-1
- ros-humble-ndt-omp: 0.0.0-1
- ros-humble-ndt-omp-dbgsym: 0.0.0-1
- ros-humble-off-highway-can: 0.6.1-1
- ros-humble-off-highway-can-dbgsym: 0.6.1-1
- ros-humble-off-highway-general-purpose-radar: 0.6.1-1
- ros-humble-off-highway-general-purpose-radar-dbgsym: 0.6.1-1
- ros-humble-off-highway-general-purpose-radar-msgs: 0.6.1-1
- ros-humble-off-highway-general-purpose-radar-msgs-dbgsym: 0.6.1-1
- ros-humble-off-highway-premium-radar-sample: 0.6.1-1
- ros-humble-off-highway-premium-radar-sample-dbgsym: 0.6.1-1
- ros-humble-off-highway-premium-radar-sample-msgs: 0.6.1-1
- ros-humble-off-highway-premium-radar-sample-msgs-dbgsym: 0.6.1-1
- ros-humble-off-highway-radar: 0.6.1-1
- ros-humble-off-highway-radar-dbgsym: 0.6.1-1
- ros-humble-off-highway-radar-msgs: 0.6.1-1
- ros-humble-off-highway-radar-msgs-dbgsym: 0.6.1-1
- ros-humble-off-highway-sensor-drivers: 0.6.1-1
- ros-humble-off-highway-sensor-drivers-examples: 0.6.1-1
- ros-humble-off-highway-sensor-drivers-examples-dbgsym: 0.6.1-1
- ros-humble-off-highway-uss: 0.6.1-1
- ros-humble-off-highway-uss-dbgsym: 0.6.1-1
- ros-humble-off-highway-uss-msgs: 0.6.1-1
- ros-humble-off-highway-uss-msgs-dbgsym: 0.6.1-1
- ros-humble-openeb-vendor: 1.1.1-1
- ros-humble-openeb-vendor-dbgsym: 1.1.1-1
- ros-humble-opennav-docking: 0.0.2-4
- ros-humble-opennav-docking-bt: 0.0.2-4
- ros-humble-opennav-docking-bt-dbgsym: 0.0.2-4
- ros-humble-opennav-docking-core: 0.0.2-4
- ros-humble-opennav-docking-dbgsym: 0.0.2-4
- ros-humble-opennav-docking-msgs: 0.0.2-4
- ros-humble-opennav-docking-msgs-dbgsym: 0.0.2-4
- ros-humble-py-binding-tools: 2.0.0-1
- ros-humble-py-binding-tools-dbgsym: 2.0.0-1
- ros-humble-qb-device: 4.1.3-1
- ros-humble-qb-device-bringup: 4.1.3-1
- ros-humble-qb-device-driver: 4.1.3-1
- ros-humble-qb-device-driver-dbgsym: 4.1.3-1
- ros-humble-qb-device-msgs: 4.1.3-1
- ros-humble-qb-device-msgs-dbgsym: 4.1.3-1
- ros-humble-qb-device-ros2-control: 4.1.3-1
- ros-humble-qb-device-ros2-control-dbgsym: 4.1.3-1
- ros-humble-qb-device-test-controllers: 4.1.3-1
- ros-humble-situational-graphs-msgs: 0.0.1-2
- ros-humble-situational-graphs-msgs-dbgsym: 0.0.1-2
- ros-humble-vimbax-camera: 1.0.2-1
- ros-humble-vimbax-camera-dbgsym: 1.0.2-1
- ros-humble-vimbax-camera-events: 1.0.2-1
- ros-humble-vimbax-camera-events-dbgsym: 1.0.2-1
- ros-humble-vimbax-camera-examples: 1.0.2-1
- ros-humble-vimbax-camera-examples-dbgsym: 1.0.2-1
- ros-humble-vimbax-camera-msgs: 1.0.2-1
- ros-humble-vimbax-camera-msgs-dbgsym: 1.0.2-1
- ros-humble-vmbc-interface: 1.0.2-1
Updated Packages [326]:
- ros-humble-ackermann-steering-controller: 2.34.0-1 → 2.35.0-1
- ros-humble-ackermann-steering-controller-dbgsym: 2.34.0-1 → 2.35.0-1
- ros-humble-actionlib-msgs: 4.2.3-1 → 4.2.4-1
- ros-humble-actionlib-msgs-dbgsym: 4.2.3-1 → 4.2.4-1
- ros-humble-admittance-controller: 2.34.0-1 → 2.35.0-1
- ros-humble-admittance-controller-dbgsym: 2.34.0-1 → 2.35.0-1
- ros-humble-apriltag-ros: 3.1.2-1 → 3.2.1-1
- ros-humble-apriltag-ros-dbgsym: 3.1.2-1 → 3.2.1-1
- ros-humble-aruco-opencv: 2.3.0-1 → 2.3.1-1
- ros-humble-aruco-opencv-dbgsym: 2.3.0-1 → 2.3.1-1
- ros-humble-aruco-opencv-msgs: 2.3.0-1 → 2.3.1-1
- ros-humble-aruco-opencv-msgs-dbgsym: 2.3.0-1 → 2.3.1-1
- ros-humble-behaviortree-cpp: 4.6.0-1 → 4.6.1-1
- ros-humble-behaviortree-cpp-dbgsym: 4.6.0-1 → 4.6.1-1
- ros-humble-bicycle-steering-controller: 2.34.0-1 → 2.35.0-1
- ros-humble-bicycle-steering-controller-dbgsym: 2.34.0-1 → 2.35.0-1
- ros-humble-clearpath-common: 0.2.8-1 → 0.2.9-1
- ros-humble-clearpath-config: 0.2.8-1 → 0.2.9-1
- ros-humble-clearpath-control: 0.2.8-1 → 0.2.9-1
- ros-humble-clearpath-customization: 0.2.8-1 → 0.2.9-1
- ros-humble-clearpath-description: 0.2.8-1 → 0.2.9-1
- ros-humble-clearpath-generator-common: 0.2.8-1 → 0.2.9-1
- ros-humble-clearpath-generator-gz: 0.2.4-1 → 0.2.5-1
- ros-humble-clearpath-gz: 0.2.4-1 → 0.2.5-1
- ros-humble-clearpath-mounts-description: 0.2.8-1 → 0.2.9-1
- ros-humble-clearpath-platform: 0.2.8-1 → 0.2.9-1
- ros-humble-clearpath-platform-dbgsym: 0.2.8-1 → 0.2.9-1
- ros-humble-clearpath-platform-description: 0.2.8-1 → 0.2.9-1
- ros-humble-clearpath-sensors-description: 0.2.8-1 → 0.2.9-1
- ros-humble-clearpath-simulator: 0.2.4-1 → 0.2.5-1
- ros-humble-common-interfaces: 4.2.3-1 → 4.2.4-1
- ros-humble-costmap-queue: 1.1.14-1 → 1.1.15-1
- ros-humble-costmap-queue-dbgsym: 1.1.14-1 → 1.1.15-1
- ros-humble-diagnostic-msgs: 4.2.3-1 → 4.2.4-1
- ros-humble-diagnostic-msgs-dbgsym: 4.2.3-1 → 4.2.4-1
- ros-humble-diff-drive-controller: 2.34.0-1 → 2.35.0-1
- ros-humble-diff-drive-controller-dbgsym: 2.34.0-1 → 2.35.0-1
- ros-humble-draco-point-cloud-transport: 1.0.10-1 → 1.0.11-1
- ros-humble-draco-point-cloud-transport-dbgsym: 1.0.10-1 → 1.0.11-1
- ros-humble-dwb-core: 1.1.14-1 → 1.1.15-1
- ros-humble-dwb-core-dbgsym: 1.1.14-1 → 1.1.15-1
- ros-humble-dwb-critics: 1.1.14-1 → 1.1.15-1
- ros-humble-dwb-critics-dbgsym: 1.1.14-1 → 1.1.15-1
- ros-humble-dwb-msgs: 1.1.14-1 → 1.1.15-1
- ros-humble-dwb-msgs-dbgsym: 1.1.14-1 → 1.1.15-1
- ros-humble-dwb-plugins: 1.1.14-1 → 1.1.15-1
- ros-humble-dwb-plugins-dbgsym: 1.1.14-1 → 1.1.15-1
- ros-humble-effort-controllers: 2.34.0-1 → 2.35.0-1
- ros-humble-effort-controllers-dbgsym: 2.34.0-1 → 2.35.0-1
- ros-humble-etsi-its-cam-coding: 2.0.1-1 → 2.0.2-1
- ros-humble-etsi-its-cam-coding-dbgsym: 2.0.1-1 → 2.0.2-1
- ros-humble-etsi-its-cam-conversion: 2.0.1-1 → 2.0.2-1
- ros-humble-etsi-its-cam-msgs: 2.0.1-1 → 2.0.2-1
- ros-humble-etsi-its-cam-msgs-dbgsym: 2.0.1-1 → 2.0.2-1
- ros-humble-etsi-its-coding: 2.0.1-1 → 2.0.2-1
- ros-humble-etsi-its-conversion: 2.0.1-1 → 2.0.2-1
- ros-humble-etsi-its-conversion-dbgsym: 2.0.1-1 → 2.0.2-1
- ros-humble-etsi-its-denm-coding: 2.0.1-1 → 2.0.2-1
- ros-humble-etsi-its-denm-coding-dbgsym: 2.0.1-1 → 2.0.2-1
- ros-humble-etsi-its-denm-conversion: 2.0.1-1 → 2.0.2-1
- ros-humble-etsi-its-denm-msgs: 2.0.1-1 → 2.0.2-1
- ros-humble-etsi-its-denm-msgs-dbgsym: 2.0.1-1 → 2.0.2-1
- ros-humble-etsi-its-messages: 2.0.1-1 → 2.0.2-1
- ros-humble-etsi-its-msgs: 2.0.1-1 → 2.0.2-1
- ros-humble-etsi-its-msgs-utils: 2.0.1-1 → 2.0.2-1
- ros-humble-etsi-its-primitives-conversion: 2.0.1-1 → 2.0.2-1
- ros-humble-etsi-its-rviz-plugins: 2.0.1-1 → 2.0.2-1
- ros-humble-etsi-its-rviz-plugins-dbgsym: 2.0.1-1 → 2.0.2-1
- ros-humble-event-camera-msgs: 1.1.5-1 → 1.1.6-1
- ros-humble-event-camera-msgs-dbgsym: 1.1.5-1 → 1.1.6-1
- ros-humble-event-camera-py: 1.1.4-1 → 1.1.6-1
- ros-humble-examples-tf2-py: 0.25.6-1 → 0.25.7-1
- ros-humble-fields2cover: 2.0.0-9 → 2.0.0-10
- ros-humble-fields2cover-dbgsym: 2.0.0-9 → 2.0.0-10
- ros-humble-flexbe-behavior-engine: 2.3.3-1 → 2.3.5-1
- ros-humble-flexbe-core: 2.3.3-1 → 2.3.5-1
- ros-humble-flexbe-input: 2.3.3-1 → 2.3.5-1
- ros-humble-flexbe-mirror: 2.3.3-1 → 2.3.5-1
- ros-humble-flexbe-msgs: 2.3.3-1 → 2.3.5-1
- ros-humble-flexbe-msgs-dbgsym: 2.3.3-1 → 2.3.5-1
- ros-humble-flexbe-onboard: 2.3.3-1 → 2.3.5-1
- ros-humble-flexbe-states: 2.3.3-1 → 2.3.5-1
- ros-humble-flexbe-testing: 2.3.3-1 → 2.3.5-1
- ros-humble-flexbe-widget: 2.3.3-1 → 2.3.5-1
- ros-humble-flir-camera-description: 2.1.16-1 → 2.1.17-1
- ros-humble-flir-camera-msgs: 2.1.16-1 → 2.1.17-1
- ros-humble-flir-camera-msgs-dbgsym: 2.1.16-1 → 2.1.17-1
- ros-humble-force-torque-sensor-broadcaster: 2.34.0-1 → 2.35.0-1
- ros-humble-force-torque-sensor-broadcaster-dbgsym: 2.34.0-1 → 2.35.0-1
- ros-humble-forward-command-controller: 2.34.0-1 → 2.35.0-1
- ros-humble-forward-command-controller-dbgsym: 2.34.0-1 → 2.35.0-1
- ros-humble-foxglove-bridge: 0.7.4-1 → 0.7.7-1
- ros-humble-foxglove-bridge-dbgsym: 0.7.4-1 → 0.7.7-1
- ros-humble-geometry-msgs: 4.2.3-1 → 4.2.4-1
- ros-humble-geometry-msgs-dbgsym: 4.2.3-1 → 4.2.4-1
- ros-humble-geometry2: 0.25.6-1 → 0.25.7-1
- ros-humble-gripper-controllers: 2.34.0-1 → 2.35.0-1
- ros-humble-gripper-controllers-dbgsym: 2.34.0-1 → 2.35.0-1
- ros-humble-imu-sensor-broadcaster: 2.34.0-1 → 2.35.0-1
- ros-humble-imu-sensor-broadcaster-dbgsym: 2.34.0-1 → 2.35.0-1
- ros-humble-joint-state-broadcaster: 2.34.0-1 → 2.35.0-1
- ros-humble-joint-state-broadcaster-dbgsym: 2.34.0-1 → 2.35.0-1
- ros-humble-joint-trajectory-controller: 2.34.0-1 → 2.35.0-1
- ros-humble-joint-trajectory-controller-dbgsym: 2.34.0-1 → 2.35.0-1
- ros-humble-kitti-metrics-eval: 1.0.4-1 → 1.0.5-1
- ros-humble-kitti-metrics-eval-dbgsym: 1.0.4-1 → 1.0.5-1
- ros-humble-libcaer-driver: 1.1.1-1 → 1.1.3-1
- ros-humble-libcaer-driver-dbgsym: 1.1.1-1 → 1.1.3-1
- ros-humble-microstrain-inertial-description: 4.2.0-1 → 4.3.0-1
- ros-humble-microstrain-inertial-driver: 4.2.0-1 → 4.3.0-1
- ros-humble-microstrain-inertial-driver-dbgsym: 4.2.0-1 → 4.3.0-1
- ros-humble-microstrain-inertial-examples: 4.2.0-1 → 4.3.0-1
- ros-humble-microstrain-inertial-msgs: 4.2.0-1 → 4.3.0-1
- ros-humble-microstrain-inertial-msgs-dbgsym: 4.2.0-1 → 4.3.0-1
- ros-humble-microstrain-inertial-rqt: 4.2.0-1 → 4.3.0-1
- ros-humble-mola: 1.0.4-1 → 1.0.5-1
- ros-humble-mola-bridge-ros2: 1.0.4-1 → 1.0.5-1
- ros-humble-mola-bridge-ros2-dbgsym: 1.0.4-1 → 1.0.5-1
- ros-humble-mola-demos: 1.0.4-1 → 1.0.5-1
- ros-humble-mola-imu-preintegration: 1.0.4-1 → 1.0.5-1
- ros-humble-mola-imu-preintegration-dbgsym: 1.0.4-1 → 1.0.5-1
- ros-humble-mola-input-euroc-dataset: 1.0.4-1 → 1.0.5-1
- ros-humble-mola-input-euroc-dataset-dbgsym: 1.0.4-1 → 1.0.5-1
- ros-humble-mola-input-kitti-dataset: 1.0.4-1 → 1.0.5-1
- ros-humble-mola-input-kitti-dataset-dbgsym: 1.0.4-1 → 1.0.5-1
- ros-humble-mola-input-kitti360-dataset: 1.0.4-1 → 1.0.5-1
- ros-humble-mola-input-kitti360-dataset-dbgsym: 1.0.4-1 → 1.0.5-1
- ros-humble-mola-input-mulran-dataset: 1.0.4-1 → 1.0.5-1
- ros-humble-mola-input-mulran-dataset-dbgsym: 1.0.4-1 → 1.0.5-1
- ros-humble-mola-input-paris-luco-dataset: 1.0.4-1 → 1.0.5-1
- ros-humble-mola-input-paris-luco-dataset-dbgsym: 1.0.4-1 → 1.0.5-1
- ros-humble-mola-input-rawlog: 1.0.4-1 → 1.0.5-1
- ros-humble-mola-input-rawlog-dbgsym: 1.0.4-1 → 1.0.5-1
- ros-humble-mola-input-rosbag2: 1.0.4-1 → 1.0.5-1
- ros-humble-mola-input-rosbag2-dbgsym: 1.0.4-1 → 1.0.5-1
- ros-humble-mola-kernel: 1.0.4-1 → 1.0.5-1
- ros-humble-mola-kernel-dbgsym: 1.0.4-1 → 1.0.5-1
- ros-humble-mola-launcher: 1.0.4-1 → 1.0.5-1
- ros-humble-mola-launcher-dbgsym: 1.0.4-1 → 1.0.5-1
- ros-humble-mola-metric-maps: 1.0.4-1 → 1.0.5-1
- ros-humble-mola-metric-maps-dbgsym: 1.0.4-1 → 1.0.5-1
- ros-humble-mola-navstate-fuse: 1.0.4-1 → 1.0.5-1
- ros-humble-mola-navstate-fuse-dbgsym: 1.0.4-1 → 1.0.5-1
- ros-humble-mola-pose-list: 1.0.4-1 → 1.0.5-1
- ros-humble-mola-pose-list-dbgsym: 1.0.4-1 → 1.0.5-1
- ros-humble-mola-relocalization: 1.0.4-1 → 1.0.5-1
- ros-humble-mola-relocalization-dbgsym: 1.0.4-1 → 1.0.5-1
- ros-humble-mola-test-datasets: 0.3.2-1 → 0.3.3-1
- ros-humble-mola-traj-tools: 1.0.4-1 → 1.0.5-1
- ros-humble-mola-traj-tools-dbgsym: 1.0.4-1 → 1.0.5-1
- ros-humble-mola-viz: 1.0.4-1 → 1.0.5-1
- ros-humble-mola-viz-dbgsym: 1.0.4-1 → 1.0.5-1
- ros-humble-mola-yaml: 1.0.4-1 → 1.0.5-1
- ros-humble-mola-yaml-dbgsym: 1.0.4-1 → 1.0.5-1
- ros-humble-mp2p-icp: 1.4.0-1 → 1.4.2-1
- ros-humble-mp2p-icp-dbgsym: 1.4.0-1 → 1.4.2-1
- ros-humble-mqtt-client: 2.2.1-1 → 2.3.0-1
- ros-humble-mqtt-client-dbgsym: 2.2.1-1 → 2.3.0-1
- ros-humble-mqtt-client-interfaces: 2.2.1-1 → 2.3.0-1
- ros-humble-mqtt-client-interfaces-dbgsym: 2.2.1-1 → 2.3.0-1
- ros-humble-mrpt-generic-sensor: 0.1.0-1 → 0.2.0-1
- ros-humble-mrpt-generic-sensor-dbgsym: 0.1.0-1 → 0.2.0-1
- ros-humble-mrpt-sensor-bumblebee-stereo: 0.1.0-1 → 0.2.0-1
- ros-humble-mrpt-sensor-bumblebee-stereo-dbgsym: 0.1.0-1 → 0.2.0-1
- ros-humble-mrpt-sensor-gnns-nmea: 0.1.0-1 → 0.2.0-1
- ros-humble-mrpt-sensor-gnns-nmea-dbgsym: 0.1.0-1 → 0.2.0-1
- ros-humble-mrpt-sensorlib: 0.1.0-1 → 0.2.0-1
- ros-humble-mrpt-sensors: 0.1.0-1 → 0.2.0-1
- ros-humble-mrpt2: 2.12.2-1 → 2.13.1-1
- ros-humble-mrpt2-dbgsym: 2.12.2-1 → 2.13.1-1
- ros-humble-nav-2d-msgs: 1.1.14-1 → 1.1.15-1
- ros-humble-nav-2d-msgs-dbgsym: 1.1.14-1 → 1.1.15-1
- ros-humble-nav-2d-utils: 1.1.14-1 → 1.1.15-1
- ros-humble-nav-2d-utils-dbgsym: 1.1.14-1 → 1.1.15-1
- ros-humble-nav-msgs: 4.2.3-1 → 4.2.4-1
- ros-humble-nav-msgs-dbgsym: 4.2.3-1 → 4.2.4-1
- ros-humble-nav2-amcl: 1.1.14-1 → 1.1.15-1
- ros-humble-nav2-amcl-dbgsym: 1.1.14-1 → 1.1.15-1
- ros-humble-nav2-behavior-tree: 1.1.14-1 → 1.1.15-1
- ros-humble-nav2-behavior-tree-dbgsym: 1.1.14-1 → 1.1.15-1
- ros-humble-nav2-behaviors: 1.1.14-1 → 1.1.15-1
- ros-humble-nav2-behaviors-dbgsym: 1.1.14-1 → 1.1.15-1
- ros-humble-nav2-bringup: 1.1.14-1 → 1.1.15-1
- ros-humble-nav2-bt-navigator: 1.1.14-1 → 1.1.15-1
- ros-humble-nav2-bt-navigator-dbgsym: 1.1.14-1 → 1.1.15-1
- ros-humble-nav2-collision-monitor: 1.1.14-1 → 1.1.15-1
- ros-humble-nav2-collision-monitor-dbgsym: 1.1.14-1 → 1.1.15-1
- ros-humble-nav2-common: 1.1.14-1 → 1.1.15-1
- ros-humble-nav2-constrained-smoother: 1.1.14-1 → 1.1.15-1
- ros-humble-nav2-constrained-smoother-dbgsym: 1.1.14-1 → 1.1.15-1
- ros-humble-nav2-controller: 1.1.14-1 → 1.1.15-1
- ros-humble-nav2-controller-dbgsym: 1.1.14-1 → 1.1.15-1
- ros-humble-nav2-core: 1.1.14-1 → 1.1.15-1
- ros-humble-nav2-costmap-2d: 1.1.14-1 → 1.1.15-1
- ros-humble-nav2-costmap-2d-dbgsym: 1.1.14-1 → 1.1.15-1
- ros-humble-nav2-dwb-controller: 1.1.14-1 → 1.1.15-1
- ros-humble-nav2-graceful-controller: 1.1.14-1 → 1.1.15-1
- ros-humble-nav2-graceful-controller-dbgsym: 1.1.14-1 → 1.1.15-1
- ros-humble-nav2-lifecycle-manager: 1.1.14-1 → 1.1.15-1
- ros-humble-nav2-lifecycle-manager-dbgsym: 1.1.14-1 → 1.1.15-1
- ros-humble-nav2-map-server: 1.1.14-1 → 1.1.15-1
- ros-humble-nav2-map-server-dbgsym: 1.1.14-1 → 1.1.15-1
- ros-humble-nav2-mppi-controller: 1.1.14-1 → 1.1.15-1
- ros-humble-nav2-mppi-controller-dbgsym: 1.1.14-1 → 1.1.15-1
- ros-humble-nav2-msgs: 1.1.14-1 → 1.1.15-1
- ros-humble-nav2-msgs-dbgsym: 1.1.14-1 → 1.1.15-1
- ros-humble-nav2-navfn-planner: 1.1.14-1 → 1.1.15-1
- ros-humble-nav2-navfn-planner-dbgsym: 1.1.14-1 → 1.1.15-1
- ros-humble-nav2-planner: 1.1.14-1 → 1.1.15-1
- ros-humble-nav2-planner-dbgsym: 1.1.14-1 → 1.1.15-1
- ros-humble-nav2-regulated-pure-pursuit-controller: 1.1.14-1 → 1.1.15-1
- ros-humble-nav2-regulated-pure-pursuit-controller-dbgsym: 1.1.14-1 → 1.1.15-1
- ros-humble-nav2-rotation-shim-controller: 1.1.14-1 → 1.1.15-1
- ros-humble-nav2-rotation-shim-controller-dbgsym: 1.1.14-1 → 1.1.15-1
- ros-humble-nav2-rviz-plugins: 1.1.14-1 → 1.1.15-1
- ros-humble-nav2-rviz-plugins-dbgsym: 1.1.14-1 → 1.1.15-1
- ros-humble-nav2-simple-commander: 1.1.14-1 → 1.1.15-1
- ros-humble-nav2-smac-planner: 1.1.14-1 → 1.1.15-1
- ros-humble-nav2-smac-planner-dbgsym: 1.1.14-1 → 1.1.15-1
- ros-humble-nav2-smoother: 1.1.14-1 → 1.1.15-1
- ros-humble-nav2-smoother-dbgsym: 1.1.14-1 → 1.1.15-1
- ros-humble-nav2-system-tests: 1.1.14-1 → 1.1.15-1
- ros-humble-nav2-system-tests-dbgsym: 1.1.14-1 → 1.1.15-1
- ros-humble-nav2-theta-star-planner: 1.1.14-1 → 1.1.15-1
- ros-humble-nav2-theta-star-planner-dbgsym: 1.1.14-1 → 1.1.15-1
- ros-humble-nav2-util: 1.1.14-1 → 1.1.15-1
- ros-humble-nav2-util-dbgsym: 1.1.14-1 → 1.1.15-1
- ros-humble-nav2-velocity-smoother: 1.1.14-1 → 1.1.15-1
- ros-humble-nav2-velocity-smoother-dbgsym: 1.1.14-1 → 1.1.15-1
- ros-humble-nav2-voxel-grid: 1.1.14-1 → 1.1.15-1
- ros-humble-nav2-voxel-grid-dbgsym: 1.1.14-1 → 1.1.15-1
- ros-humble-nav2-waypoint-follower: 1.1.14-1 → 1.1.15-1
- ros-humble-nav2-waypoint-follower-dbgsym: 1.1.14-1 → 1.1.15-1
- ros-humble-navigation2: 1.1.14-1 → 1.1.15-1
- ros-humble-pal-statistics: 2.2.3-1 → 2.2.4-1
- ros-humble-pal-statistics-dbgsym: 2.2.3-1 → 2.2.4-1
- ros-humble-pal-statistics-msgs: 2.2.3-1 → 2.2.4-1
- ros-humble-pal-statistics-msgs-dbgsym: 2.2.3-1 → 2.2.4-1
- ros-humble-point-cloud-interfaces: 1.0.10-1 → 1.0.11-1
- ros-humble-point-cloud-interfaces-dbgsym: 1.0.10-1 → 1.0.11-1
- ros-humble-point-cloud-transport: 1.0.17-1 → 1.0.18-1
- ros-humble-point-cloud-transport-dbgsym: 1.0.17-1 → 1.0.18-1
- ros-humble-point-cloud-transport-plugins: 1.0.10-1 → 1.0.11-1
- ros-humble-point-cloud-transport-py: 1.0.17-1 → 1.0.18-1
- ros-humble-position-controllers: 2.34.0-1 → 2.35.0-1
- ros-humble-position-controllers-dbgsym: 2.34.0-1 → 2.35.0-1
- ros-humble-psdk-interfaces: 1.1.1-1 → 1.3.0-1
- ros-humble-psdk-interfaces-dbgsym: 1.1.1-1 → 1.3.0-1
- ros-humble-psdk-wrapper: 1.1.1-1 → 1.3.0-1
- ros-humble-psdk-wrapper-dbgsym: 1.1.1-1 → 1.3.0-1
- ros-humble-range-sensor-broadcaster: 2.34.0-1 → 2.35.0-1
- ros-humble-range-sensor-broadcaster-dbgsym: 2.34.0-1 → 2.35.0-1
- ros-humble-realsense2-camera: 4.54.1-1 → 4.55.1-1
- ros-humble-realsense2-camera-dbgsym: 4.54.1-1 → 4.55.1-1
- ros-humble-realsense2-camera-msgs: 4.54.1-1 → 4.55.1-1
- ros-humble-realsense2-camera-msgs-dbgsym: 4.54.1-1 → 4.55.1-1
- ros-humble-realsense2-description: 4.54.1-1 → 4.55.1-1
- ros-humble-robotont-driver: 0.1.2-1 → 0.1.4-1
- ros-humble-robotont-driver-dbgsym: 0.1.2-1 → 0.1.4-1
- ros-humble-ros2-controllers: 2.34.0-1 → 2.35.0-1
- ros-humble-ros2-controllers-test-nodes: 2.34.0-1 → 2.35.0-1
- ros-humble-rqt-joint-trajectory-controller: 2.34.0-1 → 2.35.0-1
- ros-humble-sensor-msgs: 4.2.3-1 → 4.2.4-1
- ros-humble-sensor-msgs-dbgsym: 4.2.3-1 → 4.2.4-1
- ros-humble-sensor-msgs-py: 4.2.3-1 → 4.2.4-1
- ros-humble-septentrio-gnss-driver: 1.3.2-2 → 1.4.0-2
- ros-humble-septentrio-gnss-driver-dbgsym: 1.3.2-2 → 1.4.0-2
- ros-humble-shape-msgs: 4.2.3-1 → 4.2.4-1
- ros-humble-shape-msgs-dbgsym: 4.2.3-1 → 4.2.4-1
- ros-humble-slider-publisher: 2.3.0-1 → 2.4.0-1
- ros-humble-spinnaker-camera-driver: 2.1.16-1 → 2.1.17-1
- ros-humble-spinnaker-camera-driver-dbgsym: 2.1.16-1 → 2.1.17-1
- ros-humble-spinnaker-synchronized-camera-driver: 2.1.16-1 → 2.1.17-1
- ros-humble-spinnaker-synchronized-camera-driver-dbgsym: 2.1.16-1 → 2.1.17-1
- ros-humble-std-msgs: 4.2.3-1 → 4.2.4-1
- ros-humble-std-msgs-dbgsym: 4.2.3-1 → 4.2.4-1
- ros-humble-std-srvs: 4.2.3-1 → 4.2.4-1
- ros-humble-std-srvs-dbgsym: 4.2.3-1 → 4.2.4-1
- ros-humble-steering-controllers-library: 2.34.0-1 → 2.35.0-1
- ros-humble-steering-controllers-library-dbgsym: 2.34.0-1 → 2.35.0-1
- ros-humble-stereo-msgs: 4.2.3-1 → 4.2.4-1
- ros-humble-stereo-msgs-dbgsym: 4.2.3-1 → 4.2.4-1
- ros-humble-tf2: 0.25.6-1 → 0.25.7-1
- ros-humble-tf2-bullet: 0.25.6-1 → 0.25.7-1
- ros-humble-tf2-dbgsym: 0.25.6-1 → 0.25.7-1
- ros-humble-tf2-eigen: 0.25.6-1 → 0.25.7-1
- ros-humble-tf2-eigen-kdl: 0.25.6-1 → 0.25.7-1
- ros-humble-tf2-eigen-kdl-dbgsym: 0.25.6-1 → 0.25.7-1
- ros-humble-tf2-geometry-msgs: 0.25.6-1 → 0.25.7-1
- ros-humble-tf2-kdl: 0.25.6-1 → 0.25.7-1
- ros-humble-tf2-msgs: 0.25.6-1 → 0.25.7-1
- ros-humble-tf2-msgs-dbgsym: 0.25.6-1 → 0.25.7-1
- ros-humble-tf2-py: 0.25.6-1 → 0.25.7-1
- ros-humble-tf2-py-dbgsym: 0.25.6-1 → 0.25.7-1
- ros-humble-tf2-ros: 0.25.6-1 → 0.25.7-1
- ros-humble-tf2-ros-dbgsym: 0.25.6-1 → 0.25.7-1
- ros-humble-tf2-ros-py: 0.25.6-1 → 0.25.7-1
- ros-humble-tf2-sensor-msgs: 0.25.6-1 → 0.25.7-1
- ros-humble-tf2-tools: 0.25.6-1 → 0.25.7-1
- ros-humble-trajectory-msgs: 4.2.3-1 → 4.2.4-1
- ros-humble-trajectory-msgs-dbgsym: 4.2.3-1 → 4.2.4-1
- ros-humble-tricycle-controller: 2.34.0-1 → 2.35.0-1
- ros-humble-tricycle-controller-dbgsym: 2.34.0-1 → 2.35.0-1
- ros-humble-tricycle-steering-controller: 2.34.0-1 → 2.35.0-1
- ros-humble-tricycle-steering-controller-dbgsym: 2.34.0-1 → 2.35.0-1
- ros-humble-ur: 2.2.11-1 → 2.2.12-1
- ros-humble-ur-bringup: 2.2.11-1 → 2.2.12-1
- ros-humble-ur-calibration: 2.2.11-1 → 2.2.12-1
- ros-humble-ur-calibration-dbgsym: 2.2.11-1 → 2.2.12-1
- ros-humble-ur-client-library: 1.3.6-1 → 1.3.7-1
- ros-humble-ur-client-library-dbgsym: 1.3.6-1 → 1.3.7-1
- ros-humble-ur-controllers: 2.2.11-1 → 2.2.12-1
- ros-humble-ur-controllers-dbgsym: 2.2.11-1 → 2.2.12-1
- ros-humble-ur-dashboard-msgs: 2.2.11-1 → 2.2.12-1
- ros-humble-ur-dashboard-msgs-dbgsym: 2.2.11-1 → 2.2.12-1
- ros-humble-ur-moveit-config: 2.2.11-1 → 2.2.12-1
- ros-humble-ur-robot-driver: 2.2.11-1 → 2.2.12-1
- ros-humble-ur-robot-driver-dbgsym: 2.2.11-1 → 2.2.12-1
- ros-humble-velocity-controllers: 2.34.0-1 → 2.35.0-1
- ros-humble-velocity-controllers-dbgsym: 2.34.0-1 → 2.35.0-1
- ros-humble-visualization-msgs: 4.2.3-1 → 4.2.4-1
- ros-humble-visualization-msgs-dbgsym: 4.2.3-1 → 4.2.4-1
- ros-humble-zlib-point-cloud-transport: 1.0.10-1 → 1.0.11-1
- ros-humble-zlib-point-cloud-transport-dbgsym: 1.0.10-1 → 1.0.11-1
- ros-humble-zstd-point-cloud-transport: 1.0.10-1 → 1.0.11-1
- ros-humble-zstd-point-cloud-transport-dbgsym: 1.0.10-1 → 1.0.11-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:
- Alberto Tudela
- Alejandro Hernandez Cordero
- Alexey Merzlyakov
- Bence Magyar
- Berkay Karaman
- Bernd Pfrommer
- Bianca Bendris
- Brian Wilcox
- Carl Delsey
- Carlos Orduno
- Chris Lalancette
- Christian Rauch
- David V. Lu!!
- Davide Faconti
- Denis Štogl
- Dennis Langenkamp
- Felix Exner
- Fictionlab
- Franka Robotics GmbH
- Geoffrey Biggs
- Gerardo Puga
- Gergely Kovacs
- Gonzalo Mier
- Jean-Pierre Busch
- John Hurliman
- Jordan Palacios
- Jose Luis Blanco-Claraco
- Lennart Reiher
- LibRealSense ROS Team
- Luis Camero
- Markus Bader
- Martin Pecka
- Matej Vargovcik
- Michael Jeronimo
- Mohammad Haghighipanah
- Olivier Kermorgant
- Philipp Schillinger
- Rob Fisher
- Robert Haschke
- Robin Petereit
- Sarah Huber
- Stefan Laible
- Steve Macenski
- Tibor Dome
- Veiko Vunder
- hriday
- k.koide
- qb Support Team
1 post - 1 participant
![[WWW] [WWW]](./rostheme/img/moin-www.png)
ROS Discourse General: OGC GeoPose Package
Hi all,
I’ve been working on a geospatial standard - OGC GeoPose - a standard for encoding the real world position and orientation of a real or digital object in relation to the physical world in a shared geospatial frame of reference. We’re keen for this to be utilised by anyone that would find this useful, and there may be many who use ROS that may. You can see the encodings of the different message types at OGC GeoPose 1.0 Data Exchange Draft Standard. The Standard contains:
- A basic form with no configuration options for common use cases,
- An advanced form with more flexibility for more complex applications, and
- Composite GeoPose structures to support time series chain, and graph structures.
I’ve created ROS packages in the past but only locally. For publishing to the wider community once I’ve coded everything up as ogc_geopose_msgs, do I just go through the process detailed at First Time Release — ROS 2 Documentation: Foxy documentation?
Anyway, I’m quite keen to hear from anyone in the ROS community that would be interested in this, to get an idea of how they might use GeoPose, plus any comments, questions etc.
3 posts - 2 participants
![[WWW] [WWW]](./rostheme/img/moin-www.png)
ROS Discourse General: Next Medical Community group event theme announced!
After a great discussion at our first meeting, the next Medical Community group event is scheduled for 2024-07-02T16:00:00Z UTC.
There are lots of people interested in medical robotics companies being able to focus on their unique selling points, and not duplicating efforts on ROS reliability and certification. But a lot of work towards these goals already exists!
With the goal of knowledge sharing, we’re hosting “FYI, this exists” talks, a series of lightning talks from community members - be they service providers, vendors, individuals, or anyone else in the community with something to share. Sales pitches are welcome - if you’ve solved a problem others might be interested in, this is your platform to share your product/services with others!
Sign up to give your FYI as a quick 5min presentation here, no slides needed.
For inspiration, check/add to the wishlist of topics that the community wants to hear about. And make sure to join this mailing list to receive the calendar invite.
1 post - 1 participant
![[WWW] [WWW]](./rostheme/img/moin-www.png)
ROS Discourse General: ROSCon 2024 Registration Open, Workshops Announced
Hi Everyone,
It is time to start getting ready for ROSCon 2024 in Odense! I am happy to announce that the event registration page is now live, and I’ve updated the website with information about this year’s workshops. This year we’re changing the ROSCon schedule just a bit based on your feedback from ROSCon 2023.
Highlights:
- Double the Workshops: We’ve heard you loud and clear! After multiple years of ROSCon workshops selling out, we’ve decided to double the number of workshops we offer. This year, we’re offering seven workshops instead of the usual four, with three full-day and four half-day sessions to choose from.
- New “Day Zero” Events: We’re turning the ROSCon workshop day into a full-fledged event day. This year we’re setting aside dedicated time and space for birds of a feather (BoFs) sessions and community group meetings. We’ll release a sign up form for community group and BoF meeting slots a few months before ROSCon. We encourage you to start planning your sessions now!
- Please note: we’re only able to provide lunch for workshop attendees on day zero, everyone else will need to organize their own lunch sessions. There are lots of great locations near the conference center.
- Explore Odense: We’re partnering with the city of Odense to organize field trips, lab tours, and mixers before and after ROSCon 2024. More details on these activities will be announced soon. and we’ll post all the details on the ROSCon website. Plan to arrive to Denmark early and stay a few days after ROSCon.
- Full Talk Schedule Coming Soon: We’re wrapping the ROSCon CFP this week. Stay tuned for the complete ROSCon talk schedule sometime in July.
Don’t Miss Out!
Register early to secure your spot in the workshops you’re most interested in. We’re expecting some sessions to fill up quickly, and early bird rates won’t last forever! The last day for early registration is 2024-09-04T07:00:00Z UTC
We can’t wait to see you in Odense this October for another fantastic ROSCon!
2 posts - 1 participant
![[WWW] [WWW]](./rostheme/img/moin-www.png)
ROS Discourse General: Interoperability Interest Group June 6, 2024: Preview of the RMF Site Editor
In an effort to improve the usability and extensibility of RMF, we’ve been working on an experimental side project to create a whole new kind of editor. We’re getting close to launching its first release, and we thought it would be a good time to demonstrate its capabilities to the community.
This new editor, called the “Site Editor”, is foremost a replacement for the old traffic editor, so its core capabilities are:
- Edit 3D environments in sufficient detail for visualization and simulation
- Edit the robots present in the environment
- Edit the traffic rules for the robots
- Edit elevators (lifts) and doors that are present in the environment
But beyond that, the site editor opens up new possibilities that would not have been feasible with the old traffic editor. Since it was developed on top of the Bevy video game engine, it will be possible for downstream users to extend and customize its capabilities. Users could even develop and sell a commercial product built on top of it.
The site editor is cross-platform, being able to compile to a native desktop application on Linux, Windows, and macOS. It can even run in a web browser by compiling to Web Assembly. This opens up exciting opportunities to develop commercial applications locally even if you intend to deploy them to customers as a web service.
At this session, we will do a quick demonstration of using the site editor to partially build a hotel environment. If you’re familiar with using the old traffic editor, you’ll immediately see how much smoother the new workflow is. Feel free to bring in ideas for additional features that would make your workflows easier or more expressive.
3 posts - 2 participants
![[WWW] [WWW]](./rostheme/img/moin-www.png)
ROS Discourse General: New ROS Development Python Tools - ros_glint, ros_command and more
tl;dr: Five new Python libraries to help with ROS development are available now via pip
:
ros_glint
- a ROS 1 and 2 linter that evolved fromroscompile
ros_command
- command line tools previously announced hereros_introspect
- Pure Python version of the ROS 1 packageros_introspection
stylish_cmake_parser
- Parser for CMake files with the ability to retain the whitespace “style” after modifyingbetsy_ros
- A helper library with several ROS 1 & 2 “meta” operations, used by the above tools
Background
Back in 2015, I released a tool called roscompile with the goal of automating all the annoying meta-information in catkin packages. It largely stems from the fact that I’m bad at remembering to install
stuff in CMake and that I wrote so many pluginlib
plugins that it made sense to automate the process of writing the plugin definition files. I talked about it in my ROS World 2020 Lightning Talk.
But roscompile
only works for ROS 1. And rather than port it directly, and maintain two separate versions of the code, I made the questionable decision to make a new library that handled both ROS 1 and ROS 2, and was not a ROS package at all, but an independent python package.
The result is the above five Python packages, available via pip.
ros_glint
“Make your ROS code sparkle!”
Run glint_ros
in any folder with ROS packages (1 or 2) and it will suggest meta-data fixes interactively for you to apply.
- Add missing dependencies to
package.xml
- Replace the default license/author names
- Generate CMake code to build ROS messages, etc.
- Link your C++ libraries/executables with the proper libraries
- Make sure all the important package files are installed
- Clean up whitespace in many places
- Generate plugin definition files
- Generate
setup.py
files - Remove default settings from
.rviz
files - And much much more…
New features:
- Extensive tests in ROS 1 and 2 to avoid regressions
- Pre-commit hook definitions
I prioritized testing over documentation on this one, and I know I’ll need to circle around to that eventually.
ros_command
I announced ros_command over two years ago, and now its available as a pip package. Other new features in that time:
roslaunch
implemented- New command
rosexecute
for doing either a launch file or a node - Tab completion - This makes me feel like a real Python dev.
- The package completer works in
rosbuild
,roscd
,rosrun
androslaunch
- Executable completer works in
rosrun
androsexecute
- The launch file completer in
roslaunch
and fixing something that really grinds my gears, doesn’t suggest--print
and all the other args as completions when trying to remember the name of a launch file. - Also autocompletes launch file arguments.
- ROS interfaces (messages/services/actions) can be autocompleted starting with either the package name or the interface name.
- The package completer works in
- Also, the list of canonical emojis for each distro has been updated, although I’m struggling to figure out what to do for Kilted Kaiju. Maybe
Other Libraries
stylish_cmake_parser
also spun out ofroscompile
and is the only parser that can properly manipulate the “style” of the CMake in addition to the actual commands. Preliminary tests showed it successfully parsing 13351/13395 (99.67%) CMake files found in therosdistro
.ros_introspect
gives you the ability to classify all the files in a ROS package folder into different classes and then perform some operations on them. Used throughoutros_glint
betsy_ros
contains a bunch of Python functions that are needed for the other tools to work in ROS 1 or 2.get_workspace_root
determines the type and location of the current workspaceget_package_name_from_path
reads thepackage.xml
so you don’t have to.ROSInterface
is an independent class for ROS messages/services/actions.- and more…
Final Thoughts
- Please use these libraries as a jumping off point for your own ROS script hacking. I’ve thought about making a Github bot with it, and am still working on releasing an updated ROS 1 → ROS 2 conversion tool.
- Despite the polish and branding that I have given these, they are still “hobby” projects and are likely to have bugs that I encourage you to report. I’m not perfect.
- It is ridiculously easy to release pip packages once you get the hang of it. I have to credit the Scientific Python Library Development Guide as being a great starting resource. But also, there’s not actually any other human action required for getting stuff into pip, which I’ve found contrasts distinctly with the multiple rounds of PRs that you need to get stuff into the ROS distro.
- I’ve also made a Python DB wrapper based on my ros_metrics work and a Python Google API wrapper if you want to know where my “spare” developer cycles have been.
- I use my own tools daily, and I think they’re very useful. If you do too, please drop me a line. It makes the community feel more tight knit. Or, as the kids say, likeandsubscribe.
3 posts - 3 participants
![[WWW] [WWW]](./rostheme/img/moin-www.png)
ROS Discourse General: Open Robotics and Google Summer of Code 2024
We at Open Robotics are pleased to participate in another year of the Google Summer of Code (GSoC) project! We believe that mentorship and collaboration are crucial to our mission, and we are pleased to introduce this year’s contributors and mentors.
This year, five contributors are working on three different projects to improve aspects of Gazebo.
- Rakesh Vivekanandan, Helena Moyan, and Gaurav Kumar will work with Woensug Choi and Mabel Zhang on physics-based sonar simulation for underwater robots.
- Saurabh Kamat will work with Jose Luis Rivero to improve how users install Gazebo.
- Yaswanth Gonna will help Steve Peters develop an improved set of worlds for benchmarking physics engines.
Head over to our news post for more information on the projects and contributors, and if you see the contributors on Discourse, GitHub, or anywhere else, say hi and show them how welcome they are!
1 post - 1 participant
![[WWW] [WWW]](./rostheme/img/moin-www.png)
ROS Discourse General: Isaac ROS May update, 3.0 release adds more AI + robot manipulation
We are pleased to announce at Computex Taipei the release of Isaac ROS 3.0 with major updates including new packages, performance improvements and fixes.
The Isaac ROS update for ROS 2 Humble is available at github.com/NVIDIA-ISAAC-ROS, including packages for AI perception, image & LIDAR processing, navigation and adds:
- New! workflows for robot arms with Isaac Manipulator and AMR’s with Isaac Perceptor.
- New! package cuMotion for MoveIt 2 providing hardware accelerated motion planning with collision avoidance with obstacles.
- New! FoundationPose DNN for pose_estimation and tracking of unseen objects from a 3D model of the object.
- New! Multi-camera visual odometry providing robust visual tracking.
- New! Multi-camera nvBlox 3D reconstruction for costmaps used in motion planning with Nav2 and MoveIt 2.
- New! Segformer and SAM (Segment Anything) DNN packages for transformer based image_segmentation.
- New! data_recorder for multi-sensor data capture to ROSBag using MCAP and data_replayer for AI and perception development with time synchronized real sensor data at 500+ mega samples per second.
- New! Software for out of the box ROS 2 development with Nova Orin Developer Kit to stop losing time on system software and drivers.
- Updated ESS 4.0 stereo depth estimation DNN with improved accuracy, mobile robot and manipulation use cases with higher performance at >100 frames per second.
- Performance improvements with event based scheduling for NITROS.
- Bonus! tutorial for new Nav 2 docking
feature with mission_dispatch on the cloud connected over VDA5050 to mission_client.
- Update to Jetpack 6.0 with Ubuntu 22.04 with real-time optimizations and CUDA 12.2
- Bug fixes
nvBlox visualization of cuboid reconstruction with multi-camera perception to avoid obstacles missed by planar LIDAR.
FoundationPose detection on challenging objects with symmetry, reflections, specular highlights, and camera motion blur.
ESS 4.0, AI based depth estimation for manipulation and AMR applications.
Isaac ROS 3.0 is available now at github.com/NVIDIA-ISAAC-ROS and is part of our commitment to provide features and hardware acceleration for commercial deployment, development and research for autonomous robots.
Install pre-built Debian packages, leverage the Isaac ROS Dev container, or clone the repositories you need into your ROS workspace to build from source with colcon alongside your other ROS 2 packages. Please note that this release has been tested on the NVIDIA Jetson AGX Orin with JetPack 6.0. For more details see the release notes.
A minor hotfix will be released this June with the next major release in Oct at ROSCon 2024.
7 posts - 5 participants
![[WWW] [WWW]](./rostheme/img/moin-www.png)
ROS Discourse General: AI/ML Models & Framework Security Architecture Systems Community Meetings
Hello Everyone,
My name is Ronaldson Bellande. I am a PhD student and the Founder and CEO/CTO of a startup, as well as an executive in research organizations and a laboratory.
I am interested in starting a community group dedicated to AI/ML Model & Framework Security Architecture Systems. One critical issue we face is the lack of sufficient security for models; they are often deployed without adequate safeguards. My focus will be on enhancing security in AI and Machine Learning applications within robotics and related fields. We will address this challenge by testing and refining robust model structures and frameworks I have developed, as well as gathering feedback to ensure they can be accessed individually or separately for optimal protection.
I will also present the importance of this approach, discussing the benefits and drawbacks of various and my architecture systems for models.
I look forward to seeing who is interested in joining the community group. Please feel free to express your interest.
4 posts - 2 participants
![[WWW] [WWW]](./rostheme/img/moin-www.png)