[Documentation] [TitleIndex] [WordIndex] 

Planet ROS

Planet ROS - http://planet.ros.org

Planet ROS - http://planet.ros.org[WWW] http://planet.ros.org

ROS Discourse General: New packages for ROS 2 Rolling Ridley 2025-03-28

Hello everyone!

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

This sync was tagged as rolling/2025-03-28 .

Package Updates for rolling

Added Packages [13]:

Updated Packages [188]:

Removed Packages [1]:

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

1 post - 1 participant

Read full topic

[WWW] https://discourse.ros.org/t/new-packages-for-ros-2-rolling-ridley-2025-03-28/42863

ROS Discourse General: ROS News for the Week of March 24th, 2025

ROS News for the Week of March 24th, 2025


October 27th - 29th (1)

The website for ROSCon 2025 in the Republic of Singapore is now live. :tada:

Three big things to know:

ROSConDiversity

Scholarship details are available here and applications are due 2025-04-18T07:00:00Z UTC.

ib2
ib2_sim

Our colleagues over at JAXA have released the source code for the their robot on the international space station. – ROS / Gazebo source code – also available for Isaac Sim.


omni
Check out this amazing 3D printed ROS 2 omnidirectional robot – source code.


image

It was the European Robotics Forum this week. OSRA members Intrinsic, Bosch, Huawei, Husarion and ROS-I were major supporters. Our colleagues in the area also organized a ROS meetup (pictured above).


Events

News

ROS

Have a Minute :watch: ?

It would be really awesome if someone from the community could fix this autocomplete issue with ros2 topic pub before the Kilted feature freeze.

We would also appreciate some help with the official ros_gz documentation.

Please just assign yourself the ticket and go to town!

1 post - 1 participant

Read full topic

[WWW] https://discourse.ros.org/t/ros-news-for-the-week-of-march-24th-2025/42861

ROS Discourse General: Faster rclpy executor now in Rolling

I’m announcing a new executor that’s now available for rclpy in Rolling, which is a port of the rclcpp EventsExecutor approach for use in Python. This was motivated by the large increase in CPU usage my company (Merlin Labs) experienced when porting an existing project from Noetic to Iron, most especially among our Python-based nodes. More background and benchmarks are available here, but the upshot is CPU usage has been observed to be as little as a tenth of that of the default SingleThreadedExecutor for some workloads!

Functionally, it should largely be a drop-in replacement substituting rclpy.experimental.EventsExecutor for rclpy.executors.SingleThreadedExecutor in your code. Being single threaded, it does functionally ignore all callback groups and treat every event as mutually exclusive in its current form. Additionally, it may start to get inefficient if you have a large number of ROS timers running in the same process.

This feature is expected to be part of the upcoming Kilted release, and there is also an effort underway to backport it to Jazzy.

3 posts - 3 participants

Read full topic

[WWW] https://discourse.ros.org/t/faster-rclpy-executor-now-in-rolling/42852

ROS Discourse General: Floating Joints in Moveit2

Hello ROS people,

Has anyone successfully used floating joints with MoveIt 2?

I’m trying to describe a UAV in URDF format to leverage MoveIt 2’s libraries for planning.I am mostly concerned with 3D translation, not orientation.

In theory, a floating joint + position_only_ik:True would do the trick. However, in practice, I can’t get the Joint State Publisher to recognize the joint, even though MoveIt 2’s documentation claims support for floating joints.

While I understand that other methods may be simpler for UAV planning and that the purpose of Moveit2 and URDF is not to plan for UAVs, I want to explore whether something like this is possible. I find it hard to believe that the best solution would be to stack three prismatic joints with intermediate links to achieve 3D translation.

4 posts - 4 participants

Read full topic

[WWW] https://discourse.ros.org/t/floating-joints-in-moveit2/42835

ROS Discourse General: Proposal to Extend `JointLimits` in URDF

Hello Community!

We, the ros2_control PMC, would like to open this discussion to propose an extension to the JointLimits struct in URDF XML and gather community feedback.

