Subscribe

Instructions

Participants

February 01, 2025
New TGC Members elected for 2025
from ROS Discourse General

The OSRA’s Technical Governance Committee has begun 2025 with the election of several new members to represent various different parts of the OSRA and to rebalance it after the growth in OSRA members during 2024. The new membership of the TGC is:

  • Addisu Taddese, Intrinsic (Gazebo Project Leader)
  • Clara Berendsen, Ekumen (Infrastructure Project Representative)
  • Daniel Gordon, Huawei (Gold Representative)
  • David Lu!! (Supporting Individual Representative)
  • Geoffrey Biggs, OSRF (TGC Chair)
  • Hemal Shah, NVIDIA (Platinum Member Representative)
  • Henkel Christian, Bosch (Gold Representative)
  • Kat Scott, Intrinsic (Developer Relations Representative)
  • Maria Carolina Vergo, ROS-Industrial (Silver Representative)
  • Michael Carrol, Intrinsic (Interim ROS Project Leader)
  • Michael Grey, Intrinsic (Open-RMF Project Leader)
  • Michel Hidalgo, Ekumen (Silver Representative)
  • Sathish Mani, Qualcomm Technologies (Platinum Member Representative)
  • Steve Peters, Intrinsic (Gazebo Project Representative)
  • Steven! Ragnarok, Intrinsic (Infrastructure Project Leader)
  • Tully Foote, Intrinsic (Platinum Member Representative)
  • Vanessa Yamzon Orsi, OSRF (Secretary)
  • Vicky Brasseur (OSRA Open Governance Advisor)
  • Yadunund Vijay, Intrinsic (Open-RMF Project Representative)

I’d like to thank all those who have volunteered their time to help guide the OSRA. I’d also like to thank those members who stepped down recently for contributing to the TGC’s first 8 months of operation and helping to get the OSRA off to such a great start.

  • Angelo Corsaro, Zettascale
  • Christine Fraser, Asimovo
  • Jason Higgins, Clearpath Robotics
  • Andra Keay, Silicon Valley Robotics
  • Chris Lalancette, Intrinsic
  • Steve Macenski, Open Navigation

1 post - 1 participant

Read full topic

by gbiggs on February 01, 2025 05:17 AM

OSRA TGC meeting minutes for December, 2024
from ROS Discourse General

The meeting minutes for the regular meeting of the Technical Governance Committee held on the 19th of December, 2024, were approved in the January meeting and are now available in the official minutes repository. You can find the complete minutes here.

The TGC received the monthly project and technical committee updates, including notice that REP-2000 is undergoing updates in preparation for the Kilted Kaiju release and that the ROS PMC has established its first working group, the Client Libraries Working Group, led by Alberto Soragna. The Infrastructure project reported that the infrastructure is undergoing upgrades to Ubuntu 24.04.

In this meeting, the TGC was presented with the results of the work done by its Technical Committee on Use in Projects of Submissions Produced by Generative AI. The TC has produced a complete policy, along with guidance. The TGC discussed the proposal, and is due to vote on its adoption shortly.

The next TGC meeting will take place in February, 2025. The minutes of the January meeting should be approved in that meeting and posted publicly shortly thereafter.

1 post - 1 participant

Read full topic

by gbiggs on February 01, 2025 05:11 AM

January 31, 2025
ROS News for the Week of January 27th, 2025
from ROS Discourse General

ROS News for the Week of January 27th, 2025


doom_rqt_image_view

It finally happened, ROS 2 now runs Doom now!


ClassicEOLh

Gazebo Classic goes End-Of-Life today! We need a few more days to push out the final updates, but those should be out next week. The good news is that if you are using Gazebo Classic and Nav2 there is now a full upgrade guide! (Thanks @smac and crew, we really appreciate this!)


ros2_launch_gui_nav2_example

Are you a ROS 2 user that misses ROSMon? Check out this beta release of ROS 2 Launch GUI. This new utility will let you interactively launch and monitor your ROS 2 application.


ROSConJP25_logo

ROSCon JP 2025 has been announced! ROSConJP will happen September 9th, in Nagoya!


Events

News

ROS

Want to Mentor a Student?

We are now looking for Google Summer of Code mentors for ROS and Gazebo. We need FOSS developers who are willing to spend this summer helping students learn our trade. See the post above for more details.

1 post - 1 participant

Read full topic

by Katherine_Scott on January 31, 2025 08:14 PM

Proud to be joining the Open Source Robotics Alliance!
from ROS Discourse General

:sailboat: ������������� has been sailing along with ROS since C Turtle :turtle: - and this week, we became a member of the ���� ������ �������� ��������! They take care of ��� as no one else can. We will support them for many years to come!

Here’s a nice drawing (no video allowed here) to celebrate:

From C Turtle to Jazzy

2 posts - 2 participants

Read full topic

by Peter_Soetens on January 31, 2025 02:26 PM

New Packages for Noetic 2025-01-30
from ROS Discourse General

We’re happy to announce 0 new packages and 13 updates are now available in ROS Noetic. This sync was tagged as noetic/2025-01-30.

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

Package Updates for ROS Noetic

Added Packages [0]:

Updated Packages [13]:

  • ros-noetic-costmap-cspace: 0.17.3-1 → 0.17.4-1
  • ros-noetic-grpc: 0.0.12-2 → 0.0.14-1
  • ros-noetic-joystick-interrupt: 0.17.3-1 → 0.17.4-1
  • ros-noetic-map-organizer: 0.17.3-1 → 0.17.4-1
  • ros-noetic-neonavigation: 0.17.3-1 → 0.17.4-1
  • ros-noetic-neonavigation-common: 0.17.3-1 → 0.17.4-1
  • ros-noetic-neonavigation-launch: 0.17.3-1 → 0.17.4-1
  • ros-noetic-obj-to-pointcloud: 0.17.3-1 → 0.17.4-1
  • ros-noetic-planner-cspace: 0.17.3-1 → 0.17.4-1
  • ros-noetic-safety-limiter: 0.17.3-1 → 0.17.4-1
  • ros-noetic-track-odometry: 0.17.3-1 → 0.17.4-1
  • ros-noetic-trajectory-tracker: 0.17.3-1 → 0.17.4-1
  • ros-noetic-ur-client-library: 1.5.0-1 → 1.6.0-1

Removed Packages [0]:

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

  • Atsushi Watanabe
  • Felix Exner
  • Shengye Wang

1 post - 1 participant

Read full topic

by sloretz on January 31, 2025 05:16 AM

January 29, 2025
Next ROS Medical talk announced! space x medical robotics
from ROS Discourse General

First, what a great turnout for the in-person Birds of Feather at ROSCon in Denmark. Standing room only, but that was perfect for some lively, collaborative discussions about using ROS in medical devices… how BoFs should be! :raised_hands:
I couldn’t fit everyone in one pic but you can see why we’re grateful to ROSCon organisers to have had the chance to meet in-person!!

roscon-med-bof

The ROS Medical Community is very excited for our next event about PickNik’s hands-on experience using ROS in the space and medical domains.

How do people trust ROS in space? And how can that transfer to the medical domain?

Nathan Brooks, CTO of PickNik, joins us to explain the overlap with PickNik’s goals to use ROS in space and goals of the ROS medical community. Topics covered include a certifiable version of MoveIt!, tools useful in the certification process, and general robotics architecture design for mission-critical systems.

No doubt of equal interest to those new to medical software, right up to med experts curious about robotics in NASA/commercial space, and everyone in between.

2025-02-24T17:00:00Z UTC, virtual

Add it to your calendar: https://bit.ly/ros-med-space

Sign up to this mailing list to receive invites to our future events.

Also: ROSCon talks on ROS 2 in the medical context
Recordings now available for these ROSCon 2024 talks by community leaders:

Looking forward to seeing everyone at the next community event!

Deanna

1 post - 1 participant

Read full topic

by dhood on January 29, 2025 12:10 PM

January 28, 2025
Google Summer of Code - Call for Mentors
from ROS Discourse General

TLDR: GSoC 2025 has kicked off, and the OSRF is once again hosting projects. If you have a project and want to mentor someone, please get in touch by emailing gsoc@openrobotics.org!

The Open Source Robotics Foundation is planning on participating in Google Summer of Code 2025. We are now putting out a call for mentors. We need people to volunteer to mentor one or more projects and participants throughout the GSoC period.

By being a GSoC mentor, you will be contributing to a large technical contribution to one of the OSRF’s projects, but more importantly you will be contributing to the growth in expertise and experience of a new engineer! Being a mentor is very rewarding work, and we have seen many of our previous GSoC participants go on to be important long-term members of the community and long-term contributors.

Information on what it takes to be a mentor can be found on the GSoC website:

If you are interested in mentoring a GSoC participant this year, then please get in touch by emailing us at gsoc@openrobotics.org! Please describe why you want to mentor with the OSRF, what qualifies you to be a mentor, and what projects you wish to offer. For each project, please include the following information, in this bullet-list format.

  • List of prerequisites
  • Description of necessary programming skills
  • Difficulty level
  • List of potential mentors
  • Expected size
  • Expected outcome
  • Detailed description

For examples of projects that the OSRF has hosted in previous years, take a look at this page.

We are open to mentors until February 9th, 2025 at 18:00 UTC.

3 posts - 3 participants

Read full topic

by gbiggs on January 28, 2025 12:50 AM

January 27, 2025
Type hinting for ROS 2 python messages for
from ROS Discourse General

Has anyone figured out a way to get a language server like pyright to work with ros2 python messages? Normally if you have a class like this

class MyRosMessage:
    def __init__(x: float, y: float, z: float):
        ...
my_ros_message = MyRosMessage(x=1.0, y=2.0, z=3)

My LSP will warn me that z is an int when it should be a float.

However I noticed that the ROS2 implementation of Python ROS messages is as such:

