diff --git a/CNAME b/CNAME new file mode 100644 index 00000000..d05f0c5f --- /dev/null +++ b/CNAME @@ -0,0 +1 @@ +planet.ros.org diff --git a/atom.xml b/atom.xml new file mode 100644 index 00000000..1e92a5e3 --- /dev/null +++ b/atom.xml @@ -0,0 +1,1791 @@ + + + Planet ROS + 2024-12-16T20:09:47Z + Venus + + Open Robotics + info@openrobotics.org + + http://planet.ros.org/atom.xml + + + + + discourse.ros.org-topic-41094 + + Is there a ROS 2 gazebo project for humanoids robots? +

Dear ROS community,

+

I was researching if there are ROS 2 Gazebo project for humanoid robots that would facilitate in learning robot locomotion and whole-body motion planning. I am looking towards humanoids similar to Unitree’s H1/H2.

+

A research scientist from ETH Zurich pointed me to the Issac Gym environment that comes with the assets for H1/H2. But as far as I understand, that simulation pipeline does not use any ROS, and is meant for RL like research.

+

The closet project I found was Unitree’s ROS 1 project GitHub - unitreerobotics/unitree_ros but it has not been updated for the newer ROS 2 and Gazebo.

+

Thank you for your time.

+

With best,
+Azmyin

+

2 posts - 2 participants

+

Read full topic

+ + 2024-12-15T05:41:56Z + 2024-12-15T05:41:56Z + + + azmyin12 + + + + 2024-12-16T20:09:45Z + + + + + discourse.ros.org-topic-41079 + + Opinion on companies still using ROS1 +

I would like to read what you think about taking a Job in companies who work extensively with ROS, but for one reason or another they are still in ROS1.
+On one hand I realize that ROS is just a framework and that a lot can still be done and learned.
+On the other, having worked for some years on both ROS and ROS2 I see the benefits of working with ROS2.
+So I am torn and would like to hear other voices on the matter.

+

6 posts - 4 participants

+

Read full topic

+ + 2024-12-13T22:48:13Z + 2024-12-13T22:48:13Z + + + iony_m + + + + 2024-12-16T20:09:44Z + + + + + discourse.ros.org-topic-41073 + + ROS News for the Week of December 9th, 2024 +

ROS News for the Week of December 9th, 2024

+
+

image

+:cn: :tada: Our first ever ROSCon in China happened in Shanghai over the weekend! We want to congratulate the organizers on orchestrating such an impressive event. You can find a recap of ROSCon China here.
+

+

May 2023 - Nov 2024

+ROS 2 Iron Irwini is now officially end-of-life. If you are currently using Iron please consider upgrading to Jazzy!

+
+

harp2
+Check out the HARP2 robot that was posted to the ROS Discord server yesterday. The developer’s website is full of really great posts that are worth checking out, especially on the topic of microROS.

+
+

poster-thumbnail

+The team behind TidyBot2 at Stanford and Princeton have open sourced the hardware for their robot. The robot supports a variety of arms and configurations allowing you to build a clone using hardware you may already have in the lab. See the docs for more details.

+
+

image

+This week ROS Industrial released a comprehensive list of depth cameras for robotics applications. Even if you don’t need a new depth camera I recommend bookmarking this website for future website.

+
+

image

+I want to send a big shout out @abaeyens for putting together this fantastic documentation on ROS 2 integration testing for docs.ros.org. :tada:

+

People often ask us how they can best contribute to the project. My recommendation is that when you run across something that feels not poorly documented take the time to summarize what you learned while figuring out how to solve the problem. That’s exactly what @abaeyens
+did in this case and the results are excellent.

+
+

Events

+ +

News

+ +

ROS

+ +

Got a minute? :alarm_clock:

+

All we want for Christmas are pull requests to the ROS 2 docs. :gift:

+

1 post - 1 participant

+

Read full topic

+ + 2024-12-13T20:21:44Z + 2024-12-13T20:21:44Z + + + Katherine_Scott + + + + 2024-12-16T20:09:44Z + + + + + discourse.ros.org-topic-41068 + + Call for “IFR’s Women in Robotics: 10 Women Shaping the Future of Robotics in 2025” is now open +

Call for “IFR’s Women in Robotics: 10 Women Shaping the Future of Robotics in 2025” is now open

+

The International Federation of Robotics (IFR) is looking for outstanding women in robotics

+

Dec 10, 2024 — IFR would like to highlight and honor Women in Robotics - in particular women in the robotics industry - and give them more visibility. IFR will select a list of 10 women to officially award as “IFR’s Women in Robotics: 10 Women Shaping the Future of Robotics” in 2025.

+

+

IFR decided to give women in robotics more visibility and acknowledgment. This should inspire girls and young women to pursue a career in STEM subjects or robotics and will also help companies to reach gender equality and overcome shortage of staff.

+

IFR would like to highlight and honor Women in Robotics - in particular women in the robotics industry - and give them more visibility.
+IFR will select a list of 10 women to officially award as “IFR’s Women in Robotics: 10 Women Shaping the Future of Robotics” in 2025.

+

IRF is in particular looking for women that have either a proven track record in robotics, stand out as industry leader or women with a proven activity in encouraging young people to go into STEM or that somehow support females in robotics.

+

Deadline for submission is January 31st, 2025.

+

How to submit a suggestion

+

Send an email to secretariat@ifr.org
+include a short bio and a description of what makes her noteworthy or particular with respect to our described scope
+add her full name, affiliation, country, contact details and a photo

+

Selection criteria:

+
    +
  • The suggested women needs to be active in the robotics industry
    • +
  • IFR will select at least one per continent,
    • +
  • but a maximum of one woman per company,
    • +
  • consider different company sizes (large, medium, small)
    • +
  • consider different company scope (Robot supplier IR, SR, component supplier, integrator) and
    • +
  • consider different levels of hierarchy (C-level, intermediate, lower level)
    • +
  • Proven track record in robotics / stand out as industry leader
    • +
  • Proven activity in encouraging young people to go into STEM or that somehow support females in robotics
    • +
+

Publication of results will be on International Women’s Day - March 8th, 2025.

+

IFR’s 2024 Women in Robotics

+

Learn more on why gender balance is beneficial for economies

+ +

1 post - 1 participant

+

Read full topic

+ + 2024-12-13T08:38:12Z + 2024-12-13T08:38:12Z + + + ThiloZimmermann + + + + 2024-12-16T20:09:44Z + + + + + discourse.ros.org-topic-41063 + + REUSE compatibility vs multi-package repo +

Hi. I’ve started trying to have my repos REUSE-compliant.

+

It seems that single-package repos can easily be turned into REUSE-compliant by adding all the SPDX comments to files, moving the top-level LICENSE file into LICENSES/BSD-3-Clause.txt and specifying <license file="LICENSES/BSD-3-Clause.txt">BSD</license> in package.xml.

+

However, if I want to do the same for a multi-package repo, then the LICENSES folder has to be a top-level one, i.e. at the same level as are the packages (that is a REUSE requirement). At the same time, I’d like to not have to copy all licenses to each package - as it’s best if each is stored only once. However, if I put <license file="../LICENSES/BSD-3-Clause.txt"> in package.xml, then bloom-release fails not being able to find the license file. That’s because it builds each package from the repo in a separate directory that is moved outside the repo.

+

I don’t see a clean solution how to satisfy both REUSE and bloom (except not adding the file= attribute, but I’d like to keep it). My current dirty workaround is to just copy the license file into the root of each subpackage. That’s not nice, but it does the job.

+

Does anybody know of a cleaner solution? I think it would be very nice if ROS deployment process would be compatible with REUSE.

+

5 posts - 3 participants

+

Read full topic

+ + 2024-12-12T15:19:10Z + 2024-12-12T15:19:10Z + + + peci1 + + + + 2024-12-16T20:09:44Z + + + + + discourse.ros.org-topic-41048 + + Optimizations cpp ROS2 node. colcon build +

I’ve been using ROS2 for a year. Maybe previously you guys talked about this. However I’ve done experimental tests about the optimization C++ code ROS2 node and wrote a simple node.

+
#include "rclcpp/rclcpp.hpp"
+
+class HelloWorldNode : public rclcpp::Node
+{
+public:
+    HelloWorldNode() : Node("hello_world_node")
+    {
+        RCLCPP_INFO(this->get_logger(), "Hello, World! This is a ROS2 node.");
+    }
+};
+
+int main(int argc, char **argv)
+{
+    rclcpp::init(argc, argv);
+    rclcpp::spin(std::make_shared<HelloWorldNode>());
+    rclcpp::shutdown();
+    return 0;
+}
+
+
+

Then by simply building the above code by using

+
colcon build
+
+

I got hello_node then explored assemble code

+
objdump -d <path>/hello_node > hello_node.asm
+
+

got around 5000 lines of instruction code in hello_node.asm, it seems like it didn’t do any optimization to the code. Then run the following command

+
colcon build --cmake-args -DCMAKE_BUILD_TYPE=Release
+///alternative
+colcon build --cmake-args -DCMAKE_CXX_FLAGS="-O3 -march=native"
+
+
+

then looked number instructions lines the number dramatically decreased from 5000 to 1700. the number of instruction lines in assemble doesn’t always mean it’s optimized yet it’s good factor.

+

Screenshot from 2024-12-11 16-24-11

+

“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”"
+simple by adding “set(CMAKE_BUILD_TYPE Release)” to your CMakeLists.txt is enough. then you can simply use colcon build.
+Optimizations flags

+

8 posts - 7 participants

+

Read full topic

+ + 2024-12-11T08:32:38Z + 2024-12-11T08:32:38Z + + + Dony + + + + 2024-12-16T20:09:44Z + + + + + discourse.ros.org-topic-41044 + + :checkered_flag: Gazebo Garden officially end-of-life [x-post Gazebo Sim Community] +

Original Post

+

Dear ROS Community,

+

Gazebo Garden has reached end-of-life (EOL) as of November, 2024. Garden was the seventh major release of Gazebo and was supported for two years (non-LTS). It was the first release where Ignition was renamed Gazebo. It also introduced various exciting features, including custom shader plugins, Reset API, DEM support, lunar and custom surface coordinates, glTF and GLB mesh support, and an acoustic communication plugin, just to name a few. See the entire list of features on the Release Features page.

+

We recommend all Garden users migrate to a supported release as soon as possible, such as Harmonic (LTS) or Ionic, which are paired with ROS Jazzy and Rolling (Kilted once released) respectively. Migrating to either Harmonic or Ionic should be fairly smooth, however, be sure to check the release highlights for Harmonic and Ionic in addition to checking each Gazebo library’s migration guide.

+

As part of the Garden EOL, the following Gazebo libraries have also reached end-of-life. Their latest released binaries will remain available at http://packages.osrfoundation.org/, but no more fixes or releases will be made.

+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Library major versionFinal release
gz-fuel-tools88.2.0
gz-sim77.9.0
gz-gui77.2.2
gz-launch66.2.0
gz-msgs99.5.1
gz-physics66.7.0
gz-rendering77.5.0
gz-sensors77.3.1
gz-transport1212.2.2
sdformat1313.9.0
+

We sincerely thank all contributors to all libraries in Garden :pray:

+

What does End of Life Mean?

+

Users often ask us, “what does end of life mean?” To put it briefly, end of life means that the Gazebo team will no longer support that particular Gazebo release. In practical terms, this means that we will no longer be providing the following for Gazebo Garden:

+
    +
  • New features or capabilities
    • +
  • Security updates
    • +
  • Bug fixes, patches or support
    • +
  • Updated binaries
    • +
+

It is also worth noting the things that won’t change after Gazebo Garden goes end of life:

+
    +
  • Gazebo Garden binaries will not suddenly disappear
    • +
  • Users will not need to migrate immediately, but they should migrate as soon as possible
    • +
+

:gazebo: Gazebo Dev Team :gazebo:

+

1 post - 1 participant

+

Read full topic

+ + 2024-12-10T23:14:24Z + 2024-12-10T23:14:24Z + + + azeey + + + + 2024-12-16T20:09:44Z + + + + + discourse.ros.org-topic-41032 + + How important is ROS when searching for a job? +

I have made an analysis of almost 2.000 jobs in LinkedIn and found out how relevant is ROS for getting a job as a robotics software developer. I included other interesting data about what matters for companies posting robotics jobs.

+

Check all that data in this video: https://youtu.be/wDeVNsD73A4?si=wcD3F1FizuJ52K3e

+

Podcast-video-2024-Ricardo-Tellez-the-truth-about-ROS-jobs

+

1 post - 1 participant

+

Read full topic

+ + 2024-12-10T08:43:25Z + 2024-12-10T08:43:25Z + + + ricardotellez + + + + 2024-12-16T20:09:44Z + + + + + discourse.ros.org-topic-41031 + + Iron Irwini is End-of-Life +

Dear ROS Community,

+

It is bitter-sweet to announce that ROS 2 Iron Irwini is now end-of-life.

+

ROS 2 Iron Irwini

+

Iron Irwini was released on May 23rd 2023 and marked the ninth distribution of ROS 2. Despite being a non-LTS release, it was feature packed (see more).

+

Over the past year and half, there have been 40 distro syncs and 7 patch releases that cumulatively brought thousands of packages and updates to the community.

+

The last patch and sync (tagged iron/2024-12-04) brought 6 new packages and 320 updates.

+Expand for details of the final sync (click for more details) +

The distribution has been marked end-of-life across docs.ros.org, index.ros.org and rosdistro. CI and Buildfarm jobs have been disabled and will be deleted after a month assuming no issues crop up. The final snapshot of the distribution has been uploaded to snapshots.ros.org. If you are currently using Iron, please switch to Jazzy Jalisco which is the latest LTS release. The transition should be very smooth.

+

It has been a great privilege of mine to serve as the ROS Boss for Iron Irwini especially given that Steve Irwin was my childhood hero. A big thank you to all ROS maintainers and community members for making Iron Irwini such a successful release! :iron: :irwini:

+

-Yadu

+

2 posts - 2 participants

+

Read full topic

+ + 2024-12-10T07:36:47Z + 2024-12-10T07:36:47Z + + + Yadunund + + + + 2024-12-16T20:09:44Z + + + + + discourse.ros.org-topic-41021 + + Guest Talk by Tomoya Fujita - Cloud Robotics WG Meeting 2024-12-16 +

Please come and join us for this coming meeting at 1700-1800 UTC on Monday 16th December 2024, where Tomoya Fujita will be talking about Robotics Platforms empowered by Cloud-Native Technologies.

+

Tomoya is a software engineer, contributor to ROS2 core, and well-respected community builder. In this session, he will talk about a range of Cloud-Native Technologies he has worked on, and their relevance to robotics. In particular, Tomoya has done a great deal of work on KubeEdge, a platform built on Kubernetes that can be used to deploy software to robots as if they are Kubernetes clusters. Some resources from his talk includes:

+ +

Tomoya also plans to leave time to discuss Cloud Robotics with the group, particularly the problems that people are having with Cloud Robotics.

+

Last meeting, we worked through a workshop for Eclipse Zenoh to test its capabilities and ease of setup. If you’re interested to see our progress, please check the meeting recording.

+

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

+

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

+

Hopefully we will see you there!

+

1 post - 1 participant

+

Read full topic

+ + 2024-12-09T14:58:15Z + 2024-12-09T14:58:15Z + + + mikelikesrobots + + + + 2024-12-16T20:09:44Z + + + + + discourse.ros.org-topic-41015 + + Robotics engineers are in high demand — but what is the job really like? +

Robotics engineers are in high demand — but what is the job really like?

+ +

2 posts - 1 participant

+

Read full topic

+ + 2024-12-08T23:32:15Z + 2024-12-08T23:32:15Z + + + ruffsl + + + + 2024-12-16T20:09:44Z + + + + + discourse.ros.org-topic-40997 + + ROS News for the Week of December 2nd, 2024 +

ROS News for the Week of December 2nd, 2024

+

GeCwHKiX0AAHleo
Gd-rDnlW4AAsP38

+ROSCon Germany and ROSCon India were both this week! It was really exciting to see two ROS events happening concurrently on two different parts of the globe. We want to congratulate the organizers and attendees on putting together fantastic events.

+

+

ROSCon_China_2024

+But wait, there’s more! Our first ever ROSCon China in Shanghai is about to kick off in about four or five hours.

+
+

9cqsf8

+While we’re welcoming so many new friends to the ROS community we’re also getting ready to say farewell to ROS 1 Noetic, Gazebo Classic, Gazebo Citadel, and ROS 2 Iron Irwini.

+
+

SGDecROSMeetup

+We have two ROS Meetups planned for 2024-12-12. One meetup in Singapore and another one in Barcelona Spain

+
+

Thanksgiving

+If you are in a giving mood this holiday season we are currently running a donation campaign for the OSRF. We’ve made it possible for you to earmark your donation for particular OSRF projects like the ROS Build Farm, the ROS Documentation, and our educational outreach initiatives.

+
+

Aug24GCM (1)

+At last week’s Gazebo Community Meeting we met multiple competitors from the NASA SpaceROS Summer Sprint Challenge. The results are absolutely amazing and are all open source! We recommend you check it out.

+

Events

+ +

News

+ +

ROS

+ +

Got a Minute? :alarm_clock:

+

We would really appreciate it if you took ten minutes to answer just one ROS question on Robotics Stack Exchange.

+

1 post - 1 participant

+

Read full topic

+ + 2024-12-06T20:59:45Z + 2024-12-06T20:59:45Z + + + Katherine_Scott + + + + 2024-12-16T20:09:44Z + + + + + discourse.ros.org-topic-40996 + + rmw_iceoryx2 v0.1.0 release +

Hi all,

+

orecham here, one of the committers from the eclipse-iceoryx project.

+

I’m pleased to announce the alpha release of rmw_iceoryx2, compatible with ROS 2 rolling and available at: GitHub - ekxide/rmw_iceoryx2: ROS 2 RMW implementation for iceoryx2

+

Why yet another RMW? We have the following goals for rmw_iceoryx2:

+
    +
  1. Bring the high-performance zero-copy shared-memory communication offered by iceoryx2 to ROS 2 applications
    2. +
  2. Provide a unique option for reducing safety certification effort of ROS 2 applications with safety-critical use-cases
    3. +
+

Rather than require the entire ROS 2 stack be certified (e.g. for ASIL-D), rmw_iceoryx2 offers an alternative through interoperability between ROS 2 and iceoryx2 applications. This allows the freedom for porting safety-critical components that require certification to iceoryx2 (which is designed for certification) while still participating in the ROS 2 ecosystem.

+

Current State

+

With this first alpha release, there is still some work to do and polish to be made. Not all features are yet available and existing ones need thorough real-world validation. Most notably, support for message serialization is not yet available nor service-client communication (waiting on some features to be completed in iceoryx2). Lack of serialization support means that rmw_iceoryx2 can currently only work with self-contained message types, however, this will be one of the first limitations to address next.

+

Furthermore, only intra-host communication is currently possible. We have plans to introduce host-to-host capabilities in the near future by leveraging existing host-to-host-capable middlewares. Some more info about this is available in the README.

+

Performance

+

The current performance_test results are as follow. There is still quite a bit of room for improvement compared to raw iceoryx2:

+

v0.1.0

+

Contributing and Feedback

+

We look forward to your feedback! Input from real-world application configurations will be invaluable for bringing rmw_iceoryx2 to stability. Additionally, insights from those experienced with RMW implementations would greatly help improve quality. The current state was achieved using only the information available in the RMW documentation, thus there may be some edge-cases known to veterans which are not properly addressed.

+

For those who have the capacity to get involved with implementation, we welcome all contributions! We will provide as much support as needed to those who are interested.

+

Thanks for reading!
+Cheers

+

1 post - 1 participant

+

Read full topic

+ + 2024-12-06T20:29:44Z + 2024-12-06T20:29:44Z + + + orecham + + + + 2024-12-16T20:09:44Z + + + + + discourse.ros.org-topic-40995 + + New Packages for Noetic 2024-12-06 +

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

+

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

+

Package Updates for ROS Noetic

+

Added Packages [2]:

+ +

Updated Packages [46]:

+
    +
  • ros-noetic-ess-imu-driver: 2.0.1-1 → 2.0.2-1
    • +
  • ros-noetic-etsi-its-cam-coding: 2.3.0-1 → 2.4.0-1
    • +
  • ros-noetic-etsi-its-cam-conversion: 2.3.0-1 → 2.4.0-1
    • +
  • ros-noetic-etsi-its-cam-msgs: 2.3.0-1 → 2.4.0-1
    • +
  • ros-noetic-etsi-its-cam-ts-coding: 2.3.0-1 → 2.4.0-1
    • +
  • ros-noetic-etsi-its-cam-ts-conversion: 2.3.0-1 → 2.4.0-1
    • +
  • ros-noetic-etsi-its-cam-ts-msgs: 2.3.0-1 → 2.4.0-1
    • +
  • ros-noetic-etsi-its-coding: 2.3.0-1 → 2.4.0-1
    • +
  • ros-noetic-etsi-its-conversion: 2.3.0-1 → 2.4.0-1
    • +
  • ros-noetic-etsi-its-cpm-ts-coding: 2.3.0-1 → 2.4.0-1
    • +
  • ros-noetic-etsi-its-cpm-ts-conversion: 2.3.0-1 → 2.4.0-1
    • +
  • ros-noetic-etsi-its-cpm-ts-msgs: 2.3.0-1 → 2.4.0-1
    • +
  • ros-noetic-etsi-its-denm-coding: 2.3.0-1 → 2.4.0-1
    • +
  • ros-noetic-etsi-its-denm-conversion: 2.3.0-1 → 2.4.0-1
    • +
  • ros-noetic-etsi-its-denm-msgs: 2.3.0-1 → 2.4.0-1
    • +
  • ros-noetic-etsi-its-messages: 2.3.0-1 → 2.4.0-1
    • +
  • ros-noetic-etsi-its-msgs: 2.3.0-1 → 2.4.0-1
    • +
  • ros-noetic-etsi-its-msgs-utils: 2.3.0-1 → 2.4.0-1
    • +
  • ros-noetic-etsi-its-primitives-conversion: 2.3.0-1 → 2.4.0-1
    • +
  • ros-noetic-etsi-its-rviz-plugins: 2.3.0-1 → 2.4.0-1
    • +
  • ros-noetic-etsi-its-vam-ts-coding: 2.3.0-1 → 2.4.0-1
    • +
  • ros-noetic-etsi-its-vam-ts-conversion: 2.3.0-1 → 2.4.0-1
    • +
  • ros-noetic-etsi-its-vam-ts-msgs: 2.3.0-1 → 2.4.0-1
    • +
  • ros-noetic-foxglove-bridge: 0.7.10-1 → 0.8.1-1
    • +
  • ros-noetic-inorbit-republisher: 0.3.0-1 → 0.3.2-1
    • +
  • ros-noetic-nodelet: 1.11.0-2 → 1.11.1-1
    • +
  • ros-noetic-nodelet-core: 1.11.0-2 → 1.11.1-1
    • +
  • ros-noetic-nodelet-topic-tools: 1.11.0-2 → 1.11.1-1
    • +
  • ros-noetic-rc-reason-clients: 0.3.1-1 → 0.4.0-2
    • +
  • ros-noetic-rc-reason-msgs: 0.3.1-1 → 0.4.0-2
    • +
  • ros-noetic-rtabmap: 0.21.6-1 → 0.21.9-1
    • +
  • ros-noetic-rtabmap-conversions: 0.21.5-1 → 0.21.9-1
    • +
  • ros-noetic-rtabmap-costmap-plugins: 0.21.5-1 → 0.21.9-1
    • +
  • ros-noetic-rtabmap-demos: 0.21.5-1 → 0.21.9-1
    • +
  • ros-noetic-rtabmap-examples: 0.21.5-1 → 0.21.9-1
    • +
  • ros-noetic-rtabmap-launch: 0.21.5-1 → 0.21.9-1
    • +
  • ros-noetic-rtabmap-legacy: 0.21.5-1 → 0.21.9-1
    • +
  • ros-noetic-rtabmap-msgs: 0.21.5-1 → 0.21.9-1
    • +
  • ros-noetic-rtabmap-odom: 0.21.5-1 → 0.21.9-1
    • +
  • ros-noetic-rtabmap-python: 0.21.5-1 → 0.21.9-1
    • +
  • ros-noetic-rtabmap-ros: 0.21.5-1 → 0.21.9-1
    • +
  • ros-noetic-rtabmap-rviz-plugins: 0.21.5-1 → 0.21.9-1
    • +
  • ros-noetic-rtabmap-slam: 0.21.5-1 → 0.21.9-1
    • +
  • ros-noetic-rtabmap-sync: 0.21.5-1 → 0.21.9-1
    • +
  • ros-noetic-rtabmap-util: 0.21.5-1 → 0.21.9-1
    • +
  • ros-noetic-rtabmap-viz: 0.21.5-1 → 0.21.9-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:

+
    +
  • Felix Ruess
    • +
  • Geoffrey Biggs
    • +
  • Hans-Joachim Krauch
    • +
  • InOrbit
    • +
  • Jean-Pierre Busch
    • +
  • Marc Alban
    • +
  • Martin Pecka
    • +
  • Mathieu Labbe
    • +
  • Raymond Chow
    • +
+

2 posts - 2 participants

+

Read full topic

+ + 2024-12-06T18:09:43Z + 2024-12-06T18:09:43Z + + + sloretz + + + + 2024-12-16T20:09:44Z + + + + + discourse.ros.org-topic-40986 + + Open-RMF PMC Timing Change for 2024-12-17 +

Due to a one-time scheduling conflict, the Open-RMF Project Management Committee session that is normally scheduled for 2024-12-17T01:00:00Z UTC will instead take place one hour later at 2024-12-17T02:00:00Z UTC. This change is reflected in the official OSRF events calendar.

+

Sessions will return to the normal time afterwards.

+

1 post - 1 participant

+

Read full topic

+ + 2024-12-06T08:46:33Z + 2024-12-06T08:46:33Z + + + grey + + + + 2024-12-16T20:09:44Z + + + + + discourse.ros.org-topic-40976 + + New packages and patch release for Humble Hawksbill 2024-12-05 +

We’re happy to announce a new Humble release!

+

This sync brings several new packages and some updates to ROS 2 core packages. (I haven’t included the project board for patch info because there was nothing on it.)

+

Package Updates for Humble

+

Added Packages [34]:

+
    +
  • ros-humble-adi-3dtof-image-stitching: 2.1.0-1
    • +
  • ros-humble-adi-3dtof-image-stitching-dbgsym: 2.1.0-1
    • +
  • ros-humble-axis-camera: 2.0.3-1
    • +
  • ros-humble-axis-description: 2.0.3-1
    • +
  • ros-humble-axis-msgs: 2.0.3-1
    • +
  • ros-humble-axis-msgs-dbgsym: 2.0.3-1
    • +
  • ros-humble-camera-info-manager-py: 3.1.10-1
    • +
  • ros-humble-clearpath-motor-msgs: 1.0.1-1
    • +
  • ros-humble-clearpath-motor-msgs-dbgsym: 1.0.1-1
    • +
  • ros-humble-clearpath-ros2-socketcan-interface: 1.0.0-1
    • +
  • ros-humble-clearpath-ros2-socketcan-interface-dbgsym: 1.0.0-1
    • +
  • ros-humble-dual-laser-merger: 0.1.1-1
    • +
  • ros-humble-dual-laser-merger-dbgsym: 0.1.1-1
    • +
  • ros-humble-hatchbed-common: 0.1.1-1
    • +
  • ros-humble-hri-face-body-matcher: 2.1.0-1
    • +
  • ros-humble-hri-face-body-matcher-dbgsym: 2.1.0-1
    • +
  • ros-humble-hri-privacy-msgs: 1.2.0-1
    • +
  • ros-humble-hri-privacy-msgs-dbgsym: 1.2.0-1
    • +
  • ros-humble-jacro: 0.2.0-1
    • +
  • ros-humble-laser-segmentation: 3.0.2-1
    • +
  • ros-humble-laser-segmentation-dbgsym: 3.0.2-1
    • +
  • ros-humble-log-view: 0.2.5-1
    • +
  • ros-humble-log-view-dbgsym: 0.2.5-1
    • +
  • ros-humble-pose-broadcaster: 2.38.0-1
    • +
  • ros-humble-pose-broadcaster-dbgsym: 2.38.0-1
    • +
  • ros-humble-ptz-action-server-msgs: 2.0.3-1
    • +
  • ros-humble-ptz-action-server-msgs-dbgsym: 2.0.3-1
    • +
  • ros-humble-rosbag2-to-video: 1.0.1-1
    • +
  • ros-humble-simple-grasping: 0.5.0-1
    • +
  • ros-humble-simple-grasping-dbgsym: 0.5.0-1
    • +
  • ros-humble-slg-msgs: 3.9.1-1
    • +
  • ros-humble-slg-msgs-dbgsym: 3.9.1-1
    • +
  • ros-humble-zed-msgs: 4.2.2-1
    • +
  • ros-humble-zed-msgs-dbgsym: 4.2.2-1
    • +
+

Updated Packages [580]:

+
    +
  • ros-humble-ackermann-steering-controller: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-ackermann-steering-controller-dbgsym: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-adi-tmcl: 2.0.0-1 → 2.0.3-2
    • +
  • ros-humble-adi-tmcl-dbgsym: 2.0.0-1 → 2.0.3-2
    • +
  • ros-humble-admittance-controller: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-admittance-controller-dbgsym: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-ament-cmake: 1.3.10-1 → 1.3.11-1
    • +
  • ros-humble-ament-cmake-auto: 1.3.10-1 → 1.3.11-1
    • +
  • ros-humble-ament-cmake-core: 1.3.10-1 → 1.3.11-1
    • +
  • ros-humble-ament-cmake-export-definitions: 1.3.10-1 → 1.3.11-1
    • +
  • ros-humble-ament-cmake-export-dependencies: 1.3.10-1 → 1.3.11-1
    • +
  • ros-humble-ament-cmake-export-include-directories: 1.3.10-1 → 1.3.11-1
    • +
  • ros-humble-ament-cmake-export-interfaces: 1.3.10-1 → 1.3.11-1
    • +
  • ros-humble-ament-cmake-export-libraries: 1.3.10-1 → 1.3.11-1
    • +
  • ros-humble-ament-cmake-export-link-flags: 1.3.10-1 → 1.3.11-1
    • +
  • ros-humble-ament-cmake-export-targets: 1.3.10-1 → 1.3.11-1
    • +
  • ros-humble-ament-cmake-gen-version-h: 1.3.10-1 → 1.3.11-1
    • +
  • ros-humble-ament-cmake-gmock: 1.3.10-1 → 1.3.11-1
    • +
  • ros-humble-ament-cmake-google-benchmark: 1.3.10-1 → 1.3.11-1
    • +
  • ros-humble-ament-cmake-gtest: 1.3.10-1 → 1.3.11-1
    • +
  • ros-humble-ament-cmake-include-directories: 1.3.10-1 → 1.3.11-1
    • +
  • ros-humble-ament-cmake-libraries: 1.3.10-1 → 1.3.11-1
    • +
  • ros-humble-ament-cmake-nose: 1.3.10-1 → 1.3.11-1
    • +
  • ros-humble-ament-cmake-pytest: 1.3.10-1 → 1.3.11-1
    • +
  • ros-humble-ament-cmake-python: 1.3.10-1 → 1.3.11-1
    • +
  • ros-humble-ament-cmake-target-dependencies: 1.3.10-1 → 1.3.11-1
    • +
  • ros-humble-ament-cmake-test: 1.3.10-1 → 1.3.11-1
    • +
  • ros-humble-ament-cmake-vendor-package: 1.3.10-1 → 1.3.11-1
    • +
  • ros-humble-ament-cmake-version: 1.3.10-1 → 1.3.11-1
    • +
  • ros-humble-autoware-lanelet2-extension: 0.6.0-1 → 0.6.2-1
    • +
  • ros-humble-autoware-lanelet2-extension-dbgsym: 0.6.0-1 → 0.6.2-1
    • +
  • ros-humble-autoware-lanelet2-extension-python: 0.6.0-1 → 0.6.2-1
    • +
  • ros-humble-autoware-lanelet2-extension-python-dbgsym: 0.6.0-1 → 0.6.2-1
    • +
  • ros-humble-backward-ros: 1.0.5-1 → 1.0.6-1
    • +
  • ros-humble-backward-ros-dbgsym: 1.0.5-1 → 1.0.6-1
    • +
  • ros-humble-bicycle-steering-controller: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-bicycle-steering-controller-dbgsym: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-bosch-locator-bridge: 2.1.11-1 → 2.1.13-1
    • +
  • ros-humble-bosch-locator-bridge-dbgsym: 2.1.11-1 → 2.1.13-1
    • +
  • ros-humble-bosch-locator-bridge-utils: 2.1.11-1 → 2.1.13-1
    • +
  • ros-humble-bosch-locator-bridge-utils-dbgsym: 2.1.11-1 → 2.1.13-1
    • +
  • ros-humble-camera-calibration-parsers: 3.1.9-1 → 3.1.10-1
    • +
  • ros-humble-camera-calibration-parsers-dbgsym: 3.1.9-1 → 3.1.10-1
    • +
  • ros-humble-camera-info-manager: 3.1.9-1 → 3.1.10-1
    • +
  • ros-humble-camera-info-manager-dbgsym: 3.1.9-1 → 3.1.10-1
    • +
  • ros-humble-camera-ros: 0.1.0-2 → 0.2.0-1
    • +
  • ros-humble-camera-ros-dbgsym: 0.1.0-2 → 0.2.0-1
    • +
  • ros-humble-chomp-motion-planner: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-chomp-motion-planner-dbgsym: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-clearpath-common: 0.3.4-1 → 1.0.0-1
    • +
  • ros-humble-clearpath-config: 0.3.4-1 → 1.0.0-1
    • +
  • ros-humble-clearpath-config-live: 0.3.0-1 → 1.0.0-1
    • +
  • ros-humble-clearpath-control: 0.3.4-1 → 1.0.0-1
    • +
  • ros-humble-clearpath-customization: 0.3.4-1 → 1.0.0-1
    • +
  • ros-humble-clearpath-description: 0.3.4-1 → 1.0.0-1
    • +
  • ros-humble-clearpath-desktop: 0.3.0-1 → 1.0.0-1
    • +
  • ros-humble-clearpath-generator-common: 0.3.4-1 → 1.0.0-1
    • +
  • ros-humble-clearpath-generator-common-dbgsym: 0.3.4-1 → 1.0.0-1
    • +
  • ros-humble-clearpath-generator-gz: 0.3.0-1 → 1.0.0-1
    • +
  • ros-humble-clearpath-gz: 0.3.0-1 → 1.0.0-1
    • +
  • ros-humble-clearpath-manipulators: 0.3.4-1 → 1.0.0-1
    • +
  • ros-humble-clearpath-manipulators-description: 0.3.4-1 → 1.0.0-1
    • +
  • ros-humble-clearpath-mounts-description: 0.3.4-1 → 1.0.0-1
    • +
  • ros-humble-clearpath-msgs: 1.0.0-1 → 1.0.1-1
    • +
  • ros-humble-clearpath-nav2-demos: 0.2.0-1 → 1.0.0-1
    • +
  • ros-humble-clearpath-platform-description: 0.3.4-1 → 1.0.0-1
    • +
  • ros-humble-clearpath-platform-msgs: 1.0.0-1 → 1.0.1-1
    • +
  • ros-humble-clearpath-platform-msgs-dbgsym: 1.0.0-1 → 1.0.1-1
    • +
  • ros-humble-clearpath-sensors-description: 0.3.4-1 → 1.0.0-1
    • +
  • ros-humble-clearpath-simulator: 0.3.0-1 → 1.0.0-1
    • +
  • ros-humble-clearpath-viz: 0.3.0-1 → 1.0.0-1
    • +
  • ros-humble-control-msgs: 4.6.0-1 → 4.7.0-1
    • +
  • ros-humble-control-msgs-dbgsym: 4.6.0-1 → 4.7.0-1
    • +
  • ros-humble-controller-interface: 2.43.1-1 → 2.44.0-1
    • +
  • ros-humble-controller-interface-dbgsym: 2.43.1-1 → 2.44.0-1
    • +
  • ros-humble-controller-manager: 2.43.1-1 → 2.44.0-1
    • +
  • ros-humble-controller-manager-dbgsym: 2.43.1-1 → 2.44.0-1
    • +
  • ros-humble-controller-manager-msgs: 2.43.1-1 → 2.44.0-1
    • +
  • ros-humble-controller-manager-msgs-dbgsym: 2.43.1-1 → 2.44.0-1
    • +
  • ros-humble-costmap-queue: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-costmap-queue-dbgsym: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-cyclonedds: 0.10.4-1 → 0.10.5-2
    • +
  • ros-humble-cyclonedds-dbgsym: 0.10.4-1 → 0.10.5-2
    • +
  • ros-humble-depthai-bridge: 2.10.3-1 → 2.10.4-1
    • +
  • ros-humble-depthai-bridge-dbgsym: 2.10.3-1 → 2.10.4-1
    • +
  • ros-humble-depthai-descriptions: 2.10.3-1 → 2.10.4-1
    • +
  • ros-humble-depthai-examples: 2.10.3-1 → 2.10.4-1
    • +
  • ros-humble-depthai-examples-dbgsym: 2.10.3-1 → 2.10.4-1
    • +
  • ros-humble-depthai-filters: 2.10.3-1 → 2.10.4-1
    • +
  • ros-humble-depthai-filters-dbgsym: 2.10.3-1 → 2.10.4-1
    • +
  • ros-humble-depthai-ros: 2.10.3-1 → 2.10.4-1
    • +
  • ros-humble-depthai-ros-driver: 2.10.3-1 → 2.10.4-1
    • +
  • ros-humble-depthai-ros-driver-dbgsym: 2.10.3-1 → 2.10.4-1
    • +
  • ros-humble-depthai-ros-msgs: 2.10.3-1 → 2.10.4-1
    • +
  • ros-humble-depthai-ros-msgs-dbgsym: 2.10.3-1 → 2.10.4-1
    • +
  • ros-humble-diff-drive-controller: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-diff-drive-controller-dbgsym: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-dwb-core: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-dwb-core-dbgsym: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-dwb-critics: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-dwb-critics-dbgsym: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-dwb-msgs: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-dwb-msgs-dbgsym: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-dwb-plugins: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-dwb-plugins-dbgsym: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-effort-controllers: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-effort-controllers-dbgsym: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-etsi-its-cam-coding: 2.3.0-1 → 2.4.0-1
    • +
  • ros-humble-etsi-its-cam-coding-dbgsym: 2.3.0-1 → 2.4.0-1
    • +
  • ros-humble-etsi-its-cam-conversion: 2.3.0-1 → 2.4.0-1
    • +
  • ros-humble-etsi-its-cam-msgs: 2.3.0-1 → 2.4.0-1
    • +
  • ros-humble-etsi-its-cam-msgs-dbgsym: 2.3.0-1 → 2.4.0-1
    • +
  • ros-humble-etsi-its-cam-ts-coding: 2.3.0-1 → 2.4.0-1
    • +
  • ros-humble-etsi-its-cam-ts-coding-dbgsym: 2.3.0-1 → 2.4.0-1
    • +
  • ros-humble-etsi-its-cam-ts-conversion: 2.3.0-1 → 2.4.0-1
    • +
  • ros-humble-etsi-its-cam-ts-msgs: 2.3.0-1 → 2.4.0-1
    • +
  • ros-humble-etsi-its-cam-ts-msgs-dbgsym: 2.3.0-1 → 2.4.0-1
    • +
  • ros-humble-etsi-its-coding: 2.3.0-1 → 2.4.0-1
    • +
  • ros-humble-etsi-its-conversion: 2.3.0-1 → 2.4.0-1
    • +
  • ros-humble-etsi-its-conversion-dbgsym: 2.3.0-1 → 2.4.0-1
    • +
  • ros-humble-etsi-its-cpm-ts-coding: 2.3.0-1 → 2.4.0-1
    • +
  • ros-humble-etsi-its-cpm-ts-coding-dbgsym: 2.3.0-1 → 2.4.0-1
    • +
  • ros-humble-etsi-its-cpm-ts-conversion: 2.3.0-1 → 2.4.0-1
    • +
  • ros-humble-etsi-its-cpm-ts-msgs: 2.3.0-1 → 2.4.0-1
    • +
  • ros-humble-etsi-its-cpm-ts-msgs-dbgsym: 2.3.0-1 → 2.4.0-1
    • +
  • ros-humble-etsi-its-denm-coding: 2.3.0-1 → 2.4.0-1
    • +
  • ros-humble-etsi-its-denm-coding-dbgsym: 2.3.0-1 → 2.4.0-1
    • +
  • ros-humble-etsi-its-denm-conversion: 2.3.0-1 → 2.4.0-1
    • +
  • ros-humble-etsi-its-denm-msgs: 2.3.0-1 → 2.4.0-1
    • +
  • ros-humble-etsi-its-denm-msgs-dbgsym: 2.3.0-1 → 2.4.0-1
    • +
  • ros-humble-etsi-its-messages: 2.3.0-1 → 2.4.0-1
    • +
  • ros-humble-etsi-its-msgs: 2.3.0-1 → 2.4.0-1
    • +
  • ros-humble-etsi-its-msgs-utils: 2.3.0-1 → 2.4.0-1
    • +
  • ros-humble-etsi-its-primitives-conversion: 2.3.0-1 → 2.4.0-1
    • +
  • ros-humble-etsi-its-rviz-plugins: 2.3.0-1 → 2.4.0-1
    • +
  • ros-humble-etsi-its-rviz-plugins-dbgsym: 2.3.0-1 → 2.4.0-1
    • +
  • ros-humble-etsi-its-vam-ts-coding: 2.3.0-1 → 2.4.0-1
    • +
  • ros-humble-etsi-its-vam-ts-coding-dbgsym: 2.3.0-1 → 2.4.0-1
    • +
  • ros-humble-etsi-its-vam-ts-conversion: 2.3.0-1 → 2.4.0-1
    • +
  • ros-humble-etsi-its-vam-ts-msgs: 2.3.0-1 → 2.4.0-1
    • +
  • ros-humble-etsi-its-vam-ts-msgs-dbgsym: 2.3.0-1 → 2.4.0-1
    • +
  • ros-humble-examples-rclcpp-async-client: 0.15.2-1 → 0.15.3-1
    • +
  • ros-humble-examples-rclcpp-async-client-dbgsym: 0.15.2-1 → 0.15.3-1
    • +
  • ros-humble-examples-rclcpp-cbg-executor: 0.15.2-1 → 0.15.3-1
    • +
  • ros-humble-examples-rclcpp-cbg-executor-dbgsym: 0.15.2-1 → 0.15.3-1
    • +
  • ros-humble-examples-rclcpp-minimal-action-client: 0.15.2-1 → 0.15.3-1
    • +
  • ros-humble-examples-rclcpp-minimal-action-client-dbgsym: 0.15.2-1 → 0.15.3-1
    • +
  • ros-humble-examples-rclcpp-minimal-action-server: 0.15.2-1 → 0.15.3-1
    • +
  • ros-humble-examples-rclcpp-minimal-action-server-dbgsym: 0.15.2-1 → 0.15.3-1
    • +
  • ros-humble-examples-rclcpp-minimal-client: 0.15.2-1 → 0.15.3-1
    • +
  • ros-humble-examples-rclcpp-minimal-client-dbgsym: 0.15.2-1 → 0.15.3-1
    • +
  • ros-humble-examples-rclcpp-minimal-composition: 0.15.2-1 → 0.15.3-1
    • +
  • ros-humble-examples-rclcpp-minimal-composition-dbgsym: 0.15.2-1 → 0.15.3-1
    • +
  • ros-humble-examples-rclcpp-minimal-publisher: 0.15.2-1 → 0.15.3-1
    • +
  • ros-humble-examples-rclcpp-minimal-publisher-dbgsym: 0.15.2-1 → 0.15.3-1
    • +
  • ros-humble-examples-rclcpp-minimal-service: 0.15.2-1 → 0.15.3-1
    • +
  • ros-humble-examples-rclcpp-minimal-service-dbgsym: 0.15.2-1 → 0.15.3-1
    • +
  • ros-humble-examples-rclcpp-minimal-subscriber: 0.15.2-1 → 0.15.3-1
    • +
  • ros-humble-examples-rclcpp-minimal-subscriber-dbgsym: 0.15.2-1 → 0.15.3-1
    • +
  • ros-humble-examples-rclcpp-minimal-timer: 0.15.2-1 → 0.15.3-1
    • +
  • ros-humble-examples-rclcpp-minimal-timer-dbgsym: 0.15.2-1 → 0.15.3-1
    • +
  • ros-humble-examples-rclcpp-multithreaded-executor: 0.15.2-1 → 0.15.3-1
    • +
  • ros-humble-examples-rclcpp-multithreaded-executor-dbgsym: 0.15.2-1 → 0.15.3-1
    • +
  • ros-humble-examples-rclcpp-wait-set: 0.15.2-1 → 0.15.3-1
    • +
  • ros-humble-examples-rclcpp-wait-set-dbgsym: 0.15.2-1 → 0.15.3-1
    • +
  • ros-humble-examples-rclpy-executors: 0.15.2-1 → 0.15.3-1
    • +
  • ros-humble-examples-rclpy-guard-conditions: 0.15.2-1 → 0.15.3-1
    • +
  • ros-humble-examples-rclpy-minimal-action-client: 0.15.2-1 → 0.15.3-1
    • +
  • ros-humble-examples-rclpy-minimal-action-server: 0.15.2-1 → 0.15.3-1
    • +
  • ros-humble-examples-rclpy-minimal-client: 0.15.2-1 → 0.15.3-1
    • +
  • ros-humble-examples-rclpy-minimal-publisher: 0.15.2-1 → 0.15.3-1
    • +
  • ros-humble-examples-rclpy-minimal-service: 0.15.2-1 → 0.15.3-1
    • +
  • ros-humble-examples-rclpy-minimal-subscriber: 0.15.2-1 → 0.15.3-1
    • +
  • ros-humble-examples-rclpy-pointcloud-publisher: 0.15.2-1 → 0.15.3-1
    • +
  • ros-humble-examples-tf2-py: 0.25.8-1 → 0.25.9-1
    • +
  • ros-humble-fastrtps: 2.6.8-1 → 2.6.9-1
    • +
  • ros-humble-fastrtps-dbgsym: 2.6.8-1 → 2.6.9-1
    • +
  • ros-humble-flir-camera-description: 2.1.17-1 → 3.0.0-1
    • +
  • ros-humble-flir-camera-msgs: 2.1.17-1 → 3.0.0-1
    • +
  • ros-humble-flir-camera-msgs-dbgsym: 2.1.17-1 → 3.0.0-1
    • +
  • ros-humble-force-torque-sensor-broadcaster: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-force-torque-sensor-broadcaster-dbgsym: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-forward-command-controller: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-forward-command-controller-dbgsym: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-foxglove-bridge: 0.8.0-1 → 0.8.1-1
    • +
  • ros-humble-foxglove-bridge-dbgsym: 0.8.0-1 → 0.8.1-1
    • +
  • ros-humble-foxglove-compressed-video-transport: 1.0.0-1 → 1.0.1-1
    • +
  • ros-humble-foxglove-compressed-video-transport-dbgsym: 1.0.0-1 → 1.0.1-1
    • +
  • ros-humble-geometry2: 0.25.8-1 → 0.25.9-1
    • +
  • ros-humble-gripper-controllers: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-gripper-controllers-dbgsym: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-hardware-interface: 2.43.1-1 → 2.44.0-1
    • +
  • ros-humble-hardware-interface-dbgsym: 2.43.1-1 → 2.44.0-1
    • +
  • ros-humble-hardware-interface-testing: 2.43.1-1 → 2.44.0-1
    • +
  • ros-humble-hardware-interface-testing-dbgsym: 2.43.1-1 → 2.44.0-1
    • +
  • ros-humble-image-common: 3.1.9-1 → 3.1.10-1
    • +
  • ros-humble-image-transport: 3.1.9-1 → 3.1.10-1
    • +
  • ros-humble-image-transport-dbgsym: 3.1.9-1 → 3.1.10-1
    • +
  • ros-humble-imu-sensor-broadcaster: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-imu-sensor-broadcaster-dbgsym: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-interactive-marker-twist-server: 2.1.0-2 → 2.1.1-1
    • +
  • ros-humble-interactive-marker-twist-server-dbgsym: 2.1.0-2 → 2.1.1-1
    • +
  • ros-humble-joint-limits: 2.43.1-1 → 2.44.0-1
    • +
  • ros-humble-joint-limits-dbgsym: 2.43.1-1 → 2.44.0-1
    • +
  • ros-humble-joint-state-broadcaster: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-joint-state-broadcaster-dbgsym: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-joint-trajectory-controller: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-joint-trajectory-controller-dbgsym: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-joy-teleop: 1.6.0-1 → 1.7.0-1
    • +
  • ros-humble-key-teleop: 1.6.0-1 → 1.7.0-1
    • +
  • ros-humble-launch: 1.0.6-1 → 1.0.7-1
    • +
  • ros-humble-launch-pytest: 1.0.6-1 → 1.0.7-1
    • +
  • ros-humble-launch-ros: 0.19.7-2 → 0.19.8-1
    • +
  • ros-humble-launch-testing: 1.0.6-1 → 1.0.7-1
    • +
  • ros-humble-launch-testing-ament-cmake: 1.0.6-1 → 1.0.7-1
    • +
  • ros-humble-launch-testing-examples: 0.15.2-1 → 0.15.3-1
    • +
  • ros-humble-launch-testing-ros: 0.19.7-2 → 0.19.8-1
    • +
  • ros-humble-launch-xml: 1.0.6-1 → 1.0.7-1
    • +
  • ros-humble-launch-yaml: 1.0.6-1 → 1.0.7-1
    • +
  • ros-humble-leo: 1.2.3-1 → 1.2.4-1
    • +
  • ros-humble-leo-bringup: 1.4.0-1 → 1.5.0-1
    • +
  • ros-humble-leo-description: 1.2.3-1 → 1.2.4-1
    • +
  • ros-humble-leo-fw: 1.4.0-1 → 1.5.0-1
    • +
  • ros-humble-leo-fw-dbgsym: 1.4.0-1 → 1.5.0-1
    • +
  • ros-humble-leo-gz-bringup: 1.1.0-1 → 1.1.1-1
    • +
  • ros-humble-leo-gz-plugins: 1.1.0-1 → 1.1.1-1
    • +
  • ros-humble-leo-gz-plugins-dbgsym: 1.1.0-1 → 1.1.1-1
    • +
  • ros-humble-leo-gz-worlds: 1.1.0-1 → 1.1.1-1
    • +
  • ros-humble-leo-msgs: 1.2.3-1 → 1.2.4-1
    • +
  • ros-humble-leo-msgs-dbgsym: 1.2.3-1 → 1.2.4-1
    • +
  • ros-humble-leo-robot: 1.4.0-1 → 1.5.0-1
    • +
  • ros-humble-leo-simulator: 1.1.0-1 → 1.1.1-1
    • +
  • ros-humble-leo-teleop: 1.2.3-1 → 1.2.4-1
    • +
  • ros-humble-libstatistics-collector: 1.3.2-1 → 1.3.4-1
    • +
  • ros-humble-libstatistics-collector-dbgsym: 1.3.2-1 → 1.3.4-1
    • +
  • ros-humble-mcap-vendor: 0.15.12-1 → 0.15.13-1
    • +
  • ros-humble-mcap-vendor-dbgsym: 0.15.12-1 → 0.15.13-1
    • +
  • ros-humble-microstrain-inertial-description: 4.4.0-1 → 4.5.0-1
    • +
  • ros-humble-microstrain-inertial-driver: 4.4.0-1 → 4.5.0-1
    • +
  • ros-humble-microstrain-inertial-driver-dbgsym: 4.4.0-1 → 4.5.0-1
    • +
  • ros-humble-microstrain-inertial-examples: 4.4.0-1 → 4.5.0-1
    • +
  • ros-humble-microstrain-inertial-msgs: 4.4.0-1 → 4.5.0-1
    • +
  • ros-humble-microstrain-inertial-msgs-dbgsym: 4.4.0-1 → 4.5.0-1
    • +
  • ros-humble-microstrain-inertial-rqt: 4.4.0-1 → 4.5.0-1
    • +
  • ros-humble-mouse-teleop: 1.6.0-1 → 1.7.0-1
    • +
  • ros-humble-moveit: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-chomp-optimizer-adapter: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-chomp-optimizer-adapter-dbgsym: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-common: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-configs-utils: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-core: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-core-dbgsym: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-hybrid-planning: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-hybrid-planning-dbgsym: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-kinematics: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-kinematics-dbgsym: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-planners: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-planners-chomp: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-planners-chomp-dbgsym: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-planners-ompl: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-planners-ompl-dbgsym: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-plugins: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-resources-prbt-ikfast-manipulator-plugin: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-resources-prbt-ikfast-manipulator-plugin-dbgsym: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-resources-prbt-moveit-config: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-resources-prbt-pg70-support: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-resources-prbt-support: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-ros: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-ros-benchmarks: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-ros-benchmarks-dbgsym: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-ros-control-interface: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-ros-control-interface-dbgsym: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-ros-move-group: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-ros-move-group-dbgsym: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-ros-occupancy-map-monitor: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-ros-occupancy-map-monitor-dbgsym: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-ros-perception: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-ros-perception-dbgsym: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-ros-planning: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-ros-planning-dbgsym: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-ros-planning-interface: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-ros-planning-interface-dbgsym: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-ros-robot-interaction: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-ros-robot-interaction-dbgsym: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-ros-visualization: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-ros-visualization-dbgsym: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-ros-warehouse: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-ros-warehouse-dbgsym: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-runtime: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-servo: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-servo-dbgsym: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-setup-app-plugins: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-setup-app-plugins-dbgsym: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-setup-assistant: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-setup-assistant-dbgsym: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-setup-controllers: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-setup-controllers-dbgsym: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-setup-core-plugins: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-setup-core-plugins-dbgsym: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-setup-framework: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-setup-framework-dbgsym: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-setup-srdf-plugins: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-setup-srdf-plugins-dbgsym: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-simple-controller-manager: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-simple-controller-manager-dbgsym: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-mp2p-icp: 1.6.2-1 → 1.6.3-1
    • +
  • ros-humble-mp2p-icp-dbgsym: 1.6.2-1 → 1.6.3-1
    • +
  • ros-humble-mrpt-apps: 2.14.4-1 → 2.14.5-1
    • +
  • ros-humble-mrpt-apps-dbgsym: 2.14.4-1 → 2.14.5-1
    • +
  • ros-humble-mrpt-libapps: 2.14.4-1 → 2.14.5-1
    • +
  • ros-humble-mrpt-libapps-dbgsym: 2.14.4-1 → 2.14.5-1
    • +
  • ros-humble-mrpt-libbase: 2.14.4-1 → 2.14.5-1
    • +
  • ros-humble-mrpt-libbase-dbgsym: 2.14.4-1 → 2.14.5-1
    • +
  • ros-humble-mrpt-libgui: 2.14.4-1 → 2.14.5-1
    • +
  • ros-humble-mrpt-libgui-dbgsym: 2.14.4-1 → 2.14.5-1
    • +
  • ros-humble-mrpt-libhwdrivers: 2.14.4-1 → 2.14.5-1
    • +
  • ros-humble-mrpt-libhwdrivers-dbgsym: 2.14.4-1 → 2.14.5-1
    • +
  • ros-humble-mrpt-libmaps: 2.14.4-1 → 2.14.5-1
    • +
  • ros-humble-mrpt-libmaps-dbgsym: 2.14.4-1 → 2.14.5-1
    • +
  • ros-humble-mrpt-libmath: 2.14.4-1 → 2.14.5-1
    • +
  • ros-humble-mrpt-libmath-dbgsym: 2.14.4-1 → 2.14.5-1
    • +
  • ros-humble-mrpt-libnav: 2.14.4-1 → 2.14.5-1
    • +
  • ros-humble-mrpt-libnav-dbgsym: 2.14.4-1 → 2.14.5-1
    • +
  • ros-humble-mrpt-libobs: 2.14.4-1 → 2.14.5-1
    • +
  • ros-humble-mrpt-libobs-dbgsym: 2.14.4-1 → 2.14.5-1
    • +
  • ros-humble-mrpt-libopengl: 2.14.4-1 → 2.14.5-1
    • +
  • ros-humble-mrpt-libopengl-dbgsym: 2.14.4-1 → 2.14.5-1
    • +
  • ros-humble-mrpt-libposes: 2.14.4-1 → 2.14.5-1
    • +
  • ros-humble-mrpt-libposes-dbgsym: 2.14.4-1 → 2.14.5-1
    • +
  • ros-humble-mrpt-libros-bridge: 2.14.4-1 → 2.14.5-1
    • +
  • ros-humble-mrpt-libros-bridge-dbgsym: 2.14.4-1 → 2.14.5-1
    • +
  • ros-humble-mrpt-libslam: 2.14.4-1 → 2.14.5-1
    • +
  • ros-humble-mrpt-libslam-dbgsym: 2.14.4-1 → 2.14.5-1
    • +
  • ros-humble-mrpt-libtclap: 2.14.4-1 → 2.14.5-1
    • +
  • ros-humble-nav-2d-msgs: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav-2d-msgs-dbgsym: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav-2d-utils: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav-2d-utils-dbgsym: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-amcl: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-amcl-dbgsym: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-behavior-tree: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-behavior-tree-dbgsym: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-behaviors: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-behaviors-dbgsym: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-bringup: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-bt-navigator: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-bt-navigator-dbgsym: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-collision-monitor: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-collision-monitor-dbgsym: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-common: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-constrained-smoother: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-constrained-smoother-dbgsym: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-controller: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-controller-dbgsym: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-core: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-costmap-2d: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-costmap-2d-dbgsym: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-dwb-controller: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-graceful-controller: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-graceful-controller-dbgsym: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-lifecycle-manager: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-lifecycle-manager-dbgsym: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-map-server: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-map-server-dbgsym: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-mppi-controller: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-mppi-controller-dbgsym: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-msgs: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-msgs-dbgsym: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-navfn-planner: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-navfn-planner-dbgsym: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-planner: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-planner-dbgsym: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-regulated-pure-pursuit-controller: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-regulated-pure-pursuit-controller-dbgsym: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-rotation-shim-controller: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-rotation-shim-controller-dbgsym: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-rviz-plugins: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-rviz-plugins-dbgsym: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-simple-commander: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-smac-planner: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-smac-planner-dbgsym: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-smoother: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-smoother-dbgsym: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-system-tests: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-system-tests-dbgsym: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-theta-star-planner: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-theta-star-planner-dbgsym: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-util: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-util-dbgsym: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-velocity-smoother: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-velocity-smoother-dbgsym: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-voxel-grid: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-voxel-grid-dbgsym: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-waypoint-follower: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-waypoint-follower-dbgsym: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-navigation2: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-novatel-gps-driver: 4.1.3-1 → 4.2.0-1
    • +
  • ros-humble-novatel-gps-driver-dbgsym: 4.1.3-1 → 4.2.0-1
    • +
  • ros-humble-novatel-gps-msgs: 4.1.3-1 → 4.2.0-1
    • +
  • ros-humble-novatel-gps-msgs-dbgsym: 4.1.3-1 → 4.2.0-1
    • +
  • ros-humble-octomap-msgs: 2.0.0-3 → 2.0.1-1
    • +
  • ros-humble-octomap-msgs-dbgsym: 2.0.0-3 → 2.0.1-1
    • +
  • ros-humble-odom-to-tf-ros2: 1.0.2-1 → 1.0.4-1
    • +
  • ros-humble-odom-to-tf-ros2-dbgsym: 1.0.2-1 → 1.0.4-1
    • +
  • ros-humble-openni2-camera: 2.0.2-1 → 2.0.3-1
    • +
  • ros-humble-openni2-camera-dbgsym: 2.0.2-1 → 2.0.3-1
    • +
  • ros-humble-osrf-pycommon: 2.0.2-2 → 2.1.4-1
    • +
  • ros-humble-pal-gripper: 3.3.0-1 → 3.4.0-1
    • +
  • ros-humble-pal-gripper-controller-configuration: 3.3.0-1 → 3.4.0-1
    • +
  • ros-humble-pal-gripper-description: 3.3.0-1 → 3.4.0-1
    • +
  • ros-humble-pal-gripper-simulation: 3.3.0-1 → 3.4.0-1
    • +
  • ros-humble-pal-maps: 0.0.4-1 → 0.0.5-1
    • +
  • ros-humble-pal-statistics: 2.3.1-1 → 2.5.0-1
    • +
  • ros-humble-pal-statistics-dbgsym: 2.3.1-1 → 2.5.0-1
    • +
  • ros-humble-pal-statistics-msgs: 2.3.1-1 → 2.5.0-1
    • +
  • ros-humble-pal-statistics-msgs-dbgsym: 2.3.1-1 → 2.5.0-1
    • +
  • ros-humble-pid-controller: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-pid-controller-dbgsym: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-pilz-industrial-motion-planner: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-pilz-industrial-motion-planner-dbgsym: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-pilz-industrial-motion-planner-testutils: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-pilz-industrial-motion-planner-testutils-dbgsym: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-pmb2-2dnav: 4.2.0-1 → 4.5.0-1
    • +
  • ros-humble-pmb2-bringup: 5.3.1-1 → 5.4.0-1
    • +
  • ros-humble-pmb2-controller-configuration: 5.3.1-1 → 5.4.0-1
    • +
  • ros-humble-pmb2-description: 5.3.1-1 → 5.4.0-1
    • +
  • ros-humble-pmb2-gazebo: 4.0.16-1 → 4.1.0-1
    • +
  • ros-humble-pmb2-laser-sensors: 4.2.0-1 → 4.5.0-1
    • +
  • ros-humble-pmb2-navigation: 4.2.0-1 → 4.5.0-1
    • +
  • ros-humble-pmb2-robot: 5.3.1-1 → 5.4.0-1
    • +
  • ros-humble-pmb2-simulation: 4.0.16-1 → 4.1.0-1
    • +
  • ros-humble-position-controllers: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-position-controllers-dbgsym: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-python-mrpt: 2.14.4-1 → 2.14.5-1
    • +
  • ros-humble-range-sensor-broadcaster: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-range-sensor-broadcaster-dbgsym: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-rc-reason-clients: 0.3.1-1 → 0.4.0-2
    • +
  • ros-humble-rc-reason-msgs: 0.3.1-1 → 0.4.0-2
    • +
  • ros-humble-rc-reason-msgs-dbgsym: 0.3.1-1 → 0.4.0-2
    • +
  • ros-humble-rclcpp: 16.0.10-1 → 16.0.11-1
    • +
  • ros-humble-rclcpp-action: 16.0.10-1 → 16.0.11-1
    • +
  • ros-humble-rclcpp-action-dbgsym: 16.0.10-1 → 16.0.11-1
    • +
  • ros-humble-rclcpp-components: 16.0.10-1 → 16.0.11-1
    • +
  • ros-humble-rclcpp-components-dbgsym: 16.0.10-1 → 16.0.11-1
    • +
  • ros-humble-rclcpp-dbgsym: 16.0.10-1 → 16.0.11-1
    • +
  • ros-humble-rclcpp-lifecycle: 16.0.10-1 → 16.0.11-1
    • +
  • ros-humble-rclcpp-lifecycle-dbgsym: 16.0.10-1 → 16.0.11-1
    • +
  • ros-humble-rclpy: 3.3.14-1 → 3.3.15-1
    • +
  • ros-humble-rcpputils: 2.4.3-1 → 2.4.4-1
    • +
  • ros-humble-rcpputils-dbgsym: 2.4.3-1 → 2.4.4-1
    • +
  • ros-humble-realtime-tools: 2.7.0-1 → 2.8.1-1
    • +
  • ros-humble-realtime-tools-dbgsym: 2.7.0-1 → 2.8.1-1
    • +
  • ros-humble-rmf-building-map-tools: 1.6.2-1 → 1.6.3-1
    • +
  • ros-humble-rmf-traffic-editor: 1.6.2-1 → 1.6.3-1
    • +
  • ros-humble-rmf-traffic-editor-assets: 1.6.2-1 → 1.6.3-1
    • +
  • ros-humble-rmf-traffic-editor-dbgsym: 1.6.2-1 → 1.6.3-1
    • +
  • ros-humble-rmf-traffic-editor-test-maps: 1.6.2-1 → 1.6.3-1
    • +
  • ros-humble-rmw-connextdds: 0.11.2-1 → 0.11.3-1
    • +
  • ros-humble-rmw-connextdds-common: 0.11.2-1 → 0.11.3-1
    • +
  • ros-humble-rmw-connextdds-common-dbgsym: 0.11.2-1 → 0.11.3-1
    • +
  • ros-humble-rmw-connextdds-dbgsym: 0.11.2-1 → 0.11.3-1
    • +
  • ros-humble-robot-calibration: 0.8.1-1 → 0.8.2-1
    • +
  • ros-humble-robot-calibration-dbgsym: 0.8.1-1 → 0.8.2-1
    • +
  • ros-humble-robot-calibration-msgs: 0.8.1-1 → 0.8.2-1
    • +
  • ros-humble-robot-calibration-msgs-dbgsym: 0.8.1-1 → 0.8.2-1
    • +
  • ros-humble-ros2-control: 2.43.1-1 → 2.44.0-1
    • +
  • ros-humble-ros2-control-test-assets: 2.43.1-1 → 2.44.0-1
    • +
  • ros-humble-ros2-controllers: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-ros2-controllers-test-nodes: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-ros2bag: 0.15.12-1 → 0.15.13-1
    • +
  • ros-humble-ros2controlcli: 2.43.1-1 → 2.44.0-1
    • +
  • ros-humble-ros2launch: 0.19.7-2 → 0.19.8-1
    • +
  • ros-humble-rosbag2: 0.15.12-1 → 0.15.13-1
    • +
  • ros-humble-rosbag2-compression: 0.15.12-1 → 0.15.13-1
    • +
  • ros-humble-rosbag2-compression-dbgsym: 0.15.12-1 → 0.15.13-1
    • +
  • ros-humble-rosbag2-compression-zstd: 0.15.12-1 → 0.15.13-1
    • +
  • ros-humble-rosbag2-compression-zstd-dbgsym: 0.15.12-1 → 0.15.13-1
    • +
  • ros-humble-rosbag2-cpp: 0.15.12-1 → 0.15.13-1
    • +
  • ros-humble-rosbag2-cpp-dbgsym: 0.15.12-1 → 0.15.13-1
    • +
  • ros-humble-rosbag2-interfaces: 0.15.12-1 → 0.15.13-1
    • +
  • ros-humble-rosbag2-interfaces-dbgsym: 0.15.12-1 → 0.15.13-1
    • +
  • ros-humble-rosbag2-performance-benchmarking: 0.15.12-1 → 0.15.13-1
    • +
  • ros-humble-rosbag2-py: 0.15.12-1 → 0.15.13-1
    • +
  • ros-humble-rosbag2-storage: 0.15.12-1 → 0.15.13-1
    • +
  • ros-humble-rosbag2-storage-dbgsym: 0.15.12-1 → 0.15.13-1
    • +
  • ros-humble-rosbag2-storage-default-plugins: 0.15.12-1 → 0.15.13-1
    • +
  • ros-humble-rosbag2-storage-default-plugins-dbgsym: 0.15.12-1 → 0.15.13-1
    • +
  • ros-humble-rosbag2-storage-mcap: 0.15.12-1 → 0.15.13-1
    • +
  • ros-humble-rosbag2-storage-mcap-dbgsym: 0.15.12-1 → 0.15.13-1
    • +
  • ros-humble-rosbag2-storage-mcap-testdata: 0.15.12-1 → 0.15.13-1
    • +
  • ros-humble-rosbag2-storage-mcap-testdata-dbgsym: 0.15.12-1 → 0.15.13-1
    • +
  • ros-humble-rosbag2-test-common: 0.15.12-1 → 0.15.13-1
    • +
  • ros-humble-rosbag2-tests: 0.15.12-1 → 0.15.13-1
    • +
  • ros-humble-rosbag2-transport: 0.15.12-1 → 0.15.13-1
    • +
  • ros-humble-rosbag2-transport-dbgsym: 0.15.12-1 → 0.15.13-1
    • +
  • ros-humble-rosidl-adapter: 3.1.5-2 → 3.1.6-1
    • +
  • ros-humble-rosidl-cli: 3.1.5-2 → 3.1.6-1
    • +
  • ros-humble-rosidl-cmake: 3.1.5-2 → 3.1.6-1
    • +
  • ros-humble-rosidl-generator-c: 3.1.5-2 → 3.1.6-1
    • +
  • ros-humble-rosidl-generator-cpp: 3.1.5-2 → 3.1.6-1
    • +
  • ros-humble-rosidl-parser: 3.1.5-2 → 3.1.6-1
    • +
  • ros-humble-rosidl-runtime-c: 3.1.5-2 → 3.1.6-1
    • +
  • ros-humble-rosidl-runtime-c-dbgsym: 3.1.5-2 → 3.1.6-1
    • +
  • ros-humble-rosidl-runtime-cpp: 3.1.5-2 → 3.1.6-1
    • +
  • ros-humble-rosidl-typesupport-c: 2.0.1-1 → 2.0.2-1
    • +
  • ros-humble-rosidl-typesupport-c-dbgsym: 2.0.1-1 → 2.0.2-1
    • +
  • ros-humble-rosidl-typesupport-cpp: 2.0.1-1 → 2.0.2-1
    • +
  • ros-humble-rosidl-typesupport-cpp-dbgsym: 2.0.1-1 → 2.0.2-1
    • +
  • ros-humble-rosidl-typesupport-interface: 3.1.5-2 → 3.1.6-1
    • +
  • ros-humble-rosidl-typesupport-introspection-c: 3.1.5-2 → 3.1.6-1
    • +
  • ros-humble-rosidl-typesupport-introspection-c-dbgsym: 3.1.5-2 → 3.1.6-1
    • +
  • ros-humble-rosidl-typesupport-introspection-cpp: 3.1.5-2 → 3.1.6-1
    • +
  • ros-humble-rosidl-typesupport-introspection-cpp-dbgsym: 3.1.5-2 → 3.1.6-1
    • +
  • ros-humble-rqt-controller-manager: 2.43.1-1 → 2.44.0-1
    • +
  • ros-humble-rqt-joint-trajectory-controller: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-rti-connext-dds-cmake-module: 0.11.2-1 → 0.11.3-1
    • +
  • ros-humble-rviz-assimp-vendor: 11.2.13-1 → 11.2.14-1
    • +
  • ros-humble-rviz-common: 11.2.13-1 → 11.2.14-1
    • +
  • ros-humble-rviz-common-dbgsym: 11.2.13-1 → 11.2.14-1
    • +
  • ros-humble-rviz-default-plugins: 11.2.13-1 → 11.2.14-1
    • +
  • ros-humble-rviz-default-plugins-dbgsym: 11.2.13-1 → 11.2.14-1
    • +
  • ros-humble-rviz-ogre-vendor: 11.2.13-1 → 11.2.14-1
    • +
  • ros-humble-rviz-ogre-vendor-dbgsym: 11.2.13-1 → 11.2.14-1
    • +
  • ros-humble-rviz-rendering: 11.2.13-1 → 11.2.14-1
    • +
  • ros-humble-rviz-rendering-dbgsym: 11.2.13-1 → 11.2.14-1
    • +
  • ros-humble-rviz-rendering-tests: 11.2.13-1 → 11.2.14-1
    • +
  • ros-humble-rviz-visual-testing-framework: 11.2.13-1 → 11.2.14-1
    • +
  • ros-humble-rviz2: 11.2.13-1 → 11.2.14-1
    • +
  • ros-humble-rviz2-dbgsym: 11.2.13-1 → 11.2.14-1
    • +
  • ros-humble-shared-queues-vendor: 0.15.12-1 → 0.15.13-1
    • +
  • ros-humble-spinnaker-camera-driver: 2.1.17-1 → 3.0.0-1
    • +
  • ros-humble-spinnaker-camera-driver-dbgsym: 2.1.17-1 → 3.0.0-1
    • +
  • ros-humble-spinnaker-synchronized-camera-driver: 2.1.17-1 → 3.0.0-1
    • +
  • ros-humble-spinnaker-synchronized-camera-driver-dbgsym: 2.1.17-1 → 3.0.0-1
    • +
  • ros-humble-sqlite3-vendor: 0.15.12-1 → 0.15.13-1
    • +
  • ros-humble-steering-controllers-library: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-steering-controllers-library-dbgsym: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-teleop-tools: 1.6.0-1 → 1.7.0-1
    • +
  • ros-humble-teleop-tools-msgs: 1.6.0-1 → 1.7.0-1
    • +
  • ros-humble-teleop-tools-msgs-dbgsym: 1.6.0-1 → 1.7.0-1
    • +
  • ros-humble-tf2: 0.25.8-1 → 0.25.9-1
    • +
  • ros-humble-tf2-bullet: 0.25.8-1 → 0.25.9-1
    • +
  • ros-humble-tf2-dbgsym: 0.25.8-1 → 0.25.9-1
    • +
  • ros-humble-tf2-eigen: 0.25.8-1 → 0.25.9-1
    • +
  • ros-humble-tf2-eigen-kdl: 0.25.8-1 → 0.25.9-1
    • +
  • ros-humble-tf2-eigen-kdl-dbgsym: 0.25.8-1 → 0.25.9-1
    • +
  • ros-humble-tf2-geometry-msgs: 0.25.8-1 → 0.25.9-1
    • +
  • ros-humble-tf2-kdl: 0.25.8-1 → 0.25.9-1
    • +
  • ros-humble-tf2-msgs: 0.25.8-1 → 0.25.9-1
    • +
  • ros-humble-tf2-msgs-dbgsym: 0.25.8-1 → 0.25.9-1
    • +
  • ros-humble-tf2-py: 0.25.8-1 → 0.25.9-1
    • +
  • ros-humble-tf2-py-dbgsym: 0.25.8-1 → 0.25.9-1
    • +
  • ros-humble-tf2-ros: 0.25.8-1 → 0.25.9-1
    • +
  • ros-humble-tf2-ros-dbgsym: 0.25.8-1 → 0.25.9-1
    • +
  • ros-humble-tf2-ros-py: 0.25.8-1 → 0.25.9-1
    • +
  • ros-humble-tf2-sensor-msgs: 0.25.8-1 → 0.25.9-1
    • +
  • ros-humble-tf2-tools: 0.25.8-1 → 0.25.9-1
    • +
  • ros-humble-tiago-2dnav: 4.2.0-1 → 4.5.0-1
    • +
  • ros-humble-tiago-bringup: 4.6.0-1 → 4.7.1-1
    • +
  • ros-humble-tiago-controller-configuration: 4.6.0-1 → 4.7.1-1
    • +
  • ros-humble-tiago-description: 4.6.0-1 → 4.7.1-1
    • +
  • ros-humble-tiago-gazebo: 4.2.0-1 → 4.3.0-1
    • +
  • ros-humble-tiago-gazebo-dbgsym: 4.2.0-1 → 4.3.0-1
    • +
  • ros-humble-tiago-laser-sensors: 4.2.0-1 → 4.5.0-1
    • +
  • ros-humble-tiago-moveit-config: 3.1.0-1 → 3.1.1-1
    • +
  • ros-humble-tiago-navigation: 4.2.0-1 → 4.5.0-1
    • +
  • ros-humble-tiago-robot: 4.6.0-1 → 4.7.1-1
    • +
  • ros-humble-tiago-simulation: 4.2.0-1 → 4.3.0-1
    • +
  • ros-humble-transmission-interface: 2.43.1-1 → 2.44.0-1
    • +
  • ros-humble-transmission-interface-dbgsym: 2.43.1-1 → 2.44.0-1
    • +
  • ros-humble-tricycle-controller: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-tricycle-controller-dbgsym: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-tricycle-steering-controller: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-tricycle-steering-controller-dbgsym: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-twist-stamper: 0.0.3-1 → 0.0.5-1
    • +
  • ros-humble-ur-client-library: 1.4.0-1 → 1.5.0-1
    • +
  • ros-humble-ur-client-library-dbgsym: 1.4.0-1 → 1.5.0-1
    • +
  • ros-humble-velocity-controllers: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-velocity-controllers-dbgsym: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-zstd-vendor: 0.15.12-1 → 0.15.13-1
    • +
+

Removed Packages [6]:

+ +

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

+
    +
  • Adam Serafin
    • +
  • Aditya Pande
    • +
  • Aina Irisarri
    • +
  • Alberto Tudela
    • +
  • Alejandro Hernandez Cordero
    • +
  • Alexander Gutenkunst
    • +
  • Alexey Merzlyakov
    • +
  • Analog Devices
    • +
  • Andrea Sorbini
    • +
  • Antonio Brandi
    • +
  • Bence Magyar
    • +
  • Bernd Pfrommer
    • +
  • Blake Anderson
    • +
  • Brandon Ong
    • +
  • Brian Wilcox
    • +
  • Błażej Sowa
    • +
  • Carl Delsey
    • +
  • Carlos Orduno
    • +
  • Chittaranjan Srinivas Swaminathan
    • +
  • Chris Iverach-Brereton
    • +
  • Chris Lalancette
    • +
  • Christian Henkel
    • +
  • Christian Rauch
    • +
  • David V. Lu!!
    • +
  • Denis Štogl
    • +
  • Eclipse Foundation, Inc.
    • +
  • Enrique Fernandez
    • +
  • Evan Flynn
    • +
  • Felix Exner
    • +
  • Felix Ruess
    • +
  • Fictionlab
    • +
  • Foxglove
    • +
  • George Stavrinos
    • +
  • Hans-Joachim Krauch
    • +
  • Henning Kayser
    • +
  • Ivan Paunovic
    • +
  • Jacob Perron
    • +
  • Jafar Uruc
    • +
  • Jean-Pierre Busch
    • +
  • Jordan Palacios
    • +
  • Jordi Pages
    • +
  • Jose Mastrangelo
    • +
  • Jose-Luis Blanco-Claraco
    • +
  • Josh Newans
    • +
  • Luis Camero
    • +
  • Luka Juricic
    • +
  • Mamoru Sobue
    • +
  • Marc Alban
    • +
  • Matej Vargovcik
    • +
  • Michael Ferguson
    • +
  • Michael Görner
    • +
  • Michael Jeronimo
    • +
  • Michael Orlov
    • +
  • Michel Hidalgo
    • +
  • Miguel Company
    • +
  • Mike Purvis
    • +
  • Mohammad Haghighipanah
    • +
  • Morgan Quigley
    • +
  • MoveIt Release Team
    • +
  • P. J. Reed
    • +
  • ROS Tooling Working Group
    • +
  • Raghavender Sahdev
    • +
  • Ralph Lange
    • +
  • Rob Fisher
    • +
  • Robert Wilbrandt
    • +
  • Roni Kreinin
    • +
  • STEREOLABS
    • +
  • Shane Loretz
    • +
  • Stefan Laible
    • +
  • Steve Macenski
    • +
  • Séverin Lemaignan
    • +
  • TIAGo PAL support team
    • +
  • TIAGo support team
    • +
  • Tony Baltovski
    • +
  • Victor López
    • +
  • William Woodall
    • +
  • Wolfgang Merkt
    • +
  • mitsudome-r
    • +
  • pradyum
    • +
  • ruess
    • +
  • steve
    • +
+

1 post - 1 participant

+

Read full topic

+ + 2024-12-05T20:17:28Z + 2024-12-05T20:17:28Z + + + audrow + + + + 2024-12-16T20:09:44Z + + + + + discourse.ros.org-topic-40975 + + Clearpath Simulator comes to Gazebo Harmonic :fire: +

Hello everyone,

+

I have successfully ported Clearpath Robotics’s open-source simulator clearpath_simulator into Gazebo Harmonic LTS.

+

Key changes include adding support for Xbox One controllers, support for custom robot.yaml names and automatic Twist message conversion to TwistStamped required by the newer builds of ros2_controllers and Gazebo. The simulator has been tested to work in Ubuntu 22.04 (source build). Presently, only A200 Husky is supported. Version 0.2 will add RGB-D sensor and build testing in Ubuntu 24.04.

+

image

+

To accommodate a number of changes made to almost all the original dependent packages, I have opted to host my derived work separately here: GitHub - Mechazo11/clearpath_simulator_harmonic: A port of Clearpath Simulator, compatible with ROS 2 Jazzy and Gazebo Harmonic

+

A big shout-out to Clearpath Robotics team for making the original simulator publicly available. I hope this work proves valuable to the community. If you have any questions, concerns or would like to contribute please don’t hesitate to reaching out to me.

+

With best regards,
+Azmyin Md. Kamal

+

1 post - 1 participant

+

Read full topic

+ + 2024-12-05T19:42:05Z + 2024-12-05T19:42:05Z + + + azmyin12 + + + + 2024-12-16T20:09:44Z + + + + + discourse.ros.org-topic-40957 + + Expose secure communication only with specified entities +

Hi ROS developers,

+

Asking thoughts and ideas!

+

I think this is more like discussion to explore than a question, I would like to have feedback from the community how to handle this situation to support 3rd party device.

+

Original issue: Expose secure communication only with specified entities. · Issue #326 · ros2/sros2 · GitHub

+

image

+

    +
  • For performance consideration, it would be better to keep the localhost communication in robot without secured authentication nor encryption. (basically it uses localhost in robot system, but some specific nodes to be exposed.)
    • +
+

I am trying to find out what could be best solution to support above requirement with secured communication with sros2.

+

If you have any experience, please enlighten me :pray: :pray: :pray:

+

Regards,
+Tomoya

+

6 posts - 3 participants

+

Read full topic

+ + 2024-12-04T22:10:01Z + 2024-12-04T22:10:01Z + + + tomoyafujita + + + + 2024-12-16T20:09:44Z + + + + + discourse.ros.org-topic-40954 + + Next Client Library WG Meeting: Friday 6th December 2024 8AM PT +

Hi,
+The next meeting of the Client Library Working Group will be this Friday, 6th December 2024 at 8 AM Pacific Time.

+ +

We will be reviewing the charter proposal for the ROS 2 Client Library Working Group and continue the discussions from the previous meetings.

+

2 posts - 1 participant

+

Read full topic

+ + 2024-12-04T18:12:58Z + 2024-12-04T18:12:58Z + + + alsora + + + + 2024-12-16T20:09:44Z + + + + + discourse.ros.org-topic-40932 + + Call for Participation: ROS Deliberation Community Group +

Hello all,

+

After our successful workshop at ROSCon 2024, the ROS Deliberation Community Group is resuming its focus on monthly meetings to engage with the community.

+

For those who were formerly attending the meetings before we spent time preparing for the workshop, the time is right to start attending again! If you are considering attending for the first time, or have never heard of this Community Group before, we look forward to seeing you as well.

+

Either way, we’d like to hear from you all about possible topics for subsequent meetings in the new year. Some initial ideas:

+
    +
  • Putting together a survey document of ROS 2 Deliberation Technologies, very much inspired by the great Nav2 paper.
    • +
  • Collaborating on the development of open-source software tools, or examples using those tools, for robot deliberation.
    • +
  • Presentations from people interested in sharing their work (though we’d like to also have time for working discussions as well).
    • +
+

If anyone wants to share ideas or ask any questions, feel free to post here, or just show up to the next meeting(s)! You can find more information, including how to sign up in this document.

+

3 posts - 2 participants

+

Read full topic

+ + 2024-12-03T02:00:55Z + 2024-12-03T02:00:55Z + + + scastro + + + + 2024-12-16T20:09:44Z + + + + + discourse.ros.org-topic-40931 + + Gazebo Classic and Citadel End of Life [x-post Gazebo Sim Community] +

Original Post

+

Hi Everyone,

+

This is your friendly reminder that as outlined here Gazebo Classic (i.e. Gazebo 11) will officially go end of life on Friday, January 31st, 2025. Gazebo Citadel, our first modern Gazebo LTS release, will go end of life on December 30th, 2024. Gazebo Classic users are advised to transition to an LTS modern Gazebo release as soon as possible (we recommend Gazebo Harmonic, or Gazebo Fortress). We recommend that Gazebo Citadel users also upgrade to either Harmonic or Fortress. Information about currently supported Gazebo versions and support windows, can be found here.

+

What does End of Life Mean?

+

Users often ask us, “what does end of life mean?” To put it briefly, end of life means that the Gazebo team will no longer support that particular Gazebo release. In practical terms, this means that we will no longer be providing the following for Gazebo Classic:

+
    +
  • New features or capabilities
    • +
  • Security updates
    • +
  • Bug fixes, patches or support
    • +
  • Updated binaries
    • +
+

It is also worth noting the things that won’t change after Gazebo Classic goes end of life:

+
    +
  • Gazebo Classic binaries will not suddenly disappear
    • +
  • Users will not need to migrate immediately, but they should migrate as soon as possible
    • +
  • Your project will not suddenly stop working on January 31st
    • +
+

Why do we End of Life Gazebo releases?

+

We End of Life particular Gazebo releases for the same reason that most people don’t use Windows XP or an iPhone 4 anymore: better versions of the software are now available and we simply don’t have the resources to support every Gazebo release into perpetuity. Marking a particular version of Gazebo end of life frees up resources to help support newer and better versions of the software. More to the point, the underlying packages and operating system (Ubuntu Focal) used by Gazebo Classic also goes end of life in April 2025.

+

How do I upgrade to a newer version of Gazebo and which one should I use?

+

We recommend that Gazebo Classic users upgrade to the latest long term support release of modern Gazebo, Gazebo Harmonic. Gazebo Harmonic works best on Ubuntu Jammy (22.04) and Ubuntu Noble (24.04) and will be supported until September of 2028. Gazebo Classic users who still use ROS 1 will also need to upgrade to ROS 2 Jazzy to use Gazebo Harmonic. It is worth noting that all of ROS 1, including ROS 1 Noetic, will go end of life on May 23rd, 2025. Our internal estimates indicate that over 80% of the ROS community has already upgraded to ROS 2, and 67% of Gazebo users have already upgraded to modern Gazebo.

+

The modern Gazebo documentation includes a variety of guides and tutorials on how to migrate your project from Gazebo Classic to modern Gazebo. Similarly, the ROS 2 documentation provides step by step instructions on how to migrate your ROS 1 project to ROS 2. If you get stuck during migration, we would encourage you to use the Open Robotics Discord, the Gazebo Sim Community, and Robotics Stack Exchange to find help.

+

Help Spread the Word

+

We realize that many Gazebo Classic users don’t really track Gazebo end of life dates, or regularly visit Gazebosim Community, that’s why we’ve decided to include some notifications about Gazebo Classic’s impending end of life in our latest Gazebo Classic update. Starting this week, after updating Gazebo Classic users will be notified via debug output and pop-ups of the upcoming end of life date. These warnings can be suppressed by simply setting a “GAZEBO_SUPPRESS_EOL_WARNING” environment variable.

+

We would appreciate the community’s help in spreading the word about the upcoming Gazebo Classic End of Life. If you work on a team that is still using Gazebo Classic please take a moment in the next week or two to discuss upgrade paths with your team and the importance of upgrading as soon as possible.

+

2 posts - 1 participant

+

Read full topic

+ + 2024-12-02T22:01:50Z + 2024-12-02T22:01:50Z + + + Katherine_Scott + + + + 2024-12-16T20:09:45Z + + + + + discourse.ros.org-topic-40908 + + What versions of Moveit 2 are people using? +

I’ve posted a poll on the Moveit 2 discussions board asking for feedback regarding which versions people are using, as it seems like it’d be interesting to gather some quantitative data.

+

Figured I’d post it here, too, for more visibility:

+ + +

1 post - 1 participant

+

Read full topic

+ + 2024-12-01T23:36:10Z + 2024-12-01T23:36:10Z + + + TSNoble + + + + 2024-12-16T20:09:45Z + + + + + discourse.ros.org-topic-40868 + + Interoperability Interest Group December 05, 2024: Use Cases Around Open-RMF and Interoperability by Reply +

Community Page

+

Meeting Link

+

Calendar Link

+

2024-12-05T15:00:00Z UTC

+

This month our friends from Reply will be presenting on work that they’ve been doing on robotics system integration using Open-RMF.

+

2 posts - 2 participants

+

Read full topic

+ + 2024-11-28T15:23:19Z + 2024-11-28T15:23:19Z + + + grey + + + + 2024-12-16T20:09:45Z + + + + + discourse.ros.org-topic-40858 + + Missing documentation for sensors? +

Hey guys, I just migrated from ROS1 to ROS2 and I am running ROS2 Humble Hawksbill with Gazebo Harmonic (ik it’s not the default installation but yeah I pulled Harmonic separately). I am working on a basic project to bring a robot present in my academia to gazebo and I noticed that there is close to no documentation about the list of sensors and how to use them in our xacro files. There is some basic introduction here. But I don’t see any list of sensors and how to use them anywhere. Does this call for creating a well-defined documentation or am I really missing any website?

+

13 posts - 9 participants

+

Read full topic

+ + 2024-11-28T07:09:17Z + 2024-11-28T07:09:17Z + + + vishcomestrue + + + + 2024-12-16T20:09:44Z + + + + + discourse.ros.org-topic-40852 + + OSRF Holiday Donation Drive +

Thanksgiving

+

Hi Everyone,

+

Just a quick note before everyone heads off for the long holiday weekend here in the States. Next Tuesday is Giving Tuesday in the US, a day when many people make their big charitable donations for the holiday season.

+

This year, we’ve set up a donations page for the Open Source Robotics Foundation (OSRF) where you can specifically designate how you’d like your donation to be used. Want to help fund our infrastructure costs? Improve the ROS documentation? Support our educational efforts like the Diversity Scholars Program? Now you can choose!

+

We’re always thankful for your support, whether it’s monetary or a quick pull request! And remember, the OSRF is a 501(c)(3) tax-deductible charitable organization in the US.

+

If you, your colleagues, or your employer would like to support the OSRF and its mission, you can make a one-time or monthly donation using the new page. Many employers match charitable donations during the holiday season, so be sure to check if yours does. Here at Intrinsic, we’ve used our employee match program to raise almost $15,000 for the OSRF. We’d love to see other members of the ROS community join the effort.

+

Finally, please help us spread the word! Our Open Robotics community is huge, and if we all pitched in just a little bit we could make some amazing things happen in 2025.

+

Thank you for your support, and have a wonderful holiday season! :turkey:

+

4 posts - 4 participants

+

Read full topic

+ + 2024-11-27T23:08:07Z + 2024-11-27T23:08:07Z + + + Katherine_Scott + + + + 2024-12-16T20:09:44Z + + + diff --git a/foafroll.xml b/foafroll.xml new file mode 100644 index 00000000..d1a03ecd --- /dev/null +++ b/foafroll.xml @@ -0,0 +1,345 @@ + + + + Open Robotics + + + + Fawkes + + + + + + + + + + + + + William Woodall + + + wjwwood.github.io + + + + + + + + + + David Hodo + + + + + + + + + + + + + Michael Ferguson + + + + + + + + + + + + + ROS news + + + ROS robotics news + + + + + + + + + + mobotica + + + mobotica + + + + + + + + + + Achu Wilson + + + Achu's TechBlog + + + + + + + + + + ASL ETHZ + + + Kommentare zu: + + + + + + + + + + Robbie The Robot + + + Robbie The Robot + + + + + + + + + + NooTriX + + + nootrix + + + + + + + + + + ROS Industrial + + + Blog - ROS-Industrial + + + + + + + + + + Yujin R&D + + + + + + + + + + + + + Isaac Saito + + + ROS Jogger + + + + + + + + + + John Stowers + + + Johns Blog + + + + + + + + + + MobileWill + + + MobileWill + + + + + + + + + + MoveIt! + + + MoveIt Motion Planning Framework + + + + + + + + + + CAR: Components, Agents, and Robots with Dynamic Languages + + + + + + + + + + + + + Open Source Robotics Foundation + + + Open Robotics + + + + + + + + + + PAL Robotics blog + + + + + + + + + + + + + Sachin Chitta's Blog + + + + + + + + + + + + + TORK + + + Tokyo Opensource Robotics Kyokai Association + + + + + + + + + + Pi Robot + + + + + + + + + + + + + ROSVirtual + + + + + + + + + + + + + ROS Discourse General + + + General - ROS Discourse + + + + + + + + + + Mat Sadowski Blog + + + msadowski blog + + + + + + + + + + Robots For Robots + + + RobotsForRobots + + + + + + + + + diff --git a/images/Robot_Head_clip_art.svg b/images/Robot_Head_clip_art.svg new file mode 100644 index 00000000..c38294c0 --- /dev/null +++ b/images/Robot_Head_clip_art.svg @@ -0,0 +1,905 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + image/svg+xml + + robo + + + hrum + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/images/feed-icon-10x10.png b/images/feed-icon-10x10.png new file mode 100644 index 00000000..cc869bc6 Binary files /dev/null and b/images/feed-icon-10x10.png differ diff --git a/images/feed-icon-plus.svg b/images/feed-icon-plus.svg new file mode 100644 index 00000000..4841f7db --- /dev/null +++ b/images/feed-icon-plus.svg @@ -0,0 +1,142 @@ + + + + + + image/svg+xml + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/images/feed-icon.svg b/images/feed-icon.svg new file mode 100644 index 00000000..ce172c26 --- /dev/null +++ b/images/feed-icon.svg @@ -0,0 +1,137 @@ + + + + + + image/svg+xml + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/images/planet_ros.svg b/images/planet_ros.svg new file mode 100644 index 00000000..e7c190c3 --- /dev/null +++ b/images/planet_ros.svg @@ -0,0 +1,153 @@ + + + + + + + + + + image/svg+xml + + + + + + + + + + + + + + + + + + + + + + + diff --git a/images/ros.ico b/images/ros.ico new file mode 100644 index 00000000..0d8a03c5 Binary files /dev/null and b/images/ros.ico differ diff --git a/images/ros_logo.svg b/images/ros_logo.svg new file mode 100644 index 00000000..f808ee4d --- /dev/null +++ b/images/ros_logo.svg @@ -0,0 +1,28 @@ + + + + + + + + + + + + + + + + diff --git a/images/venus.png b/images/venus.png new file mode 100644 index 00000000..685035de Binary files /dev/null and b/images/venus.png differ diff --git a/index.html b/index.html new file mode 100644 index 00000000..70d47f0f --- /dev/null +++ b/index.html @@ -0,0 +1,2360 @@ + + + + + + + + + + + + + + + Planet ROS + + + + + + + + + + + + + +
+ + +
+
+
+ +
+
+ +
+
+
+
+
+ +
+
+ + + + + + +
+
+ +
+ + Subscribe + +
+ 		+
+ +
+ + Instructions + +
+ 		+
+ +
+ + Participants + +
+
+
+
+ + +
+ + +
+ + + + +
+ + +
December 15, 2024
+ + + + + + + + +
+ + +
Is there a ROS 2 gazebo project for humanoids robots?
+ +
from ROS Discourse General
+ +
+ +
+

Dear ROS community,

+

I was researching if there are ROS 2 Gazebo project for humanoid robots that would facilitate in learning robot locomotion and whole-body motion planning. I am looking towards humanoids similar to Unitree’s H1/H2.

+

A research scientist from ETH Zurich pointed me to the Issac Gym environment that comes with the assets for H1/H2. But as far as I understand, that simulation pipeline does not use any ROS, and is meant for RL like research.

+

The closet project I found was Unitree’s ROS 1 project GitHub - unitreerobotics/unitree_ros but it has not been updated for the newer ROS 2 and Gazebo.

+

Thank you for your time.

+

With best,
+Azmyin

+

2 posts - 2 participants

+

Read full topic

+ + + + + + + +
+

+by azmyin12 on December 15, 2024 05:41 AM +

+ +
+ +
December 13, 2024
+ + + + + + + + +
+ + +
Opinion on companies still using ROS1
+ +
from ROS Discourse General
+ +
+ +
+

I would like to read what you think about taking a Job in companies who work extensively with ROS, but for one reason or another they are still in ROS1.
+On one hand I realize that ROS is just a framework and that a lot can still be done and learned.
+On the other, having worked for some years on both ROS and ROS2 I see the benefits of working with ROS2.
+So I am torn and would like to hear other voices on the matter.

+

6 posts - 4 participants

+

Read full topic

+ + + + + + + +
+

+by iony_m on December 13, 2024 10:48 PM +

+ +
+ + + + + + + + + +
+ + +
ROS News for the Week of December 9th, 2024
+ +
from ROS Discourse General
+ +
+ +
+

ROS News for the Week of December 9th, 2024

+
+

image

+:cn: :tada: Our first ever ROSCon in China happened in Shanghai over the weekend! We want to congratulate the organizers on orchestrating such an impressive event. You can find a recap of ROSCon China here.
+

+

May 2023 - Nov 2024

+ROS 2 Iron Irwini is now officially end-of-life. If you are currently using Iron please consider upgrading to Jazzy!

+
+

harp2
+Check out the HARP2 robot that was posted to the ROS Discord server yesterday. The developer’s website is full of really great posts that are worth checking out, especially on the topic of microROS.

+
+

poster-thumbnail

+The team behind TidyBot2 at Stanford and Princeton have open sourced the hardware for their robot. The robot supports a variety of arms and configurations allowing you to build a clone using hardware you may already have in the lab. See the docs for more details.

+
+

image

+This week ROS Industrial released a comprehensive list of depth cameras for robotics applications. Even if you don’t need a new depth camera I recommend bookmarking this website for future website.

+
+

image

+I want to send a big shout out @abaeyens for putting together this fantastic documentation on ROS 2 integration testing for docs.ros.org. :tada:

+

People often ask us how they can best contribute to the project. My recommendation is that when you run across something that feels not poorly documented take the time to summarize what you learned while figuring out how to solve the problem. That’s exactly what @abaeyens
+did in this case and the results are excellent.

+
+

Events

+ +

News

+ +

ROS

+ +

Got a minute? :alarm_clock:

+

All we want for Christmas are pull requests to the ROS 2 docs. :gift:

+

1 post - 1 participant

+

Read full topic

+ + + + + + + +
+

+by Katherine_Scott on December 13, 2024 08:21 PM +

+ +
+ + + + + + + + + +
+ + +
Call for “IFR’s Women in Robotics: 10 Women Shaping the Future of Robotics in 2025” is now open
+ +
from ROS Discourse General
+ +
+ +
+

Call for “IFR’s Women in Robotics: 10 Women Shaping the Future of Robotics in 2025” is now open

+

The International Federation of Robotics (IFR) is looking for outstanding women in robotics

+

Dec 10, 2024 — IFR would like to highlight and honor Women in Robotics - in particular women in the robotics industry - and give them more visibility. IFR will select a list of 10 women to officially award as “IFR’s Women in Robotics: 10 Women Shaping the Future of Robotics” in 2025.

+

+

IFR decided to give women in robotics more visibility and acknowledgment. This should inspire girls and young women to pursue a career in STEM subjects or robotics and will also help companies to reach gender equality and overcome shortage of staff.

+

IFR would like to highlight and honor Women in Robotics - in particular women in the robotics industry - and give them more visibility.
+IFR will select a list of 10 women to officially award as “IFR’s Women in Robotics: 10 Women Shaping the Future of Robotics” in 2025.

+

IRF is in particular looking for women that have either a proven track record in robotics, stand out as industry leader or women with a proven activity in encouraging young people to go into STEM or that somehow support females in robotics.

+

Deadline for submission is January 31st, 2025.

+

How to submit a suggestion

+

Send an email to secretariat@ifr.org
+include a short bio and a description of what makes her noteworthy or particular with respect to our described scope
+add her full name, affiliation, country, contact details and a photo

+

Selection criteria:

+
    +
  • The suggested women needs to be active in the robotics industry
    • +
  • IFR will select at least one per continent,
    • +
  • but a maximum of one woman per company,
    • +
  • consider different company sizes (large, medium, small)
    • +
  • consider different company scope (Robot supplier IR, SR, component supplier, integrator) and
    • +
  • consider different levels of hierarchy (C-level, intermediate, lower level)
    • +
  • Proven track record in robotics / stand out as industry leader
    • +
  • Proven activity in encouraging young people to go into STEM or that somehow support females in robotics
    • +
+

Publication of results will be on International Women’s Day - March 8th, 2025.

+

IFR’s 2024 Women in Robotics

+

Learn more on why gender balance is beneficial for economies

+ +

1 post - 1 participant

+

Read full topic

+ + + + + + + +
+

+by ThiloZimmermann on December 13, 2024 08:38 AM +

+ +
+ +
December 12, 2024
+ + + + + + + + +
+ + +
REUSE compatibility vs multi-package repo
+ +
from ROS Discourse General
+ +
+ +
+

Hi. I’ve started trying to have my repos REUSE-compliant.

+

It seems that single-package repos can easily be turned into REUSE-compliant by adding all the SPDX comments to files, moving the top-level LICENSE file into LICENSES/BSD-3-Clause.txt and specifying <license file="LICENSES/BSD-3-Clause.txt">BSD</license> in package.xml.

+

However, if I want to do the same for a multi-package repo, then the LICENSES folder has to be a top-level one, i.e. at the same level as are the packages (that is a REUSE requirement). At the same time, I’d like to not have to copy all licenses to each package - as it’s best if each is stored only once. However, if I put <license file="../LICENSES/BSD-3-Clause.txt"> in package.xml, then bloom-release fails not being able to find the license file. That’s because it builds each package from the repo in a separate directory that is moved outside the repo.

+

I don’t see a clean solution how to satisfy both REUSE and bloom (except not adding the file= attribute, but I’d like to keep it). My current dirty workaround is to just copy the license file into the root of each subpackage. That’s not nice, but it does the job.

+

Does anybody know of a cleaner solution? I think it would be very nice if ROS deployment process would be compatible with REUSE.

+

5 posts - 3 participants

+

Read full topic

+ + + + + + + +
+

+by peci1 on December 12, 2024 03:19 PM +

+ +
+ +
December 11, 2024
+ + + + + + + + +
+ + +
Optimizations cpp ROS2 node. colcon build
+ +
from ROS Discourse General
+ +
+ +
+

I’ve been using ROS2 for a year. Maybe previously you guys talked about this. However I’ve done experimental tests about the optimization C++ code ROS2 node and wrote a simple node.

+
#include "rclcpp/rclcpp.hpp"
+
+class HelloWorldNode : public rclcpp::Node
+{
+public:
+    HelloWorldNode() : Node("hello_world_node")
+    {
+        RCLCPP_INFO(this->get_logger(), "Hello, World! This is a ROS2 node.");
+    }
+};
+
+int main(int argc, char **argv)
+{
+    rclcpp::init(argc, argv);
+    rclcpp::spin(std::make_shared<HelloWorldNode>());
+    rclcpp::shutdown();
+    return 0;
+}
+
+
+

Then by simply building the above code by using

+
colcon build
+
+

I got hello_node then explored assemble code

+
objdump -d <path>/hello_node > hello_node.asm
+
+

got around 5000 lines of instruction code in hello_node.asm, it seems like it didn’t do any optimization to the code. Then run the following command

+
colcon build --cmake-args -DCMAKE_BUILD_TYPE=Release
+///alternative
+colcon build --cmake-args -DCMAKE_CXX_FLAGS="-O3 -march=native"
+
+
+

then looked number instructions lines the number dramatically decreased from 5000 to 1700. the number of instruction lines in assemble doesn’t always mean it’s optimized yet it’s good factor.

+

Screenshot from 2024-12-11 16-24-11

+

“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”"
+simple by adding “set(CMAKE_BUILD_TYPE Release)” to your CMakeLists.txt is enough. then you can simply use colcon build.
+Optimizations flags

+

8 posts - 7 participants

+

Read full topic

+ + + + + + + +
+

+by Dony on December 11, 2024 08:32 AM +

+ +
+ +
December 10, 2024
+ + + + + + + + +
+ + +
:checkered_flag: Gazebo Garden officially end-of-life [x-post Gazebo Sim Community]
+ +
from ROS Discourse General
+ +
+ +
+

Original Post

+

Dear ROS Community,

+

Gazebo Garden has reached end-of-life (EOL) as of November, 2024. Garden was the seventh major release of Gazebo and was supported for two years (non-LTS). It was the first release where Ignition was renamed Gazebo. It also introduced various exciting features, including custom shader plugins, Reset API, DEM support, lunar and custom surface coordinates, glTF and GLB mesh support, and an acoustic communication plugin, just to name a few. See the entire list of features on the Release Features page.

+

We recommend all Garden users migrate to a supported release as soon as possible, such as Harmonic (LTS) or Ionic, which are paired with ROS Jazzy and Rolling (Kilted once released) respectively. Migrating to either Harmonic or Ionic should be fairly smooth, however, be sure to check the release highlights for Harmonic and Ionic in addition to checking each Gazebo library’s migration guide.

+

As part of the Garden EOL, the following Gazebo libraries have also reached end-of-life. Their latest released binaries will remain available at http://packages.osrfoundation.org/, but no more fixes or releases will be made.

+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Library major versionFinal release
gz-fuel-tools88.2.0
gz-sim77.9.0
gz-gui77.2.2
gz-launch66.2.0
gz-msgs99.5.1
gz-physics66.7.0
gz-rendering77.5.0
gz-sensors77.3.1
gz-transport1212.2.2
sdformat1313.9.0
+

We sincerely thank all contributors to all libraries in Garden :pray:

+

What does End of Life Mean?

+

Users often ask us, “what does end of life mean?” To put it briefly, end of life means that the Gazebo team will no longer support that particular Gazebo release. In practical terms, this means that we will no longer be providing the following for Gazebo Garden:

+
    +
  • New features or capabilities
    • +
  • Security updates
    • +
  • Bug fixes, patches or support
    • +
  • Updated binaries
    • +
+

It is also worth noting the things that won’t change after Gazebo Garden goes end of life:

+
    +
  • Gazebo Garden binaries will not suddenly disappear
    • +
  • Users will not need to migrate immediately, but they should migrate as soon as possible
    • +
+

:gazebo: Gazebo Dev Team :gazebo:

+

1 post - 1 participant

+

Read full topic

+ + + + + + + +
+

+by azeey on December 10, 2024 11:14 PM +

+ +
+ + + + + + + + + +
+ + +
How important is ROS when searching for a job?
+ +
from ROS Discourse General
+ +
+ +
+

I have made an analysis of almost 2.000 jobs in LinkedIn and found out how relevant is ROS for getting a job as a robotics software developer. I included other interesting data about what matters for companies posting robotics jobs.

+

Check all that data in this video: https://youtu.be/wDeVNsD73A4?si=wcD3F1FizuJ52K3e

+

Podcast-video-2024-Ricardo-Tellez-the-truth-about-ROS-jobs

+

1 post - 1 participant

+

Read full topic

+ + + + + + + +
+

+by ricardotellez on December 10, 2024 08:43 AM +

+ +
+ + + + + + + + + +
+ + +
Iron Irwini is End-of-Life
+ +
from ROS Discourse General
+ +
+ +
+

Dear ROS Community,

+

It is bitter-sweet to announce that ROS 2 Iron Irwini is now end-of-life.

+

ROS 2 Iron Irwini

+

Iron Irwini was released on May 23rd 2023 and marked the ninth distribution of ROS 2. Despite being a non-LTS release, it was feature packed (see more).

+

Over the past year and half, there have been 40 distro syncs and 7 patch releases that cumulatively brought thousands of packages and updates to the community.

+

The last patch and sync (tagged iron/2024-12-04) brought 6 new packages and 320 updates.

+Expand for details of the final sync (click for more details) +

The distribution has been marked end-of-life across docs.ros.org, index.ros.org and rosdistro. CI and Buildfarm jobs have been disabled and will be deleted after a month assuming no issues crop up. The final snapshot of the distribution has been uploaded to snapshots.ros.org. If you are currently using Iron, please switch to Jazzy Jalisco which is the latest LTS release. The transition should be very smooth.

+

It has been a great privilege of mine to serve as the ROS Boss for Iron Irwini especially given that Steve Irwin was my childhood hero. A big thank you to all ROS maintainers and community members for making Iron Irwini such a successful release! :iron: :irwini:

+

-Yadu

+

2 posts - 2 participants

+

Read full topic

+ + + + + + + +
+

+by Yadunund on December 10, 2024 07:36 AM +

+ +
+ +
December 09, 2024
+ + + + + + + + +
+ + +
Guest Talk by Tomoya Fujita - Cloud Robotics WG Meeting 2024-12-16
+ +
from ROS Discourse General
+ +
+ +
+

Please come and join us for this coming meeting at 1700-1800 UTC on Monday 16th December 2024, where Tomoya Fujita will be talking about Robotics Platforms empowered by Cloud-Native Technologies.

+

Tomoya is a software engineer, contributor to ROS2 core, and well-respected community builder. In this session, he will talk about a range of Cloud-Native Technologies he has worked on, and their relevance to robotics. In particular, Tomoya has done a great deal of work on KubeEdge, a platform built on Kubernetes that can be used to deploy software to robots as if they are Kubernetes clusters. Some resources from his talk includes:

+ +

Tomoya also plans to leave time to discuss Cloud Robotics with the group, particularly the problems that people are having with Cloud Robotics.

+

Last meeting, we worked through a workshop for Eclipse Zenoh to test its capabilities and ease of setup. If you’re interested to see our progress, please check the meeting recording.

+

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

+

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

+

Hopefully we will see you there!

+

1 post - 1 participant

+

Read full topic

+ + + + + + + +
+

+by mikelikesrobots on December 09, 2024 02:58 PM +

+ +
+ +
December 08, 2024
+ + + + + + + + +
+ + +
Robotics engineers are in high demand — but what is the job really like?
+ +
from ROS Discourse General
+ +
+ +
+

Robotics engineers are in high demand — but what is the job really like?

+ +

2 posts - 1 participant

+

Read full topic

+ + + + + + + +
+

+by ruffsl on December 08, 2024 11:32 PM +

+ +
+ +
December 06, 2024
+ + + + + + + + +
+ + +
ROS News for the Week of December 2nd, 2024
+ +
from ROS Discourse General
+ +
+ +
+

ROS News for the Week of December 2nd, 2024

+

GeCwHKiX0AAHleo
Gd-rDnlW4AAsP38

+ROSCon Germany and ROSCon India were both this week! It was really exciting to see two ROS events happening concurrently on two different parts of the globe. We want to congratulate the organizers and attendees on putting together fantastic events.

+ +

ROSCon_China_2024

+But wait, there’s more! Our first ever ROSCon China in Shanghai is about to kick off in about four or five hours.

+
+

9cqsf8

+While we’re welcoming so many new friends to the ROS community we’re also getting ready to say farewell to ROS 1 Noetic, Gazebo Classic, Gazebo Citadel, and ROS 2 Iron Irwini.

+
+

SGDecROSMeetup

+We have two ROS Meetups planned for 2024-12-12. One meetup in Singapore and another one in Barcelona Spain

+
+

Thanksgiving

+If you are in a giving mood this holiday season we are currently running a donation campaign for the OSRF. We’ve made it possible for you to earmark your donation for particular OSRF projects like the ROS Build Farm, the ROS Documentation, and our educational outreach initiatives.

+
+

Aug24GCM (1)

+At last week’s Gazebo Community Meeting we met multiple competitors from the NASA SpaceROS Summer Sprint Challenge. The results are absolutely amazing and are all open source! We recommend you check it out.

+

Events

+ +

News

+ +

ROS

+ +

Got a Minute? :alarm_clock:

+

We would really appreciate it if you took ten minutes to answer just one ROS question on Robotics Stack Exchange.

+

1 post - 1 participant

+

Read full topic

+ + + + + + + +
+

+by Katherine_Scott on December 06, 2024 08:59 PM +

+ +
+ + + + + + + + + +
+ + +
rmw_iceoryx2 v0.1.0 release
+ +
from ROS Discourse General
+ +
+ +
+

Hi all,

+

orecham here, one of the committers from the eclipse-iceoryx project.

+

I’m pleased to announce the alpha release of rmw_iceoryx2, compatible with ROS 2 rolling and available at: GitHub - ekxide/rmw_iceoryx2: ROS 2 RMW implementation for iceoryx2

+

Why yet another RMW? We have the following goals for rmw_iceoryx2:

+
    +
  1. Bring the high-performance zero-copy shared-memory communication offered by iceoryx2 to ROS 2 applications
    2. +
  2. Provide a unique option for reducing safety certification effort of ROS 2 applications with safety-critical use-cases
    3. +
+

Rather than require the entire ROS 2 stack be certified (e.g. for ASIL-D), rmw_iceoryx2 offers an alternative through interoperability between ROS 2 and iceoryx2 applications. This allows the freedom for porting safety-critical components that require certification to iceoryx2 (which is designed for certification) while still participating in the ROS 2 ecosystem.

+

Current State

+

With this first alpha release, there is still some work to do and polish to be made. Not all features are yet available and existing ones need thorough real-world validation. Most notably, support for message serialization is not yet available nor service-client communication (waiting on some features to be completed in iceoryx2). Lack of serialization support means that rmw_iceoryx2 can currently only work with self-contained message types, however, this will be one of the first limitations to address next.

+

Furthermore, only intra-host communication is currently possible. We have plans to introduce host-to-host capabilities in the near future by leveraging existing host-to-host-capable middlewares. Some more info about this is available in the README.

+

Performance

+

The current performance_test results are as follow. There is still quite a bit of room for improvement compared to raw iceoryx2:

+

v0.1.0

+

Contributing and Feedback

+

We look forward to your feedback! Input from real-world application configurations will be invaluable for bringing rmw_iceoryx2 to stability. Additionally, insights from those experienced with RMW implementations would greatly help improve quality. The current state was achieved using only the information available in the RMW documentation, thus there may be some edge-cases known to veterans which are not properly addressed.

+

For those who have the capacity to get involved with implementation, we welcome all contributions! We will provide as much support as needed to those who are interested.

+

Thanks for reading!
+Cheers

+

1 post - 1 participant

+

Read full topic

+ + + + + + + +
+

+by orecham on December 06, 2024 08:29 PM +

+ +
+ + + + + + + + + +
+ + +
New Packages for Noetic 2024-12-06
+ +
from ROS Discourse General
+ +
+ +
+

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

+

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

+

Package Updates for ROS Noetic

+

Added Packages [2]:

+ +

Updated Packages [46]:

+
    +
  • ros-noetic-ess-imu-driver: 2.0.1-1 → 2.0.2-1
    • +
  • ros-noetic-etsi-its-cam-coding: 2.3.0-1 → 2.4.0-1
    • +
  • ros-noetic-etsi-its-cam-conversion: 2.3.0-1 → 2.4.0-1
    • +
  • ros-noetic-etsi-its-cam-msgs: 2.3.0-1 → 2.4.0-1
    • +
  • ros-noetic-etsi-its-cam-ts-coding: 2.3.0-1 → 2.4.0-1
    • +
  • ros-noetic-etsi-its-cam-ts-conversion: 2.3.0-1 → 2.4.0-1
    • +
  • ros-noetic-etsi-its-cam-ts-msgs: 2.3.0-1 → 2.4.0-1
    • +
  • ros-noetic-etsi-its-coding: 2.3.0-1 → 2.4.0-1
    • +
  • ros-noetic-etsi-its-conversion: 2.3.0-1 → 2.4.0-1
    • +
  • ros-noetic-etsi-its-cpm-ts-coding: 2.3.0-1 → 2.4.0-1
    • +
  • ros-noetic-etsi-its-cpm-ts-conversion: 2.3.0-1 → 2.4.0-1
    • +
  • ros-noetic-etsi-its-cpm-ts-msgs: 2.3.0-1 → 2.4.0-1
    • +
  • ros-noetic-etsi-its-denm-coding: 2.3.0-1 → 2.4.0-1
    • +
  • ros-noetic-etsi-its-denm-conversion: 2.3.0-1 → 2.4.0-1
    • +
  • ros-noetic-etsi-its-denm-msgs: 2.3.0-1 → 2.4.0-1
    • +
  • ros-noetic-etsi-its-messages: 2.3.0-1 → 2.4.0-1
    • +
  • ros-noetic-etsi-its-msgs: 2.3.0-1 → 2.4.0-1
    • +
  • ros-noetic-etsi-its-msgs-utils: 2.3.0-1 → 2.4.0-1
    • +
  • ros-noetic-etsi-its-primitives-conversion: 2.3.0-1 → 2.4.0-1
    • +
  • ros-noetic-etsi-its-rviz-plugins: 2.3.0-1 → 2.4.0-1
    • +
  • ros-noetic-etsi-its-vam-ts-coding: 2.3.0-1 → 2.4.0-1
    • +
  • ros-noetic-etsi-its-vam-ts-conversion: 2.3.0-1 → 2.4.0-1
    • +
  • ros-noetic-etsi-its-vam-ts-msgs: 2.3.0-1 → 2.4.0-1
    • +
  • ros-noetic-foxglove-bridge: 0.7.10-1 → 0.8.1-1
    • +
  • ros-noetic-inorbit-republisher: 0.3.0-1 → 0.3.2-1
    • +
  • ros-noetic-nodelet: 1.11.0-2 → 1.11.1-1
    • +
  • ros-noetic-nodelet-core: 1.11.0-2 → 1.11.1-1
    • +
  • ros-noetic-nodelet-topic-tools: 1.11.0-2 → 1.11.1-1
    • +
  • ros-noetic-rc-reason-clients: 0.3.1-1 → 0.4.0-2
    • +
  • ros-noetic-rc-reason-msgs: 0.3.1-1 → 0.4.0-2
    • +
  • ros-noetic-rtabmap: 0.21.6-1 → 0.21.9-1
    • +
  • ros-noetic-rtabmap-conversions: 0.21.5-1 → 0.21.9-1
    • +
  • ros-noetic-rtabmap-costmap-plugins: 0.21.5-1 → 0.21.9-1
    • +
  • ros-noetic-rtabmap-demos: 0.21.5-1 → 0.21.9-1
    • +
  • ros-noetic-rtabmap-examples: 0.21.5-1 → 0.21.9-1
    • +
  • ros-noetic-rtabmap-launch: 0.21.5-1 → 0.21.9-1
    • +
  • ros-noetic-rtabmap-legacy: 0.21.5-1 → 0.21.9-1
    • +
  • ros-noetic-rtabmap-msgs: 0.21.5-1 → 0.21.9-1
    • +
  • ros-noetic-rtabmap-odom: 0.21.5-1 → 0.21.9-1
    • +
  • ros-noetic-rtabmap-python: 0.21.5-1 → 0.21.9-1
    • +
  • ros-noetic-rtabmap-ros: 0.21.5-1 → 0.21.9-1
    • +
  • ros-noetic-rtabmap-rviz-plugins: 0.21.5-1 → 0.21.9-1
    • +
  • ros-noetic-rtabmap-slam: 0.21.5-1 → 0.21.9-1
    • +
  • ros-noetic-rtabmap-sync: 0.21.5-1 → 0.21.9-1
    • +
  • ros-noetic-rtabmap-util: 0.21.5-1 → 0.21.9-1
    • +
  • ros-noetic-rtabmap-viz: 0.21.5-1 → 0.21.9-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:

+
    +
  • Felix Ruess
    • +
  • Geoffrey Biggs
    • +
  • Hans-Joachim Krauch
    • +
  • InOrbit
    • +
  • Jean-Pierre Busch
    • +
  • Marc Alban
    • +
  • Martin Pecka
    • +
  • Mathieu Labbe
    • +
  • Raymond Chow
    • +
+

2 posts - 2 participants

+

Read full topic

+ + + + + + + +
+

+by sloretz on December 06, 2024 06:09 PM +

+ +
+ + + + + + + + + +
+ + +
Open-RMF PMC Timing Change for 2024-12-17
+ +
from ROS Discourse General
+ +
+ +
+

Due to a one-time scheduling conflict, the Open-RMF Project Management Committee session that is normally scheduled for 2024-12-17T01:00:00Z UTC will instead take place one hour later at 2024-12-17T02:00:00Z UTC. This change is reflected in the official OSRF events calendar.

+

Sessions will return to the normal time afterwards.

+

1 post - 1 participant

+

Read full topic

+ + + + + + + +
+

+by grey on December 06, 2024 08:46 AM +

+ +
+ +
December 05, 2024
+ + + + + + + + +
+ + +
New packages and patch release for Humble Hawksbill 2024-12-05
+ +
from ROS Discourse General
+ +
+ +
+

We’re happy to announce a new Humble release!

+

This sync brings several new packages and some updates to ROS 2 core packages. (I haven’t included the project board for patch info because there was nothing on it.)

+

Package Updates for Humble

+

Added Packages [34]:

+
    +
  • ros-humble-adi-3dtof-image-stitching: 2.1.0-1
    • +
  • ros-humble-adi-3dtof-image-stitching-dbgsym: 2.1.0-1
    • +
  • ros-humble-axis-camera: 2.0.3-1
    • +
  • ros-humble-axis-description: 2.0.3-1
    • +
  • ros-humble-axis-msgs: 2.0.3-1
    • +
  • ros-humble-axis-msgs-dbgsym: 2.0.3-1
    • +
  • ros-humble-camera-info-manager-py: 3.1.10-1
    • +
  • ros-humble-clearpath-motor-msgs: 1.0.1-1
    • +
  • ros-humble-clearpath-motor-msgs-dbgsym: 1.0.1-1
    • +
  • ros-humble-clearpath-ros2-socketcan-interface: 1.0.0-1
    • +
  • ros-humble-clearpath-ros2-socketcan-interface-dbgsym: 1.0.0-1
    • +
  • ros-humble-dual-laser-merger: 0.1.1-1
    • +
  • ros-humble-dual-laser-merger-dbgsym: 0.1.1-1
    • +
  • ros-humble-hatchbed-common: 0.1.1-1
    • +
  • ros-humble-hri-face-body-matcher: 2.1.0-1
    • +
  • ros-humble-hri-face-body-matcher-dbgsym: 2.1.0-1
    • +
  • ros-humble-hri-privacy-msgs: 1.2.0-1
    • +
  • ros-humble-hri-privacy-msgs-dbgsym: 1.2.0-1
    • +
  • ros-humble-jacro: 0.2.0-1
    • +
  • ros-humble-laser-segmentation: 3.0.2-1
    • +
  • ros-humble-laser-segmentation-dbgsym: 3.0.2-1
    • +
  • ros-humble-log-view: 0.2.5-1
    • +
  • ros-humble-log-view-dbgsym: 0.2.5-1
    • +
  • ros-humble-pose-broadcaster: 2.38.0-1
    • +
  • ros-humble-pose-broadcaster-dbgsym: 2.38.0-1
    • +
  • ros-humble-ptz-action-server-msgs: 2.0.3-1
    • +
  • ros-humble-ptz-action-server-msgs-dbgsym: 2.0.3-1
    • +
  • ros-humble-rosbag2-to-video: 1.0.1-1
    • +
  • ros-humble-simple-grasping: 0.5.0-1
    • +
  • ros-humble-simple-grasping-dbgsym: 0.5.0-1
    • +
  • ros-humble-slg-msgs: 3.9.1-1
    • +
  • ros-humble-slg-msgs-dbgsym: 3.9.1-1
    • +
  • ros-humble-zed-msgs: 4.2.2-1
    • +
  • ros-humble-zed-msgs-dbgsym: 4.2.2-1
    • +
+

Updated Packages [580]:

+
    +
  • ros-humble-ackermann-steering-controller: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-ackermann-steering-controller-dbgsym: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-adi-tmcl: 2.0.0-1 → 2.0.3-2
    • +
  • ros-humble-adi-tmcl-dbgsym: 2.0.0-1 → 2.0.3-2
    • +
  • ros-humble-admittance-controller: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-admittance-controller-dbgsym: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-ament-cmake: 1.3.10-1 → 1.3.11-1
    • +
  • ros-humble-ament-cmake-auto: 1.3.10-1 → 1.3.11-1
    • +
  • ros-humble-ament-cmake-core: 1.3.10-1 → 1.3.11-1
    • +
  • ros-humble-ament-cmake-export-definitions: 1.3.10-1 → 1.3.11-1
    • +
  • ros-humble-ament-cmake-export-dependencies: 1.3.10-1 → 1.3.11-1
    • +
  • ros-humble-ament-cmake-export-include-directories: 1.3.10-1 → 1.3.11-1
    • +
  • ros-humble-ament-cmake-export-interfaces: 1.3.10-1 → 1.3.11-1
    • +
  • ros-humble-ament-cmake-export-libraries: 1.3.10-1 → 1.3.11-1
    • +
  • ros-humble-ament-cmake-export-link-flags: 1.3.10-1 → 1.3.11-1
    • +
  • ros-humble-ament-cmake-export-targets: 1.3.10-1 → 1.3.11-1
    • +
  • ros-humble-ament-cmake-gen-version-h: 1.3.10-1 → 1.3.11-1
    • +
  • ros-humble-ament-cmake-gmock: 1.3.10-1 → 1.3.11-1
    • +
  • ros-humble-ament-cmake-google-benchmark: 1.3.10-1 → 1.3.11-1
    • +
  • ros-humble-ament-cmake-gtest: 1.3.10-1 → 1.3.11-1
    • +
  • ros-humble-ament-cmake-include-directories: 1.3.10-1 → 1.3.11-1
    • +
  • ros-humble-ament-cmake-libraries: 1.3.10-1 → 1.3.11-1
    • +
  • ros-humble-ament-cmake-nose: 1.3.10-1 → 1.3.11-1
    • +
  • ros-humble-ament-cmake-pytest: 1.3.10-1 → 1.3.11-1
    • +
  • ros-humble-ament-cmake-python: 1.3.10-1 → 1.3.11-1
    • +
  • ros-humble-ament-cmake-target-dependencies: 1.3.10-1 → 1.3.11-1
    • +
  • ros-humble-ament-cmake-test: 1.3.10-1 → 1.3.11-1
    • +
  • ros-humble-ament-cmake-vendor-package: 1.3.10-1 → 1.3.11-1
    • +
  • ros-humble-ament-cmake-version: 1.3.10-1 → 1.3.11-1
    • +
  • ros-humble-autoware-lanelet2-extension: 0.6.0-1 → 0.6.2-1
    • +
  • ros-humble-autoware-lanelet2-extension-dbgsym: 0.6.0-1 → 0.6.2-1
    • +
  • ros-humble-autoware-lanelet2-extension-python: 0.6.0-1 → 0.6.2-1
    • +
  • ros-humble-autoware-lanelet2-extension-python-dbgsym: 0.6.0-1 → 0.6.2-1
    • +
  • ros-humble-backward-ros: 1.0.5-1 → 1.0.6-1
    • +
  • ros-humble-backward-ros-dbgsym: 1.0.5-1 → 1.0.6-1
    • +
  • ros-humble-bicycle-steering-controller: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-bicycle-steering-controller-dbgsym: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-bosch-locator-bridge: 2.1.11-1 → 2.1.13-1
    • +
  • ros-humble-bosch-locator-bridge-dbgsym: 2.1.11-1 → 2.1.13-1
    • +
  • ros-humble-bosch-locator-bridge-utils: 2.1.11-1 → 2.1.13-1
    • +
  • ros-humble-bosch-locator-bridge-utils-dbgsym: 2.1.11-1 → 2.1.13-1
    • +
  • ros-humble-camera-calibration-parsers: 3.1.9-1 → 3.1.10-1
    • +
  • ros-humble-camera-calibration-parsers-dbgsym: 3.1.9-1 → 3.1.10-1
    • +
  • ros-humble-camera-info-manager: 3.1.9-1 → 3.1.10-1
    • +
  • ros-humble-camera-info-manager-dbgsym: 3.1.9-1 → 3.1.10-1
    • +
  • ros-humble-camera-ros: 0.1.0-2 → 0.2.0-1
    • +
  • ros-humble-camera-ros-dbgsym: 0.1.0-2 → 0.2.0-1
    • +
  • ros-humble-chomp-motion-planner: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-chomp-motion-planner-dbgsym: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-clearpath-common: 0.3.4-1 → 1.0.0-1
    • +
  • ros-humble-clearpath-config: 0.3.4-1 → 1.0.0-1
    • +
  • ros-humble-clearpath-config-live: 0.3.0-1 → 1.0.0-1
    • +
  • ros-humble-clearpath-control: 0.3.4-1 → 1.0.0-1
    • +
  • ros-humble-clearpath-customization: 0.3.4-1 → 1.0.0-1
    • +
  • ros-humble-clearpath-description: 0.3.4-1 → 1.0.0-1
    • +
  • ros-humble-clearpath-desktop: 0.3.0-1 → 1.0.0-1
    • +
  • ros-humble-clearpath-generator-common: 0.3.4-1 → 1.0.0-1
    • +
  • ros-humble-clearpath-generator-common-dbgsym: 0.3.4-1 → 1.0.0-1
    • +
  • ros-humble-clearpath-generator-gz: 0.3.0-1 → 1.0.0-1
    • +
  • ros-humble-clearpath-gz: 0.3.0-1 → 1.0.0-1
    • +
  • ros-humble-clearpath-manipulators: 0.3.4-1 → 1.0.0-1
    • +
  • ros-humble-clearpath-manipulators-description: 0.3.4-1 → 1.0.0-1
    • +
  • ros-humble-clearpath-mounts-description: 0.3.4-1 → 1.0.0-1
    • +
  • ros-humble-clearpath-msgs: 1.0.0-1 → 1.0.1-1
    • +
  • ros-humble-clearpath-nav2-demos: 0.2.0-1 → 1.0.0-1
    • +
  • ros-humble-clearpath-platform-description: 0.3.4-1 → 1.0.0-1
    • +
  • ros-humble-clearpath-platform-msgs: 1.0.0-1 → 1.0.1-1
    • +
  • ros-humble-clearpath-platform-msgs-dbgsym: 1.0.0-1 → 1.0.1-1
    • +
  • ros-humble-clearpath-sensors-description: 0.3.4-1 → 1.0.0-1
    • +
  • ros-humble-clearpath-simulator: 0.3.0-1 → 1.0.0-1
    • +
  • ros-humble-clearpath-viz: 0.3.0-1 → 1.0.0-1
    • +
  • ros-humble-control-msgs: 4.6.0-1 → 4.7.0-1
    • +
  • ros-humble-control-msgs-dbgsym: 4.6.0-1 → 4.7.0-1
    • +
  • ros-humble-controller-interface: 2.43.1-1 → 2.44.0-1
    • +
  • ros-humble-controller-interface-dbgsym: 2.43.1-1 → 2.44.0-1
    • +
  • ros-humble-controller-manager: 2.43.1-1 → 2.44.0-1
    • +
  • ros-humble-controller-manager-dbgsym: 2.43.1-1 → 2.44.0-1
    • +
  • ros-humble-controller-manager-msgs: 2.43.1-1 → 2.44.0-1
    • +
  • ros-humble-controller-manager-msgs-dbgsym: 2.43.1-1 → 2.44.0-1
    • +
  • ros-humble-costmap-queue: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-costmap-queue-dbgsym: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-cyclonedds: 0.10.4-1 → 0.10.5-2
    • +
  • ros-humble-cyclonedds-dbgsym: 0.10.4-1 → 0.10.5-2
    • +
  • ros-humble-depthai-bridge: 2.10.3-1 → 2.10.4-1
    • +
  • ros-humble-depthai-bridge-dbgsym: 2.10.3-1 → 2.10.4-1
    • +
  • ros-humble-depthai-descriptions: 2.10.3-1 → 2.10.4-1
    • +
  • ros-humble-depthai-examples: 2.10.3-1 → 2.10.4-1
    • +
  • ros-humble-depthai-examples-dbgsym: 2.10.3-1 → 2.10.4-1
    • +
  • ros-humble-depthai-filters: 2.10.3-1 → 2.10.4-1
    • +
  • ros-humble-depthai-filters-dbgsym: 2.10.3-1 → 2.10.4-1
    • +
  • ros-humble-depthai-ros: 2.10.3-1 → 2.10.4-1
    • +
  • ros-humble-depthai-ros-driver: 2.10.3-1 → 2.10.4-1
    • +
  • ros-humble-depthai-ros-driver-dbgsym: 2.10.3-1 → 2.10.4-1
    • +
  • ros-humble-depthai-ros-msgs: 2.10.3-1 → 2.10.4-1
    • +
  • ros-humble-depthai-ros-msgs-dbgsym: 2.10.3-1 → 2.10.4-1
    • +
  • ros-humble-diff-drive-controller: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-diff-drive-controller-dbgsym: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-dwb-core: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-dwb-core-dbgsym: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-dwb-critics: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-dwb-critics-dbgsym: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-dwb-msgs: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-dwb-msgs-dbgsym: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-dwb-plugins: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-dwb-plugins-dbgsym: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-effort-controllers: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-effort-controllers-dbgsym: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-etsi-its-cam-coding: 2.3.0-1 → 2.4.0-1
    • +
  • ros-humble-etsi-its-cam-coding-dbgsym: 2.3.0-1 → 2.4.0-1
    • +
  • ros-humble-etsi-its-cam-conversion: 2.3.0-1 → 2.4.0-1
    • +
  • ros-humble-etsi-its-cam-msgs: 2.3.0-1 → 2.4.0-1
    • +
  • ros-humble-etsi-its-cam-msgs-dbgsym: 2.3.0-1 → 2.4.0-1
    • +
  • ros-humble-etsi-its-cam-ts-coding: 2.3.0-1 → 2.4.0-1
    • +
  • ros-humble-etsi-its-cam-ts-coding-dbgsym: 2.3.0-1 → 2.4.0-1
    • +
  • ros-humble-etsi-its-cam-ts-conversion: 2.3.0-1 → 2.4.0-1
    • +
  • ros-humble-etsi-its-cam-ts-msgs: 2.3.0-1 → 2.4.0-1
    • +
  • ros-humble-etsi-its-cam-ts-msgs-dbgsym: 2.3.0-1 → 2.4.0-1
    • +
  • ros-humble-etsi-its-coding: 2.3.0-1 → 2.4.0-1
    • +
  • ros-humble-etsi-its-conversion: 2.3.0-1 → 2.4.0-1
    • +
  • ros-humble-etsi-its-conversion-dbgsym: 2.3.0-1 → 2.4.0-1
    • +
  • ros-humble-etsi-its-cpm-ts-coding: 2.3.0-1 → 2.4.0-1
    • +
  • ros-humble-etsi-its-cpm-ts-coding-dbgsym: 2.3.0-1 → 2.4.0-1
    • +
  • ros-humble-etsi-its-cpm-ts-conversion: 2.3.0-1 → 2.4.0-1
    • +
  • ros-humble-etsi-its-cpm-ts-msgs: 2.3.0-1 → 2.4.0-1
    • +
  • ros-humble-etsi-its-cpm-ts-msgs-dbgsym: 2.3.0-1 → 2.4.0-1
    • +
  • ros-humble-etsi-its-denm-coding: 2.3.0-1 → 2.4.0-1
    • +
  • ros-humble-etsi-its-denm-coding-dbgsym: 2.3.0-1 → 2.4.0-1
    • +
  • ros-humble-etsi-its-denm-conversion: 2.3.0-1 → 2.4.0-1
    • +
  • ros-humble-etsi-its-denm-msgs: 2.3.0-1 → 2.4.0-1
    • +
  • ros-humble-etsi-its-denm-msgs-dbgsym: 2.3.0-1 → 2.4.0-1
    • +
  • ros-humble-etsi-its-messages: 2.3.0-1 → 2.4.0-1
    • +
  • ros-humble-etsi-its-msgs: 2.3.0-1 → 2.4.0-1
    • +
  • ros-humble-etsi-its-msgs-utils: 2.3.0-1 → 2.4.0-1
    • +
  • ros-humble-etsi-its-primitives-conversion: 2.3.0-1 → 2.4.0-1
    • +
  • ros-humble-etsi-its-rviz-plugins: 2.3.0-1 → 2.4.0-1
    • +
  • ros-humble-etsi-its-rviz-plugins-dbgsym: 2.3.0-1 → 2.4.0-1
    • +
  • ros-humble-etsi-its-vam-ts-coding: 2.3.0-1 → 2.4.0-1
    • +
  • ros-humble-etsi-its-vam-ts-coding-dbgsym: 2.3.0-1 → 2.4.0-1
    • +
  • ros-humble-etsi-its-vam-ts-conversion: 2.3.0-1 → 2.4.0-1
    • +
  • ros-humble-etsi-its-vam-ts-msgs: 2.3.0-1 → 2.4.0-1
    • +
  • ros-humble-etsi-its-vam-ts-msgs-dbgsym: 2.3.0-1 → 2.4.0-1
    • +
  • ros-humble-examples-rclcpp-async-client: 0.15.2-1 → 0.15.3-1
    • +
  • ros-humble-examples-rclcpp-async-client-dbgsym: 0.15.2-1 → 0.15.3-1
    • +
  • ros-humble-examples-rclcpp-cbg-executor: 0.15.2-1 → 0.15.3-1
    • +
  • ros-humble-examples-rclcpp-cbg-executor-dbgsym: 0.15.2-1 → 0.15.3-1
    • +
  • ros-humble-examples-rclcpp-minimal-action-client: 0.15.2-1 → 0.15.3-1
    • +
  • ros-humble-examples-rclcpp-minimal-action-client-dbgsym: 0.15.2-1 → 0.15.3-1
    • +
  • ros-humble-examples-rclcpp-minimal-action-server: 0.15.2-1 → 0.15.3-1
    • +
  • ros-humble-examples-rclcpp-minimal-action-server-dbgsym: 0.15.2-1 → 0.15.3-1
    • +
  • ros-humble-examples-rclcpp-minimal-client: 0.15.2-1 → 0.15.3-1
    • +
  • ros-humble-examples-rclcpp-minimal-client-dbgsym: 0.15.2-1 → 0.15.3-1
    • +
  • ros-humble-examples-rclcpp-minimal-composition: 0.15.2-1 → 0.15.3-1
    • +
  • ros-humble-examples-rclcpp-minimal-composition-dbgsym: 0.15.2-1 → 0.15.3-1
    • +
  • ros-humble-examples-rclcpp-minimal-publisher: 0.15.2-1 → 0.15.3-1
    • +
  • ros-humble-examples-rclcpp-minimal-publisher-dbgsym: 0.15.2-1 → 0.15.3-1
    • +
  • ros-humble-examples-rclcpp-minimal-service: 0.15.2-1 → 0.15.3-1
    • +
  • ros-humble-examples-rclcpp-minimal-service-dbgsym: 0.15.2-1 → 0.15.3-1
    • +
  • ros-humble-examples-rclcpp-minimal-subscriber: 0.15.2-1 → 0.15.3-1
    • +
  • ros-humble-examples-rclcpp-minimal-subscriber-dbgsym: 0.15.2-1 → 0.15.3-1
    • +
  • ros-humble-examples-rclcpp-minimal-timer: 0.15.2-1 → 0.15.3-1
    • +
  • ros-humble-examples-rclcpp-minimal-timer-dbgsym: 0.15.2-1 → 0.15.3-1
    • +
  • ros-humble-examples-rclcpp-multithreaded-executor: 0.15.2-1 → 0.15.3-1
    • +
  • ros-humble-examples-rclcpp-multithreaded-executor-dbgsym: 0.15.2-1 → 0.15.3-1
    • +
  • ros-humble-examples-rclcpp-wait-set: 0.15.2-1 → 0.15.3-1
    • +
  • ros-humble-examples-rclcpp-wait-set-dbgsym: 0.15.2-1 → 0.15.3-1
    • +
  • ros-humble-examples-rclpy-executors: 0.15.2-1 → 0.15.3-1
    • +
  • ros-humble-examples-rclpy-guard-conditions: 0.15.2-1 → 0.15.3-1
    • +
  • ros-humble-examples-rclpy-minimal-action-client: 0.15.2-1 → 0.15.3-1
    • +
  • ros-humble-examples-rclpy-minimal-action-server: 0.15.2-1 → 0.15.3-1
    • +
  • ros-humble-examples-rclpy-minimal-client: 0.15.2-1 → 0.15.3-1
    • +
  • ros-humble-examples-rclpy-minimal-publisher: 0.15.2-1 → 0.15.3-1
    • +
  • ros-humble-examples-rclpy-minimal-service: 0.15.2-1 → 0.15.3-1
    • +
  • ros-humble-examples-rclpy-minimal-subscriber: 0.15.2-1 → 0.15.3-1
    • +
  • ros-humble-examples-rclpy-pointcloud-publisher: 0.15.2-1 → 0.15.3-1
    • +
  • ros-humble-examples-tf2-py: 0.25.8-1 → 0.25.9-1
    • +
  • ros-humble-fastrtps: 2.6.8-1 → 2.6.9-1
    • +
  • ros-humble-fastrtps-dbgsym: 2.6.8-1 → 2.6.9-1
    • +
  • ros-humble-flir-camera-description: 2.1.17-1 → 3.0.0-1
    • +
  • ros-humble-flir-camera-msgs: 2.1.17-1 → 3.0.0-1
    • +
  • ros-humble-flir-camera-msgs-dbgsym: 2.1.17-1 → 3.0.0-1
    • +
  • ros-humble-force-torque-sensor-broadcaster: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-force-torque-sensor-broadcaster-dbgsym: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-forward-command-controller: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-forward-command-controller-dbgsym: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-foxglove-bridge: 0.8.0-1 → 0.8.1-1
    • +
  • ros-humble-foxglove-bridge-dbgsym: 0.8.0-1 → 0.8.1-1
    • +
  • ros-humble-foxglove-compressed-video-transport: 1.0.0-1 → 1.0.1-1
    • +
  • ros-humble-foxglove-compressed-video-transport-dbgsym: 1.0.0-1 → 1.0.1-1
    • +
  • ros-humble-geometry2: 0.25.8-1 → 0.25.9-1
    • +
  • ros-humble-gripper-controllers: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-gripper-controllers-dbgsym: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-hardware-interface: 2.43.1-1 → 2.44.0-1
    • +
  • ros-humble-hardware-interface-dbgsym: 2.43.1-1 → 2.44.0-1
    • +
  • ros-humble-hardware-interface-testing: 2.43.1-1 → 2.44.0-1
    • +
  • ros-humble-hardware-interface-testing-dbgsym: 2.43.1-1 → 2.44.0-1
    • +
  • ros-humble-image-common: 3.1.9-1 → 3.1.10-1
    • +
  • ros-humble-image-transport: 3.1.9-1 → 3.1.10-1
    • +
  • ros-humble-image-transport-dbgsym: 3.1.9-1 → 3.1.10-1
    • +
  • ros-humble-imu-sensor-broadcaster: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-imu-sensor-broadcaster-dbgsym: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-interactive-marker-twist-server: 2.1.0-2 → 2.1.1-1
    • +
  • ros-humble-interactive-marker-twist-server-dbgsym: 2.1.0-2 → 2.1.1-1
    • +
  • ros-humble-joint-limits: 2.43.1-1 → 2.44.0-1
    • +
  • ros-humble-joint-limits-dbgsym: 2.43.1-1 → 2.44.0-1
    • +
  • ros-humble-joint-state-broadcaster: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-joint-state-broadcaster-dbgsym: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-joint-trajectory-controller: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-joint-trajectory-controller-dbgsym: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-joy-teleop: 1.6.0-1 → 1.7.0-1
    • +
  • ros-humble-key-teleop: 1.6.0-1 → 1.7.0-1
    • +
  • ros-humble-launch: 1.0.6-1 → 1.0.7-1
    • +
  • ros-humble-launch-pytest: 1.0.6-1 → 1.0.7-1
    • +
  • ros-humble-launch-ros: 0.19.7-2 → 0.19.8-1
    • +
  • ros-humble-launch-testing: 1.0.6-1 → 1.0.7-1
    • +
  • ros-humble-launch-testing-ament-cmake: 1.0.6-1 → 1.0.7-1
    • +
  • ros-humble-launch-testing-examples: 0.15.2-1 → 0.15.3-1
    • +
  • ros-humble-launch-testing-ros: 0.19.7-2 → 0.19.8-1
    • +
  • ros-humble-launch-xml: 1.0.6-1 → 1.0.7-1
    • +
  • ros-humble-launch-yaml: 1.0.6-1 → 1.0.7-1
    • +
  • ros-humble-leo: 1.2.3-1 → 1.2.4-1
    • +
  • ros-humble-leo-bringup: 1.4.0-1 → 1.5.0-1
    • +
  • ros-humble-leo-description: 1.2.3-1 → 1.2.4-1
    • +
  • ros-humble-leo-fw: 1.4.0-1 → 1.5.0-1
    • +
  • ros-humble-leo-fw-dbgsym: 1.4.0-1 → 1.5.0-1
    • +
  • ros-humble-leo-gz-bringup: 1.1.0-1 → 1.1.1-1
    • +
  • ros-humble-leo-gz-plugins: 1.1.0-1 → 1.1.1-1
    • +
  • ros-humble-leo-gz-plugins-dbgsym: 1.1.0-1 → 1.1.1-1
    • +
  • ros-humble-leo-gz-worlds: 1.1.0-1 → 1.1.1-1
    • +
  • ros-humble-leo-msgs: 1.2.3-1 → 1.2.4-1
    • +
  • ros-humble-leo-msgs-dbgsym: 1.2.3-1 → 1.2.4-1
    • +
  • ros-humble-leo-robot: 1.4.0-1 → 1.5.0-1
    • +
  • ros-humble-leo-simulator: 1.1.0-1 → 1.1.1-1
    • +
  • ros-humble-leo-teleop: 1.2.3-1 → 1.2.4-1
    • +
  • ros-humble-libstatistics-collector: 1.3.2-1 → 1.3.4-1
    • +
  • ros-humble-libstatistics-collector-dbgsym: 1.3.2-1 → 1.3.4-1
    • +
  • ros-humble-mcap-vendor: 0.15.12-1 → 0.15.13-1
    • +
  • ros-humble-mcap-vendor-dbgsym: 0.15.12-1 → 0.15.13-1
    • +
  • ros-humble-microstrain-inertial-description: 4.4.0-1 → 4.5.0-1
    • +
  • ros-humble-microstrain-inertial-driver: 4.4.0-1 → 4.5.0-1
    • +
  • ros-humble-microstrain-inertial-driver-dbgsym: 4.4.0-1 → 4.5.0-1
    • +
  • ros-humble-microstrain-inertial-examples: 4.4.0-1 → 4.5.0-1
    • +
  • ros-humble-microstrain-inertial-msgs: 4.4.0-1 → 4.5.0-1
    • +
  • ros-humble-microstrain-inertial-msgs-dbgsym: 4.4.0-1 → 4.5.0-1
    • +
  • ros-humble-microstrain-inertial-rqt: 4.4.0-1 → 4.5.0-1
    • +
  • ros-humble-mouse-teleop: 1.6.0-1 → 1.7.0-1
    • +
  • ros-humble-moveit: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-chomp-optimizer-adapter: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-chomp-optimizer-adapter-dbgsym: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-common: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-configs-utils: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-core: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-core-dbgsym: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-hybrid-planning: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-hybrid-planning-dbgsym: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-kinematics: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-kinematics-dbgsym: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-planners: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-planners-chomp: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-planners-chomp-dbgsym: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-planners-ompl: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-planners-ompl-dbgsym: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-plugins: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-resources-prbt-ikfast-manipulator-plugin: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-resources-prbt-ikfast-manipulator-plugin-dbgsym: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-resources-prbt-moveit-config: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-resources-prbt-pg70-support: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-resources-prbt-support: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-ros: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-ros-benchmarks: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-ros-benchmarks-dbgsym: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-ros-control-interface: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-ros-control-interface-dbgsym: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-ros-move-group: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-ros-move-group-dbgsym: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-ros-occupancy-map-monitor: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-ros-occupancy-map-monitor-dbgsym: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-ros-perception: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-ros-perception-dbgsym: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-ros-planning: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-ros-planning-dbgsym: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-ros-planning-interface: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-ros-planning-interface-dbgsym: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-ros-robot-interaction: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-ros-robot-interaction-dbgsym: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-ros-visualization: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-ros-visualization-dbgsym: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-ros-warehouse: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-ros-warehouse-dbgsym: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-runtime: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-servo: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-servo-dbgsym: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-setup-app-plugins: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-setup-app-plugins-dbgsym: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-setup-assistant: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-setup-assistant-dbgsym: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-setup-controllers: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-setup-controllers-dbgsym: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-setup-core-plugins: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-setup-core-plugins-dbgsym: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-setup-framework: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-setup-framework-dbgsym: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-setup-srdf-plugins: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-setup-srdf-plugins-dbgsym: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-simple-controller-manager: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-moveit-simple-controller-manager-dbgsym: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-mp2p-icp: 1.6.2-1 → 1.6.3-1
    • +
  • ros-humble-mp2p-icp-dbgsym: 1.6.2-1 → 1.6.3-1
    • +
  • ros-humble-mrpt-apps: 2.14.4-1 → 2.14.5-1
    • +
  • ros-humble-mrpt-apps-dbgsym: 2.14.4-1 → 2.14.5-1
    • +
  • ros-humble-mrpt-libapps: 2.14.4-1 → 2.14.5-1
    • +
  • ros-humble-mrpt-libapps-dbgsym: 2.14.4-1 → 2.14.5-1
    • +
  • ros-humble-mrpt-libbase: 2.14.4-1 → 2.14.5-1
    • +
  • ros-humble-mrpt-libbase-dbgsym: 2.14.4-1 → 2.14.5-1
    • +
  • ros-humble-mrpt-libgui: 2.14.4-1 → 2.14.5-1
    • +
  • ros-humble-mrpt-libgui-dbgsym: 2.14.4-1 → 2.14.5-1
    • +
  • ros-humble-mrpt-libhwdrivers: 2.14.4-1 → 2.14.5-1
    • +
  • ros-humble-mrpt-libhwdrivers-dbgsym: 2.14.4-1 → 2.14.5-1
    • +
  • ros-humble-mrpt-libmaps: 2.14.4-1 → 2.14.5-1
    • +
  • ros-humble-mrpt-libmaps-dbgsym: 2.14.4-1 → 2.14.5-1
    • +
  • ros-humble-mrpt-libmath: 2.14.4-1 → 2.14.5-1
    • +
  • ros-humble-mrpt-libmath-dbgsym: 2.14.4-1 → 2.14.5-1
    • +
  • ros-humble-mrpt-libnav: 2.14.4-1 → 2.14.5-1
    • +
  • ros-humble-mrpt-libnav-dbgsym: 2.14.4-1 → 2.14.5-1
    • +
  • ros-humble-mrpt-libobs: 2.14.4-1 → 2.14.5-1
    • +
  • ros-humble-mrpt-libobs-dbgsym: 2.14.4-1 → 2.14.5-1
    • +
  • ros-humble-mrpt-libopengl: 2.14.4-1 → 2.14.5-1
    • +
  • ros-humble-mrpt-libopengl-dbgsym: 2.14.4-1 → 2.14.5-1
    • +
  • ros-humble-mrpt-libposes: 2.14.4-1 → 2.14.5-1
    • +
  • ros-humble-mrpt-libposes-dbgsym: 2.14.4-1 → 2.14.5-1
    • +
  • ros-humble-mrpt-libros-bridge: 2.14.4-1 → 2.14.5-1
    • +
  • ros-humble-mrpt-libros-bridge-dbgsym: 2.14.4-1 → 2.14.5-1
    • +
  • ros-humble-mrpt-libslam: 2.14.4-1 → 2.14.5-1
    • +
  • ros-humble-mrpt-libslam-dbgsym: 2.14.4-1 → 2.14.5-1
    • +
  • ros-humble-mrpt-libtclap: 2.14.4-1 → 2.14.5-1
    • +
  • ros-humble-nav-2d-msgs: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav-2d-msgs-dbgsym: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav-2d-utils: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav-2d-utils-dbgsym: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-amcl: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-amcl-dbgsym: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-behavior-tree: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-behavior-tree-dbgsym: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-behaviors: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-behaviors-dbgsym: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-bringup: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-bt-navigator: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-bt-navigator-dbgsym: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-collision-monitor: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-collision-monitor-dbgsym: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-common: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-constrained-smoother: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-constrained-smoother-dbgsym: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-controller: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-controller-dbgsym: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-core: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-costmap-2d: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-costmap-2d-dbgsym: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-dwb-controller: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-graceful-controller: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-graceful-controller-dbgsym: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-lifecycle-manager: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-lifecycle-manager-dbgsym: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-map-server: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-map-server-dbgsym: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-mppi-controller: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-mppi-controller-dbgsym: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-msgs: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-msgs-dbgsym: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-navfn-planner: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-navfn-planner-dbgsym: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-planner: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-planner-dbgsym: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-regulated-pure-pursuit-controller: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-regulated-pure-pursuit-controller-dbgsym: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-rotation-shim-controller: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-rotation-shim-controller-dbgsym: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-rviz-plugins: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-rviz-plugins-dbgsym: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-simple-commander: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-smac-planner: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-smac-planner-dbgsym: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-smoother: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-smoother-dbgsym: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-system-tests: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-system-tests-dbgsym: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-theta-star-planner: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-theta-star-planner-dbgsym: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-util: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-util-dbgsym: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-velocity-smoother: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-velocity-smoother-dbgsym: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-voxel-grid: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-voxel-grid-dbgsym: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-waypoint-follower: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-nav2-waypoint-follower-dbgsym: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-navigation2: 1.1.16-1 → 1.1.17-1
    • +
  • ros-humble-novatel-gps-driver: 4.1.3-1 → 4.2.0-1
    • +
  • ros-humble-novatel-gps-driver-dbgsym: 4.1.3-1 → 4.2.0-1
    • +
  • ros-humble-novatel-gps-msgs: 4.1.3-1 → 4.2.0-1
    • +
  • ros-humble-novatel-gps-msgs-dbgsym: 4.1.3-1 → 4.2.0-1
    • +
  • ros-humble-octomap-msgs: 2.0.0-3 → 2.0.1-1
    • +
  • ros-humble-octomap-msgs-dbgsym: 2.0.0-3 → 2.0.1-1
    • +
  • ros-humble-odom-to-tf-ros2: 1.0.2-1 → 1.0.4-1
    • +
  • ros-humble-odom-to-tf-ros2-dbgsym: 1.0.2-1 → 1.0.4-1
    • +
  • ros-humble-openni2-camera: 2.0.2-1 → 2.0.3-1
    • +
  • ros-humble-openni2-camera-dbgsym: 2.0.2-1 → 2.0.3-1
    • +
  • ros-humble-osrf-pycommon: 2.0.2-2 → 2.1.4-1
    • +
  • ros-humble-pal-gripper: 3.3.0-1 → 3.4.0-1
    • +
  • ros-humble-pal-gripper-controller-configuration: 3.3.0-1 → 3.4.0-1
    • +
  • ros-humble-pal-gripper-description: 3.3.0-1 → 3.4.0-1
    • +
  • ros-humble-pal-gripper-simulation: 3.3.0-1 → 3.4.0-1
    • +
  • ros-humble-pal-maps: 0.0.4-1 → 0.0.5-1
    • +
  • ros-humble-pal-statistics: 2.3.1-1 → 2.5.0-1
    • +
  • ros-humble-pal-statistics-dbgsym: 2.3.1-1 → 2.5.0-1
    • +
  • ros-humble-pal-statistics-msgs: 2.3.1-1 → 2.5.0-1
    • +
  • ros-humble-pal-statistics-msgs-dbgsym: 2.3.1-1 → 2.5.0-1
    • +
  • ros-humble-pid-controller: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-pid-controller-dbgsym: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-pilz-industrial-motion-planner: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-pilz-industrial-motion-planner-dbgsym: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-pilz-industrial-motion-planner-testutils: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-pilz-industrial-motion-planner-testutils-dbgsym: 2.5.5-1 → 2.5.6-1
    • +
  • ros-humble-pmb2-2dnav: 4.2.0-1 → 4.5.0-1
    • +
  • ros-humble-pmb2-bringup: 5.3.1-1 → 5.4.0-1
    • +
  • ros-humble-pmb2-controller-configuration: 5.3.1-1 → 5.4.0-1
    • +
  • ros-humble-pmb2-description: 5.3.1-1 → 5.4.0-1
    • +
  • ros-humble-pmb2-gazebo: 4.0.16-1 → 4.1.0-1
    • +
  • ros-humble-pmb2-laser-sensors: 4.2.0-1 → 4.5.0-1
    • +
  • ros-humble-pmb2-navigation: 4.2.0-1 → 4.5.0-1
    • +
  • ros-humble-pmb2-robot: 5.3.1-1 → 5.4.0-1
    • +
  • ros-humble-pmb2-simulation: 4.0.16-1 → 4.1.0-1
    • +
  • ros-humble-position-controllers: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-position-controllers-dbgsym: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-python-mrpt: 2.14.4-1 → 2.14.5-1
    • +
  • ros-humble-range-sensor-broadcaster: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-range-sensor-broadcaster-dbgsym: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-rc-reason-clients: 0.3.1-1 → 0.4.0-2
    • +
  • ros-humble-rc-reason-msgs: 0.3.1-1 → 0.4.0-2
    • +
  • ros-humble-rc-reason-msgs-dbgsym: 0.3.1-1 → 0.4.0-2
    • +
  • ros-humble-rclcpp: 16.0.10-1 → 16.0.11-1
    • +
  • ros-humble-rclcpp-action: 16.0.10-1 → 16.0.11-1
    • +
  • ros-humble-rclcpp-action-dbgsym: 16.0.10-1 → 16.0.11-1
    • +
  • ros-humble-rclcpp-components: 16.0.10-1 → 16.0.11-1
    • +
  • ros-humble-rclcpp-components-dbgsym: 16.0.10-1 → 16.0.11-1
    • +
  • ros-humble-rclcpp-dbgsym: 16.0.10-1 → 16.0.11-1
    • +
  • ros-humble-rclcpp-lifecycle: 16.0.10-1 → 16.0.11-1
    • +
  • ros-humble-rclcpp-lifecycle-dbgsym: 16.0.10-1 → 16.0.11-1
    • +
  • ros-humble-rclpy: 3.3.14-1 → 3.3.15-1
    • +
  • ros-humble-rcpputils: 2.4.3-1 → 2.4.4-1
    • +
  • ros-humble-rcpputils-dbgsym: 2.4.3-1 → 2.4.4-1
    • +
  • ros-humble-realtime-tools: 2.7.0-1 → 2.8.1-1
    • +
  • ros-humble-realtime-tools-dbgsym: 2.7.0-1 → 2.8.1-1
    • +
  • ros-humble-rmf-building-map-tools: 1.6.2-1 → 1.6.3-1
    • +
  • ros-humble-rmf-traffic-editor: 1.6.2-1 → 1.6.3-1
    • +
  • ros-humble-rmf-traffic-editor-assets: 1.6.2-1 → 1.6.3-1
    • +
  • ros-humble-rmf-traffic-editor-dbgsym: 1.6.2-1 → 1.6.3-1
    • +
  • ros-humble-rmf-traffic-editor-test-maps: 1.6.2-1 → 1.6.3-1
    • +
  • ros-humble-rmw-connextdds: 0.11.2-1 → 0.11.3-1
    • +
  • ros-humble-rmw-connextdds-common: 0.11.2-1 → 0.11.3-1
    • +
  • ros-humble-rmw-connextdds-common-dbgsym: 0.11.2-1 → 0.11.3-1
    • +
  • ros-humble-rmw-connextdds-dbgsym: 0.11.2-1 → 0.11.3-1
    • +
  • ros-humble-robot-calibration: 0.8.1-1 → 0.8.2-1
    • +
  • ros-humble-robot-calibration-dbgsym: 0.8.1-1 → 0.8.2-1
    • +
  • ros-humble-robot-calibration-msgs: 0.8.1-1 → 0.8.2-1
    • +
  • ros-humble-robot-calibration-msgs-dbgsym: 0.8.1-1 → 0.8.2-1
    • +
  • ros-humble-ros2-control: 2.43.1-1 → 2.44.0-1
    • +
  • ros-humble-ros2-control-test-assets: 2.43.1-1 → 2.44.0-1
    • +
  • ros-humble-ros2-controllers: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-ros2-controllers-test-nodes: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-ros2bag: 0.15.12-1 → 0.15.13-1
    • +
  • ros-humble-ros2controlcli: 2.43.1-1 → 2.44.0-1
    • +
  • ros-humble-ros2launch: 0.19.7-2 → 0.19.8-1
    • +
  • ros-humble-rosbag2: 0.15.12-1 → 0.15.13-1
    • +
  • ros-humble-rosbag2-compression: 0.15.12-1 → 0.15.13-1
    • +
  • ros-humble-rosbag2-compression-dbgsym: 0.15.12-1 → 0.15.13-1
    • +
  • ros-humble-rosbag2-compression-zstd: 0.15.12-1 → 0.15.13-1
    • +
  • ros-humble-rosbag2-compression-zstd-dbgsym: 0.15.12-1 → 0.15.13-1
    • +
  • ros-humble-rosbag2-cpp: 0.15.12-1 → 0.15.13-1
    • +
  • ros-humble-rosbag2-cpp-dbgsym: 0.15.12-1 → 0.15.13-1
    • +
  • ros-humble-rosbag2-interfaces: 0.15.12-1 → 0.15.13-1
    • +
  • ros-humble-rosbag2-interfaces-dbgsym: 0.15.12-1 → 0.15.13-1
    • +
  • ros-humble-rosbag2-performance-benchmarking: 0.15.12-1 → 0.15.13-1
    • +
  • ros-humble-rosbag2-py: 0.15.12-1 → 0.15.13-1
    • +
  • ros-humble-rosbag2-storage: 0.15.12-1 → 0.15.13-1
    • +
  • ros-humble-rosbag2-storage-dbgsym: 0.15.12-1 → 0.15.13-1
    • +
  • ros-humble-rosbag2-storage-default-plugins: 0.15.12-1 → 0.15.13-1
    • +
  • ros-humble-rosbag2-storage-default-plugins-dbgsym: 0.15.12-1 → 0.15.13-1
    • +
  • ros-humble-rosbag2-storage-mcap: 0.15.12-1 → 0.15.13-1
    • +
  • ros-humble-rosbag2-storage-mcap-dbgsym: 0.15.12-1 → 0.15.13-1
    • +
  • ros-humble-rosbag2-storage-mcap-testdata: 0.15.12-1 → 0.15.13-1
    • +
  • ros-humble-rosbag2-storage-mcap-testdata-dbgsym: 0.15.12-1 → 0.15.13-1
    • +
  • ros-humble-rosbag2-test-common: 0.15.12-1 → 0.15.13-1
    • +
  • ros-humble-rosbag2-tests: 0.15.12-1 → 0.15.13-1
    • +
  • ros-humble-rosbag2-transport: 0.15.12-1 → 0.15.13-1
    • +
  • ros-humble-rosbag2-transport-dbgsym: 0.15.12-1 → 0.15.13-1
    • +
  • ros-humble-rosidl-adapter: 3.1.5-2 → 3.1.6-1
    • +
  • ros-humble-rosidl-cli: 3.1.5-2 → 3.1.6-1
    • +
  • ros-humble-rosidl-cmake: 3.1.5-2 → 3.1.6-1
    • +
  • ros-humble-rosidl-generator-c: 3.1.5-2 → 3.1.6-1
    • +
  • ros-humble-rosidl-generator-cpp: 3.1.5-2 → 3.1.6-1
    • +
  • ros-humble-rosidl-parser: 3.1.5-2 → 3.1.6-1
    • +
  • ros-humble-rosidl-runtime-c: 3.1.5-2 → 3.1.6-1
    • +
  • ros-humble-rosidl-runtime-c-dbgsym: 3.1.5-2 → 3.1.6-1
    • +
  • ros-humble-rosidl-runtime-cpp: 3.1.5-2 → 3.1.6-1
    • +
  • ros-humble-rosidl-typesupport-c: 2.0.1-1 → 2.0.2-1
    • +
  • ros-humble-rosidl-typesupport-c-dbgsym: 2.0.1-1 → 2.0.2-1
    • +
  • ros-humble-rosidl-typesupport-cpp: 2.0.1-1 → 2.0.2-1
    • +
  • ros-humble-rosidl-typesupport-cpp-dbgsym: 2.0.1-1 → 2.0.2-1
    • +
  • ros-humble-rosidl-typesupport-interface: 3.1.5-2 → 3.1.6-1
    • +
  • ros-humble-rosidl-typesupport-introspection-c: 3.1.5-2 → 3.1.6-1
    • +
  • ros-humble-rosidl-typesupport-introspection-c-dbgsym: 3.1.5-2 → 3.1.6-1
    • +
  • ros-humble-rosidl-typesupport-introspection-cpp: 3.1.5-2 → 3.1.6-1
    • +
  • ros-humble-rosidl-typesupport-introspection-cpp-dbgsym: 3.1.5-2 → 3.1.6-1
    • +
  • ros-humble-rqt-controller-manager: 2.43.1-1 → 2.44.0-1
    • +
  • ros-humble-rqt-joint-trajectory-controller: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-rti-connext-dds-cmake-module: 0.11.2-1 → 0.11.3-1
    • +
  • ros-humble-rviz-assimp-vendor: 11.2.13-1 → 11.2.14-1
    • +
  • ros-humble-rviz-common: 11.2.13-1 → 11.2.14-1
    • +
  • ros-humble-rviz-common-dbgsym: 11.2.13-1 → 11.2.14-1
    • +
  • ros-humble-rviz-default-plugins: 11.2.13-1 → 11.2.14-1
    • +
  • ros-humble-rviz-default-plugins-dbgsym: 11.2.13-1 → 11.2.14-1
    • +
  • ros-humble-rviz-ogre-vendor: 11.2.13-1 → 11.2.14-1
    • +
  • ros-humble-rviz-ogre-vendor-dbgsym: 11.2.13-1 → 11.2.14-1
    • +
  • ros-humble-rviz-rendering: 11.2.13-1 → 11.2.14-1
    • +
  • ros-humble-rviz-rendering-dbgsym: 11.2.13-1 → 11.2.14-1
    • +
  • ros-humble-rviz-rendering-tests: 11.2.13-1 → 11.2.14-1
    • +
  • ros-humble-rviz-visual-testing-framework: 11.2.13-1 → 11.2.14-1
    • +
  • ros-humble-rviz2: 11.2.13-1 → 11.2.14-1
    • +
  • ros-humble-rviz2-dbgsym: 11.2.13-1 → 11.2.14-1
    • +
  • ros-humble-shared-queues-vendor: 0.15.12-1 → 0.15.13-1
    • +
  • ros-humble-spinnaker-camera-driver: 2.1.17-1 → 3.0.0-1
    • +
  • ros-humble-spinnaker-camera-driver-dbgsym: 2.1.17-1 → 3.0.0-1
    • +
  • ros-humble-spinnaker-synchronized-camera-driver: 2.1.17-1 → 3.0.0-1
    • +
  • ros-humble-spinnaker-synchronized-camera-driver-dbgsym: 2.1.17-1 → 3.0.0-1
    • +
  • ros-humble-sqlite3-vendor: 0.15.12-1 → 0.15.13-1
    • +
  • ros-humble-steering-controllers-library: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-steering-controllers-library-dbgsym: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-teleop-tools: 1.6.0-1 → 1.7.0-1
    • +
  • ros-humble-teleop-tools-msgs: 1.6.0-1 → 1.7.0-1
    • +
  • ros-humble-teleop-tools-msgs-dbgsym: 1.6.0-1 → 1.7.0-1
    • +
  • ros-humble-tf2: 0.25.8-1 → 0.25.9-1
    • +
  • ros-humble-tf2-bullet: 0.25.8-1 → 0.25.9-1
    • +
  • ros-humble-tf2-dbgsym: 0.25.8-1 → 0.25.9-1
    • +
  • ros-humble-tf2-eigen: 0.25.8-1 → 0.25.9-1
    • +
  • ros-humble-tf2-eigen-kdl: 0.25.8-1 → 0.25.9-1
    • +
  • ros-humble-tf2-eigen-kdl-dbgsym: 0.25.8-1 → 0.25.9-1
    • +
  • ros-humble-tf2-geometry-msgs: 0.25.8-1 → 0.25.9-1
    • +
  • ros-humble-tf2-kdl: 0.25.8-1 → 0.25.9-1
    • +
  • ros-humble-tf2-msgs: 0.25.8-1 → 0.25.9-1
    • +
  • ros-humble-tf2-msgs-dbgsym: 0.25.8-1 → 0.25.9-1
    • +
  • ros-humble-tf2-py: 0.25.8-1 → 0.25.9-1
    • +
  • ros-humble-tf2-py-dbgsym: 0.25.8-1 → 0.25.9-1
    • +
  • ros-humble-tf2-ros: 0.25.8-1 → 0.25.9-1
    • +
  • ros-humble-tf2-ros-dbgsym: 0.25.8-1 → 0.25.9-1
    • +
  • ros-humble-tf2-ros-py: 0.25.8-1 → 0.25.9-1
    • +
  • ros-humble-tf2-sensor-msgs: 0.25.8-1 → 0.25.9-1
    • +
  • ros-humble-tf2-tools: 0.25.8-1 → 0.25.9-1
    • +
  • ros-humble-tiago-2dnav: 4.2.0-1 → 4.5.0-1
    • +
  • ros-humble-tiago-bringup: 4.6.0-1 → 4.7.1-1
    • +
  • ros-humble-tiago-controller-configuration: 4.6.0-1 → 4.7.1-1
    • +
  • ros-humble-tiago-description: 4.6.0-1 → 4.7.1-1
    • +
  • ros-humble-tiago-gazebo: 4.2.0-1 → 4.3.0-1
    • +
  • ros-humble-tiago-gazebo-dbgsym: 4.2.0-1 → 4.3.0-1
    • +
  • ros-humble-tiago-laser-sensors: 4.2.0-1 → 4.5.0-1
    • +
  • ros-humble-tiago-moveit-config: 3.1.0-1 → 3.1.1-1
    • +
  • ros-humble-tiago-navigation: 4.2.0-1 → 4.5.0-1
    • +
  • ros-humble-tiago-robot: 4.6.0-1 → 4.7.1-1
    • +
  • ros-humble-tiago-simulation: 4.2.0-1 → 4.3.0-1
    • +
  • ros-humble-transmission-interface: 2.43.1-1 → 2.44.0-1
    • +
  • ros-humble-transmission-interface-dbgsym: 2.43.1-1 → 2.44.0-1
    • +
  • ros-humble-tricycle-controller: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-tricycle-controller-dbgsym: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-tricycle-steering-controller: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-tricycle-steering-controller-dbgsym: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-twist-stamper: 0.0.3-1 → 0.0.5-1
    • +
  • ros-humble-ur-client-library: 1.4.0-1 → 1.5.0-1
    • +
  • ros-humble-ur-client-library-dbgsym: 1.4.0-1 → 1.5.0-1
    • +
  • ros-humble-velocity-controllers: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-velocity-controllers-dbgsym: 2.37.3-1 → 2.38.0-1
    • +
  • ros-humble-zstd-vendor: 0.15.12-1 → 0.15.13-1
    • +
+

Removed Packages [6]:

+ +

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

+
    +
  • Adam Serafin
    • +
  • Aditya Pande
    • +
  • Aina Irisarri
    • +
  • Alberto Tudela
    • +
  • Alejandro Hernandez Cordero
    • +
  • Alexander Gutenkunst
    • +
  • Alexey Merzlyakov
    • +
  • Analog Devices
    • +
  • Andrea Sorbini
    • +
  • Antonio Brandi
    • +
  • Bence Magyar
    • +
  • Bernd Pfrommer
    • +
  • Blake Anderson
    • +
  • Brandon Ong
    • +
  • Brian Wilcox
    • +
  • Błażej Sowa
    • +
  • Carl Delsey
    • +
  • Carlos Orduno
    • +
  • Chittaranjan Srinivas Swaminathan
    • +
  • Chris Iverach-Brereton
    • +
  • Chris Lalancette
    • +
  • Christian Henkel
    • +
  • Christian Rauch
    • +
  • David V. Lu!!
    • +
  • Denis Štogl
    • +
  • Eclipse Foundation, Inc.
    • +
  • Enrique Fernandez
    • +
  • Evan Flynn
    • +
  • Felix Exner
    • +
  • Felix Ruess
    • +
  • Fictionlab
    • +
  • Foxglove
    • +
  • George Stavrinos
    • +
  • Hans-Joachim Krauch
    • +
  • Henning Kayser
    • +
  • Ivan Paunovic
    • +
  • Jacob Perron
    • +
  • Jafar Uruc
    • +
  • Jean-Pierre Busch
    • +
  • Jordan Palacios
    • +
  • Jordi Pages
    • +
  • Jose Mastrangelo
    • +
  • Jose-Luis Blanco-Claraco
    • +
  • Josh Newans
    • +
  • Luis Camero
    • +
  • Luka Juricic
    • +
  • Mamoru Sobue
    • +
  • Marc Alban
    • +
  • Matej Vargovcik
    • +
  • Michael Ferguson
    • +
  • Michael Görner
    • +
  • Michael Jeronimo
    • +
  • Michael Orlov
    • +
  • Michel Hidalgo
    • +
  • Miguel Company
    • +
  • Mike Purvis
    • +
  • Mohammad Haghighipanah
    • +
  • Morgan Quigley
    • +
  • MoveIt Release Team
    • +
  • P. J. Reed
    • +
  • ROS Tooling Working Group
    • +
  • Raghavender Sahdev
    • +
  • Ralph Lange
    • +
  • Rob Fisher
    • +
  • Robert Wilbrandt
    • +
  • Roni Kreinin
    • +
  • STEREOLABS
    • +
  • Shane Loretz
    • +
  • Stefan Laible
    • +
  • Steve Macenski
    • +
  • Séverin Lemaignan
    • +
  • TIAGo PAL support team
    • +
  • TIAGo support team
    • +
  • Tony Baltovski
    • +
  • Victor López
    • +
  • William Woodall
    • +
  • Wolfgang Merkt
    • +
  • mitsudome-r
    • +
  • pradyum
    • +
  • ruess
    • +
  • steve
    • +
+

1 post - 1 participant

+

Read full topic

+ + + + + + + +
+

+by audrow on December 05, 2024 08:17 PM +

+ +
+ + + + + + + + + +
+ + +
Clearpath Simulator comes to Gazebo Harmonic :fire:
+ +
from ROS Discourse General
+ +
+ +
+

Hello everyone,

+

I have successfully ported Clearpath Robotics’s open-source simulator clearpath_simulator into Gazebo Harmonic LTS.

+

Key changes include adding support for Xbox One controllers, support for custom robot.yaml names and automatic Twist message conversion to TwistStamped required by the newer builds of ros2_controllers and Gazebo. The simulator has been tested to work in Ubuntu 22.04 (source build). Presently, only A200 Husky is supported. Version 0.2 will add RGB-D sensor and build testing in Ubuntu 24.04.

+

image

+

To accommodate a number of changes made to almost all the original dependent packages, I have opted to host my derived work separately here: GitHub - Mechazo11/clearpath_simulator_harmonic: A port of Clearpath Simulator, compatible with ROS 2 Jazzy and Gazebo Harmonic

+

A big shout-out to Clearpath Robotics team for making the original simulator publicly available. I hope this work proves valuable to the community. If you have any questions, concerns or would like to contribute please don’t hesitate to reaching out to me.

+

With best regards,
+Azmyin Md. Kamal

+

1 post - 1 participant

+

Read full topic

+ + + + + + + +
+

+by azmyin12 on December 05, 2024 07:42 PM +

+ +
+ +
December 04, 2024
+ + + + + + + + +
+ + +
Expose secure communication only with specified entities
+ +
from ROS Discourse General
+ +
+ +
+

Hi ROS developers,

+

Asking thoughts and ideas!

+

I think this is more like discussion to explore than a question, I would like to have feedback from the community how to handle this situation to support 3rd party device.

+

Original issue: Expose secure communication only with specified entities. · Issue #326 · ros2/sros2 · GitHub

+

image

+
    +
  • For performance consideration, it would be better to keep the localhost communication in robot without secured authentication nor encryption. (basically it uses localhost in robot system, but some specific nodes to be exposed.)
    • +
+

I am trying to find out what could be best solution to support above requirement with secured communication with sros2.

+

If you have any experience, please enlighten me :pray: :pray: :pray:

+

Regards,
+Tomoya

+

6 posts - 3 participants

+

Read full topic

+ + + + + + + +
+

+by tomoyafujita on December 04, 2024 10:10 PM +

+ +
+ + + + + + + + + +
+ + +
Next Client Library WG Meeting: Friday 6th December 2024 8AM PT
+ +
from ROS Discourse General
+ +
+ +
+

Hi,
+The next meeting of the Client Library Working Group will be this Friday, 6th December 2024 at 8 AM Pacific Time.

+ +

We will be reviewing the charter proposal for the ROS 2 Client Library Working Group and continue the discussions from the previous meetings.

+

2 posts - 1 participant

+

Read full topic

+ + + + + + + +
+

+by alsora on December 04, 2024 06:12 PM +

+ +
+ +
December 03, 2024
+ + + + + + + + +
+ + +
Call for Participation: ROS Deliberation Community Group
+ +
from ROS Discourse General
+ +
+ +
+

Hello all,

+

After our successful workshop at ROSCon 2024, the ROS Deliberation Community Group is resuming its focus on monthly meetings to engage with the community.

+

For those who were formerly attending the meetings before we spent time preparing for the workshop, the time is right to start attending again! If you are considering attending for the first time, or have never heard of this Community Group before, we look forward to seeing you as well.

+

Either way, we’d like to hear from you all about possible topics for subsequent meetings in the new year. Some initial ideas:

+
    +
  • Putting together a survey document of ROS 2 Deliberation Technologies, very much inspired by the great Nav2 paper.
    • +
  • Collaborating on the development of open-source software tools, or examples using those tools, for robot deliberation.
    • +
  • Presentations from people interested in sharing their work (though we’d like to also have time for working discussions as well).
    • +
+

If anyone wants to share ideas or ask any questions, feel free to post here, or just show up to the next meeting(s)! You can find more information, including how to sign up in this document.

+

3 posts - 2 participants

+

Read full topic

+ + + + + + + +
+

+by scastro on December 03, 2024 02:00 AM +

+ +
+ +
December 02, 2024
+ + + + + + + + +
+ + +
Gazebo Classic and Citadel End of Life [x-post Gazebo Sim Community]
+ +
from ROS Discourse General
+ +
+ +
+

Original Post

+

Hi Everyone,

+

This is your friendly reminder that as outlined here Gazebo Classic (i.e. Gazebo 11) will officially go end of life on Friday, January 31st, 2025. Gazebo Citadel, our first modern Gazebo LTS release, will go end of life on December 30th, 2024. Gazebo Classic users are advised to transition to an LTS modern Gazebo release as soon as possible (we recommend Gazebo Harmonic, or Gazebo Fortress). We recommend that Gazebo Citadel users also upgrade to either Harmonic or Fortress. Information about currently supported Gazebo versions and support windows, can be found here.

+

What does End of Life Mean?

+

Users often ask us, “what does end of life mean?” To put it briefly, end of life means that the Gazebo team will no longer support that particular Gazebo release. In practical terms, this means that we will no longer be providing the following for Gazebo Classic:

+
    +
  • New features or capabilities
    • +
  • Security updates
    • +
  • Bug fixes, patches or support
    • +
  • Updated binaries
    • +
+

It is also worth noting the things that won’t change after Gazebo Classic goes end of life:

+
    +
  • Gazebo Classic binaries will not suddenly disappear
    • +
  • Users will not need to migrate immediately, but they should migrate as soon as possible
    • +
  • Your project will not suddenly stop working on January 31st
    • +
+

Why do we End of Life Gazebo releases?

+

We End of Life particular Gazebo releases for the same reason that most people don’t use Windows XP or an iPhone 4 anymore: better versions of the software are now available and we simply don’t have the resources to support every Gazebo release into perpetuity. Marking a particular version of Gazebo end of life frees up resources to help support newer and better versions of the software. More to the point, the underlying packages and operating system (Ubuntu Focal) used by Gazebo Classic also goes end of life in April 2025.

+

How do I upgrade to a newer version of Gazebo and which one should I use?

+

We recommend that Gazebo Classic users upgrade to the latest long term support release of modern Gazebo, Gazebo Harmonic. Gazebo Harmonic works best on Ubuntu Jammy (22.04) and Ubuntu Noble (24.04) and will be supported until September of 2028. Gazebo Classic users who still use ROS 1 will also need to upgrade to ROS 2 Jazzy to use Gazebo Harmonic. It is worth noting that all of ROS 1, including ROS 1 Noetic, will go end of life on May 23rd, 2025. Our internal estimates indicate that over 80% of the ROS community has already upgraded to ROS 2, and 67% of Gazebo users have already upgraded to modern Gazebo.

+

The modern Gazebo documentation includes a variety of guides and tutorials on how to migrate your project from Gazebo Classic to modern Gazebo. Similarly, the ROS 2 documentation provides step by step instructions on how to migrate your ROS 1 project to ROS 2. If you get stuck during migration, we would encourage you to use the Open Robotics Discord, the Gazebo Sim Community, and Robotics Stack Exchange to find help.

+

Help Spread the Word

+

We realize that many Gazebo Classic users don’t really track Gazebo end of life dates, or regularly visit Gazebosim Community, that’s why we’ve decided to include some notifications about Gazebo Classic’s impending end of life in our latest Gazebo Classic update. Starting this week, after updating Gazebo Classic users will be notified via debug output and pop-ups of the upcoming end of life date. These warnings can be suppressed by simply setting a “GAZEBO_SUPPRESS_EOL_WARNING” environment variable.

+

We would appreciate the community’s help in spreading the word about the upcoming Gazebo Classic End of Life. If you work on a team that is still using Gazebo Classic please take a moment in the next week or two to discuss upgrade paths with your team and the importance of upgrading as soon as possible.

+

2 posts - 1 participant

+

Read full topic

+ + + + + + + +
+

+by Katherine_Scott on December 02, 2024 10:01 PM +

+ +
+ +
December 01, 2024
+ + + + + + + + +
+ + +
What versions of Moveit 2 are people using?
+ +
from ROS Discourse General
+ +
+ +
+

I’ve posted a poll on the Moveit 2 discussions board asking for feedback regarding which versions people are using, as it seems like it’d be interesting to gather some quantitative data.

+

Figured I’d post it here, too, for more visibility:

+ + +

1 post - 1 participant

+

Read full topic

+ + + + + + + +
+

+by TSNoble on December 01, 2024 11:36 PM +

+ +
+ +
November 28, 2024
+ + + + + + + + +
+ + +
Interoperability Interest Group December 05, 2024: Use Cases Around Open-RMF and Interoperability by Reply
+ +
from ROS Discourse General
+ +
+ +
+

Community Page

+

Meeting Link

+

Calendar Link

+

2024-12-05T15:00:00Z UTC

+

This month our friends from Reply will be presenting on work that they’ve been doing on robotics system integration using Open-RMF.

+

2 posts - 2 participants

+

Read full topic

+ + + + + + + +
+

+by grey on November 28, 2024 03:23 PM +

+ +
+ + + + + + + + + +
+ + +
Missing documentation for sensors?
+ +
from ROS Discourse General
+ +
+ +
+

Hey guys, I just migrated from ROS1 to ROS2 and I am running ROS2 Humble Hawksbill with Gazebo Harmonic (ik it’s not the default installation but yeah I pulled Harmonic separately). I am working on a basic project to bring a robot present in my academia to gazebo and I noticed that there is close to no documentation about the list of sensors and how to use them in our xacro files. There is some basic introduction here. But I don’t see any list of sensors and how to use them anywhere. Does this call for creating a well-defined documentation or am I really missing any website?

+

13 posts - 9 participants

+

Read full topic

+ + + + + + + +
+

+by vishcomestrue on November 28, 2024 07:09 AM +

+ +
+ +
November 27, 2024
+ + + + + + + + +
+ + +
OSRF Holiday Donation Drive
+ +
from ROS Discourse General
+ +
+ +
+

Thanksgiving

+

Hi Everyone,

+

Just a quick note before everyone heads off for the long holiday weekend here in the States. Next Tuesday is Giving Tuesday in the US, a day when many people make their big charitable donations for the holiday season.

+

This year, we’ve set up a donations page for the Open Source Robotics Foundation (OSRF) where you can specifically designate how you’d like your donation to be used. Want to help fund our infrastructure costs? Improve the ROS documentation? Support our educational efforts like the Diversity Scholars Program? Now you can choose!

+

We’re always thankful for your support, whether it’s monetary or a quick pull request! And remember, the OSRF is a 501(c)(3) tax-deductible charitable organization in the US.

+

If you, your colleagues, or your employer would like to support the OSRF and its mission, you can make a one-time or monthly donation using the new page. Many employers match charitable donations during the holiday season, so be sure to check if yours does. Here at Intrinsic, we’ve used our employee match program to raise almost $15,000 for the OSRF. We’d love to see other members of the ROS community join the effort.

+

Finally, please help us spread the word! Our Open Robotics community is huge, and if we all pitched in just a little bit we could make some amazing things happen in 2025.

+

Thank you for your support, and have a wonderful holiday season! :turkey:

+

4 posts - 4 participants

+

Read full topic

+ + + + + + + +
+

+by Katherine_Scott on November 27, 2024 11:08 PM +

+ +
+ + + +
+ + +
+ + +
+Powered by the awesome: Planet

+
+ + + diff --git a/opml.xml b/opml.xml new file mode 100644 index 00000000..6e0acad3 --- /dev/null +++ b/opml.xml @@ -0,0 +1,37 @@ + + + + Planet ROS + Mon, 16 Dec 2024 20:09:47 GMT + Open Robotics + info@openrobotics.org + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/planet.css b/planet.css new file mode 100644 index 00000000..e9800734 --- /dev/null +++ b/planet.css @@ -0,0 +1,132 @@ +body { + padding-left: 20px; + padding-right: 20px; + margin-top: 0; + font-family: "Arial",sans-serif; +} + +.top_block { + border-radius: 0 0 15px 15px; + -moz-border-radius: 0 0 15px 15px; + border-width: medium; + border-color: #2E3E60; + border-style:solid; + border-top: none; + margin-bottom:20px; + width:500px; + padding-bottom:15px; + padding-top:5px +} + +#participants { + text-align:left; +} + +#add_your_blog { + text-align:left; +} + +.ROS_planet_text { + font-size: 40pt; + font-family: "Interstate",sans-serif; + color:#2E3E60; + font-weight: bold; + font-stretch:semi-condensed; +} + +#top_info { + text-align: left; + border-radius: 15px; + -moz-border-radius: 15px; + border-width: medium; + border-color: #2E3E60; + border-style:solid; +} + +.entry { + font-size: 11pt; + margin-bottom: 2em; + padding-top: 20px; + padding-left: 20px; + padding-right: 20px; + padding-bottom: 10px; + text-align: left; + border-radius: 15px; + -moz-border-radius: 15px; + border-width: medium; + border-color: #2E3E60; + border-style:solid; + width: 800px; +} + +.entry .content { + padding-left: 20px; + padding-right: 20px; +} + +.entry .by_and_date { + color: grey; + text-align: right; +} + +.entry .by_and_date a { + text-decoration: none; + color: inherit; +} + +.entry_title { + font-weight: none; + font-size: 25pt; + padding-bottom: 20pt; + float:left; +} + +.channel_name { + color: grey; + font-weight: none; + float:right; +} + +.date { + font-size: 20pt; + font-weight: none; + color:#2E3E60; + padding-bottom: 15px; +} + +.entry a { + text-decoration: none; + color: #2E3E60; +} + +a:hover { + text-decoration: underline !important; +} + +.top_button { + color: grey; + text-decoration: none; + text-align: center; +} + +.top_button a:active, a:focus, input[type="image"] { +outline: 0; +} + +div.top_button { + padding-left: 30px; + padding-right: 30px; + text-align: center; +} + +.top_button img { + height: 30px; + width: 30px; + text-decoration: none; + text-align: center; +} + +.top_button .icon { + width: 30px; + height: 30px; +} diff --git a/rss10.xml b/rss10.xml new file mode 100644 index 00000000..f804c473 --- /dev/null +++ b/rss10.xml @@ -0,0 +1,1549 @@ + + + + Planet ROS + http://planet.ros.org + Planet ROS - http://planet.ros.org + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + ROS Discourse General: Is there a ROS 2 gazebo project for humanoids robots? + https://discourse.ros.org/t/is-there-a-ros-2-gazebo-project-for-humanoids-robots/41094 + <p>Dear ROS community,</p> +<p>I was researching if there are ROS 2 Gazebo project for humanoid robots that would facilitate in learning robot locomotion and whole-body motion planning. I am looking towards humanoids similar to Unitree’s H1/H2.</p> +<p>A research scientist from ETH Zurich pointed me to the Issac Gym environment that comes with the assets for H1/H2. But as far as I understand, that simulation pipeline does not use any ROS, and is meant for RL like research.</p> +<p>The closet project I found was Unitree’s ROS 1 project <a class="inline-onebox" href="https://github.com/unitreerobotics/unitree_ros" rel="noopener nofollow ugc">GitHub - unitreerobotics/unitree_ros</a> but it has not been updated for the newer ROS 2 and Gazebo.</p> +<p>Thank you for your time.</p> +<p>With best,<br /> +Azmyin</p> + <p><small>2 posts - 2 participants</small></p> + <p><a href="https://discourse.ros.org/t/is-there-a-ros-2-gazebo-project-for-humanoids-robots/41094">Read full topic</a></p> + 2024-12-15T05:41:56+00:00 + azmyin12 + + + ROS Discourse General: Opinion on companies still using ROS1 + https://discourse.ros.org/t/opinion-on-companies-still-using-ros1/41079 + <p>I would like to read what you think about taking a Job in companies who work extensively with ROS, but for one reason or another they are still in ROS1.<br /> +On one hand I realize that ROS is just a framework and that a lot can still be done and learned.<br /> +On the other, having worked for some years on both ROS and ROS2 I see the benefits of working with ROS2.<br /> +So I am torn and would like to hear other voices on the matter.</p> + <p><small>6 posts - 4 participants</small></p> + <p><a href="https://discourse.ros.org/t/opinion-on-companies-still-using-ros1/41079">Read full topic</a></p> + 2024-12-13T22:48:13+00:00 + iony_m + + + ROS Discourse General: ROS News for the Week of December 9th, 2024 + https://discourse.ros.org/t/ros-news-for-the-week-of-december-9th-2024/41073 + <h1><a class="anchor" href="https://discourse.ros.org#p-88510-ros-news-for-the-week-of-december-9th-2024-1" name="p-88510-ros-news-for-the-week-of-december-9th-2024-1"></a>ROS News for the Week of December 9th, 2024</h1> +<br /> +<p></p><div class="lightbox-wrapper"><a class="lightbox" href="https://global.discourse-cdn.com/flex022/uploads/ros/original/3X/f/3/f3d9d5342b7374ac0526df78b067dad56b1f0bee.jpeg" title="image"><img alt="image" height="345" src="https://global.discourse-cdn.com/flex022/uploads/ros/original/3X/f/3/f3d9d5342b7374ac0526df78b067dad56b1f0bee.jpeg" width="517" /></a></div><br /> +<img alt=":cn:" class="emoji" height="20" src="https://emoji.discourse-cdn.com/twitter/cn.png?v=12" title=":cn:" width="20" /> <img alt=":tada:" class="emoji" height="20" src="https://emoji.discourse-cdn.com/twitter/tada.png?v=12" title=":tada:" width="20" /> Our first ever ROSCon in China happened in Shanghai over the weekend! We want to congratulate the organizers on orchestrating such an impressive event. <a href="https://discourse.ros.org/t/roscon-china-2024-more-than-200-robotics-companies-participated/41029">You can find a recap of ROSCon China here.</a><br /> +<br /><p></p> +<p></p><div class="lightbox-wrapper"><a class="lightbox" href="https://global.discourse-cdn.com/flex022/uploads/ros/original/3X/c/7/c7be912533f5142c58a62011a97ee7b766602b37.jpeg" title="May 2023 - Nov 2024"><img alt="May 2023 - Nov 2024" height="194" src="https://global.discourse-cdn.com/flex022/uploads/ros/optimized/3X/c/7/c7be912533f5142c58a62011a97ee7b766602b37_2_345x194.jpeg" width="345" /></a></div><br /> +<a href="https://discourse.ros.org/t/iron-irwini-is-end-of-life/41031/2">ROS 2 Iron Irwini is now officially end-of-life</a>. If you are currently using Iron please consider upgrading to Jazzy!<p></p> +<br /> +<p><img alt="harp2" class="animated" height="136" src="https://global.discourse-cdn.com/flex022/uploads/ros/original/3X/e/4/e412077900cd1e52fab01fd99a57208448f0e4ef.gif" width="240" /><br /> +Check out the <a href="https://robotcopper.github.io/HARP/HARP2.html">HARP2 robot</a> that was posted to the ROS Discord server yesterday. The developer’s website is full of really great posts that are worth checking out, especially on the topic of microROS.</p> +<br /> +<p></p><div class="lightbox-wrapper"><a class="lightbox" href="https://global.discourse-cdn.com/flex022/uploads/ros/original/3X/1/3/136cf3f23f025849b44bb6bcc52f45998bf87e98.jpeg" title="poster-thumbnail"><img alt="poster-thumbnail" height="243" src="https://global.discourse-cdn.com/flex022/uploads/ros/optimized/3X/1/3/136cf3f23f025849b44bb6bcc52f45998bf87e98_2_345x243.jpeg" width="345" /></a></div><br /> +<a href="https://tidybot2.github.io/">The team behind TidyBot2</a> at Stanford and Princeton have open sourced the hardware for their robot. The robot supports a variety of arms and configurations allowing you to build a clone using hardware you may already have in the lab. See the <a href="https://tidybot2.github.io/docs/">docs</a> for more details.<p></p> +<br /> +<p></p><div class="lightbox-wrapper"><a class="lightbox" href="https://global.discourse-cdn.com/flex022/uploads/ros/original/3X/2/1/216a2ac455603652fbda5952ec9661defc9d6bd5.png" title="image"><img alt="image" height="250" src="https://global.discourse-cdn.com/flex022/uploads/ros/optimized/3X/2/1/216a2ac455603652fbda5952ec9661defc9d6bd5_2_280x250.png" width="280" /></a></div><br /> +This week <a href="https://rosindustrial.org/3d-camera-survey">ROS Industrial</a> released a comprehensive list of depth cameras for robotics applications. Even if you don’t need a new depth camera I recommend bookmarking this website for future website.<p></p> +<br /> +<p></p><div class="lightbox-wrapper"><a class="lightbox" href="https://global.discourse-cdn.com/flex022/uploads/ros/original/3X/6/9/6952c4de9dae5cdfea47cd10bb075cd8502088f4.png" title="image"><img alt="image" height="250" src="https://global.discourse-cdn.com/flex022/uploads/ros/optimized/3X/6/9/6952c4de9dae5cdfea47cd10bb075cd8502088f4_2_274x250.png" width="274" /></a></div><br /> +I want to send a big shout out <a class="mention" href="https://discourse.ros.org/u/abaeyens">@abaeyens</a> for putting together this fantastic documentation on <a href="https://docs.ros.org/en/rolling/Tutorials/Intermediate/Testing/Integration.html">ROS 2 integration testing</a> for <a href="http://docs.ros.org">docs.ros.org</a>. <img alt=":tada:" class="emoji" height="20" src="https://emoji.discourse-cdn.com/twitter/tada.png?v=12" title=":tada:" width="20" /><p></p> +<p>People often ask us how they can best contribute to the project. My recommendation is that when you run across something that feels not poorly documented take the time to summarize what you learned while figuring out how to solve the problem. <a href="https://discourse.ros.org/t/towards-a-rosdoc-integation-testing-tutorial/40701">That’s exactly what @abaeyens<br /> +did in this case and the results are excellent</a>.</p> +<br /> +<h1><a class="anchor" href="https://discourse.ros.org#p-88510-events-2" name="p-88510-events-2"></a>Events</h1> +<ul> +<li><a href="https://firahackathon.github.io/">2024-12-15 FIRA Ag Robotics Hackathon Registration Deadline</a></li> +<li><a href="https://autodrive-ecosystem.github.io/competitions/f1tenth-sim-racing-cdc-2024/">2024-12-16 =&gt; 2024-12-19 F1Tenth Sim Racing League at CDC 2024</a></li> +<li><a href="https://discourse.ros.org/t/aerial-robotics-meeting-xmas-with-bitcraze-dec-18-2024/40951">2024-12-18 Aerial Robotics meeting - Xmas with Bitcraze</a></li> +<li><a href="https://docs.google.com/forms/d/e/1FAIpQLSeiuWtUClyQ2Aj-CBFwZacpfL9xxgG_ZA8ImF0SF9sT2-sqKA/viewform">2024-12-22 Open Hardware Summit CFP Deadline</a></li> +<li><a href="https://www.naturalroboticscontest.com/">2024-12-31 Deadline for Natural Robotics Contest</a></li> +<li><a href="https://fosdem.org/2025/">2025-02-01 FOSDEM 25</a> – <a href="https://discourse.ros.org/t/fosdem-2025-robotics-simulation-first-edition/40349">See Robotics and Sim Room</a></li> +<li><a href="https://world-fira.com/">2025-02-04 =&gt; 2025-02-06 World FIRA Ag Robotics Conference in Toulouse, France</a></li> +<li><a href="https://discourse.ros.org/t/7th-international-workshop-on-robotics-software-engineering/39901">2025-04-28 International Workshop on Robotics Software Engineering</a></li> +<li><a href="https://2025.oshwa.org/">2025-05-30 =&gt; 2025-05-31 2025 Open Hardware Summit in Edinburgh</a></li> +</ul> +<h1><a class="anchor" href="https://discourse.ros.org#p-88510-news-3" name="p-88510-news-3"></a>News</h1> +<ul> +<li><a href="https://discourse.ros.org/t/roscon-china-2024-more-than-200-robotics-companies-participated/41029">ROSCon China 2024</a></li> +<li><a href="https://discourse.ros.org/t/ros-pmc-meeting-minutes-2024-12-10/41040">ROS PMC Meeting Minutes 2024-12-10</a></li> +<li><a href="https://www.ieee-ras.org/publications/ra-p">IEEE Robotics and Automation Society Launches new Journal</a></li> +<li><a href="https://discourse.ros.org/t/we-seek-for-your-feedback-to-shape-the-future-of-autoware/41038">We seek for your feedback to shape the future of Autoware!</a></li> +<li><a href="https://discourse.ros.org/t/how-important-is-ros-when-searching-for-a-job/41032">How important is ROS when searching for a job?</a></li> +<li><a href="https://techcrunch.com/2024/12/12/rip-cruise-robotaxi/">RIP, Cruise robotaxi</a>– <a href="https://www.therobotreport.com/gm-will-no-longer-fund-cruise-robotaxi-development/">The Robot Report</a></li> +<li><a href="https://www.therobotreport.com/diligent-robotics-new-ai-advisory-board-advance-embodied-ai-healthcare-robotics/">Diligent Robotics’ new AI Advisory Board to advance embodied AI in healthcare robotics</a></li> +<li><a href="https://techcrunch.com/2024/12/12/anybotics-raises-60m-to-scale-autonomous-industrial-robots-in-the-u-s/">Anybotics raises $60M to bring more autonomous industrial robots to the US</a></li> +<li><a href="https://techcrunch.com/2024/12/05/amp-robotics-raises-91m-to-build-more-robot-filled-waste-sorting-facilities/">Amp Robotics raises $91M to build more robot-filled waste-sorting facilities</a></li> +<li><a href="https://spectrum.ieee.org/fei-fei-li-world-labs">AI Pioneer Fei-Fei Li Has a Vision for Computer Vision</a></li> +<li><a href="https://spectrum.ieee.org/ai-safety">OpenAI, GoogleDeepMind, and Meta Get Bad Grades on AI Safety</a></li> +<li><a href="https://spectrum.ieee.org/video-friday-mars-chopper">Robot Videos: Mars Helicopter, Sanctuary AI, and More</a></li> +<li><a href="https://discourse.ros.org/t/safe-dds-achieves-iso-26262-asil-d-certification/41036">Safe DDS Achieves ISO 26262 ASIL D Certification</a></li> +<li><a href="https://discourse.ros.org/t/call-for-ifr-s-women-in-robotics-10-women-shaping-the-future-of-robotics-in-2025-is-now-open/41068">Call for “IFR’s Women in Robotics: 10 Women Shaping the Future of Robotics in 2025” is now open</a></li> +<li><a href="https://www.ieee-ras.org/about-ras/latest-news/call-students-participating-in-ieee-robotic-standardization-efforts-spirse">Grant for Students Participating in IEEE Robotic Standardization Efforts (SPIRSE)</a></li> +<li><a href="https://discourse.ros.org/t/robotics-engineers-are-in-high-demand-but-what-is-the-job-really-like/41015">Robotics engineers are in high demand — but what is the job really like?</a></li> +<li><a href="https://discourse.ros.org/t/interest-for-a-south-florida-ros-users-group/41008/2">Interest for a South Florida ROS Users Group?</a></li> +<li><a href="https://www.youtube.com/watch?v=kKCU3DM8PT0">Video: Kids Train Their Own AI-Powered Robot</a></li> +<li><a href="https://www.youtube.com/watch?v=oMIzIRqv1e0">Annual FZI Xmas Video</a></li> +<li><a href="https://www.space.com/the-universe/jupiter/nasa-tests-high-tech-software-for-future-mission-to-search-for-life-on-jupiters-moon-europa">NASA tests high-tech software for future mission to search for life on Jupiter’s moon Europa</a></li> +<li><a href="https://www.mccormick.northwestern.edu/robotics/inside-our-program/stories/2024/navigating-hazardous-terrain-at-nasas-jet-propulsion-laboratory.html">Navigating Hazardous Terrain at NASA’s Jet Propulsion Laboratory</a></li> +<li><a href="https://www.youtube.com/watch?v=_U0IYuIWwqk">ELISA Workshop at NASA Goddard, Washington, D.C.</a></li> +<li><a href="https://github.com/Robertleoj/pen_plotter_robot/blob/main/story.md">Pen Plotter Robot Build</a></li> +</ul> +<h1><a class="anchor" href="https://discourse.ros.org#p-88510-ros-4" name="p-88510-ros-4"></a>ROS</h1> +<ul> +<li><a href="https://discourse.ros.org/t/iron-irwini-is-end-of-life/41031/2">Iron Irwini is End-of-Life</a></li> +<li><a href="https://discourse.ros.org/t/quik-a-ultra-fast-and-robust-generalized-inverse-kinematics-solver-for-c-ros2/41024/4">QuIK: A ultra-fast and robust generalized inverse kinematics solver for C++/ROS2</a></li> +<li><a href="https://discourse.ros.org/t/towards-a-rosdoc-integation-testing-tutorial/40701/4">Towards a ROSdoc integation testing tutorial</a> – <a href="https://docs.ros.org/en/rolling/Tutorials/Intermediate/Testing/Integration.html">Docs link</a></li> +<li><a href="https://discourse.ros.org/t/gazebo-garden-officially-end-of-life-x-post-gazebo-sim-community/41044"><img alt=":checkered_flag:" class="emoji" height="20" src="https://emoji.discourse-cdn.com/twitter/checkered_flag.png?v=12" title=":checkered_flag:" width="20" /> Gazebo Garden officially end-of-life</a></li> +<li><a href="https://discourse.ros.org/t/extending-urdf-to-include-physical-interfaces-plugs-and-computing-component-e-g-control-boxes/41061">Extending URDF to include physical interfaces (plugs) and computing components (e.g., control boxes)</a></li> +<li><a href="https://discourse.ros.org/t/ros-2-rust-meeting-december-2024/40991">ROS 2 Rust Meeting: December 2024</a></li> +<li><a href="https://duckietown.com/monocular-navigation-in-duckietown-using-lednet-architecture/?utm_campaign=Student%27s%20Project&amp;utm_content=318875713&amp;utm_medium=social&amp;utm_source=twitter&amp;hss_channel=tw-991690269975371776">Monocular Navigation in Duckietown Using LEDNet Architecture</a></li> +<li><a href="https://github.com/SYSU-STAR/SOAR">IROS 2024: Simultaneous Exploration and Photographing with Heterogeneous UAVs for Fast Autonomous Reconstruction</a></li> +<li><a href="https://rosindustrial.org/3d-camera-survey"><img alt=":cool:" class="emoji" height="20" src="https://emoji.discourse-cdn.com/twitter/cool.png?v=12" title=":cool:" width="20" /> ROS Industrial 3D Camera Survey</a></li> +<li><a href="https://github.com/bdaiinstitute/proto2ros">Protobuf / ROS 2 interoperability layer</a></li> +<li><a href="https://github.com/tier4/umber_dds">DDS but in Rust</a></li> +<li><a href="https://github.com/sparolab/referee">ReFeree: Radar-based Lightweight and Robust Localization using Feature and Free space.</a></li> +<li><a href="https://github.com/xieyuser/GS-LIVM">GS-LIVM: Real-Time Photo-Realistic LiDAR-Inertial-Visual Mapping with Gaussian Splatting</a></li> +<li><a href="https://github.com/yorklyb/L-PR">Exploiting LiDAR Fiducial Marker for Unordered Low Overlap Multiview Point Cloud Registration</a></li> +<li><a href="https://arxiv.org/abs/2412.03887">MOANA: Multi-Radar Dataset for Maritime Odometry and Autonomous Navigation Application</a> – <a href="https://sites.google.com/corp/view/rpmmoana/">MOANA Dataset</a></li> +<li><a href="https://www.youtube.com/live/ithYYtUduMQ">Video: Articulation Rigging with ROS 2 Bridge</a></li> +<li><a href="https://github.com/ywyeli/UniDrive">UniDrive: Towards Universal Driving Perception Across Camera Configurations</a></li> +<li><a href="https://www.youtube.com/watch?v=B0fMZHYs_Vc">Video: Zenoh User Meeting 2024</a></li> +<li><a href="https://qiita.com/Ninagawa123/items/c4643ca92e57c3a45efb">URDF kitchen: A powerful GUI to help you create URDFs</a></li> +<li><a href="https://tidybot2.github.io/">TidyBot++: An Open-Source Holonomic Mobile Manipulator for Robot Learning</a> – <a href="https://tidybot2.github.io/docs/">docs</a></li> +<li><a href="https://github.com/Chyaru/Keyboard-controller-for-ROS2">Keyboard Controller for ROS 2</a></li> +<li><a href="https://github.com/danielpmorton/cbfpy/">Control Barrier Functions in Python and Jax</a> – <a href="https://danielpmorton.github.io/cbfpy/">docs</a></li> +<li><a href="https://github.com/Minipada/ros2_data_collection">Collect, validate and send data reliably from ROS 2 to create APIs and dashboards.</a></li> +<li><a href="https://arxiv.org/abs/2412.03760">Large-Scale Dense 3D Mapping Using Submaps Derived From Orthogonal Imaging Sonars</a></li> +<li><a href="https://robotcopper.github.io/HARP/HARP2.html">HARP2 Holonomic Robot</a></li> +<li><a href="https://github.com/pojenwang/Space-ROS-Isaac-Sim/">Space ROS Isaac Sim</a></li> +</ul> +<h1><a class="anchor" href="https://discourse.ros.org#p-88510-got-a-minute-alarm_clock-5" name="p-88510-got-a-minute-alarm_clock-5"></a>Got a minute? <img alt=":alarm_clock:" class="emoji" height="20" src="https://emoji.discourse-cdn.com/twitter/alarm_clock.png?v=12" title=":alarm_clock:" width="20" /></h1> +<p>All we want for Christmas are <a href="https://docs.ros.org/en/rolling/The-ROS2-Project/Contributing.html">pull requests to the ROS 2 docs</a>. <img alt=":gift:" class="emoji" height="20" src="https://emoji.discourse-cdn.com/twitter/gift.png?v=12" title=":gift:" width="20" /></p> + <p><small>1 post - 1 participant</small></p> + <p><a href="https://discourse.ros.org/t/ros-news-for-the-week-of-december-9th-2024/41073">Read full topic</a></p> + 2024-12-13T20:21:44+00:00 + Katherine_Scott + + + ROS Discourse General: Call for “IFR’s Women in Robotics: 10 Women Shaping the Future of Robotics in 2025” is now open + https://discourse.ros.org/t/call-for-ifr-s-women-in-robotics-10-women-shaping-the-future-of-robotics-in-2025-is-now-open/41068 + <h1><a class="anchor" href="https://discourse.ros.org#p-88501-call-for-ifrs-women-in-robotics-10-women-shaping-the-future-of-robotics-in-2025-is-now-open-1" name="p-88501-call-for-ifrs-women-in-robotics-10-women-shaping-the-future-of-robotics-in-2025-is-now-open-1"></a>Call for “IFR’s Women in Robotics: 10 Women Shaping the Future of Robotics in 2025” is now open</h1> +<h3><a class="anchor" href="https://discourse.ros.org#p-88501-the-international-federation-of-robotics-ifrhttpsifrorgifr-press-releasesnewscall-ifr-women-in-robotics-2025-is-looking-for-outstanding-women-in-robotics-2" name="p-88501-the-international-federation-of-robotics-ifrhttpsifrorgifr-press-releasesnewscall-ifr-women-in-robotics-2025-is-looking-for-outstanding-women-in-robotics-2"></a>The International Federation of Robotics (<a href="https://ifr.org/ifr-press-releases/news/call-ifr-women-in-robotics-2025" rel="noopener nofollow ugc">IFR</a>) is looking for outstanding women in robotics</h3> +<p><em>Dec 10, 2024 —</em> IFR would like to highlight and honor Women in Robotics - in particular women in the robotics industry - and give them more visibility. IFR will select a list of 10 women to officially award as “IFR’s Women in Robotics: 10 Women Shaping the Future of Robotics” in 2025.</p> +<p></p><div class="lightbox-wrapper"><a class="lightbox" href="https://global.discourse-cdn.com/flex022/uploads/ros/original/3X/9/6/96ba7ad97a9382cdf82718e435234cba6964a291.jpeg" rel="noopener nofollow ugc" title=""><img alt="" height="388" src="https://global.discourse-cdn.com/flex022/uploads/ros/optimized/3X/9/6/96ba7ad97a9382cdf82718e435234cba6964a291_2_690x388.jpeg" width="690" /></a></div><p></p> +<p>IFR decided to <strong>give women in robotics more visibility and acknowledgment</strong>. This should inspire girls and young women to pursue a career in STEM subjects or robotics and will also help companies to reach gender equality and overcome shortage of staff.</p> +<p>IFR would like to highlight and honor Women in Robotics - in particular women in the robotics industry - and give them more visibility.<br /> +IFR will select a list of 10 women to officially award as “IFR’s Women in Robotics: 10 Women Shaping the Future of Robotics” in 2025.</p> +<p><strong>IRF is in particular looking for women that have either a proven track record in robotics, stand out as industry leader or women with a proven activity in encouraging young people to go into STEM or that somehow support females in robotics.</strong></p> +<p><em>Deadline for submission is January 31st, 2025.</em></p> +<h3><a class="anchor" href="https://discourse.ros.org#p-88501-how-to-submit-a-suggestion-3" name="p-88501-how-to-submit-a-suggestion-3"></a>How to submit a suggestion</h3> +<p>Send an email to <a href="mailto:secretariat@ifr.org">secretariat@ifr.org</a><br /> +include a <strong>short bio</strong> and a description of <strong>what makes her noteworthy or particular</strong> with respect to our described scope<br /> +add her full name, affiliation, country, contact details and a photo</p> +<h3><a class="anchor" href="https://discourse.ros.org#p-88501-selection-criteria-4" name="p-88501-selection-criteria-4"></a>Selection criteria:</h3> +<ul> +<li>The suggested women needs to be active in the robotics industry</li> +<li>IFR will select at least one per continent,</li> +<li>but a maximum of one woman per company,</li> +<li>consider different company sizes (large, medium, small)</li> +<li>consider different company scope (Robot supplier IR, SR, component supplier, integrator) and</li> +<li>consider different levels of hierarchy (C-level, intermediate, lower level)</li> +<li>Proven track record in robotics / stand out as industry leader</li> +<li>Proven activity in encouraging young people to go into STEM or that somehow support females in robotics</li> +</ul> +<p><strong>Publication of results</strong> will be on International Women’s Day - March 8th, 2025.</p> +<p><a href="https://ifr.org/ifr-press-releases/news/10-women-shaping-the-future-of-robotics-2024" rel="noopener nofollow ugc">IFR’s 2024 Women in Robotics</a></p> +<p>Learn more on <a href="https://ifr.org/ifr-press-releases/news/world-bank-predicts-20-economic-boost-by-closing-gender-gap" rel="noopener nofollow ugc">why gender balance is beneficial for economies</a></p> +<ul> +<li><a href="https://ifr.org/img/office/IFR_Women_in_Robotics_Call2025.pdf" rel="noopener nofollow ugc"> IFR Women in Robotics: 2025 Call for nominations (576KB)</a></li> +</ul> + <p><small>1 post - 1 participant</small></p> + <p><a href="https://discourse.ros.org/t/call-for-ifr-s-women-in-robotics-10-women-shaping-the-future-of-robotics-in-2025-is-now-open/41068">Read full topic</a></p> + 2024-12-13T08:38:12+00:00 + ThiloZimmermann + + + ROS Discourse General: REUSE compatibility vs multi-package repo + https://discourse.ros.org/t/reuse-compatibility-vs-multi-package-repo/41063 + <p>Hi. I’ve started trying to have my repos <a href="https://reuse.software/spec-3.2/" rel="noopener nofollow ugc">REUSE-compliant</a>.</p> +<p>It seems that single-package repos can easily be turned into REUSE-compliant by adding all the SPDX comments to files, moving the top-level <code>LICENSE</code> file into <code>LICENSES/BSD-3-Clause.txt</code> and specifying <code>&lt;license file="LICENSES/BSD-3-Clause.txt"&gt;BSD&lt;/license&gt;</code> in <code>package.xml</code>.</p> +<p>However, if I want to do the same for a multi-package repo, then the <code>LICENSES</code> folder has to be a top-level one, i.e. at the same level as are the packages (that is a REUSE requirement). At the same time, I’d like to not have to copy all licenses to each package - as it’s best if each is stored only once. However, if I put <code>&lt;license file="../LICENSES/BSD-3-Clause.txt"&gt;</code> in <code>package.xml</code>, then <code>bloom-release</code> fails not being able to find the license file. That’s because it builds each package from the repo in a separate directory that is moved outside the repo.</p> +<p>I don’t see a clean solution how to satisfy both REUSE and bloom (except not adding the <code>file=</code> attribute, but I’d like to keep it). My current dirty workaround is to just copy the license file into the root of each subpackage. That’s not nice, but it does the job.</p> +<p>Does anybody know of a cleaner solution? I think it would be very nice if ROS deployment process would be compatible with REUSE.</p> + <p><small>5 posts - 3 participants</small></p> + <p><a href="https://discourse.ros.org/t/reuse-compatibility-vs-multi-package-repo/41063">Read full topic</a></p> + 2024-12-12T15:19:10+00:00 + peci1 + + + ROS Discourse General: Optimizations cpp ROS2 node. colcon build + https://discourse.ros.org/t/optimizations-cpp-ros2-node-colcon-build/41048 + <p>I’ve been using ROS2 for a year. Maybe previously you guys talked about this. However I’ve done experimental tests about the optimization C++ code ROS2 node and wrote a simple node.</p> +<pre><code class="lang-auto">#include "rclcpp/rclcpp.hpp" + +class HelloWorldNode : public rclcpp::Node +{ +public: + HelloWorldNode() : Node("hello_world_node") + { + RCLCPP_INFO(this-&gt;get_logger(), "Hello, World! This is a ROS2 node."); + } +}; + +int main(int argc, char **argv) +{ + rclcpp::init(argc, argv); + rclcpp::spin(std::make_shared&lt;HelloWorldNode&gt;()); + rclcpp::shutdown(); + return 0; +} + +</code></pre> +<p>Then by simply building the above code by using</p> +<pre><code class="lang-auto">colcon build +</code></pre> +<p>I got hello_node then explored assemble code</p> +<pre><code class="lang-auto">objdump -d &lt;path&gt;/hello_node &gt; hello_node.asm +</code></pre> +<p>got around 5000 lines of instruction code in hello_node.asm, it seems like it didn’t do any optimization to the code. Then run the following command</p> +<pre><code class="lang-auto">colcon build --cmake-args -DCMAKE_BUILD_TYPE=Release +///alternative +colcon build --cmake-args -DCMAKE_CXX_FLAGS="-O3 -march=native" + +</code></pre> +<p>then looked number instructions lines the number dramatically decreased from 5000 to 1700. the number of instruction lines in assemble doesn’t always mean it’s optimized yet it’s good factor.</p> +<p></p><div class="lightbox-wrapper"><a class="lightbox" href="https://global.discourse-cdn.com/flex022/uploads/ros/original/3X/6/8/68451cf4ffb2af3503e805517c6f42c1c297c70c.jpeg" rel="noopener nofollow ugc" title="Screenshot from 2024-12-11 16-24-11"><img alt="Screenshot from 2024-12-11 16-24-11" height="388" src="https://global.discourse-cdn.com/flex022/uploads/ros/optimized/3X/6/8/68451cf4ffb2af3503e805517c6f42c1c297c70c_2_690x388.jpeg" width="690" /></a></div><p></p> +<p>“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”"<br /> +simple by adding “set(CMAKE_BUILD_TYPE Release)” to your CMakeLists.txt is enough. then you can simply use colcon build.<br /> +<a href="https://gcc.gnu.org/onlinedocs/gcc/Optimize-Options.html" rel="noopener nofollow ugc">Optimizations flags</a></p> + <p><small>8 posts - 7 participants</small></p> + <p><a href="https://discourse.ros.org/t/optimizations-cpp-ros2-node-colcon-build/41048">Read full topic</a></p> + 2024-12-11T08:32:38+00:00 + Dony + + + ROS Discourse General: :checkered_flag: Gazebo Garden officially end-of-life [x-post Gazebo Sim Community] + https://discourse.ros.org/t/gazebo-garden-officially-end-of-life-x-post-gazebo-sim-community/41044 + <p><a href="https://community.gazebosim.org/t/gazebo-garden-officially-end-of-life/3278">Original Post</a></p> +<p>Dear ROS Community,</p> +<p>Gazebo Garden has reached end-of-life (EOL) as of November, 2024. Garden was <a href="https://community.gazebosim.org/t/gazebo-garden-release/1627">the seventh major release</a> of Gazebo and was supported for two years (non-LTS). It was the first release where Ignition was renamed Gazebo. It also introduced various exciting features, including custom shader plugins, Reset API, DEM support, lunar and custom surface coordinates, glTF and GLB mesh support, and an acoustic communication plugin, just to name a few. See the entire list of features on the <a href="https://gazebosim.org/docs/latest/release-features/#garden">Release Features page</a>.</p> +<p>We recommend all Garden users migrate to a supported release as soon as possible, such as <a href="https://ignitionrobotics.org/docs/harmonic" rel="noopener nofollow ugc">Harmonic (LTS)</a> or <a href="https://ignitionrobotics.org/docs/ionic" rel="noopener nofollow ugc">Ionic</a>, which are paired with ROS Jazzy and Rolling (Kilted once released) respectively. Migrating to either Harmonic or Ionic should be fairly smooth, however, be sure to check the release highlights for <a href="https://github.com/gazebosim/gz-harmonic/blob/main/highlights.md" rel="noopener nofollow ugc">Harmonic</a> and <a href="https://github.com/gazebosim/gz-ionic/blob/main/highlights.md" rel="noopener nofollow ugc">Ionic</a> in addition to checking each Gazebo library’s migration guide.</p> +<p>As part of the Garden EOL, the following Gazebo libraries have also reached end-of-life. Their latest released binaries will remain available at <a href="http://packages.osrfoundation.org/">http://packages.osrfoundation.org/</a>, but no more fixes or releases will be made.</p> +<div class="md-table"> +<table> +<thead> +<tr> +<th style="text-align: left;">Library major version</th> +<th style="text-align: left;">Final release</th> +</tr> +</thead> +<tbody> +<tr> +<td style="text-align: left;">gz-fuel-tools8</td> +<td style="text-align: left;">8.2.0</td> +</tr> +<tr> +<td style="text-align: left;">gz-sim7</td> +<td style="text-align: left;">7.9.0</td> +</tr> +<tr> +<td style="text-align: left;">gz-gui7</td> +<td style="text-align: left;">7.2.2</td> +</tr> +<tr> +<td style="text-align: left;">gz-launch6</td> +<td style="text-align: left;">6.2.0</td> +</tr> +<tr> +<td style="text-align: left;">gz-msgs9</td> +<td style="text-align: left;">9.5.1</td> +</tr> +<tr> +<td style="text-align: left;">gz-physics6</td> +<td style="text-align: left;">6.7.0</td> +</tr> +<tr> +<td style="text-align: left;">gz-rendering7</td> +<td style="text-align: left;">7.5.0</td> +</tr> +<tr> +<td style="text-align: left;">gz-sensors7</td> +<td style="text-align: left;">7.3.1</td> +</tr> +<tr> +<td style="text-align: left;">gz-transport12</td> +<td style="text-align: left;">12.2.2</td> +</tr> +<tr> +<td style="text-align: left;">sdformat13</td> +<td style="text-align: left;">13.9.0</td> +</tr> +</tbody> +</table> +</div><p><strong>We sincerely thank all contributors to all libraries in Garden <img alt=":pray:" class="emoji" height="20" src="https://emoji.discourse-cdn.com/twitter/pray.png?v=12" title=":pray:" width="20" /></strong></p> +<h3><a class="anchor" href="https://discourse.ros.org#p-88451-what-does-end-of-life-mean-1" name="p-88451-what-does-end-of-life-mean-1"></a>What does End of Life Mean?</h3> +<p>Users often ask us, “what does end of life mean?” To put it briefly, end of life means that the Gazebo team will no longer support that particular Gazebo release. In practical terms, this means that we will no longer be providing the following for Gazebo Garden:</p> +<ul> +<li>New features or capabilities</li> +<li>Security updates</li> +<li>Bug fixes, patches or support</li> +<li>Updated binaries</li> +</ul> +<p>It is also worth noting the things that won’t change after Gazebo Garden goes end of life:</p> +<ul> +<li>Gazebo Garden binaries <em>will not</em> suddenly disappear</li> +<li>Users <em>will not need</em> to migrate immediately, but they should migrate as soon as possible</li> +</ul> +<p><img alt=":gazebo:" class="emoji emoji-custom" height="20" src="https://global.discourse-cdn.com/flex022/uploads/ros/original/2X/6/65ca80e7c1f76154e9158bb4ad6aeaa5b25968cb.png?v=12" title=":gazebo:" width="20" /> Gazebo Dev Team <img alt=":gazebo:" class="emoji emoji-custom" height="20" src="https://global.discourse-cdn.com/flex022/uploads/ros/original/2X/6/65ca80e7c1f76154e9158bb4ad6aeaa5b25968cb.png?v=12" title=":gazebo:" width="20" /></p> + <p><small>1 post - 1 participant</small></p> + <p><a href="https://discourse.ros.org/t/gazebo-garden-officially-end-of-life-x-post-gazebo-sim-community/41044">Read full topic</a></p> + 2024-12-10T23:14:24+00:00 + azeey + + + ROS Discourse General: How important is ROS when searching for a job? + https://discourse.ros.org/t/how-important-is-ros-when-searching-for-a-job/41032 + <p>I have made an analysis of almost 2.000 jobs in LinkedIn and found out how relevant is ROS for getting a job as a robotics software developer. I included other interesting data about what matters for companies posting robotics jobs.</p> +<p>Check all that data in this video: <a href="https://youtu.be/wDeVNsD73A4?si=wcD3F1FizuJ52K3e" rel="noopener nofollow ugc">https://youtu.be/wDeVNsD73A4?si=wcD3F1FizuJ52K3e</a></p> +<p></p><div class="lightbox-wrapper"><a class="lightbox" href="https://global.discourse-cdn.com/flex022/uploads/ros/original/3X/7/0/70948045f3d694c112973bfe5cf4c28a46c74e7f.jpeg" rel="noopener nofollow ugc" title="Podcast-video-2024-Ricardo-Tellez-the-truth-about-ROS-jobs"><img alt="Podcast-video-2024-Ricardo-Tellez-the-truth-about-ROS-jobs" height="388" src="https://global.discourse-cdn.com/flex022/uploads/ros/optimized/3X/7/0/70948045f3d694c112973bfe5cf4c28a46c74e7f_2_690x388.jpeg" width="690" /></a></div><p></p> + <p><small>1 post - 1 participant</small></p> + <p><a href="https://discourse.ros.org/t/how-important-is-ros-when-searching-for-a-job/41032">Read full topic</a></p> + 2024-12-10T08:43:25+00:00 + ricardotellez + + + ROS Discourse General: Iron Irwini is End-of-Life + https://discourse.ros.org/t/iron-irwini-is-end-of-life/41031 + <p>Dear ROS Community,</p> +<p>It is bitter-sweet to announce that ROS 2 Iron Irwini is now end-of-life.</p> +<p></p><div class="lightbox-wrapper"><a class="lightbox" href="https://global.discourse-cdn.com/flex022/uploads/ros/original/3X/1/8/1844c68fbd9b3eb4e873ef39f2c57a7d0603b311.jpeg" rel="noopener nofollow ugc" title="ROS 2 Iron Irwini"><img alt="ROS 2 Iron Irwini" height="500" src="https://global.discourse-cdn.com/flex022/uploads/ros/optimized/3X/1/8/1844c68fbd9b3eb4e873ef39f2c57a7d0603b311_2_465x500.jpeg" width="465" /></a></div><p></p> +<p>Iron Irwini was released on May 23rd 2023 and marked the ninth distribution of ROS 2. Despite being a non-LTS release, it was feature packed (<a href="https://discourse.ros.org/t/ros-2-iron-irwini-released/">see more</a>).</p> +<p>Over the past year and half, there have been <a href="https://build.ros2.org/job/Irel_sync-packages-to-main/" rel="noopener nofollow ugc">40 distro syncs</a> and <a href="https://github.com/ros2/ros2/releases?q=iron&amp;expanded=true" rel="noopener nofollow ugc">7 patch releases</a> that cumulatively brought thousands of packages and updates to the community.</p> +<p>The <a href="https://github.com/ros2/ros2/releases/tag/release-iron-20241204" rel="noopener nofollow ugc">last patch</a> and sync (tagged <a href="https://github.com/ros/rosdistro/blob/iron/2024-12-04/iron/distribution.yaml" rel="noopener nofollow ugc"><code>iron/2024-12-04</code></a>) brought <strong>6</strong> new packages and <strong>320</strong> updates.</p> +Expand for details of the final sync <a href="https://discourse.ros.org/t/iron-irwini-is-end-of-life/41031/1">(click for more details)</a> +<p>The distribution has been marked end-of-life across <a href="http://docs.ros.org">docs.ros.org</a>, <a href="http://index.ros.org">index.ros.org</a> and <a href="https://github.com/ros/rosdistro" rel="noopener nofollow ugc">rosdistro</a>. CI and Buildfarm jobs have been disabled and will be deleted after a month assuming no issues crop up. The final snapshot of the distribution has been uploaded to <a href="http://snapshots.ros.org/iron/">snapshots.ros.org</a>. If you are currently using Iron, please switch to <a href="https://docs.ros.org/en/jazzy/">Jazzy Jalisco</a> which is the latest LTS release. The transition should be very smooth.</p> +<p>It has been a great privilege of mine to serve as the ROS Boss for Iron Irwini especially given that Steve Irwin was my childhood hero. A big thank you to all ROS maintainers and community members for making Iron Irwini such a successful release! <img alt=":iron:" class="emoji emoji-custom" height="20" src="https://global.discourse-cdn.com/flex022/uploads/ros/original/3X/b/3/b3c1340fc185f5e47c7ec55ef5bb1771802de993.png?v=12" title=":iron:" width="20" /> <img alt=":irwini:" class="emoji emoji-custom" height="20" src="https://global.discourse-cdn.com/flex022/uploads/ros/original/3X/d/2/d2f3dcbdaff6f33258719fe5b8f692594a9feab0.png?v=12" title=":irwini:" width="20" /></p> +<p>-Yadu</p> + <p><small>2 posts - 2 participants</small></p> + <p><a href="https://discourse.ros.org/t/iron-irwini-is-end-of-life/41031">Read full topic</a></p> + 2024-12-10T07:36:47+00:00 + Yadunund + + + ROS Discourse General: Guest Talk by Tomoya Fujita - Cloud Robotics WG Meeting 2024-12-16 + https://discourse.ros.org/t/guest-talk-by-tomoya-fujita-cloud-robotics-wg-meeting-2024-12-16/41021 + <p>Please come and join us for this coming meeting at 1700-1800 UTC on Monday 16th December 2024, where <a href="https://github.com/fujitatomoya" rel="noopener nofollow ugc">Tomoya Fujita</a> will be talking about Robotics Platforms empowered by Cloud-Native Technologies.</p> +<p>Tomoya is a software engineer, contributor to ROS2 core, and well-respected community builder. In this session, he will talk about a range of Cloud-Native Technologies he has worked on, and their relevance to robotics. In particular, Tomoya has done a great deal of work on KubeEdge, a platform built on Kubernetes that can be used to deploy software to robots as if they are Kubernetes clusters. Some resources from his talk includes:</p> +<ul> +<li><a href="https://roscon.ros.org/2023/talks/ROS_with_KubernetesKubeEdge.pdf">ROSCon 2023: ROS with Kubernetes / KubeEdge</a></li> +<li><a href="https://github.com/fujitatomoya/ros_k8s" rel="noopener nofollow ugc">Some examples to deploy ROS / ROS 2 with Kubernetes</a></li> +<li><a href="https://static.sched.com/hosted_files/colocatedeventsna2024/15/Cilium%2BeBPF-Day-NA_Cilium-with-KubeEdge.v0.pdf" rel="noopener nofollow ugc">Next-generation Robotics Platform for Edge/Cloud</a></li> +</ul> +<p>Tomoya also plans to leave time to discuss Cloud Robotics with the group, particularly the problems that people are having with Cloud Robotics.</p> +<p>Last meeting, we worked through a workshop for Eclipse Zenoh to test its capabilities and ease of setup. If you’re interested to see our progress, please check the <a href="https://youtu.be/NwZrAPGrDpU" rel="noopener nofollow ugc">meeting recording</a>.</p> +<p>If you are willing and able to give a talk on cloud robotics in future meetings, we would be happy to host you - please reply here, message me directly, or sign up using the <a href="https://docs.google.com/spreadsheets/d/1drBcG-CXmX8YxBZuRK8Lr3eTTfqe2p_RF_HlDw4Rj5g/edit?gid=0#gid=0" rel="noopener nofollow ugc">Guest Speaker Signup Sheet</a>. We will record your talk and host it on YouTube with our other meeting recordings too!</p> +<p>The meeting link is <a href="https://meet.google.com/xox-nshv-uvm" rel="noopener nofollow ugc">here</a>, and you can sign up to <a href="https://calendar.google.com/calendar/u/0/embed?src=c_3fc5c4d6ece9d80d49f136c1dcd54d7f44e1acefdbe87228c92ff268e85e2ea0@group.calendar.google.com" rel="noopener nofollow ugc">our calendar</a> or our <a href="https://groups.google.com/g/cloud-robotics-working-group-invites" rel="noopener nofollow ugc">Google Group</a> for meeting notifications.</p> +<p>Hopefully we will see you there!</p> + <p><small>1 post - 1 participant</small></p> + <p><a href="https://discourse.ros.org/t/guest-talk-by-tomoya-fujita-cloud-robotics-wg-meeting-2024-12-16/41021">Read full topic</a></p> + 2024-12-09T14:58:15+00:00 + mikelikesrobots + + + ROS Discourse General: Robotics engineers are in high demand — but what is the job really like? + https://discourse.ros.org/t/robotics-engineers-are-in-high-demand-but-what-is-the-job-really-like/41015 + <p><a href="https://www.youtube.com/watch?v=z_uGhq2ayVA">Robotics engineers are in high demand — but what is the job really like?</a></p> + + <p><small>2 posts - 1 participant</small></p> + <p><a href="https://discourse.ros.org/t/robotics-engineers-are-in-high-demand-but-what-is-the-job-really-like/41015">Read full topic</a></p> + 2024-12-08T23:32:15+00:00 + ruffsl + + + ROS Discourse General: ROS News for the Week of December 2nd, 2024 + https://discourse.ros.org/t/ros-news-for-the-week-of-december-2nd-2024/40997 + <h1><a class="anchor" href="https://discourse.ros.org#p-88375-ros-news-for-the-week-of-december-2nd-2024-1" name="p-88375-ros-news-for-the-week-of-december-2nd-2024-1"></a>ROS News for the Week of December 2nd, 2024</h1> +<p></p><div class="lightbox-wrapper"><a class="lightbox" href="https://global.discourse-cdn.com/flex022/uploads/ros/original/3X/7/1/71f9dbb6dd793e528e6b7dc0f823db7b16b6d66a.jpeg" title="GeCwHKiX0AAHleo"><img alt="GeCwHKiX0AAHleo" height="250" src="https://global.discourse-cdn.com/flex022/uploads/ros/optimized/3X/7/1/71f9dbb6dd793e528e6b7dc0f823db7b16b6d66a_2_333x250.jpeg" width="333" /></a></div><div class="lightbox-wrapper"><a class="lightbox" href="https://global.discourse-cdn.com/flex022/uploads/ros/original/3X/9/f/9f7d76e4cd5fcbbdcca69965bf2929822fded345.jpeg" title="Gd-rDnlW4AAsP38"><img alt="Gd-rDnlW4AAsP38" height="230" src="https://global.discourse-cdn.com/flex022/uploads/ros/optimized/3X/9/f/9f7d76e4cd5fcbbdcca69965bf2929822fded345_2_345x230.jpeg" width="345" /></a></div><br /> +ROSCon Germany and ROSCon India were both this week! It was really exciting to see two ROS events happening concurrently on two different parts of the globe. We want to congratulate the organizers and attendees on putting together fantastic events.<p></p> +<ul> +<li><a href="https://x.com/purushottamshet/status/1864683903409148096">ROSCon India photo from @purushottamshet on Twitter</a></li> +<li><a href="https://x.com/stoglrobotics/status/1864397010998042805/photo/1">ROSCon Germany photo from @stoglrobotics on Twitter</a></li> +</ul> +<p></p><div class="lightbox-wrapper"><a class="lightbox" href="https://global.discourse-cdn.com/flex022/uploads/ros/original/3X/7/7/775a0e1e4201695f64be7a4bcbd10757a3fc904b.jpeg" title="ROSCon_China_2024"><img alt="ROSCon_China_2024" height="375" src="https://global.discourse-cdn.com/flex022/uploads/ros/optimized/3X/7/7/775a0e1e4201695f64be7a4bcbd10757a3fc904b_2_376x375.jpeg" width="376" /></a></div><br /> +But wait, there’s more! Our first ever <a href="https://www.roscon.cn/2024/index.html">ROSCon China</a> in Shanghai is about to kick off in about four or five hours.<p></p> +<br /> +<p></p><div class="lightbox-wrapper"><a class="lightbox" href="https://global.discourse-cdn.com/flex022/uploads/ros/original/3X/8/7/87978cd5a5b63e38d982ed533928a5d73bb94c03.jpeg" title="9cqsf8"><img alt="9cqsf8" height="375" src="https://global.discourse-cdn.com/flex022/uploads/ros/optimized/3X/8/7/87978cd5a5b63e38d982ed533928a5d73bb94c03_2_374x375.jpeg" width="374" /></a></div><br /> +While we’re welcoming so many new friends to the ROS community we’re also getting ready to say farewell to <a href="https://dlu.github.io/ros_clock/index.html">ROS 1 Noetic</a>, <a href="https://discourse.ros.org/t/gazebo-classic-and-citadel-end-of-life-x-post-gazebo-sim-community/40931">Gazebo Classic, Gazebo Citadel</a>, and <a href="https://discourse.ros.org/t/preparing-for-final-iron-irwini-patch-release-and-sync-2024-11-18/40619">ROS 2 Iron Irwini</a>.<p></p> +<br /> +<p></p><div class="lightbox-wrapper"><a class="lightbox" href="https://global.discourse-cdn.com/flex022/uploads/ros/original/3X/0/0/00840d8b17a4ec3d6663d42e439242720c0a043e.jpeg" title="SGDecROSMeetup"><img alt="SGDecROSMeetup" height="291" src="https://global.discourse-cdn.com/flex022/uploads/ros/optimized/3X/0/0/00840d8b17a4ec3d6663d42e439242720c0a043e_2_517x291.jpeg" width="517" /></a></div><br /> +We have two ROS Meetups planned for 2024-12-12. <a href="https://www.meetup.com/singapore-ros-meetup/events/304791372">One meetup in Singapore</a> and <a href="https://discourse.ros.org/t/meetup-fin-de-ano-de-ros-barcelona/40880">another one in Barcelona Spain</a><p></p> +<br /> +<p></p><div class="lightbox-wrapper"><a class="lightbox" href="https://global.discourse-cdn.com/flex022/uploads/ros/original/3X/0/8/0886c02ebe7cf611b3d87c1a059892a4b6cb6610.jpeg" title="Thanksgiving"><img alt="Thanksgiving" height="291" src="https://global.discourse-cdn.com/flex022/uploads/ros/optimized/3X/0/8/0886c02ebe7cf611b3d87c1a059892a4b6cb6610_2_517x291.jpeg" width="517" /></a></div><br /> +If you are in a giving mood this holiday season we are currently running <a href="https://discourse.ros.org/t/osrf-holiday-donation-drive/40852">a donation campaign for the OSRF</a>. We’ve made it possible for you to earmark your donation for particular OSRF projects like the ROS Build Farm, the ROS Documentation, and our educational outreach initiatives.<p></p> +<br /> +<p></p><div class="lightbox-wrapper"><a class="lightbox" href="https://global.discourse-cdn.com/flex022/uploads/ros/original/3X/1/5/158b104ca9c6e150a6639b69b1ad19f1149e12b1.jpeg" title="Aug24GCM (1)"><img alt="Aug24GCM (1)" height="194" src="https://global.discourse-cdn.com/flex022/uploads/ros/optimized/3X/1/5/158b104ca9c6e150a6639b69b1ad19f1149e12b1_2_345x194.jpeg" width="345" /></a></div><br /> +At last week’s <a href="https://discourse.ros.org/t/november-gazebo-community-meeting-nasa-space-ros-challenge/40848">Gazebo Community Meeting</a> we met multiple competitors from the NASA SpaceROS Summer Sprint Challenge. The results are absolutely amazing and are all open source! We recommend you check it out.<p></p> +<h1><a class="anchor" href="https://discourse.ros.org#p-88375-events-2" name="p-88375-events-2"></a>Events</h1> +<ul> +<li><a href="https://discourse.ros.org/t/looking-for-austin-ros-meetup-speakers/40981">Looking for Austin ROS Meetup Speakers!</a></li> +<li><a href="https://lu.ma/2lkm9otp?tk=wqm4zy">2024-12-07 Circuit Launch Mountain View Grand Opening</a></li> +<li><a href="https://www.roscon.cn/2024/index.html">2024-12-07 → 2024-12-08 ROSCon China in Shenzhen</a></li> +<li><a href="https://discourse.ros.org/t/ros-2-rust-meeting-december-2024/40991">2024-12-10 ROS 2 Rust Meeting: December 2024</a></li> +<li><a href="https://humanoidssummit.com/">2024-12-11 =&gt; 2024-12-12 Humanoids Summit Bay Area</a></li> +<li><a href="https://discourse.ros.org/t/embodied-ai-community-group-meeting-2/40987">2024-12-11 Embodied AI Community Group meeting 2</a></li> +<li><a href="https://www.meetup.com/singapore-ros-meetup/events/304791372">2024-12-12 ROS Meetup Singapore</a></li> +<li><a href="https://discourse.ros.org/t/meetup-fin-de-ano-de-ros-barcelona/40880">2024-12-12 ROS Meetup Barcelona</a></li> +<li><a href="https://firahackathon.github.io/">2024-12-15 FIRA Ag Robotics Hackathon Registration Deadline</a></li> +<li><a href="https://autodrive-ecosystem.github.io/competitions/f1tenth-sim-racing-cdc-2024/">2024-12-16 =&gt; 2024-12-19 F1Tenth Sim Racing League at CDC 2024</a></li> +<li><a href="https://discourse.ros.org/t/aerial-robotics-meeting-xmas-with-bitcraze-dec-18-2024/40951">2024-12-18 Aerial Robotics meeting - Xmas with Bitcraze</a></li> +<li><a href="https://docs.google.com/forms/d/e/1FAIpQLSeiuWtUClyQ2Aj-CBFwZacpfL9xxgG_ZA8ImF0SF9sT2-sqKA/viewform">2024-12-22 Open Hardware Summit CFP Deadline</a></li> +<li><a href="https://www.naturalroboticscontest.com/">2024-12-31 Deadline for Natural Robotics Contest</a></li> +<li><a href="https://fosdem.org/2025/">2025-02-01 FOSDEM 25</a> – <a href="https://discourse.ros.org/t/fosdem-2025-robotics-simulation-first-edition/40349">See Robotics and Sim Room</a></li> +<li><a href="https://world-fira.com/">2025-02-04 =&gt; 2025-02-06 World FIRA Ag Robotics Conference in Toulouse, France</a></li> +<li><a href="https://discourse.ros.org/t/7th-international-workshop-on-robotics-software-engineering/39901">2025-04-28 International Workshop on Robotics Software Engineering</a></li> +<li><a href="https://2025.oshwa.org/">2025-05-30 =&gt; 2025-05-31 2025 Open Hardware Summit in Edinburgh</a></li> +</ul> +<h1><a class="anchor" href="https://discourse.ros.org#p-88375-news-3" name="p-88375-news-3"></a>News</h1> +<ul> +<li><a href="https://discourse.ros.org/t/osrf-holiday-donation-drive/40852">OSRF Holiday Donation Drive</a></li> +<li><a href="https://discourse.ros.org/t/november-gazebo-community-meeting-nasa-space-ros-challenge/40848"><img alt=":cool:" class="emoji" height="20" src="https://emoji.discourse-cdn.com/twitter/cool.png?v=12" title=":cool:" width="20" /> November Gazebo Community Meeting: NASA Space ROS Challenge</a></li> +<li><a href="https://discourse.ros.org/t/call-for-participation-ros-deliberation-community-group/40932">Call for Participation: ROS Deliberation Community Group</a></li> +<li><a href="https://discourse.ros.org/t/robotic-blending-milestone-5-highlight-video-live/40920">Robotic Blending Milestone 5 Highlight Video Live</a></li> +<li><a href="https://discourse.ros.org/t/open-call-for-eurobotics-technology-transfer-award-2025/40978">Call for euRobotics Technology Transfer Award 2025</a></li> +<li><a href="https://www.ieee-ras.org/membership/dei-committee/idea-travel-support">IEEE RAS DEI / Accessibilty Travel Support Grant</a></li> +<li><a href="https://discourse.ros.org/t/osra-tgc-meeting-minutes-for-october-2024/40768">OSRA TGC meeting minutes for October, 2024</a></li> +<li><a href="https://discourse.ros.org/t/ros-pmc-meeting-minutes-2024-12-03/40941">ROS PMC Meeting minutes 2024-12-03</a></li> +<li><a href="https://discourse.ros.org/t/ros-pmc-meeting-minutes-2024-11-26/40833">ROS PMC Meeting minutes 2024-11-26</a></li> +<li><a href="https://elisa.tech/event/elisa-workshop-at-nasa-goddard-space-grade-linux/">ELISA Workshop at NASA Goddard – Space Grade Linux</a></li> +<li><a href="https://www.youtube.com/watch?v=lyPkcCAOrP8">How Arduino Forged a Path for Open Hardware - David Cuartielles, Co-Founder, Arduino</a></li> +<li><a href="https://github.com/GimpelZhang/GaussianRPG">GaussianRPG: 3D Gaussian Rendering PlayGround: an open-source autonomous driving closed-loop simulator demo using 3D Gaussian Splatting tech</a></li> +<li><a href="https://www.youtube.com/watch?v=DvvFEh0PmvU&amp;t=1s">Jeffrey Ichnowski : Learning for Dynamic Robot Manipulation of Deformable Objects</a></li> +<li><a href="https://www.youtube.com/watch?v=hBWMQvCjevs">Sebastian Castro: Research and Industry Future in Robotics</a></li> +<li><a href="https://weed-ai.sydney.edu.au/explore?is_head_filter=%5B%22latest+version%22%5D">Weed Dataset (for agriculture)</a></li> +<li><a href="https://www.youtube.com/watch?v=2XHhq9hQB0g">Video: Crazyflie at Bitcraze’s Headquarters in Malmö, Sweden</a></li> +<li><a href="https://www.therobotreport.com/teleo-raises-16-2-million-to-scale-supervised-autonomy-for-heavy-equipment/">Teleo raises $16.2M to scale supervised autonomy for heavy equipment</a></li> +<li><a href="https://picknik.ai/2024/11/05/SBIR-Space-contract-wins.html">PickNik Robotics Secures $3 Million in NASA and Space Force</a></li> +<li><a href="https://techcrunch.com/2024/12/05/amp-robotics-raises-91m-to-build-more-robot-filled-waste-sorting-facilities/">Amp Robotics raises $91M</a> – <a href="https://www.therobotreport.com/amp-robotics-raises-91m-accelerate-deployment-recycling-systems/">The Robot Report</a></li> +<li><a href="https://www.therobotreport.com/a300-clearpath-robotics-discusses-development/">Clearpath Robotics discusses development of Husky A300 ground vehicle</a></li> +<li><a href="https://www.therobotreport.com/astm-developing-testing-standards-for-mobile-manipulators/">ASTM developing testing standards for mobile manipulator</a></li> +<li><a href="https://techcrunch.com/2024/12/05/arx-launches-firestick-like-platform-to-make-military-trucks-autonomous/">ARX launches firestick-like platform to make military trucks autonomous</a></li> +<li><a href="https://discourse.ros.org/t/fosdem-2025-robotics-simulation-first-edition/40349">FOSDEM 2025: Robotics &amp; Simulation… first edition!</a></li> +</ul> +<h1><a class="anchor" href="https://discourse.ros.org#p-88375-ros-4" name="p-88375-ros-4"></a>ROS</h1> +<ul> +<li><a href="https://discourse.ros.org/t/gazebo-classic-and-citadel-end-of-life-x-post-gazebo-sim-community/40931">Gazebo Classic and Citadel End of Life</a></li> +<li><a href="https://discourse.ros.org/t/new-book-ros-2-from-scratch/40807">New Book - ROS 2 from Scratch</a></li> +<li><a href="https://discourse.ros.org/t/new-packages-for-noetic-2024-12-06/40995">New Packages for Noetic 2024-12-06</a></li> +<li><a href="https://discourse.ros.org/t/new-packages-and-patch-release-for-humble-hawksbill-2024-12-05/40976">New packages for Humble Hawksbill 2024-12-05</a></li> +<li><a href="https://discourse.ros.org/t/new-packages-for-ros-2-rolling-ridley-2024-11-26/40835">New packages for ROS 2 Rolling Ridley 2024-11-26</a></li> +<li><a href="https://discourse.ros.org/t/preparing-for-final-iron-irwini-patch-release-and-sync-2024-11-18/40619">Preparing for final Iron Irwini Patch Release and Sync 2024-11-18</a></li> +<li><a href="https://discourse.ros.org/t/iron-irwini-eol-plan/40365">Iron Irwini EOL Plan</a></li> +<li><a href="https://discourse.ros.org/t/rmw-iceoryx2-v0-1-0-release/40996">rmw_iceoryx2 v0.1.0 release</a></li> +<li><a href="https://discourse.ros.org/t/leveraging-ros-build-infrastructure-for-non-ros-packages/40658">Leveraging ROS build infrastructure for non-ROS packages</a></li> +<li><a href="https://discourse.ros.org/t/clearpath-simulator-comes-to-gazebo-harmonic/40975">Clearpath Simulator comes to Gazebo Harmonic <img alt=":fire:" class="emoji" height="20" src="https://emoji.discourse-cdn.com/twitter/fire.png?v=12" title=":fire:" width="20" /></a></li> +<li><a href="https://discourse.ros.org/t/expose-secure-communication-only-with-specified-entities/40957">Expose secure communication only with specified entities</a></li> +<li><a href="https://discourse.ros.org/t/reference-implementation-of-zenoh-pico-to-micro-ros/40750">Reference implementation of Zenoh-pico to micro-ROS</a></li> +<li><a href="https://discourse.ros.org/t/notice-nav2-migrated-to-twiststamped-to-replace-twist-for-cmd-vel-topics/40944">Nav2 Migrated to TwistStamped to replace Twist for cmd_vel Topics</a></li> +<li><a href="https://discourse.ros.org/t/towards-a-rosdoc-integation-testing-tutorial/40701">Towards a ROSdoc integation testing tutorial</a></li> +<li><a href="https://discourse.ros.org/t/polar-grid-rviz-plugin/40909">Polar Grid Rviz Plugin - ROS Projects</a></li> +<li><a href="https://discourse.ros.org/t/fusionsdf-export-fusion-360-cad-designs-to-sdf/39430">FusionSDF: Export Fusion 360 CAD designs to SDF</a></li> +<li><a href="https://discourse.ros.org/t/ros-2-reinforcement-learning/40898">ROS 2 Reinforcement learning</a></li> +<li><a href="https://discourse.ros.org/t/new-ros2-package-for-dynamically-interpolating-3d-lidar-point-clouds/40876">New ROS 2 package for dynamically interpolating 3D LiDAR point clouds</a></li> +<li><a href="https://discourse.ros.org/t/help-needed-distribute-a-ros-package-against-multiple-sdk-versions/40827">Help needed: Distribute a ROS package against multiple SDK versions</a></li> +<li><a href="https://discourse.ros.org/t/ros-2-whisper-update/40808">ROS 2 Whisper update</a></li> +<li><a href="https://github.com/victorcarvesk/ros-voice-assistant">ros-voice-assistant: A ROS 2 package for building voice-enabled robotic applications</a></li> +<li><a href="https://arxiv.org/abs/2412.03887">MOANA: Multi-Radar Dataset for Maritime Odometry and Autonomous Navigation Application</a> – <a href="https://sites.google.com/corp/view/rpmmoana/">MOANA Dataset</a></li> +<li><a href="https://github.com/ChenHoy/DROID-Splat">DROID-Splat: End-to-End SLAM with camera calibration, monocular prior integration and dense Rendering</a></li> +<li><a href="https://github.com/alesof/ROS2-VSC-Toolkit">ROS2-VSC-Toolkit: Visual Studio Code Extension for ROS 2 development</a></li> +<li><a href="https://marketplace.visualstudio.com/items?itemName=morningfrog.urdf-visualizer">URDF Visualizer - Visual Studio Plugin</a></li> +<li><a href="https://github.com/hijimasa/ros2-tools-to-use-unity-like-gazebo">ros2-tools-to-use-unity-like-gazebo: ros2_control in Unity</a></li> +<li><a href="https://github.com/luohongk/SuperVINS">SuperVINS: A real-time visual-inertial SLAM framework for challenging imaging conditions</a></li> +<li><a href="https://ekumenlabs.com/blog/posts/big-shoes-to-fill-beluga-performance-report/">Validating the performance of Beluga AMCL</a></li> +<li><a href="https://github.com/agimus-project/happypose_ros"><img alt=":cool:" class="emoji" height="20" src="https://emoji.discourse-cdn.com/twitter/cool.png?v=12" title=":cool:" width="20" /> happypose_ros: ROS 2 wrapper for a 6D pose estimation library</a></li> +<li><a href="https://github.com/HiroIshida/plainmp">plainmp: Very fast motion planning for articulated robot, through a bit of premature-optimization (C++ / Python)</a></li> +<li><a href="https://github.com/nobleo/full_coverage_path_planner">full_coverage_path_planner with a move_base_flex plugin</a></li> +<li><a href="https://github.com/liangheming/VoxelMapPlus_FASTLIO2">VoxelMapPlus_FASTLIO2: FAST-LIO 2 with VoxelMapPlus and STD</a></li> +<li><a href="https://github.com/NKU-MobFly-Robotics/SPTG-LCC">SPTG-LCC: Single-shot, Pixel-level, Target-free and General LiDAR-Camera Extrinsic Self-Calibration</a></li> +<li><a href="https://github.com/karlkurzer/path_planner">path_planner: Hybrid A* Path Planner for the KTH Research Concept Vehicle</a></li> +<li><a href="https://github.com/Liansheng-Wang/InGM-LIO">InGM-LIO: InGM-LIO: A Multiscale Gaussian Model-Based LiDAR-Inertial Odometry Using Invariant Kalman Filtering.</a></li> +<li><a href="https://github.com/UTS-RI/2fast2lamaa">2fast2lamaa: Real-time lidar-inertial odometry and mapping framework for dynamic environments</a></li> +<li><a href="https://github.com/PRBonn/kinematic-icp">kinematic-icp: A LiDAR odometry pipeline for wheeled mobile robots</a></li> +<li><a href="https://github.com/MizuhoAOKI/python_simple_mppi">python_simple_mppi: Python implementation of MPPI (Model Predictive Path-Integral) controller</a></li> +<li><a href="https://github.com/Geekgineer/YOLOs-CPP">YOLOs-CPP: A high-performance C++ headers for real-time object detection using YOLO models</a></li> +<li><a href="https://github.com/ghm0819/ERPoT">ERPoT: Effective and Reliable Pose Tracking for Mobile Robots Based on Lightweight and Compact Polygon Maps</a></li> +<li><a href="https://github.com/kyavuzkurt/multicast_parser">multicast_parser: ROS Package for parsing multicast data from Motive Tracker 2.0.2 to Appropriate Nodes</a></li> +<li><a href="https://github.com/winstxnhdw/AutoCarROS2">AutoCarROS2: A virtual simulation platform for autonomous vehicle sensing, mapping, control and behaviour methods using ROS 2 and Gazebo.</a></li> +<li><a href="https://ieeexplore.ieee.org/document/10684721">SlicerROS2: A Research and Development Module for Image-Guided Robotic Interventions</a></li> +<li><a href="https://github.com/anujjain-dev/unitree-go2-ros2">unitree-go2-ros2: URDF for Unitree Go2 with Champ Controller</a></li> +<li><a href="https://ieeexplore.ieee.org/document/10769556">DPFT: Dual Perspective Fusion Transformer for Camera-Radar-based Object Detection</a> – <a href="https://github.com/TUMFTM/DPFT">source</a></li> +<li><a href="https://github.com/saadi-tech/kidnapped_robot_finder">kidnapped_robot_finder: TROS 2 package for 2d-Lidar scanner based kidnapped robot re-localization</a></li> +</ul> +<h1><a class="anchor" href="https://discourse.ros.org#p-88375-got-a-minute-alarm_clock-5" name="p-88375-got-a-minute-alarm_clock-5"></a>Got a Minute? <img alt=":alarm_clock:" class="emoji" height="20" src="https://emoji.discourse-cdn.com/twitter/alarm_clock.png?v=12" title=":alarm_clock:" width="20" /></h1> +<p>We would really appreciate it if you took ten minutes to answer just one ROS question on <a href="https://robotics.stackexchange.com/?tags=ros2">Robotics Stack Exchange</a>.</p> + <p><small>1 post - 1 participant</small></p> + <p><a href="https://discourse.ros.org/t/ros-news-for-the-week-of-december-2nd-2024/40997">Read full topic</a></p> + 2024-12-06T20:59:45+00:00 + Katherine_Scott + + + ROS Discourse General: rmw_iceoryx2 v0.1.0 release + https://discourse.ros.org/t/rmw-iceoryx2-v0-1-0-release/40996 + <p>Hi all,</p> +<p><code>orecham</code> here, one of the committers from the <code>eclipse-iceoryx</code> project.</p> +<p>I’m pleased to announce the alpha release of <code>rmw_iceoryx2</code>, compatible with ROS 2 <code>rolling</code> and available at: <a class="inline-onebox" href="https://github.com/ekxide/rmw_iceoryx2" rel="noopener nofollow ugc">GitHub - ekxide/rmw_iceoryx2: ROS 2 RMW implementation for iceoryx2</a></p> +<p>Why yet another RMW? We have the following goals for <code>rmw_iceoryx2</code>:</p> +<ol> +<li>Bring the high-performance zero-copy shared-memory communication offered by <a href="https://github.com/eclipse-iceoryx/iceoryx2/tree/main" rel="noopener nofollow ugc"><code>iceoryx2</code></a> to ROS 2 applications</li> +<li>Provide a unique option for reducing safety certification effort of ROS 2 applications with safety-critical use-cases</li> +</ol> +<p>Rather than require the entire ROS 2 stack be certified (e.g. for ASIL-D), <code>rmw_iceoryx2</code> offers an alternative through interoperability between ROS 2 and <code>iceoryx2</code> applications. This allows the freedom for porting safety-critical components that require certification to <code>iceoryx2</code> (which is designed for certification) while still participating in the ROS 2 ecosystem.</p> +<h2><a class="anchor" href="https://discourse.ros.org#p-88374-current-state-1" name="p-88374-current-state-1"></a>Current State</h2> +<p>With this first alpha release, there is still some work to do and polish to be made. Not all features are yet available and existing ones need thorough real-world validation. Most notably, support for message serialization is not yet available nor service-client communication (waiting on some features to be completed in <code>iceoryx2</code>). Lack of serialization support means that <code>rmw_iceoryx2</code> can currently only work with self-contained message types, however, this will be one of the first limitations to address next.</p> +<p>Furthermore, only intra-host communication is currently possible. We have plans to introduce host-to-host capabilities in the near future by leveraging existing host-to-host-capable middlewares. Some more info about this is available in the <a href="https://github.com/ekxide/rmw_iceoryx2/tree/main?tab=readme-ov-file#is-rmw_iceoryx2-capable-of-host-to-host-communication" rel="noopener nofollow ugc"><code>README</code></a>.</p> +<h2><a class="anchor" href="https://discourse.ros.org#p-88374-performance-2" name="p-88374-performance-2"></a>Performance</h2> +<p>The current <a href="https://gitlab.com/ApexAI/performance_test/-/tree/master" rel="noopener nofollow ugc"><code>performance_test</code></a> results are as follow. There is still quite a bit of room for improvement compared to <a href="https://github.com/eclipse-iceoryx/iceoryx2?tab=readme-ov-file#performance" rel="noopener nofollow ugc">raw <code>iceoryx2</code></a>:</p> +<p></p><div class="lightbox-wrapper"><a class="lightbox" href="https://global.discourse-cdn.com/flex022/uploads/ros/original/3X/7/5/75f0f5a88ce7d73d7e9f0d4238112255176df783.png" rel="noopener nofollow ugc" title="v0.1.0"><img alt="v0.1.0" height="500" src="https://global.discourse-cdn.com/flex022/uploads/ros/optimized/3X/7/5/75f0f5a88ce7d73d7e9f0d4238112255176df783_2_652x500.png" width="652" /></a></div><p></p> +<h2><a class="anchor" href="https://discourse.ros.org#p-88374-contributing-and-feedback-3" name="p-88374-contributing-and-feedback-3"></a>Contributing and Feedback</h2> +<p>We look forward to your feedback! Input from real-world application configurations will be invaluable for bringing <code>rmw_iceoryx2</code> to stability. Additionally, insights from those experienced with RMW implementations would greatly help improve quality. The current state was achieved using only the information available in the RMW documentation, thus there may be some edge-cases known to veterans which are not properly addressed.</p> +<p>For those who have the capacity to get involved with implementation, we welcome all contributions! We will provide as much support as needed to those who are interested.</p> +<p>Thanks for reading!<br /> +Cheers</p> + <p><small>1 post - 1 participant</small></p> + <p><a href="https://discourse.ros.org/t/rmw-iceoryx2-v0-1-0-release/40996">Read full topic</a></p> + 2024-12-06T20:29:44+00:00 + orecham + + + ROS Discourse General: New Packages for Noetic 2024-12-06 + https://discourse.ros.org/t/new-packages-for-noetic-2024-12-06/40995 + <p>We’re happy to announce <strong>2</strong> new packages and <strong>46</strong> updates are now available in ROS Noetic. This sync was tagged as <a href="https://github.com/ros/rosdistro/blob/noetic/2024-12-06/noetic/distribution.yaml" rel="noopener nofollow ugc"><code>noetic/2024-12-06</code></a>.</p> +<p>Thank you to every maintainer and contributor who made these updates available!</p> +<h2><a class="anchor" href="https://discourse.ros.org#p-88370-package-updates-for-ros-noetic-1" name="p-88370-package-updates-for-ros-noetic-1"></a>Package Updates for ROS Noetic</h2> +<h3><a class="anchor" href="https://discourse.ros.org#p-88370-added-packages-2-2" name="p-88370-added-packages-2-2"></a>Added Packages [2]:</h3> +<ul> +<li><a href="https://github.com/peci1/gazebo_noisy_depth_camera" rel="noopener nofollow ugc">ros-noetic-gazebo-noisy-depth-camera</a>: 1.0.1-1</li> +<li>ros-noetic-hatchbed-common: 0.0.2-1</li> +</ul> +<h3><a class="anchor" href="https://discourse.ros.org#p-88370-updated-packages-46-3" name="p-88370-updated-packages-46-3"></a>Updated Packages [46]:</h3> +<ul> +<li><a href="https://wiki.ros.org/ess_imu_driver">ros-noetic-ess-imu-driver</a>: 2.0.1-1 → 2.0.2-1</li> +<li>ros-noetic-etsi-its-cam-coding: 2.3.0-1 → 2.4.0-1</li> +<li>ros-noetic-etsi-its-cam-conversion: 2.3.0-1 → 2.4.0-1</li> +<li>ros-noetic-etsi-its-cam-msgs: 2.3.0-1 → 2.4.0-1</li> +<li>ros-noetic-etsi-its-cam-ts-coding: 2.3.0-1 → 2.4.0-1</li> +<li>ros-noetic-etsi-its-cam-ts-conversion: 2.3.0-1 → 2.4.0-1</li> +<li>ros-noetic-etsi-its-cam-ts-msgs: 2.3.0-1 → 2.4.0-1</li> +<li>ros-noetic-etsi-its-coding: 2.3.0-1 → 2.4.0-1</li> +<li>ros-noetic-etsi-its-conversion: 2.3.0-1 → 2.4.0-1</li> +<li>ros-noetic-etsi-its-cpm-ts-coding: 2.3.0-1 → 2.4.0-1</li> +<li>ros-noetic-etsi-its-cpm-ts-conversion: 2.3.0-1 → 2.4.0-1</li> +<li>ros-noetic-etsi-its-cpm-ts-msgs: 2.3.0-1 → 2.4.0-1</li> +<li>ros-noetic-etsi-its-denm-coding: 2.3.0-1 → 2.4.0-1</li> +<li>ros-noetic-etsi-its-denm-conversion: 2.3.0-1 → 2.4.0-1</li> +<li>ros-noetic-etsi-its-denm-msgs: 2.3.0-1 → 2.4.0-1</li> +<li>ros-noetic-etsi-its-messages: 2.3.0-1 → 2.4.0-1</li> +<li>ros-noetic-etsi-its-msgs: 2.3.0-1 → 2.4.0-1</li> +<li>ros-noetic-etsi-its-msgs-utils: 2.3.0-1 → 2.4.0-1</li> +<li>ros-noetic-etsi-its-primitives-conversion: 2.3.0-1 → 2.4.0-1</li> +<li>ros-noetic-etsi-its-rviz-plugins: 2.3.0-1 → 2.4.0-1</li> +<li>ros-noetic-etsi-its-vam-ts-coding: 2.3.0-1 → 2.4.0-1</li> +<li>ros-noetic-etsi-its-vam-ts-conversion: 2.3.0-1 → 2.4.0-1</li> +<li>ros-noetic-etsi-its-vam-ts-msgs: 2.3.0-1 → 2.4.0-1</li> +<li><a href="https://github.com/foxglove/ros-foxglove-bridge" rel="noopener nofollow ugc">ros-noetic-foxglove-bridge</a>: 0.7.10-1 → 0.8.1-1</li> +<li>ros-noetic-inorbit-republisher: 0.3.0-1 → 0.3.2-1</li> +<li><a href="http://ros.org/wiki/nodelet">ros-noetic-nodelet</a>: 1.11.0-2 → 1.11.1-1</li> +<li><a href="http://www.ros.org/wiki/nodelet_core">ros-noetic-nodelet-core</a>: 1.11.0-2 → 1.11.1-1</li> +<li><a href="http://ros.org/wiki/nodelet_topic_tools">ros-noetic-nodelet-topic-tools</a>: 1.11.0-2 → 1.11.1-1</li> +<li>ros-noetic-rc-reason-clients: 0.3.1-1 → 0.4.0-2</li> +<li>ros-noetic-rc-reason-msgs: 0.3.1-1 → 0.4.0-2</li> +<li><a href="http://introlab.github.io/rtabmap" rel="noopener nofollow ugc">ros-noetic-rtabmap</a>: 0.21.6-1 → 0.21.9-1</li> +<li>ros-noetic-rtabmap-conversions: 0.21.5-1 → 0.21.9-1</li> +<li>ros-noetic-rtabmap-costmap-plugins: 0.21.5-1 → 0.21.9-1</li> +<li>ros-noetic-rtabmap-demos: 0.21.5-1 → 0.21.9-1</li> +<li>ros-noetic-rtabmap-examples: 0.21.5-1 → 0.21.9-1</li> +<li>ros-noetic-rtabmap-launch: 0.21.5-1 → 0.21.9-1</li> +<li>ros-noetic-rtabmap-legacy: 0.21.5-1 → 0.21.9-1</li> +<li>ros-noetic-rtabmap-msgs: 0.21.5-1 → 0.21.9-1</li> +<li>ros-noetic-rtabmap-odom: 0.21.5-1 → 0.21.9-1</li> +<li>ros-noetic-rtabmap-python: 0.21.5-1 → 0.21.9-1</li> +<li>ros-noetic-rtabmap-ros: 0.21.5-1 → 0.21.9-1</li> +<li>ros-noetic-rtabmap-rviz-plugins: 0.21.5-1 → 0.21.9-1</li> +<li>ros-noetic-rtabmap-slam: 0.21.5-1 → 0.21.9-1</li> +<li>ros-noetic-rtabmap-sync: 0.21.5-1 → 0.21.9-1</li> +<li>ros-noetic-rtabmap-util: 0.21.5-1 → 0.21.9-1</li> +<li>ros-noetic-rtabmap-viz: 0.21.5-1 → 0.21.9-1</li> +</ul> +<h3><a class="anchor" href="https://discourse.ros.org#p-88370-removed-packages-0-4" name="p-88370-removed-packages-0-4"></a>Removed Packages [0]:</h3> +<p>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:</p> +<ul> +<li>Felix Ruess</li> +<li>Geoffrey Biggs</li> +<li>Hans-Joachim Krauch</li> +<li>InOrbit</li> +<li>Jean-Pierre Busch</li> +<li>Marc Alban</li> +<li>Martin Pecka</li> +<li>Mathieu Labbe</li> +<li>Raymond Chow</li> +</ul> + <p><small>2 posts - 2 participants</small></p> + <p><a href="https://discourse.ros.org/t/new-packages-for-noetic-2024-12-06/40995">Read full topic</a></p> + 2024-12-06T18:09:43+00:00 + sloretz + + + ROS Discourse General: Open-RMF PMC Timing Change for 2024-12-17 + https://discourse.ros.org/t/open-rmf-pmc-timing-change-for-2024-12-17/40986 + <p>Due to a one-time scheduling conflict, the Open-RMF Project Management Committee session that is normally scheduled for <span class="discourse-local-date">2024-12-17T01:00:00Z UTC</span> will instead take place one hour later at <span class="discourse-local-date">2024-12-17T02:00:00Z UTC</span>. This change is reflected in the official OSRF events calendar.</p> +<p>Sessions will return to the normal time afterwards.</p> + <p><small>1 post - 1 participant</small></p> + <p><a href="https://discourse.ros.org/t/open-rmf-pmc-timing-change-for-2024-12-17/40986">Read full topic</a></p> + 2024-12-06T08:46:33+00:00 + grey + + + ROS Discourse General: New packages and patch release for Humble Hawksbill 2024-12-05 + https://discourse.ros.org/t/new-packages-and-patch-release-for-humble-hawksbill-2024-12-05/40976 + <p>We’re happy to announce a <a href="https://github.com/ros2/ros2/releases/tag/release-humble-20241205" rel="noopener nofollow ugc">new Humble release</a>!</p> +<p>This sync brings several new packages and some updates to ROS 2 core packages. (I haven’t included the project board for patch info because there was nothing on it.)</p> +<h2><a class="anchor" href="https://discourse.ros.org#p-88326-package-updates-for-humble-1" name="p-88326-package-updates-for-humble-1"></a>Package Updates for Humble</h2> +<h3><a class="anchor" href="https://discourse.ros.org#p-88326-added-packages-34-2" name="p-88326-added-packages-34-2"></a>Added Packages [34]:</h3> +<ul> +<li>ros-humble-adi-3dtof-image-stitching: 2.1.0-1</li> +<li>ros-humble-adi-3dtof-image-stitching-dbgsym: 2.1.0-1</li> +<li><a href="http://ros.org/wiki/axis_camera">ros-humble-axis-camera</a>: 2.0.3-1</li> +<li>ros-humble-axis-description: 2.0.3-1</li> +<li><a href="http://ros.org/wiki/axis_camera">ros-humble-axis-msgs</a>: 2.0.3-1</li> +<li>ros-humble-axis-msgs-dbgsym: 2.0.3-1</li> +<li><a href="http://ros.org/wiki/camera_info_manager_py">ros-humble-camera-info-manager-py</a>: 3.1.10-1</li> +<li>ros-humble-clearpath-motor-msgs: 1.0.1-1</li> +<li>ros-humble-clearpath-motor-msgs-dbgsym: 1.0.1-1</li> +<li>ros-humble-clearpath-ros2-socketcan-interface: 1.0.0-1</li> +<li>ros-humble-clearpath-ros2-socketcan-interface-dbgsym: 1.0.0-1</li> +<li>ros-humble-dual-laser-merger: 0.1.1-1</li> +<li>ros-humble-dual-laser-merger-dbgsym: 0.1.1-1</li> +<li>ros-humble-hatchbed-common: 0.1.1-1</li> +<li>ros-humble-hri-face-body-matcher: 2.1.0-1</li> +<li>ros-humble-hri-face-body-matcher-dbgsym: 2.1.0-1</li> +<li>ros-humble-hri-privacy-msgs: 1.2.0-1</li> +<li>ros-humble-hri-privacy-msgs-dbgsym: 1.2.0-1</li> +<li><a href="https://github.com/JafarAbdi/jacro" rel="noopener nofollow ugc">ros-humble-jacro</a>: 0.2.0-1</li> +<li>ros-humble-laser-segmentation: 3.0.2-1</li> +<li>ros-humble-laser-segmentation-dbgsym: 3.0.2-1</li> +<li>ros-humble-log-view: 0.2.5-1</li> +<li>ros-humble-log-view-dbgsym: 0.2.5-1</li> +<li>ros-humble-pose-broadcaster: 2.38.0-1</li> +<li>ros-humble-pose-broadcaster-dbgsym: 2.38.0-1</li> +<li>ros-humble-ptz-action-server-msgs: 2.0.3-1</li> +<li>ros-humble-ptz-action-server-msgs-dbgsym: 2.0.3-1</li> +<li>ros-humble-rosbag2-to-video: 1.0.1-1</li> +<li><a href="http://ros.org/wiki/simple_grasping">ros-humble-simple-grasping</a>: 0.5.0-1</li> +<li>ros-humble-simple-grasping-dbgsym: 0.5.0-1</li> +<li>ros-humble-slg-msgs: 3.9.1-1</li> +<li>ros-humble-slg-msgs-dbgsym: 3.9.1-1</li> +<li><a href="https://www.stereolabs.com/" rel="noopener nofollow ugc">ros-humble-zed-msgs</a>: 4.2.2-1</li> +<li>ros-humble-zed-msgs-dbgsym: 4.2.2-1</li> +</ul> +<h3><a class="anchor" href="https://discourse.ros.org#p-88326-updated-packages-580-3" name="p-88326-updated-packages-580-3"></a>Updated Packages [580]:</h3> +<ul> +<li>ros-humble-ackermann-steering-controller: 2.37.3-1 → 2.38.0-1</li> +<li>ros-humble-ackermann-steering-controller-dbgsym: 2.37.3-1 → 2.38.0-1</li> +<li>ros-humble-adi-tmcl: 2.0.0-1 → 2.0.3-2</li> +<li>ros-humble-adi-tmcl-dbgsym: 2.0.0-1 → 2.0.3-2</li> +<li>ros-humble-admittance-controller: 2.37.3-1 → 2.38.0-1</li> +<li>ros-humble-admittance-controller-dbgsym: 2.37.3-1 → 2.38.0-1</li> +<li>ros-humble-ament-cmake: 1.3.10-1 → 1.3.11-1</li> +<li>ros-humble-ament-cmake-auto: 1.3.10-1 → 1.3.11-1</li> +<li>ros-humble-ament-cmake-core: 1.3.10-1 → 1.3.11-1</li> +<li>ros-humble-ament-cmake-export-definitions: 1.3.10-1 → 1.3.11-1</li> +<li>ros-humble-ament-cmake-export-dependencies: 1.3.10-1 → 1.3.11-1</li> +<li>ros-humble-ament-cmake-export-include-directories: 1.3.10-1 → 1.3.11-1</li> +<li>ros-humble-ament-cmake-export-interfaces: 1.3.10-1 → 1.3.11-1</li> +<li>ros-humble-ament-cmake-export-libraries: 1.3.10-1 → 1.3.11-1</li> +<li>ros-humble-ament-cmake-export-link-flags: 1.3.10-1 → 1.3.11-1</li> +<li>ros-humble-ament-cmake-export-targets: 1.3.10-1 → 1.3.11-1</li> +<li>ros-humble-ament-cmake-gen-version-h: 1.3.10-1 → 1.3.11-1</li> +<li>ros-humble-ament-cmake-gmock: 1.3.10-1 → 1.3.11-1</li> +<li>ros-humble-ament-cmake-google-benchmark: 1.3.10-1 → 1.3.11-1</li> +<li>ros-humble-ament-cmake-gtest: 1.3.10-1 → 1.3.11-1</li> +<li>ros-humble-ament-cmake-include-directories: 1.3.10-1 → 1.3.11-1</li> +<li>ros-humble-ament-cmake-libraries: 1.3.10-1 → 1.3.11-1</li> +<li>ros-humble-ament-cmake-nose: 1.3.10-1 → 1.3.11-1</li> +<li>ros-humble-ament-cmake-pytest: 1.3.10-1 → 1.3.11-1</li> +<li>ros-humble-ament-cmake-python: 1.3.10-1 → 1.3.11-1</li> +<li>ros-humble-ament-cmake-target-dependencies: 1.3.10-1 → 1.3.11-1</li> +<li>ros-humble-ament-cmake-test: 1.3.10-1 → 1.3.11-1</li> +<li>ros-humble-ament-cmake-vendor-package: 1.3.10-1 → 1.3.11-1</li> +<li>ros-humble-ament-cmake-version: 1.3.10-1 → 1.3.11-1</li> +<li>ros-humble-autoware-lanelet2-extension: 0.6.0-1 → 0.6.2-1</li> +<li>ros-humble-autoware-lanelet2-extension-dbgsym: 0.6.0-1 → 0.6.2-1</li> +<li>ros-humble-autoware-lanelet2-extension-python: 0.6.0-1 → 0.6.2-1</li> +<li>ros-humble-autoware-lanelet2-extension-python-dbgsym: 0.6.0-1 → 0.6.2-1</li> +<li><a href="https://github.com/pal-robotics/backward_ros" rel="noopener nofollow ugc">ros-humble-backward-ros</a>: 1.0.5-1 → 1.0.6-1</li> +<li>ros-humble-backward-ros-dbgsym: 1.0.5-1 → 1.0.6-1</li> +<li>ros-humble-bicycle-steering-controller: 2.37.3-1 → 2.38.0-1</li> +<li>ros-humble-bicycle-steering-controller-dbgsym: 2.37.3-1 → 2.38.0-1</li> +<li>ros-humble-bosch-locator-bridge: 2.1.11-1 → 2.1.13-1</li> +<li>ros-humble-bosch-locator-bridge-dbgsym: 2.1.11-1 → 2.1.13-1</li> +<li>ros-humble-bosch-locator-bridge-utils: 2.1.11-1 → 2.1.13-1</li> +<li>ros-humble-bosch-locator-bridge-utils-dbgsym: 2.1.11-1 → 2.1.13-1</li> +<li><a href="http://ros.org/wiki/camera_calibration_parsers">ros-humble-camera-calibration-parsers</a>: 3.1.9-1 → 3.1.10-1</li> +<li>ros-humble-camera-calibration-parsers-dbgsym: 3.1.9-1 → 3.1.10-1</li> +<li><a href="http://ros.org/wiki/camera_info_manager">ros-humble-camera-info-manager</a>: 3.1.9-1 → 3.1.10-1</li> +<li>ros-humble-camera-info-manager-dbgsym: 3.1.9-1 → 3.1.10-1</li> +<li>ros-humble-camera-ros: 0.1.0-2 → 0.2.0-1</li> +<li>ros-humble-camera-ros-dbgsym: 0.1.0-2 → 0.2.0-1</li> +<li><a href="http://ros.org/wiki/chomp_motion_planner">ros-humble-chomp-motion-planner</a>: 2.5.5-1 → 2.5.6-1</li> +<li>ros-humble-chomp-motion-planner-dbgsym: 2.5.5-1 → 2.5.6-1</li> +<li>ros-humble-clearpath-common: 0.3.4-1 → 1.0.0-1</li> +<li>ros-humble-clearpath-config: 0.3.4-1 → 1.0.0-1</li> +<li>ros-humble-clearpath-config-live: 0.3.0-1 → 1.0.0-1</li> +<li>ros-humble-clearpath-control: 0.3.4-1 → 1.0.0-1</li> +<li>ros-humble-clearpath-customization: 0.3.4-1 → 1.0.0-1</li> +<li>ros-humble-clearpath-description: 0.3.4-1 → 1.0.0-1</li> +<li>ros-humble-clearpath-desktop: 0.3.0-1 → 1.0.0-1</li> +<li>ros-humble-clearpath-generator-common: 0.3.4-1 → 1.0.0-1</li> +<li>ros-humble-clearpath-generator-common-dbgsym: 0.3.4-1 → 1.0.0-1</li> +<li>ros-humble-clearpath-generator-gz: 0.3.0-1 → 1.0.0-1</li> +<li>ros-humble-clearpath-gz: 0.3.0-1 → 1.0.0-1</li> +<li>ros-humble-clearpath-manipulators: 0.3.4-1 → 1.0.0-1</li> +<li>ros-humble-clearpath-manipulators-description: 0.3.4-1 → 1.0.0-1</li> +<li>ros-humble-clearpath-mounts-description: 0.3.4-1 → 1.0.0-1</li> +<li>ros-humble-clearpath-msgs: 1.0.0-1 → 1.0.1-1</li> +<li>ros-humble-clearpath-nav2-demos: 0.2.0-1 → 1.0.0-1</li> +<li>ros-humble-clearpath-platform-description: 0.3.4-1 → 1.0.0-1</li> +<li>ros-humble-clearpath-platform-msgs: 1.0.0-1 → 1.0.1-1</li> +<li>ros-humble-clearpath-platform-msgs-dbgsym: 1.0.0-1 → 1.0.1-1</li> +<li>ros-humble-clearpath-sensors-description: 0.3.4-1 → 1.0.0-1</li> +<li>ros-humble-clearpath-simulator: 0.3.0-1 → 1.0.0-1</li> +<li>ros-humble-clearpath-viz: 0.3.0-1 → 1.0.0-1</li> +<li><a href="https://control.ros.org">ros-humble-control-msgs</a>: 4.6.0-1 → 4.7.0-1</li> +<li>ros-humble-control-msgs-dbgsym: 4.6.0-1 → 4.7.0-1</li> +<li>ros-humble-controller-interface: 2.43.1-1 → 2.44.0-1</li> +<li>ros-humble-controller-interface-dbgsym: 2.43.1-1 → 2.44.0-1</li> +<li>ros-humble-controller-manager: 2.43.1-1 → 2.44.0-1</li> +<li>ros-humble-controller-manager-dbgsym: 2.43.1-1 → 2.44.0-1</li> +<li><a href="http://ros.org/wiki/controller_manager_msgs">ros-humble-controller-manager-msgs</a>: 2.43.1-1 → 2.44.0-1</li> +<li>ros-humble-controller-manager-msgs-dbgsym: 2.43.1-1 → 2.44.0-1</li> +<li>ros-humble-costmap-queue: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-costmap-queue-dbgsym: 1.1.16-1 → 1.1.17-1</li> +<li><a href="https://projects.eclipse.org/projects/iot.cyclonedds" rel="noopener nofollow ugc">ros-humble-cyclonedds</a>: 0.10.4-1 → 0.10.5-2</li> +<li>ros-humble-cyclonedds-dbgsym: 0.10.4-1 → 0.10.5-2</li> +<li>ros-humble-depthai-bridge: 2.10.3-1 → 2.10.4-1</li> +<li>ros-humble-depthai-bridge-dbgsym: 2.10.3-1 → 2.10.4-1</li> +<li>ros-humble-depthai-descriptions: 2.10.3-1 → 2.10.4-1</li> +<li>ros-humble-depthai-examples: 2.10.3-1 → 2.10.4-1</li> +<li>ros-humble-depthai-examples-dbgsym: 2.10.3-1 → 2.10.4-1</li> +<li>ros-humble-depthai-filters: 2.10.3-1 → 2.10.4-1</li> +<li>ros-humble-depthai-filters-dbgsym: 2.10.3-1 → 2.10.4-1</li> +<li>ros-humble-depthai-ros: 2.10.3-1 → 2.10.4-1</li> +<li>ros-humble-depthai-ros-driver: 2.10.3-1 → 2.10.4-1</li> +<li>ros-humble-depthai-ros-driver-dbgsym: 2.10.3-1 → 2.10.4-1</li> +<li>ros-humble-depthai-ros-msgs: 2.10.3-1 → 2.10.4-1</li> +<li>ros-humble-depthai-ros-msgs-dbgsym: 2.10.3-1 → 2.10.4-1</li> +<li>ros-humble-diff-drive-controller: 2.37.3-1 → 2.38.0-1</li> +<li>ros-humble-diff-drive-controller-dbgsym: 2.37.3-1 → 2.38.0-1</li> +<li>ros-humble-dwb-core: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-dwb-core-dbgsym: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-dwb-critics: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-dwb-critics-dbgsym: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-dwb-msgs: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-dwb-msgs-dbgsym: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-dwb-plugins: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-dwb-plugins-dbgsym: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-effort-controllers: 2.37.3-1 → 2.38.0-1</li> +<li>ros-humble-effort-controllers-dbgsym: 2.37.3-1 → 2.38.0-1</li> +<li>ros-humble-etsi-its-cam-coding: 2.3.0-1 → 2.4.0-1</li> +<li>ros-humble-etsi-its-cam-coding-dbgsym: 2.3.0-1 → 2.4.0-1</li> +<li>ros-humble-etsi-its-cam-conversion: 2.3.0-1 → 2.4.0-1</li> +<li>ros-humble-etsi-its-cam-msgs: 2.3.0-1 → 2.4.0-1</li> +<li>ros-humble-etsi-its-cam-msgs-dbgsym: 2.3.0-1 → 2.4.0-1</li> +<li>ros-humble-etsi-its-cam-ts-coding: 2.3.0-1 → 2.4.0-1</li> +<li>ros-humble-etsi-its-cam-ts-coding-dbgsym: 2.3.0-1 → 2.4.0-1</li> +<li>ros-humble-etsi-its-cam-ts-conversion: 2.3.0-1 → 2.4.0-1</li> +<li>ros-humble-etsi-its-cam-ts-msgs: 2.3.0-1 → 2.4.0-1</li> +<li>ros-humble-etsi-its-cam-ts-msgs-dbgsym: 2.3.0-1 → 2.4.0-1</li> +<li>ros-humble-etsi-its-coding: 2.3.0-1 → 2.4.0-1</li> +<li>ros-humble-etsi-its-conversion: 2.3.0-1 → 2.4.0-1</li> +<li>ros-humble-etsi-its-conversion-dbgsym: 2.3.0-1 → 2.4.0-1</li> +<li>ros-humble-etsi-its-cpm-ts-coding: 2.3.0-1 → 2.4.0-1</li> +<li>ros-humble-etsi-its-cpm-ts-coding-dbgsym: 2.3.0-1 → 2.4.0-1</li> +<li>ros-humble-etsi-its-cpm-ts-conversion: 2.3.0-1 → 2.4.0-1</li> +<li>ros-humble-etsi-its-cpm-ts-msgs: 2.3.0-1 → 2.4.0-1</li> +<li>ros-humble-etsi-its-cpm-ts-msgs-dbgsym: 2.3.0-1 → 2.4.0-1</li> +<li>ros-humble-etsi-its-denm-coding: 2.3.0-1 → 2.4.0-1</li> +<li>ros-humble-etsi-its-denm-coding-dbgsym: 2.3.0-1 → 2.4.0-1</li> +<li>ros-humble-etsi-its-denm-conversion: 2.3.0-1 → 2.4.0-1</li> +<li>ros-humble-etsi-its-denm-msgs: 2.3.0-1 → 2.4.0-1</li> +<li>ros-humble-etsi-its-denm-msgs-dbgsym: 2.3.0-1 → 2.4.0-1</li> +<li>ros-humble-etsi-its-messages: 2.3.0-1 → 2.4.0-1</li> +<li>ros-humble-etsi-its-msgs: 2.3.0-1 → 2.4.0-1</li> +<li>ros-humble-etsi-its-msgs-utils: 2.3.0-1 → 2.4.0-1</li> +<li>ros-humble-etsi-its-primitives-conversion: 2.3.0-1 → 2.4.0-1</li> +<li>ros-humble-etsi-its-rviz-plugins: 2.3.0-1 → 2.4.0-1</li> +<li>ros-humble-etsi-its-rviz-plugins-dbgsym: 2.3.0-1 → 2.4.0-1</li> +<li>ros-humble-etsi-its-vam-ts-coding: 2.3.0-1 → 2.4.0-1</li> +<li>ros-humble-etsi-its-vam-ts-coding-dbgsym: 2.3.0-1 → 2.4.0-1</li> +<li>ros-humble-etsi-its-vam-ts-conversion: 2.3.0-1 → 2.4.0-1</li> +<li>ros-humble-etsi-its-vam-ts-msgs: 2.3.0-1 → 2.4.0-1</li> +<li>ros-humble-etsi-its-vam-ts-msgs-dbgsym: 2.3.0-1 → 2.4.0-1</li> +<li>ros-humble-examples-rclcpp-async-client: 0.15.2-1 → 0.15.3-1</li> +<li>ros-humble-examples-rclcpp-async-client-dbgsym: 0.15.2-1 → 0.15.3-1</li> +<li>ros-humble-examples-rclcpp-cbg-executor: 0.15.2-1 → 0.15.3-1</li> +<li>ros-humble-examples-rclcpp-cbg-executor-dbgsym: 0.15.2-1 → 0.15.3-1</li> +<li>ros-humble-examples-rclcpp-minimal-action-client: 0.15.2-1 → 0.15.3-1</li> +<li>ros-humble-examples-rclcpp-minimal-action-client-dbgsym: 0.15.2-1 → 0.15.3-1</li> +<li>ros-humble-examples-rclcpp-minimal-action-server: 0.15.2-1 → 0.15.3-1</li> +<li>ros-humble-examples-rclcpp-minimal-action-server-dbgsym: 0.15.2-1 → 0.15.3-1</li> +<li>ros-humble-examples-rclcpp-minimal-client: 0.15.2-1 → 0.15.3-1</li> +<li>ros-humble-examples-rclcpp-minimal-client-dbgsym: 0.15.2-1 → 0.15.3-1</li> +<li>ros-humble-examples-rclcpp-minimal-composition: 0.15.2-1 → 0.15.3-1</li> +<li>ros-humble-examples-rclcpp-minimal-composition-dbgsym: 0.15.2-1 → 0.15.3-1</li> +<li>ros-humble-examples-rclcpp-minimal-publisher: 0.15.2-1 → 0.15.3-1</li> +<li>ros-humble-examples-rclcpp-minimal-publisher-dbgsym: 0.15.2-1 → 0.15.3-1</li> +<li>ros-humble-examples-rclcpp-minimal-service: 0.15.2-1 → 0.15.3-1</li> +<li>ros-humble-examples-rclcpp-minimal-service-dbgsym: 0.15.2-1 → 0.15.3-1</li> +<li>ros-humble-examples-rclcpp-minimal-subscriber: 0.15.2-1 → 0.15.3-1</li> +<li>ros-humble-examples-rclcpp-minimal-subscriber-dbgsym: 0.15.2-1 → 0.15.3-1</li> +<li>ros-humble-examples-rclcpp-minimal-timer: 0.15.2-1 → 0.15.3-1</li> +<li>ros-humble-examples-rclcpp-minimal-timer-dbgsym: 0.15.2-1 → 0.15.3-1</li> +<li>ros-humble-examples-rclcpp-multithreaded-executor: 0.15.2-1 → 0.15.3-1</li> +<li>ros-humble-examples-rclcpp-multithreaded-executor-dbgsym: 0.15.2-1 → 0.15.3-1</li> +<li>ros-humble-examples-rclcpp-wait-set: 0.15.2-1 → 0.15.3-1</li> +<li>ros-humble-examples-rclcpp-wait-set-dbgsym: 0.15.2-1 → 0.15.3-1</li> +<li>ros-humble-examples-rclpy-executors: 0.15.2-1 → 0.15.3-1</li> +<li>ros-humble-examples-rclpy-guard-conditions: 0.15.2-1 → 0.15.3-1</li> +<li>ros-humble-examples-rclpy-minimal-action-client: 0.15.2-1 → 0.15.3-1</li> +<li>ros-humble-examples-rclpy-minimal-action-server: 0.15.2-1 → 0.15.3-1</li> +<li>ros-humble-examples-rclpy-minimal-client: 0.15.2-1 → 0.15.3-1</li> +<li>ros-humble-examples-rclpy-minimal-publisher: 0.15.2-1 → 0.15.3-1</li> +<li>ros-humble-examples-rclpy-minimal-service: 0.15.2-1 → 0.15.3-1</li> +<li>ros-humble-examples-rclpy-minimal-subscriber: 0.15.2-1 → 0.15.3-1</li> +<li>ros-humble-examples-rclpy-pointcloud-publisher: 0.15.2-1 → 0.15.3-1</li> +<li>ros-humble-examples-tf2-py: 0.25.8-1 → 0.25.9-1</li> +<li><a href="https://www.eprosima.com/" rel="noopener nofollow ugc">ros-humble-fastrtps</a>: 2.6.8-1 → 2.6.9-1</li> +<li>ros-humble-fastrtps-dbgsym: 2.6.8-1 → 2.6.9-1</li> +<li>ros-humble-flir-camera-description: 2.1.17-1 → 3.0.0-1</li> +<li>ros-humble-flir-camera-msgs: 2.1.17-1 → 3.0.0-1</li> +<li>ros-humble-flir-camera-msgs-dbgsym: 2.1.17-1 → 3.0.0-1</li> +<li>ros-humble-force-torque-sensor-broadcaster: 2.37.3-1 → 2.38.0-1</li> +<li>ros-humble-force-torque-sensor-broadcaster-dbgsym: 2.37.3-1 → 2.38.0-1</li> +<li>ros-humble-forward-command-controller: 2.37.3-1 → 2.38.0-1</li> +<li>ros-humble-forward-command-controller-dbgsym: 2.37.3-1 → 2.38.0-1</li> +<li><a href="https://github.com/foxglove/ros-foxglove-bridge" rel="noopener nofollow ugc">ros-humble-foxglove-bridge</a>: 0.8.0-1 → 0.8.1-1</li> +<li>ros-humble-foxglove-bridge-dbgsym: 0.8.0-1 → 0.8.1-1</li> +<li><a href="http://www.ros.org/wiki/image_transport_plugins">ros-humble-foxglove-compressed-video-transport</a>: 1.0.0-1 → 1.0.1-1</li> +<li>ros-humble-foxglove-compressed-video-transport-dbgsym: 1.0.0-1 → 1.0.1-1</li> +<li><a href="http://www.ros.org/wiki/geometry2">ros-humble-geometry2</a>: 0.25.8-1 → 0.25.9-1</li> +<li>ros-humble-gripper-controllers: 2.37.3-1 → 2.38.0-1</li> +<li>ros-humble-gripper-controllers-dbgsym: 2.37.3-1 → 2.38.0-1</li> +<li>ros-humble-hardware-interface: 2.43.1-1 → 2.44.0-1</li> +<li>ros-humble-hardware-interface-dbgsym: 2.43.1-1 → 2.44.0-1</li> +<li>ros-humble-hardware-interface-testing: 2.43.1-1 → 2.44.0-1</li> +<li>ros-humble-hardware-interface-testing-dbgsym: 2.43.1-1 → 2.44.0-1</li> +<li><a href="http://www.ros.org/wiki/image_common">ros-humble-image-common</a>: 3.1.9-1 → 3.1.10-1</li> +<li><a href="http://ros.org/wiki/image_transport">ros-humble-image-transport</a>: 3.1.9-1 → 3.1.10-1</li> +<li>ros-humble-image-transport-dbgsym: 3.1.9-1 → 3.1.10-1</li> +<li>ros-humble-imu-sensor-broadcaster: 2.37.3-1 → 2.38.0-1</li> +<li>ros-humble-imu-sensor-broadcaster-dbgsym: 2.37.3-1 → 2.38.0-1</li> +<li>ros-humble-interactive-marker-twist-server: 2.1.0-2 → 2.1.1-1</li> +<li>ros-humble-interactive-marker-twist-server-dbgsym: 2.1.0-2 → 2.1.1-1</li> +<li><a href="https://github.com/ros-controls/ros2_control/wiki" rel="noopener nofollow ugc">ros-humble-joint-limits</a>: 2.43.1-1 → 2.44.0-1</li> +<li>ros-humble-joint-limits-dbgsym: 2.43.1-1 → 2.44.0-1</li> +<li>ros-humble-joint-state-broadcaster: 2.37.3-1 → 2.38.0-1</li> +<li>ros-humble-joint-state-broadcaster-dbgsym: 2.37.3-1 → 2.38.0-1</li> +<li>ros-humble-joint-trajectory-controller: 2.37.3-1 → 2.38.0-1</li> +<li>ros-humble-joint-trajectory-controller-dbgsym: 2.37.3-1 → 2.38.0-1</li> +<li>ros-humble-joy-teleop: 1.6.0-1 → 1.7.0-1</li> +<li>ros-humble-key-teleop: 1.6.0-1 → 1.7.0-1</li> +<li>ros-humble-launch: 1.0.6-1 → 1.0.7-1</li> +<li>ros-humble-launch-pytest: 1.0.6-1 → 1.0.7-1</li> +<li>ros-humble-launch-ros: 0.19.7-2 → 0.19.8-1</li> +<li>ros-humble-launch-testing: 1.0.6-1 → 1.0.7-1</li> +<li>ros-humble-launch-testing-ament-cmake: 1.0.6-1 → 1.0.7-1</li> +<li>ros-humble-launch-testing-examples: 0.15.2-1 → 0.15.3-1</li> +<li>ros-humble-launch-testing-ros: 0.19.7-2 → 0.19.8-1</li> +<li>ros-humble-launch-xml: 1.0.6-1 → 1.0.7-1</li> +<li>ros-humble-launch-yaml: 1.0.6-1 → 1.0.7-1</li> +<li><a href="http://wiki.ros.org/leo">ros-humble-leo</a>: 1.2.3-1 → 1.2.4-1</li> +<li><a href="http://wiki.ros.org/leo_bringup">ros-humble-leo-bringup</a>: 1.4.0-1 → 1.5.0-1</li> +<li><a href="http://wiki.ros.org/leo_description">ros-humble-leo-description</a>: 1.2.3-1 → 1.2.4-1</li> +<li><a href="http://wiki.ros.org/leo_fw">ros-humble-leo-fw</a>: 1.4.0-1 → 1.5.0-1</li> +<li>ros-humble-leo-fw-dbgsym: 1.4.0-1 → 1.5.0-1</li> +<li>ros-humble-leo-gz-bringup: 1.1.0-1 → 1.1.1-1</li> +<li>ros-humble-leo-gz-plugins: 1.1.0-1 → 1.1.1-1</li> +<li>ros-humble-leo-gz-plugins-dbgsym: 1.1.0-1 → 1.1.1-1</li> +<li>ros-humble-leo-gz-worlds: 1.1.0-1 → 1.1.1-1</li> +<li><a href="http://wiki.ros.org/leo">ros-humble-leo-msgs</a>: 1.2.3-1 → 1.2.4-1</li> +<li>ros-humble-leo-msgs-dbgsym: 1.2.3-1 → 1.2.4-1</li> +<li><a href="http://wiki.ros.org/leo_robot">ros-humble-leo-robot</a>: 1.4.0-1 → 1.5.0-1</li> +<li>ros-humble-leo-simulator: 1.1.0-1 → 1.1.1-1</li> +<li><a href="http://wiki.ros.org/leo_teleop">ros-humble-leo-teleop</a>: 1.2.3-1 → 1.2.4-1</li> +<li>ros-humble-libstatistics-collector: 1.3.2-1 → 1.3.4-1</li> +<li>ros-humble-libstatistics-collector-dbgsym: 1.3.2-1 → 1.3.4-1</li> +<li>ros-humble-mcap-vendor: 0.15.12-1 → 0.15.13-1</li> +<li>ros-humble-mcap-vendor-dbgsym: 0.15.12-1 → 0.15.13-1</li> +<li><a href="https://github.com/LORD-MicroStrain/microstrain_inertial" rel="noopener nofollow ugc">ros-humble-microstrain-inertial-description</a>: 4.4.0-1 → 4.5.0-1</li> +<li><a href="https://github.com/LORD-MicroStrain/microstrain_inertial" rel="noopener nofollow ugc">ros-humble-microstrain-inertial-driver</a>: 4.4.0-1 → 4.5.0-1</li> +<li>ros-humble-microstrain-inertial-driver-dbgsym: 4.4.0-1 → 4.5.0-1</li> +<li><a href="https://github.com/LORD-MicroStrain/microstrain_inertial" rel="noopener nofollow ugc">ros-humble-microstrain-inertial-examples</a>: 4.4.0-1 → 4.5.0-1</li> +<li><a href="https://github.com/LORD-MicroStrain/microstrain_inertial" rel="noopener nofollow ugc">ros-humble-microstrain-inertial-msgs</a>: 4.4.0-1 → 4.5.0-1</li> +<li>ros-humble-microstrain-inertial-msgs-dbgsym: 4.4.0-1 → 4.5.0-1</li> +<li><a href="https://github.com/LORD-MicroStrain/microstrain_inertial" rel="noopener nofollow ugc">ros-humble-microstrain-inertial-rqt</a>: 4.4.0-1 → 4.5.0-1</li> +<li>ros-humble-mouse-teleop: 1.6.0-1 → 1.7.0-1</li> +<li><a href="http://moveit.ros.org">ros-humble-moveit</a>: 2.5.5-1 → 2.5.6-1</li> +<li>ros-humble-moveit-chomp-optimizer-adapter: 2.5.5-1 → 2.5.6-1</li> +<li>ros-humble-moveit-chomp-optimizer-adapter-dbgsym: 2.5.5-1 → 2.5.6-1</li> +<li><a href="http://moveit.ros.org">ros-humble-moveit-common</a>: 2.5.5-1 → 2.5.6-1</li> +<li>ros-humble-moveit-configs-utils: 2.5.5-1 → 2.5.6-1</li> +<li><a href="http://moveit.ros.org">ros-humble-moveit-core</a>: 2.5.5-1 → 2.5.6-1</li> +<li>ros-humble-moveit-core-dbgsym: 2.5.5-1 → 2.5.6-1</li> +<li><a href="http://moveit.ros.org">ros-humble-moveit-hybrid-planning</a>: 2.5.5-1 → 2.5.6-1</li> +<li>ros-humble-moveit-hybrid-planning-dbgsym: 2.5.5-1 → 2.5.6-1</li> +<li><a href="http://moveit.ros.org">ros-humble-moveit-kinematics</a>: 2.5.5-1 → 2.5.6-1</li> +<li>ros-humble-moveit-kinematics-dbgsym: 2.5.5-1 → 2.5.6-1</li> +<li><a href="http://moveit.ros.org">ros-humble-moveit-planners</a>: 2.5.5-1 → 2.5.6-1</li> +<li>ros-humble-moveit-planners-chomp: 2.5.5-1 → 2.5.6-1</li> +<li>ros-humble-moveit-planners-chomp-dbgsym: 2.5.5-1 → 2.5.6-1</li> +<li><a href="http://moveit.ros.org">ros-humble-moveit-planners-ompl</a>: 2.5.5-1 → 2.5.6-1</li> +<li>ros-humble-moveit-planners-ompl-dbgsym: 2.5.5-1 → 2.5.6-1</li> +<li><a href="http://moveit.ros.org">ros-humble-moveit-plugins</a>: 2.5.5-1 → 2.5.6-1</li> +<li><a href="http://moveit.ros.org">ros-humble-moveit-resources-prbt-ikfast-manipulator-plugin</a>: 2.5.5-1 → 2.5.6-1</li> +<li>ros-humble-moveit-resources-prbt-ikfast-manipulator-plugin-dbgsym: 2.5.5-1 → 2.5.6-1</li> +<li><a href="http://moveit.ros.org">ros-humble-moveit-resources-prbt-moveit-config</a>: 2.5.5-1 → 2.5.6-1</li> +<li><a href="http://moveit.ros.org">ros-humble-moveit-resources-prbt-pg70-support</a>: 2.5.5-1 → 2.5.6-1</li> +<li><a href="http://moveit.ros.org">ros-humble-moveit-resources-prbt-support</a>: 2.5.5-1 → 2.5.6-1</li> +<li><a href="http://moveit.ros.org">ros-humble-moveit-ros</a>: 2.5.5-1 → 2.5.6-1</li> +<li><a href="http://moveit.ros.org">ros-humble-moveit-ros-benchmarks</a>: 2.5.5-1 → 2.5.6-1</li> +<li>ros-humble-moveit-ros-benchmarks-dbgsym: 2.5.5-1 → 2.5.6-1</li> +<li>ros-humble-moveit-ros-control-interface: 2.5.5-1 → 2.5.6-1</li> +<li>ros-humble-moveit-ros-control-interface-dbgsym: 2.5.5-1 → 2.5.6-1</li> +<li><a href="http://moveit.ros.org">ros-humble-moveit-ros-move-group</a>: 2.5.5-1 → 2.5.6-1</li> +<li>ros-humble-moveit-ros-move-group-dbgsym: 2.5.5-1 → 2.5.6-1</li> +<li><a href="http://moveit.ros.org">ros-humble-moveit-ros-occupancy-map-monitor</a>: 2.5.5-1 → 2.5.6-1</li> +<li>ros-humble-moveit-ros-occupancy-map-monitor-dbgsym: 2.5.5-1 → 2.5.6-1</li> +<li><a href="http://moveit.ros.org">ros-humble-moveit-ros-perception</a>: 2.5.5-1 → 2.5.6-1</li> +<li>ros-humble-moveit-ros-perception-dbgsym: 2.5.5-1 → 2.5.6-1</li> +<li><a href="http://moveit.ros.org">ros-humble-moveit-ros-planning</a>: 2.5.5-1 → 2.5.6-1</li> +<li>ros-humble-moveit-ros-planning-dbgsym: 2.5.5-1 → 2.5.6-1</li> +<li><a href="http://moveit.ros.org">ros-humble-moveit-ros-planning-interface</a>: 2.5.5-1 → 2.5.6-1</li> +<li>ros-humble-moveit-ros-planning-interface-dbgsym: 2.5.5-1 → 2.5.6-1</li> +<li><a href="http://moveit.ros.org">ros-humble-moveit-ros-robot-interaction</a>: 2.5.5-1 → 2.5.6-1</li> +<li>ros-humble-moveit-ros-robot-interaction-dbgsym: 2.5.5-1 → 2.5.6-1</li> +<li><a href="http://moveit.ros.org">ros-humble-moveit-ros-visualization</a>: 2.5.5-1 → 2.5.6-1</li> +<li>ros-humble-moveit-ros-visualization-dbgsym: 2.5.5-1 → 2.5.6-1</li> +<li><a href="http://moveit.ros.org">ros-humble-moveit-ros-warehouse</a>: 2.5.5-1 → 2.5.6-1</li> +<li>ros-humble-moveit-ros-warehouse-dbgsym: 2.5.5-1 → 2.5.6-1</li> +<li><a href="http://moveit.ros.org">ros-humble-moveit-runtime</a>: 2.5.5-1 → 2.5.6-1</li> +<li><a href="https://ros-planning.github.io/moveit_tutorials" rel="noopener nofollow ugc">ros-humble-moveit-servo</a>: 2.5.5-1 → 2.5.6-1</li> +<li>ros-humble-moveit-servo-dbgsym: 2.5.5-1 → 2.5.6-1</li> +<li>ros-humble-moveit-setup-app-plugins: 2.5.5-1 → 2.5.6-1</li> +<li>ros-humble-moveit-setup-app-plugins-dbgsym: 2.5.5-1 → 2.5.6-1</li> +<li><a href="http://moveit.ros.org">ros-humble-moveit-setup-assistant</a>: 2.5.5-1 → 2.5.6-1</li> +<li>ros-humble-moveit-setup-assistant-dbgsym: 2.5.5-1 → 2.5.6-1</li> +<li>ros-humble-moveit-setup-controllers: 2.5.5-1 → 2.5.6-1</li> +<li>ros-humble-moveit-setup-controllers-dbgsym: 2.5.5-1 → 2.5.6-1</li> +<li>ros-humble-moveit-setup-core-plugins: 2.5.5-1 → 2.5.6-1</li> +<li>ros-humble-moveit-setup-core-plugins-dbgsym: 2.5.5-1 → 2.5.6-1</li> +<li>ros-humble-moveit-setup-framework: 2.5.5-1 → 2.5.6-1</li> +<li>ros-humble-moveit-setup-framework-dbgsym: 2.5.5-1 → 2.5.6-1</li> +<li>ros-humble-moveit-setup-srdf-plugins: 2.5.5-1 → 2.5.6-1</li> +<li>ros-humble-moveit-setup-srdf-plugins-dbgsym: 2.5.5-1 → 2.5.6-1</li> +<li><a href="http://moveit.ros.org">ros-humble-moveit-simple-controller-manager</a>: 2.5.5-1 → 2.5.6-1</li> +<li>ros-humble-moveit-simple-controller-manager-dbgsym: 2.5.5-1 → 2.5.6-1</li> +<li><a href="https://github.com/MOLAorg/mp2p_icp" rel="noopener nofollow ugc">ros-humble-mp2p-icp</a>: 1.6.2-1 → 1.6.3-1</li> +<li>ros-humble-mp2p-icp-dbgsym: 1.6.2-1 → 1.6.3-1</li> +<li><a href="https://www.mrpt.org/" rel="noopener nofollow ugc">ros-humble-mrpt-apps</a>: 2.14.4-1 → 2.14.5-1</li> +<li>ros-humble-mrpt-apps-dbgsym: 2.14.4-1 → 2.14.5-1</li> +<li><a href="https://www.mrpt.org/" rel="noopener nofollow ugc">ros-humble-mrpt-libapps</a>: 2.14.4-1 → 2.14.5-1</li> +<li>ros-humble-mrpt-libapps-dbgsym: 2.14.4-1 → 2.14.5-1</li> +<li><a href="https://www.mrpt.org/" rel="noopener nofollow ugc">ros-humble-mrpt-libbase</a>: 2.14.4-1 → 2.14.5-1</li> +<li>ros-humble-mrpt-libbase-dbgsym: 2.14.4-1 → 2.14.5-1</li> +<li><a href="https://www.mrpt.org/" rel="noopener nofollow ugc">ros-humble-mrpt-libgui</a>: 2.14.4-1 → 2.14.5-1</li> +<li>ros-humble-mrpt-libgui-dbgsym: 2.14.4-1 → 2.14.5-1</li> +<li><a href="https://www.mrpt.org/" rel="noopener nofollow ugc">ros-humble-mrpt-libhwdrivers</a>: 2.14.4-1 → 2.14.5-1</li> +<li>ros-humble-mrpt-libhwdrivers-dbgsym: 2.14.4-1 → 2.14.5-1</li> +<li><a href="https://www.mrpt.org/" rel="noopener nofollow ugc">ros-humble-mrpt-libmaps</a>: 2.14.4-1 → 2.14.5-1</li> +<li>ros-humble-mrpt-libmaps-dbgsym: 2.14.4-1 → 2.14.5-1</li> +<li><a href="https://www.mrpt.org/" rel="noopener nofollow ugc">ros-humble-mrpt-libmath</a>: 2.14.4-1 → 2.14.5-1</li> +<li>ros-humble-mrpt-libmath-dbgsym: 2.14.4-1 → 2.14.5-1</li> +<li><a href="https://www.mrpt.org/" rel="noopener nofollow ugc">ros-humble-mrpt-libnav</a>: 2.14.4-1 → 2.14.5-1</li> +<li>ros-humble-mrpt-libnav-dbgsym: 2.14.4-1 → 2.14.5-1</li> +<li><a href="https://www.mrpt.org/" rel="noopener nofollow ugc">ros-humble-mrpt-libobs</a>: 2.14.4-1 → 2.14.5-1</li> +<li>ros-humble-mrpt-libobs-dbgsym: 2.14.4-1 → 2.14.5-1</li> +<li><a href="https://www.mrpt.org/" rel="noopener nofollow ugc">ros-humble-mrpt-libopengl</a>: 2.14.4-1 → 2.14.5-1</li> +<li>ros-humble-mrpt-libopengl-dbgsym: 2.14.4-1 → 2.14.5-1</li> +<li><a href="https://www.mrpt.org/" rel="noopener nofollow ugc">ros-humble-mrpt-libposes</a>: 2.14.4-1 → 2.14.5-1</li> +<li>ros-humble-mrpt-libposes-dbgsym: 2.14.4-1 → 2.14.5-1</li> +<li><a href="https://www.mrpt.org/" rel="noopener nofollow ugc">ros-humble-mrpt-libros-bridge</a>: 2.14.4-1 → 2.14.5-1</li> +<li>ros-humble-mrpt-libros-bridge-dbgsym: 2.14.4-1 → 2.14.5-1</li> +<li><a href="https://www.mrpt.org/" rel="noopener nofollow ugc">ros-humble-mrpt-libslam</a>: 2.14.4-1 → 2.14.5-1</li> +<li>ros-humble-mrpt-libslam-dbgsym: 2.14.4-1 → 2.14.5-1</li> +<li><a href="https://www.mrpt.org/" rel="noopener nofollow ugc">ros-humble-mrpt-libtclap</a>: 2.14.4-1 → 2.14.5-1</li> +<li>ros-humble-nav-2d-msgs: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav-2d-msgs-dbgsym: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav-2d-utils: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav-2d-utils-dbgsym: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-amcl: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-amcl-dbgsym: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-behavior-tree: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-behavior-tree-dbgsym: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-behaviors: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-behaviors-dbgsym: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-bringup: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-bt-navigator: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-bt-navigator-dbgsym: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-collision-monitor: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-collision-monitor-dbgsym: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-common: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-constrained-smoother: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-constrained-smoother-dbgsym: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-controller: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-controller-dbgsym: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-core: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-costmap-2d: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-costmap-2d-dbgsym: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-dwb-controller: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-graceful-controller: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-graceful-controller-dbgsym: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-lifecycle-manager: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-lifecycle-manager-dbgsym: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-map-server: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-map-server-dbgsym: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-mppi-controller: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-mppi-controller-dbgsym: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-msgs: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-msgs-dbgsym: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-navfn-planner: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-navfn-planner-dbgsym: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-planner: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-planner-dbgsym: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-regulated-pure-pursuit-controller: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-regulated-pure-pursuit-controller-dbgsym: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-rotation-shim-controller: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-rotation-shim-controller-dbgsym: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-rviz-plugins: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-rviz-plugins-dbgsym: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-simple-commander: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-smac-planner: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-smac-planner-dbgsym: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-smoother: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-smoother-dbgsym: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-system-tests: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-system-tests-dbgsym: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-theta-star-planner: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-theta-star-planner-dbgsym: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-util: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-util-dbgsym: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-velocity-smoother: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-velocity-smoother-dbgsym: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-voxel-grid: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-voxel-grid-dbgsym: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-waypoint-follower: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-waypoint-follower-dbgsym: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-navigation2: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-novatel-gps-driver: 4.1.3-1 → 4.2.0-1</li> +<li>ros-humble-novatel-gps-driver-dbgsym: 4.1.3-1 → 4.2.0-1</li> +<li>ros-humble-novatel-gps-msgs: 4.1.3-1 → 4.2.0-1</li> +<li>ros-humble-novatel-gps-msgs-dbgsym: 4.1.3-1 → 4.2.0-1</li> +<li><a href="http://ros.org/wiki/octomap_msgs">ros-humble-octomap-msgs</a>: 2.0.0-3 → 2.0.1-1</li> +<li>ros-humble-octomap-msgs-dbgsym: 2.0.0-3 → 2.0.1-1</li> +<li>ros-humble-odom-to-tf-ros2: 1.0.2-1 → 1.0.4-1</li> +<li>ros-humble-odom-to-tf-ros2-dbgsym: 1.0.2-1 → 1.0.4-1</li> +<li>ros-humble-openni2-camera: 2.0.2-1 → 2.0.3-1</li> +<li>ros-humble-openni2-camera-dbgsym: 2.0.2-1 → 2.0.3-1</li> +<li>ros-humble-osrf-pycommon: 2.0.2-2 → 2.1.4-1</li> +<li><a href="https://github.com/pal-robotics/tiago_simulation" rel="noopener nofollow ugc">ros-humble-pal-gripper</a>: 3.3.0-1 → 3.4.0-1</li> +<li><a href="https://github.com/pal-robotics/tiago_simulation" rel="noopener nofollow ugc">ros-humble-pal-gripper-controller-configuration</a>: 3.3.0-1 → 3.4.0-1</li> +<li><a href="https://github.com/pal-robotics/tiago_simulation" rel="noopener nofollow ugc">ros-humble-pal-gripper-description</a>: 3.3.0-1 → 3.4.0-1</li> +<li>ros-humble-pal-gripper-simulation: 3.3.0-1 → 3.4.0-1</li> +<li><a href="https://github.com/pal-robotics" rel="noopener nofollow ugc">ros-humble-pal-maps</a>: 0.0.4-1 → 0.0.5-1</li> +<li><a href="https://github.com/pal-robotics/pal_statistics" rel="noopener nofollow ugc">ros-humble-pal-statistics</a>: 2.3.1-1 → 2.5.0-1</li> +<li>ros-humble-pal-statistics-dbgsym: 2.3.1-1 → 2.5.0-1</li> +<li><a href="https://github.com/pal-robotics/pal_statistics" rel="noopener nofollow ugc">ros-humble-pal-statistics-msgs</a>: 2.3.1-1 → 2.5.0-1</li> +<li>ros-humble-pal-statistics-msgs-dbgsym: 2.3.1-1 → 2.5.0-1</li> +<li>ros-humble-pid-controller: 2.37.3-1 → 2.38.0-1</li> +<li>ros-humble-pid-controller-dbgsym: 2.37.3-1 → 2.38.0-1</li> +<li><a href="http://moveit.ros.org">ros-humble-pilz-industrial-motion-planner</a>: 2.5.5-1 → 2.5.6-1</li> +<li>ros-humble-pilz-industrial-motion-planner-dbgsym: 2.5.5-1 → 2.5.6-1</li> +<li><a href="http://moveit.ros.org">ros-humble-pilz-industrial-motion-planner-testutils</a>: 2.5.5-1 → 2.5.6-1</li> +<li>ros-humble-pilz-industrial-motion-planner-testutils-dbgsym: 2.5.5-1 → 2.5.6-1</li> +<li><a href="https://github.com/pal-robotics/pmb2_simulation" rel="noopener nofollow ugc">ros-humble-pmb2-2dnav</a>: 4.2.0-1 → 4.5.0-1</li> +<li><a href="https://github.com/pal-robotics/pmb2_simulation" rel="noopener nofollow ugc">ros-humble-pmb2-bringup</a>: 5.3.1-1 → 5.4.0-1</li> +<li><a href="https://github.com/pal-robotics/pmb2_simulation" rel="noopener nofollow ugc">ros-humble-pmb2-controller-configuration</a>: 5.3.1-1 → 5.4.0-1</li> +<li><a href="https://github.com/pal-robotics/pmb2_simulation" rel="noopener nofollow ugc">ros-humble-pmb2-description</a>: 5.3.1-1 → 5.4.0-1</li> +<li><a href="https://github.com/pal-robotics/pmb2_simulation" rel="noopener nofollow ugc">ros-humble-pmb2-gazebo</a>: 4.0.16-1 → 4.1.0-1</li> +<li><a href="https://github.com/pal-robotics/pmb2_simulation" rel="noopener nofollow ugc">ros-humble-pmb2-laser-sensors</a>: 4.2.0-1 → 4.5.0-1</li> +<li><a href="https://github.com/pal-robotics/pmb2_simulation" rel="noopener nofollow ugc">ros-humble-pmb2-navigation</a>: 4.2.0-1 → 4.5.0-1</li> +<li><a href="https://github.com/pal-robotics/pmb2_simulation" rel="noopener nofollow ugc">ros-humble-pmb2-robot</a>: 5.3.1-1 → 5.4.0-1</li> +<li><a href="https://github.com/pal-robotics/pmb2_simulation" rel="noopener nofollow ugc">ros-humble-pmb2-simulation</a>: 4.0.16-1 → 4.1.0-1</li> +<li>ros-humble-position-controllers: 2.37.3-1 → 2.38.0-1</li> +<li>ros-humble-position-controllers-dbgsym: 2.37.3-1 → 2.38.0-1</li> +<li><a href="https://www.mrpt.org/" rel="noopener nofollow ugc">ros-humble-python-mrpt</a>: 2.14.4-1 → 2.14.5-1</li> +<li>ros-humble-range-sensor-broadcaster: 2.37.3-1 → 2.38.0-1</li> +<li>ros-humble-range-sensor-broadcaster-dbgsym: 2.37.3-1 → 2.38.0-1</li> +<li>ros-humble-rc-reason-clients: 0.3.1-1 → 0.4.0-2</li> +<li>ros-humble-rc-reason-msgs: 0.3.1-1 → 0.4.0-2</li> +<li>ros-humble-rc-reason-msgs-dbgsym: 0.3.1-1 → 0.4.0-2</li> +<li>ros-humble-rclcpp: 16.0.10-1 → 16.0.11-1</li> +<li>ros-humble-rclcpp-action: 16.0.10-1 → 16.0.11-1</li> +<li>ros-humble-rclcpp-action-dbgsym: 16.0.10-1 → 16.0.11-1</li> +<li>ros-humble-rclcpp-components: 16.0.10-1 → 16.0.11-1</li> +<li>ros-humble-rclcpp-components-dbgsym: 16.0.10-1 → 16.0.11-1</li> +<li>ros-humble-rclcpp-dbgsym: 16.0.10-1 → 16.0.11-1</li> +<li>ros-humble-rclcpp-lifecycle: 16.0.10-1 → 16.0.11-1</li> +<li>ros-humble-rclcpp-lifecycle-dbgsym: 16.0.10-1 → 16.0.11-1</li> +<li>ros-humble-rclpy: 3.3.14-1 → 3.3.15-1</li> +<li>ros-humble-rcpputils: 2.4.3-1 → 2.4.4-1</li> +<li>ros-humble-rcpputils-dbgsym: 2.4.3-1 → 2.4.4-1</li> +<li><a href="https://control.ros.org">ros-humble-realtime-tools</a>: 2.7.0-1 → 2.8.1-1</li> +<li>ros-humble-realtime-tools-dbgsym: 2.7.0-1 → 2.8.1-1</li> +<li>ros-humble-rmf-building-map-tools: 1.6.2-1 → 1.6.3-1</li> +<li>ros-humble-rmf-traffic-editor: 1.6.2-1 → 1.6.3-1</li> +<li>ros-humble-rmf-traffic-editor-assets: 1.6.2-1 → 1.6.3-1</li> +<li>ros-humble-rmf-traffic-editor-dbgsym: 1.6.2-1 → 1.6.3-1</li> +<li>ros-humble-rmf-traffic-editor-test-maps: 1.6.2-1 → 1.6.3-1</li> +<li>ros-humble-rmw-connextdds: 0.11.2-1 → 0.11.3-1</li> +<li>ros-humble-rmw-connextdds-common: 0.11.2-1 → 0.11.3-1</li> +<li>ros-humble-rmw-connextdds-common-dbgsym: 0.11.2-1 → 0.11.3-1</li> +<li>ros-humble-rmw-connextdds-dbgsym: 0.11.2-1 → 0.11.3-1</li> +<li><a href="http://ros.org/wiki/robot_calibration">ros-humble-robot-calibration</a>: 0.8.1-1 → 0.8.2-1</li> +<li>ros-humble-robot-calibration-dbgsym: 0.8.1-1 → 0.8.2-1</li> +<li><a href="http://ros.org/wiki/robot_calibration_msgs">ros-humble-robot-calibration-msgs</a>: 0.8.1-1 → 0.8.2-1</li> +<li>ros-humble-robot-calibration-msgs-dbgsym: 0.8.1-1 → 0.8.2-1</li> +<li><a href="https://control.ros.org">ros-humble-ros2-control</a>: 2.43.1-1 → 2.44.0-1</li> +<li>ros-humble-ros2-control-test-assets: 2.43.1-1 → 2.44.0-1</li> +<li><a href="https://control.ros.org">ros-humble-ros2-controllers</a>: 2.37.3-1 → 2.38.0-1</li> +<li>ros-humble-ros2-controllers-test-nodes: 2.37.3-1 → 2.38.0-1</li> +<li>ros-humble-ros2bag: 0.15.12-1 → 0.15.13-1</li> +<li>ros-humble-ros2controlcli: 2.43.1-1 → 2.44.0-1</li> +<li>ros-humble-ros2launch: 0.19.7-2 → 0.19.8-1</li> +<li>ros-humble-rosbag2: 0.15.12-1 → 0.15.13-1</li> +<li>ros-humble-rosbag2-compression: 0.15.12-1 → 0.15.13-1</li> +<li>ros-humble-rosbag2-compression-dbgsym: 0.15.12-1 → 0.15.13-1</li> +<li>ros-humble-rosbag2-compression-zstd: 0.15.12-1 → 0.15.13-1</li> +<li>ros-humble-rosbag2-compression-zstd-dbgsym: 0.15.12-1 → 0.15.13-1</li> +<li>ros-humble-rosbag2-cpp: 0.15.12-1 → 0.15.13-1</li> +<li>ros-humble-rosbag2-cpp-dbgsym: 0.15.12-1 → 0.15.13-1</li> +<li>ros-humble-rosbag2-interfaces: 0.15.12-1 → 0.15.13-1</li> +<li>ros-humble-rosbag2-interfaces-dbgsym: 0.15.12-1 → 0.15.13-1</li> +<li>ros-humble-rosbag2-performance-benchmarking: 0.15.12-1 → 0.15.13-1</li> +<li>ros-humble-rosbag2-py: 0.15.12-1 → 0.15.13-1</li> +<li>ros-humble-rosbag2-storage: 0.15.12-1 → 0.15.13-1</li> +<li>ros-humble-rosbag2-storage-dbgsym: 0.15.12-1 → 0.15.13-1</li> +<li>ros-humble-rosbag2-storage-default-plugins: 0.15.12-1 → 0.15.13-1</li> +<li>ros-humble-rosbag2-storage-default-plugins-dbgsym: 0.15.12-1 → 0.15.13-1</li> +<li>ros-humble-rosbag2-storage-mcap: 0.15.12-1 → 0.15.13-1</li> +<li>ros-humble-rosbag2-storage-mcap-dbgsym: 0.15.12-1 → 0.15.13-1</li> +<li>ros-humble-rosbag2-storage-mcap-testdata: 0.15.12-1 → 0.15.13-1</li> +<li>ros-humble-rosbag2-storage-mcap-testdata-dbgsym: 0.15.12-1 → 0.15.13-1</li> +<li>ros-humble-rosbag2-test-common: 0.15.12-1 → 0.15.13-1</li> +<li>ros-humble-rosbag2-tests: 0.15.12-1 → 0.15.13-1</li> +<li>ros-humble-rosbag2-transport: 0.15.12-1 → 0.15.13-1</li> +<li>ros-humble-rosbag2-transport-dbgsym: 0.15.12-1 → 0.15.13-1</li> +<li>ros-humble-rosidl-adapter: 3.1.5-2 → 3.1.6-1</li> +<li>ros-humble-rosidl-cli: 3.1.5-2 → 3.1.6-1</li> +<li>ros-humble-rosidl-cmake: 3.1.5-2 → 3.1.6-1</li> +<li>ros-humble-rosidl-generator-c: 3.1.5-2 → 3.1.6-1</li> +<li>ros-humble-rosidl-generator-cpp: 3.1.5-2 → 3.1.6-1</li> +<li>ros-humble-rosidl-parser: 3.1.5-2 → 3.1.6-1</li> +<li>ros-humble-rosidl-runtime-c: 3.1.5-2 → 3.1.6-1</li> +<li>ros-humble-rosidl-runtime-c-dbgsym: 3.1.5-2 → 3.1.6-1</li> +<li>ros-humble-rosidl-runtime-cpp: 3.1.5-2 → 3.1.6-1</li> +<li>ros-humble-rosidl-typesupport-c: 2.0.1-1 → 2.0.2-1</li> +<li>ros-humble-rosidl-typesupport-c-dbgsym: 2.0.1-1 → 2.0.2-1</li> +<li>ros-humble-rosidl-typesupport-cpp: 2.0.1-1 → 2.0.2-1</li> +<li>ros-humble-rosidl-typesupport-cpp-dbgsym: 2.0.1-1 → 2.0.2-1</li> +<li>ros-humble-rosidl-typesupport-interface: 3.1.5-2 → 3.1.6-1</li> +<li>ros-humble-rosidl-typesupport-introspection-c: 3.1.5-2 → 3.1.6-1</li> +<li>ros-humble-rosidl-typesupport-introspection-c-dbgsym: 3.1.5-2 → 3.1.6-1</li> +<li>ros-humble-rosidl-typesupport-introspection-cpp: 3.1.5-2 → 3.1.6-1</li> +<li>ros-humble-rosidl-typesupport-introspection-cpp-dbgsym: 3.1.5-2 → 3.1.6-1</li> +<li><a href="http://ros.org/wiki/rqt_controller_manager">ros-humble-rqt-controller-manager</a>: 2.43.1-1 → 2.44.0-1</li> +<li>ros-humble-rqt-joint-trajectory-controller: 2.37.3-1 → 2.38.0-1</li> +<li>ros-humble-rti-connext-dds-cmake-module: 0.11.2-1 → 0.11.3-1</li> +<li><a href="http://assimp.sourceforge.net/index.html" rel="noopener nofollow ugc">ros-humble-rviz-assimp-vendor</a>: 11.2.13-1 → 11.2.14-1</li> +<li><a href="https://github.com/ros2/rviz/blob/ros2/README.md" rel="noopener nofollow ugc">ros-humble-rviz-common</a>: 11.2.13-1 → 11.2.14-1</li> +<li>ros-humble-rviz-common-dbgsym: 11.2.13-1 → 11.2.14-1</li> +<li><a href="https://github.com/ros2/rviz/blob/ros2/README.md" rel="noopener nofollow ugc">ros-humble-rviz-default-plugins</a>: 11.2.13-1 → 11.2.14-1</li> +<li>ros-humble-rviz-default-plugins-dbgsym: 11.2.13-1 → 11.2.14-1</li> +<li><a href="https://www.ogre3d.org/" rel="noopener nofollow ugc">ros-humble-rviz-ogre-vendor</a>: 11.2.13-1 → 11.2.14-1</li> +<li>ros-humble-rviz-ogre-vendor-dbgsym: 11.2.13-1 → 11.2.14-1</li> +<li><a href="https://github.com/ros2/rviz/blob/ros2/README.md" rel="noopener nofollow ugc">ros-humble-rviz-rendering</a>: 11.2.13-1 → 11.2.14-1</li> +<li>ros-humble-rviz-rendering-dbgsym: 11.2.13-1 → 11.2.14-1</li> +<li>ros-humble-rviz-rendering-tests: 11.2.13-1 → 11.2.14-1</li> +<li><a href="http://ros.org/wiki/rviz2">ros-humble-rviz-visual-testing-framework</a>: 11.2.13-1 → 11.2.14-1</li> +<li><a href="https://github.com/ros2/rviz/blob/ros2/README.md" rel="noopener nofollow ugc">ros-humble-rviz2</a>: 11.2.13-1 → 11.2.14-1</li> +<li>ros-humble-rviz2-dbgsym: 11.2.13-1 → 11.2.14-1</li> +<li>ros-humble-shared-queues-vendor: 0.15.12-1 → 0.15.13-1</li> +<li>ros-humble-spinnaker-camera-driver: 2.1.17-1 → 3.0.0-1</li> +<li>ros-humble-spinnaker-camera-driver-dbgsym: 2.1.17-1 → 3.0.0-1</li> +<li>ros-humble-spinnaker-synchronized-camera-driver: 2.1.17-1 → 3.0.0-1</li> +<li>ros-humble-spinnaker-synchronized-camera-driver-dbgsym: 2.1.17-1 → 3.0.0-1</li> +<li>ros-humble-sqlite3-vendor: 0.15.12-1 → 0.15.13-1</li> +<li>ros-humble-steering-controllers-library: 2.37.3-1 → 2.38.0-1</li> +<li>ros-humble-steering-controllers-library-dbgsym: 2.37.3-1 → 2.38.0-1</li> +<li>ros-humble-teleop-tools: 1.6.0-1 → 1.7.0-1</li> +<li>ros-humble-teleop-tools-msgs: 1.6.0-1 → 1.7.0-1</li> +<li>ros-humble-teleop-tools-msgs-dbgsym: 1.6.0-1 → 1.7.0-1</li> +<li><a href="http://www.ros.org/wiki/tf2">ros-humble-tf2</a>: 0.25.8-1 → 0.25.9-1</li> +<li><a href="http://www.ros.org/wiki/tf2_bullet">ros-humble-tf2-bullet</a>: 0.25.8-1 → 0.25.9-1</li> +<li>ros-humble-tf2-dbgsym: 0.25.8-1 → 0.25.9-1</li> +<li>ros-humble-tf2-eigen: 0.25.8-1 → 0.25.9-1</li> +<li>ros-humble-tf2-eigen-kdl: 0.25.8-1 → 0.25.9-1</li> +<li>ros-humble-tf2-eigen-kdl-dbgsym: 0.25.8-1 → 0.25.9-1</li> +<li><a href="http://www.ros.org/wiki/tf2_ros">ros-humble-tf2-geometry-msgs</a>: 0.25.8-1 → 0.25.9-1</li> +<li><a href="http://ros.org/wiki/tf2">ros-humble-tf2-kdl</a>: 0.25.8-1 → 0.25.9-1</li> +<li><a href="http://www.ros.org/wiki/tf2_msgs">ros-humble-tf2-msgs</a>: 0.25.8-1 → 0.25.9-1</li> +<li>ros-humble-tf2-msgs-dbgsym: 0.25.8-1 → 0.25.9-1</li> +<li><a href="http://ros.org/wiki/tf2_py">ros-humble-tf2-py</a>: 0.25.8-1 → 0.25.9-1</li> +<li>ros-humble-tf2-py-dbgsym: 0.25.8-1 → 0.25.9-1</li> +<li><a href="http://www.ros.org/wiki/tf2_ros">ros-humble-tf2-ros</a>: 0.25.8-1 → 0.25.9-1</li> +<li>ros-humble-tf2-ros-dbgsym: 0.25.8-1 → 0.25.9-1</li> +<li><a href="http://www.ros.org/wiki/tf2_ros">ros-humble-tf2-ros-py</a>: 0.25.8-1 → 0.25.9-1</li> +<li><a href="http://www.ros.org/wiki/tf2_ros">ros-humble-tf2-sensor-msgs</a>: 0.25.8-1 → 0.25.9-1</li> +<li><a href="http://www.ros.org/wiki/tf2_tools">ros-humble-tf2-tools</a>: 0.25.8-1 → 0.25.9-1</li> +<li><a href="https://github.com/pal-robotics/tiago_simulation" rel="noopener nofollow ugc">ros-humble-tiago-2dnav</a>: 4.2.0-1 → 4.5.0-1</li> +<li><a href="https://github.com/pal-robotics/tiago_simulation" rel="noopener nofollow ugc">ros-humble-tiago-bringup</a>: 4.6.0-1 → 4.7.1-1</li> +<li><a href="https://github.com/pal-robotics/tiago_simulation" rel="noopener nofollow ugc">ros-humble-tiago-controller-configuration</a>: 4.6.0-1 → 4.7.1-1</li> +<li><a href="https://github.com/pal-robotics/tiago_simulation" rel="noopener nofollow ugc">ros-humble-tiago-description</a>: 4.6.0-1 → 4.7.1-1</li> +<li><a href="https://github.com/pal-robotics/tiago_simulation" rel="noopener nofollow ugc">ros-humble-tiago-gazebo</a>: 4.2.0-1 → 4.3.0-1</li> +<li>ros-humble-tiago-gazebo-dbgsym: 4.2.0-1 → 4.3.0-1</li> +<li><a href="https://github.com/pal-robotics/tiago_simulation" rel="noopener nofollow ugc">ros-humble-tiago-laser-sensors</a>: 4.2.0-1 → 4.5.0-1</li> +<li><a href="https://github.com/pal-robotics/tiago_simulation" rel="noopener nofollow ugc">ros-humble-tiago-moveit-config</a>: 3.1.0-1 → 3.1.1-1</li> +<li><a href="https://github.com/pal-robotics/tiago_simulation" rel="noopener nofollow ugc">ros-humble-tiago-navigation</a>: 4.2.0-1 → 4.5.0-1</li> +<li><a href="https://github.com/pal-robotics/tiago_simulation" rel="noopener nofollow ugc">ros-humble-tiago-robot</a>: 4.6.0-1 → 4.7.1-1</li> +<li><a href="https://github.com/pal-robotics/tiago_simulation" rel="noopener nofollow ugc">ros-humble-tiago-simulation</a>: 4.2.0-1 → 4.3.0-1</li> +<li>ros-humble-transmission-interface: 2.43.1-1 → 2.44.0-1</li> +<li>ros-humble-transmission-interface-dbgsym: 2.43.1-1 → 2.44.0-1</li> +<li>ros-humble-tricycle-controller: 2.37.3-1 → 2.38.0-1</li> +<li>ros-humble-tricycle-controller-dbgsym: 2.37.3-1 → 2.38.0-1</li> +<li>ros-humble-tricycle-steering-controller: 2.37.3-1 → 2.38.0-1</li> +<li>ros-humble-tricycle-steering-controller-dbgsym: 2.37.3-1 → 2.38.0-1</li> +<li>ros-humble-twist-stamper: 0.0.3-1 → 0.0.5-1</li> +<li><a href="http://wiki.ros.org/ur_client_library">ros-humble-ur-client-library</a>: 1.4.0-1 → 1.5.0-1</li> +<li>ros-humble-ur-client-library-dbgsym: 1.4.0-1 → 1.5.0-1</li> +<li>ros-humble-velocity-controllers: 2.37.3-1 → 2.38.0-1</li> +<li>ros-humble-velocity-controllers-dbgsym: 2.37.3-1 → 2.38.0-1</li> +<li><a href="https://facebook.github.io/zstd/" rel="noopener nofollow ugc">ros-humble-zstd-vendor</a>: 0.15.12-1 → 0.15.13-1</li> +</ul> +<h3><a class="anchor" href="https://discourse.ros.org#p-88326-removed-packages-6-4" name="p-88326-removed-packages-6-4"></a>Removed Packages [6]:</h3> +<ul> +<li>ros-humble-clearpath-platform</li> +<li>ros-humble-clearpath-platform-dbgsym</li> +<li><a href="https://www.mrpt.org/" rel="noopener nofollow ugc">ros-humble-mrpt2</a></li> +<li>ros-humble-mrpt2-dbgsym</li> +<li>ros-humble-omni-base-maps</li> +<li><a href="https://github.com/swri-robotics/marti_common" rel="noopener nofollow ugc">ros-humble-swri-prefix-tools</a></li> +</ul> +<p>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:</p> +<ul> +<li>Adam Serafin</li> +<li>Aditya Pande</li> +<li>Aina Irisarri</li> +<li>Alberto Tudela</li> +<li>Alejandro Hernandez Cordero</li> +<li>Alexander Gutenkunst</li> +<li>Alexey Merzlyakov</li> +<li>Analog Devices</li> +<li>Andrea Sorbini</li> +<li>Antonio Brandi</li> +<li>Bence Magyar</li> +<li>Bernd Pfrommer</li> +<li>Blake Anderson</li> +<li>Brandon Ong</li> +<li>Brian Wilcox</li> +<li>Błażej Sowa</li> +<li>Carl Delsey</li> +<li>Carlos Orduno</li> +<li>Chittaranjan Srinivas Swaminathan</li> +<li>Chris Iverach-Brereton</li> +<li>Chris Lalancette</li> +<li>Christian Henkel</li> +<li>Christian Rauch</li> +<li>David V. Lu!!</li> +<li>Denis Štogl</li> +<li>Eclipse Foundation, Inc.</li> +<li>Enrique Fernandez</li> +<li>Evan Flynn</li> +<li>Felix Exner</li> +<li>Felix Ruess</li> +<li>Fictionlab</li> +<li>Foxglove</li> +<li>George Stavrinos</li> +<li>Hans-Joachim Krauch</li> +<li>Henning Kayser</li> +<li>Ivan Paunovic</li> +<li>Jacob Perron</li> +<li>Jafar Uruc</li> +<li>Jean-Pierre Busch</li> +<li>Jordan Palacios</li> +<li>Jordi Pages</li> +<li>Jose Mastrangelo</li> +<li>Jose-Luis Blanco-Claraco</li> +<li>Josh Newans</li> +<li>Luis Camero</li> +<li>Luka Juricic</li> +<li>Mamoru Sobue</li> +<li>Marc Alban</li> +<li>Matej Vargovcik</li> +<li>Michael Ferguson</li> +<li>Michael Görner</li> +<li>Michael Jeronimo</li> +<li>Michael Orlov</li> +<li>Michel Hidalgo</li> +<li>Miguel Company</li> +<li>Mike Purvis</li> +<li>Mohammad Haghighipanah</li> +<li>Morgan Quigley</li> +<li>MoveIt Release Team</li> +<li>P. J. Reed</li> +<li>ROS Tooling Working Group</li> +<li>Raghavender Sahdev</li> +<li>Ralph Lange</li> +<li>Rob Fisher</li> +<li>Robert Wilbrandt</li> +<li>Roni Kreinin</li> +<li>STEREOLABS</li> +<li>Shane Loretz</li> +<li>Stefan Laible</li> +<li>Steve Macenski</li> +<li>Séverin Lemaignan</li> +<li>TIAGo PAL support team</li> +<li>TIAGo support team</li> +<li>Tony Baltovski</li> +<li>Victor López</li> +<li>William Woodall</li> +<li>Wolfgang Merkt</li> +<li>mitsudome-r</li> +<li>pradyum</li> +<li>ruess</li> +<li>steve</li> +</ul> + <p><small>1 post - 1 participant</small></p> + <p><a href="https://discourse.ros.org/t/new-packages-and-patch-release-for-humble-hawksbill-2024-12-05/40976">Read full topic</a></p> + 2024-12-05T20:17:28+00:00 + audrow + + + ROS Discourse General: Clearpath Simulator comes to Gazebo Harmonic :fire: + https://discourse.ros.org/t/clearpath-simulator-comes-to-gazebo-harmonic/40975 + <p>Hello everyone,</p> +<p>I have successfully ported Clearpath Robotics’s open-source simulator <a href="https://github.com/clearpathrobotics/clearpath_simulator" rel="noopener nofollow ugc">clearpath_simulator</a> into <strong>Gazebo Harmonic LTS</strong>.</p> +<p>Key changes include adding support for Xbox One controllers, support for custom <code>robot.yaml</code> names and automatic Twist message conversion to TwistStamped required by the newer builds of <code>ros2_controllers</code> and Gazebo. The simulator has been tested to work in Ubuntu 22.04 (source build). Presently, only <strong>A200 Husky</strong> is supported. Version 0.2 will add RGB-D sensor and build testing in Ubuntu 24.04.</p> +<p></p><div class="lightbox-wrapper"><a class="lightbox" href="https://global.discourse-cdn.com/flex022/uploads/ros/original/3X/b/e/be3b8e0353f1e6c5a73f53dc6a6c73f7d041a9ea.jpeg" rel="noopener nofollow ugc" title="image"><img alt="image" height="428" src="https://global.discourse-cdn.com/flex022/uploads/ros/optimized/3X/b/e/be3b8e0353f1e6c5a73f53dc6a6c73f7d041a9ea_2_690x428.jpeg" width="690" /></a></div><p></p> +<p>To accommodate a number of changes made to almost all the original dependent packages, I have opted to host my derived work separately here: <a class="inline-onebox" href="https://github.com/Mechazo11/clearpath_simulator_harmonic" rel="noopener nofollow ugc">GitHub - Mechazo11/clearpath_simulator_harmonic: A port of Clearpath Simulator, compatible with ROS 2 Jazzy and Gazebo Harmonic</a></p> +<p>A big shout-out to <strong>Clearpath Robotics</strong> team for making the original simulator publicly available. I hope this work proves valuable to the community. If you have any questions, concerns or would like to contribute please don’t hesitate to reaching out to me.</p> +<p>With best regards,<br /> +Azmyin Md. Kamal</p> + <p><small>1 post - 1 participant</small></p> + <p><a href="https://discourse.ros.org/t/clearpath-simulator-comes-to-gazebo-harmonic/40975">Read full topic</a></p> + 2024-12-05T19:42:05+00:00 + azmyin12 + + + ROS Discourse General: Expose secure communication only with specified entities + https://discourse.ros.org/t/expose-secure-communication-only-with-specified-entities/40957 + <p>Hi ROS developers,</p> +<p>Asking thoughts and ideas!</p> +<p>I think this is more like discussion to explore than a question, I would like to have feedback from the community how to handle this situation to support 3rd party device.</p> +<p>Original issue: <a class="inline-onebox" href="https://github.com/ros2/sros2/issues/326" rel="noopener nofollow ugc">Expose secure communication only with specified entities. · Issue #326 · ros2/sros2 · GitHub</a></p> +<p></p><div class="lightbox-wrapper"><a class="lightbox" href="https://global.discourse-cdn.com/flex022/uploads/ros/original/3X/3/5/35632153b9d04cd824e0e77b298998b5e16cc7e7.png" rel="noopener nofollow ugc" title="image"><img alt="image" height="385" src="https://global.discourse-cdn.com/flex022/uploads/ros/optimized/3X/3/5/35632153b9d04cd824e0e77b298998b5e16cc7e7_2_690x385.png" width="690" /></a></div><p></p> +<ul> +<li>For performance consideration, it would be better to keep the localhost communication in robot without secured authentication nor encryption. (basically it uses localhost in robot system, but some specific nodes to be exposed.)</li> +</ul> +<p>I am trying to find out what could be best solution to support above requirement with secured communication with sros2.</p> +<p>If you have any experience, please enlighten me <img alt=":pray:" class="emoji" height="20" src="https://emoji.discourse-cdn.com/twitter/pray.png?v=12" title=":pray:" width="20" /> <img alt=":pray:" class="emoji" height="20" src="https://emoji.discourse-cdn.com/twitter/pray.png?v=12" title=":pray:" width="20" /> <img alt=":pray:" class="emoji" height="20" src="https://emoji.discourse-cdn.com/twitter/pray.png?v=12" title=":pray:" width="20" /></p> +<p>Regards,<br /> +Tomoya</p> + <p><small>6 posts - 3 participants</small></p> + <p><a href="https://discourse.ros.org/t/expose-secure-communication-only-with-specified-entities/40957">Read full topic</a></p> + 2024-12-04T22:10:01+00:00 + tomoyafujita + + + ROS Discourse General: Next Client Library WG Meeting: Friday 6th December 2024 8AM PT + https://discourse.ros.org/t/next-client-library-wg-meeting-friday-6th-december-2024-8am-pt/40954 + <p>Hi,<br /> +The next meeting of the Client Library Working Group will be this Friday, 6th December 2024 at 8 AM Pacific Time.</p> +<ul> +<li>Meeting link: <a href="https://meet.google.com/oij-atzj-znw" rel="noopener nofollow ugc">https://meet.google.com/oij-atzj-znw </a></li> +<li>Calendar invite: <a href="https://calendar.app.google/WDSVtbpSu5SrNc1Q8" rel="noopener nofollow ugc">https://calendar.app.google/WDSVtbpSu5SrNc1Q8</a></li> +<li>Google group if you want to be notified of future meetings: <a href="https://groups.google.com/g/ros-2-client-library-wg" rel="noopener nofollow ugc">https://groups.google.com/g/ros-2-client-library-wg</a></li> +</ul> +<p>We will be reviewing the charter proposal for the ROS 2 Client Library Working Group and continue the discussions from the previous meetings.</p> + <p><small>2 posts - 1 participant</small></p> + <p><a href="https://discourse.ros.org/t/next-client-library-wg-meeting-friday-6th-december-2024-8am-pt/40954">Read full topic</a></p> + 2024-12-04T18:12:58+00:00 + alsora + + + ROS Discourse General: Call for Participation: ROS Deliberation Community Group + https://discourse.ros.org/t/call-for-participation-ros-deliberation-community-group/40932 + <p>Hello all,</p> +<p>After our <a href="https://github.com/ros-wg-delib/roscon24-workshop" rel="noopener nofollow ugc">successful workshop</a> at ROSCon 2024, the <a href="https://github.com/ros-wg-delib" rel="noopener nofollow ugc">ROS Deliberation Community Group</a> is resuming its focus on monthly meetings to engage with the community.</p> +<p>For those who were formerly attending the meetings before we spent time preparing for the workshop, the time is right to start attending again! If you are considering attending for the first time, or have never heard of this Community Group before, we look forward to seeing you as well.</p> +<p>Either way, we’d like to hear from you all about possible topics for subsequent meetings in the new year. Some initial ideas:</p> +<ul> +<li>Putting together a survey document of ROS 2 Deliberation Technologies, very much inspired by the great <a href="https://arxiv.org/abs/2307.15236" rel="noopener nofollow ugc">Nav2 paper</a>.</li> +<li>Collaborating on the development of open-source software tools, or examples using those tools, for robot deliberation.</li> +<li>Presentations from people interested in sharing their work (though we’d like to also have time for working discussions as well).</li> +</ul> +<p>If anyone wants to share ideas or ask any questions, feel free to post here, or just show up to the next meeting(s)! You can find more information, including how to sign up in <a href="https://docs.google.com/document/d/13TCHp3ycbDa2agGs0SjP3CpTllUeguAcXqih5LlCVDg/edit?tab=t.0#heading=h.lnamemvhhzoa" rel="noopener nofollow ugc">this document</a>.</p> + <p><small>3 posts - 2 participants</small></p> + <p><a href="https://discourse.ros.org/t/call-for-participation-ros-deliberation-community-group/40932">Read full topic</a></p> + 2024-12-03T02:00:55+00:00 + scastro + + + ROS Discourse General: Gazebo Classic and Citadel End of Life [x-post Gazebo Sim Community] + https://discourse.ros.org/t/gazebo-classic-and-citadel-end-of-life-x-post-gazebo-sim-community/40931 + <p><a href="https://community.gazebosim.org/t/gazebo-classic-and-citadel-end-of-life/3242">Original Post</a></p> +<p>Hi Everyone,</p> +<p>This is your friendly reminder that as outlined here Gazebo Classic (i.e. Gazebo 11) <a href="https://classic.gazebosim.org/#status">will officially go end of life on Friday, January 31st, 2025</a>. Gazebo Citadel, our first modern Gazebo LTS release, will go end of life on December 30th, 2024. Gazebo Classic users are advised to transition to an LTS modern Gazebo release as soon as possible (we recommend <a href="https://gazebosim.org/docs/harmonic/install_ubuntu/">Gazebo Harmonic</a>, or <a href="https://gazebosim.org/docs/fortress/install_ubuntu/">Gazebo Fortress</a>). We recommend that Gazebo Citadel users also upgrade to either Harmonic or Fortress. Information about currently supported Gazebo versions and support windows, <a href="https://gazebosim.org/docs/latest/releases/">can be found here</a>.</p> +<h3><a class="anchor" href="https://discourse.ros.org#p-88253-what-does-end-of-life-mean-1" name="p-88253-what-does-end-of-life-mean-1"></a>What does End of Life Mean?</h3> +<p>Users often ask us, “what does end of life mean?” To put it briefly, end of life means that the Gazebo team will no longer support that particular Gazebo release. In practical terms, this means that we will no longer be providing the following for Gazebo Classic:</p> +<ul> +<li>New features or capabilities</li> +<li>Security updates</li> +<li>Bug fixes, patches or support</li> +<li>Updated binaries</li> +</ul> +<p>It is also worth noting the things that won’t change after Gazebo Classic goes end of life:</p> +<ul> +<li>Gazebo Classic binaries will not suddenly disappear</li> +<li>Users will not need to migrate immediately, but they should migrate as soon as possible</li> +<li>Your project will not suddenly stop working on January 31st</li> +</ul> +<h3><a class="anchor" href="https://discourse.ros.org#p-88253-why-do-we-end-of-life-gazebo-releases-2" name="p-88253-why-do-we-end-of-life-gazebo-releases-2"></a>Why do we End of Life Gazebo releases?</h3> +<p>We End of Life particular Gazebo releases for the same reason that most people don’t use Windows XP or an iPhone 4 anymore: better versions of the software are now available and we simply don’t have the resources to support every Gazebo release into perpetuity. Marking a particular version of Gazebo end of life frees up resources to help support newer and better versions of the software. More to the point, the underlying packages and operating system (<a href="https://wiki.ubuntu.com/Releases">Ubuntu Focal</a>) used by Gazebo Classic also goes end of life in April 2025.</p> +<h3><a class="anchor" href="https://discourse.ros.org#p-88253-how-do-i-upgrade-to-a-newer-version-of-gazebo-and-which-one-should-i-use-3" name="p-88253-how-do-i-upgrade-to-a-newer-version-of-gazebo-and-which-one-should-i-use-3"></a>How do I upgrade to a newer version of Gazebo and which one should I use?</h3> +<p>We recommend that Gazebo Classic users upgrade to the latest long term support release of modern Gazebo, <a href="https://gazebosim.org/docs/harmonic/install_ubuntu/">Gazebo Harmonic</a>. Gazebo Harmonic works best on Ubuntu Jammy (22.04) and Ubuntu Noble (24.04) and will be supported until September of 2028. Gazebo Classic users who still use ROS 1 will also need to upgrade to ROS 2 Jazzy to use Gazebo Harmonic. It is worth noting that all of ROS 1, including ROS 1 Noetic, will go end of life on May 23rd, 2025. Our internal estimates indicate that over 80% of the ROS community has already upgraded to ROS 2, and 67% of Gazebo users have already upgraded to modern Gazebo.</p> +<p>The modern Gazebo documentation includes a variety of guides and tutorials on how to <a href="https://gazebosim.org/docs/harmonic/gazebo_classic_migration/">migrate your project from Gazebo Classic to modern Gazebo.</a> Similarly, the ROS 2 documentation provides <a href="https://docs.ros.org/en/jazzy/How-To-Guides/Migrating-from-ROS1.html">step by step instructions on how to migrate your ROS 1 project to ROS 2</a>. If you get stuck during migration, we would encourage you to use the <a href="https://discord.com/servers/open-robotics-1077825543698927656">Open Robotics Discord</a>, the <a href="https://community.gazebosim.org/">Gazebo Sim Community</a>, and <a href="https://community.gazebosim.org/">Robotics Stack Exchange</a> to find help.</p> +<h3><a class="anchor" href="https://discourse.ros.org#p-88253-help-spread-the-word-4" name="p-88253-help-spread-the-word-4"></a>Help Spread the Word</h3> +<p>We realize that many Gazebo Classic users don’t really track Gazebo end of life dates, or regularly visit Gazebosim Community, that’s why we’ve decided to include some notifications about Gazebo Classic’s impending end of life in our latest Gazebo Classic update. Starting this week, after<a href="https://github.com/gazebosim/gazebo-classic/blob/gazebo11/Changelog.md#gazebo-11150-2024-11-26"> updating Gazebo Classic</a> users will be <a href="https://github.com/gazebosim/gazebo-classic/pull/3405">notified via debug output and pop-ups of the upcoming end of life date</a>. These warnings can be suppressed by simply setting a “GAZEBO_SUPPRESS_EOL_WARNING” environment variable.</p> +<p>We would appreciate the community’s help in spreading the word about the upcoming Gazebo Classic End of Life. If you work on a team that is still using Gazebo Classic please take a moment in the next week or two to discuss upgrade paths with your team and the importance of upgrading as soon as possible.</p> + <p><small>2 posts - 1 participant</small></p> + <p><a href="https://discourse.ros.org/t/gazebo-classic-and-citadel-end-of-life-x-post-gazebo-sim-community/40931">Read full topic</a></p> + 2024-12-02T22:01:50+00:00 + Katherine_Scott + + + ROS Discourse General: What versions of Moveit 2 are people using? + https://discourse.ros.org/t/what-versions-of-moveit-2-are-people-using/40908 + <p>I’ve posted a poll on the Moveit 2 discussions board asking for feedback regarding which versions people are using, as it seems like it’d be interesting to gather some quantitative data.</p> +<p>Figured I’d post it here, too, for more visibility:</p> +<aside class="onebox allowlistedgeneric"> + <header class="source"> + <img class="site-icon" height="32" src="https://global.discourse-cdn.com/flex022/uploads/ros/original/2X/b/bad3e5f9ad67c1ddf145107ce7032ac1d7b22563.svg" width="32" /> + + <a href="https://github.com/orgs/moveit/discussions/3138" rel="noopener nofollow ugc" target="_blank">GitHub</a> + </header> + + <article class="onebox-body"> + <div class="aspect-image"><img class="thumbnail" height="345" src="https://global.discourse-cdn.com/flex022/uploads/ros/optimized/3X/8/a/8a3acef9f83f7dd78ad168763cf690a2ad9d4439_2_690x345.png" width="690" /></div> + +<h3><a href="https://github.com/orgs/moveit/discussions/3138" rel="noopener nofollow ugc" target="_blank">What versions of Moveit 2 are people using? · moveit · Discussion #3138</a></h3> + + <p>@sea-bass @nbbrooks I believe a question was briefly asked at the Maintainer Meeting yesterday regarding what versions of Moveit 2 tend to be used. I thought it might be interesting to raise a poll...</p> + + + </article> + + <div class="onebox-metadata"> + + + </div> + + <div style="clear: both;"></div> +</aside> + + <p><small>1 post - 1 participant</small></p> + <p><a href="https://discourse.ros.org/t/what-versions-of-moveit-2-are-people-using/40908">Read full topic</a></p> + 2024-12-01T23:36:10+00:00 + TSNoble + + + ROS Discourse General: Interoperability Interest Group December 05, 2024: Use Cases Around Open-RMF and Interoperability by Reply + https://discourse.ros.org/t/interoperability-interest-group-december-05-2024-use-cases-around-open-rmf-and-interoperability-by-reply/40868 + <p><a href="https://github.com/osrf-sig-interoperability/community" rel="noopener nofollow ugc">Community Page </a></p> +<p><a href="https://openrobotics-org.zoom.us/j/82222141986?pwd=30wAfBwxIQ66O12HslQVvBziGxPmJ0.1" rel="noopener nofollow ugc">Meeting Link </a></p> +<p><a href="https://calendar.google.com/calendar/u/0/embed?src=agf3kajirket8khktupm9go748@group.calendar.google.com" rel="noopener nofollow ugc">Calendar Link </a></p> +<p><span class="discourse-local-date">2024-12-05T15:00:00Z UTC</span></p> +<p>This month our friends from <a href="https://www.reply.com/en" rel="noopener nofollow ugc">Reply</a> will be presenting on work that they’ve been doing on robotics system integration using Open-RMF.</p> + <p><small>2 posts - 2 participants</small></p> + <p><a href="https://discourse.ros.org/t/interoperability-interest-group-december-05-2024-use-cases-around-open-rmf-and-interoperability-by-reply/40868">Read full topic</a></p> + 2024-11-28T15:23:19+00:00 + grey + + + ROS Discourse General: Missing documentation for sensors? + https://discourse.ros.org/t/missing-documentation-for-sensors/40858 + <p>Hey guys, I just migrated from ROS1 to ROS2 and I am running ROS2 Humble Hawksbill with Gazebo Harmonic (ik it’s not the default installation but yeah I pulled Harmonic separately). I am working on a basic project to bring a robot present in my academia to gazebo and I noticed that there is close to no documentation about the list of sensors and how to use them in our xacro files. There is some basic introduction <a href="https://gazebosim.org/docs/harmonic/sensors/">here</a>. But I don’t see any list of sensors and how to use them anywhere. Does this call for creating a well-defined documentation or am I really missing any website?</p> + <p><small>13 posts - 9 participants</small></p> + <p><a href="https://discourse.ros.org/t/missing-documentation-for-sensors/40858">Read full topic</a></p> + 2024-11-28T07:09:17+00:00 + vishcomestrue + + + ROS Discourse General: OSRF Holiday Donation Drive + https://discourse.ros.org/t/osrf-holiday-donation-drive/40852 + <p></p><div class="lightbox-wrapper"><a class="lightbox" href="https://global.discourse-cdn.com/flex022/uploads/ros/original/3X/0/8/0886c02ebe7cf611b3d87c1a059892a4b6cb6610.jpeg" title="Thanksgiving"><img alt="Thanksgiving" height="388" src="https://global.discourse-cdn.com/flex022/uploads/ros/optimized/3X/0/8/0886c02ebe7cf611b3d87c1a059892a4b6cb6610_2_690x388.jpeg" width="690" /></a></div><p></p> +<p>Hi Everyone,</p> +<p>Just a quick note before everyone heads off for the long holiday weekend here in the States. Next Tuesday is Giving Tuesday in the US, a day when many people make their big charitable donations for the holiday season.</p> +<p>This year, we’ve set up a <a href="https://donorbox.org/open-robotics-giving-tuesday-2024">donations page for the Open Source Robotics Foundation (OSRF)</a> where you can specifically designate how you’d like your donation to be used. Want to help fund our infrastructure costs? Improve the ROS documentation? Support our educational efforts like the Diversity Scholars Program? Now you can choose!</p> +<p>We’re always thankful for your support, whether it’s monetary or a quick pull request! And remember, the OSRF is a 501(c)(3) tax-deductible charitable organization in the US.</p> +<p>If you, your colleagues, or your employer would like to support the OSRF and its mission, you can make a <a href="https://donorbox.org/open-robotics-giving-tuesday-2024">one-time or monthly donation using the new page</a>. Many employers match charitable donations during the holiday season, so be sure to check if yours does. Here at Intrinsic, we’ve used our employee match program to raise almost $15,000 for the OSRF. We’d love to see other members of the ROS community join the effort.</p> +<p>Finally, please help us spread the word! Our Open Robotics community is huge, and if we all pitched in just a little bit we could make some amazing things happen in 2025.</p> +<p>Thank you for your support, and have a wonderful holiday season! <img alt=":turkey:" class="emoji" height="20" src="https://emoji.discourse-cdn.com/twitter/turkey.png?v=12" title=":turkey:" width="20" /></p> + <p><small>4 posts - 4 participants</small></p> + <p><a href="https://discourse.ros.org/t/osrf-holiday-donation-drive/40852">Read full topic</a></p> + 2024-11-27T23:08:07+00:00 + Katherine_Scott + + + diff --git a/rss20.xml b/rss20.xml new file mode 100644 index 00000000..6643e921 --- /dev/null +++ b/rss20.xml @@ -0,0 +1,1515 @@ + + + + + Planet ROS + http://planet.ros.org + en + Planet ROS - http://planet.ros.org + + + ROS Discourse General: Is there a ROS 2 gazebo project for humanoids robots? + discourse.ros.org-topic-41094 + https://discourse.ros.org/t/is-there-a-ros-2-gazebo-project-for-humanoids-robots/41094 + <p>Dear ROS community,</p> +<p>I was researching if there are ROS 2 Gazebo project for humanoid robots that would facilitate in learning robot locomotion and whole-body motion planning. I am looking towards humanoids similar to Unitree’s H1/H2.</p> +<p>A research scientist from ETH Zurich pointed me to the Issac Gym environment that comes with the assets for H1/H2. But as far as I understand, that simulation pipeline does not use any ROS, and is meant for RL like research.</p> +<p>The closet project I found was Unitree’s ROS 1 project <a class="inline-onebox" href="https://github.com/unitreerobotics/unitree_ros" rel="noopener nofollow ugc">GitHub - unitreerobotics/unitree_ros</a> but it has not been updated for the newer ROS 2 and Gazebo.</p> +<p>Thank you for your time.</p> +<p>With best,<br /> +Azmyin</p> + <p><small>2 posts - 2 participants</small></p> + <p><a href="https://discourse.ros.org/t/is-there-a-ros-2-gazebo-project-for-humanoids-robots/41094">Read full topic</a></p> + Sun, 15 Dec 2024 05:41:56 +0000 + + + ROS Discourse General: Opinion on companies still using ROS1 + discourse.ros.org-topic-41079 + https://discourse.ros.org/t/opinion-on-companies-still-using-ros1/41079 + <p>I would like to read what you think about taking a Job in companies who work extensively with ROS, but for one reason or another they are still in ROS1.<br /> +On one hand I realize that ROS is just a framework and that a lot can still be done and learned.<br /> +On the other, having worked for some years on both ROS and ROS2 I see the benefits of working with ROS2.<br /> +So I am torn and would like to hear other voices on the matter.</p> + <p><small>6 posts - 4 participants</small></p> + <p><a href="https://discourse.ros.org/t/opinion-on-companies-still-using-ros1/41079">Read full topic</a></p> + Fri, 13 Dec 2024 22:48:13 +0000 + + + ROS Discourse General: ROS News for the Week of December 9th, 2024 + discourse.ros.org-topic-41073 + https://discourse.ros.org/t/ros-news-for-the-week-of-december-9th-2024/41073 + <h1><a class="anchor" href="https://discourse.ros.org#p-88510-ros-news-for-the-week-of-december-9th-2024-1" name="p-88510-ros-news-for-the-week-of-december-9th-2024-1"></a>ROS News for the Week of December 9th, 2024</h1> +<br /> +<p></p><div class="lightbox-wrapper"><a class="lightbox" href="https://global.discourse-cdn.com/flex022/uploads/ros/original/3X/f/3/f3d9d5342b7374ac0526df78b067dad56b1f0bee.jpeg" title="image"><img alt="image" height="345" src="https://global.discourse-cdn.com/flex022/uploads/ros/original/3X/f/3/f3d9d5342b7374ac0526df78b067dad56b1f0bee.jpeg" width="517" /></a></div><br /> +<img alt=":cn:" class="emoji" height="20" src="https://emoji.discourse-cdn.com/twitter/cn.png?v=12" title=":cn:" width="20" /> <img alt=":tada:" class="emoji" height="20" src="https://emoji.discourse-cdn.com/twitter/tada.png?v=12" title=":tada:" width="20" /> Our first ever ROSCon in China happened in Shanghai over the weekend! We want to congratulate the organizers on orchestrating such an impressive event. <a href="https://discourse.ros.org/t/roscon-china-2024-more-than-200-robotics-companies-participated/41029">You can find a recap of ROSCon China here.</a><br /> +<br /><p></p> +<p></p><div class="lightbox-wrapper"><a class="lightbox" href="https://global.discourse-cdn.com/flex022/uploads/ros/original/3X/c/7/c7be912533f5142c58a62011a97ee7b766602b37.jpeg" title="May 2023 - Nov 2024"><img alt="May 2023 - Nov 2024" height="194" src="https://global.discourse-cdn.com/flex022/uploads/ros/optimized/3X/c/7/c7be912533f5142c58a62011a97ee7b766602b37_2_345x194.jpeg" width="345" /></a></div><br /> +<a href="https://discourse.ros.org/t/iron-irwini-is-end-of-life/41031/2">ROS 2 Iron Irwini is now officially end-of-life</a>. If you are currently using Iron please consider upgrading to Jazzy!<p></p> +<br /> +<p><img alt="harp2" class="animated" height="136" src="https://global.discourse-cdn.com/flex022/uploads/ros/original/3X/e/4/e412077900cd1e52fab01fd99a57208448f0e4ef.gif" width="240" /><br /> +Check out the <a href="https://robotcopper.github.io/HARP/HARP2.html">HARP2 robot</a> that was posted to the ROS Discord server yesterday. The developer’s website is full of really great posts that are worth checking out, especially on the topic of microROS.</p> +<br /> +<p></p><div class="lightbox-wrapper"><a class="lightbox" href="https://global.discourse-cdn.com/flex022/uploads/ros/original/3X/1/3/136cf3f23f025849b44bb6bcc52f45998bf87e98.jpeg" title="poster-thumbnail"><img alt="poster-thumbnail" height="243" src="https://global.discourse-cdn.com/flex022/uploads/ros/optimized/3X/1/3/136cf3f23f025849b44bb6bcc52f45998bf87e98_2_345x243.jpeg" width="345" /></a></div><br /> +<a href="https://tidybot2.github.io/">The team behind TidyBot2</a> at Stanford and Princeton have open sourced the hardware for their robot. The robot supports a variety of arms and configurations allowing you to build a clone using hardware you may already have in the lab. See the <a href="https://tidybot2.github.io/docs/">docs</a> for more details.<p></p> +<br /> +<p></p><div class="lightbox-wrapper"><a class="lightbox" href="https://global.discourse-cdn.com/flex022/uploads/ros/original/3X/2/1/216a2ac455603652fbda5952ec9661defc9d6bd5.png" title="image"><img alt="image" height="250" src="https://global.discourse-cdn.com/flex022/uploads/ros/optimized/3X/2/1/216a2ac455603652fbda5952ec9661defc9d6bd5_2_280x250.png" width="280" /></a></div><br /> +This week <a href="https://rosindustrial.org/3d-camera-survey">ROS Industrial</a> released a comprehensive list of depth cameras for robotics applications. Even if you don’t need a new depth camera I recommend bookmarking this website for future website.<p></p> +<br /> +<p></p><div class="lightbox-wrapper"><a class="lightbox" href="https://global.discourse-cdn.com/flex022/uploads/ros/original/3X/6/9/6952c4de9dae5cdfea47cd10bb075cd8502088f4.png" title="image"><img alt="image" height="250" src="https://global.discourse-cdn.com/flex022/uploads/ros/optimized/3X/6/9/6952c4de9dae5cdfea47cd10bb075cd8502088f4_2_274x250.png" width="274" /></a></div><br /> +I want to send a big shout out <a class="mention" href="https://discourse.ros.org/u/abaeyens">@abaeyens</a> for putting together this fantastic documentation on <a href="https://docs.ros.org/en/rolling/Tutorials/Intermediate/Testing/Integration.html">ROS 2 integration testing</a> for <a href="http://docs.ros.org">docs.ros.org</a>. <img alt=":tada:" class="emoji" height="20" src="https://emoji.discourse-cdn.com/twitter/tada.png?v=12" title=":tada:" width="20" /><p></p> +<p>People often ask us how they can best contribute to the project. My recommendation is that when you run across something that feels not poorly documented take the time to summarize what you learned while figuring out how to solve the problem. <a href="https://discourse.ros.org/t/towards-a-rosdoc-integation-testing-tutorial/40701">That’s exactly what @abaeyens<br /> +did in this case and the results are excellent</a>.</p> +<br /> +<h1><a class="anchor" href="https://discourse.ros.org#p-88510-events-2" name="p-88510-events-2"></a>Events</h1> +<ul> +<li><a href="https://firahackathon.github.io/">2024-12-15 FIRA Ag Robotics Hackathon Registration Deadline</a></li> +<li><a href="https://autodrive-ecosystem.github.io/competitions/f1tenth-sim-racing-cdc-2024/">2024-12-16 =&gt; 2024-12-19 F1Tenth Sim Racing League at CDC 2024</a></li> +<li><a href="https://discourse.ros.org/t/aerial-robotics-meeting-xmas-with-bitcraze-dec-18-2024/40951">2024-12-18 Aerial Robotics meeting - Xmas with Bitcraze</a></li> +<li><a href="https://docs.google.com/forms/d/e/1FAIpQLSeiuWtUClyQ2Aj-CBFwZacpfL9xxgG_ZA8ImF0SF9sT2-sqKA/viewform">2024-12-22 Open Hardware Summit CFP Deadline</a></li> +<li><a href="https://www.naturalroboticscontest.com/">2024-12-31 Deadline for Natural Robotics Contest</a></li> +<li><a href="https://fosdem.org/2025/">2025-02-01 FOSDEM 25</a> – <a href="https://discourse.ros.org/t/fosdem-2025-robotics-simulation-first-edition/40349">See Robotics and Sim Room</a></li> +<li><a href="https://world-fira.com/">2025-02-04 =&gt; 2025-02-06 World FIRA Ag Robotics Conference in Toulouse, France</a></li> +<li><a href="https://discourse.ros.org/t/7th-international-workshop-on-robotics-software-engineering/39901">2025-04-28 International Workshop on Robotics Software Engineering</a></li> +<li><a href="https://2025.oshwa.org/">2025-05-30 =&gt; 2025-05-31 2025 Open Hardware Summit in Edinburgh</a></li> +</ul> +<h1><a class="anchor" href="https://discourse.ros.org#p-88510-news-3" name="p-88510-news-3"></a>News</h1> +<ul> +<li><a href="https://discourse.ros.org/t/roscon-china-2024-more-than-200-robotics-companies-participated/41029">ROSCon China 2024</a></li> +<li><a href="https://discourse.ros.org/t/ros-pmc-meeting-minutes-2024-12-10/41040">ROS PMC Meeting Minutes 2024-12-10</a></li> +<li><a href="https://www.ieee-ras.org/publications/ra-p">IEEE Robotics and Automation Society Launches new Journal</a></li> +<li><a href="https://discourse.ros.org/t/we-seek-for-your-feedback-to-shape-the-future-of-autoware/41038">We seek for your feedback to shape the future of Autoware!</a></li> +<li><a href="https://discourse.ros.org/t/how-important-is-ros-when-searching-for-a-job/41032">How important is ROS when searching for a job?</a></li> +<li><a href="https://techcrunch.com/2024/12/12/rip-cruise-robotaxi/">RIP, Cruise robotaxi</a>– <a href="https://www.therobotreport.com/gm-will-no-longer-fund-cruise-robotaxi-development/">The Robot Report</a></li> +<li><a href="https://www.therobotreport.com/diligent-robotics-new-ai-advisory-board-advance-embodied-ai-healthcare-robotics/">Diligent Robotics’ new AI Advisory Board to advance embodied AI in healthcare robotics</a></li> +<li><a href="https://techcrunch.com/2024/12/12/anybotics-raises-60m-to-scale-autonomous-industrial-robots-in-the-u-s/">Anybotics raises $60M to bring more autonomous industrial robots to the US</a></li> +<li><a href="https://techcrunch.com/2024/12/05/amp-robotics-raises-91m-to-build-more-robot-filled-waste-sorting-facilities/">Amp Robotics raises $91M to build more robot-filled waste-sorting facilities</a></li> +<li><a href="https://spectrum.ieee.org/fei-fei-li-world-labs">AI Pioneer Fei-Fei Li Has a Vision for Computer Vision</a></li> +<li><a href="https://spectrum.ieee.org/ai-safety">OpenAI, GoogleDeepMind, and Meta Get Bad Grades on AI Safety</a></li> +<li><a href="https://spectrum.ieee.org/video-friday-mars-chopper">Robot Videos: Mars Helicopter, Sanctuary AI, and More</a></li> +<li><a href="https://discourse.ros.org/t/safe-dds-achieves-iso-26262-asil-d-certification/41036">Safe DDS Achieves ISO 26262 ASIL D Certification</a></li> +<li><a href="https://discourse.ros.org/t/call-for-ifr-s-women-in-robotics-10-women-shaping-the-future-of-robotics-in-2025-is-now-open/41068">Call for “IFR’s Women in Robotics: 10 Women Shaping the Future of Robotics in 2025” is now open</a></li> +<li><a href="https://www.ieee-ras.org/about-ras/latest-news/call-students-participating-in-ieee-robotic-standardization-efforts-spirse">Grant for Students Participating in IEEE Robotic Standardization Efforts (SPIRSE)</a></li> +<li><a href="https://discourse.ros.org/t/robotics-engineers-are-in-high-demand-but-what-is-the-job-really-like/41015">Robotics engineers are in high demand — but what is the job really like?</a></li> +<li><a href="https://discourse.ros.org/t/interest-for-a-south-florida-ros-users-group/41008/2">Interest for a South Florida ROS Users Group?</a></li> +<li><a href="https://www.youtube.com/watch?v=kKCU3DM8PT0">Video: Kids Train Their Own AI-Powered Robot</a></li> +<li><a href="https://www.youtube.com/watch?v=oMIzIRqv1e0">Annual FZI Xmas Video</a></li> +<li><a href="https://www.space.com/the-universe/jupiter/nasa-tests-high-tech-software-for-future-mission-to-search-for-life-on-jupiters-moon-europa">NASA tests high-tech software for future mission to search for life on Jupiter’s moon Europa</a></li> +<li><a href="https://www.mccormick.northwestern.edu/robotics/inside-our-program/stories/2024/navigating-hazardous-terrain-at-nasas-jet-propulsion-laboratory.html">Navigating Hazardous Terrain at NASA’s Jet Propulsion Laboratory</a></li> +<li><a href="https://www.youtube.com/watch?v=_U0IYuIWwqk">ELISA Workshop at NASA Goddard, Washington, D.C.</a></li> +<li><a href="https://github.com/Robertleoj/pen_plotter_robot/blob/main/story.md">Pen Plotter Robot Build</a></li> +</ul> +<h1><a class="anchor" href="https://discourse.ros.org#p-88510-ros-4" name="p-88510-ros-4"></a>ROS</h1> +<ul> +<li><a href="https://discourse.ros.org/t/iron-irwini-is-end-of-life/41031/2">Iron Irwini is End-of-Life</a></li> +<li><a href="https://discourse.ros.org/t/quik-a-ultra-fast-and-robust-generalized-inverse-kinematics-solver-for-c-ros2/41024/4">QuIK: A ultra-fast and robust generalized inverse kinematics solver for C++/ROS2</a></li> +<li><a href="https://discourse.ros.org/t/towards-a-rosdoc-integation-testing-tutorial/40701/4">Towards a ROSdoc integation testing tutorial</a> – <a href="https://docs.ros.org/en/rolling/Tutorials/Intermediate/Testing/Integration.html">Docs link</a></li> +<li><a href="https://discourse.ros.org/t/gazebo-garden-officially-end-of-life-x-post-gazebo-sim-community/41044"><img alt=":checkered_flag:" class="emoji" height="20" src="https://emoji.discourse-cdn.com/twitter/checkered_flag.png?v=12" title=":checkered_flag:" width="20" /> Gazebo Garden officially end-of-life</a></li> +<li><a href="https://discourse.ros.org/t/extending-urdf-to-include-physical-interfaces-plugs-and-computing-component-e-g-control-boxes/41061">Extending URDF to include physical interfaces (plugs) and computing components (e.g., control boxes)</a></li> +<li><a href="https://discourse.ros.org/t/ros-2-rust-meeting-december-2024/40991">ROS 2 Rust Meeting: December 2024</a></li> +<li><a href="https://duckietown.com/monocular-navigation-in-duckietown-using-lednet-architecture/?utm_campaign=Student%27s%20Project&amp;utm_content=318875713&amp;utm_medium=social&amp;utm_source=twitter&amp;hss_channel=tw-991690269975371776">Monocular Navigation in Duckietown Using LEDNet Architecture</a></li> +<li><a href="https://github.com/SYSU-STAR/SOAR">IROS 2024: Simultaneous Exploration and Photographing with Heterogeneous UAVs for Fast Autonomous Reconstruction</a></li> +<li><a href="https://rosindustrial.org/3d-camera-survey"><img alt=":cool:" class="emoji" height="20" src="https://emoji.discourse-cdn.com/twitter/cool.png?v=12" title=":cool:" width="20" /> ROS Industrial 3D Camera Survey</a></li> +<li><a href="https://github.com/bdaiinstitute/proto2ros">Protobuf / ROS 2 interoperability layer</a></li> +<li><a href="https://github.com/tier4/umber_dds">DDS but in Rust</a></li> +<li><a href="https://github.com/sparolab/referee">ReFeree: Radar-based Lightweight and Robust Localization using Feature and Free space.</a></li> +<li><a href="https://github.com/xieyuser/GS-LIVM">GS-LIVM: Real-Time Photo-Realistic LiDAR-Inertial-Visual Mapping with Gaussian Splatting</a></li> +<li><a href="https://github.com/yorklyb/L-PR">Exploiting LiDAR Fiducial Marker for Unordered Low Overlap Multiview Point Cloud Registration</a></li> +<li><a href="https://arxiv.org/abs/2412.03887">MOANA: Multi-Radar Dataset for Maritime Odometry and Autonomous Navigation Application</a> – <a href="https://sites.google.com/corp/view/rpmmoana/">MOANA Dataset</a></li> +<li><a href="https://www.youtube.com/live/ithYYtUduMQ">Video: Articulation Rigging with ROS 2 Bridge</a></li> +<li><a href="https://github.com/ywyeli/UniDrive">UniDrive: Towards Universal Driving Perception Across Camera Configurations</a></li> +<li><a href="https://www.youtube.com/watch?v=B0fMZHYs_Vc">Video: Zenoh User Meeting 2024</a></li> +<li><a href="https://qiita.com/Ninagawa123/items/c4643ca92e57c3a45efb">URDF kitchen: A powerful GUI to help you create URDFs</a></li> +<li><a href="https://tidybot2.github.io/">TidyBot++: An Open-Source Holonomic Mobile Manipulator for Robot Learning</a> – <a href="https://tidybot2.github.io/docs/">docs</a></li> +<li><a href="https://github.com/Chyaru/Keyboard-controller-for-ROS2">Keyboard Controller for ROS 2</a></li> +<li><a href="https://github.com/danielpmorton/cbfpy/">Control Barrier Functions in Python and Jax</a> – <a href="https://danielpmorton.github.io/cbfpy/">docs</a></li> +<li><a href="https://github.com/Minipada/ros2_data_collection">Collect, validate and send data reliably from ROS 2 to create APIs and dashboards.</a></li> +<li><a href="https://arxiv.org/abs/2412.03760">Large-Scale Dense 3D Mapping Using Submaps Derived From Orthogonal Imaging Sonars</a></li> +<li><a href="https://robotcopper.github.io/HARP/HARP2.html">HARP2 Holonomic Robot</a></li> +<li><a href="https://github.com/pojenwang/Space-ROS-Isaac-Sim/">Space ROS Isaac Sim</a></li> +</ul> +<h1><a class="anchor" href="https://discourse.ros.org#p-88510-got-a-minute-alarm_clock-5" name="p-88510-got-a-minute-alarm_clock-5"></a>Got a minute? <img alt=":alarm_clock:" class="emoji" height="20" src="https://emoji.discourse-cdn.com/twitter/alarm_clock.png?v=12" title=":alarm_clock:" width="20" /></h1> +<p>All we want for Christmas are <a href="https://docs.ros.org/en/rolling/The-ROS2-Project/Contributing.html">pull requests to the ROS 2 docs</a>. <img alt=":gift:" class="emoji" height="20" src="https://emoji.discourse-cdn.com/twitter/gift.png?v=12" title=":gift:" width="20" /></p> + <p><small>1 post - 1 participant</small></p> + <p><a href="https://discourse.ros.org/t/ros-news-for-the-week-of-december-9th-2024/41073">Read full topic</a></p> + Fri, 13 Dec 2024 20:21:44 +0000 + + + ROS Discourse General: Call for “IFR’s Women in Robotics: 10 Women Shaping the Future of Robotics in 2025” is now open + discourse.ros.org-topic-41068 + https://discourse.ros.org/t/call-for-ifr-s-women-in-robotics-10-women-shaping-the-future-of-robotics-in-2025-is-now-open/41068 + <h1><a class="anchor" href="https://discourse.ros.org#p-88501-call-for-ifrs-women-in-robotics-10-women-shaping-the-future-of-robotics-in-2025-is-now-open-1" name="p-88501-call-for-ifrs-women-in-robotics-10-women-shaping-the-future-of-robotics-in-2025-is-now-open-1"></a>Call for “IFR’s Women in Robotics: 10 Women Shaping the Future of Robotics in 2025” is now open</h1> +<h3><a class="anchor" href="https://discourse.ros.org#p-88501-the-international-federation-of-robotics-ifrhttpsifrorgifr-press-releasesnewscall-ifr-women-in-robotics-2025-is-looking-for-outstanding-women-in-robotics-2" name="p-88501-the-international-federation-of-robotics-ifrhttpsifrorgifr-press-releasesnewscall-ifr-women-in-robotics-2025-is-looking-for-outstanding-women-in-robotics-2"></a>The International Federation of Robotics (<a href="https://ifr.org/ifr-press-releases/news/call-ifr-women-in-robotics-2025" rel="noopener nofollow ugc">IFR</a>) is looking for outstanding women in robotics</h3> +<p><em>Dec 10, 2024 —</em> IFR would like to highlight and honor Women in Robotics - in particular women in the robotics industry - and give them more visibility. IFR will select a list of 10 women to officially award as “IFR’s Women in Robotics: 10 Women Shaping the Future of Robotics” in 2025.</p> +<p></p><div class="lightbox-wrapper"><a class="lightbox" href="https://global.discourse-cdn.com/flex022/uploads/ros/original/3X/9/6/96ba7ad97a9382cdf82718e435234cba6964a291.jpeg" rel="noopener nofollow ugc" title=""><img alt="" height="388" src="https://global.discourse-cdn.com/flex022/uploads/ros/optimized/3X/9/6/96ba7ad97a9382cdf82718e435234cba6964a291_2_690x388.jpeg" width="690" /></a></div><p></p> +<p>IFR decided to <strong>give women in robotics more visibility and acknowledgment</strong>. This should inspire girls and young women to pursue a career in STEM subjects or robotics and will also help companies to reach gender equality and overcome shortage of staff.</p> +<p>IFR would like to highlight and honor Women in Robotics - in particular women in the robotics industry - and give them more visibility.<br /> +IFR will select a list of 10 women to officially award as “IFR’s Women in Robotics: 10 Women Shaping the Future of Robotics” in 2025.</p> +<p><strong>IRF is in particular looking for women that have either a proven track record in robotics, stand out as industry leader or women with a proven activity in encouraging young people to go into STEM or that somehow support females in robotics.</strong></p> +<p><em>Deadline for submission is January 31st, 2025.</em></p> +<h3><a class="anchor" href="https://discourse.ros.org#p-88501-how-to-submit-a-suggestion-3" name="p-88501-how-to-submit-a-suggestion-3"></a>How to submit a suggestion</h3> +<p>Send an email to <a href="mailto:secretariat@ifr.org">secretariat@ifr.org</a><br /> +include a <strong>short bio</strong> and a description of <strong>what makes her noteworthy or particular</strong> with respect to our described scope<br /> +add her full name, affiliation, country, contact details and a photo</p> +<h3><a class="anchor" href="https://discourse.ros.org#p-88501-selection-criteria-4" name="p-88501-selection-criteria-4"></a>Selection criteria:</h3> +<ul> +<li>The suggested women needs to be active in the robotics industry</li> +<li>IFR will select at least one per continent,</li> +<li>but a maximum of one woman per company,</li> +<li>consider different company sizes (large, medium, small)</li> +<li>consider different company scope (Robot supplier IR, SR, component supplier, integrator) and</li> +<li>consider different levels of hierarchy (C-level, intermediate, lower level)</li> +<li>Proven track record in robotics / stand out as industry leader</li> +<li>Proven activity in encouraging young people to go into STEM or that somehow support females in robotics</li> +</ul> +<p><strong>Publication of results</strong> will be on International Women’s Day - March 8th, 2025.</p> +<p><a href="https://ifr.org/ifr-press-releases/news/10-women-shaping-the-future-of-robotics-2024" rel="noopener nofollow ugc">IFR’s 2024 Women in Robotics</a></p> +<p>Learn more on <a href="https://ifr.org/ifr-press-releases/news/world-bank-predicts-20-economic-boost-by-closing-gender-gap" rel="noopener nofollow ugc">why gender balance is beneficial for economies</a></p> +<ul> +<li><a href="https://ifr.org/img/office/IFR_Women_in_Robotics_Call2025.pdf" rel="noopener nofollow ugc"> IFR Women in Robotics: 2025 Call for nominations (576KB)</a></li> +</ul> + <p><small>1 post - 1 participant</small></p> + <p><a href="https://discourse.ros.org/t/call-for-ifr-s-women-in-robotics-10-women-shaping-the-future-of-robotics-in-2025-is-now-open/41068">Read full topic</a></p> + Fri, 13 Dec 2024 08:38:12 +0000 + + + ROS Discourse General: REUSE compatibility vs multi-package repo + discourse.ros.org-topic-41063 + https://discourse.ros.org/t/reuse-compatibility-vs-multi-package-repo/41063 + <p>Hi. I’ve started trying to have my repos <a href="https://reuse.software/spec-3.2/" rel="noopener nofollow ugc">REUSE-compliant</a>.</p> +<p>It seems that single-package repos can easily be turned into REUSE-compliant by adding all the SPDX comments to files, moving the top-level <code>LICENSE</code> file into <code>LICENSES/BSD-3-Clause.txt</code> and specifying <code>&lt;license file="LICENSES/BSD-3-Clause.txt"&gt;BSD&lt;/license&gt;</code> in <code>package.xml</code>.</p> +<p>However, if I want to do the same for a multi-package repo, then the <code>LICENSES</code> folder has to be a top-level one, i.e. at the same level as are the packages (that is a REUSE requirement). At the same time, I’d like to not have to copy all licenses to each package - as it’s best if each is stored only once. However, if I put <code>&lt;license file="../LICENSES/BSD-3-Clause.txt"&gt;</code> in <code>package.xml</code>, then <code>bloom-release</code> fails not being able to find the license file. That’s because it builds each package from the repo in a separate directory that is moved outside the repo.</p> +<p>I don’t see a clean solution how to satisfy both REUSE and bloom (except not adding the <code>file=</code> attribute, but I’d like to keep it). My current dirty workaround is to just copy the license file into the root of each subpackage. That’s not nice, but it does the job.</p> +<p>Does anybody know of a cleaner solution? I think it would be very nice if ROS deployment process would be compatible with REUSE.</p> + <p><small>5 posts - 3 participants</small></p> + <p><a href="https://discourse.ros.org/t/reuse-compatibility-vs-multi-package-repo/41063">Read full topic</a></p> + Thu, 12 Dec 2024 15:19:10 +0000 + + + ROS Discourse General: Optimizations cpp ROS2 node. colcon build + discourse.ros.org-topic-41048 + https://discourse.ros.org/t/optimizations-cpp-ros2-node-colcon-build/41048 + <p>I’ve been using ROS2 for a year. Maybe previously you guys talked about this. However I’ve done experimental tests about the optimization C++ code ROS2 node and wrote a simple node.</p> +<pre><code class="lang-auto">#include "rclcpp/rclcpp.hpp" + +class HelloWorldNode : public rclcpp::Node +{ +public: + HelloWorldNode() : Node("hello_world_node") + { + RCLCPP_INFO(this-&gt;get_logger(), "Hello, World! This is a ROS2 node."); + } +}; + +int main(int argc, char **argv) +{ + rclcpp::init(argc, argv); + rclcpp::spin(std::make_shared&lt;HelloWorldNode&gt;()); + rclcpp::shutdown(); + return 0; +} + +</code></pre> +<p>Then by simply building the above code by using</p> +<pre><code class="lang-auto">colcon build +</code></pre> +<p>I got hello_node then explored assemble code</p> +<pre><code class="lang-auto">objdump -d &lt;path&gt;/hello_node &gt; hello_node.asm +</code></pre> +<p>got around 5000 lines of instruction code in hello_node.asm, it seems like it didn’t do any optimization to the code. Then run the following command</p> +<pre><code class="lang-auto">colcon build --cmake-args -DCMAKE_BUILD_TYPE=Release +///alternative +colcon build --cmake-args -DCMAKE_CXX_FLAGS="-O3 -march=native" + +</code></pre> +<p>then looked number instructions lines the number dramatically decreased from 5000 to 1700. the number of instruction lines in assemble doesn’t always mean it’s optimized yet it’s good factor.</p> +<p></p><div class="lightbox-wrapper"><a class="lightbox" href="https://global.discourse-cdn.com/flex022/uploads/ros/original/3X/6/8/68451cf4ffb2af3503e805517c6f42c1c297c70c.jpeg" rel="noopener nofollow ugc" title="Screenshot from 2024-12-11 16-24-11"><img alt="Screenshot from 2024-12-11 16-24-11" height="388" src="https://global.discourse-cdn.com/flex022/uploads/ros/optimized/3X/6/8/68451cf4ffb2af3503e805517c6f42c1c297c70c_2_690x388.jpeg" width="690" /></a></div><p></p> +<p>“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”“”"<br /> +simple by adding “set(CMAKE_BUILD_TYPE Release)” to your CMakeLists.txt is enough. then you can simply use colcon build.<br /> +<a href="https://gcc.gnu.org/onlinedocs/gcc/Optimize-Options.html" rel="noopener nofollow ugc">Optimizations flags</a></p> + <p><small>8 posts - 7 participants</small></p> + <p><a href="https://discourse.ros.org/t/optimizations-cpp-ros2-node-colcon-build/41048">Read full topic</a></p> + Wed, 11 Dec 2024 08:32:38 +0000 + + + ROS Discourse General: :checkered_flag: Gazebo Garden officially end-of-life [x-post Gazebo Sim Community] + discourse.ros.org-topic-41044 + https://discourse.ros.org/t/gazebo-garden-officially-end-of-life-x-post-gazebo-sim-community/41044 + <p><a href="https://community.gazebosim.org/t/gazebo-garden-officially-end-of-life/3278">Original Post</a></p> +<p>Dear ROS Community,</p> +<p>Gazebo Garden has reached end-of-life (EOL) as of November, 2024. Garden was <a href="https://community.gazebosim.org/t/gazebo-garden-release/1627">the seventh major release</a> of Gazebo and was supported for two years (non-LTS). It was the first release where Ignition was renamed Gazebo. It also introduced various exciting features, including custom shader plugins, Reset API, DEM support, lunar and custom surface coordinates, glTF and GLB mesh support, and an acoustic communication plugin, just to name a few. See the entire list of features on the <a href="https://gazebosim.org/docs/latest/release-features/#garden">Release Features page</a>.</p> +<p>We recommend all Garden users migrate to a supported release as soon as possible, such as <a href="https://ignitionrobotics.org/docs/harmonic" rel="noopener nofollow ugc">Harmonic (LTS)</a> or <a href="https://ignitionrobotics.org/docs/ionic" rel="noopener nofollow ugc">Ionic</a>, which are paired with ROS Jazzy and Rolling (Kilted once released) respectively. Migrating to either Harmonic or Ionic should be fairly smooth, however, be sure to check the release highlights for <a href="https://github.com/gazebosim/gz-harmonic/blob/main/highlights.md" rel="noopener nofollow ugc">Harmonic</a> and <a href="https://github.com/gazebosim/gz-ionic/blob/main/highlights.md" rel="noopener nofollow ugc">Ionic</a> in addition to checking each Gazebo library’s migration guide.</p> +<p>As part of the Garden EOL, the following Gazebo libraries have also reached end-of-life. Their latest released binaries will remain available at <a href="http://packages.osrfoundation.org/">http://packages.osrfoundation.org/</a>, but no more fixes or releases will be made.</p> +<div class="md-table"> +<table> +<thead> +<tr> +<th style="text-align: left;">Library major version</th> +<th style="text-align: left;">Final release</th> +</tr> +</thead> +<tbody> +<tr> +<td style="text-align: left;">gz-fuel-tools8</td> +<td style="text-align: left;">8.2.0</td> +</tr> +<tr> +<td style="text-align: left;">gz-sim7</td> +<td style="text-align: left;">7.9.0</td> +</tr> +<tr> +<td style="text-align: left;">gz-gui7</td> +<td style="text-align: left;">7.2.2</td> +</tr> +<tr> +<td style="text-align: left;">gz-launch6</td> +<td style="text-align: left;">6.2.0</td> +</tr> +<tr> +<td style="text-align: left;">gz-msgs9</td> +<td style="text-align: left;">9.5.1</td> +</tr> +<tr> +<td style="text-align: left;">gz-physics6</td> +<td style="text-align: left;">6.7.0</td> +</tr> +<tr> +<td style="text-align: left;">gz-rendering7</td> +<td style="text-align: left;">7.5.0</td> +</tr> +<tr> +<td style="text-align: left;">gz-sensors7</td> +<td style="text-align: left;">7.3.1</td> +</tr> +<tr> +<td style="text-align: left;">gz-transport12</td> +<td style="text-align: left;">12.2.2</td> +</tr> +<tr> +<td style="text-align: left;">sdformat13</td> +<td style="text-align: left;">13.9.0</td> +</tr> +</tbody> +</table> +</div><p><strong>We sincerely thank all contributors to all libraries in Garden <img alt=":pray:" class="emoji" height="20" src="https://emoji.discourse-cdn.com/twitter/pray.png?v=12" title=":pray:" width="20" /></strong></p> +<h3><a class="anchor" href="https://discourse.ros.org#p-88451-what-does-end-of-life-mean-1" name="p-88451-what-does-end-of-life-mean-1"></a>What does End of Life Mean?</h3> +<p>Users often ask us, “what does end of life mean?” To put it briefly, end of life means that the Gazebo team will no longer support that particular Gazebo release. In practical terms, this means that we will no longer be providing the following for Gazebo Garden:</p> +<ul> +<li>New features or capabilities</li> +<li>Security updates</li> +<li>Bug fixes, patches or support</li> +<li>Updated binaries</li> +</ul> +<p>It is also worth noting the things that won’t change after Gazebo Garden goes end of life:</p> +<ul> +<li>Gazebo Garden binaries <em>will not</em> suddenly disappear</li> +<li>Users <em>will not need</em> to migrate immediately, but they should migrate as soon as possible</li> +</ul> +<p><img alt=":gazebo:" class="emoji emoji-custom" height="20" src="https://global.discourse-cdn.com/flex022/uploads/ros/original/2X/6/65ca80e7c1f76154e9158bb4ad6aeaa5b25968cb.png?v=12" title=":gazebo:" width="20" /> Gazebo Dev Team <img alt=":gazebo:" class="emoji emoji-custom" height="20" src="https://global.discourse-cdn.com/flex022/uploads/ros/original/2X/6/65ca80e7c1f76154e9158bb4ad6aeaa5b25968cb.png?v=12" title=":gazebo:" width="20" /></p> + <p><small>1 post - 1 participant</small></p> + <p><a href="https://discourse.ros.org/t/gazebo-garden-officially-end-of-life-x-post-gazebo-sim-community/41044">Read full topic</a></p> + Tue, 10 Dec 2024 23:14:24 +0000 + + + ROS Discourse General: How important is ROS when searching for a job? + discourse.ros.org-topic-41032 + https://discourse.ros.org/t/how-important-is-ros-when-searching-for-a-job/41032 + <p>I have made an analysis of almost 2.000 jobs in LinkedIn and found out how relevant is ROS for getting a job as a robotics software developer. I included other interesting data about what matters for companies posting robotics jobs.</p> +<p>Check all that data in this video: <a href="https://youtu.be/wDeVNsD73A4?si=wcD3F1FizuJ52K3e" rel="noopener nofollow ugc">https://youtu.be/wDeVNsD73A4?si=wcD3F1FizuJ52K3e</a></p> +<p></p><div class="lightbox-wrapper"><a class="lightbox" href="https://global.discourse-cdn.com/flex022/uploads/ros/original/3X/7/0/70948045f3d694c112973bfe5cf4c28a46c74e7f.jpeg" rel="noopener nofollow ugc" title="Podcast-video-2024-Ricardo-Tellez-the-truth-about-ROS-jobs"><img alt="Podcast-video-2024-Ricardo-Tellez-the-truth-about-ROS-jobs" height="388" src="https://global.discourse-cdn.com/flex022/uploads/ros/optimized/3X/7/0/70948045f3d694c112973bfe5cf4c28a46c74e7f_2_690x388.jpeg" width="690" /></a></div><p></p> + <p><small>1 post - 1 participant</small></p> + <p><a href="https://discourse.ros.org/t/how-important-is-ros-when-searching-for-a-job/41032">Read full topic</a></p> + Tue, 10 Dec 2024 08:43:25 +0000 + + + ROS Discourse General: Iron Irwini is End-of-Life + discourse.ros.org-topic-41031 + https://discourse.ros.org/t/iron-irwini-is-end-of-life/41031 + <p>Dear ROS Community,</p> +<p>It is bitter-sweet to announce that ROS 2 Iron Irwini is now end-of-life.</p> +<p></p><div class="lightbox-wrapper"><a class="lightbox" href="https://global.discourse-cdn.com/flex022/uploads/ros/original/3X/1/8/1844c68fbd9b3eb4e873ef39f2c57a7d0603b311.jpeg" rel="noopener nofollow ugc" title="ROS 2 Iron Irwini"><img alt="ROS 2 Iron Irwini" height="500" src="https://global.discourse-cdn.com/flex022/uploads/ros/optimized/3X/1/8/1844c68fbd9b3eb4e873ef39f2c57a7d0603b311_2_465x500.jpeg" width="465" /></a></div><p></p> +<p>Iron Irwini was released on May 23rd 2023 and marked the ninth distribution of ROS 2. Despite being a non-LTS release, it was feature packed (<a href="https://discourse.ros.org/t/ros-2-iron-irwini-released/">see more</a>).</p> +<p>Over the past year and half, there have been <a href="https://build.ros2.org/job/Irel_sync-packages-to-main/" rel="noopener nofollow ugc">40 distro syncs</a> and <a href="https://github.com/ros2/ros2/releases?q=iron&amp;expanded=true" rel="noopener nofollow ugc">7 patch releases</a> that cumulatively brought thousands of packages and updates to the community.</p> +<p>The <a href="https://github.com/ros2/ros2/releases/tag/release-iron-20241204" rel="noopener nofollow ugc">last patch</a> and sync (tagged <a href="https://github.com/ros/rosdistro/blob/iron/2024-12-04/iron/distribution.yaml" rel="noopener nofollow ugc"><code>iron/2024-12-04</code></a>) brought <strong>6</strong> new packages and <strong>320</strong> updates.</p> +Expand for details of the final sync <a href="https://discourse.ros.org/t/iron-irwini-is-end-of-life/41031/1">(click for more details)</a> +<p>The distribution has been marked end-of-life across <a href="http://docs.ros.org">docs.ros.org</a>, <a href="http://index.ros.org">index.ros.org</a> and <a href="https://github.com/ros/rosdistro" rel="noopener nofollow ugc">rosdistro</a>. CI and Buildfarm jobs have been disabled and will be deleted after a month assuming no issues crop up. The final snapshot of the distribution has been uploaded to <a href="http://snapshots.ros.org/iron/">snapshots.ros.org</a>. If you are currently using Iron, please switch to <a href="https://docs.ros.org/en/jazzy/">Jazzy Jalisco</a> which is the latest LTS release. The transition should be very smooth.</p> +<p>It has been a great privilege of mine to serve as the ROS Boss for Iron Irwini especially given that Steve Irwin was my childhood hero. A big thank you to all ROS maintainers and community members for making Iron Irwini such a successful release! <img alt=":iron:" class="emoji emoji-custom" height="20" src="https://global.discourse-cdn.com/flex022/uploads/ros/original/3X/b/3/b3c1340fc185f5e47c7ec55ef5bb1771802de993.png?v=12" title=":iron:" width="20" /> <img alt=":irwini:" class="emoji emoji-custom" height="20" src="https://global.discourse-cdn.com/flex022/uploads/ros/original/3X/d/2/d2f3dcbdaff6f33258719fe5b8f692594a9feab0.png?v=12" title=":irwini:" width="20" /></p> +<p>-Yadu</p> + <p><small>2 posts - 2 participants</small></p> + <p><a href="https://discourse.ros.org/t/iron-irwini-is-end-of-life/41031">Read full topic</a></p> + Tue, 10 Dec 2024 07:36:47 +0000 + + + ROS Discourse General: Guest Talk by Tomoya Fujita - Cloud Robotics WG Meeting 2024-12-16 + discourse.ros.org-topic-41021 + https://discourse.ros.org/t/guest-talk-by-tomoya-fujita-cloud-robotics-wg-meeting-2024-12-16/41021 + <p>Please come and join us for this coming meeting at 1700-1800 UTC on Monday 16th December 2024, where <a href="https://github.com/fujitatomoya" rel="noopener nofollow ugc">Tomoya Fujita</a> will be talking about Robotics Platforms empowered by Cloud-Native Technologies.</p> +<p>Tomoya is a software engineer, contributor to ROS2 core, and well-respected community builder. In this session, he will talk about a range of Cloud-Native Technologies he has worked on, and their relevance to robotics. In particular, Tomoya has done a great deal of work on KubeEdge, a platform built on Kubernetes that can be used to deploy software to robots as if they are Kubernetes clusters. Some resources from his talk includes:</p> +<ul> +<li><a href="https://roscon.ros.org/2023/talks/ROS_with_KubernetesKubeEdge.pdf">ROSCon 2023: ROS with Kubernetes / KubeEdge</a></li> +<li><a href="https://github.com/fujitatomoya/ros_k8s" rel="noopener nofollow ugc">Some examples to deploy ROS / ROS 2 with Kubernetes</a></li> +<li><a href="https://static.sched.com/hosted_files/colocatedeventsna2024/15/Cilium%2BeBPF-Day-NA_Cilium-with-KubeEdge.v0.pdf" rel="noopener nofollow ugc">Next-generation Robotics Platform for Edge/Cloud</a></li> +</ul> +<p>Tomoya also plans to leave time to discuss Cloud Robotics with the group, particularly the problems that people are having with Cloud Robotics.</p> +<p>Last meeting, we worked through a workshop for Eclipse Zenoh to test its capabilities and ease of setup. If you’re interested to see our progress, please check the <a href="https://youtu.be/NwZrAPGrDpU" rel="noopener nofollow ugc">meeting recording</a>.</p> +<p>If you are willing and able to give a talk on cloud robotics in future meetings, we would be happy to host you - please reply here, message me directly, or sign up using the <a href="https://docs.google.com/spreadsheets/d/1drBcG-CXmX8YxBZuRK8Lr3eTTfqe2p_RF_HlDw4Rj5g/edit?gid=0#gid=0" rel="noopener nofollow ugc">Guest Speaker Signup Sheet</a>. We will record your talk and host it on YouTube with our other meeting recordings too!</p> +<p>The meeting link is <a href="https://meet.google.com/xox-nshv-uvm" rel="noopener nofollow ugc">here</a>, and you can sign up to <a href="https://calendar.google.com/calendar/u/0/embed?src=c_3fc5c4d6ece9d80d49f136c1dcd54d7f44e1acefdbe87228c92ff268e85e2ea0@group.calendar.google.com" rel="noopener nofollow ugc">our calendar</a> or our <a href="https://groups.google.com/g/cloud-robotics-working-group-invites" rel="noopener nofollow ugc">Google Group</a> for meeting notifications.</p> +<p>Hopefully we will see you there!</p> + <p><small>1 post - 1 participant</small></p> + <p><a href="https://discourse.ros.org/t/guest-talk-by-tomoya-fujita-cloud-robotics-wg-meeting-2024-12-16/41021">Read full topic</a></p> + Mon, 09 Dec 2024 14:58:15 +0000 + + + ROS Discourse General: Robotics engineers are in high demand — but what is the job really like? + discourse.ros.org-topic-41015 + https://discourse.ros.org/t/robotics-engineers-are-in-high-demand-but-what-is-the-job-really-like/41015 + <p><a href="https://www.youtube.com/watch?v=z_uGhq2ayVA">Robotics engineers are in high demand — but what is the job really like?</a></p> + + <p><small>2 posts - 1 participant</small></p> + <p><a href="https://discourse.ros.org/t/robotics-engineers-are-in-high-demand-but-what-is-the-job-really-like/41015">Read full topic</a></p> + Sun, 08 Dec 2024 23:32:15 +0000 + + + ROS Discourse General: ROS News for the Week of December 2nd, 2024 + discourse.ros.org-topic-40997 + https://discourse.ros.org/t/ros-news-for-the-week-of-december-2nd-2024/40997 + <h1><a class="anchor" href="https://discourse.ros.org#p-88375-ros-news-for-the-week-of-december-2nd-2024-1" name="p-88375-ros-news-for-the-week-of-december-2nd-2024-1"></a>ROS News for the Week of December 2nd, 2024</h1> +<p></p><div class="lightbox-wrapper"><a class="lightbox" href="https://global.discourse-cdn.com/flex022/uploads/ros/original/3X/7/1/71f9dbb6dd793e528e6b7dc0f823db7b16b6d66a.jpeg" title="GeCwHKiX0AAHleo"><img alt="GeCwHKiX0AAHleo" height="250" src="https://global.discourse-cdn.com/flex022/uploads/ros/optimized/3X/7/1/71f9dbb6dd793e528e6b7dc0f823db7b16b6d66a_2_333x250.jpeg" width="333" /></a></div><div class="lightbox-wrapper"><a class="lightbox" href="https://global.discourse-cdn.com/flex022/uploads/ros/original/3X/9/f/9f7d76e4cd5fcbbdcca69965bf2929822fded345.jpeg" title="Gd-rDnlW4AAsP38"><img alt="Gd-rDnlW4AAsP38" height="230" src="https://global.discourse-cdn.com/flex022/uploads/ros/optimized/3X/9/f/9f7d76e4cd5fcbbdcca69965bf2929822fded345_2_345x230.jpeg" width="345" /></a></div><br /> +ROSCon Germany and ROSCon India were both this week! It was really exciting to see two ROS events happening concurrently on two different parts of the globe. We want to congratulate the organizers and attendees on putting together fantastic events.<p></p> +<ul> +<li><a href="https://x.com/purushottamshet/status/1864683903409148096">ROSCon India photo from @purushottamshet on Twitter</a></li> +<li><a href="https://x.com/stoglrobotics/status/1864397010998042805/photo/1">ROSCon Germany photo from @stoglrobotics on Twitter</a></li> +</ul> +<p></p><div class="lightbox-wrapper"><a class="lightbox" href="https://global.discourse-cdn.com/flex022/uploads/ros/original/3X/7/7/775a0e1e4201695f64be7a4bcbd10757a3fc904b.jpeg" title="ROSCon_China_2024"><img alt="ROSCon_China_2024" height="375" src="https://global.discourse-cdn.com/flex022/uploads/ros/optimized/3X/7/7/775a0e1e4201695f64be7a4bcbd10757a3fc904b_2_376x375.jpeg" width="376" /></a></div><br /> +But wait, there’s more! Our first ever <a href="https://www.roscon.cn/2024/index.html">ROSCon China</a> in Shanghai is about to kick off in about four or five hours.<p></p> +<br /> +<p></p><div class="lightbox-wrapper"><a class="lightbox" href="https://global.discourse-cdn.com/flex022/uploads/ros/original/3X/8/7/87978cd5a5b63e38d982ed533928a5d73bb94c03.jpeg" title="9cqsf8"><img alt="9cqsf8" height="375" src="https://global.discourse-cdn.com/flex022/uploads/ros/optimized/3X/8/7/87978cd5a5b63e38d982ed533928a5d73bb94c03_2_374x375.jpeg" width="374" /></a></div><br /> +While we’re welcoming so many new friends to the ROS community we’re also getting ready to say farewell to <a href="https://dlu.github.io/ros_clock/index.html">ROS 1 Noetic</a>, <a href="https://discourse.ros.org/t/gazebo-classic-and-citadel-end-of-life-x-post-gazebo-sim-community/40931">Gazebo Classic, Gazebo Citadel</a>, and <a href="https://discourse.ros.org/t/preparing-for-final-iron-irwini-patch-release-and-sync-2024-11-18/40619">ROS 2 Iron Irwini</a>.<p></p> +<br /> +<p></p><div class="lightbox-wrapper"><a class="lightbox" href="https://global.discourse-cdn.com/flex022/uploads/ros/original/3X/0/0/00840d8b17a4ec3d6663d42e439242720c0a043e.jpeg" title="SGDecROSMeetup"><img alt="SGDecROSMeetup" height="291" src="https://global.discourse-cdn.com/flex022/uploads/ros/optimized/3X/0/0/00840d8b17a4ec3d6663d42e439242720c0a043e_2_517x291.jpeg" width="517" /></a></div><br /> +We have two ROS Meetups planned for 2024-12-12. <a href="https://www.meetup.com/singapore-ros-meetup/events/304791372">One meetup in Singapore</a> and <a href="https://discourse.ros.org/t/meetup-fin-de-ano-de-ros-barcelona/40880">another one in Barcelona Spain</a><p></p> +<br /> +<p></p><div class="lightbox-wrapper"><a class="lightbox" href="https://global.discourse-cdn.com/flex022/uploads/ros/original/3X/0/8/0886c02ebe7cf611b3d87c1a059892a4b6cb6610.jpeg" title="Thanksgiving"><img alt="Thanksgiving" height="291" src="https://global.discourse-cdn.com/flex022/uploads/ros/optimized/3X/0/8/0886c02ebe7cf611b3d87c1a059892a4b6cb6610_2_517x291.jpeg" width="517" /></a></div><br /> +If you are in a giving mood this holiday season we are currently running <a href="https://discourse.ros.org/t/osrf-holiday-donation-drive/40852">a donation campaign for the OSRF</a>. We’ve made it possible for you to earmark your donation for particular OSRF projects like the ROS Build Farm, the ROS Documentation, and our educational outreach initiatives.<p></p> +<br /> +<p></p><div class="lightbox-wrapper"><a class="lightbox" href="https://global.discourse-cdn.com/flex022/uploads/ros/original/3X/1/5/158b104ca9c6e150a6639b69b1ad19f1149e12b1.jpeg" title="Aug24GCM (1)"><img alt="Aug24GCM (1)" height="194" src="https://global.discourse-cdn.com/flex022/uploads/ros/optimized/3X/1/5/158b104ca9c6e150a6639b69b1ad19f1149e12b1_2_345x194.jpeg" width="345" /></a></div><br /> +At last week’s <a href="https://discourse.ros.org/t/november-gazebo-community-meeting-nasa-space-ros-challenge/40848">Gazebo Community Meeting</a> we met multiple competitors from the NASA SpaceROS Summer Sprint Challenge. The results are absolutely amazing and are all open source! We recommend you check it out.<p></p> +<h1><a class="anchor" href="https://discourse.ros.org#p-88375-events-2" name="p-88375-events-2"></a>Events</h1> +<ul> +<li><a href="https://discourse.ros.org/t/looking-for-austin-ros-meetup-speakers/40981">Looking for Austin ROS Meetup Speakers!</a></li> +<li><a href="https://lu.ma/2lkm9otp?tk=wqm4zy">2024-12-07 Circuit Launch Mountain View Grand Opening</a></li> +<li><a href="https://www.roscon.cn/2024/index.html">2024-12-07 → 2024-12-08 ROSCon China in Shenzhen</a></li> +<li><a href="https://discourse.ros.org/t/ros-2-rust-meeting-december-2024/40991">2024-12-10 ROS 2 Rust Meeting: December 2024</a></li> +<li><a href="https://humanoidssummit.com/">2024-12-11 =&gt; 2024-12-12 Humanoids Summit Bay Area</a></li> +<li><a href="https://discourse.ros.org/t/embodied-ai-community-group-meeting-2/40987">2024-12-11 Embodied AI Community Group meeting 2</a></li> +<li><a href="https://www.meetup.com/singapore-ros-meetup/events/304791372">2024-12-12 ROS Meetup Singapore</a></li> +<li><a href="https://discourse.ros.org/t/meetup-fin-de-ano-de-ros-barcelona/40880">2024-12-12 ROS Meetup Barcelona</a></li> +<li><a href="https://firahackathon.github.io/">2024-12-15 FIRA Ag Robotics Hackathon Registration Deadline</a></li> +<li><a href="https://autodrive-ecosystem.github.io/competitions/f1tenth-sim-racing-cdc-2024/">2024-12-16 =&gt; 2024-12-19 F1Tenth Sim Racing League at CDC 2024</a></li> +<li><a href="https://discourse.ros.org/t/aerial-robotics-meeting-xmas-with-bitcraze-dec-18-2024/40951">2024-12-18 Aerial Robotics meeting - Xmas with Bitcraze</a></li> +<li><a href="https://docs.google.com/forms/d/e/1FAIpQLSeiuWtUClyQ2Aj-CBFwZacpfL9xxgG_ZA8ImF0SF9sT2-sqKA/viewform">2024-12-22 Open Hardware Summit CFP Deadline</a></li> +<li><a href="https://www.naturalroboticscontest.com/">2024-12-31 Deadline for Natural Robotics Contest</a></li> +<li><a href="https://fosdem.org/2025/">2025-02-01 FOSDEM 25</a> – <a href="https://discourse.ros.org/t/fosdem-2025-robotics-simulation-first-edition/40349">See Robotics and Sim Room</a></li> +<li><a href="https://world-fira.com/">2025-02-04 =&gt; 2025-02-06 World FIRA Ag Robotics Conference in Toulouse, France</a></li> +<li><a href="https://discourse.ros.org/t/7th-international-workshop-on-robotics-software-engineering/39901">2025-04-28 International Workshop on Robotics Software Engineering</a></li> +<li><a href="https://2025.oshwa.org/">2025-05-30 =&gt; 2025-05-31 2025 Open Hardware Summit in Edinburgh</a></li> +</ul> +<h1><a class="anchor" href="https://discourse.ros.org#p-88375-news-3" name="p-88375-news-3"></a>News</h1> +<ul> +<li><a href="https://discourse.ros.org/t/osrf-holiday-donation-drive/40852">OSRF Holiday Donation Drive</a></li> +<li><a href="https://discourse.ros.org/t/november-gazebo-community-meeting-nasa-space-ros-challenge/40848"><img alt=":cool:" class="emoji" height="20" src="https://emoji.discourse-cdn.com/twitter/cool.png?v=12" title=":cool:" width="20" /> November Gazebo Community Meeting: NASA Space ROS Challenge</a></li> +<li><a href="https://discourse.ros.org/t/call-for-participation-ros-deliberation-community-group/40932">Call for Participation: ROS Deliberation Community Group</a></li> +<li><a href="https://discourse.ros.org/t/robotic-blending-milestone-5-highlight-video-live/40920">Robotic Blending Milestone 5 Highlight Video Live</a></li> +<li><a href="https://discourse.ros.org/t/open-call-for-eurobotics-technology-transfer-award-2025/40978">Call for euRobotics Technology Transfer Award 2025</a></li> +<li><a href="https://www.ieee-ras.org/membership/dei-committee/idea-travel-support">IEEE RAS DEI / Accessibilty Travel Support Grant</a></li> +<li><a href="https://discourse.ros.org/t/osra-tgc-meeting-minutes-for-october-2024/40768">OSRA TGC meeting minutes for October, 2024</a></li> +<li><a href="https://discourse.ros.org/t/ros-pmc-meeting-minutes-2024-12-03/40941">ROS PMC Meeting minutes 2024-12-03</a></li> +<li><a href="https://discourse.ros.org/t/ros-pmc-meeting-minutes-2024-11-26/40833">ROS PMC Meeting minutes 2024-11-26</a></li> +<li><a href="https://elisa.tech/event/elisa-workshop-at-nasa-goddard-space-grade-linux/">ELISA Workshop at NASA Goddard – Space Grade Linux</a></li> +<li><a href="https://www.youtube.com/watch?v=lyPkcCAOrP8">How Arduino Forged a Path for Open Hardware - David Cuartielles, Co-Founder, Arduino</a></li> +<li><a href="https://github.com/GimpelZhang/GaussianRPG">GaussianRPG: 3D Gaussian Rendering PlayGround: an open-source autonomous driving closed-loop simulator demo using 3D Gaussian Splatting tech</a></li> +<li><a href="https://www.youtube.com/watch?v=DvvFEh0PmvU&amp;t=1s">Jeffrey Ichnowski : Learning for Dynamic Robot Manipulation of Deformable Objects</a></li> +<li><a href="https://www.youtube.com/watch?v=hBWMQvCjevs">Sebastian Castro: Research and Industry Future in Robotics</a></li> +<li><a href="https://weed-ai.sydney.edu.au/explore?is_head_filter=%5B%22latest+version%22%5D">Weed Dataset (for agriculture)</a></li> +<li><a href="https://www.youtube.com/watch?v=2XHhq9hQB0g">Video: Crazyflie at Bitcraze’s Headquarters in Malmö, Sweden</a></li> +<li><a href="https://www.therobotreport.com/teleo-raises-16-2-million-to-scale-supervised-autonomy-for-heavy-equipment/">Teleo raises $16.2M to scale supervised autonomy for heavy equipment</a></li> +<li><a href="https://picknik.ai/2024/11/05/SBIR-Space-contract-wins.html">PickNik Robotics Secures $3 Million in NASA and Space Force</a></li> +<li><a href="https://techcrunch.com/2024/12/05/amp-robotics-raises-91m-to-build-more-robot-filled-waste-sorting-facilities/">Amp Robotics raises $91M</a> – <a href="https://www.therobotreport.com/amp-robotics-raises-91m-accelerate-deployment-recycling-systems/">The Robot Report</a></li> +<li><a href="https://www.therobotreport.com/a300-clearpath-robotics-discusses-development/">Clearpath Robotics discusses development of Husky A300 ground vehicle</a></li> +<li><a href="https://www.therobotreport.com/astm-developing-testing-standards-for-mobile-manipulators/">ASTM developing testing standards for mobile manipulator</a></li> +<li><a href="https://techcrunch.com/2024/12/05/arx-launches-firestick-like-platform-to-make-military-trucks-autonomous/">ARX launches firestick-like platform to make military trucks autonomous</a></li> +<li><a href="https://discourse.ros.org/t/fosdem-2025-robotics-simulation-first-edition/40349">FOSDEM 2025: Robotics &amp; Simulation… first edition!</a></li> +</ul> +<h1><a class="anchor" href="https://discourse.ros.org#p-88375-ros-4" name="p-88375-ros-4"></a>ROS</h1> +<ul> +<li><a href="https://discourse.ros.org/t/gazebo-classic-and-citadel-end-of-life-x-post-gazebo-sim-community/40931">Gazebo Classic and Citadel End of Life</a></li> +<li><a href="https://discourse.ros.org/t/new-book-ros-2-from-scratch/40807">New Book - ROS 2 from Scratch</a></li> +<li><a href="https://discourse.ros.org/t/new-packages-for-noetic-2024-12-06/40995">New Packages for Noetic 2024-12-06</a></li> +<li><a href="https://discourse.ros.org/t/new-packages-and-patch-release-for-humble-hawksbill-2024-12-05/40976">New packages for Humble Hawksbill 2024-12-05</a></li> +<li><a href="https://discourse.ros.org/t/new-packages-for-ros-2-rolling-ridley-2024-11-26/40835">New packages for ROS 2 Rolling Ridley 2024-11-26</a></li> +<li><a href="https://discourse.ros.org/t/preparing-for-final-iron-irwini-patch-release-and-sync-2024-11-18/40619">Preparing for final Iron Irwini Patch Release and Sync 2024-11-18</a></li> +<li><a href="https://discourse.ros.org/t/iron-irwini-eol-plan/40365">Iron Irwini EOL Plan</a></li> +<li><a href="https://discourse.ros.org/t/rmw-iceoryx2-v0-1-0-release/40996">rmw_iceoryx2 v0.1.0 release</a></li> +<li><a href="https://discourse.ros.org/t/leveraging-ros-build-infrastructure-for-non-ros-packages/40658">Leveraging ROS build infrastructure for non-ROS packages</a></li> +<li><a href="https://discourse.ros.org/t/clearpath-simulator-comes-to-gazebo-harmonic/40975">Clearpath Simulator comes to Gazebo Harmonic <img alt=":fire:" class="emoji" height="20" src="https://emoji.discourse-cdn.com/twitter/fire.png?v=12" title=":fire:" width="20" /></a></li> +<li><a href="https://discourse.ros.org/t/expose-secure-communication-only-with-specified-entities/40957">Expose secure communication only with specified entities</a></li> +<li><a href="https://discourse.ros.org/t/reference-implementation-of-zenoh-pico-to-micro-ros/40750">Reference implementation of Zenoh-pico to micro-ROS</a></li> +<li><a href="https://discourse.ros.org/t/notice-nav2-migrated-to-twiststamped-to-replace-twist-for-cmd-vel-topics/40944">Nav2 Migrated to TwistStamped to replace Twist for cmd_vel Topics</a></li> +<li><a href="https://discourse.ros.org/t/towards-a-rosdoc-integation-testing-tutorial/40701">Towards a ROSdoc integation testing tutorial</a></li> +<li><a href="https://discourse.ros.org/t/polar-grid-rviz-plugin/40909">Polar Grid Rviz Plugin - ROS Projects</a></li> +<li><a href="https://discourse.ros.org/t/fusionsdf-export-fusion-360-cad-designs-to-sdf/39430">FusionSDF: Export Fusion 360 CAD designs to SDF</a></li> +<li><a href="https://discourse.ros.org/t/ros-2-reinforcement-learning/40898">ROS 2 Reinforcement learning</a></li> +<li><a href="https://discourse.ros.org/t/new-ros2-package-for-dynamically-interpolating-3d-lidar-point-clouds/40876">New ROS 2 package for dynamically interpolating 3D LiDAR point clouds</a></li> +<li><a href="https://discourse.ros.org/t/help-needed-distribute-a-ros-package-against-multiple-sdk-versions/40827">Help needed: Distribute a ROS package against multiple SDK versions</a></li> +<li><a href="https://discourse.ros.org/t/ros-2-whisper-update/40808">ROS 2 Whisper update</a></li> +<li><a href="https://github.com/victorcarvesk/ros-voice-assistant">ros-voice-assistant: A ROS 2 package for building voice-enabled robotic applications</a></li> +<li><a href="https://arxiv.org/abs/2412.03887">MOANA: Multi-Radar Dataset for Maritime Odometry and Autonomous Navigation Application</a> – <a href="https://sites.google.com/corp/view/rpmmoana/">MOANA Dataset</a></li> +<li><a href="https://github.com/ChenHoy/DROID-Splat">DROID-Splat: End-to-End SLAM with camera calibration, monocular prior integration and dense Rendering</a></li> +<li><a href="https://github.com/alesof/ROS2-VSC-Toolkit">ROS2-VSC-Toolkit: Visual Studio Code Extension for ROS 2 development</a></li> +<li><a href="https://marketplace.visualstudio.com/items?itemName=morningfrog.urdf-visualizer">URDF Visualizer - Visual Studio Plugin</a></li> +<li><a href="https://github.com/hijimasa/ros2-tools-to-use-unity-like-gazebo">ros2-tools-to-use-unity-like-gazebo: ros2_control in Unity</a></li> +<li><a href="https://github.com/luohongk/SuperVINS">SuperVINS: A real-time visual-inertial SLAM framework for challenging imaging conditions</a></li> +<li><a href="https://ekumenlabs.com/blog/posts/big-shoes-to-fill-beluga-performance-report/">Validating the performance of Beluga AMCL</a></li> +<li><a href="https://github.com/agimus-project/happypose_ros"><img alt=":cool:" class="emoji" height="20" src="https://emoji.discourse-cdn.com/twitter/cool.png?v=12" title=":cool:" width="20" /> happypose_ros: ROS 2 wrapper for a 6D pose estimation library</a></li> +<li><a href="https://github.com/HiroIshida/plainmp">plainmp: Very fast motion planning for articulated robot, through a bit of premature-optimization (C++ / Python)</a></li> +<li><a href="https://github.com/nobleo/full_coverage_path_planner">full_coverage_path_planner with a move_base_flex plugin</a></li> +<li><a href="https://github.com/liangheming/VoxelMapPlus_FASTLIO2">VoxelMapPlus_FASTLIO2: FAST-LIO 2 with VoxelMapPlus and STD</a></li> +<li><a href="https://github.com/NKU-MobFly-Robotics/SPTG-LCC">SPTG-LCC: Single-shot, Pixel-level, Target-free and General LiDAR-Camera Extrinsic Self-Calibration</a></li> +<li><a href="https://github.com/karlkurzer/path_planner">path_planner: Hybrid A* Path Planner for the KTH Research Concept Vehicle</a></li> +<li><a href="https://github.com/Liansheng-Wang/InGM-LIO">InGM-LIO: InGM-LIO: A Multiscale Gaussian Model-Based LiDAR-Inertial Odometry Using Invariant Kalman Filtering.</a></li> +<li><a href="https://github.com/UTS-RI/2fast2lamaa">2fast2lamaa: Real-time lidar-inertial odometry and mapping framework for dynamic environments</a></li> +<li><a href="https://github.com/PRBonn/kinematic-icp">kinematic-icp: A LiDAR odometry pipeline for wheeled mobile robots</a></li> +<li><a href="https://github.com/MizuhoAOKI/python_simple_mppi">python_simple_mppi: Python implementation of MPPI (Model Predictive Path-Integral) controller</a></li> +<li><a href="https://github.com/Geekgineer/YOLOs-CPP">YOLOs-CPP: A high-performance C++ headers for real-time object detection using YOLO models</a></li> +<li><a href="https://github.com/ghm0819/ERPoT">ERPoT: Effective and Reliable Pose Tracking for Mobile Robots Based on Lightweight and Compact Polygon Maps</a></li> +<li><a href="https://github.com/kyavuzkurt/multicast_parser">multicast_parser: ROS Package for parsing multicast data from Motive Tracker 2.0.2 to Appropriate Nodes</a></li> +<li><a href="https://github.com/winstxnhdw/AutoCarROS2">AutoCarROS2: A virtual simulation platform for autonomous vehicle sensing, mapping, control and behaviour methods using ROS 2 and Gazebo.</a></li> +<li><a href="https://ieeexplore.ieee.org/document/10684721">SlicerROS2: A Research and Development Module for Image-Guided Robotic Interventions</a></li> +<li><a href="https://github.com/anujjain-dev/unitree-go2-ros2">unitree-go2-ros2: URDF for Unitree Go2 with Champ Controller</a></li> +<li><a href="https://ieeexplore.ieee.org/document/10769556">DPFT: Dual Perspective Fusion Transformer for Camera-Radar-based Object Detection</a> – <a href="https://github.com/TUMFTM/DPFT">source</a></li> +<li><a href="https://github.com/saadi-tech/kidnapped_robot_finder">kidnapped_robot_finder: TROS 2 package for 2d-Lidar scanner based kidnapped robot re-localization</a></li> +</ul> +<h1><a class="anchor" href="https://discourse.ros.org#p-88375-got-a-minute-alarm_clock-5" name="p-88375-got-a-minute-alarm_clock-5"></a>Got a Minute? <img alt=":alarm_clock:" class="emoji" height="20" src="https://emoji.discourse-cdn.com/twitter/alarm_clock.png?v=12" title=":alarm_clock:" width="20" /></h1> +<p>We would really appreciate it if you took ten minutes to answer just one ROS question on <a href="https://robotics.stackexchange.com/?tags=ros2">Robotics Stack Exchange</a>.</p> + <p><small>1 post - 1 participant</small></p> + <p><a href="https://discourse.ros.org/t/ros-news-for-the-week-of-december-2nd-2024/40997">Read full topic</a></p> + Fri, 06 Dec 2024 20:59:45 +0000 + + + ROS Discourse General: rmw_iceoryx2 v0.1.0 release + discourse.ros.org-topic-40996 + https://discourse.ros.org/t/rmw-iceoryx2-v0-1-0-release/40996 + <p>Hi all,</p> +<p><code>orecham</code> here, one of the committers from the <code>eclipse-iceoryx</code> project.</p> +<p>I’m pleased to announce the alpha release of <code>rmw_iceoryx2</code>, compatible with ROS 2 <code>rolling</code> and available at: <a class="inline-onebox" href="https://github.com/ekxide/rmw_iceoryx2" rel="noopener nofollow ugc">GitHub - ekxide/rmw_iceoryx2: ROS 2 RMW implementation for iceoryx2</a></p> +<p>Why yet another RMW? We have the following goals for <code>rmw_iceoryx2</code>:</p> +<ol> +<li>Bring the high-performance zero-copy shared-memory communication offered by <a href="https://github.com/eclipse-iceoryx/iceoryx2/tree/main" rel="noopener nofollow ugc"><code>iceoryx2</code></a> to ROS 2 applications</li> +<li>Provide a unique option for reducing safety certification effort of ROS 2 applications with safety-critical use-cases</li> +</ol> +<p>Rather than require the entire ROS 2 stack be certified (e.g. for ASIL-D), <code>rmw_iceoryx2</code> offers an alternative through interoperability between ROS 2 and <code>iceoryx2</code> applications. This allows the freedom for porting safety-critical components that require certification to <code>iceoryx2</code> (which is designed for certification) while still participating in the ROS 2 ecosystem.</p> +<h2><a class="anchor" href="https://discourse.ros.org#p-88374-current-state-1" name="p-88374-current-state-1"></a>Current State</h2> +<p>With this first alpha release, there is still some work to do and polish to be made. Not all features are yet available and existing ones need thorough real-world validation. Most notably, support for message serialization is not yet available nor service-client communication (waiting on some features to be completed in <code>iceoryx2</code>). Lack of serialization support means that <code>rmw_iceoryx2</code> can currently only work with self-contained message types, however, this will be one of the first limitations to address next.</p> +<p>Furthermore, only intra-host communication is currently possible. We have plans to introduce host-to-host capabilities in the near future by leveraging existing host-to-host-capable middlewares. Some more info about this is available in the <a href="https://github.com/ekxide/rmw_iceoryx2/tree/main?tab=readme-ov-file#is-rmw_iceoryx2-capable-of-host-to-host-communication" rel="noopener nofollow ugc"><code>README</code></a>.</p> +<h2><a class="anchor" href="https://discourse.ros.org#p-88374-performance-2" name="p-88374-performance-2"></a>Performance</h2> +<p>The current <a href="https://gitlab.com/ApexAI/performance_test/-/tree/master" rel="noopener nofollow ugc"><code>performance_test</code></a> results are as follow. There is still quite a bit of room for improvement compared to <a href="https://github.com/eclipse-iceoryx/iceoryx2?tab=readme-ov-file#performance" rel="noopener nofollow ugc">raw <code>iceoryx2</code></a>:</p> +<p></p><div class="lightbox-wrapper"><a class="lightbox" href="https://global.discourse-cdn.com/flex022/uploads/ros/original/3X/7/5/75f0f5a88ce7d73d7e9f0d4238112255176df783.png" rel="noopener nofollow ugc" title="v0.1.0"><img alt="v0.1.0" height="500" src="https://global.discourse-cdn.com/flex022/uploads/ros/optimized/3X/7/5/75f0f5a88ce7d73d7e9f0d4238112255176df783_2_652x500.png" width="652" /></a></div><p></p> +<h2><a class="anchor" href="https://discourse.ros.org#p-88374-contributing-and-feedback-3" name="p-88374-contributing-and-feedback-3"></a>Contributing and Feedback</h2> +<p>We look forward to your feedback! Input from real-world application configurations will be invaluable for bringing <code>rmw_iceoryx2</code> to stability. Additionally, insights from those experienced with RMW implementations would greatly help improve quality. The current state was achieved using only the information available in the RMW documentation, thus there may be some edge-cases known to veterans which are not properly addressed.</p> +<p>For those who have the capacity to get involved with implementation, we welcome all contributions! We will provide as much support as needed to those who are interested.</p> +<p>Thanks for reading!<br /> +Cheers</p> + <p><small>1 post - 1 participant</small></p> + <p><a href="https://discourse.ros.org/t/rmw-iceoryx2-v0-1-0-release/40996">Read full topic</a></p> + Fri, 06 Dec 2024 20:29:44 +0000 + + + ROS Discourse General: New Packages for Noetic 2024-12-06 + discourse.ros.org-topic-40995 + https://discourse.ros.org/t/new-packages-for-noetic-2024-12-06/40995 + <p>We’re happy to announce <strong>2</strong> new packages and <strong>46</strong> updates are now available in ROS Noetic. This sync was tagged as <a href="https://github.com/ros/rosdistro/blob/noetic/2024-12-06/noetic/distribution.yaml" rel="noopener nofollow ugc"><code>noetic/2024-12-06</code></a>.</p> +<p>Thank you to every maintainer and contributor who made these updates available!</p> +<h2><a class="anchor" href="https://discourse.ros.org#p-88370-package-updates-for-ros-noetic-1" name="p-88370-package-updates-for-ros-noetic-1"></a>Package Updates for ROS Noetic</h2> +<h3><a class="anchor" href="https://discourse.ros.org#p-88370-added-packages-2-2" name="p-88370-added-packages-2-2"></a>Added Packages [2]:</h3> +<ul> +<li><a href="https://github.com/peci1/gazebo_noisy_depth_camera" rel="noopener nofollow ugc">ros-noetic-gazebo-noisy-depth-camera</a>: 1.0.1-1</li> +<li>ros-noetic-hatchbed-common: 0.0.2-1</li> +</ul> +<h3><a class="anchor" href="https://discourse.ros.org#p-88370-updated-packages-46-3" name="p-88370-updated-packages-46-3"></a>Updated Packages [46]:</h3> +<ul> +<li><a href="https://wiki.ros.org/ess_imu_driver">ros-noetic-ess-imu-driver</a>: 2.0.1-1 → 2.0.2-1</li> +<li>ros-noetic-etsi-its-cam-coding: 2.3.0-1 → 2.4.0-1</li> +<li>ros-noetic-etsi-its-cam-conversion: 2.3.0-1 → 2.4.0-1</li> +<li>ros-noetic-etsi-its-cam-msgs: 2.3.0-1 → 2.4.0-1</li> +<li>ros-noetic-etsi-its-cam-ts-coding: 2.3.0-1 → 2.4.0-1</li> +<li>ros-noetic-etsi-its-cam-ts-conversion: 2.3.0-1 → 2.4.0-1</li> +<li>ros-noetic-etsi-its-cam-ts-msgs: 2.3.0-1 → 2.4.0-1</li> +<li>ros-noetic-etsi-its-coding: 2.3.0-1 → 2.4.0-1</li> +<li>ros-noetic-etsi-its-conversion: 2.3.0-1 → 2.4.0-1</li> +<li>ros-noetic-etsi-its-cpm-ts-coding: 2.3.0-1 → 2.4.0-1</li> +<li>ros-noetic-etsi-its-cpm-ts-conversion: 2.3.0-1 → 2.4.0-1</li> +<li>ros-noetic-etsi-its-cpm-ts-msgs: 2.3.0-1 → 2.4.0-1</li> +<li>ros-noetic-etsi-its-denm-coding: 2.3.0-1 → 2.4.0-1</li> +<li>ros-noetic-etsi-its-denm-conversion: 2.3.0-1 → 2.4.0-1</li> +<li>ros-noetic-etsi-its-denm-msgs: 2.3.0-1 → 2.4.0-1</li> +<li>ros-noetic-etsi-its-messages: 2.3.0-1 → 2.4.0-1</li> +<li>ros-noetic-etsi-its-msgs: 2.3.0-1 → 2.4.0-1</li> +<li>ros-noetic-etsi-its-msgs-utils: 2.3.0-1 → 2.4.0-1</li> +<li>ros-noetic-etsi-its-primitives-conversion: 2.3.0-1 → 2.4.0-1</li> +<li>ros-noetic-etsi-its-rviz-plugins: 2.3.0-1 → 2.4.0-1</li> +<li>ros-noetic-etsi-its-vam-ts-coding: 2.3.0-1 → 2.4.0-1</li> +<li>ros-noetic-etsi-its-vam-ts-conversion: 2.3.0-1 → 2.4.0-1</li> +<li>ros-noetic-etsi-its-vam-ts-msgs: 2.3.0-1 → 2.4.0-1</li> +<li><a href="https://github.com/foxglove/ros-foxglove-bridge" rel="noopener nofollow ugc">ros-noetic-foxglove-bridge</a>: 0.7.10-1 → 0.8.1-1</li> +<li>ros-noetic-inorbit-republisher: 0.3.0-1 → 0.3.2-1</li> +<li><a href="http://ros.org/wiki/nodelet">ros-noetic-nodelet</a>: 1.11.0-2 → 1.11.1-1</li> +<li><a href="http://www.ros.org/wiki/nodelet_core">ros-noetic-nodelet-core</a>: 1.11.0-2 → 1.11.1-1</li> +<li><a href="http://ros.org/wiki/nodelet_topic_tools">ros-noetic-nodelet-topic-tools</a>: 1.11.0-2 → 1.11.1-1</li> +<li>ros-noetic-rc-reason-clients: 0.3.1-1 → 0.4.0-2</li> +<li>ros-noetic-rc-reason-msgs: 0.3.1-1 → 0.4.0-2</li> +<li><a href="http://introlab.github.io/rtabmap" rel="noopener nofollow ugc">ros-noetic-rtabmap</a>: 0.21.6-1 → 0.21.9-1</li> +<li>ros-noetic-rtabmap-conversions: 0.21.5-1 → 0.21.9-1</li> +<li>ros-noetic-rtabmap-costmap-plugins: 0.21.5-1 → 0.21.9-1</li> +<li>ros-noetic-rtabmap-demos: 0.21.5-1 → 0.21.9-1</li> +<li>ros-noetic-rtabmap-examples: 0.21.5-1 → 0.21.9-1</li> +<li>ros-noetic-rtabmap-launch: 0.21.5-1 → 0.21.9-1</li> +<li>ros-noetic-rtabmap-legacy: 0.21.5-1 → 0.21.9-1</li> +<li>ros-noetic-rtabmap-msgs: 0.21.5-1 → 0.21.9-1</li> +<li>ros-noetic-rtabmap-odom: 0.21.5-1 → 0.21.9-1</li> +<li>ros-noetic-rtabmap-python: 0.21.5-1 → 0.21.9-1</li> +<li>ros-noetic-rtabmap-ros: 0.21.5-1 → 0.21.9-1</li> +<li>ros-noetic-rtabmap-rviz-plugins: 0.21.5-1 → 0.21.9-1</li> +<li>ros-noetic-rtabmap-slam: 0.21.5-1 → 0.21.9-1</li> +<li>ros-noetic-rtabmap-sync: 0.21.5-1 → 0.21.9-1</li> +<li>ros-noetic-rtabmap-util: 0.21.5-1 → 0.21.9-1</li> +<li>ros-noetic-rtabmap-viz: 0.21.5-1 → 0.21.9-1</li> +</ul> +<h3><a class="anchor" href="https://discourse.ros.org#p-88370-removed-packages-0-4" name="p-88370-removed-packages-0-4"></a>Removed Packages [0]:</h3> +<p>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:</p> +<ul> +<li>Felix Ruess</li> +<li>Geoffrey Biggs</li> +<li>Hans-Joachim Krauch</li> +<li>InOrbit</li> +<li>Jean-Pierre Busch</li> +<li>Marc Alban</li> +<li>Martin Pecka</li> +<li>Mathieu Labbe</li> +<li>Raymond Chow</li> +</ul> + <p><small>2 posts - 2 participants</small></p> + <p><a href="https://discourse.ros.org/t/new-packages-for-noetic-2024-12-06/40995">Read full topic</a></p> + Fri, 06 Dec 2024 18:09:43 +0000 + + + ROS Discourse General: Open-RMF PMC Timing Change for 2024-12-17 + discourse.ros.org-topic-40986 + https://discourse.ros.org/t/open-rmf-pmc-timing-change-for-2024-12-17/40986 + <p>Due to a one-time scheduling conflict, the Open-RMF Project Management Committee session that is normally scheduled for <span class="discourse-local-date">2024-12-17T01:00:00Z UTC</span> will instead take place one hour later at <span class="discourse-local-date">2024-12-17T02:00:00Z UTC</span>. This change is reflected in the official OSRF events calendar.</p> +<p>Sessions will return to the normal time afterwards.</p> + <p><small>1 post - 1 participant</small></p> + <p><a href="https://discourse.ros.org/t/open-rmf-pmc-timing-change-for-2024-12-17/40986">Read full topic</a></p> + Fri, 06 Dec 2024 08:46:33 +0000 + + + ROS Discourse General: New packages and patch release for Humble Hawksbill 2024-12-05 + discourse.ros.org-topic-40976 + https://discourse.ros.org/t/new-packages-and-patch-release-for-humble-hawksbill-2024-12-05/40976 + <p>We’re happy to announce a <a href="https://github.com/ros2/ros2/releases/tag/release-humble-20241205" rel="noopener nofollow ugc">new Humble release</a>!</p> +<p>This sync brings several new packages and some updates to ROS 2 core packages. (I haven’t included the project board for patch info because there was nothing on it.)</p> +<h2><a class="anchor" href="https://discourse.ros.org#p-88326-package-updates-for-humble-1" name="p-88326-package-updates-for-humble-1"></a>Package Updates for Humble</h2> +<h3><a class="anchor" href="https://discourse.ros.org#p-88326-added-packages-34-2" name="p-88326-added-packages-34-2"></a>Added Packages [34]:</h3> +<ul> +<li>ros-humble-adi-3dtof-image-stitching: 2.1.0-1</li> +<li>ros-humble-adi-3dtof-image-stitching-dbgsym: 2.1.0-1</li> +<li><a href="http://ros.org/wiki/axis_camera">ros-humble-axis-camera</a>: 2.0.3-1</li> +<li>ros-humble-axis-description: 2.0.3-1</li> +<li><a href="http://ros.org/wiki/axis_camera">ros-humble-axis-msgs</a>: 2.0.3-1</li> +<li>ros-humble-axis-msgs-dbgsym: 2.0.3-1</li> +<li><a href="http://ros.org/wiki/camera_info_manager_py">ros-humble-camera-info-manager-py</a>: 3.1.10-1</li> +<li>ros-humble-clearpath-motor-msgs: 1.0.1-1</li> +<li>ros-humble-clearpath-motor-msgs-dbgsym: 1.0.1-1</li> +<li>ros-humble-clearpath-ros2-socketcan-interface: 1.0.0-1</li> +<li>ros-humble-clearpath-ros2-socketcan-interface-dbgsym: 1.0.0-1</li> +<li>ros-humble-dual-laser-merger: 0.1.1-1</li> +<li>ros-humble-dual-laser-merger-dbgsym: 0.1.1-1</li> +<li>ros-humble-hatchbed-common: 0.1.1-1</li> +<li>ros-humble-hri-face-body-matcher: 2.1.0-1</li> +<li>ros-humble-hri-face-body-matcher-dbgsym: 2.1.0-1</li> +<li>ros-humble-hri-privacy-msgs: 1.2.0-1</li> +<li>ros-humble-hri-privacy-msgs-dbgsym: 1.2.0-1</li> +<li><a href="https://github.com/JafarAbdi/jacro" rel="noopener nofollow ugc">ros-humble-jacro</a>: 0.2.0-1</li> +<li>ros-humble-laser-segmentation: 3.0.2-1</li> +<li>ros-humble-laser-segmentation-dbgsym: 3.0.2-1</li> +<li>ros-humble-log-view: 0.2.5-1</li> +<li>ros-humble-log-view-dbgsym: 0.2.5-1</li> +<li>ros-humble-pose-broadcaster: 2.38.0-1</li> +<li>ros-humble-pose-broadcaster-dbgsym: 2.38.0-1</li> +<li>ros-humble-ptz-action-server-msgs: 2.0.3-1</li> +<li>ros-humble-ptz-action-server-msgs-dbgsym: 2.0.3-1</li> +<li>ros-humble-rosbag2-to-video: 1.0.1-1</li> +<li><a href="http://ros.org/wiki/simple_grasping">ros-humble-simple-grasping</a>: 0.5.0-1</li> +<li>ros-humble-simple-grasping-dbgsym: 0.5.0-1</li> +<li>ros-humble-slg-msgs: 3.9.1-1</li> +<li>ros-humble-slg-msgs-dbgsym: 3.9.1-1</li> +<li><a href="https://www.stereolabs.com/" rel="noopener nofollow ugc">ros-humble-zed-msgs</a>: 4.2.2-1</li> +<li>ros-humble-zed-msgs-dbgsym: 4.2.2-1</li> +</ul> +<h3><a class="anchor" href="https://discourse.ros.org#p-88326-updated-packages-580-3" name="p-88326-updated-packages-580-3"></a>Updated Packages [580]:</h3> +<ul> +<li>ros-humble-ackermann-steering-controller: 2.37.3-1 → 2.38.0-1</li> +<li>ros-humble-ackermann-steering-controller-dbgsym: 2.37.3-1 → 2.38.0-1</li> +<li>ros-humble-adi-tmcl: 2.0.0-1 → 2.0.3-2</li> +<li>ros-humble-adi-tmcl-dbgsym: 2.0.0-1 → 2.0.3-2</li> +<li>ros-humble-admittance-controller: 2.37.3-1 → 2.38.0-1</li> +<li>ros-humble-admittance-controller-dbgsym: 2.37.3-1 → 2.38.0-1</li> +<li>ros-humble-ament-cmake: 1.3.10-1 → 1.3.11-1</li> +<li>ros-humble-ament-cmake-auto: 1.3.10-1 → 1.3.11-1</li> +<li>ros-humble-ament-cmake-core: 1.3.10-1 → 1.3.11-1</li> +<li>ros-humble-ament-cmake-export-definitions: 1.3.10-1 → 1.3.11-1</li> +<li>ros-humble-ament-cmake-export-dependencies: 1.3.10-1 → 1.3.11-1</li> +<li>ros-humble-ament-cmake-export-include-directories: 1.3.10-1 → 1.3.11-1</li> +<li>ros-humble-ament-cmake-export-interfaces: 1.3.10-1 → 1.3.11-1</li> +<li>ros-humble-ament-cmake-export-libraries: 1.3.10-1 → 1.3.11-1</li> +<li>ros-humble-ament-cmake-export-link-flags: 1.3.10-1 → 1.3.11-1</li> +<li>ros-humble-ament-cmake-export-targets: 1.3.10-1 → 1.3.11-1</li> +<li>ros-humble-ament-cmake-gen-version-h: 1.3.10-1 → 1.3.11-1</li> +<li>ros-humble-ament-cmake-gmock: 1.3.10-1 → 1.3.11-1</li> +<li>ros-humble-ament-cmake-google-benchmark: 1.3.10-1 → 1.3.11-1</li> +<li>ros-humble-ament-cmake-gtest: 1.3.10-1 → 1.3.11-1</li> +<li>ros-humble-ament-cmake-include-directories: 1.3.10-1 → 1.3.11-1</li> +<li>ros-humble-ament-cmake-libraries: 1.3.10-1 → 1.3.11-1</li> +<li>ros-humble-ament-cmake-nose: 1.3.10-1 → 1.3.11-1</li> +<li>ros-humble-ament-cmake-pytest: 1.3.10-1 → 1.3.11-1</li> +<li>ros-humble-ament-cmake-python: 1.3.10-1 → 1.3.11-1</li> +<li>ros-humble-ament-cmake-target-dependencies: 1.3.10-1 → 1.3.11-1</li> +<li>ros-humble-ament-cmake-test: 1.3.10-1 → 1.3.11-1</li> +<li>ros-humble-ament-cmake-vendor-package: 1.3.10-1 → 1.3.11-1</li> +<li>ros-humble-ament-cmake-version: 1.3.10-1 → 1.3.11-1</li> +<li>ros-humble-autoware-lanelet2-extension: 0.6.0-1 → 0.6.2-1</li> +<li>ros-humble-autoware-lanelet2-extension-dbgsym: 0.6.0-1 → 0.6.2-1</li> +<li>ros-humble-autoware-lanelet2-extension-python: 0.6.0-1 → 0.6.2-1</li> +<li>ros-humble-autoware-lanelet2-extension-python-dbgsym: 0.6.0-1 → 0.6.2-1</li> +<li><a href="https://github.com/pal-robotics/backward_ros" rel="noopener nofollow ugc">ros-humble-backward-ros</a>: 1.0.5-1 → 1.0.6-1</li> +<li>ros-humble-backward-ros-dbgsym: 1.0.5-1 → 1.0.6-1</li> +<li>ros-humble-bicycle-steering-controller: 2.37.3-1 → 2.38.0-1</li> +<li>ros-humble-bicycle-steering-controller-dbgsym: 2.37.3-1 → 2.38.0-1</li> +<li>ros-humble-bosch-locator-bridge: 2.1.11-1 → 2.1.13-1</li> +<li>ros-humble-bosch-locator-bridge-dbgsym: 2.1.11-1 → 2.1.13-1</li> +<li>ros-humble-bosch-locator-bridge-utils: 2.1.11-1 → 2.1.13-1</li> +<li>ros-humble-bosch-locator-bridge-utils-dbgsym: 2.1.11-1 → 2.1.13-1</li> +<li><a href="http://ros.org/wiki/camera_calibration_parsers">ros-humble-camera-calibration-parsers</a>: 3.1.9-1 → 3.1.10-1</li> +<li>ros-humble-camera-calibration-parsers-dbgsym: 3.1.9-1 → 3.1.10-1</li> +<li><a href="http://ros.org/wiki/camera_info_manager">ros-humble-camera-info-manager</a>: 3.1.9-1 → 3.1.10-1</li> +<li>ros-humble-camera-info-manager-dbgsym: 3.1.9-1 → 3.1.10-1</li> +<li>ros-humble-camera-ros: 0.1.0-2 → 0.2.0-1</li> +<li>ros-humble-camera-ros-dbgsym: 0.1.0-2 → 0.2.0-1</li> +<li><a href="http://ros.org/wiki/chomp_motion_planner">ros-humble-chomp-motion-planner</a>: 2.5.5-1 → 2.5.6-1</li> +<li>ros-humble-chomp-motion-planner-dbgsym: 2.5.5-1 → 2.5.6-1</li> +<li>ros-humble-clearpath-common: 0.3.4-1 → 1.0.0-1</li> +<li>ros-humble-clearpath-config: 0.3.4-1 → 1.0.0-1</li> +<li>ros-humble-clearpath-config-live: 0.3.0-1 → 1.0.0-1</li> +<li>ros-humble-clearpath-control: 0.3.4-1 → 1.0.0-1</li> +<li>ros-humble-clearpath-customization: 0.3.4-1 → 1.0.0-1</li> +<li>ros-humble-clearpath-description: 0.3.4-1 → 1.0.0-1</li> +<li>ros-humble-clearpath-desktop: 0.3.0-1 → 1.0.0-1</li> +<li>ros-humble-clearpath-generator-common: 0.3.4-1 → 1.0.0-1</li> +<li>ros-humble-clearpath-generator-common-dbgsym: 0.3.4-1 → 1.0.0-1</li> +<li>ros-humble-clearpath-generator-gz: 0.3.0-1 → 1.0.0-1</li> +<li>ros-humble-clearpath-gz: 0.3.0-1 → 1.0.0-1</li> +<li>ros-humble-clearpath-manipulators: 0.3.4-1 → 1.0.0-1</li> +<li>ros-humble-clearpath-manipulators-description: 0.3.4-1 → 1.0.0-1</li> +<li>ros-humble-clearpath-mounts-description: 0.3.4-1 → 1.0.0-1</li> +<li>ros-humble-clearpath-msgs: 1.0.0-1 → 1.0.1-1</li> +<li>ros-humble-clearpath-nav2-demos: 0.2.0-1 → 1.0.0-1</li> +<li>ros-humble-clearpath-platform-description: 0.3.4-1 → 1.0.0-1</li> +<li>ros-humble-clearpath-platform-msgs: 1.0.0-1 → 1.0.1-1</li> +<li>ros-humble-clearpath-platform-msgs-dbgsym: 1.0.0-1 → 1.0.1-1</li> +<li>ros-humble-clearpath-sensors-description: 0.3.4-1 → 1.0.0-1</li> +<li>ros-humble-clearpath-simulator: 0.3.0-1 → 1.0.0-1</li> +<li>ros-humble-clearpath-viz: 0.3.0-1 → 1.0.0-1</li> +<li><a href="https://control.ros.org">ros-humble-control-msgs</a>: 4.6.0-1 → 4.7.0-1</li> +<li>ros-humble-control-msgs-dbgsym: 4.6.0-1 → 4.7.0-1</li> +<li>ros-humble-controller-interface: 2.43.1-1 → 2.44.0-1</li> +<li>ros-humble-controller-interface-dbgsym: 2.43.1-1 → 2.44.0-1</li> +<li>ros-humble-controller-manager: 2.43.1-1 → 2.44.0-1</li> +<li>ros-humble-controller-manager-dbgsym: 2.43.1-1 → 2.44.0-1</li> +<li><a href="http://ros.org/wiki/controller_manager_msgs">ros-humble-controller-manager-msgs</a>: 2.43.1-1 → 2.44.0-1</li> +<li>ros-humble-controller-manager-msgs-dbgsym: 2.43.1-1 → 2.44.0-1</li> +<li>ros-humble-costmap-queue: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-costmap-queue-dbgsym: 1.1.16-1 → 1.1.17-1</li> +<li><a href="https://projects.eclipse.org/projects/iot.cyclonedds" rel="noopener nofollow ugc">ros-humble-cyclonedds</a>: 0.10.4-1 → 0.10.5-2</li> +<li>ros-humble-cyclonedds-dbgsym: 0.10.4-1 → 0.10.5-2</li> +<li>ros-humble-depthai-bridge: 2.10.3-1 → 2.10.4-1</li> +<li>ros-humble-depthai-bridge-dbgsym: 2.10.3-1 → 2.10.4-1</li> +<li>ros-humble-depthai-descriptions: 2.10.3-1 → 2.10.4-1</li> +<li>ros-humble-depthai-examples: 2.10.3-1 → 2.10.4-1</li> +<li>ros-humble-depthai-examples-dbgsym: 2.10.3-1 → 2.10.4-1</li> +<li>ros-humble-depthai-filters: 2.10.3-1 → 2.10.4-1</li> +<li>ros-humble-depthai-filters-dbgsym: 2.10.3-1 → 2.10.4-1</li> +<li>ros-humble-depthai-ros: 2.10.3-1 → 2.10.4-1</li> +<li>ros-humble-depthai-ros-driver: 2.10.3-1 → 2.10.4-1</li> +<li>ros-humble-depthai-ros-driver-dbgsym: 2.10.3-1 → 2.10.4-1</li> +<li>ros-humble-depthai-ros-msgs: 2.10.3-1 → 2.10.4-1</li> +<li>ros-humble-depthai-ros-msgs-dbgsym: 2.10.3-1 → 2.10.4-1</li> +<li>ros-humble-diff-drive-controller: 2.37.3-1 → 2.38.0-1</li> +<li>ros-humble-diff-drive-controller-dbgsym: 2.37.3-1 → 2.38.0-1</li> +<li>ros-humble-dwb-core: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-dwb-core-dbgsym: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-dwb-critics: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-dwb-critics-dbgsym: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-dwb-msgs: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-dwb-msgs-dbgsym: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-dwb-plugins: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-dwb-plugins-dbgsym: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-effort-controllers: 2.37.3-1 → 2.38.0-1</li> +<li>ros-humble-effort-controllers-dbgsym: 2.37.3-1 → 2.38.0-1</li> +<li>ros-humble-etsi-its-cam-coding: 2.3.0-1 → 2.4.0-1</li> +<li>ros-humble-etsi-its-cam-coding-dbgsym: 2.3.0-1 → 2.4.0-1</li> +<li>ros-humble-etsi-its-cam-conversion: 2.3.0-1 → 2.4.0-1</li> +<li>ros-humble-etsi-its-cam-msgs: 2.3.0-1 → 2.4.0-1</li> +<li>ros-humble-etsi-its-cam-msgs-dbgsym: 2.3.0-1 → 2.4.0-1</li> +<li>ros-humble-etsi-its-cam-ts-coding: 2.3.0-1 → 2.4.0-1</li> +<li>ros-humble-etsi-its-cam-ts-coding-dbgsym: 2.3.0-1 → 2.4.0-1</li> +<li>ros-humble-etsi-its-cam-ts-conversion: 2.3.0-1 → 2.4.0-1</li> +<li>ros-humble-etsi-its-cam-ts-msgs: 2.3.0-1 → 2.4.0-1</li> +<li>ros-humble-etsi-its-cam-ts-msgs-dbgsym: 2.3.0-1 → 2.4.0-1</li> +<li>ros-humble-etsi-its-coding: 2.3.0-1 → 2.4.0-1</li> +<li>ros-humble-etsi-its-conversion: 2.3.0-1 → 2.4.0-1</li> +<li>ros-humble-etsi-its-conversion-dbgsym: 2.3.0-1 → 2.4.0-1</li> +<li>ros-humble-etsi-its-cpm-ts-coding: 2.3.0-1 → 2.4.0-1</li> +<li>ros-humble-etsi-its-cpm-ts-coding-dbgsym: 2.3.0-1 → 2.4.0-1</li> +<li>ros-humble-etsi-its-cpm-ts-conversion: 2.3.0-1 → 2.4.0-1</li> +<li>ros-humble-etsi-its-cpm-ts-msgs: 2.3.0-1 → 2.4.0-1</li> +<li>ros-humble-etsi-its-cpm-ts-msgs-dbgsym: 2.3.0-1 → 2.4.0-1</li> +<li>ros-humble-etsi-its-denm-coding: 2.3.0-1 → 2.4.0-1</li> +<li>ros-humble-etsi-its-denm-coding-dbgsym: 2.3.0-1 → 2.4.0-1</li> +<li>ros-humble-etsi-its-denm-conversion: 2.3.0-1 → 2.4.0-1</li> +<li>ros-humble-etsi-its-denm-msgs: 2.3.0-1 → 2.4.0-1</li> +<li>ros-humble-etsi-its-denm-msgs-dbgsym: 2.3.0-1 → 2.4.0-1</li> +<li>ros-humble-etsi-its-messages: 2.3.0-1 → 2.4.0-1</li> +<li>ros-humble-etsi-its-msgs: 2.3.0-1 → 2.4.0-1</li> +<li>ros-humble-etsi-its-msgs-utils: 2.3.0-1 → 2.4.0-1</li> +<li>ros-humble-etsi-its-primitives-conversion: 2.3.0-1 → 2.4.0-1</li> +<li>ros-humble-etsi-its-rviz-plugins: 2.3.0-1 → 2.4.0-1</li> +<li>ros-humble-etsi-its-rviz-plugins-dbgsym: 2.3.0-1 → 2.4.0-1</li> +<li>ros-humble-etsi-its-vam-ts-coding: 2.3.0-1 → 2.4.0-1</li> +<li>ros-humble-etsi-its-vam-ts-coding-dbgsym: 2.3.0-1 → 2.4.0-1</li> +<li>ros-humble-etsi-its-vam-ts-conversion: 2.3.0-1 → 2.4.0-1</li> +<li>ros-humble-etsi-its-vam-ts-msgs: 2.3.0-1 → 2.4.0-1</li> +<li>ros-humble-etsi-its-vam-ts-msgs-dbgsym: 2.3.0-1 → 2.4.0-1</li> +<li>ros-humble-examples-rclcpp-async-client: 0.15.2-1 → 0.15.3-1</li> +<li>ros-humble-examples-rclcpp-async-client-dbgsym: 0.15.2-1 → 0.15.3-1</li> +<li>ros-humble-examples-rclcpp-cbg-executor: 0.15.2-1 → 0.15.3-1</li> +<li>ros-humble-examples-rclcpp-cbg-executor-dbgsym: 0.15.2-1 → 0.15.3-1</li> +<li>ros-humble-examples-rclcpp-minimal-action-client: 0.15.2-1 → 0.15.3-1</li> +<li>ros-humble-examples-rclcpp-minimal-action-client-dbgsym: 0.15.2-1 → 0.15.3-1</li> +<li>ros-humble-examples-rclcpp-minimal-action-server: 0.15.2-1 → 0.15.3-1</li> +<li>ros-humble-examples-rclcpp-minimal-action-server-dbgsym: 0.15.2-1 → 0.15.3-1</li> +<li>ros-humble-examples-rclcpp-minimal-client: 0.15.2-1 → 0.15.3-1</li> +<li>ros-humble-examples-rclcpp-minimal-client-dbgsym: 0.15.2-1 → 0.15.3-1</li> +<li>ros-humble-examples-rclcpp-minimal-composition: 0.15.2-1 → 0.15.3-1</li> +<li>ros-humble-examples-rclcpp-minimal-composition-dbgsym: 0.15.2-1 → 0.15.3-1</li> +<li>ros-humble-examples-rclcpp-minimal-publisher: 0.15.2-1 → 0.15.3-1</li> +<li>ros-humble-examples-rclcpp-minimal-publisher-dbgsym: 0.15.2-1 → 0.15.3-1</li> +<li>ros-humble-examples-rclcpp-minimal-service: 0.15.2-1 → 0.15.3-1</li> +<li>ros-humble-examples-rclcpp-minimal-service-dbgsym: 0.15.2-1 → 0.15.3-1</li> +<li>ros-humble-examples-rclcpp-minimal-subscriber: 0.15.2-1 → 0.15.3-1</li> +<li>ros-humble-examples-rclcpp-minimal-subscriber-dbgsym: 0.15.2-1 → 0.15.3-1</li> +<li>ros-humble-examples-rclcpp-minimal-timer: 0.15.2-1 → 0.15.3-1</li> +<li>ros-humble-examples-rclcpp-minimal-timer-dbgsym: 0.15.2-1 → 0.15.3-1</li> +<li>ros-humble-examples-rclcpp-multithreaded-executor: 0.15.2-1 → 0.15.3-1</li> +<li>ros-humble-examples-rclcpp-multithreaded-executor-dbgsym: 0.15.2-1 → 0.15.3-1</li> +<li>ros-humble-examples-rclcpp-wait-set: 0.15.2-1 → 0.15.3-1</li> +<li>ros-humble-examples-rclcpp-wait-set-dbgsym: 0.15.2-1 → 0.15.3-1</li> +<li>ros-humble-examples-rclpy-executors: 0.15.2-1 → 0.15.3-1</li> +<li>ros-humble-examples-rclpy-guard-conditions: 0.15.2-1 → 0.15.3-1</li> +<li>ros-humble-examples-rclpy-minimal-action-client: 0.15.2-1 → 0.15.3-1</li> +<li>ros-humble-examples-rclpy-minimal-action-server: 0.15.2-1 → 0.15.3-1</li> +<li>ros-humble-examples-rclpy-minimal-client: 0.15.2-1 → 0.15.3-1</li> +<li>ros-humble-examples-rclpy-minimal-publisher: 0.15.2-1 → 0.15.3-1</li> +<li>ros-humble-examples-rclpy-minimal-service: 0.15.2-1 → 0.15.3-1</li> +<li>ros-humble-examples-rclpy-minimal-subscriber: 0.15.2-1 → 0.15.3-1</li> +<li>ros-humble-examples-rclpy-pointcloud-publisher: 0.15.2-1 → 0.15.3-1</li> +<li>ros-humble-examples-tf2-py: 0.25.8-1 → 0.25.9-1</li> +<li><a href="https://www.eprosima.com/" rel="noopener nofollow ugc">ros-humble-fastrtps</a>: 2.6.8-1 → 2.6.9-1</li> +<li>ros-humble-fastrtps-dbgsym: 2.6.8-1 → 2.6.9-1</li> +<li>ros-humble-flir-camera-description: 2.1.17-1 → 3.0.0-1</li> +<li>ros-humble-flir-camera-msgs: 2.1.17-1 → 3.0.0-1</li> +<li>ros-humble-flir-camera-msgs-dbgsym: 2.1.17-1 → 3.0.0-1</li> +<li>ros-humble-force-torque-sensor-broadcaster: 2.37.3-1 → 2.38.0-1</li> +<li>ros-humble-force-torque-sensor-broadcaster-dbgsym: 2.37.3-1 → 2.38.0-1</li> +<li>ros-humble-forward-command-controller: 2.37.3-1 → 2.38.0-1</li> +<li>ros-humble-forward-command-controller-dbgsym: 2.37.3-1 → 2.38.0-1</li> +<li><a href="https://github.com/foxglove/ros-foxglove-bridge" rel="noopener nofollow ugc">ros-humble-foxglove-bridge</a>: 0.8.0-1 → 0.8.1-1</li> +<li>ros-humble-foxglove-bridge-dbgsym: 0.8.0-1 → 0.8.1-1</li> +<li><a href="http://www.ros.org/wiki/image_transport_plugins">ros-humble-foxglove-compressed-video-transport</a>: 1.0.0-1 → 1.0.1-1</li> +<li>ros-humble-foxglove-compressed-video-transport-dbgsym: 1.0.0-1 → 1.0.1-1</li> +<li><a href="http://www.ros.org/wiki/geometry2">ros-humble-geometry2</a>: 0.25.8-1 → 0.25.9-1</li> +<li>ros-humble-gripper-controllers: 2.37.3-1 → 2.38.0-1</li> +<li>ros-humble-gripper-controllers-dbgsym: 2.37.3-1 → 2.38.0-1</li> +<li>ros-humble-hardware-interface: 2.43.1-1 → 2.44.0-1</li> +<li>ros-humble-hardware-interface-dbgsym: 2.43.1-1 → 2.44.0-1</li> +<li>ros-humble-hardware-interface-testing: 2.43.1-1 → 2.44.0-1</li> +<li>ros-humble-hardware-interface-testing-dbgsym: 2.43.1-1 → 2.44.0-1</li> +<li><a href="http://www.ros.org/wiki/image_common">ros-humble-image-common</a>: 3.1.9-1 → 3.1.10-1</li> +<li><a href="http://ros.org/wiki/image_transport">ros-humble-image-transport</a>: 3.1.9-1 → 3.1.10-1</li> +<li>ros-humble-image-transport-dbgsym: 3.1.9-1 → 3.1.10-1</li> +<li>ros-humble-imu-sensor-broadcaster: 2.37.3-1 → 2.38.0-1</li> +<li>ros-humble-imu-sensor-broadcaster-dbgsym: 2.37.3-1 → 2.38.0-1</li> +<li>ros-humble-interactive-marker-twist-server: 2.1.0-2 → 2.1.1-1</li> +<li>ros-humble-interactive-marker-twist-server-dbgsym: 2.1.0-2 → 2.1.1-1</li> +<li><a href="https://github.com/ros-controls/ros2_control/wiki" rel="noopener nofollow ugc">ros-humble-joint-limits</a>: 2.43.1-1 → 2.44.0-1</li> +<li>ros-humble-joint-limits-dbgsym: 2.43.1-1 → 2.44.0-1</li> +<li>ros-humble-joint-state-broadcaster: 2.37.3-1 → 2.38.0-1</li> +<li>ros-humble-joint-state-broadcaster-dbgsym: 2.37.3-1 → 2.38.0-1</li> +<li>ros-humble-joint-trajectory-controller: 2.37.3-1 → 2.38.0-1</li> +<li>ros-humble-joint-trajectory-controller-dbgsym: 2.37.3-1 → 2.38.0-1</li> +<li>ros-humble-joy-teleop: 1.6.0-1 → 1.7.0-1</li> +<li>ros-humble-key-teleop: 1.6.0-1 → 1.7.0-1</li> +<li>ros-humble-launch: 1.0.6-1 → 1.0.7-1</li> +<li>ros-humble-launch-pytest: 1.0.6-1 → 1.0.7-1</li> +<li>ros-humble-launch-ros: 0.19.7-2 → 0.19.8-1</li> +<li>ros-humble-launch-testing: 1.0.6-1 → 1.0.7-1</li> +<li>ros-humble-launch-testing-ament-cmake: 1.0.6-1 → 1.0.7-1</li> +<li>ros-humble-launch-testing-examples: 0.15.2-1 → 0.15.3-1</li> +<li>ros-humble-launch-testing-ros: 0.19.7-2 → 0.19.8-1</li> +<li>ros-humble-launch-xml: 1.0.6-1 → 1.0.7-1</li> +<li>ros-humble-launch-yaml: 1.0.6-1 → 1.0.7-1</li> +<li><a href="http://wiki.ros.org/leo">ros-humble-leo</a>: 1.2.3-1 → 1.2.4-1</li> +<li><a href="http://wiki.ros.org/leo_bringup">ros-humble-leo-bringup</a>: 1.4.0-1 → 1.5.0-1</li> +<li><a href="http://wiki.ros.org/leo_description">ros-humble-leo-description</a>: 1.2.3-1 → 1.2.4-1</li> +<li><a href="http://wiki.ros.org/leo_fw">ros-humble-leo-fw</a>: 1.4.0-1 → 1.5.0-1</li> +<li>ros-humble-leo-fw-dbgsym: 1.4.0-1 → 1.5.0-1</li> +<li>ros-humble-leo-gz-bringup: 1.1.0-1 → 1.1.1-1</li> +<li>ros-humble-leo-gz-plugins: 1.1.0-1 → 1.1.1-1</li> +<li>ros-humble-leo-gz-plugins-dbgsym: 1.1.0-1 → 1.1.1-1</li> +<li>ros-humble-leo-gz-worlds: 1.1.0-1 → 1.1.1-1</li> +<li><a href="http://wiki.ros.org/leo">ros-humble-leo-msgs</a>: 1.2.3-1 → 1.2.4-1</li> +<li>ros-humble-leo-msgs-dbgsym: 1.2.3-1 → 1.2.4-1</li> +<li><a href="http://wiki.ros.org/leo_robot">ros-humble-leo-robot</a>: 1.4.0-1 → 1.5.0-1</li> +<li>ros-humble-leo-simulator: 1.1.0-1 → 1.1.1-1</li> +<li><a href="http://wiki.ros.org/leo_teleop">ros-humble-leo-teleop</a>: 1.2.3-1 → 1.2.4-1</li> +<li>ros-humble-libstatistics-collector: 1.3.2-1 → 1.3.4-1</li> +<li>ros-humble-libstatistics-collector-dbgsym: 1.3.2-1 → 1.3.4-1</li> +<li>ros-humble-mcap-vendor: 0.15.12-1 → 0.15.13-1</li> +<li>ros-humble-mcap-vendor-dbgsym: 0.15.12-1 → 0.15.13-1</li> +<li><a href="https://github.com/LORD-MicroStrain/microstrain_inertial" rel="noopener nofollow ugc">ros-humble-microstrain-inertial-description</a>: 4.4.0-1 → 4.5.0-1</li> +<li><a href="https://github.com/LORD-MicroStrain/microstrain_inertial" rel="noopener nofollow ugc">ros-humble-microstrain-inertial-driver</a>: 4.4.0-1 → 4.5.0-1</li> +<li>ros-humble-microstrain-inertial-driver-dbgsym: 4.4.0-1 → 4.5.0-1</li> +<li><a href="https://github.com/LORD-MicroStrain/microstrain_inertial" rel="noopener nofollow ugc">ros-humble-microstrain-inertial-examples</a>: 4.4.0-1 → 4.5.0-1</li> +<li><a href="https://github.com/LORD-MicroStrain/microstrain_inertial" rel="noopener nofollow ugc">ros-humble-microstrain-inertial-msgs</a>: 4.4.0-1 → 4.5.0-1</li> +<li>ros-humble-microstrain-inertial-msgs-dbgsym: 4.4.0-1 → 4.5.0-1</li> +<li><a href="https://github.com/LORD-MicroStrain/microstrain_inertial" rel="noopener nofollow ugc">ros-humble-microstrain-inertial-rqt</a>: 4.4.0-1 → 4.5.0-1</li> +<li>ros-humble-mouse-teleop: 1.6.0-1 → 1.7.0-1</li> +<li><a href="http://moveit.ros.org">ros-humble-moveit</a>: 2.5.5-1 → 2.5.6-1</li> +<li>ros-humble-moveit-chomp-optimizer-adapter: 2.5.5-1 → 2.5.6-1</li> +<li>ros-humble-moveit-chomp-optimizer-adapter-dbgsym: 2.5.5-1 → 2.5.6-1</li> +<li><a href="http://moveit.ros.org">ros-humble-moveit-common</a>: 2.5.5-1 → 2.5.6-1</li> +<li>ros-humble-moveit-configs-utils: 2.5.5-1 → 2.5.6-1</li> +<li><a href="http://moveit.ros.org">ros-humble-moveit-core</a>: 2.5.5-1 → 2.5.6-1</li> +<li>ros-humble-moveit-core-dbgsym: 2.5.5-1 → 2.5.6-1</li> +<li><a href="http://moveit.ros.org">ros-humble-moveit-hybrid-planning</a>: 2.5.5-1 → 2.5.6-1</li> +<li>ros-humble-moveit-hybrid-planning-dbgsym: 2.5.5-1 → 2.5.6-1</li> +<li><a href="http://moveit.ros.org">ros-humble-moveit-kinematics</a>: 2.5.5-1 → 2.5.6-1</li> +<li>ros-humble-moveit-kinematics-dbgsym: 2.5.5-1 → 2.5.6-1</li> +<li><a href="http://moveit.ros.org">ros-humble-moveit-planners</a>: 2.5.5-1 → 2.5.6-1</li> +<li>ros-humble-moveit-planners-chomp: 2.5.5-1 → 2.5.6-1</li> +<li>ros-humble-moveit-planners-chomp-dbgsym: 2.5.5-1 → 2.5.6-1</li> +<li><a href="http://moveit.ros.org">ros-humble-moveit-planners-ompl</a>: 2.5.5-1 → 2.5.6-1</li> +<li>ros-humble-moveit-planners-ompl-dbgsym: 2.5.5-1 → 2.5.6-1</li> +<li><a href="http://moveit.ros.org">ros-humble-moveit-plugins</a>: 2.5.5-1 → 2.5.6-1</li> +<li><a href="http://moveit.ros.org">ros-humble-moveit-resources-prbt-ikfast-manipulator-plugin</a>: 2.5.5-1 → 2.5.6-1</li> +<li>ros-humble-moveit-resources-prbt-ikfast-manipulator-plugin-dbgsym: 2.5.5-1 → 2.5.6-1</li> +<li><a href="http://moveit.ros.org">ros-humble-moveit-resources-prbt-moveit-config</a>: 2.5.5-1 → 2.5.6-1</li> +<li><a href="http://moveit.ros.org">ros-humble-moveit-resources-prbt-pg70-support</a>: 2.5.5-1 → 2.5.6-1</li> +<li><a href="http://moveit.ros.org">ros-humble-moveit-resources-prbt-support</a>: 2.5.5-1 → 2.5.6-1</li> +<li><a href="http://moveit.ros.org">ros-humble-moveit-ros</a>: 2.5.5-1 → 2.5.6-1</li> +<li><a href="http://moveit.ros.org">ros-humble-moveit-ros-benchmarks</a>: 2.5.5-1 → 2.5.6-1</li> +<li>ros-humble-moveit-ros-benchmarks-dbgsym: 2.5.5-1 → 2.5.6-1</li> +<li>ros-humble-moveit-ros-control-interface: 2.5.5-1 → 2.5.6-1</li> +<li>ros-humble-moveit-ros-control-interface-dbgsym: 2.5.5-1 → 2.5.6-1</li> +<li><a href="http://moveit.ros.org">ros-humble-moveit-ros-move-group</a>: 2.5.5-1 → 2.5.6-1</li> +<li>ros-humble-moveit-ros-move-group-dbgsym: 2.5.5-1 → 2.5.6-1</li> +<li><a href="http://moveit.ros.org">ros-humble-moveit-ros-occupancy-map-monitor</a>: 2.5.5-1 → 2.5.6-1</li> +<li>ros-humble-moveit-ros-occupancy-map-monitor-dbgsym: 2.5.5-1 → 2.5.6-1</li> +<li><a href="http://moveit.ros.org">ros-humble-moveit-ros-perception</a>: 2.5.5-1 → 2.5.6-1</li> +<li>ros-humble-moveit-ros-perception-dbgsym: 2.5.5-1 → 2.5.6-1</li> +<li><a href="http://moveit.ros.org">ros-humble-moveit-ros-planning</a>: 2.5.5-1 → 2.5.6-1</li> +<li>ros-humble-moveit-ros-planning-dbgsym: 2.5.5-1 → 2.5.6-1</li> +<li><a href="http://moveit.ros.org">ros-humble-moveit-ros-planning-interface</a>: 2.5.5-1 → 2.5.6-1</li> +<li>ros-humble-moveit-ros-planning-interface-dbgsym: 2.5.5-1 → 2.5.6-1</li> +<li><a href="http://moveit.ros.org">ros-humble-moveit-ros-robot-interaction</a>: 2.5.5-1 → 2.5.6-1</li> +<li>ros-humble-moveit-ros-robot-interaction-dbgsym: 2.5.5-1 → 2.5.6-1</li> +<li><a href="http://moveit.ros.org">ros-humble-moveit-ros-visualization</a>: 2.5.5-1 → 2.5.6-1</li> +<li>ros-humble-moveit-ros-visualization-dbgsym: 2.5.5-1 → 2.5.6-1</li> +<li><a href="http://moveit.ros.org">ros-humble-moveit-ros-warehouse</a>: 2.5.5-1 → 2.5.6-1</li> +<li>ros-humble-moveit-ros-warehouse-dbgsym: 2.5.5-1 → 2.5.6-1</li> +<li><a href="http://moveit.ros.org">ros-humble-moveit-runtime</a>: 2.5.5-1 → 2.5.6-1</li> +<li><a href="https://ros-planning.github.io/moveit_tutorials" rel="noopener nofollow ugc">ros-humble-moveit-servo</a>: 2.5.5-1 → 2.5.6-1</li> +<li>ros-humble-moveit-servo-dbgsym: 2.5.5-1 → 2.5.6-1</li> +<li>ros-humble-moveit-setup-app-plugins: 2.5.5-1 → 2.5.6-1</li> +<li>ros-humble-moveit-setup-app-plugins-dbgsym: 2.5.5-1 → 2.5.6-1</li> +<li><a href="http://moveit.ros.org">ros-humble-moveit-setup-assistant</a>: 2.5.5-1 → 2.5.6-1</li> +<li>ros-humble-moveit-setup-assistant-dbgsym: 2.5.5-1 → 2.5.6-1</li> +<li>ros-humble-moveit-setup-controllers: 2.5.5-1 → 2.5.6-1</li> +<li>ros-humble-moveit-setup-controllers-dbgsym: 2.5.5-1 → 2.5.6-1</li> +<li>ros-humble-moveit-setup-core-plugins: 2.5.5-1 → 2.5.6-1</li> +<li>ros-humble-moveit-setup-core-plugins-dbgsym: 2.5.5-1 → 2.5.6-1</li> +<li>ros-humble-moveit-setup-framework: 2.5.5-1 → 2.5.6-1</li> +<li>ros-humble-moveit-setup-framework-dbgsym: 2.5.5-1 → 2.5.6-1</li> +<li>ros-humble-moveit-setup-srdf-plugins: 2.5.5-1 → 2.5.6-1</li> +<li>ros-humble-moveit-setup-srdf-plugins-dbgsym: 2.5.5-1 → 2.5.6-1</li> +<li><a href="http://moveit.ros.org">ros-humble-moveit-simple-controller-manager</a>: 2.5.5-1 → 2.5.6-1</li> +<li>ros-humble-moveit-simple-controller-manager-dbgsym: 2.5.5-1 → 2.5.6-1</li> +<li><a href="https://github.com/MOLAorg/mp2p_icp" rel="noopener nofollow ugc">ros-humble-mp2p-icp</a>: 1.6.2-1 → 1.6.3-1</li> +<li>ros-humble-mp2p-icp-dbgsym: 1.6.2-1 → 1.6.3-1</li> +<li><a href="https://www.mrpt.org/" rel="noopener nofollow ugc">ros-humble-mrpt-apps</a>: 2.14.4-1 → 2.14.5-1</li> +<li>ros-humble-mrpt-apps-dbgsym: 2.14.4-1 → 2.14.5-1</li> +<li><a href="https://www.mrpt.org/" rel="noopener nofollow ugc">ros-humble-mrpt-libapps</a>: 2.14.4-1 → 2.14.5-1</li> +<li>ros-humble-mrpt-libapps-dbgsym: 2.14.4-1 → 2.14.5-1</li> +<li><a href="https://www.mrpt.org/" rel="noopener nofollow ugc">ros-humble-mrpt-libbase</a>: 2.14.4-1 → 2.14.5-1</li> +<li>ros-humble-mrpt-libbase-dbgsym: 2.14.4-1 → 2.14.5-1</li> +<li><a href="https://www.mrpt.org/" rel="noopener nofollow ugc">ros-humble-mrpt-libgui</a>: 2.14.4-1 → 2.14.5-1</li> +<li>ros-humble-mrpt-libgui-dbgsym: 2.14.4-1 → 2.14.5-1</li> +<li><a href="https://www.mrpt.org/" rel="noopener nofollow ugc">ros-humble-mrpt-libhwdrivers</a>: 2.14.4-1 → 2.14.5-1</li> +<li>ros-humble-mrpt-libhwdrivers-dbgsym: 2.14.4-1 → 2.14.5-1</li> +<li><a href="https://www.mrpt.org/" rel="noopener nofollow ugc">ros-humble-mrpt-libmaps</a>: 2.14.4-1 → 2.14.5-1</li> +<li>ros-humble-mrpt-libmaps-dbgsym: 2.14.4-1 → 2.14.5-1</li> +<li><a href="https://www.mrpt.org/" rel="noopener nofollow ugc">ros-humble-mrpt-libmath</a>: 2.14.4-1 → 2.14.5-1</li> +<li>ros-humble-mrpt-libmath-dbgsym: 2.14.4-1 → 2.14.5-1</li> +<li><a href="https://www.mrpt.org/" rel="noopener nofollow ugc">ros-humble-mrpt-libnav</a>: 2.14.4-1 → 2.14.5-1</li> +<li>ros-humble-mrpt-libnav-dbgsym: 2.14.4-1 → 2.14.5-1</li> +<li><a href="https://www.mrpt.org/" rel="noopener nofollow ugc">ros-humble-mrpt-libobs</a>: 2.14.4-1 → 2.14.5-1</li> +<li>ros-humble-mrpt-libobs-dbgsym: 2.14.4-1 → 2.14.5-1</li> +<li><a href="https://www.mrpt.org/" rel="noopener nofollow ugc">ros-humble-mrpt-libopengl</a>: 2.14.4-1 → 2.14.5-1</li> +<li>ros-humble-mrpt-libopengl-dbgsym: 2.14.4-1 → 2.14.5-1</li> +<li><a href="https://www.mrpt.org/" rel="noopener nofollow ugc">ros-humble-mrpt-libposes</a>: 2.14.4-1 → 2.14.5-1</li> +<li>ros-humble-mrpt-libposes-dbgsym: 2.14.4-1 → 2.14.5-1</li> +<li><a href="https://www.mrpt.org/" rel="noopener nofollow ugc">ros-humble-mrpt-libros-bridge</a>: 2.14.4-1 → 2.14.5-1</li> +<li>ros-humble-mrpt-libros-bridge-dbgsym: 2.14.4-1 → 2.14.5-1</li> +<li><a href="https://www.mrpt.org/" rel="noopener nofollow ugc">ros-humble-mrpt-libslam</a>: 2.14.4-1 → 2.14.5-1</li> +<li>ros-humble-mrpt-libslam-dbgsym: 2.14.4-1 → 2.14.5-1</li> +<li><a href="https://www.mrpt.org/" rel="noopener nofollow ugc">ros-humble-mrpt-libtclap</a>: 2.14.4-1 → 2.14.5-1</li> +<li>ros-humble-nav-2d-msgs: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav-2d-msgs-dbgsym: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav-2d-utils: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav-2d-utils-dbgsym: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-amcl: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-amcl-dbgsym: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-behavior-tree: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-behavior-tree-dbgsym: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-behaviors: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-behaviors-dbgsym: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-bringup: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-bt-navigator: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-bt-navigator-dbgsym: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-collision-monitor: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-collision-monitor-dbgsym: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-common: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-constrained-smoother: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-constrained-smoother-dbgsym: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-controller: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-controller-dbgsym: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-core: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-costmap-2d: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-costmap-2d-dbgsym: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-dwb-controller: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-graceful-controller: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-graceful-controller-dbgsym: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-lifecycle-manager: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-lifecycle-manager-dbgsym: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-map-server: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-map-server-dbgsym: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-mppi-controller: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-mppi-controller-dbgsym: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-msgs: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-msgs-dbgsym: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-navfn-planner: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-navfn-planner-dbgsym: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-planner: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-planner-dbgsym: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-regulated-pure-pursuit-controller: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-regulated-pure-pursuit-controller-dbgsym: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-rotation-shim-controller: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-rotation-shim-controller-dbgsym: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-rviz-plugins: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-rviz-plugins-dbgsym: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-simple-commander: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-smac-planner: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-smac-planner-dbgsym: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-smoother: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-smoother-dbgsym: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-system-tests: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-system-tests-dbgsym: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-theta-star-planner: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-theta-star-planner-dbgsym: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-util: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-util-dbgsym: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-velocity-smoother: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-velocity-smoother-dbgsym: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-voxel-grid: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-voxel-grid-dbgsym: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-waypoint-follower: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-nav2-waypoint-follower-dbgsym: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-navigation2: 1.1.16-1 → 1.1.17-1</li> +<li>ros-humble-novatel-gps-driver: 4.1.3-1 → 4.2.0-1</li> +<li>ros-humble-novatel-gps-driver-dbgsym: 4.1.3-1 → 4.2.0-1</li> +<li>ros-humble-novatel-gps-msgs: 4.1.3-1 → 4.2.0-1</li> +<li>ros-humble-novatel-gps-msgs-dbgsym: 4.1.3-1 → 4.2.0-1</li> +<li><a href="http://ros.org/wiki/octomap_msgs">ros-humble-octomap-msgs</a>: 2.0.0-3 → 2.0.1-1</li> +<li>ros-humble-octomap-msgs-dbgsym: 2.0.0-3 → 2.0.1-1</li> +<li>ros-humble-odom-to-tf-ros2: 1.0.2-1 → 1.0.4-1</li> +<li>ros-humble-odom-to-tf-ros2-dbgsym: 1.0.2-1 → 1.0.4-1</li> +<li>ros-humble-openni2-camera: 2.0.2-1 → 2.0.3-1</li> +<li>ros-humble-openni2-camera-dbgsym: 2.0.2-1 → 2.0.3-1</li> +<li>ros-humble-osrf-pycommon: 2.0.2-2 → 2.1.4-1</li> +<li><a href="https://github.com/pal-robotics/tiago_simulation" rel="noopener nofollow ugc">ros-humble-pal-gripper</a>: 3.3.0-1 → 3.4.0-1</li> +<li><a href="https://github.com/pal-robotics/tiago_simulation" rel="noopener nofollow ugc">ros-humble-pal-gripper-controller-configuration</a>: 3.3.0-1 → 3.4.0-1</li> +<li><a href="https://github.com/pal-robotics/tiago_simulation" rel="noopener nofollow ugc">ros-humble-pal-gripper-description</a>: 3.3.0-1 → 3.4.0-1</li> +<li>ros-humble-pal-gripper-simulation: 3.3.0-1 → 3.4.0-1</li> +<li><a href="https://github.com/pal-robotics" rel="noopener nofollow ugc">ros-humble-pal-maps</a>: 0.0.4-1 → 0.0.5-1</li> +<li><a href="https://github.com/pal-robotics/pal_statistics" rel="noopener nofollow ugc">ros-humble-pal-statistics</a>: 2.3.1-1 → 2.5.0-1</li> +<li>ros-humble-pal-statistics-dbgsym: 2.3.1-1 → 2.5.0-1</li> +<li><a href="https://github.com/pal-robotics/pal_statistics" rel="noopener nofollow ugc">ros-humble-pal-statistics-msgs</a>: 2.3.1-1 → 2.5.0-1</li> +<li>ros-humble-pal-statistics-msgs-dbgsym: 2.3.1-1 → 2.5.0-1</li> +<li>ros-humble-pid-controller: 2.37.3-1 → 2.38.0-1</li> +<li>ros-humble-pid-controller-dbgsym: 2.37.3-1 → 2.38.0-1</li> +<li><a href="http://moveit.ros.org">ros-humble-pilz-industrial-motion-planner</a>: 2.5.5-1 → 2.5.6-1</li> +<li>ros-humble-pilz-industrial-motion-planner-dbgsym: 2.5.5-1 → 2.5.6-1</li> +<li><a href="http://moveit.ros.org">ros-humble-pilz-industrial-motion-planner-testutils</a>: 2.5.5-1 → 2.5.6-1</li> +<li>ros-humble-pilz-industrial-motion-planner-testutils-dbgsym: 2.5.5-1 → 2.5.6-1</li> +<li><a href="https://github.com/pal-robotics/pmb2_simulation" rel="noopener nofollow ugc">ros-humble-pmb2-2dnav</a>: 4.2.0-1 → 4.5.0-1</li> +<li><a href="https://github.com/pal-robotics/pmb2_simulation" rel="noopener nofollow ugc">ros-humble-pmb2-bringup</a>: 5.3.1-1 → 5.4.0-1</li> +<li><a href="https://github.com/pal-robotics/pmb2_simulation" rel="noopener nofollow ugc">ros-humble-pmb2-controller-configuration</a>: 5.3.1-1 → 5.4.0-1</li> +<li><a href="https://github.com/pal-robotics/pmb2_simulation" rel="noopener nofollow ugc">ros-humble-pmb2-description</a>: 5.3.1-1 → 5.4.0-1</li> +<li><a href="https://github.com/pal-robotics/pmb2_simulation" rel="noopener nofollow ugc">ros-humble-pmb2-gazebo</a>: 4.0.16-1 → 4.1.0-1</li> +<li><a href="https://github.com/pal-robotics/pmb2_simulation" rel="noopener nofollow ugc">ros-humble-pmb2-laser-sensors</a>: 4.2.0-1 → 4.5.0-1</li> +<li><a href="https://github.com/pal-robotics/pmb2_simulation" rel="noopener nofollow ugc">ros-humble-pmb2-navigation</a>: 4.2.0-1 → 4.5.0-1</li> +<li><a href="https://github.com/pal-robotics/pmb2_simulation" rel="noopener nofollow ugc">ros-humble-pmb2-robot</a>: 5.3.1-1 → 5.4.0-1</li> +<li><a href="https://github.com/pal-robotics/pmb2_simulation" rel="noopener nofollow ugc">ros-humble-pmb2-simulation</a>: 4.0.16-1 → 4.1.0-1</li> +<li>ros-humble-position-controllers: 2.37.3-1 → 2.38.0-1</li> +<li>ros-humble-position-controllers-dbgsym: 2.37.3-1 → 2.38.0-1</li> +<li><a href="https://www.mrpt.org/" rel="noopener nofollow ugc">ros-humble-python-mrpt</a>: 2.14.4-1 → 2.14.5-1</li> +<li>ros-humble-range-sensor-broadcaster: 2.37.3-1 → 2.38.0-1</li> +<li>ros-humble-range-sensor-broadcaster-dbgsym: 2.37.3-1 → 2.38.0-1</li> +<li>ros-humble-rc-reason-clients: 0.3.1-1 → 0.4.0-2</li> +<li>ros-humble-rc-reason-msgs: 0.3.1-1 → 0.4.0-2</li> +<li>ros-humble-rc-reason-msgs-dbgsym: 0.3.1-1 → 0.4.0-2</li> +<li>ros-humble-rclcpp: 16.0.10-1 → 16.0.11-1</li> +<li>ros-humble-rclcpp-action: 16.0.10-1 → 16.0.11-1</li> +<li>ros-humble-rclcpp-action-dbgsym: 16.0.10-1 → 16.0.11-1</li> +<li>ros-humble-rclcpp-components: 16.0.10-1 → 16.0.11-1</li> +<li>ros-humble-rclcpp-components-dbgsym: 16.0.10-1 → 16.0.11-1</li> +<li>ros-humble-rclcpp-dbgsym: 16.0.10-1 → 16.0.11-1</li> +<li>ros-humble-rclcpp-lifecycle: 16.0.10-1 → 16.0.11-1</li> +<li>ros-humble-rclcpp-lifecycle-dbgsym: 16.0.10-1 → 16.0.11-1</li> +<li>ros-humble-rclpy: 3.3.14-1 → 3.3.15-1</li> +<li>ros-humble-rcpputils: 2.4.3-1 → 2.4.4-1</li> +<li>ros-humble-rcpputils-dbgsym: 2.4.3-1 → 2.4.4-1</li> +<li><a href="https://control.ros.org">ros-humble-realtime-tools</a>: 2.7.0-1 → 2.8.1-1</li> +<li>ros-humble-realtime-tools-dbgsym: 2.7.0-1 → 2.8.1-1</li> +<li>ros-humble-rmf-building-map-tools: 1.6.2-1 → 1.6.3-1</li> +<li>ros-humble-rmf-traffic-editor: 1.6.2-1 → 1.6.3-1</li> +<li>ros-humble-rmf-traffic-editor-assets: 1.6.2-1 → 1.6.3-1</li> +<li>ros-humble-rmf-traffic-editor-dbgsym: 1.6.2-1 → 1.6.3-1</li> +<li>ros-humble-rmf-traffic-editor-test-maps: 1.6.2-1 → 1.6.3-1</li> +<li>ros-humble-rmw-connextdds: 0.11.2-1 → 0.11.3-1</li> +<li>ros-humble-rmw-connextdds-common: 0.11.2-1 → 0.11.3-1</li> +<li>ros-humble-rmw-connextdds-common-dbgsym: 0.11.2-1 → 0.11.3-1</li> +<li>ros-humble-rmw-connextdds-dbgsym: 0.11.2-1 → 0.11.3-1</li> +<li><a href="http://ros.org/wiki/robot_calibration">ros-humble-robot-calibration</a>: 0.8.1-1 → 0.8.2-1</li> +<li>ros-humble-robot-calibration-dbgsym: 0.8.1-1 → 0.8.2-1</li> +<li><a href="http://ros.org/wiki/robot_calibration_msgs">ros-humble-robot-calibration-msgs</a>: 0.8.1-1 → 0.8.2-1</li> +<li>ros-humble-robot-calibration-msgs-dbgsym: 0.8.1-1 → 0.8.2-1</li> +<li><a href="https://control.ros.org">ros-humble-ros2-control</a>: 2.43.1-1 → 2.44.0-1</li> +<li>ros-humble-ros2-control-test-assets: 2.43.1-1 → 2.44.0-1</li> +<li><a href="https://control.ros.org">ros-humble-ros2-controllers</a>: 2.37.3-1 → 2.38.0-1</li> +<li>ros-humble-ros2-controllers-test-nodes: 2.37.3-1 → 2.38.0-1</li> +<li>ros-humble-ros2bag: 0.15.12-1 → 0.15.13-1</li> +<li>ros-humble-ros2controlcli: 2.43.1-1 → 2.44.0-1</li> +<li>ros-humble-ros2launch: 0.19.7-2 → 0.19.8-1</li> +<li>ros-humble-rosbag2: 0.15.12-1 → 0.15.13-1</li> +<li>ros-humble-rosbag2-compression: 0.15.12-1 → 0.15.13-1</li> +<li>ros-humble-rosbag2-compression-dbgsym: 0.15.12-1 → 0.15.13-1</li> +<li>ros-humble-rosbag2-compression-zstd: 0.15.12-1 → 0.15.13-1</li> +<li>ros-humble-rosbag2-compression-zstd-dbgsym: 0.15.12-1 → 0.15.13-1</li> +<li>ros-humble-rosbag2-cpp: 0.15.12-1 → 0.15.13-1</li> +<li>ros-humble-rosbag2-cpp-dbgsym: 0.15.12-1 → 0.15.13-1</li> +<li>ros-humble-rosbag2-interfaces: 0.15.12-1 → 0.15.13-1</li> +<li>ros-humble-rosbag2-interfaces-dbgsym: 0.15.12-1 → 0.15.13-1</li> +<li>ros-humble-rosbag2-performance-benchmarking: 0.15.12-1 → 0.15.13-1</li> +<li>ros-humble-rosbag2-py: 0.15.12-1 → 0.15.13-1</li> +<li>ros-humble-rosbag2-storage: 0.15.12-1 → 0.15.13-1</li> +<li>ros-humble-rosbag2-storage-dbgsym: 0.15.12-1 → 0.15.13-1</li> +<li>ros-humble-rosbag2-storage-default-plugins: 0.15.12-1 → 0.15.13-1</li> +<li>ros-humble-rosbag2-storage-default-plugins-dbgsym: 0.15.12-1 → 0.15.13-1</li> +<li>ros-humble-rosbag2-storage-mcap: 0.15.12-1 → 0.15.13-1</li> +<li>ros-humble-rosbag2-storage-mcap-dbgsym: 0.15.12-1 → 0.15.13-1</li> +<li>ros-humble-rosbag2-storage-mcap-testdata: 0.15.12-1 → 0.15.13-1</li> +<li>ros-humble-rosbag2-storage-mcap-testdata-dbgsym: 0.15.12-1 → 0.15.13-1</li> +<li>ros-humble-rosbag2-test-common: 0.15.12-1 → 0.15.13-1</li> +<li>ros-humble-rosbag2-tests: 0.15.12-1 → 0.15.13-1</li> +<li>ros-humble-rosbag2-transport: 0.15.12-1 → 0.15.13-1</li> +<li>ros-humble-rosbag2-transport-dbgsym: 0.15.12-1 → 0.15.13-1</li> +<li>ros-humble-rosidl-adapter: 3.1.5-2 → 3.1.6-1</li> +<li>ros-humble-rosidl-cli: 3.1.5-2 → 3.1.6-1</li> +<li>ros-humble-rosidl-cmake: 3.1.5-2 → 3.1.6-1</li> +<li>ros-humble-rosidl-generator-c: 3.1.5-2 → 3.1.6-1</li> +<li>ros-humble-rosidl-generator-cpp: 3.1.5-2 → 3.1.6-1</li> +<li>ros-humble-rosidl-parser: 3.1.5-2 → 3.1.6-1</li> +<li>ros-humble-rosidl-runtime-c: 3.1.5-2 → 3.1.6-1</li> +<li>ros-humble-rosidl-runtime-c-dbgsym: 3.1.5-2 → 3.1.6-1</li> +<li>ros-humble-rosidl-runtime-cpp: 3.1.5-2 → 3.1.6-1</li> +<li>ros-humble-rosidl-typesupport-c: 2.0.1-1 → 2.0.2-1</li> +<li>ros-humble-rosidl-typesupport-c-dbgsym: 2.0.1-1 → 2.0.2-1</li> +<li>ros-humble-rosidl-typesupport-cpp: 2.0.1-1 → 2.0.2-1</li> +<li>ros-humble-rosidl-typesupport-cpp-dbgsym: 2.0.1-1 → 2.0.2-1</li> +<li>ros-humble-rosidl-typesupport-interface: 3.1.5-2 → 3.1.6-1</li> +<li>ros-humble-rosidl-typesupport-introspection-c: 3.1.5-2 → 3.1.6-1</li> +<li>ros-humble-rosidl-typesupport-introspection-c-dbgsym: 3.1.5-2 → 3.1.6-1</li> +<li>ros-humble-rosidl-typesupport-introspection-cpp: 3.1.5-2 → 3.1.6-1</li> +<li>ros-humble-rosidl-typesupport-introspection-cpp-dbgsym: 3.1.5-2 → 3.1.6-1</li> +<li><a href="http://ros.org/wiki/rqt_controller_manager">ros-humble-rqt-controller-manager</a>: 2.43.1-1 → 2.44.0-1</li> +<li>ros-humble-rqt-joint-trajectory-controller: 2.37.3-1 → 2.38.0-1</li> +<li>ros-humble-rti-connext-dds-cmake-module: 0.11.2-1 → 0.11.3-1</li> +<li><a href="http://assimp.sourceforge.net/index.html" rel="noopener nofollow ugc">ros-humble-rviz-assimp-vendor</a>: 11.2.13-1 → 11.2.14-1</li> +<li><a href="https://github.com/ros2/rviz/blob/ros2/README.md" rel="noopener nofollow ugc">ros-humble-rviz-common</a>: 11.2.13-1 → 11.2.14-1</li> +<li>ros-humble-rviz-common-dbgsym: 11.2.13-1 → 11.2.14-1</li> +<li><a href="https://github.com/ros2/rviz/blob/ros2/README.md" rel="noopener nofollow ugc">ros-humble-rviz-default-plugins</a>: 11.2.13-1 → 11.2.14-1</li> +<li>ros-humble-rviz-default-plugins-dbgsym: 11.2.13-1 → 11.2.14-1</li> +<li><a href="https://www.ogre3d.org/" rel="noopener nofollow ugc">ros-humble-rviz-ogre-vendor</a>: 11.2.13-1 → 11.2.14-1</li> +<li>ros-humble-rviz-ogre-vendor-dbgsym: 11.2.13-1 → 11.2.14-1</li> +<li><a href="https://github.com/ros2/rviz/blob/ros2/README.md" rel="noopener nofollow ugc">ros-humble-rviz-rendering</a>: 11.2.13-1 → 11.2.14-1</li> +<li>ros-humble-rviz-rendering-dbgsym: 11.2.13-1 → 11.2.14-1</li> +<li>ros-humble-rviz-rendering-tests: 11.2.13-1 → 11.2.14-1</li> +<li><a href="http://ros.org/wiki/rviz2">ros-humble-rviz-visual-testing-framework</a>: 11.2.13-1 → 11.2.14-1</li> +<li><a href="https://github.com/ros2/rviz/blob/ros2/README.md" rel="noopener nofollow ugc">ros-humble-rviz2</a>: 11.2.13-1 → 11.2.14-1</li> +<li>ros-humble-rviz2-dbgsym: 11.2.13-1 → 11.2.14-1</li> +<li>ros-humble-shared-queues-vendor: 0.15.12-1 → 0.15.13-1</li> +<li>ros-humble-spinnaker-camera-driver: 2.1.17-1 → 3.0.0-1</li> +<li>ros-humble-spinnaker-camera-driver-dbgsym: 2.1.17-1 → 3.0.0-1</li> +<li>ros-humble-spinnaker-synchronized-camera-driver: 2.1.17-1 → 3.0.0-1</li> +<li>ros-humble-spinnaker-synchronized-camera-driver-dbgsym: 2.1.17-1 → 3.0.0-1</li> +<li>ros-humble-sqlite3-vendor: 0.15.12-1 → 0.15.13-1</li> +<li>ros-humble-steering-controllers-library: 2.37.3-1 → 2.38.0-1</li> +<li>ros-humble-steering-controllers-library-dbgsym: 2.37.3-1 → 2.38.0-1</li> +<li>ros-humble-teleop-tools: 1.6.0-1 → 1.7.0-1</li> +<li>ros-humble-teleop-tools-msgs: 1.6.0-1 → 1.7.0-1</li> +<li>ros-humble-teleop-tools-msgs-dbgsym: 1.6.0-1 → 1.7.0-1</li> +<li><a href="http://www.ros.org/wiki/tf2">ros-humble-tf2</a>: 0.25.8-1 → 0.25.9-1</li> +<li><a href="http://www.ros.org/wiki/tf2_bullet">ros-humble-tf2-bullet</a>: 0.25.8-1 → 0.25.9-1</li> +<li>ros-humble-tf2-dbgsym: 0.25.8-1 → 0.25.9-1</li> +<li>ros-humble-tf2-eigen: 0.25.8-1 → 0.25.9-1</li> +<li>ros-humble-tf2-eigen-kdl: 0.25.8-1 → 0.25.9-1</li> +<li>ros-humble-tf2-eigen-kdl-dbgsym: 0.25.8-1 → 0.25.9-1</li> +<li><a href="http://www.ros.org/wiki/tf2_ros">ros-humble-tf2-geometry-msgs</a>: 0.25.8-1 → 0.25.9-1</li> +<li><a href="http://ros.org/wiki/tf2">ros-humble-tf2-kdl</a>: 0.25.8-1 → 0.25.9-1</li> +<li><a href="http://www.ros.org/wiki/tf2_msgs">ros-humble-tf2-msgs</a>: 0.25.8-1 → 0.25.9-1</li> +<li>ros-humble-tf2-msgs-dbgsym: 0.25.8-1 → 0.25.9-1</li> +<li><a href="http://ros.org/wiki/tf2_py">ros-humble-tf2-py</a>: 0.25.8-1 → 0.25.9-1</li> +<li>ros-humble-tf2-py-dbgsym: 0.25.8-1 → 0.25.9-1</li> +<li><a href="http://www.ros.org/wiki/tf2_ros">ros-humble-tf2-ros</a>: 0.25.8-1 → 0.25.9-1</li> +<li>ros-humble-tf2-ros-dbgsym: 0.25.8-1 → 0.25.9-1</li> +<li><a href="http://www.ros.org/wiki/tf2_ros">ros-humble-tf2-ros-py</a>: 0.25.8-1 → 0.25.9-1</li> +<li><a href="http://www.ros.org/wiki/tf2_ros">ros-humble-tf2-sensor-msgs</a>: 0.25.8-1 → 0.25.9-1</li> +<li><a href="http://www.ros.org/wiki/tf2_tools">ros-humble-tf2-tools</a>: 0.25.8-1 → 0.25.9-1</li> +<li><a href="https://github.com/pal-robotics/tiago_simulation" rel="noopener nofollow ugc">ros-humble-tiago-2dnav</a>: 4.2.0-1 → 4.5.0-1</li> +<li><a href="https://github.com/pal-robotics/tiago_simulation" rel="noopener nofollow ugc">ros-humble-tiago-bringup</a>: 4.6.0-1 → 4.7.1-1</li> +<li><a href="https://github.com/pal-robotics/tiago_simulation" rel="noopener nofollow ugc">ros-humble-tiago-controller-configuration</a>: 4.6.0-1 → 4.7.1-1</li> +<li><a href="https://github.com/pal-robotics/tiago_simulation" rel="noopener nofollow ugc">ros-humble-tiago-description</a>: 4.6.0-1 → 4.7.1-1</li> +<li><a href="https://github.com/pal-robotics/tiago_simulation" rel="noopener nofollow ugc">ros-humble-tiago-gazebo</a>: 4.2.0-1 → 4.3.0-1</li> +<li>ros-humble-tiago-gazebo-dbgsym: 4.2.0-1 → 4.3.0-1</li> +<li><a href="https://github.com/pal-robotics/tiago_simulation" rel="noopener nofollow ugc">ros-humble-tiago-laser-sensors</a>: 4.2.0-1 → 4.5.0-1</li> +<li><a href="https://github.com/pal-robotics/tiago_simulation" rel="noopener nofollow ugc">ros-humble-tiago-moveit-config</a>: 3.1.0-1 → 3.1.1-1</li> +<li><a href="https://github.com/pal-robotics/tiago_simulation" rel="noopener nofollow ugc">ros-humble-tiago-navigation</a>: 4.2.0-1 → 4.5.0-1</li> +<li><a href="https://github.com/pal-robotics/tiago_simulation" rel="noopener nofollow ugc">ros-humble-tiago-robot</a>: 4.6.0-1 → 4.7.1-1</li> +<li><a href="https://github.com/pal-robotics/tiago_simulation" rel="noopener nofollow ugc">ros-humble-tiago-simulation</a>: 4.2.0-1 → 4.3.0-1</li> +<li>ros-humble-transmission-interface: 2.43.1-1 → 2.44.0-1</li> +<li>ros-humble-transmission-interface-dbgsym: 2.43.1-1 → 2.44.0-1</li> +<li>ros-humble-tricycle-controller: 2.37.3-1 → 2.38.0-1</li> +<li>ros-humble-tricycle-controller-dbgsym: 2.37.3-1 → 2.38.0-1</li> +<li>ros-humble-tricycle-steering-controller: 2.37.3-1 → 2.38.0-1</li> +<li>ros-humble-tricycle-steering-controller-dbgsym: 2.37.3-1 → 2.38.0-1</li> +<li>ros-humble-twist-stamper: 0.0.3-1 → 0.0.5-1</li> +<li><a href="http://wiki.ros.org/ur_client_library">ros-humble-ur-client-library</a>: 1.4.0-1 → 1.5.0-1</li> +<li>ros-humble-ur-client-library-dbgsym: 1.4.0-1 → 1.5.0-1</li> +<li>ros-humble-velocity-controllers: 2.37.3-1 → 2.38.0-1</li> +<li>ros-humble-velocity-controllers-dbgsym: 2.37.3-1 → 2.38.0-1</li> +<li><a href="https://facebook.github.io/zstd/" rel="noopener nofollow ugc">ros-humble-zstd-vendor</a>: 0.15.12-1 → 0.15.13-1</li> +</ul> +<h3><a class="anchor" href="https://discourse.ros.org#p-88326-removed-packages-6-4" name="p-88326-removed-packages-6-4"></a>Removed Packages [6]:</h3> +<ul> +<li>ros-humble-clearpath-platform</li> +<li>ros-humble-clearpath-platform-dbgsym</li> +<li><a href="https://www.mrpt.org/" rel="noopener nofollow ugc">ros-humble-mrpt2</a></li> +<li>ros-humble-mrpt2-dbgsym</li> +<li>ros-humble-omni-base-maps</li> +<li><a href="https://github.com/swri-robotics/marti_common" rel="noopener nofollow ugc">ros-humble-swri-prefix-tools</a></li> +</ul> +<p>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:</p> +<ul> +<li>Adam Serafin</li> +<li>Aditya Pande</li> +<li>Aina Irisarri</li> +<li>Alberto Tudela</li> +<li>Alejandro Hernandez Cordero</li> +<li>Alexander Gutenkunst</li> +<li>Alexey Merzlyakov</li> +<li>Analog Devices</li> +<li>Andrea Sorbini</li> +<li>Antonio Brandi</li> +<li>Bence Magyar</li> +<li>Bernd Pfrommer</li> +<li>Blake Anderson</li> +<li>Brandon Ong</li> +<li>Brian Wilcox</li> +<li>Błażej Sowa</li> +<li>Carl Delsey</li> +<li>Carlos Orduno</li> +<li>Chittaranjan Srinivas Swaminathan</li> +<li>Chris Iverach-Brereton</li> +<li>Chris Lalancette</li> +<li>Christian Henkel</li> +<li>Christian Rauch</li> +<li>David V. Lu!!</li> +<li>Denis Štogl</li> +<li>Eclipse Foundation, Inc.</li> +<li>Enrique Fernandez</li> +<li>Evan Flynn</li> +<li>Felix Exner</li> +<li>Felix Ruess</li> +<li>Fictionlab</li> +<li>Foxglove</li> +<li>George Stavrinos</li> +<li>Hans-Joachim Krauch</li> +<li>Henning Kayser</li> +<li>Ivan Paunovic</li> +<li>Jacob Perron</li> +<li>Jafar Uruc</li> +<li>Jean-Pierre Busch</li> +<li>Jordan Palacios</li> +<li>Jordi Pages</li> +<li>Jose Mastrangelo</li> +<li>Jose-Luis Blanco-Claraco</li> +<li>Josh Newans</li> +<li>Luis Camero</li> +<li>Luka Juricic</li> +<li>Mamoru Sobue</li> +<li>Marc Alban</li> +<li>Matej Vargovcik</li> +<li>Michael Ferguson</li> +<li>Michael Görner</li> +<li>Michael Jeronimo</li> +<li>Michael Orlov</li> +<li>Michel Hidalgo</li> +<li>Miguel Company</li> +<li>Mike Purvis</li> +<li>Mohammad Haghighipanah</li> +<li>Morgan Quigley</li> +<li>MoveIt Release Team</li> +<li>P. J. Reed</li> +<li>ROS Tooling Working Group</li> +<li>Raghavender Sahdev</li> +<li>Ralph Lange</li> +<li>Rob Fisher</li> +<li>Robert Wilbrandt</li> +<li>Roni Kreinin</li> +<li>STEREOLABS</li> +<li>Shane Loretz</li> +<li>Stefan Laible</li> +<li>Steve Macenski</li> +<li>Séverin Lemaignan</li> +<li>TIAGo PAL support team</li> +<li>TIAGo support team</li> +<li>Tony Baltovski</li> +<li>Victor López</li> +<li>William Woodall</li> +<li>Wolfgang Merkt</li> +<li>mitsudome-r</li> +<li>pradyum</li> +<li>ruess</li> +<li>steve</li> +</ul> + <p><small>1 post - 1 participant</small></p> + <p><a href="https://discourse.ros.org/t/new-packages-and-patch-release-for-humble-hawksbill-2024-12-05/40976">Read full topic</a></p> + Thu, 05 Dec 2024 20:17:28 +0000 + + + ROS Discourse General: Clearpath Simulator comes to Gazebo Harmonic :fire: + discourse.ros.org-topic-40975 + https://discourse.ros.org/t/clearpath-simulator-comes-to-gazebo-harmonic/40975 + <p>Hello everyone,</p> +<p>I have successfully ported Clearpath Robotics’s open-source simulator <a href="https://github.com/clearpathrobotics/clearpath_simulator" rel="noopener nofollow ugc">clearpath_simulator</a> into <strong>Gazebo Harmonic LTS</strong>.</p> +<p>Key changes include adding support for Xbox One controllers, support for custom <code>robot.yaml</code> names and automatic Twist message conversion to TwistStamped required by the newer builds of <code>ros2_controllers</code> and Gazebo. The simulator has been tested to work in Ubuntu 22.04 (source build). Presently, only <strong>A200 Husky</strong> is supported. Version 0.2 will add RGB-D sensor and build testing in Ubuntu 24.04.</p> +<p></p><div class="lightbox-wrapper"><a class="lightbox" href="https://global.discourse-cdn.com/flex022/uploads/ros/original/3X/b/e/be3b8e0353f1e6c5a73f53dc6a6c73f7d041a9ea.jpeg" rel="noopener nofollow ugc" title="image"><img alt="image" height="428" src="https://global.discourse-cdn.com/flex022/uploads/ros/optimized/3X/b/e/be3b8e0353f1e6c5a73f53dc6a6c73f7d041a9ea_2_690x428.jpeg" width="690" /></a></div><p></p> +<p>To accommodate a number of changes made to almost all the original dependent packages, I have opted to host my derived work separately here: <a class="inline-onebox" href="https://github.com/Mechazo11/clearpath_simulator_harmonic" rel="noopener nofollow ugc">GitHub - Mechazo11/clearpath_simulator_harmonic: A port of Clearpath Simulator, compatible with ROS 2 Jazzy and Gazebo Harmonic</a></p> +<p>A big shout-out to <strong>Clearpath Robotics</strong> team for making the original simulator publicly available. I hope this work proves valuable to the community. If you have any questions, concerns or would like to contribute please don’t hesitate to reaching out to me.</p> +<p>With best regards,<br /> +Azmyin Md. Kamal</p> + <p><small>1 post - 1 participant</small></p> + <p><a href="https://discourse.ros.org/t/clearpath-simulator-comes-to-gazebo-harmonic/40975">Read full topic</a></p> + Thu, 05 Dec 2024 19:42:05 +0000 + + + ROS Discourse General: Expose secure communication only with specified entities + discourse.ros.org-topic-40957 + https://discourse.ros.org/t/expose-secure-communication-only-with-specified-entities/40957 + <p>Hi ROS developers,</p> +<p>Asking thoughts and ideas!</p> +<p>I think this is more like discussion to explore than a question, I would like to have feedback from the community how to handle this situation to support 3rd party device.</p> +<p>Original issue: <a class="inline-onebox" href="https://github.com/ros2/sros2/issues/326" rel="noopener nofollow ugc">Expose secure communication only with specified entities. · Issue #326 · ros2/sros2 · GitHub</a></p> +<p></p><div class="lightbox-wrapper"><a class="lightbox" href="https://global.discourse-cdn.com/flex022/uploads/ros/original/3X/3/5/35632153b9d04cd824e0e77b298998b5e16cc7e7.png" rel="noopener nofollow ugc" title="image"><img alt="image" height="385" src="https://global.discourse-cdn.com/flex022/uploads/ros/optimized/3X/3/5/35632153b9d04cd824e0e77b298998b5e16cc7e7_2_690x385.png" width="690" /></a></div><p></p> +<ul> +<li>For performance consideration, it would be better to keep the localhost communication in robot without secured authentication nor encryption. (basically it uses localhost in robot system, but some specific nodes to be exposed.)</li> +</ul> +<p>I am trying to find out what could be best solution to support above requirement with secured communication with sros2.</p> +<p>If you have any experience, please enlighten me <img alt=":pray:" class="emoji" height="20" src="https://emoji.discourse-cdn.com/twitter/pray.png?v=12" title=":pray:" width="20" /> <img alt=":pray:" class="emoji" height="20" src="https://emoji.discourse-cdn.com/twitter/pray.png?v=12" title=":pray:" width="20" /> <img alt=":pray:" class="emoji" height="20" src="https://emoji.discourse-cdn.com/twitter/pray.png?v=12" title=":pray:" width="20" /></p> +<p>Regards,<br /> +Tomoya</p> + <p><small>6 posts - 3 participants</small></p> + <p><a href="https://discourse.ros.org/t/expose-secure-communication-only-with-specified-entities/40957">Read full topic</a></p> + Wed, 04 Dec 2024 22:10:01 +0000 + + + ROS Discourse General: Next Client Library WG Meeting: Friday 6th December 2024 8AM PT + discourse.ros.org-topic-40954 + https://discourse.ros.org/t/next-client-library-wg-meeting-friday-6th-december-2024-8am-pt/40954 + <p>Hi,<br /> +The next meeting of the Client Library Working Group will be this Friday, 6th December 2024 at 8 AM Pacific Time.</p> +<ul> +<li>Meeting link: <a href="https://meet.google.com/oij-atzj-znw" rel="noopener nofollow ugc">https://meet.google.com/oij-atzj-znw </a></li> +<li>Calendar invite: <a href="https://calendar.app.google/WDSVtbpSu5SrNc1Q8" rel="noopener nofollow ugc">https://calendar.app.google/WDSVtbpSu5SrNc1Q8</a></li> +<li>Google group if you want to be notified of future meetings: <a href="https://groups.google.com/g/ros-2-client-library-wg" rel="noopener nofollow ugc">https://groups.google.com/g/ros-2-client-library-wg</a></li> +</ul> +<p>We will be reviewing the charter proposal for the ROS 2 Client Library Working Group and continue the discussions from the previous meetings.</p> + <p><small>2 posts - 1 participant</small></p> + <p><a href="https://discourse.ros.org/t/next-client-library-wg-meeting-friday-6th-december-2024-8am-pt/40954">Read full topic</a></p> + Wed, 04 Dec 2024 18:12:58 +0000 + + + ROS Discourse General: Call for Participation: ROS Deliberation Community Group + discourse.ros.org-topic-40932 + https://discourse.ros.org/t/call-for-participation-ros-deliberation-community-group/40932 + <p>Hello all,</p> +<p>After our <a href="https://github.com/ros-wg-delib/roscon24-workshop" rel="noopener nofollow ugc">successful workshop</a> at ROSCon 2024, the <a href="https://github.com/ros-wg-delib" rel="noopener nofollow ugc">ROS Deliberation Community Group</a> is resuming its focus on monthly meetings to engage with the community.</p> +<p>For those who were formerly attending the meetings before we spent time preparing for the workshop, the time is right to start attending again! If you are considering attending for the first time, or have never heard of this Community Group before, we look forward to seeing you as well.</p> +<p>Either way, we’d like to hear from you all about possible topics for subsequent meetings in the new year. Some initial ideas:</p> +<ul> +<li>Putting together a survey document of ROS 2 Deliberation Technologies, very much inspired by the great <a href="https://arxiv.org/abs/2307.15236" rel="noopener nofollow ugc">Nav2 paper</a>.</li> +<li>Collaborating on the development of open-source software tools, or examples using those tools, for robot deliberation.</li> +<li>Presentations from people interested in sharing their work (though we’d like to also have time for working discussions as well).</li> +</ul> +<p>If anyone wants to share ideas or ask any questions, feel free to post here, or just show up to the next meeting(s)! You can find more information, including how to sign up in <a href="https://docs.google.com/document/d/13TCHp3ycbDa2agGs0SjP3CpTllUeguAcXqih5LlCVDg/edit?tab=t.0#heading=h.lnamemvhhzoa" rel="noopener nofollow ugc">this document</a>.</p> + <p><small>3 posts - 2 participants</small></p> + <p><a href="https://discourse.ros.org/t/call-for-participation-ros-deliberation-community-group/40932">Read full topic</a></p> + Tue, 03 Dec 2024 02:00:55 +0000 + + + ROS Discourse General: Gazebo Classic and Citadel End of Life [x-post Gazebo Sim Community] + discourse.ros.org-topic-40931 + https://discourse.ros.org/t/gazebo-classic-and-citadel-end-of-life-x-post-gazebo-sim-community/40931 + <p><a href="https://community.gazebosim.org/t/gazebo-classic-and-citadel-end-of-life/3242">Original Post</a></p> +<p>Hi Everyone,</p> +<p>This is your friendly reminder that as outlined here Gazebo Classic (i.e. Gazebo 11) <a href="https://classic.gazebosim.org/#status">will officially go end of life on Friday, January 31st, 2025</a>. Gazebo Citadel, our first modern Gazebo LTS release, will go end of life on December 30th, 2024. Gazebo Classic users are advised to transition to an LTS modern Gazebo release as soon as possible (we recommend <a href="https://gazebosim.org/docs/harmonic/install_ubuntu/">Gazebo Harmonic</a>, or <a href="https://gazebosim.org/docs/fortress/install_ubuntu/">Gazebo Fortress</a>). We recommend that Gazebo Citadel users also upgrade to either Harmonic or Fortress. Information about currently supported Gazebo versions and support windows, <a href="https://gazebosim.org/docs/latest/releases/">can be found here</a>.</p> +<h3><a class="anchor" href="https://discourse.ros.org#p-88253-what-does-end-of-life-mean-1" name="p-88253-what-does-end-of-life-mean-1"></a>What does End of Life Mean?</h3> +<p>Users often ask us, “what does end of life mean?” To put it briefly, end of life means that the Gazebo team will no longer support that particular Gazebo release. In practical terms, this means that we will no longer be providing the following for Gazebo Classic:</p> +<ul> +<li>New features or capabilities</li> +<li>Security updates</li> +<li>Bug fixes, patches or support</li> +<li>Updated binaries</li> +</ul> +<p>It is also worth noting the things that won’t change after Gazebo Classic goes end of life:</p> +<ul> +<li>Gazebo Classic binaries will not suddenly disappear</li> +<li>Users will not need to migrate immediately, but they should migrate as soon as possible</li> +<li>Your project will not suddenly stop working on January 31st</li> +</ul> +<h3><a class="anchor" href="https://discourse.ros.org#p-88253-why-do-we-end-of-life-gazebo-releases-2" name="p-88253-why-do-we-end-of-life-gazebo-releases-2"></a>Why do we End of Life Gazebo releases?</h3> +<p>We End of Life particular Gazebo releases for the same reason that most people don’t use Windows XP or an iPhone 4 anymore: better versions of the software are now available and we simply don’t have the resources to support every Gazebo release into perpetuity. Marking a particular version of Gazebo end of life frees up resources to help support newer and better versions of the software. More to the point, the underlying packages and operating system (<a href="https://wiki.ubuntu.com/Releases">Ubuntu Focal</a>) used by Gazebo Classic also goes end of life in April 2025.</p> +<h3><a class="anchor" href="https://discourse.ros.org#p-88253-how-do-i-upgrade-to-a-newer-version-of-gazebo-and-which-one-should-i-use-3" name="p-88253-how-do-i-upgrade-to-a-newer-version-of-gazebo-and-which-one-should-i-use-3"></a>How do I upgrade to a newer version of Gazebo and which one should I use?</h3> +<p>We recommend that Gazebo Classic users upgrade to the latest long term support release of modern Gazebo, <a href="https://gazebosim.org/docs/harmonic/install_ubuntu/">Gazebo Harmonic</a>. Gazebo Harmonic works best on Ubuntu Jammy (22.04) and Ubuntu Noble (24.04) and will be supported until September of 2028. Gazebo Classic users who still use ROS 1 will also need to upgrade to ROS 2 Jazzy to use Gazebo Harmonic. It is worth noting that all of ROS 1, including ROS 1 Noetic, will go end of life on May 23rd, 2025. Our internal estimates indicate that over 80% of the ROS community has already upgraded to ROS 2, and 67% of Gazebo users have already upgraded to modern Gazebo.</p> +<p>The modern Gazebo documentation includes a variety of guides and tutorials on how to <a href="https://gazebosim.org/docs/harmonic/gazebo_classic_migration/">migrate your project from Gazebo Classic to modern Gazebo.</a> Similarly, the ROS 2 documentation provides <a href="https://docs.ros.org/en/jazzy/How-To-Guides/Migrating-from-ROS1.html">step by step instructions on how to migrate your ROS 1 project to ROS 2</a>. If you get stuck during migration, we would encourage you to use the <a href="https://discord.com/servers/open-robotics-1077825543698927656">Open Robotics Discord</a>, the <a href="https://community.gazebosim.org/">Gazebo Sim Community</a>, and <a href="https://community.gazebosim.org/">Robotics Stack Exchange</a> to find help.</p> +<h3><a class="anchor" href="https://discourse.ros.org#p-88253-help-spread-the-word-4" name="p-88253-help-spread-the-word-4"></a>Help Spread the Word</h3> +<p>We realize that many Gazebo Classic users don’t really track Gazebo end of life dates, or regularly visit Gazebosim Community, that’s why we’ve decided to include some notifications about Gazebo Classic’s impending end of life in our latest Gazebo Classic update. Starting this week, after<a href="https://github.com/gazebosim/gazebo-classic/blob/gazebo11/Changelog.md#gazebo-11150-2024-11-26"> updating Gazebo Classic</a> users will be <a href="https://github.com/gazebosim/gazebo-classic/pull/3405">notified via debug output and pop-ups of the upcoming end of life date</a>. These warnings can be suppressed by simply setting a “GAZEBO_SUPPRESS_EOL_WARNING” environment variable.</p> +<p>We would appreciate the community’s help in spreading the word about the upcoming Gazebo Classic End of Life. If you work on a team that is still using Gazebo Classic please take a moment in the next week or two to discuss upgrade paths with your team and the importance of upgrading as soon as possible.</p> + <p><small>2 posts - 1 participant</small></p> + <p><a href="https://discourse.ros.org/t/gazebo-classic-and-citadel-end-of-life-x-post-gazebo-sim-community/40931">Read full topic</a></p> + Mon, 02 Dec 2024 22:01:50 +0000 + + + ROS Discourse General: What versions of Moveit 2 are people using? + discourse.ros.org-topic-40908 + https://discourse.ros.org/t/what-versions-of-moveit-2-are-people-using/40908 + <p>I’ve posted a poll on the Moveit 2 discussions board asking for feedback regarding which versions people are using, as it seems like it’d be interesting to gather some quantitative data.</p> +<p>Figured I’d post it here, too, for more visibility:</p> +<aside class="onebox allowlistedgeneric"> + <header class="source"> + <img class="site-icon" height="32" src="https://global.discourse-cdn.com/flex022/uploads/ros/original/2X/b/bad3e5f9ad67c1ddf145107ce7032ac1d7b22563.svg" width="32" /> + + <a href="https://github.com/orgs/moveit/discussions/3138" rel="noopener nofollow ugc" target="_blank">GitHub</a> + </header> + + <article class="onebox-body"> + <div class="aspect-image"><img class="thumbnail" height="345" src="https://global.discourse-cdn.com/flex022/uploads/ros/optimized/3X/8/a/8a3acef9f83f7dd78ad168763cf690a2ad9d4439_2_690x345.png" width="690" /></div> + +<h3><a href="https://github.com/orgs/moveit/discussions/3138" rel="noopener nofollow ugc" target="_blank">What versions of Moveit 2 are people using? · moveit · Discussion #3138</a></h3> + + <p>@sea-bass @nbbrooks I believe a question was briefly asked at the Maintainer Meeting yesterday regarding what versions of Moveit 2 tend to be used. I thought it might be interesting to raise a poll...</p> + + + </article> + + <div class="onebox-metadata"> + + + </div> + + <div style="clear: both;"></div> +</aside> + + <p><small>1 post - 1 participant</small></p> + <p><a href="https://discourse.ros.org/t/what-versions-of-moveit-2-are-people-using/40908">Read full topic</a></p> + Sun, 01 Dec 2024 23:36:10 +0000 + + + ROS Discourse General: Interoperability Interest Group December 05, 2024: Use Cases Around Open-RMF and Interoperability by Reply + discourse.ros.org-topic-40868 + https://discourse.ros.org/t/interoperability-interest-group-december-05-2024-use-cases-around-open-rmf-and-interoperability-by-reply/40868 + <p><a href="https://github.com/osrf-sig-interoperability/community" rel="noopener nofollow ugc">Community Page </a></p> +<p><a href="https://openrobotics-org.zoom.us/j/82222141986?pwd=30wAfBwxIQ66O12HslQVvBziGxPmJ0.1" rel="noopener nofollow ugc">Meeting Link </a></p> +<p><a href="https://calendar.google.com/calendar/u/0/embed?src=agf3kajirket8khktupm9go748@group.calendar.google.com" rel="noopener nofollow ugc">Calendar Link </a></p> +<p><span class="discourse-local-date">2024-12-05T15:00:00Z UTC</span></p> +<p>This month our friends from <a href="https://www.reply.com/en" rel="noopener nofollow ugc">Reply</a> will be presenting on work that they’ve been doing on robotics system integration using Open-RMF.</p> + <p><small>2 posts - 2 participants</small></p> + <p><a href="https://discourse.ros.org/t/interoperability-interest-group-december-05-2024-use-cases-around-open-rmf-and-interoperability-by-reply/40868">Read full topic</a></p> + Thu, 28 Nov 2024 15:23:19 +0000 + + + ROS Discourse General: Missing documentation for sensors? + discourse.ros.org-topic-40858 + https://discourse.ros.org/t/missing-documentation-for-sensors/40858 + <p>Hey guys, I just migrated from ROS1 to ROS2 and I am running ROS2 Humble Hawksbill with Gazebo Harmonic (ik it’s not the default installation but yeah I pulled Harmonic separately). I am working on a basic project to bring a robot present in my academia to gazebo and I noticed that there is close to no documentation about the list of sensors and how to use them in our xacro files. There is some basic introduction <a href="https://gazebosim.org/docs/harmonic/sensors/">here</a>. But I don’t see any list of sensors and how to use them anywhere. Does this call for creating a well-defined documentation or am I really missing any website?</p> + <p><small>13 posts - 9 participants</small></p> + <p><a href="https://discourse.ros.org/t/missing-documentation-for-sensors/40858">Read full topic</a></p> + Thu, 28 Nov 2024 07:09:17 +0000 + + + ROS Discourse General: OSRF Holiday Donation Drive + discourse.ros.org-topic-40852 + https://discourse.ros.org/t/osrf-holiday-donation-drive/40852 + <p></p><div class="lightbox-wrapper"><a class="lightbox" href="https://global.discourse-cdn.com/flex022/uploads/ros/original/3X/0/8/0886c02ebe7cf611b3d87c1a059892a4b6cb6610.jpeg" title="Thanksgiving"><img alt="Thanksgiving" height="388" src="https://global.discourse-cdn.com/flex022/uploads/ros/optimized/3X/0/8/0886c02ebe7cf611b3d87c1a059892a4b6cb6610_2_690x388.jpeg" width="690" /></a></div><p></p> +<p>Hi Everyone,</p> +<p>Just a quick note before everyone heads off for the long holiday weekend here in the States. Next Tuesday is Giving Tuesday in the US, a day when many people make their big charitable donations for the holiday season.</p> +<p>This year, we’ve set up a <a href="https://donorbox.org/open-robotics-giving-tuesday-2024">donations page for the Open Source Robotics Foundation (OSRF)</a> where you can specifically designate how you’d like your donation to be used. Want to help fund our infrastructure costs? Improve the ROS documentation? Support our educational efforts like the Diversity Scholars Program? Now you can choose!</p> +<p>We’re always thankful for your support, whether it’s monetary or a quick pull request! And remember, the OSRF is a 501(c)(3) tax-deductible charitable organization in the US.</p> +<p>If you, your colleagues, or your employer would like to support the OSRF and its mission, you can make a <a href="https://donorbox.org/open-robotics-giving-tuesday-2024">one-time or monthly donation using the new page</a>. Many employers match charitable donations during the holiday season, so be sure to check if yours does. Here at Intrinsic, we’ve used our employee match program to raise almost $15,000 for the OSRF. We’d love to see other members of the ROS community join the effort.</p> +<p>Finally, please help us spread the word! Our Open Robotics community is huge, and if we all pitched in just a little bit we could make some amazing things happen in 2025.</p> +<p>Thank you for your support, and have a wonderful holiday season! <img alt=":turkey:" class="emoji" height="20" src="https://emoji.discourse-cdn.com/twitter/turkey.png?v=12" title=":turkey:" width="20" /></p> + <p><small>4 posts - 4 participants</small></p> + <p><a href="https://discourse.ros.org/t/osrf-holiday-donation-drive/40852">Read full topic</a></p> + Wed, 27 Nov 2024 23:08:07 +0000 + + + +