ROS 2 is designed to integrate seamlessly with industrial manipulators, service robots, and other robotic ecosystems. While the existing position and velocity limits cover basic use cases, more advanced motion planning and task execution require additional constraints. Specifically, acceleration and jerk limits play a crucial role in ensuring smooth, safe, and precise motion. The proposed PRs introduce these additional limits into the URDF specification, enhancing motion control capabilities:

Once these changes are merged, the next step would be integrating these extended joint limits into the ros2_control ecosystem. This would allow controllers to automatically enforce these constraints, ensuring safer and more precise command execution—without requiring users to manually implement workarounds to respect hardware limits.

We’d love to hear the community’s thoughts on this proposal. Do you see value in adding acceleration and jerk limits to URDF? Are there any potential challenges or alternative approaches we should consider?

A related discussion can be found here: Allow for More Complex Joints in URDF

Looking forward to your feedback!

3 posts - 2 participants

Read full topic

[WWW] https://discourse.ros.org/t/proposal-to-extend-jointlimits-in-urdf/42831

ROS Discourse General: Should all released packages be documented by ros infrastructure?

ROS maintains package-level indexing and documentation with rosindex and rosdoc2 for repos that have entries in rosdistro. There are a variety of reasons why a package in rosdistro might not have their documentation appear, but one reason is because the author did not specify a source or doc repo in their release to rosdistro.

Are there any package authors that for some reason want to have their package released in ROS 2 but not appear in rosindex or rosdoc2?

Presently, rosindex attempts to document packages with no doc or source repo by diving into the release tracks, while rosdoc2 shows nothing. So a package like, e.g. radar_msgs has an entry in rosindex, but not in rosdoc2.

My inclination is to assume that the non-documentation status of these packages is inadvertent rather than deliberate, so I would be inclined to correct the ‘mistake’ by looking into the release entries in rosdistro, and presenting that as the source for documentation This is what rosindex does currently, but not rosdoc2.

Any thoughts on this?

Here is a list of packages with release entries but no doc or source, hence not appearing in rosdoc2:

clearpath_mecanum_drive_controller
ifm3d_core
libg2o
marvelmind_ros2_msgs
nonpersistent_voxel_layer
ompl
ortools_vendor
picknik_ament_copyright
radar_msgs
ros_industrial_cmake_boilerplate
topic_based_ros2_control
gazebo_ros_pkgs

5 posts - 4 participants

Read full topic

[WWW] https://discourse.ros.org/t/should-all-released-packages-be-documented-by-ros-infrastructure/42830

ROS Discourse General: Challenges with ROS2 on commercial robots

I would like to get in touch with companies and organizations that use ROS2 on commercial robots or that are developing with ROS2 for commercial robots. I am especially interested in issues that robot developers currently face when bringing a robot to market. Topics could be difficulties with (fast) system bring-up, graceful degradation, use of lifecycle nodes, heartbeats, DDS, debugging and analyzing nodes, hard real-time requirements, communication with other industrial platforms, updating systems in the field, etc. My goal is to identify common challenges that multiple parties encounter and that we potentially could address in applied research projects.

10 posts - 10 participants

Read full topic

[WWW] https://discourse.ros.org/t/challenges-with-ros2-on-commercial-robots/42784

ROS Discourse General: 📝 New Issue Template Added for ROS 2 Documentation

Hi ROS Developers,

To improve the process of reporting and tracking issues related to the ROS 2 documentation, we have introduced a new issue template! :tada::tada::tada:

This update has been merged in add github issue template. by fujitatomoya · Pull Request #5140 · ros2/ros2_documentation · GitHub and is now online.
The new template provides a structured format for reporting documentation issues, making it easier for contributors to provide relevant details and for maintainers to address them efficiently.

ros2_doc_issue_config

ros2_doc_issue_template

We encourage all contributors to use this template when submitting documentation-related issues to help streamline discussions and improvements. Your feedback is always welcome—let us know if you have any suggestions!

Happy documenting! :rocket::rocket::rocket:

@tomoyafujita
@Katherine_Scott
@christophebedard

1 post - 1 participant

Read full topic

[WWW] https://discourse.ros.org/t/new-issue-template-added-for-ros-2-documentation/42779