class MyRosMessage:
    def __init__(kwargs**):
        ...
        self.x = kwargs.get('x', float())
        self.y = kwargs.get('y', float())
        self.z = kwargs.get('z', float())

    @x.setter
    def x(self, value):
        if __debug__:
            assert \
                isinstance(value, float), \
                "The 'x' field must be of type 'float'"
            assert not (value < -1.7976931348623157e+308 or value > 1.7976931348623157e+308) or math.isinf(value), \
                "The 'x' field must be a double in [-1.7976931348623157e+308, 1.7976931348623157e+308]"
        self._x = value

# This line will throw an assertion error. pyright will not warn you about this mistake.
my_ros_message = MyRosMessage(x=1.0, y=2.0, z=3)

Is there any way to make a language server understand the the code above will throw an exception before hand? Is there an easy way to modify the ROS2 message generation to include type hinting in the setter or something like such?

class MyRosMessage:
...

    @x.setter
    def x(self, value: float):
...

2 posts - 2 participants

Read full topic

by snwu on January 27, 2025 01:45 AM

January 26, 2025
ROS Deliberation Community Group Meeting - Feb 3, 2025
from ROS Discourse General

After an extended holiday break, the next ROS Deliberation Community Group meeting will be on 2025-02-03T15:00:00Z UTC.

Google Meet link: https://meet.google.com/njs-ieym-dgk

Agenda:

For the tool spotlight and group discussion topics, it would be fantastic to get input from people who have relevant experience. I also believe it’s a great opportunity to promote your work and set up presentations/learning sessions for future meetings.

Feel free to propose additional agenda items, join the mailing list, or the Discord server.

- Sebastian

1 post - 1 participant

Read full topic

by scastro on January 26, 2025 06:34 PM

January 24, 2025
ROS News for the Week of January 20th, 2025
from ROS Discourse General

ROS News for the Week of January 20th, 2025


Jan25GCM

ROSBTBJan25 (1)

Copy of Meetup at Photonics West 2025

We have three different ROS events scheduled next week and we would love for you to join us!


image

I don’t have a great image for this item, Zig doesn’t have a fancy mascot like Rust :crab:, but I want to call your attention to ZigROS, a way to build ROS with the zig build system.


image

LG has acquired a majority share of Bear Robotics. Bear Robotics builds food delivery robots for restaurants and they have been ROS users for years. Additional reporting on the acquisition at TechCrunch


fast
:tada: Thanks to the hard work of @rkent ROS Index has a number of new improvements, including faster search, an updated UI, extending search to read me files, and a whole lot more. @rkent has been working on these pull requests for a long time and we really appreciate his patience and determination. :heart:

Events

News

ROS

Got a Minute? :mantelpiece_clock:

Here are couple of easy issues on docs.ros.org that need attention. Why not take a moment to become a ROS contributor instead of just a ROS user?

1 post - 1 participant

Read full topic

by Katherine_Scott on January 24, 2025 07:55 PM

Mitsubishi Electric ROS2 Community Discussion
from ROS Discourse General

Hi ROS community,

I am the developer and maintainer for Mitsubishi Electric ROS2 Driver.

In our efforts to continue our commitment to democratize MELFA robots and participate in Open-Source robotics, I would like to start an open discussion with the community. Any ROS and open-source robotics topics are welcomed.

I would like to start the ball rolling with a few topics:

  1. which robots do you want us to add to our MELFA ROS2 Driver?
  2. what kind of existing functionality would you like to see in our MELFA ROS2 Driver?
  3. In the coming months, I will be releasing repositories with tutorials & documentation for MELSEC Programmable Logic Controller ROS2 compatibility and GOT-Human Machine Interface ROS2 compatibility via the MELFA ROS2 Driver. If there’s a Mitsubishi Electric product that you want to use for your ROS2 project, feel free to reply as well or contact me directly.
  • Please do not request for a return of the Lancer Evo :smiling_face_with_tear:

If you have another topic that you would like to discuss, feel free to start a discussion in this thread. If you prefer to contact me directly, you can send me an email at muyao.liu@asia.meap.com

3 posts - 3 participants

Read full topic

by offinliu on January 24, 2025 09:50 AM

January 21, 2025
Cloud Robotics WG Meeting 2025-01-27 | Trying KubeEdge
from ROS Discourse General

Please come and join us for this coming meeting at 2025-01-27T17:00:00Z UTC→2025-01-27T18:00:00Z UTC, where we will locate and work through some KubeEdge examples. We will note down our feedback and provide it to Tomoya Fujita, who gave a talk in a previous session about KubeEdge and some related technologies. If you’re interested to see the talk, we have published it on YouTube.

Last meeting, we had a general catchup, including discussing NVIDIA Cosmos, the proliferation of humanoid robotics at present, and what cloud robotics encompasses - to name a few subjects. If you are interested to see the meeting, the recording is available on YouTube.

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 or keep an eye on the Cloud Robotics Hub.

Hopefully we will see you there!

1 post - 1 participant

Read full topic

by mikelikesrobots on January 21, 2025 05:07 PM

New packages for Humble Hawksbill 2025-01-21
from ROS Discourse General

Package Updates for Humble

Added Packages [24]:

Updated Packages [282]:

  • ros-humble-ackermann-steering-controller: 2.39.0-1 → 2.41.0-1
  • ros-humble-ackermann-steering-controller-dbgsym: 2.39.0-1 → 2.41.0-1
  • ros-humble-admittance-controller: 2.39.0-1 → 2.41.0-1
  • ros-humble-admittance-controller-dbgsym: 2.39.0-1 → 2.41.0-1
  • ros-humble-autoware-internal-msgs: 1.1.0-1 → 1.3.0-1
  • ros-humble-autoware-internal-msgs-dbgsym: 1.1.0-1 → 1.3.0-1
  • ros-humble-bicycle-steering-controller: 2.39.0-1 → 2.41.0-1
  • ros-humble-bicycle-steering-controller-dbgsym: 2.39.0-1 → 2.41.0-1
  • ros-humble-camera-ros: 0.2.1-1 → 0.3.0-1
  • ros-humble-camera-ros-dbgsym: 0.2.1-1 → 0.3.0-1
  • ros-humble-chomp-motion-planner: 2.5.6-1 → 2.5.7-1
  • ros-humble-chomp-motion-planner-dbgsym: 2.5.6-1 → 2.5.7-1
  • ros-humble-clearpath-common: 1.0.0-1 → 1.1.1-1
  • ros-humble-clearpath-config: 1.0.0-1 → 1.1.0-1
  • ros-humble-clearpath-control: 1.0.0-1 → 1.1.1-1
  • ros-humble-clearpath-customization: 1.0.0-1 → 1.1.1-1
  • ros-humble-clearpath-description: 1.0.0-1 → 1.1.1-1
  • ros-humble-clearpath-generator-common: 1.0.0-1 → 1.1.1-1
  • ros-humble-clearpath-generator-common-dbgsym: 1.0.0-1 → 1.1.1-1
  • ros-humble-clearpath-manipulators: 1.0.0-1 → 1.1.1-1
  • ros-humble-clearpath-manipulators-description: 1.0.0-1 → 1.1.1-1
  • ros-humble-clearpath-mounts-description: 1.0.0-1 → 1.1.1-1
  • ros-humble-clearpath-platform-description: 1.0.0-1 → 1.1.1-1
  • ros-humble-clearpath-sensors-description: 1.0.0-1 → 1.1.1-1
  • ros-humble-control-toolbox: 3.4.0-1 → 3.6.0-1
  • ros-humble-control-toolbox-dbgsym: 3.4.0-1 → 3.6.0-1
  • ros-humble-controller-interface: 2.46.0-1 → 2.47.0-1
  • ros-humble-controller-interface-dbgsym: 2.46.0-1 → 2.47.0-1
  • ros-humble-controller-manager: 2.46.0-1 → 2.47.0-1
  • ros-humble-controller-manager-dbgsym: 2.46.0-1 → 2.47.0-1
  • ros-humble-controller-manager-msgs: 2.46.0-1 → 2.47.0-1
  • ros-humble-controller-manager-msgs-dbgsym: 2.46.0-1 → 2.47.0-1
  • ros-humble-depthai: 2.28.0-1 → 2.29.0-1
  • ros-humble-depthai-bridge: 2.10.4-1 → 2.10.5-1
  • ros-humble-depthai-bridge-dbgsym: 2.10.4-1 → 2.10.5-1
  • ros-humble-depthai-dbgsym: 2.28.0-1 → 2.29.0-1
  • ros-humble-depthai-descriptions: 2.10.4-1 → 2.10.5-1
  • ros-humble-depthai-examples: 2.10.4-1 → 2.10.5-1
  • ros-humble-depthai-examples-dbgsym: 2.10.4-1 → 2.10.5-1
  • ros-humble-depthai-filters: 2.10.4-1 → 2.10.5-1
  • ros-humble-depthai-filters-dbgsym: 2.10.4-1 → 2.10.5-1
  • ros-humble-depthai-ros: 2.10.4-1 → 2.10.5-1
  • ros-humble-depthai-ros-driver: 2.10.4-1 → 2.10.5-1
  • ros-humble-depthai-ros-driver-dbgsym: 2.10.4-1 → 2.10.5-1
  • ros-humble-depthai-ros-msgs: 2.10.4-1 → 2.10.5-1
  • ros-humble-depthai-ros-msgs-dbgsym: 2.10.4-1 → 2.10.5-1
  • ros-humble-diff-drive-controller: 2.39.0-1 → 2.41.0-1
  • ros-humble-diff-drive-controller-dbgsym: 2.39.0-1 → 2.41.0-1
  • ros-humble-effort-controllers: 2.39.0-1 → 2.41.0-1
  • ros-humble-effort-controllers-dbgsym: 2.39.0-1 → 2.41.0-1
  • ros-humble-examples-tf2-py: 0.25.9-1 → 0.25.11-1
  • ros-humble-force-torque-sensor-broadcaster: 2.39.0-1 → 2.41.0-1
  • ros-humble-force-torque-sensor-broadcaster-dbgsym: 2.39.0-1 → 2.41.0-1
  • ros-humble-forward-command-controller: 2.39.0-1 → 2.41.0-1
  • ros-humble-forward-command-controller-dbgsym: 2.39.0-1 → 2.41.0-1
  • ros-humble-generate-parameter-library: 0.3.9-1 → 0.4.0-1
  • ros-humble-generate-parameter-library-example: 0.3.9-1 → 0.4.0-1
  • ros-humble-generate-parameter-library-example-dbgsym: 0.3.9-1 → 0.4.0-1
  • ros-humble-generate-parameter-library-py: 0.3.9-1 → 0.4.0-1
  • ros-humble-generate-parameter-module-example: 0.3.9-1 → 0.4.0-1
  • ros-humble-geometry2: 0.25.9-1 → 0.25.11-1
  • ros-humble-gripper-controllers: 2.39.0-1 → 2.41.0-1
  • ros-humble-gripper-controllers-dbgsym: 2.39.0-1 → 2.41.0-1
  • ros-humble-hardware-interface: 2.46.0-1 → 2.47.0-1
  • ros-humble-hardware-interface-dbgsym: 2.46.0-1 → 2.47.0-1
  • ros-humble-hardware-interface-testing: 2.46.0-1 → 2.47.0-1
  • ros-humble-hardware-interface-testing-dbgsym: 2.46.0-1 → 2.47.0-1
  • ros-humble-imu-sensor-broadcaster: 2.39.0-1 → 2.41.0-1
  • ros-humble-imu-sensor-broadcaster-dbgsym: 2.39.0-1 → 2.41.0-1
  • ros-humble-joint-limits: 2.46.0-1 → 2.47.0-1
  • ros-humble-joint-limits-dbgsym: 2.46.0-1 → 2.47.0-1
  • ros-humble-joint-state-broadcaster: 2.39.0-1 → 2.41.0-1
  • ros-humble-joint-state-broadcaster-dbgsym: 2.39.0-1 → 2.41.0-1
  • ros-humble-joint-trajectory-controller: 2.39.0-1 → 2.41.0-1
  • ros-humble-joint-trajectory-controller-dbgsym: 2.39.0-1 → 2.41.0-1
  • ros-humble-kitti-metrics-eval: 1.3.0-1 → 1.5.1-1
  • ros-humble-kitti-metrics-eval-dbgsym: 1.3.0-1 → 1.5.1-1
  • ros-humble-mola: 1.3.0-1 → 1.5.1-1
  • ros-humble-mola-bridge-ros2: 1.3.0-1 → 1.5.1-1
  • ros-humble-mola-bridge-ros2-dbgsym: 1.3.0-1 → 1.5.1-1
  • ros-humble-mola-demos: 1.3.0-1 → 1.5.1-1
  • ros-humble-mola-imu-preintegration: 1.3.0-1 → 1.6.1-1
  • ros-humble-mola-imu-preintegration-dbgsym: 1.3.0-1 → 1.6.1-1
  • ros-humble-mola-input-euroc-dataset: 1.3.0-1 → 1.5.1-1
  • ros-humble-mola-input-euroc-dataset-dbgsym: 1.3.0-1 → 1.5.1-1
  • ros-humble-mola-input-kitti-dataset: 1.3.0-1 → 1.5.1-1
  • ros-humble-mola-input-kitti-dataset-dbgsym: 1.3.0-1 → 1.5.1-1
  • ros-humble-mola-input-kitti360-dataset: 1.3.0-1 → 1.5.1-1
  • ros-humble-mola-input-kitti360-dataset-dbgsym: 1.3.0-1 → 1.5.1-1
  • ros-humble-mola-input-mulran-dataset: 1.3.0-1 → 1.5.1-1
  • ros-humble-mola-input-mulran-dataset-dbgsym: 1.3.0-1 → 1.5.1-1
  • ros-humble-mola-input-paris-luco-dataset: 1.3.0-1 → 1.5.1-1
  • ros-humble-mola-input-paris-luco-dataset-dbgsym: 1.3.0-1 → 1.5.1-1
  • ros-humble-mola-input-rawlog: 1.3.0-1 → 1.5.1-1
  • ros-humble-mola-input-rawlog-dbgsym: 1.3.0-1 → 1.5.1-1
  • ros-humble-mola-input-rosbag2: 1.3.0-1 → 1.5.1-1
  • ros-humble-mola-input-rosbag2-dbgsym: 1.3.0-1 → 1.5.1-1
  • ros-humble-mola-kernel: 1.3.0-1 → 1.5.1-1
  • ros-humble-mola-kernel-dbgsym: 1.3.0-1 → 1.5.1-1
  • ros-humble-mola-launcher: 1.3.0-1 → 1.5.1-1
  • ros-humble-mola-launcher-dbgsym: 1.3.0-1 → 1.5.1-1
  • ros-humble-mola-lidar-odometry: 0.3.3-1 → 0.5.4-1
  • ros-humble-mola-lidar-odometry-dbgsym: 0.3.3-1 → 0.5.4-1
  • ros-humble-mola-metric-maps: 1.3.0-1 → 1.5.1-1
  • ros-humble-mola-metric-maps-dbgsym: 1.3.0-1 → 1.5.1-1
  • ros-humble-mola-msgs: 1.3.0-1 → 1.5.1-1
  • ros-humble-mola-msgs-dbgsym: 1.3.0-1 → 1.5.1-1
  • ros-humble-mola-pose-list: 1.3.0-1 → 1.5.1-1
  • ros-humble-mola-pose-list-dbgsym: 1.3.0-1 → 1.5.1-1
  • ros-humble-mola-relocalization: 1.3.0-1 → 1.5.1-1
  • ros-humble-mola-relocalization-dbgsym: 1.3.0-1 → 1.5.1-1
  • ros-humble-mola-test-datasets: 0.3.4-1 → 0.4.0-1
  • ros-humble-mola-traj-tools: 1.3.0-1 → 1.5.1-1
  • ros-humble-mola-traj-tools-dbgsym: 1.3.0-1 → 1.5.1-1
  • ros-humble-mola-viz: 1.3.0-1 → 1.5.1-1
  • ros-humble-mola-viz-dbgsym: 1.3.0-1 → 1.5.1-1
  • ros-humble-mola-yaml: 1.3.0-1 → 1.5.1-1
  • ros-humble-mola-yaml-dbgsym: 1.3.0-1 → 1.5.1-1
  • ros-humble-moveit: 2.5.6-1 → 2.5.7-1
  • ros-humble-moveit-chomp-optimizer-adapter: 2.5.6-1 → 2.5.7-1
  • ros-humble-moveit-chomp-optimizer-adapter-dbgsym: 2.5.6-1 → 2.5.7-1
  • ros-humble-moveit-common: 2.5.6-1 → 2.5.7-1
  • ros-humble-moveit-configs-utils: 2.5.6-1 → 2.5.7-1
  • ros-humble-moveit-core: 2.5.6-1 → 2.5.7-1
  • ros-humble-moveit-core-dbgsym: 2.5.6-1 → 2.5.7-1
  • ros-humble-moveit-hybrid-planning: 2.5.6-1 → 2.5.7-1
  • ros-humble-moveit-hybrid-planning-dbgsym: 2.5.6-1 → 2.5.7-1
  • ros-humble-moveit-kinematics: 2.5.6-1 → 2.5.7-1
  • ros-humble-moveit-kinematics-dbgsym: 2.5.6-1 → 2.5.7-1
  • ros-humble-moveit-planners: 2.5.6-1 → 2.5.7-1
  • ros-humble-moveit-planners-chomp: 2.5.6-1 → 2.5.7-1
  • ros-humble-moveit-planners-chomp-dbgsym: 2.5.6-1 → 2.5.7-1
  • ros-humble-moveit-planners-ompl: 2.5.6-1 → 2.5.7-1
  • ros-humble-moveit-planners-ompl-dbgsym: 2.5.6-1 → 2.5.7-1
  • ros-humble-moveit-plugins: 2.5.6-1 → 2.5.7-1
  • ros-humble-moveit-resources-prbt-ikfast-manipulator-plugin: 2.5.6-1 → 2.5.7-1
  • ros-humble-moveit-resources-prbt-ikfast-manipulator-plugin-dbgsym: 2.5.6-1 → 2.5.7-1
  • ros-humble-moveit-resources-prbt-moveit-config: 2.5.6-1 → 2.5.7-1
  • ros-humble-moveit-resources-prbt-pg70-support: 2.5.6-1 → 2.5.7-1
  • ros-humble-moveit-resources-prbt-support: 2.5.6-1 → 2.5.7-1
  • ros-humble-moveit-ros: 2.5.6-1 → 2.5.7-1
  • ros-humble-moveit-ros-benchmarks: 2.5.6-1 → 2.5.7-1
  • ros-humble-moveit-ros-benchmarks-dbgsym: 2.5.6-1 → 2.5.7-1
  • ros-humble-moveit-ros-control-interface: 2.5.6-1 → 2.5.7-1
  • ros-humble-moveit-ros-control-interface-dbgsym: 2.5.6-1 → 2.5.7-1
  • ros-humble-moveit-ros-move-group: 2.5.6-1 → 2.5.7-1
  • ros-humble-moveit-ros-move-group-dbgsym: 2.5.6-1 → 2.5.7-1
  • ros-humble-moveit-ros-occupancy-map-monitor: 2.5.6-1 → 2.5.7-1
  • ros-humble-moveit-ros-occupancy-map-monitor-dbgsym: 2.5.6-1 → 2.5.7-1
  • ros-humble-moveit-ros-perception: 2.5.6-1 → 2.5.7-1
  • ros-humble-moveit-ros-perception-dbgsym: 2.5.6-1 → 2.5.7-1
  • ros-humble-moveit-ros-planning: 2.5.6-1 → 2.5.7-1
  • ros-humble-moveit-ros-planning-dbgsym: 2.5.6-1 → 2.5.7-1
  • ros-humble-moveit-ros-planning-interface: 2.5.6-1 → 2.5.7-1
  • ros-humble-moveit-ros-planning-interface-dbgsym: 2.5.6-1 → 2.5.7-1
  • ros-humble-moveit-ros-robot-interaction: 2.5.6-1 → 2.5.7-1
  • ros-humble-moveit-ros-robot-interaction-dbgsym: 2.5.6-1 → 2.5.7-1
  • ros-humble-moveit-ros-visualization: 2.5.6-1 → 2.5.7-1
  • ros-humble-moveit-ros-visualization-dbgsym: 2.5.6-1 → 2.5.7-1
  • ros-humble-moveit-ros-warehouse: 2.5.6-1 → 2.5.7-1
  • ros-humble-moveit-ros-warehouse-dbgsym: 2.5.6-1 → 2.5.7-1
  • ros-humble-moveit-runtime: 2.5.6-1 → 2.5.7-1
  • ros-humble-moveit-servo: 2.5.6-1 → 2.5.7-1
  • ros-humble-moveit-servo-dbgsym: 2.5.6-1 → 2.5.7-1
  • ros-humble-moveit-setup-app-plugins: 2.5.6-1 → 2.5.7-1
  • ros-humble-moveit-setup-app-plugins-dbgsym: 2.5.6-1 → 2.5.7-1
  • ros-humble-moveit-setup-assistant: 2.5.6-1 → 2.5.7-1
  • ros-humble-moveit-setup-assistant-dbgsym: 2.5.6-1 → 2.5.7-1
  • ros-humble-moveit-setup-controllers: 2.5.6-1 → 2.5.7-1
  • ros-humble-moveit-setup-controllers-dbgsym: 2.5.6-1 → 2.5.7-1
  • ros-humble-moveit-setup-core-plugins: 2.5.6-1 → 2.5.7-1
  • ros-humble-moveit-setup-core-plugins-dbgsym: 2.5.6-1 → 2.5.7-1
  • ros-humble-moveit-setup-framework: 2.5.6-1 → 2.5.7-1
  • ros-humble-moveit-setup-framework-dbgsym: 2.5.6-1 → 2.5.7-1
  • ros-humble-moveit-setup-srdf-plugins: 2.5.6-1 → 2.5.7-1
  • ros-humble-moveit-setup-srdf-plugins-dbgsym: 2.5.6-1 → 2.5.7-1
  • ros-humble-moveit-simple-controller-manager: 2.5.6-1 → 2.5.7-1
  • ros-humble-moveit-simple-controller-manager-dbgsym: 2.5.6-1 → 2.5.7-1
  • ros-humble-mp2p-icp: 1.6.3-1 → 1.6.4-1
  • ros-humble-mp2p-icp-dbgsym: 1.6.3-1 → 1.6.4-1
  • ros-humble-mvsim: 0.12.0-1 → 0.13.0-1
  • ros-humble-mvsim-dbgsym: 0.12.0-1 → 0.13.0-1
  • ros-humble-ntrip-client: 1.3.0-1 → 1.4.0-1
  • ros-humble-parameter-traits: 0.3.9-1 → 0.4.0-1
  • ros-humble-pid-controller: 2.39.0-1 → 2.41.0-1
  • ros-humble-pid-controller-dbgsym: 2.39.0-1 → 2.41.0-1
  • ros-humble-pilz-industrial-motion-planner: 2.5.6-1 → 2.5.7-1
  • ros-humble-pilz-industrial-motion-planner-dbgsym: 2.5.6-1 → 2.5.7-1
  • ros-humble-pilz-industrial-motion-planner-testutils: 2.5.6-1 → 2.5.7-1
  • ros-humble-pilz-industrial-motion-planner-testutils-dbgsym: 2.5.6-1 → 2.5.7-1
  • ros-humble-pose-broadcaster: 2.39.0-1 → 2.41.0-1
  • ros-humble-pose-broadcaster-dbgsym: 2.39.0-1 → 2.41.0-1
  • ros-humble-position-controllers: 2.39.0-1 → 2.41.0-1
  • ros-humble-position-controllers-dbgsym: 2.39.0-1 → 2.41.0-1
  • ros-humble-py-trees: 2.2.3-1 → 2.3.0-1
  • ros-humble-py-trees-js: 0.6.4-1 → 0.6.6-1
  • ros-humble-py-trees-ros: 2.2.2-3 → 2.3.0-1
  • ros-humble-py-trees-ros-interfaces: 2.1.0-1 → 2.1.1-1
  • ros-humble-py-trees-ros-interfaces-dbgsym: 2.1.0-1 → 2.1.1-1
  • ros-humble-qml-ros2-plugin: 1.0.1-1 → 1.0.1-2
  • ros-humble-qml-ros2-plugin-dbgsym: 1.0.1-1 → 1.0.1-2
  • ros-humble-range-sensor-broadcaster: 2.39.0-1 → 2.41.0-1
  • ros-humble-range-sensor-broadcaster-dbgsym: 2.39.0-1 → 2.41.0-1
  • ros-humble-ros2-control: 2.46.0-1 → 2.47.0-1
  • ros-humble-ros2-control-test-assets: 2.46.0-1 → 2.47.0-1
  • ros-humble-ros2-controllers: 2.39.0-1 → 2.41.0-1
  • ros-humble-ros2-controllers-test-nodes: 2.39.0-1 → 2.41.0-1
  • ros-humble-ros2controlcli: 2.46.0-1 → 2.47.0-1
  • ros-humble-rqt-controller-manager: 2.46.0-1 → 2.47.0-1
  • ros-humble-rqt-joint-trajectory-controller: 2.39.0-1 → 2.41.0-1
  • ros-humble-rviz-assimp-vendor: 11.2.14-1 → 11.2.16-1
  • ros-humble-rviz-common: 11.2.14-1 → 11.2.16-1
  • ros-humble-rviz-common-dbgsym: 11.2.14-1 → 11.2.16-1
  • ros-humble-rviz-default-plugins: 11.2.14-1 → 11.2.16-1
  • ros-humble-rviz-default-plugins-dbgsym: 11.2.14-1 → 11.2.16-1
  • ros-humble-rviz-ogre-vendor: 11.2.14-1 → 11.2.16-1
  • ros-humble-rviz-ogre-vendor-dbgsym: 11.2.14-1 → 11.2.16-1
  • ros-humble-rviz-rendering: 11.2.14-1 → 11.2.16-1
  • ros-humble-rviz-rendering-dbgsym: 11.2.14-1 → 11.2.16-1
  • ros-humble-rviz-rendering-tests: 11.2.14-1 → 11.2.16-1
  • ros-humble-rviz-visual-testing-framework: 11.2.14-1 → 11.2.16-1
  • ros-humble-rviz2: 11.2.14-1 → 11.2.16-1
  • ros-humble-rviz2-dbgsym: 11.2.14-1 → 11.2.16-1
  • ros-humble-steering-controllers-library: 2.39.0-1 → 2.41.0-1
  • ros-humble-steering-controllers-library-dbgsym: 2.39.0-1 → 2.41.0-1
  • ros-humble-tensorrt-cmake-module: 0.0.3-1 → 0.0.4-1
  • ros-humble-tf2: 0.25.9-1 → 0.25.11-1
  • ros-humble-tf2-bullet: 0.25.9-1 → 0.25.11-1
  • ros-humble-tf2-dbgsym: 0.25.9-1 → 0.25.11-1
  • ros-humble-tf2-eigen: 0.25.9-1 → 0.25.11-1
  • ros-humble-tf2-eigen-kdl: 0.25.9-1 → 0.25.11-1
  • ros-humble-tf2-eigen-kdl-dbgsym: 0.25.9-1 → 0.25.11-1
  • ros-humble-tf2-geometry-msgs: 0.25.9-1 → 0.25.11-1
  • ros-humble-tf2-kdl: 0.25.9-1 → 0.25.11-1
  • ros-humble-tf2-msgs: 0.25.9-1 → 0.25.11-1
  • ros-humble-tf2-msgs-dbgsym: 0.25.9-1 → 0.25.11-1
  • ros-humble-tf2-py: 0.25.9-1 → 0.25.11-1
  • ros-humble-tf2-py-dbgsym: 0.25.9-1 → 0.25.11-1
  • ros-humble-tf2-ros: 0.25.9-1 → 0.25.11-1
  • ros-humble-tf2-ros-dbgsym: 0.25.9-1 → 0.25.11-1
  • ros-humble-tf2-ros-py: 0.25.9-1 → 0.25.11-1
  • ros-humble-tf2-sensor-msgs: 0.25.9-1 → 0.25.11-1
  • ros-humble-tf2-tools: 0.25.9-1 → 0.25.11-1
  • ros-humble-transmission-interface: 2.46.0-1 → 2.47.0-1
  • ros-humble-transmission-interface-dbgsym: 2.46.0-1 → 2.47.0-1
  • ros-humble-tricycle-controller: 2.39.0-1 → 2.41.0-1
  • ros-humble-tricycle-controller-dbgsym: 2.39.0-1 → 2.41.0-1
  • ros-humble-tricycle-steering-controller: 2.39.0-1 → 2.41.0-1
  • ros-humble-tricycle-steering-controller-dbgsym: 2.39.0-1 → 2.41.0-1
  • ros-humble-turtlebot4-setup: 1.0.4-1 → 1.0.5-1
  • ros-humble-tuw-airskin-msgs: 0.2.1-1 → 0.2.5-1
  • ros-humble-tuw-airskin-msgs-dbgsym: 0.2.1-1 → 0.2.5-1
  • ros-humble-tuw-geo-msgs: 0.2.3-1 → 0.2.5-1
  • ros-humble-tuw-geo-msgs-dbgsym: 0.2.3-1 → 0.2.5-1
  • ros-humble-tuw-geometry-msgs: 0.2.1-1 → 0.2.5-1
  • ros-humble-tuw-geometry-msgs-dbgsym: 0.2.1-1 → 0.2.5-1
  • ros-humble-tuw-graph-msgs: 0.2.3-1 → 0.2.5-1
  • ros-humble-tuw-graph-msgs-dbgsym: 0.2.3-1 → 0.2.5-1
  • ros-humble-tuw-msgs: 0.2.1-1 → 0.2.5-1
  • ros-humble-tuw-multi-robot-msgs: 0.2.1-1 → 0.2.5-1
  • ros-humble-tuw-multi-robot-msgs-dbgsym: 0.2.1-1 → 0.2.5-1
  • ros-humble-tuw-nav-msgs: 0.2.1-1 → 0.2.5-1
  • ros-humble-tuw-nav-msgs-dbgsym: 0.2.1-1 → 0.2.5-1
  • ros-humble-tuw-object-map-msgs: 0.2.3-1 → 0.2.5-1
  • ros-humble-tuw-object-map-msgs-dbgsym: 0.2.3-1 → 0.2.5-1
  • ros-humble-tuw-object-msgs: 0.2.1-1 → 0.2.5-1
  • ros-humble-tuw-object-msgs-dbgsym: 0.2.1-1 → 0.2.5-1
  • ros-humble-tuw-std-msgs: 0.2.4-1 → 0.2.5-1
  • ros-humble-tuw-std-msgs-dbgsym: 0.2.4-1 → 0.2.5-1
  • ros-humble-ur: 2.2.16-5 → 2.5.1-1
  • ros-humble-ur-bringup: 2.2.16-5 → 2.5.1-1
  • ros-humble-ur-calibration: 2.2.16-5 → 2.5.1-1
  • ros-humble-ur-calibration-dbgsym: 2.2.16-5 → 2.5.1-1
  • ros-humble-ur-controllers: 2.2.16-5 → 2.5.1-1
  • ros-humble-ur-controllers-dbgsym: 2.2.16-5 → 2.5.1-1
  • ros-humble-ur-dashboard-msgs: 2.2.16-5 → 2.5.1-1
  • ros-humble-ur-dashboard-msgs-dbgsym: 2.2.16-5 → 2.5.1-1
  • ros-humble-ur-moveit-config: 2.2.16-5 → 2.5.1-1
  • ros-humble-ur-robot-driver: 2.2.16-5 → 2.5.1-1
  • ros-humble-ur-robot-driver-dbgsym: 2.2.16-5 → 2.5.1-1
  • ros-humble-velocity-controllers: 2.39.0-1 → 2.41.0-1
  • ros-humble-velocity-controllers-dbgsym: 2.39.0-1 → 2.41.0-1

Removed Packages [4]:

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

  • Adam Serafin
  • Alexander Gutenkunst
  • Automatika Robotics
  • Bence Magyar
  • Benjamin Binder
  • Berkay Karaman
  • Blake Anderson
  • Chittaranjan Srinivas Swaminathan
  • Chris Lalancette
  • Christian Henkel
  • Christian Rauch
  • Daisuke Nishimatsu
  • Daniel Stonier
  • David V. Lu!!
  • Felix Exner
  • George Todoran
  • Henning Kayser
  • Jacob Perron
  • Jafar Uruc
  • Jose Luis Blanco-Claraco
  • Jose-Luis Blanco-Claraco
  • Joseph Mirabel
  • Luis Camero
  • M. Fatih Cırıt
  • Markus Bader
  • Michael Görner
  • MoveIt Release Team
  • Paul Gesel
  • Raghavender Sahdev
  • Rob Fisher
  • Ryohsuke Mitsudome
  • Stefan Fabian
  • Tyler Weaver
  • Yadunund
  • paul
  • rkreinin

1 post - 1 participant

Read full topic

by audrow on January 21, 2025 12:17 PM

January 20, 2025
Speeding up Python nodes with the Bit-Bots TF Buffer
from ROS Discourse General

Repo: GitHub - bit-bots/bitbots_tf_buffer: A performant non blocking rclpy tf buffer utilizing rclcpp under the hood.