ROS Discourse General: Announcing ROSCon 2025 in the Republic of Singapore :tada:

Announcing ROSCon 2025 in the Republic of Singapore :tada:

ROSCon2025
Our call for proposals and diversity scholarship application form are now open and we are currently seeking sponsors for ROSCon 2025!

ROSCon 2025

I am happy to announce that we just launched the ROSCon 2025 website! This year’s ROSCon will take place in the Republic of Singapore 2025-10-27T07:00:00Z UTC→2025-10-29T07:00:00Z UTC.

The Republic of Singapore has a long history of supporting the ROS project and the robotics industry and we’re excited for our Singaporean colleagues to show us what they have been working on! Singapore is home to a number of ROS core contributors, most of the Open-RMF core contributors, our colleagues at ROS Industrial AP and OSRA member organization National Robotics Program of Singapore.

If you’re a ROS developer you won’t want to miss ROSCon 2025; we’ll have most of the ROS core developers and contributors all in one place for three days for talks, workshops, birds-of-a-feather sessions, robot demonstrations, and vendor exhibitions. Last year ROSCon completely sold out, so we recommend you keep an eye on the website and plan to register early.

Sponsor ROSCon 2025

We can’t make ROSCon happen without the generous support of our sponsors. If your organization would like to exhibit at ROSCon you can find our sponsorship prospectus here. We offer five different levels of event sponsorship along with a variety of sponsorship add-ons to increase your exposure. Perhaps you would like to help support one of our many ROSCon Diversity Scholars? Whatever your interests, we encourage you to book your space early, as exhibit space out last year and fully expect it to sell out again this year.

ROSCon Call for Proposals & Important Dates :date:

I am happy to announce that ROSCon CFP opens today, March 24th! We want to encourage everyone in the ROS community to submit their talk and workshop proposals, don’t hold back! We absolutely want to hear about your ROS development experiences. The advice I give to all my interns and employees is to never self-censor, let the CFP reviewers decide if your idea is worth presenting. If you’ve never attended a ROSCon we absolutely want to hear what you have to say!

ROSCon workshop proposals are due 2025-05-05T07:00:00Z UTC and regular session talk proposals are due 2025-06-02T07:00:00Z UTC, about a month later. We plan on having proposals reviewed and finalized by 2025-07-07T07:00:00Z UTC. All of the important event dates are listed below and on the ROSCon website.

ROSCon 2025 Diversity Scholarships :rainbow_flag:

The ROSCon Diversity Scholarship is the only program we offer to help students and new open source contributors attend ROSCon. If you would like to attend ROSCon 2025 but don’t have the financial means, this is our one and only program to help you get there! The scholarship covers ROSCon admission, travel, and shared lodging at the event. We recommend you start your application early! Like last year, this year’s ROSCon diversity scholarship application form is currently open and accepting applications. This year the application deadline for Diversity Scholarships will be 2025-04-18T07:00:00Z UTC, a little less than a month from now.

4 posts - 2 participants

Read full topic

[WWW] https://discourse.ros.org/t/announcing-roscon-2025-in-the-republic-of-singapore/42766

ROS Discourse General: QOI (Quite OK Image) format available as image_transport (lossless RGB(A) 50x faster than PNG)

Today I’ve learned about QOI (Quite OK Image) format (while reading GIMP 3.0 release notes!). I followed the urge and implemented image_transport for it.

It can be used for lossless compression of RGB or RGBA images. Its compression ratio is comparable to lossless PNG, but encoding is 10-50x faster and decoding 2-4x faster. Check the benchmark.

Thanks to our package image_transport_codecs, qoi_image_transport offers not only the normal image_transport functionality (on subtopic “qoi”), but it also provides a pure C++/Python interface to do image encoding and decoding without the need of going through the tedious and unreliable pub/sub cycle. If you’re interested, I’m curious about your opinions on image_transport_codecs and whether such thing should be used as the general backend for image_transport.

Slightly related advertisement:

If you now want to convert some of your bag files and images in them to QOI format, you can utilize our cras_bag_tools/filter_bag utility, e.g. with a recompress config. But feel free to explore also the other implemented filters, e.g. for topic filtering by name/type/size, TF filtering, remapping of topics or fixing wrong frame_ids .