Sadly, rclpy is slow. This is not only a Python problem, but also a problem of the underlying rclpy implementation. (hint: a Python based events executor is currently being developed by us, but is a story for another day).

TF2 is used in many nodes. The amount of callbacks that are triggered by TF2 can be very high, especially if there are multiple sources of TF data and you operate on a high frequency. A simple ROS 2 rclpy node can easily max out a CPU core just by processing TF data. This is especially unlucky, if TF is only used at a few places in the code for e.g. low frequency navigation or behavior operations.

This package aims to solve this problem by moving the TF buffer and listener to a C++ node that shares the process with the rclpy node. That way, the TF callbacks are processed in C++ and the Python node only needs to query the buffer for the latest transforms using a simple and performant pybind11 interface when needed.

While spinning up an additional Node is not ideal, the performance gain is significant and the overhead of the additional node is negligible compared to the performance gain. I don’t have reliable performance trials, but it brought down the CPU utilization of many nodes in our stack from 100% to ~20% CPU.

In addition to that, this solution also reduces the amount of executor deadlock scenarios and enables the usage of a single threaded executor for the rclpy node instead of the multi-threaded executor in many cases, resulting in further performance gains.

We use it in-house for a few months now, and it runs very smooth.

6 posts - 3 participants

Read full topic

by Flova on January 20, 2025 07:29 PM

A library for inverse dynamics computation - where to contribute?
from ROS Discourse General

I have developed an interface exposing methods to compute the dynamic components of robots (inertia, coriolis, gravity, friction).

I am also willing to specialize this interface with a KDL-based solver for simulated robots, and with a concrete solver for real manipulators.

I am wondering where I should commit the code I have produced:

  • should it be a new repository? If so, how can I create a new repo under existing organizations?
  • should it be a PR in a specific repository? If so, which repository should it be?

For your convenience, the library has been released on CodeOcean: Code Ocean

10 posts - 4 participants

Read full topic

by v8p1197 on January 20, 2025 02:21 PM

Announcing ZigROS! build ROS with the zig build system
from ROS Discourse General

Hello all,

I’d like to share a project I’ve been tinkering away at for a few months, ZigROS. ZigROS uses the zig toolchain to build rcl and rclcpp along with all their dependencies directly.

ZigROS is focused on creating static builds for simplified deployments. The Zig tooling makes this very straight forward. The zig toolchain supports static and dynamic linking with both arbitrary glibc versions and musl out of the box, as well as cross compilation.

ZigROS is capable of building the rclcpp stack in under 2 minutes on modern hardware, and producing statically linked binaries under 5MB that will run standalone on any linux systems.

The zig toolchain puts emphasis on being self contained, and ZigROS follows that ethos. The only dependency is the zig compiler, all other build and runtime dependencies (including python) are brought in and built.

Check out this example repo to see it in action.

Currently the project handles rcl, rclcpp, and all the needed message generation for interfaces. Only the base rclcpp is supported so far (no actions or lifecycle support just yet) but I do plan on continuing to improve feature support.

Given that the main goal of this project is ease of static builds, not all ROS projects will be compatible. For starters building anything with a runtime dependency on python or shared libraries won’t work. It also requires providing a build.zig file to build the project, though the API there is very straight forward.

I invite anyone curious about zig, or anyone interested in experimenting with static builds to give it a try. Setup is as straight forward as installing zig 0.13 and building the example repo.

For deployments to edge hardware like a raspberry pi or similar embedded linux system, the static linking and ease of cross compilation offered here could be a valuable alternative to the main build system.

Let me know if there are any questions or if you’re interested in collaborating.

Thanks!

14 posts - 7 participants

Read full topic

by zig-robotics on January 20, 2025 05:40 AM

New Packages for Jazzy Jalisco 2025-01-20
from ROS Discourse General

Hello there everyone!

We’re happy to announce 49 new packages (including rmw_zenoh :wink:) and 244 updates are now available in ROS 2 Jazzy Jalisco :jazzy: :jazzy: :jazzy: .

This sync was tagged as jazzy/2025-01-20 .

Package Updates for jazzy

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

Added Packages [49]:

  • ros-jazzy-automatika-ros-sugar: 0.2.5-1
  • ros-jazzy-autoware-internal-debug-msgs: 1.3.0-1
  • ros-jazzy-autoware-internal-perception-msgs: 1.3.0-1
  • ros-jazzy-clearpath-bt-joy: 2.0.0-1
  • ros-jazzy-clearpath-common: 2.0.0-1
  • ros-jazzy-clearpath-config: 2.0.1-1
  • ros-jazzy-clearpath-control: 2.0.0-1
  • ros-jazzy-clearpath-customization: 2.0.0-1
  • ros-jazzy-clearpath-description: 2.0.0-1
  • ros-jazzy-clearpath-generator-common: 2.0.0-1
  • ros-jazzy-clearpath-manipulators: 2.0.0-1
  • ros-jazzy-clearpath-manipulators-description: 2.0.0-1
  • ros-jazzy-clearpath-mounts-description: 2.0.0-1
  • ros-jazzy-clearpath-platform-description: 2.0.0-1
  • ros-jazzy-clearpath-sensors-description: 2.0.0-1
  • ros-jazzy-coal: 3.0.0-1
  • ros-jazzy-feetech-ros2-driver: 0.1.0-3
  • ros-jazzy-generate-parameter-library-example-external: 0.4.0-1
  • ros-jazzy-jacro: 0.2.0-2
  • ros-jazzy-kinematics-interface-pinocchio: 0.0.1-1
  • ros-jazzy-mola-state-estimation: 1.6.1-1
  • ros-jazzy-mola-state-estimation-simple: 1.6.1-1
  • ros-jazzy-mola-state-estimation-smoother: 1.6.1-1
  • ros-jazzy-plansys2-bringup: 2.0.18-1
  • ros-jazzy-plansys2-bt-actions: 2.0.18-1
  • ros-jazzy-plansys2-terminal: 2.0.18-1
  • ros-jazzy-plansys2-tests: 2.0.18-1
  • ros-jazzy-py-trees-ros-viewer: 0.2.5-1
  • ros-jazzy-rmf-demos-assets: 2.3.0-1
  • ros-jazzy-rmf-demos-bridges: 2.3.0-1
  • ros-jazzy-rmf-demos-fleet-adapter: 2.3.0-1
  • ros-jazzy-rmf-demos-tasks: 2.3.0-1
  • ros-jazzy-rmw-zenoh-cpp: 0.2.0-1
  • ros-jazzy-zenoh-cpp-vendor: 0.2.0-1

Updated Packages [244]:

  • ros-jazzy-ackermann-steering-controller: 4.18.0-1 → 4.19.0-1
  • ros-jazzy-admittance-controller: 4.18.0-1 → 4.19.0-1
  • ros-jazzy-autoware-internal-msgs: 1.1.0-1 → 1.3.0-1
  • ros-jazzy-bicycle-steering-controller: 4.18.0-1 → 4.19.0-1
  • ros-jazzy-camera-ros: 0.2.1-1 → 0.3.0-1
  • ros-jazzy-clearpath-motor-msgs: 1.0.1-1 → 2.0.0-1
  • ros-jazzy-clearpath-msgs: 1.0.1-1 → 2.0.0-1
  • ros-jazzy-clearpath-platform-msgs: 1.0.1-1 → 2.0.0-1
  • ros-jazzy-control-toolbox: 3.4.0-1 → 3.5.0-1
  • ros-jazzy-controller-interface: 4.21.0-1 → 4.24.0-1
  • ros-jazzy-controller-manager: 4.21.0-1 → 4.24.0-1
  • ros-jazzy-controller-manager-msgs: 4.21.0-1 → 4.24.0-1
  • ros-jazzy-depthai: 2.28.0-1 → 2.29.0-1
  • ros-jazzy-depthai-bridge: 2.10.3-1 → 2.10.5-1
  • ros-jazzy-depthai-descriptions: 2.10.3-1 → 2.10.5-1
  • ros-jazzy-depthai-examples: 2.10.3-1 → 2.10.5-1
  • ros-jazzy-depthai-filters: 2.10.3-1 → 2.10.5-1
  • ros-jazzy-depthai-ros: 2.10.3-1 → 2.10.5-1
  • ros-jazzy-depthai-ros-driver: 2.10.3-1 → 2.10.5-1
  • ros-jazzy-depthai-ros-msgs: 2.10.3-1 → 2.10.5-1
  • ros-jazzy-diff-drive-controller: 4.18.0-1 → 4.19.0-1
  • ros-jazzy-effort-controllers: 4.18.0-1 → 4.19.0-1
  • ros-jazzy-examples-tf2-py: 0.36.7-1 → 0.36.8-1
  • ros-jazzy-force-torque-sensor-broadcaster: 4.18.0-1 → 4.19.0-1
  • ros-jazzy-forward-command-controller: 4.18.0-1 → 4.19.0-1
  • ros-jazzy-generate-parameter-library: 0.3.9-1 → 0.4.0-1
  • ros-jazzy-generate-parameter-library-example: 0.3.9-1 → 0.4.0-1
  • ros-jazzy-generate-parameter-library-py: 0.3.9-1 → 0.4.0-1
  • ros-jazzy-generate-parameter-module-example: 0.3.9-1 → 0.4.0-1
  • ros-jazzy-geometry2: 0.36.7-1 → 0.36.8-1
  • ros-jazzy-gpio-controllers: 4.18.0-1 → 4.19.0-1
  • ros-jazzy-gripper-controllers: 4.18.0-1 → 4.19.0-1
  • ros-jazzy-gz-ros2-control: 1.2.9-1 → 1.2.10-1
  • ros-jazzy-gz-ros2-control-demos: 1.2.9-1 → 1.2.10-1
  • ros-jazzy-gz-sim-vendor: 0.0.6-1 → 0.0.7-1
  • ros-jazzy-hardware-interface: 4.21.0-1 → 4.24.0-1
  • ros-jazzy-hardware-interface-testing: 4.21.0-1 → 4.24.0-1
  • ros-jazzy-imu-sensor-broadcaster: 4.18.0-1 → 4.19.0-1
  • ros-jazzy-joint-limits: 4.21.0-1 → 4.24.0-1
  • ros-jazzy-joint-state-broadcaster: 4.18.0-1 → 4.19.0-1
  • ros-jazzy-joint-trajectory-controller: 4.18.0-1 → 4.19.0-1
  • ros-jazzy-kitti-metrics-eval: 1.4.0-1 → 1.5.1-1
  • ros-jazzy-libcamera: 0.3.2-1 → 0.4.0-1
  • ros-jazzy-mecanum-drive-controller: 4.18.0-1 → 4.19.0-1
  • ros-jazzy-mola: 1.4.0-1 → 1.5.1-1
  • ros-jazzy-mola-bridge-ros2: 1.4.0-1 → 1.5.1-1
  • ros-jazzy-mola-demos: 1.4.0-1 → 1.5.1-1
  • ros-jazzy-mola-imu-preintegration: 1.4.0-1 → 1.6.1-1
  • ros-jazzy-mola-input-euroc-dataset: 1.4.0-1 → 1.5.1-1
  • ros-jazzy-mola-input-kitti-dataset: 1.4.0-1 → 1.5.1-1
  • ros-jazzy-mola-input-kitti360-dataset: 1.4.0-1 → 1.5.1-1
  • ros-jazzy-mola-input-mulran-dataset: 1.4.0-1 → 1.5.1-1
  • ros-jazzy-mola-input-paris-luco-dataset: 1.4.0-1 → 1.5.1-1
  • ros-jazzy-mola-input-rawlog: 1.4.0-1 → 1.5.1-1
  • ros-jazzy-mola-input-rosbag2: 1.4.0-1 → 1.5.1-1
  • ros-jazzy-mola-kernel: 1.4.0-1 → 1.5.1-1
  • ros-jazzy-mola-launcher: 1.4.0-1 → 1.5.1-1
  • ros-jazzy-mola-lidar-odometry: 0.4.0-1 → 0.5.4-1
  • ros-jazzy-mola-metric-maps: 1.4.0-1 → 1.5.1-1
  • ros-jazzy-mola-msgs: 1.4.0-1 → 1.5.1-1
  • ros-jazzy-mola-pose-list: 1.4.0-1 → 1.5.1-1
  • ros-jazzy-mola-relocalization: 1.4.0-1 → 1.5.1-1
  • ros-jazzy-mola-test-datasets: 0.3.4-1 → 0.4.0-1
  • ros-jazzy-mola-traj-tools: 1.4.0-1 → 1.5.1-1
  • ros-jazzy-mola-viz: 1.4.0-1 → 1.5.1-1
  • ros-jazzy-mola-yaml: 1.4.0-1 → 1.5.1-1
  • ros-jazzy-mvsim: 0.12.0-1 → 0.13.0-1
  • ros-jazzy-parallel-gripper-controller: 4.18.0-1 → 4.19.0-1
  • ros-jazzy-parameter-traits: 0.3.9-1 → 0.4.0-1
  • ros-jazzy-pid-controller: 4.18.0-1 → 4.19.0-1
  • ros-jazzy-plansys2-core: 2.0.15-1 → 2.0.18-1
  • ros-jazzy-plansys2-domain-expert: 2.0.15-1 → 2.0.18-1
  • ros-jazzy-plansys2-executor: 2.0.15-1 → 2.0.18-1
  • ros-jazzy-plansys2-lifecycle-manager: 2.0.15-1 → 2.0.18-1
  • ros-jazzy-plansys2-msgs: 2.0.15-1 → 2.0.18-1
  • ros-jazzy-plansys2-pddl-parser: 2.0.15-1 → 2.0.18-1
  • ros-jazzy-plansys2-planner: 2.0.15-1 → 2.0.18-1
  • ros-jazzy-plansys2-popf-plan-solver: 2.0.15-1 → 2.0.18-1
  • ros-jazzy-plansys2-problem-expert: 2.0.15-1 → 2.0.18-1
  • ros-jazzy-plansys2-support-py: 2.0.15-1 → 2.0.18-1
  • ros-jazzy-plansys2-tools: 2.0.15-1 → 2.0.18-1
  • ros-jazzy-pose-broadcaster: 4.18.0-1 → 4.19.0-1
  • ros-jazzy-position-controllers: 4.18.0-1 → 4.19.0-1
  • ros-jazzy-py-trees: 2.2.1-4 → 2.3.0-1
  • ros-jazzy-py-trees-js: 0.6.4-1 → 0.6.6-1
  • ros-jazzy-py-trees-ros: 2.2.2-4 → 2.3.0-1
  • ros-jazzy-py-trees-ros-interfaces: 2.1.0-4 → 2.1.1-1
  • ros-jazzy-range-sensor-broadcaster: 4.18.0-1 → 4.19.0-1
  • ros-jazzy-realtime-tools: 3.0.0-1 → 3.1.0-1
  • ros-jazzy-rmf-building-map-tools: 1.9.1-1 → 1.9.2-1
  • ros-jazzy-rmf-traffic-editor: 1.9.1-1 → 1.9.2-1
  • ros-jazzy-rmf-traffic-editor-assets: 1.9.1-1 → 1.9.2-1
  • ros-jazzy-rmf-traffic-editor-test-maps: 1.9.1-1 → 1.9.2-1
  • ros-jazzy-ros2-control: 4.21.0-1 → 4.24.0-1
  • ros-jazzy-ros2-control-test-assets: 4.21.0-1 → 4.24.0-1
  • ros-jazzy-ros2-controllers: 4.18.0-1 → 4.19.0-1
  • ros-jazzy-ros2-controllers-test-nodes: 4.18.0-1 → 4.19.0-1
  • ros-jazzy-ros2controlcli: 4.21.0-1 → 4.24.0-1
  • ros-jazzy-rqt-controller-manager: 4.21.0-1 → 4.24.0-1
  • ros-jazzy-rqt-joint-trajectory-controller: 4.18.0-1 → 4.19.0-1
  • ros-jazzy-rviz-assimp-vendor: 14.1.6-1 → 14.1.7-1
  • ros-jazzy-rviz-common: 14.1.6-1 → 14.1.7-1
  • ros-jazzy-rviz-default-plugins: 14.1.6-1 → 14.1.7-1
  • ros-jazzy-rviz-ogre-vendor: 14.1.6-1 → 14.1.7-1
  • ros-jazzy-rviz-rendering: 14.1.6-1 → 14.1.7-1
  • ros-jazzy-rviz-rendering-tests: 14.1.6-1 → 14.1.7-1
  • ros-jazzy-rviz-visual-testing-framework: 14.1.6-1 → 14.1.7-1
  • ros-jazzy-rviz2: 14.1.6-1 → 14.1.7-1
  • ros-jazzy-steering-controllers-library: 4.18.0-1 → 4.19.0-1
  • ros-jazzy-tensorrt-cmake-module: 0.0.3-4 → 0.0.4-1
  • ros-jazzy-tf2: 0.36.7-1 → 0.36.8-1
  • ros-jazzy-tf2-bullet: 0.36.7-1 → 0.36.8-1
  • ros-jazzy-tf2-eigen: 0.36.7-1 → 0.36.8-1
  • ros-jazzy-tf2-eigen-kdl: 0.36.7-1 → 0.36.8-1
  • ros-jazzy-tf2-geometry-msgs: 0.36.7-1 → 0.36.8-1
  • ros-jazzy-tf2-kdl: 0.36.7-1 → 0.36.8-1
  • ros-jazzy-tf2-msgs: 0.36.7-1 → 0.36.8-1
  • ros-jazzy-tf2-py: 0.36.7-1 → 0.36.8-1
  • ros-jazzy-tf2-ros: 0.36.7-1 → 0.36.8-1
  • ros-jazzy-tf2-ros-py: 0.36.7-1 → 0.36.8-1
  • ros-jazzy-tf2-sensor-msgs: 0.36.7-1 → 0.36.8-1
  • ros-jazzy-tf2-tools: 0.36.7-1 → 0.36.8-1
  • ros-jazzy-transmission-interface: 4.21.0-1 → 4.24.0-1
  • ros-jazzy-tricycle-controller: 4.18.0-1 → 4.19.0-1
  • ros-jazzy-tricycle-steering-controller: 4.18.0-1 → 4.19.0-1
  • ros-jazzy-tuw-airskin-msgs: 0.2.4-1 → 0.2.5-1
  • ros-jazzy-tuw-geo-msgs: 0.2.4-1 → 0.2.5-1
  • ros-jazzy-tuw-geometry-msgs: 0.2.4-1 → 0.2.5-1
  • ros-jazzy-tuw-graph-msgs: 0.2.4-1 → 0.2.5-1
  • ros-jazzy-tuw-msgs: 0.2.4-1 → 0.2.5-1
  • ros-jazzy-tuw-multi-robot-msgs: 0.2.4-1 → 0.2.5-1
  • ros-jazzy-tuw-nav-msgs: 0.2.4-1 → 0.2.5-1
  • ros-jazzy-tuw-object-map-msgs: 0.2.4-1 → 0.2.5-1
  • ros-jazzy-tuw-object-msgs: 0.2.4-1 → 0.2.5-1
  • ros-jazzy-tuw-std-msgs: 0.2.4-1 → 0.2.5-1
  • ros-jazzy-ur: 3.0.0-1 → 3.0.1-1
  • ros-jazzy-ur-calibration: 3.0.0-1 → 3.0.1-1
  • ros-jazzy-ur-controllers: 3.0.0-1 → 3.0.1-1
  • ros-jazzy-ur-dashboard-msgs: 3.0.0-1 → 3.0.1-1
  • ros-jazzy-ur-moveit-config: 3.0.0-1 → 3.0.1-1
  • ros-jazzy-ur-robot-driver: 3.0.0-1 → 3.0.1-1
  • ros-jazzy-velocity-controllers: 4.18.0-1 → 4.19.0-1