Even less relevant advertisement:

The package is fully REUSE-compatible. This means automated license checking and composition of SBOM is possible. Join the movement and upgrade your packages with REUSE! There is even a handy Github Action for verifying compatibility.

2 posts - 1 participant

Read full topic

[WWW] https://discourse.ros.org/t/qoi-quite-ok-image-format-available-as-image-transport-lossless-rgb-a-50x-faster-than-png/42709

ROS Discourse General: ROS News for the Week of March 17th, 2025 :four_leaf_clover:

ROS News for the Week of March 17th, 2025 :four_leaf_clover:


image

Thanks to some design contributions from our friends at HeloRobo.com the landing page on docs.ros.org just got a facelift!


1 (2)

:cake: The OSRA turned one year old this week! As of this week we have 48 corporate members, five open source projects, and close to 200 individual members.


OSRF Google Summer of Code

The week we launched our 2025 OSRF Google Summer of Code program. JdeRobot is also looking for GSoC students. We’ve also opened up our 2025 Internship open thread. where companies can post their internship opportunities.


image

We had some greatnews out of NVIDIA GTC: Jetson boards will finally run recent Ubuntu releases! No more using Docker containers to run Jazzy on your Jetson!


alignment
Introducing "maps“: Inspect, compare and align multiple grid maps


Publicacion inscribirse

:colombia: Our first ever ROS meetup in Colombia will happen May 24th in Cali!

Events

News

ROS

Got a Minute :alarm_clock:

Why not send us a pull request?

We need someone to help unify the ROS_GZ bridge documentation and another person to fix the documentation for Gazebo plugins. If you are looking for something more technical, why not fix this broken type error exception in Gazebo?

1 post - 1 participant

Read full topic

[WWW] https://discourse.ros.org/t/ros-news-for-the-week-of-march-17th-2025/42704

ROS Discourse General: Is WSL Sufficient for Learning and Using ROS?

Hey everyone,

I’m currently diving into learning and working with ROS (Robot Operating System) for my robotics projects, and I’m considering using Windows Subsystem for Linux (WSL) as my primary development environment. From what I’ve read, WSL is a great option to run Linux tools directly on Windows without the need for dual-booting or setting up a VM, but I’m wondering if it’s fully sufficient for all aspects of ROS development.

Has anyone used WSL for ROS before? Specifically, I’m curious to know if it can handle all the required dependencies, the ROS graphical tools, and simulations like Gazebo or RViz, and whether there are any limitations that might come up. Also, is it good for working with robots like Baxter or other hardware interfaces that might require low-latency communication or more complex setups?

Any tips or experiences you can share would be really helpful!

Thanks in advance!

9 posts - 7 participants

Read full topic

[WWW] https://discourse.ros.org/t/is-wsl-sufficient-for-learning-and-using-ros/42700

ROS Discourse General: New Packages for Noetic 2025-03-20

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

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

Package Updates for ROS Noetic

Added Packages [0]:

Updated Packages [19]:

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:

1 post - 1 participant

Read full topic

[WWW] https://discourse.ros.org/t/new-packages-for-noetic-2025-03-20/42669

ROS Discourse General: Gazebo Sim documentation

Hello guys,
It has been now 2 weeks that I use the new gazebo version (gz) and wow is the doc unhelpfull. Every time I search some thing I find the old version tutorial…
I have a few examples for example :

I am not here to just say this is bad but I want to know if other people feel lost like me and how can we change this situation ?

Hope I don’t make to many people angry !

5 posts - 5 participants

Read full topic

[WWW] https://discourse.ros.org/t/gazebo-sim-documentation/42668

ROS Discourse General: OSRF Google Summer of Code 2025 :sun_with_face:

OSRF Google Summer of Code 2025 :sun_with_face:

OSRF Google Summer of Code

Hi Everyone,

I am excited to announce that all of our Google Summer of Code (GSoC) projects for 2025 are now available online in our GSoC Wiki. If you are unfamiliar with GSoC, it is a summer internship program sponsored by Google that is open to undergraduate and graduate students in most countries (see video below). The GSoC program allows students to work with veteran open source developers over the summer to contribute to open source projects.