Removed Packages [4]:

  • ros-jazzy-mola-navstate-fg
  • ros-jazzy-mola-navstate-fg-dbgsym
  • ros-jazzy-mola-navstate-fuse
  • ros-jazzy-mola-navstate-fuse-dbgsym

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

  • Adam Serafin
  • Addisu Z. Taddese
  • Alejandro Hernandez
  • Alejandro Hernandez Cordero
  • Alejandro Hernández
  • Automatika Robotics
  • Bence Magyar
  • Benjamin Binder
  • Berkay Karaman
  • Brandon Ong
  • Chris Iverach-Brereton
  • Christian Rauch
  • Daisuke Nishimatsu
  • Daniel Stonier
  • Felix Exner
  • Francisco Martin Rico
  • George Todoran
  • Jafar Uruc
  • Jose Luis Blanco-Claraco
  • Jose-Luis Blanco-Claraco
  • Joseph Mirabel
  • Luis Camero
  • M. Fatih Cırıt
  • Markus Bader
  • Morgan Quigley
  • Paul Gesel
  • Roni Kreinin
  • Ryohsuke Mitsudome
  • Saif Sidhik
  • Tyler Weaver
  • Xi Yu Oh
  • Yadunund
  • paul

Enjoy! :jazzy:

1 post - 1 participant

Read full topic

by marcogg on January 20, 2025 05:32 AM

January 17, 2025
ROS News for the Week of January 13th, 2024
from ROS Discourse General

ROS News for the Week of January 13th, 2024


Meetup at Photonics West 2025

If you happen to be in San Francisco for Photonics West we’re organizing and informal ROS meetup with OpenCV. If you are in the Bay Area I recommend taking an afternoon to walk the floor. The event is free and almost every camera and lidar vendor will be there.


Jan25GCM

Our next Gazebo Community Meeting will be on 2025-01-29 Well be talking about a new Gazebo Harmonic simulation for Hello Robot’s new Stretch robot.

ROSBTBJan25 (1)

On 2025-01-30 join us ROS By-The-Bay! @tomoyafujita and @Yadunund will be presenting.


3D22D
Check out this new ROS 2 package for 3D voxel map to 2D occupancy map conversion.


5b0f9d98e535bbac2b35006da16e5fb04c249506_2_690x314 (1)

Along similar lines, there is a new ROS 2 camera lidar fusion package that’s been released.


Select1

There’s a new tutorial in the ROS 2 docs thanks to @DLu: on how to build a custom RViz panel.


Events

News

ROS

Got a minute? :mantelpiece_clock:

Lightning talks - Day 2

Remember this ROSCon 2023 lightning talk from @methylDragon? I would love it if we had one new contributor close this ticket in the ROS 2 documentation. This is a great opportunity to learn more about lifecycle nodes and to become a ROS 2 contributor.

1 post - 1 participant

Read full topic

by Katherine_Scott on January 17, 2025 08:21 PM

New Packages for Noetic 2025-01-17
from ROS Discourse General

We’re happy to announce 1 new packages and 32 updates are now available in ROS Noetic. This sync was tagged as noetic/2025-01-17.

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

Package Updates for ROS Noetic

Added Packages [1]:

Updated Packages [32]:

Removed Packages [0]:

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

  • Adam Serafin
  • Atsushi Watanabe
  • Jose-Luis Blanco-Claraco
  • Martin Pecka
  • Rob Fisher
  • Robert Haschke

2 posts - 2 participants

Read full topic

by sloretz on January 17, 2025 07:31 PM

New Packages for ROS 2 Rolling Ridley 2025-01-17
from ROS Discourse General

Hello everyone!

We’re happy to announce 22 new package and 137 updates are now available in ROS 2 Rolling Ridley :rolling_head: :rolling:

This sync was tagged as rolling/2025-01-17 .

Package Updates for rolling

Added Packages [22]:

  • ros-rolling-apriltag-ros: 3.2.2-1
  • ros-rolling-apriltag-ros-dbgsym: 3.2.2-1
  • ros-rolling-autoware-lanelet2-extension: 0.6.2-1
  • ros-rolling-autoware-lanelet2-extension-dbgsym: 0.6.2-1
  • ros-rolling-autoware-lanelet2-extension-python: 0.6.2-1
  • ros-rolling-autoware-lanelet2-extension-python-dbgsym: 0.6.2-1
  • ros-rolling-coal: 3.0.0-1
  • ros-rolling-coal-dbgsym: 3.0.0-1
  • ros-rolling-generate-parameter-library-example-external: 0.4.0-1
  • ros-rolling-generate-parameter-library-example-external-dbgsym: 0.4.0-1
  • ros-rolling-mola-lidar-odometry: 0.5.4-1
  • ros-rolling-mola-lidar-odometry-dbgsym: 0.5.4-1
  • ros-rolling-mola-state-estimation: 1.6.1-1
  • ros-rolling-mola-state-estimation-simple: 1.6.1-1
  • ros-rolling-mola-state-estimation-simple-dbgsym: 1.6.1-1
  • ros-rolling-mola-state-estimation-smoother: 1.6.1-1
  • ros-rolling-mola-state-estimation-smoother-dbgsym: 1.6.1-1
  • ros-rolling-py-trees-ros-viewer: 0.2.5-1
  • ros-rolling-rmw-zenoh-cpp: 0.3.0-1
  • ros-rolling-rmw-zenoh-cpp-dbgsym: 0.3.0-1
  • ros-rolling-zenoh-cpp-vendor: 0.3.0-1
  • ros-rolling-zenoh-cpp-vendor-dbgsym: 0.3.0-1

Updated Packages [137]:

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:

  • Addisu Z. Taddese
  • Aditya Pande
  • Alejandro Hernandez
  • Alejandro Hernandez Cordero
  • Automatika Robotics
  • Bence Magyar
  • Chris Lalancette
  • Christian Rauch
  • Daisuke Nishimatsu
  • Daniel Stonier
  • Dharini Dutia
  • Jose-Luis Blanco-Claraco
  • Joseph Mirabel
  • Mamoru Sobue
  • Paul Gesel
  • Robert Haschke
  • Steve Macenski
  • Tyler Weaver
  • Yadunund
  • mitsudome-r
  • paul

1 post - 1 participant

Read full topic

by Yadunund on January 17, 2025 07:25 PM

FOSDEM 2025 Robotics Devroom Schedule
from ROS Discourse General

Hi all!

2 more weeks until FOSDEM 2025 starts! The Robotics and Simulation developer room has the schedule and speakers all ready to go! We had a lot of submissions since our CfP so we couldn’t accept all but we are quite excited about the talks that will be present.

Info:

Schedule

  • 13:15 - Room Welcome
  • 13:20 - Lightning round 1:
    • Jonas Dech - PyCRAM, A Framework for Cognitive Robot Control
    • Roland Meertens - All my frustrations with ROS summed up in 5 minutes
    • Edgar Riba - Kornia-rs: Low level Computer Vision and 3D Library in Rust
    • Loïc Vigneron - Building a robot powered with Raspberry pis and Arduinos from a super fast Traxxas RC car
  • 13:45 - Ignacio Davila Gallesio, Agustin Alba Chicar - Accelerating robotics development through simulation
  • 14:15 - Jan Hanca - O3DE: Creating realistic simulations with open-source game engine
  • 14:45 - Said Alvarado-Marin - Repurposing Valve’s SteamVR 2.0 Technology to Develop an Open-Source, Low-Cost Motion Capture System for Robotics
  • 15:15 - Julien Enoch - Eclipse Zenoh: Understanding the Protocol and its Potential in Robotic
  • 15:45 - JoseMaria Cañas Plaza, Javier Izquierdo - BTstudio, a web tool for programming robots with Behavior Trees
  • 16:15 - Pierre Kancir - ArduPilot : Trusted, Versatile and FOSS autopilot for all and everything
  • 16:40 - Lightning round 2:
    • Michel Hidalgo, Lucas Chiesa - Whales use Lighthouses too: Open source positioning for open source robots
    • Ramon Roche - Build, Launch, and Soar with Dronecode: The infrastructure ecosystem for the development of autonomous aerial robotics.
    • Arne Baeyens - Integration and unit testing in ROS 2
    • Jose Luis Rivero - ROS in transition: a new organizational path under the Open Source Robotics Alliance

Make sure to keep an eye on the official Robotics and Simulation Development room schedule for any updates. Also you can watch a recording of the talks if you can’t make it yourself. The rest of you, we will see you in Brussels!

Fosdev-ogłoszenie-1

4 posts - 2 participants

Read full topic

by KimMcG on January 17, 2025 02:41 PM

January 16, 2025
Customizable Template for Docker Environment Setup
from ROS Discourse General

Hello everyone,

I’d like to share and release an easy to use repository I’ve created to help streamline and simplify the setup process for different ROS environments and it’s dependencies using Docker. The template provides a flexible and easy-to-use framework that allows you to configure the environment tailored to your specific needs.

I have been working on setting environments and packages that range across different OS and Distro requirements and managing them with Docker was definitely the shot. In this process I managed to shape this template for easily setting up different ROS envs with minimal efforts in listing and installing dependencies. My goal with this Docker template was to speed up the setup process, make it smoother, and eliminate the repetitive steps needed to get everything running.

Key Features:

  • Pre-configured ROS env: The template comes with an initial ROS Noetic base version, making it quick to start developing without many additional setup steps.
  • Configurable .env file: Easily modify arguments in the .env and Dockerfile to fit your specific ROS version, dependencies, and configurations.
  • Customization: Easily modify the template to add any extra dependencies or changes as needed.

How it works:

  • Simply clone the repository, customize the files mentioned in the README.md for your environment, and build your Docker image.
  • The template can be used for both ROS 1 and ROS 2 setups, and it integrates seamlessly with your ROS packages and dependencies.

There is scope for more work here and I’d love to get feedback from the community on how this template can be improved to make this as useful as possible for everyone. So if you have any suggestions, improvements, or features you’d like to see, please feel free to share! :raised_hands: With this as a starter, I look forward to contributing more!!

You can find the repository here: GitHub - dipshikha-das/docker-env-blueprints at ros-any

Looking forward to your feedback! :star2:

3 posts - 2 participants

Read full topic

by DipshikhaDas on January 16, 2025 05:16 PM

The forgotten gem that is environment hooks and DSV
from ROS Discourse General

Greetings fellow robotics enthusiasts :rocket::heart:,

In the good old days of ROS 1, we had a useful little cmake command catkin_add_env_hooks where you could provide a list of shell scripts for different shells (bash, sh, zsh, …) to be sourced when the ROS workspace is sourced.
You could use this to register your library in an environment variable, e.g., to make a plugin findable, to create your own environment variables or helper functions, or whatever else you needed to do when sourcing the workspace.

This command was improved (as many things were) for ROS2 which now provides the ament_environment_hooks command.
In addition to specific shell scripts, you could also use DSV files, which is a simple format that allows you to modify environment variables.
For example, you can prepend or append your library path to a plugin environment variable.
The advantage here is that it’s supposedly faster, but most importantly, it is cross-platform.

Unfortunately, this feature is very well hidden and apparently, only a select few seem to know about it judging from the number of READMEs I’ve seen that include:

Then you have to make this library findable by running export RANDOM_LIB_PLUGIN_PATH=$(instruction that some people will certainly have issues with)/somepath/lib:${RANDOM_LIB_PLUGIN_PATH}

So, this post hopefully provides someone (maybe you) with the information that this gem exists and might be helpful to you.
I’m pretty sure I have seen documentation for DSV and environment hooks at some point but even with the flaky knowledge that it should exist, I couldn’t find it on Google.
Here’s the closest thing that I could find: ros_gz_project_template/ros_gz_example_gazebo/hooks at main · gazebosim/ros_gz_project_template · GitHub
(See @gavanderhoorn’s comment)

The only downside I know of is that the ROS binary workspace is currently broken and ignores DSV files, so they only work in the source workspace :person_shrugging:
See DSV files are not sourced in binary workspace · Issue #1613 · ros2/ros2 · GitHub
However, you can also register sh or bash scripts and they should work in both binary and source workspaces.

Some examples of my own:

Here I register my QML ROS 2 plugin to be found by QML. Please ignore the .in ending, I just noticed that I changed the path and don’t need any template processing anymore, so it could just be a .dsv.

In this WIP package, it’s used to register a command that makes working with a ROS 2 source workspace and robots a bit more comfortable:

This just serves to show that you can also use environment hooks for more complex functionality. Please ignore the current documentation status, which may be a bit outdated. You can expect a release post sometime in the future with more polished documentation.

I hope this information is useful of you.
If not, here’s an AI-generated cat riding on an AI-knockoff Spot to make up for the time you took to read this:

image

5 posts - 3 participants

Read full topic

by StefanFabian on January 16, 2025 09:34 AM

January 15, 2025
:checkered_flag: Gazebo Citadel officially end-of-life [x-post Gazebo Sim Community]
from ROS Discourse General

Dear ROS Community,

Gazebo Citadel has reached end-of-life (EOL) as of December, 2024. Citadel was released in December, 2019 and it was the third major release of Gazebo (named Ignition back then). It was a milestone release because it was the first Long Term Supported (LTS) release of Gazebo with support lasting 5 years. Citadel introduced various exciting features, including SDF frame semantics, Animated actors, Visualization markers, Thermal camera sensors, CLI to Upload models to Fuel, and Rechargeable batteries to name a few. See the entire list of features on the Release Features page.

We recommend all Citadel 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 will require migrating from Ignition to Gazebo, so please follow the migration guide. Also, be sure to check the release highlights for Harmonic and Ionic in addition to checking each library’s migration guide.

As part of the Citadel 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 version Final release
gz-gui3 (ignition-gui3) 3.12.0
gz-launch2 (ignition-launch2) 2.3.1
gz-physics2 (ignition-physics2) 2.6.2
gz-rendering3 (ignition-rendering3) 3.7.2
gz-sensors3 (ignition-sensors3) 3.6.0
gz-sim3 (ignition-gazebo3) 3.15.1

We sincerely thank all contributors to all libraries in Citadel :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 Citadel:

  • 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 Citadel goes end of life:

  • Gazebo Citadel 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 January 15, 2025 05:54 PM

Live RMW Zenoh Workshop
from ROS Discourse General

Hi all,

For everyone interested in learning more about RMW Zenoh, our team will host a workshop live on YouTube (https://www.youtube.com/watch?v=_NqaILDTT2s) on 2025-01-21T16:00:00Z UTC. You can add this workshop to your calendar: (Live) RMW Zenoh Workshop.

It’ll be similar to the workshop we presented at ROSCon 2024 with @Yadunund and Steven Palma, and everyone can ask our team questions live. This is perfect for those who are ready to deploy RMW Zenoh or are already doing so but have questions.

For those who want to learn more about Zenoh and its features, ahead of trying RMW Zenoh, we have a second webinar on 2025-02-11T16:00:00Z UTC. The webinar is titled “Zenoh Advanced Features Workshop”, and it’ll be live on YouTube (https://www.youtube.com/watch?v=UfH6KFJ3v0c). You can set up a calendar reminder: (Live) Zenoh Advanced Features Workshop.

If you have any questions ahead of the webinars, let me know.

1 post - 1 participant

Read full topic

by JEnoch on January 15, 2025 11:18 AM


Powered by the awesome: Planet