This year, all five Open Robotics projects (ROS, Gazebo, Open-RMF, ROS Infrastructure, and ROS Control) will participate in GSoC. This will be our only internship opportunity this year, so we made sure to recruit as many mentors as possible. We will also be posting an open internship thread on ROS Discourse in the next couple days.

2025 Open Robotics Projects

This year we will offer sixteen GSoC projects across our five open source projects. These projects will be mentored or co-mentored by sixteen seasoned contributors from the Open Robotics community. I’ve summarized the projects below, but you can read all about them on our project wiki page.

Project Proposals

Student applications for GSoC will be open from 2025-03-24T07:00:00Z UTC→2025-04-08T07:00:00Z UTC. Students must apply using the application form on the official GSoC website.

After speaking with our mentors I want to call out a few things that we’re looking for in student applications. Students applying to our GSoC projects should make sure to highlight the following things in their application:

Finally, the best way to enhance your GSoC proposal is to connect with our mentors and the ROS community. Consider submitting a pull request to one of our projects. Most Open Robotics project repositories have “Good First Issue” and “Help Wanted” tags in their issue trackers. If you have time, please consider making a small project contribution. For guidance, feel free to join our Discord server.

2 posts - 1 participant

Read full topic

[WWW] https://discourse.ros.org/t/osrf-google-summer-of-code-2025/42653

ROS Discourse General: 💅 docs.ros.org just got a facelift!

docs.ros.org Got a Facelift!

image


Hi everyone,

If you’re anything like me, you probably visit docs.ros.org at least five times a day, and you probably also have at least two dozen bookmarks related to ROS development in your browser. It seems like a good portion of onboarding new ROS users is just pointing them to the ROS documentation and our useful resources.

I’ve been trying to fix this problem for quite a while, and I finally have some good news! Thanks to some wonderful open-source design contributions from Shak and Vlad at HelloRobo.co, we’ve put together a new landing page for the ROS documentation. This new landing page should be your one-stop shop for most of your ROS documentation resources, and it renders well on mobile devices!

Don’t worry, the page still points you to the same ROS documentation, but we’ve managed to include just about everything you could need on one handy page! On the new docs.ros.org page, you’ll find:

If there’s something you think we missed that belongs there, please don’t hesitate to reach out or send us a pull request.

And thanks again Vlad and Shak for contributing their design skills to the project! And thanks @Nuclearsandwich with the deployment help.

11 posts - 8 participants

Read full topic

[WWW] https://discourse.ros.org/t/docs-ros-org-just-got-a-facelift/42639

ROS Discourse General: Can GPS Alone Guide a Mobile Robot Along Line Patterns in Sports Fields?

Hi everyone,

I’m exploring the idea of using GPS sensor exclusively to guide a mobile robot along predefined line patterns on sports fields (such as soccer fields, tracks, or basketball courts). The goal is to rely solely on GPS data for navigation—without the use of cameras, vision systems, or any additional sensors. Is it possible?

My main objective here is to investigate the weaknesses and limitations of using only GPS for precise navigation. This exploration could serve as a foundation for later expansion by incorporating multiple sensors or technologies, but for now, I want to focus on how far GPS alone can take us.

9 posts - 7 participants

Read full topic

[WWW] https://discourse.ros.org/t/can-gps-alone-guide-a-mobile-robot-along-line-patterns-in-sports-fields/42595

ROS Discourse General: ROS Noetic is reaching End of Life in May 2025 – Which additional packages do you need in ROS Noetic ESM?

ROS Noetic is reaching End of Life in May 2025 – Which additional packages do you need in ROS Noetic ESM?

With ROS Noetic and Ubuntu 20.04 approaching EOL, their Extended Security Maintenance (ESM) period begins in April-May this year. During this time, ROS packages inside Ubuntu’s ROS ESM repository will continue receiving five more years of security updates, alongside Ubuntu Main. This is crucial for companies that must comply with security regulations but aren’t ready to migrate to a newer ROS or Ubuntu distribution yet.

:light_bulb:Canonical would like to know which Noetic packages are essential for you to be included in our ESM.

Right now for each ROS distribution entering its ESM phase, we include:

We follow a structured process, similar to Ubuntu’s Main Inclusion Process, to ensure long-term support for these packages.

This is your chance to let us know which additional packages you need.

You can use this form, it should take less than 5 minutes! Survey Form

Remember that ROS ESM is available with the Ubuntu Pro subscription – and anyone can use Ubuntu Pro for free with up to 5 machines!

3 posts - 3 participants

Read full topic

[WWW] https://discourse.ros.org/t/ros-noetic-is-reaching-end-of-life-in-may-2025-which-additional-packages-do-you-need-in-ros-noetic-esm/42594

ROS Discourse General: Next Client Library WG Meeting: Friday 21st March 8AM PST

Hi,

The next meeting of the Client Library Working Group will be this Friday, 21st March 2025 at 8 AM Pacific Time.

We are currently pushing the rclpy implementation to the finish line.
There’s currently some test issues that are being worked on and that we should discuss if not resolved by Friday.

Besides that, there’s also an interesting discussion about the expected behavior of the rclpp events executor EventsExecutor with an overrunning timer can lead to a burst of timer events · Issue #2771 · ros2/rclcpp · GitHub

Everyone is welcome to join and bring their own topics for discussion, just add them to the agenda!

1 post - 1 participant

Read full topic

[WWW] https://discourse.ros.org/t/next-client-library-wg-meeting-friday-21st-march-8am-pst/42590

ROS Discourse General: Install ros2 humble(deb packages) in ubuntu 20.04 focal

Officially, ubuntu 22.04 is the tier1 platform for ros2 humble.

But nvidia isaac-ros team has migrated the version to ubuntu 20.04(for their jetson devices), which makes ros2 foxy, galactic and humble available in apt-get in one platform. This supports both amd64 and aarch64, only in ubuntu20.04.

Just sharing this rarely known info

# add isaac-ros repo
wget -qO - https://isaac.download.nvidia.com/isaac-ros/repos.key | sudo apt-key add -
echo "deb [arch=$(dpkg --print-architecture)] https://isaac.download.nvidia.com/isaac-ros/ubuntu/main $(lsb_release -cs) main" | sudo tee -a /etc/apt/sources.list

# add ros2 repo
sudo apt update && sudo apt install curl -y
sudo curl -sSL https://raw.githubusercontent.com/ros/rosdistro/master/ros.key -o /usr/share/keyrings/ros-archive-keyring.gpg
echo "deb [arch=$(dpkg --print-architecture) signed-by=/usr/share/keyrings/ros-archive-keyring.gpg] http://packages.ros.org/ros2/ubuntu $(. /etc/os-release && echo $UBUNTU_CODENAME) main" | sudo tee /etc/apt/sources.list.d/ros2.list > /dev/null

# install ros2
sudo apt-get update
sudo apt install ros-humble-desktop
sudo apt install ros-humble-ros-base
sudo apt install ros-dev-tools

# more tests
lsb_release -as
ape-cache search yaml-cpp
ape-cache search isaac-ros
sudo apt install ros-humble-isaac-ros-nitros

5 posts - 2 participants

Read full topic

[WWW] https://discourse.ros.org/t/install-ros2-humble-deb-packages-in-ubuntu-20-04-focal/42589

ROS Discourse General: Amazing Contributor Badge

[ROS Amazing Contributor Badge]

I am honored and grateful to have received the prestigious ‘ROS Amazing Contributor Badge’ an accolade granted to only 20 individuals globally by the ROS community.

The ROS Contributor Badge is categorized into three levels—Contributor, Great Contributor, and Amazing Contributor—based on the number of pull requests submitted to the official ROS GitHub repositories, verified by the ROS Discourse community. Currently, there are 535 Contributors, 126 Great Contributors, and only 20 Amazing Contributors worldwide.

ROS is a robotic software development platform that holds significant meaning for me. Since my first encounter with ROS 1 Diamondback in 2011, I have consistently utilized ROS in research and development projects for over 15 years. My Master’s and Ph.D. studies centered around ROS, and it remains an essential development tool at ROBOTIS, where I am currently employed. Additionally, I have attended ROSCon nine times between 2014 and 2022, including presenting at ROSCon 2016.

Moreover, in collaboration with Open Robotics, I contributed to developing TurtleBot3, a ROS standard platform robot launched officially in 2017. TurtleBot3 is an official Open Robotics brand, and ROBOTIS contributes part of the TurtleBot3 sales revenue back to Open Robotics. Thus, every TurtleBot3 user is significantly contributing to the growth of the ROS ecosystem.

Furthermore, I have authored nine ROS-related books translated into English, Japanese, Chinese, and Korean, including “Robot Programming with ROS 2” (Korean edition). I served as a ROS Technical Steering Committee (TSC) member from 2018 to 2019, helping guide the community’s future, and have organized approximately 60 ROS-related seminars, actively promoting the open-source community.

During the ROS 1 Kinetic era, I maintained 154 out of the 2,051 official ROS packages. Although I had slowed down in recent years, I resumed actively developing public packages again this year, regularly updating ROS 2 packages and planning further contributions beneficial to the community.

This ‘ROS Amazing Contributor Badge’ has given me an opportunity to reflect on my journey and deepened my passion for the ROS community. I look forward to continuing my contributions to help many individuals positively impact the robotics industry through ROS.

Furthermore, we are continuing active development not only on TurtleBot3, OpenManipulator, DYNAMIXEL, and Delivery Service Robot (GAEMI) but also advancing leader, follower, and humanoid robots utilizing manipulators essential for the era of Physical AI. Please stay tuned for future developments.

Thanks, Open Robotics and ROS Community. I :heart: ROS.

https://discourse.ros.org/badges/107/amazing-contributor

Screenshot from 2025-03-18 10-10-11

2 posts - 2 participants

Read full topic

[WWW] https://discourse.ros.org/t/amazing-contributor-badge/42587

ROS Discourse General: ROS MeetUp in Cali, Colombia!

:robot: The ROS MeetUp is coming to Cali, Colombia! :robot:

Enjoy an afternoon of inspiring talks about ROS / ROS 2, connect with developers, researchers, students, and robotics enthusiasts, and take the opportunity to exchange ideas.

:spiral_calendar: When? May 24, 2025, from 3:00 to 7:00 pm.

:round_pushpin: Where? Universidad Santiago de Cali, Pedro Elías Serrano Auditorium.

:bookmark_tabs: How to participate? Register for the event as an attendee here.

:pushpin: Want to share your experience? Apply to speak here. (Until May 4th)

Come share, learn, and be part of this experience!
:smiley:

1 post - 1 participant

Read full topic

[WWW] https://discourse.ros.org/t/ros-meetup-in-cali-colombia/42582

ROS Discourse General: Cloud Robotics WG Meeting 2025-03-24 | Group Progress Review

Please come and join us for this coming meeting at 2025-03-24T17:00:00Z UTC→2025-03-24T18:00:00Z UTC, where we will have a general catch-up, review our progress as a group, and discuss a new option for some meetings going forward: determining a meeting topic in advance and spending the meeting discussing that topic.

Last meeting, the group had a general catch-up and spent the session discussing their preferences and issues with the most popular deployment methods. We agreed that distribution via Docker containers was our preferred method, but that it still had issues, and we also discussed a possible project to remotely disable particular functions of a robot. If you want to watch for yourself, 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

[WWW] https://discourse.ros.org/t/cloud-robotics-wg-meeting-2025-03-24-group-progress-review/42574

ROS Discourse General: Running ROS Noetic in Docker: A Practical Guide for Simulation and Teleoperation

Intro

The Robot Operating System (ROS) is an essential platform for developing robotic applications. However, getting ROS up and running on various systems can be challenging due to issues like dependency conflicts, varying operating system versions, and hardware inconsistencies.

One way to simplify this is by using Docker, which allows you to containerize your ROS environment. This method provides a portable, isolated environment that can be shared across different machines without affecting your host system.

In this guide, we will walk through the process of setting up ROS Noetic inside a Docker container and using it to:

  1. Run ROS Noetic in Docker.
  2. Simulate a mobile robot using Gazebo.
  3. Control the robot with teleop_twist_keyboard.
  4. Customize launch files for different simulation environments.

Benefits of Using Docker for ROS:

For more about Docker, visit the official Docker documentation.

Setting Up ROS Noetic in Docker

To begin, you need Docker installed on your machine. If you haven’t installed Docker yet, follow the official guide to install Docker.

Run a ROS Noetic Docker Container in your Windows Terminal

Start by pulling the official ROS Noetic image and running it in an interactive terminal:

docker run -it --name ros_container --net=host --privileged osrf/ros:noetic-desktop-full bash

Explanation of Parameters:

Once you execute this command, you’ll be inside the Docker container, where ROS Noetic is fully set up and ready to use.

Creating a ROS Workspace and Building Packages

A ROS workspace is essential for organizing your projects and packages. Here’s how you can set up a basic workspace:

Create and Build a Catkin Workspace

mkdir -p ~/Workspaces/smb_ws/src
cd ~/Workspaces/smb_ws
catkin_make
source devel/setup.bash

Running a Robot Simulation in Gazebo

To test ROS in a real-world scenario, we will simulate a Small Mobile Robot (SMB) in Gazebo, a popular robot simulation tool integrated with ROS.

Clone the SMB Simulation Repository

cd ~/Workspaces/smb_ws/src
git clone https://github.com/ethz-asl/smb_common.git

Build the Package

cd ~/Workspaces/smb_ws
catkin_make
source devel/setup.bash

Launch the Simulation

roslaunch smb_gazebo smb_gazebo.launch

Controlling the Robot with Teleoperation

To manually control the simulated robot, we’ll use the teleop_twist_keyboard package, which allows control via keyboard input.

Clone and Build the Teleoperation Package

cd ~/Workspaces/smb_ws/src
git clone https://github.com/ros-teleop/teleop_twist_keyboard.git
cd ~/Workspaces/smb_ws
catkin_make
source devel/setup.bash

Run the Teleoperation Node

rosrun teleop_twist_keyboard teleop_twist_keyboard.py

Use the W/A/S/D keys to move the robot forward, backward, left, and right, and the Q/E keys to rotate it.

Verifying and Debugging ROS Nodes

As with any ROS application, debugging is an essential part of development.
Here are some common commands to verify the status of your ROS nodes and topics.

Check Running ROS Nodes

rosnode list

Check Available ROS Topics

rostopic list

Publish Velocity Commands Manually

To control the robot directly via command line, you can publish velocity command

rostopic pub -r 10 /cmd_vel geometry_msgs/Twist '{linear: {x: 0.5, y: 0.0, z: 0.0}, angular: {x: 0.0, y: 0.0, z: 0.5}}'

This command will move the robot forward while rotating it at a rate of 0.5 radians per second.

Conclusion

In this guide, we’ve set up ROS Noetic in Docker and demonstrated how to simulate a robot in Gazebo, control it manually.

Further Resources

If you have any feedback or questions, feel free to reach out through the ROS Discourse.

Hope this helps :slightly_smiling_face:

5 posts - 4 participants

Read full topic

[WWW] https://discourse.ros.org/t/running-ros-noetic-in-docker-a-practical-guide-for-simulation-and-teleoperation/42572

ROS Discourse General: Participate in GSoC 2025 with JdeRobot open-source organization

Hi folks!,

JdeRobot org is again participating in Google Summer of Code 2025. If you are a student or otherwise eligible to the GSoC program, we are seeking Robotics enthusiasts!. Just submit your application for one of our proposed projects, all of them using ROS2 , and typically Gazebo or Carla robotics simulators (this year even O3DE simulator!). For GSoC-2025 JdeRobot is mentoring projects about:

For more details about the projects and application submission, visit the JdeRobot GSoC 2025 page and our candidate selection process!

Take a look at some JdeRobot’s previous GSoC success stories such as those of Prajyot, Óscar or Pankaj.

1 post - 1 participant

Read full topic

[WWW] https://discourse.ros.org/t/participate-in-gsoc-2025-with-jderobot-open-source-organization/42571

2025-03-29 13:28