Planet ROS

ROS 2 TSC Meeting Minutes 2023-11-16

2023-11-20T23:28:00Z

ROS 2 TSC Meeting Minutes 2023-11-16

ROS 2 TSC Contribution Report 2023-11-16.pdf (111.8 KB)

+
Attendees
+
- TSC Members +
  - Microsoft / Lou Amadio
  - eProsima / Jaime Martin Losa
  - Intrinsic.ai / Chris Lalancette
  - Intrinsic.ai / Katherine Scott
  - Canonical / Mirko Ferrati
  - OSRF / Geoff Biggs
  - Community / Francisco Martin Rico
  - Apex.AI / Michael Orlov
  - Bosch / Christian Henkel
  - Picknik / Henning Kayser
  - Devcom / Jerry Towler
  - iRobot / Alberto Soragna
  - iRobot / Brian Wilcox
  - Foxglove / Adrian Macneil
  - Wind River / Andrei Kholodnyi
  - Amazon / Aaron Blasdel
  - Toyota Research Institute / Ian McMahon
  - Sony / Tomoya Fujita
  +
- Observers +
  - Community / David Lu!! (observer until December)
  - Community / Steve Macenski (observer until December)
  - Locus Robotics / Bence Magyar
  +
- Absent (Please move to TSC Members Line): +
  - Apex.AI / Lyle Johnson
  - Intel / Harold Lang
  - Robotis / Will Son (excused)
  - ROS Industrial / Matt Robinson
  - Zettascale / Angelo Corsaro
  +
+
+
Preliminaries
+
- You should only have comment access to this document.
- [Kat ][1 min] Please remember to fill out your contribution report at the bottom of this document prior to the meeting.
+
+
Old business
+
- Welcome new TSC members. Steve and David +
  - Note: official start is in December but I’ve invited them to observe.
  - Full results can be found here.
  - 2023 ROS 2 Technical Steering Committee Community Representative Election Results
  +
- [20 min][Soragna] NEW TSC Production Working Group Proposal +
  - Charter on ROS Discourse
  - VOTE: FOR___14 / AGAINST 0 / TOTAL 18 / ABSTAIN 4
  - TODO: Add working group to Discourse and Docs
  +
+
+
New business
+
- [5 min][Kat] Do we want to change the next meeting date? +
  - Next meeting is 12/21/2023
  - Many people have Friday 12/22 off for the holiday.
  - Alternative date would be 12/14/2023 +
    - No objections. TODO: Move meeting.
    +
  +
- [25 min][Steve Macenski] – REP-2003 Sensor Data and Map QoS Settings +
  - Discuss this meeting, if no changes requested vote next meeting
  - REP 2003: Sensor Data and Map QoS Settings by SteveMacenski · Pull Request #212 · ros-infrastructure/rep · GitHub
  - TODO: Setup vote and send out e-mail
  +
+
+
Recurring business
+
- Next ROS 2 distro release +
  - Continued work on rmw_zenoh +
    - Working towards getting the graph cache actually working
    - Combining code with the old https://github.com/atolabs/rmw_zenoh +
      - Whole thing moved to GitHub - ros2/rmw_zenoh: RMW for ROS 2 using Zenoh as the middleware, development streams merged together
      +
    +
  - Update to REP-2000 for Jazzy happening soon +
    - Happened this week
    +
  - Switch to Ubuntu 24.04 +
    - Very early docker images now available
    - Will start working on various transitions in the next few weeks
    +
  +
- Working groups [<=5 mins each] +
  - [Bence] Control +
    - Finally branched for Iron +
      - Rolling getting breaking changes now
      - Controllers get URDF and CM update rate in init
      - diff_drive_controller doesn’t support non-stamped Twist anymore
      - Deprecations (warnings in place in Humble and Iron)
      +
    - Working on better nodeoptions configurability
    - (all versions) controller spawner accepts list of controllers and can spawn in order or at once
    - Discussions on Python support for both controllers and hardware components
    - More discussions to support async and distributed setups
    - Next WG meeting: mini-roadmapping session for next year
    +
  - [Martin Losa] Embedded +
    - No EWG meeting in october due ROSCON
    - Working in the Agenda for the November EWG (Nov 28th):
    - Pablo Garrido from eProsima will present a demo running Safe DDS across all three cores of the AMD KR260 platform – Cortex A53, Cortex R5, and MicroBlaze FPGA-softcore, interoperating with ROS2 +
      - You can see a video of the demo here
      +
    +
  - [Kayser] Manipulation +
    - Added support for node logging in moveit_ros and reverting it now since some ROS test went flaky
    - Discussing support for tool changing, requires dynamic robot model and possibly major API refactoring +
      - Early work has been implemented as MoveIt capability
      +
    - Refactoring MoveIt’s planner adapter chain +
      - intuitive call order
      - separate types for pre- and post-adapters
      - Better support for validation checks, step-wise result introspection and returning errors
      +
    +
  - [Woodall] Middleware +
    - No update (trying to schedule next meeting)
    +
  - [Macenski] Navigation +
    - Requested change to geometry_msgs/Polygon +
      - Adding unique identifer field to Polygon/Polygon Stamped · Issue #230 · ros2/common_interfaces · GitHub
      - Reviews please!
      +
    - Major rework on the MPPI critics to improve performance and behavior quality (Open Navigation)
    - Various threading violation fixes (Peanut, Open Navigation)
    - Collison Monitor upgrades: +
      - Watchdog for sensors to stop robot (Dexory)
      - Adding Polygon Source-type (Pixel Robotics)
      +
    - Starting collaboration with ROS 2 Control, Gazebo on TwistStamped migration from Twist for commanded velocities
    - New Coverage Navigator, Task Server! +
      - GitHub - open-navigation/opennav_coverage: Nav2 Compatible Complete Cover Task Server, Navigator, and BT Utils
      +
    +
  - [Andrei] Real-Time +
    - Real-time workshop at ROSCON +
      - ROScon 2023 real-time workshop
      - https://docs.google.com/presentation/d/1yHaHiukJe-87RhiN8WIkncY23HxFkJynCQ8j3dIFx_w/edit#slide=id.p
      - Different use cases for the real-time
      - Many participants want to understand the basics
      +
    - Raspberry Pi 5 image
    +
  - [Andrei] meta-ros (Open Embedded) +
    - Updated to the support humble and iron with the latest Yocto releases, GitHub - ros/meta-ros: OpenEmbedded Layers for ROS 1 and ROS 2
    - To update REP2000
    +
  - [Mirko] Security +
    - Last Security Working Group meeting happened on Nov. 14. The following points were discussed:
    - Progress on RustDDS, a memory-safe DDS implementation. Plan to have a presentation and discussion at a later meeting.
    - A vulnerability was reported to the FastDDS Github repo recently and shared on the group’s Matrix channel. We discussed the issue and supporting the reporter to get feedback from the project maintainers.
    +
  - [Orlov] Tooling +
    - Use enum values for offered_qos_profiles in code and string names in serialized metadata (rosbag2#1476)
    - Made progress on the following PRs: +
      +
    +
  +
+

1 post - 1 participant

Read full topic

Upcoming API break in urdfdom

2023-11-20T18:51:06Z

Hi all,

Please bear with me on a long post about urdfdom.

For those who don’t know, GitHub - ros/urdfdom: URDF parser houses the source code that both ROS 1 and ROS 2 use to parse and interact with URDF files.

Since 2012, the code there has had a dependency on TinyXML (the original version). Further, that dependency is exposed via the public API, in the form of a few functions that either consume or produce a TinyXML object.

Unfortunately, TinyXML itself has been deprecated for a long time. So we want to move urdfdom exclusively to TinyXML2, but we have been concerned that doing that would break current users of the urdfdom API.

One thing we could do here would be to have a transition period where we introduced TinyXML2 APIs alongside the existing TinyXML ones. I suggested this earlier this year, and SMillerDev took up the challenge. Unfortunately, the resulting PR is large and we would have to maintain a lot more code.

Instead, we recently took a look at the uses of urdfdom across all packages in Rolling, and we found that there are zero callers of the affected APIs there. That doesn’t mean there are zero callers in the world; we can’t see things that aren’t released publicly. However, the fact that there are no callers in Rolling gives us confidence that there are few callers of these APIs in the world.

Therefore, we are very seriously considering closing the PR adding in TinyXML2 APIs and merging this PR that replaces TinyXML with TinyXML2. That would break the API, but it would be much simpler going forward and we don’t expect too much fallout from it.

This post acts as both a notice that we are going to do this, and as a question: do you depend on the TinyXML APIs from urdfdom? If you do, please respond and let us know how you are using them. If we don’t hear back from users that these APIs are important to them, then we will likely break the API and bump the major number of the urdfdom library.

Please also respond if you have any other questions or concerns about this change. Thank you.

2 posts - 2 participants

Read full topic

Important Announcement, Patch Release 3 and New Packages for Iron Irwini 2023-11-20

2023-11-20T16:37:22Z

We’re happy to announce a new Iron release

The latest sync brings 11 new packages and 118 updates to ROS 2 Iron Irwini. This sync was tagged as iron/2023-11-20 .

We’ve recently made an important update to ROS 2: loaned messages are
+now disabled by default. If you don’t know what loaned messages are,
+then you can skip the following paragraph. If you are using loaned messages,
+continue reading.
+We disabled the loaned messages by default to address safety
+concerns, as there were instances of shared pointers being unsafely
+reused across multiple callbacks. While this adjustment temporarily
+limits loaned message capabilities in callbacks, it’s a necessary step to
+ensure the reliability and safety of the system. See Disable the loaned messages inside the executor. by clalancette · Pull Request #2335 · ros2/rclcpp · GitHub for more details.
+If you understand the risks of using loaned messages and want to enable them,
+you can set ROS_DISABLE_LOANED_MESSAGE=0 in the environment before launching your nodes.
+Rest assured, we’re exploring options to safely reintroduce this feature in the future. Your
+understanding and support in this matter are greatly appreciated.

Package Updates for iron

Added Packages [11]:

ros-iron-event-camera-codecs: 1.2.2-1

ros-iron-event-camera-codecs-dbgsym: 1.2.2-1

ros-iron-event-camera-msgs: 1.2.5-1

ros-iron-event-camera-msgs-dbgsym: 1.2.5-1

ros-iron-leo: 2.0.0-1
ros-iron-leo-description: 2.0.0-1
ros-iron-leo-desktop: 2.0.0-1
ros-iron-leo-msgs: 2.0.0-1
ros-iron-leo-msgs-dbgsym: 2.0.0-1
ros-iron-leo-teleop: 2.0.0-1
ros-iron-leo-viz: 2.0.0-1

Updated Packages [118]:

ros-iron-controller-interface: 3.20.0-1 → 3.21.0-1

ros-iron-controller-interface-dbgsym: 3.20.0-1 → 3.21.0-1

ros-iron-controller-manager: 3.20.0-1 → 3.21.0-1

ros-iron-controller-manager-dbgsym: 3.20.0-1 → 3.21.0-1

ros-iron-controller-manager-msgs: 3.20.0-1 → 3.21.0-1
ros-iron-controller-manager-msgs-dbgsym: 3.20.0-1 → 3.21.0-1
ros-iron-fastrtps-cmake-module: 3.0.1-1 → 3.0.2-1
ros-iron-hardware-interface: 3.20.0-1 → 3.21.0-1
ros-iron-hardware-interface-dbgsym: 3.20.0-1 → 3.21.0-1
ros-iron-joint-limits: 3.20.0-1 → 3.21.0-1
ros-iron-libstatistics-collector: 1.5.1-2 → 1.5.2-1
ros-iron-libstatistics-collector-dbgsym: 1.5.1-2 → 1.5.2-1
ros-iron-mcap-vendor: 0.22.4-1 → 0.22.5-1
ros-iron-mcap-vendor-dbgsym: 0.22.4-1 → 0.22.5-1
ros-iron-rcl: 6.0.3-1 → 6.0.4-1
ros-iron-rcl-action: 6.0.3-1 → 6.0.4-1
ros-iron-rcl-action-dbgsym: 6.0.3-1 → 6.0.4-1
ros-iron-rcl-dbgsym: 6.0.3-1 → 6.0.4-1
ros-iron-rcl-lifecycle: 6.0.3-1 → 6.0.4-1
ros-iron-rcl-lifecycle-dbgsym: 6.0.3-1 → 6.0.4-1
ros-iron-rcl-yaml-param-parser: 6.0.3-1 → 6.0.4-1
ros-iron-rcl-yaml-param-parser-dbgsym: 6.0.3-1 → 6.0.4-1
ros-iron-rclcpp: 21.0.3-1 → 21.0.4-1
ros-iron-rclcpp-action: 21.0.3-1 → 21.0.4-1
ros-iron-rclcpp-action-dbgsym: 21.0.3-1 → 21.0.4-1
ros-iron-rclcpp-components: 21.0.3-1 → 21.0.4-1
ros-iron-rclcpp-components-dbgsym: 21.0.3-1 → 21.0.4-1
ros-iron-rclcpp-dbgsym: 21.0.3-1 → 21.0.4-1
ros-iron-rclcpp-lifecycle: 21.0.3-1 → 21.0.4-1
ros-iron-rclcpp-lifecycle-dbgsym: 21.0.3-1 → 21.0.4-1
ros-iron-rclpy: 4.1.3-1 → 4.1.4-1
ros-iron-rcpputils: 2.6.1-3 → 2.6.2-1
ros-iron-rcpputils-dbgsym: 2.6.1-3 → 2.6.2-1
ros-iron-rcutils: 6.2.1-2 → 6.2.2-2
ros-iron-rcutils-dbgsym: 6.2.1-2 → 6.2.2-2
ros-iron-rmw-fastrtps-cpp: 7.1.1-2 → 7.1.2-1
ros-iron-rmw-fastrtps-cpp-dbgsym: 7.1.1-2 → 7.1.2-1
ros-iron-rmw-fastrtps-dynamic-cpp: 7.1.1-2 → 7.1.2-1
ros-iron-rmw-fastrtps-dynamic-cpp-dbgsym: 7.1.1-2 → 7.1.2-1
ros-iron-rmw-fastrtps-shared-cpp: 7.1.1-2 → 7.1.2-1
ros-iron-rmw-fastrtps-shared-cpp-dbgsym: 7.1.1-2 → 7.1.2-1
ros-iron-ros2-control: 3.20.0-1 → 3.21.0-1
ros-iron-ros2-control-test-assets: 3.20.0-1 → 3.21.0-1
ros-iron-ros2action: 0.25.3-1 → 0.25.4-1
ros-iron-ros2bag: 0.22.4-1 → 0.22.5-1
ros-iron-ros2cli: 0.25.3-1 → 0.25.4-1
ros-iron-ros2cli-test-interfaces: 0.25.3-1 → 0.25.4-1
ros-iron-ros2cli-test-interfaces-dbgsym: 0.25.3-1 → 0.25.4-1
ros-iron-ros2component: 0.25.3-1 → 0.25.4-1
ros-iron-ros2controlcli: 3.20.0-1 → 3.21.0-1
ros-iron-ros2doctor: 0.25.3-1 → 0.25.4-1
ros-iron-ros2interface: 0.25.3-1 → 0.25.4-1
ros-iron-ros2lifecycle: 0.25.3-1 → 0.25.4-1
ros-iron-ros2lifecycle-test-fixtures: 0.25.3-1 → 0.25.4-1
ros-iron-ros2lifecycle-test-fixtures-dbgsym: 0.25.3-1 → 0.25.4-1
ros-iron-ros2multicast: 0.25.3-1 → 0.25.4-1
ros-iron-ros2node: 0.25.3-1 → 0.25.4-1
ros-iron-ros2param: 0.25.3-1 → 0.25.4-1
ros-iron-ros2pkg: 0.25.3-1 → 0.25.4-1
ros-iron-ros2run: 0.25.3-1 → 0.25.4-1
ros-iron-ros2service: 0.25.3-1 → 0.25.4-1
ros-iron-ros2topic: 0.25.3-1 → 0.25.4-1
ros-iron-rosbag2: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-compression: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-compression-dbgsym: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-compression-zstd: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-compression-zstd-dbgsym: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-cpp: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-cpp-dbgsym: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-examples-cpp: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-examples-cpp-dbgsym: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-examples-py: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-interfaces: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-interfaces-dbgsym: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-performance-benchmarking: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-performance-benchmarking-msgs: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-py: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-storage: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-storage-dbgsym: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-storage-default-plugins: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-storage-mcap: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-storage-mcap-dbgsym: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-storage-sqlite3: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-storage-sqlite3-dbgsym: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-test-common: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-test-msgdefs: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-test-msgdefs-dbgsym: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-tests: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-transport: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-transport-dbgsym: 0.22.4-1 → 0.22.5-1
ros-iron-rosidl-dynamic-typesupport: 0.0.4-1 → 0.0.5-1
ros-iron-rosidl-dynamic-typesupport-dbgsym: 0.0.4-1 → 0.0.5-1
ros-iron-rosidl-typesupport-fastrtps-c: 3.0.1-1 → 3.0.2-1
ros-iron-rosidl-typesupport-fastrtps-c-dbgsym: 3.0.1-1 → 3.0.2-1
ros-iron-rosidl-typesupport-fastrtps-cpp: 3.0.1-1 → 3.0.2-1
ros-iron-rosidl-typesupport-fastrtps-cpp-dbgsym: 3.0.1-1 → 3.0.2-1
ros-iron-rqt-controller-manager: 3.20.0-1 → 3.21.0-1
ros-iron-rqt-reconfigure: 1.3.3-2 → 1.3.4-1
ros-iron-rviz-assimp-vendor: 12.4.4-1 → 12.4.5-1
ros-iron-rviz-common: 12.4.4-1 → 12.4.5-1
ros-iron-rviz-common-dbgsym: 12.4.4-1 → 12.4.5-1
ros-iron-rviz-default-plugins: 12.4.4-1 → 12.4.5-1
ros-iron-rviz-default-plugins-dbgsym: 12.4.4-1 → 12.4.5-1
ros-iron-rviz-ogre-vendor: 12.4.4-1 → 12.4.5-1
ros-iron-rviz-ogre-vendor-dbgsym: 12.4.4-1 → 12.4.5-1
ros-iron-rviz-rendering: 12.4.4-1 → 12.4.5-1
ros-iron-rviz-rendering-dbgsym: 12.4.4-1 → 12.4.5-1
ros-iron-rviz-rendering-tests: 12.4.4-1 → 12.4.5-1
ros-iron-rviz-visual-testing-framework: 12.4.4-1 → 12.4.5-1
ros-iron-rviz2: 12.4.4-1 → 12.4.5-1
ros-iron-rviz2-dbgsym: 12.4.4-1 → 12.4.5-1
ros-iron-shared-queues-vendor: 0.22.4-1 → 0.22.5-1
ros-iron-sqlite3-vendor: 0.22.4-1 → 0.22.5-1
ros-iron-transmission-interface: 3.20.0-1 → 3.21.0-1
ros-iron-transmission-interface-dbgsym: 3.20.0-1 → 3.21.0-1
ros-iron-twist-mux: 4.2.0-1 → 4.3.0-1
ros-iron-twist-mux-dbgsym: 4.2.0-1 → 4.3.0-1
ros-iron-zstd-vendor: 0.22.4-1 → 0.22.5-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:

+
Note: The list of contributors is incomplete as there may be an issue with the tool used to generate this report.
+

Alejandro Hernandez Cordero
Audrow Nash
Bence Magyar
Bernd Pfrommer
Brandon Ong
Dharini Dutia
Fictionlab
Foxglove
Geoffrey Biggs
Ivan Paunovic
Michael Orlov
ROS Tooling Working Group
Shane Loretz
geoff

1 post - 1 participant

Read full topic

Again... Snapshot repo GPG key expired

2023-11-20T09:21:04Z

Since yesterday, there is a problem running Melodic Industrial CI:

$ sudo apt-get update -qq
+  W: GPG error: http://snapshots.ros.org/melodic/final/ubuntu bionic InRelease: The following signatures were invalid: EXPKEYSIG AD19BAB3CBF125EA ROS Snapshot builder 
+  E: The repository 'http://snapshots.ros.org/melodic/final/ubuntu bionic InRelease' is not signed.
+

I know Melodic is EOL, but still, it should be usable from the snapshot repo, shouldnâ€™t it?

There is already another report on RSE, but I think this is a better place to discuss such problem.

8 posts - 6 participants

Read full topic

Simple_launch approaching event handling

2023-11-18T20:27:42Z

Hi,

A few posts on discourse and stackexchange have already highlighted the difficulty of writing Python launch files for ROS 2.

In particular, the syntax may be a bit verbose and the arguments somehow hard to handle as they are not raw Python types.

The simple_launch package wraps the standard launch syntax inside a much lighter approach. In particular, groups (by namespace or conditions) are defined through the with Python syntax and thus the indentation clearly expresses the current level of namespace or condition.

The current release allows easy handling of:

namespaces
conditions
finding a file inside a package (thanks os.walk)
container and composable nodes
spawning a robot_state_publisher from a xacro file with arguments, even if all of those come from launch arguments
uploading models to Gazebo
bridging topics with Gazebo (ros_gz_bridge wrapper)
setting use_sim_time for all nodes in the launch file
using the OpaqueFunction idiom (my favorite) without seeing perform or context everywhere, in case you really need raw Python types

The package is available through apt and the next release will be focusing on event-based groups. This is already available in the repository but edge cases appear when combining events and namespaces.
+The next release will make it clear what the chosen approach is.

The goal is not to be able to re-do everything in a simpler way, but to be able to do very easily what people do very often. Feel free to comment, issue or pull request.
+Next releases will also be focusing on documentation and type hints that are still a bit lacking due to numerous combinations of Substitutions and raw Python types.

6 posts - 4 participants

Read full topic

ROS News for the Week of November 12th, 2023

2023-11-17T21:50:59Z

ROS News for the Week of November 12th, 2023

What's New and Upcoming in Open Source Robotics at ROSCon '23

Check out this fantastic PX4 and ROSCon recap video from our friends at PX4

+
+

+Our next Gazebo Community Meeting will include a report from the IIT Madras Aritra maritime robotics team.

+
+

+Check out this new ROS Noetic package that implements a Segment Anything Model as a ROS Service.

+
+

+All good things must come to an end. Audrow has stepped down from Sense, Think, Act.

+
+

+Our friends at Tangram have a new Kickstarter campaign for their HiFi Depth Sensor. From what we’re told the sensor has fantastic accuracy and resolution, auto-calibrates, and supports ROS 2 out of the box.

+
+

Events

News

ROS

6 posts - 3 participants

Read full topic

ROS Deployment Meeting (#1?)

2023-11-16T19:18:23Z

Hi,

for those who are interested in how to manage and deploy the ROS application?, letâ€™s have a follow-up meeting as we promised at ROSCon 2023 BoF

revised from Automatic Deployment of ROS2 Based System to remote devices: Dual Copy or Containers?, besides we had 44 people registered to BoF: Deployment of ROS 2 to remote devices at ROSCon 2023.

with that, i think there are many interests about how to deploy and manage robot application. Please feel free to join the meeting

Date / Place

2023-12-04T17:00:00Z UTC

+ + +

(*) I am not able to do recording at this time.

Agenda

Really appreciate @ciandonovan , he is willing to share the experience and take the effort for ROS community.

ROSCon 2023 ROS with Kubernetes/KubeEdge Talk Follow-Up and QA/Discussion (@tomoyafujita ) 15-20mins +
- GitHub - fujitatomoya/ros_k8s: Kuberenetes / ROS&ROS2 Cluster Samples Issues / Explanation
+
ROS deployment control with podman and systemd. (@ciandonovan ) 25mins including QA/Discussion
Open Discussion (should we have regular meeting? other topics? problem sharing?) 5mins

How to join?

No registration is required, you can just jump in the meeting

Or if you do not want to miss, DM @tomoyafujita / tomoya.fujita825@gmail.com to get the meeting invitation.

Reference

+ + +

thanks,

14 posts - 8 participants

Read full topic

New Packages for Noetic 2023-11-15

2023-11-16T00:47:59Z

We’re happy to announce 5 new packages and 51 updates are now available in ROS Noetic. This sync was tagged as noetic/2023-11-15.

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

Package Updates for ROS Noetic

Added Packages [5]:

ros-noetic-clearpath-onav-api-examples: 0.0.3-1

ros-noetic-clearpath-onav-api-examples-lib: 0.0.3-1

ros-noetic-clearpath-onav-examples: 0.0.3-1

ros-noetic-pr2eus-moveit: 0.3.15-3
ros-noetic-sick-scan-xd: 3.0.3-1

Updated Packages [51]:

ros-noetic-clearpath-configuration-msgs: 0.9.4-1 → 0.9.5-1

ros-noetic-clearpath-control-msgs: 0.9.4-1 → 0.9.5-1

ros-noetic-clearpath-dock-msgs: 0.9.4-1 → 0.9.5-1

ros-noetic-clearpath-localization-msgs: 0.9.4-1 → 0.9.5-1

ros-noetic-clearpath-mission-manager-msgs: 0.9.4-1 → 0.9.5-1

ros-noetic-clearpath-mission-scheduler-msgs: 0.9.4-1 → 0.9.5-1

ros-noetic-clearpath-msgs: 0.9.4-1 → 0.9.5-1

ros-noetic-clearpath-navigation-msgs: 0.9.4-1 → 0.9.5-1

ros-noetic-clearpath-platform-msgs: 0.9.4-1 → 0.9.5-1

ros-noetic-clearpath-safety-msgs: 0.9.4-1 → 0.9.5-1

ros-noetic-combined-robot-hw: 0.19.6-1 → 0.20.0-1
ros-noetic-combined-robot-hw-tests: 0.19.6-1 → 0.20.0-1
ros-noetic-controller-interface: 0.19.6-1 → 0.20.0-1
ros-noetic-controller-manager: 0.19.6-1 → 0.20.0-1
ros-noetic-controller-manager-msgs: 0.19.6-1 → 0.20.0-1
ros-noetic-controller-manager-tests: 0.19.6-1 → 0.20.0-1
ros-noetic-cpr-onav-description: 0.1.9-1 → 0.1.10-1
ros-noetic-cras-cpp-common: 2.3.3-1 → 2.3.4-1
ros-noetic-cras-docs-common: 2.3.3-1 → 2.3.4-1
ros-noetic-cras-py-common: 2.3.3-1 → 2.3.4-1
ros-noetic-cras-topic-tools: 2.3.3-1 → 2.3.4-1
ros-noetic-foxglove-bridge: 0.7.2-1 → 0.7.3-1
ros-noetic-hardware-interface: 0.19.6-1 → 0.20.0-1
ros-noetic-image-transport-codecs: 2.3.3-1 → 2.3.4-1
ros-noetic-joint-limits-interface: 0.19.6-1 → 0.20.0-1
ros-noetic-jsk-pr2eus: 0.3.15-1 → 0.3.15-3
ros-noetic-leo: 2.2.0-1 → 2.3.0-1
ros-noetic-leo-bringup: 2.3.0-1 → 2.4.0-1
ros-noetic-leo-description: 2.2.0-1 → 2.3.0-1
ros-noetic-leo-desktop: 0.2.3-1 → 0.3.0-1
ros-noetic-leo-fw: 2.3.0-1 → 2.4.0-1
ros-noetic-leo-msgs: 2.2.0-1 → 2.3.0-1
ros-noetic-leo-robot: 2.3.0-1 → 2.4.0-1
ros-noetic-leo-teleop: 2.2.0-1 → 2.3.0-1
ros-noetic-leo-viz: 0.2.3-1 → 0.3.0-1
ros-noetic-marti-can-msgs: 0.12.1-1 → 0.12.2-1
ros-noetic-marti-common-msgs: 0.12.1-1 → 0.12.2-1
ros-noetic-marti-dbw-msgs: 0.12.1-1 → 0.12.2-1
ros-noetic-marti-introspection-msgs: 0.12.1-1 → 0.12.2-1
ros-noetic-marti-nav-msgs: 0.12.1-1 → 0.12.2-1
ros-noetic-marti-perception-msgs: 0.12.1-1 → 0.12.2-1
ros-noetic-marti-sensor-msgs: 0.12.1-1 → 0.12.2-1
ros-noetic-marti-status-msgs: 0.12.1-1 → 0.12.2-1
ros-noetic-marti-visualization-msgs: 0.12.1-1 → 0.12.2-1
ros-noetic-mrpt2: 2.11.1-1 → 2.11.2-1
ros-noetic-openni2-camera: 1.6.0-1 → 1.6.1-1
ros-noetic-openni2-launch: 1.6.0-1 → 1.6.1-1
ros-noetic-pr2eus: 0.3.15-1 → 0.3.15-3
ros-noetic-ros-control: 0.19.6-1 → 0.20.0-1
ros-noetic-rqt-controller-manager: 0.19.6-1 → 0.20.0-1
ros-noetic-transmission-interface: 0.19.6-1 → 0.20.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:

Bence Magyar
Chris Iverach-Brereton
Fictionlab
Isaac I. Y. Saito
Jason Higgins
John Hurliman
Jose Mastrangelo
Jose-Luis Blanco-Claraco
José Mastrangelo
Kei Okada
Martin Pecka
Michael Ferguson
Roni Kreinin
Southwest Research Institute
YoheiKakiuchi
rostest

1 post - 1 participant

Read full topic

Proposal for ROS 2 Production Working Group

2023-11-15T18:05:14Z

In the October 2023 Technical Steering Committee meeting, representatives from iRobot presented on the topic of “Scaling ROS 2 for Production”, where issues regarding the current state of ROS 2 in how it manages developer cost, product quality, stability, and performance were addressed, and new ideas were proposed. The general consensus from the meeting feedback was that a working group could be formed to dedicate planning and resources towards implementing solutions to this agenda. Thus, here is the proposal:

Context: ROS 2 is a great software framework that enables efficient research, quick prototyping, and access to a community of open-source robotics projects. However, the challenge remains for issues concerning scaling ROS 2 usage for a production robot. In a production-oriented environment, quality control is a necessary requirement, therefore, any regression in the build, or stability of code on the robot, or in its performance can have major consequences. In addition, if an underlying change in the ROS 2 code significantly affects the overall build time or developer cost for integrating into robotics products, then it may impact a developer or company’s bottom line. These are concerns that make ROS 2 limited and difficult to incorporate in larger-scale production use cases.

Mission Statement: Affirm ROS 2’s commitment as an infrastructure for scalable deployment and production of robotics products by prioritizing and coordinating efforts to address concerns of Developer Cost, Stability, Quality Control, and Performance.

Key Topics to Cover:
+• ROS 2 Build Farm & Statistics
+• CICD & Testing Coverage
+• Release schedule requirements
+• Performance Evaluation & Regressions
+• RMW Relationship
+• Architecture Improvements
+• Documentation

Goals
+• Early-detection / resolution of regressions in build time, performance, and stability
+• Support for physical testing as part of CI before release
+• Improved capacity for developer tuning / configuration
+• Stricter requirements for RMW tier support to address testing and stability
+• Accessible documentation for advanced or optimized production use cases

Group expectations:
+• Bi-weekly or monthly meetings to discuss solutions to address above agenda
+• Define tasks and github issues related to implementing solutions
+• Recruit and assign owners and resources for completing tasks
+• Align agenda and task(s) timeline with ROS 2 release schedule

Call for Participation:
+If you are interested in updates or participating in working group meetings, please fill out the following google form survey:

+ +

If you have any feedback on the content or direction of this proposed working group, please feel free to write a comment on this post or in the above survey. We will send a follow-up notification to organize the first meeting launch date and time.

4 posts - 2 participants

Read full topic

Audrow Nash to step down from hosting the Sense, Think, Act podcast

2023-11-14T17:26:08Z

Hi Everyone,

We have some bittersweet news. @audrow is moving on to the next phase of his podcasting career and will be stepping down as the host of the OSRF’s Sense, Think, Act podcast. Under Audrow’s masterful leadership and hosting, Sense, Think, Act has become one of the premier places to hear interviews with leaders in the world of robotics.

The OSRF is sincerely grateful to Audrow for giving Sense, Think, Act a powerful start through his hard work and dedication to interviewing a stellar range of individuals in the wide field of robotics, including Dave Coleman, Ryan Garipy, Steve Macenski, Brett Aldrich, Melonee Wise, and Matt Robinson. Topics discussed have included robot navigation, robot ethics, STEM education, manufacturing, scanning warehouse inventory, and so much more. Audrow’s interviews have been informative and thought-provoking, and he has helped to make the field of robotics more accessible to a broader audience.

Audrow’s new podcast, The Audrow Nash Podcast, is available here, and here, and we encourage you all to check it out and subscribe! It’s sure to be a fantastic and educational show, and we wish him all the best in his future endeavors. If you want to stay up to date on Audrow’s latest works you can follow him on Twitter, and LinkedIn.

Please stay tuned for exciting new content to come from Sense, Think, Act! In the meantime, existing episodes will remain available. If you haven’t listened to them yet, we encourage you to do so! We believe they’re very educational and inspirational to all in the robotics community.

5 posts - 5 participants

Read full topic

ROS 2 Router for Remote Robotics and Topic Filtering

2023-11-14T14:44:23Z

Hi everyone!

We’re introducing the new husarnet/ros2router Docker image, which allows you to easily bridge ROS 2 nodes running across different robots, servers, or laptops in various networks. It features built-in topic filtering, enabling you to decide in real-time which ROS 2 interface should be exposed to remote hosts.

There’s no need to change your DDS settings. Simply run our Docker image alongside your existing ROS 2 application, regardless of whether it’s running on a host or inside Docker containers.

Our Docker image is based on the newest release of eProsima DDSRouter and it automatically integrates with the Husarnet VPN client via its HTTP API.

For more details and tutorial on how to integrate husarnet/ros2router with your robots, computers, or multi-tenant cloud applications, check out the article: ROS 2 Router for Remote Robotics and Topic Filtering | Husarnet

1 post - 1 participant

Read full topic

ROS News for the Week of November 6th, 2023

2023-11-10T21:25:08Z

ROS News for November 5th, 2023

+ROSCon 2023 Videos and Slides Now Available! Our friends at PX4 have their event recaps up as well. Meanwhile, Odense Denmark is already planning ROSCon 2024.

+
+

+We’ve got a ROS Meetup Singapore at the end of the month. This event will focus on robot dev ops!
+

+The Conference on Robot Learning was this week. The gif above is taken from HomeRobot: Open Vocabulary Mobile Manipulation which uses a HelloRobot Stretch to basic tasks around the house. I’ve included some of the open access papers I came across this week below.

+
+

+Cruise is not having a good week. Last week it was made public that Cruise vehicles needed human assistance every five miles. Early this week it was published that Cruise knew their cars had problems detecting children while driving autonomously. Now Cruise and GM are recalling all their autonomous vehicles and laying off staff.

+
+

Events

News

Papers (Mainly CoRL, but also others)

ROS

+
+

Got a minute? Why not help out some other robot developers?

5 posts - 3 participants

Read full topic

⚜️ ROSCon 2023 Videos and Slides Now Available!

2023-11-09T17:38:33Z

ROSCon 2023 Videos and Slides Now Available

Hi Everyone,

I am happy to announce that the videos and slides from ROSCon 2023 are now available online. You can find everything on the ROSCon website and in the OSRF Vimeo Showcase of the event. We’ve also created a short link for the videos that should make the videos easier to share: bit.ly/ROSCon23Vids. To aid discoverability on ROS Discourse I’ve pasted links to all of the talks at the bottom of the post that you can also use.

Along with the videos and slides we’ve put together a quick wrap up post on openrobotics.org. If you want to see some of our professional photos from the event please take a look.

If you missed ROSCon this year and would like a chance to meet up with your colleagues we still have ROSCon Germany next week and ROSCon India coming up in about a month. As for ROSCon 2024, Odense, Denmark is already getting ready for our visit next year.

Finally, I want to thank everyone who made ROSCon 2023 possible! We couldn’t put together such a fantastic event without the help of our speakers, sponsors, volunteers, reviewers, and workshop organizers. You all deserve a round of applause.

ROSCon 2023 Talks

10 posts - 4 participants

Read full topic

CoppeliaSim V4.6 Released: enhanced Python integration

2023-11-08T18:28:55Z

Robotics simulator: enhanced Python integration in CoppeliaSim

+I’m happy to share the latest update of CoppeliaSim: version 4.6 is out, with enhanced Python integration:

Effortless connection to CoppeliaSim from any Python script
Access to all of CoppeliaSim’s objects and API
CoppeliaSim library incorporation into a Python script
Efficiently scheduling, initiation, and execution of multiple embedded Python scripts

For more information, please visit https://www.coppeliarobotics.com

CoppeliaSim Edu is free to download and works out-of-the-box, no registration required

Cheers,
+Marc

1 post - 1 participant

Read full topic

Update from the Deliberation Working Group

2023-11-08T17:15:48Z

On Monday, the latest meeting of the Deliberation Working Group took place. We had a presentation by Thomas Horstink on how he uses Petri Nets to control drones, which was super exciting and insightful.
+You can find minutes, video recordings and slides here

The next meeting will happen on 4 December, and I am looking forward to @grey presenting aspects of Deliberation in OpenRMF

1 post - 1 participant

Read full topic

New Packages for Iron Irwini 2023-11-08

2023-11-08T02:09:13Z

We’re happy to announce 2 new packages and 170 updates are now available in ROS 2 Iron Irwini . This sync was tagged as iron/2023-11-08 .

Package Updates for iron

Added Packages [2]:

ros-iron-interactive-marker-twist-server: 2.1.0-1
ros-iron-interactive-marker-twist-server-dbgsym: 2.1.0-1

Updated Packages [170]:

ros-iron-ackermann-steering-controller: 3.16.0-1 → 3.17.0-1

ros-iron-ackermann-steering-controller-dbgsym: 3.16.0-1 → 3.17.0-1

ros-iron-admittance-controller: 3.16.0-1 → 3.17.0-1

ros-iron-admittance-controller-dbgsym: 3.16.0-1 → 3.17.0-1

ros-iron-bicycle-steering-controller: 3.16.0-1 → 3.17.0-1

ros-iron-bicycle-steering-controller-dbgsym: 3.16.0-1 → 3.17.0-1

ros-iron-catch-ros2: 0.1.0-1 → 0.2.0-1

ros-iron-catch-ros2-dbgsym: 0.1.0-1 → 0.2.0-1

ros-iron-controller-interface: 3.19.1-1 → 3.20.0-1

ros-iron-controller-interface-dbgsym: 3.19.1-1 → 3.20.0-1

ros-iron-controller-manager: 3.19.1-1 → 3.20.0-1

ros-iron-controller-manager-dbgsym: 3.19.1-1 → 3.20.0-1

ros-iron-controller-manager-msgs: 3.19.1-1 → 3.20.0-1
ros-iron-controller-manager-msgs-dbgsym: 3.19.1-1 → 3.20.0-1
ros-iron-depthai-bridge: 2.8.1-1 → 2.8.2-1
ros-iron-depthai-bridge-dbgsym: 2.8.1-1 → 2.8.2-1
ros-iron-depthai-descriptions: 2.8.1-1 → 2.8.2-1
ros-iron-depthai-examples: 2.8.1-1 → 2.8.2-1
ros-iron-depthai-examples-dbgsym: 2.8.1-1 → 2.8.2-1
ros-iron-depthai-filters: 2.8.1-1 → 2.8.2-1
ros-iron-depthai-filters-dbgsym: 2.8.1-1 → 2.8.2-1
ros-iron-depthai-ros: 2.8.1-1 → 2.8.2-1
ros-iron-depthai-ros-driver: 2.8.1-1 → 2.8.2-1
ros-iron-depthai-ros-driver-dbgsym: 2.8.1-1 → 2.8.2-1
ros-iron-depthai-ros-msgs: 2.8.1-1 → 2.8.2-1
ros-iron-depthai-ros-msgs-dbgsym: 2.8.1-1 → 2.8.2-1
ros-iron-diff-drive-controller: 3.16.0-1 → 3.17.0-1
ros-iron-diff-drive-controller-dbgsym: 3.16.0-1 → 3.17.0-1
ros-iron-effort-controllers: 3.16.0-1 → 3.17.0-1
ros-iron-effort-controllers-dbgsym: 3.16.0-1 → 3.17.0-1
ros-iron-force-torque-sensor-broadcaster: 3.16.0-1 → 3.17.0-1
ros-iron-force-torque-sensor-broadcaster-dbgsym: 3.16.0-1 → 3.17.0-1
ros-iron-forward-command-controller: 3.16.0-1 → 3.17.0-1
ros-iron-forward-command-controller-dbgsym: 3.16.0-1 → 3.17.0-1
ros-iron-foxglove-bridge: 0.7.2-1 → 0.7.3-1
ros-iron-foxglove-bridge-dbgsym: 0.7.2-1 → 0.7.3-1
ros-iron-gripper-controllers: 3.16.0-1 → 3.17.0-1
ros-iron-gripper-controllers-dbgsym: 3.16.0-1 → 3.17.0-1
ros-iron-hardware-interface: 3.19.1-1 → 3.20.0-1
ros-iron-hardware-interface-dbgsym: 3.19.1-1 → 3.20.0-1
ros-iron-imu-sensor-broadcaster: 3.16.0-1 → 3.17.0-1
ros-iron-imu-sensor-broadcaster-dbgsym: 3.16.0-1 → 3.17.0-1
ros-iron-joint-limits: 3.19.1-1 → 3.20.0-1
ros-iron-joint-state-broadcaster: 3.16.0-1 → 3.17.0-1
ros-iron-joint-state-broadcaster-dbgsym: 3.16.0-1 → 3.17.0-1
ros-iron-joint-trajectory-controller: 3.16.0-1 → 3.17.0-1
ros-iron-joint-trajectory-controller-dbgsym: 3.16.0-1 → 3.17.0-1
ros-iron-joy: 3.2.0-1 → 3.3.0-1
ros-iron-joy-dbgsym: 3.2.0-1 → 3.3.0-1
ros-iron-joy-linux: 3.2.0-1 → 3.3.0-1
ros-iron-joy-linux-dbgsym: 3.2.0-1 → 3.3.0-1
ros-iron-joy-teleop: 1.4.0-2 → 1.5.0-1
ros-iron-key-teleop: 1.4.0-2 → 1.5.0-1
ros-iron-marti-can-msgs: 1.4.1-1 → 1.5.2-1
ros-iron-marti-can-msgs-dbgsym: 1.4.1-1 → 1.5.2-1
ros-iron-marti-common-msgs: 1.4.1-1 → 1.5.2-1
ros-iron-marti-common-msgs-dbgsym: 1.4.1-1 → 1.5.2-1
ros-iron-marti-dbw-msgs: 1.4.1-1 → 1.5.2-1
ros-iron-marti-dbw-msgs-dbgsym: 1.4.1-1 → 1.5.2-1
ros-iron-marti-introspection-msgs: 1.4.1-1 → 1.5.2-1
ros-iron-marti-introspection-msgs-dbgsym: 1.4.1-1 → 1.5.2-1
ros-iron-marti-nav-msgs: 1.4.1-1 → 1.5.2-1
ros-iron-marti-nav-msgs-dbgsym: 1.4.1-1 → 1.5.2-1
ros-iron-marti-perception-msgs: 1.4.1-1 → 1.5.2-1
ros-iron-marti-perception-msgs-dbgsym: 1.4.1-1 → 1.5.2-1
ros-iron-marti-sensor-msgs: 1.4.1-1 → 1.5.2-1
ros-iron-marti-sensor-msgs-dbgsym: 1.4.1-1 → 1.5.2-1
ros-iron-marti-status-msgs: 1.4.1-1 → 1.5.2-1
ros-iron-marti-status-msgs-dbgsym: 1.4.1-1 → 1.5.2-1
ros-iron-marti-visualization-msgs: 1.4.1-1 → 1.5.2-1
ros-iron-marti-visualization-msgs-dbgsym: 1.4.1-1 → 1.5.2-1
ros-iron-mcap-vendor: 0.22.3-1 → 0.22.4-1
ros-iron-mcap-vendor-dbgsym: 0.22.3-1 → 0.22.4-1
ros-iron-mouse-teleop: 1.4.0-2 → 1.5.0-1
ros-iron-mrpt2: 2.10.2-1 → 2.11.2-1
ros-iron-mrpt2-dbgsym: 2.10.2-1 → 2.11.2-1
ros-iron-ntrip-client-node: 0.5.1-1 → 0.5.2-1
ros-iron-ntrip-client-node-dbgsym: 0.5.1-1 → 0.5.2-1
ros-iron-position-controllers: 3.16.0-1 → 3.17.0-1
ros-iron-position-controllers-dbgsym: 3.16.0-1 → 3.17.0-1
ros-iron-range-sensor-broadcaster: 3.16.0-1 → 3.17.0-1
ros-iron-range-sensor-broadcaster-dbgsym: 3.16.0-1 → 3.17.0-1
ros-iron-ros-gz: 0.245.0-1 → 0.247.0-1
ros-iron-ros-gz-bridge: 0.245.0-1 → 0.247.0-1
ros-iron-ros-gz-bridge-dbgsym: 0.245.0-1 → 0.247.0-1
ros-iron-ros-gz-image: 0.245.0-1 → 0.247.0-1
ros-iron-ros-gz-image-dbgsym: 0.245.0-1 → 0.247.0-1
ros-iron-ros-gz-interfaces: 0.245.0-1 → 0.247.0-1
ros-iron-ros-gz-interfaces-dbgsym: 0.245.0-1 → 0.247.0-1
ros-iron-ros-gz-sim: 0.245.0-1 → 0.247.0-1
ros-iron-ros-gz-sim-dbgsym: 0.245.0-1 → 0.247.0-1
ros-iron-ros-gz-sim-demos: 0.245.0-1 → 0.247.0-1
ros-iron-ros-ign: 0.245.0-1 → 0.247.0-1
ros-iron-ros-ign-bridge: 0.245.0-1 → 0.247.0-1
ros-iron-ros-ign-bridge-dbgsym: 0.245.0-1 → 0.247.0-1
ros-iron-ros-ign-gazebo: 0.245.0-1 → 0.247.0-1
ros-iron-ros-ign-gazebo-dbgsym: 0.245.0-1 → 0.247.0-1
ros-iron-ros-ign-gazebo-demos: 0.245.0-1 → 0.247.0-1
ros-iron-ros-ign-image: 0.245.0-1 → 0.247.0-1
ros-iron-ros-ign-image-dbgsym: 0.245.0-1 → 0.247.0-1
ros-iron-ros-ign-interfaces: 0.245.0-1 → 0.247.0-1
ros-iron-ros-ign-interfaces-dbgsym: 0.245.0-1 → 0.247.0-1
ros-iron-ros2-control: 3.19.1-1 → 3.20.0-1
ros-iron-ros2-control-test-assets: 3.19.1-1 → 3.20.0-1
ros-iron-ros2-controllers: 3.16.0-1 → 3.17.0-1
ros-iron-ros2-controllers-test-nodes: 3.16.0-1 → 3.17.0-1
ros-iron-ros2bag: 0.22.3-1 → 0.22.4-1
ros-iron-ros2controlcli: 3.19.1-1 → 3.20.0-1
ros-iron-rosbag2: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-compression: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-compression-dbgsym: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-compression-zstd: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-compression-zstd-dbgsym: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-cpp: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-cpp-dbgsym: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-examples-cpp: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-examples-cpp-dbgsym: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-examples-py: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-interfaces: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-interfaces-dbgsym: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-performance-benchmarking: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-performance-benchmarking-msgs: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-py: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-storage: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-storage-dbgsym: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-storage-default-plugins: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-storage-mcap: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-storage-mcap-dbgsym: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-storage-sqlite3: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-storage-sqlite3-dbgsym: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-test-common: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-test-msgdefs: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-test-msgdefs-dbgsym: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-tests: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-transport: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-transport-dbgsym: 0.22.3-1 → 0.22.4-1
ros-iron-rqt-controller-manager: 3.19.1-1 → 3.20.0-1
ros-iron-rqt-joint-trajectory-controller: 3.16.0-1 → 3.17.0-1
ros-iron-sdl2-vendor: 3.2.0-1 → 3.3.0-1
ros-iron-shared-queues-vendor: 0.22.3-1 → 0.22.4-1
ros-iron-spacenav: 3.2.0-1 → 3.3.0-1
ros-iron-spacenav-dbgsym: 3.2.0-1 → 3.3.0-1
ros-iron-sqlite3-vendor: 0.22.3-1 → 0.22.4-1
ros-iron-steering-controllers-library: 3.16.0-1 → 3.17.0-1
ros-iron-steering-controllers-library-dbgsym: 3.16.0-1 → 3.17.0-1
ros-iron-teleop-tools: 1.4.0-2 → 1.5.0-1
ros-iron-teleop-tools-msgs: 1.4.0-2 → 1.5.0-1
ros-iron-teleop-tools-msgs-dbgsym: 1.4.0-2 → 1.5.0-1
ros-iron-transmission-interface: 3.19.1-1 → 3.20.0-1
ros-iron-transmission-interface-dbgsym: 3.19.1-1 → 3.20.0-1
ros-iron-tricycle-controller: 3.16.0-1 → 3.17.0-1
ros-iron-tricycle-controller-dbgsym: 3.16.0-1 → 3.17.0-1
ros-iron-tricycle-steering-controller: 3.16.0-1 → 3.17.0-1
ros-iron-tricycle-steering-controller-dbgsym: 3.16.0-1 → 3.17.0-1
ros-iron-ublox-dgnss: 0.5.1-1 → 0.5.2-1
ros-iron-ublox-dgnss-node: 0.5.1-1 → 0.5.2-1
ros-iron-ublox-dgnss-node-dbgsym: 0.5.1-1 → 0.5.2-1
ros-iron-ublox-nav-sat-fix-hp-node: 0.5.1-1 → 0.5.2-1
ros-iron-ublox-nav-sat-fix-hp-node-dbgsym: 0.5.1-1 → 0.5.2-1
ros-iron-ublox-ubx-interfaces: 0.5.1-1 → 0.5.2-1
ros-iron-ublox-ubx-interfaces-dbgsym: 0.5.1-1 → 0.5.2-1
ros-iron-ublox-ubx-msgs: 0.5.1-1 → 0.5.2-1
ros-iron-ublox-ubx-msgs-dbgsym: 0.5.1-1 → 0.5.2-1
ros-iron-velocity-controllers: 3.16.0-1 → 3.17.0-1
ros-iron-velocity-controllers-dbgsym: 3.16.0-1 → 3.17.0-1
ros-iron-wiimote: 3.2.0-1 → 3.3.0-1
ros-iron-wiimote-dbgsym: 3.2.0-1 → 3.3.0-1
ros-iron-wiimote-msgs: 3.2.0-1 → 3.3.0-1
ros-iron-wiimote-msgs-dbgsym: 3.2.0-1 → 3.3.0-1
ros-iron-zstd-vendor: 0.22.3-1 → 0.22.4-1

Removed Packages [0]:

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

Adam Serafin
Alejandro Hernandez
Bence Magyar
Brandon Ong
Chris Lalancette
Denis Štogl
Enrique Fernandez
Foxglove
Geoff Sokoll
John Hurliman
Jonathan Bohren
Jose-Luis Blanco-Claraco
Louise Poubel
Michael Orlov
Mike Purvis
Nick Hortovanyi
Nick Morales
ROS Tooling Working Group
Sachin Guruswamy
Southwest Research Institute
geoff
sachin

1 post - 1 participant

Read full topic

BT-Studio 0.2 available (with video)

2023-11-06T19:47:12Z

Hi folks,

we have just published today the 0.2 release of our BT Studio. This release introduces a web-based visual IDE that enhances the development of ROS 2 applications with Behavior Trees.

[BT Studio] Version 0.2 released: showcasing the Web IDE.

+ + + +

BT Studio has multi-project support for improved efficiency and an integrated graphical tree editor to ease the design of complex tree structures. Additionally, once apps are defined, they can be downloaded as ROS 2 packages, with dependencies handled for seamless installation and use. ros2 #BehaviorTrees python

In addition, some clarifications regarding the last Deliberation Working group meeting (23-10-02) @ct2034 @fmrico :

+
JdeRobot is a non profit association for developing open source software in robotics and AI. We started informally in 2003 and finally registered formally in 2018. JdeRobot is not a “false spin off from URJC”, despite it was born at that university. We have contributors from several Spanish universities (URJC, UPM, UCM, UJI…) and from several countries. Since 2015 we have participated 8 times at Google Summer of Code developing open source robotics software projects.
+
+
We do not “hate ROS”. We developed an ICE based robotics middleware until 2018, then we changed our approach, deprecated such software code base and widely adopted ROS. Since then all our software is ROS friendly. Developing an alternative middleware does not mean to hate other available ones :-).
+
+
We are currently working on integrating BehaviorTrees in our robot programming website, named Unibotics, and continuously improving it, both in reliability and in new functionalities. Unibotics is fully ROS based, and available online for the robotics community for free. Our BT functionality currently includes a translator to Python files and a visual editor. It will soon (0.3 release) include the dockerized execution of BT robotics applications.
+

Hope it helps,

1 post - 1 participant

Read full topic

Introducing launch-generator: A simplified launch description creation tool for ROS 2

2023-11-05T11:01:41Z

Launch-generator is a tool designed to ease the complexities and code redundancies inherent in ROS 2’s launch and launch_ros descriptions. It enables shorter and more concise descriptions compared to those made with launch and launch_ros. While there are actions not yet implemented in launch-generator, its add_action() function allows for the free addition of launch and launch_ros actions. (Feature addition requests are also welcome.) It also supports the inclusion of existing launch files, facilitating seamless collaboration with launch and launch_ros modules, so there’s no need to replace everything. It’s already published on PyPI and is ready to use with pip.

pip install launch-generator

I hope to alleviate the fatigue of writing launch files in Python by using this library.

1 post - 1 participant

Read full topic

ROS News for the Week of October 30th, 2023

2023-11-03T20:00:45Z

ROS News for the Week of October 30th, 2023

+
+

+I work closely with the executive teams for three or four open source non-profits, and let me tell you, things are really rough right now. Our friends at OpenCV are taking a new approach to fundraising, they are attempting to crowd fund the next release of OpenCV. If you use OpenCV please consider donating to their new IndieGoGo campaign and please help spread the word.

+
+

+Mass Robotics has created a new start-up incubator for early-stage robotics companies. What’s different about this incubator is that they don’t take a chunk of equity from the company (most incubators want between 5-10% of a new startup’s equity).

+
+

The Future of Robotics - What do the experts think? (ROSCon '23)

@joshnewans has put together a great set of interviews from ROSCon 2023. There are a number of other summaries from @TheConstruct and Weekly Robotics. The videos from ROSCon 2023 should be up on the website early next week.

+
+

+Remember that really cool open source hardware / software dexterous hand from CMU that I posted awhile back? – Our friends at Robotis are now selling the hand directly. There is even a kit version with lower end servos that you can purchase for about $500.

Events

News

ROS

ROS Questions

Please take a moment to help out your fellow developers by answering a few questions on robotics.stackexchange.com

1 post - 1 participant

Read full topic

Interviews from ROSCon '23

2023-11-02T20:58:19Z

Hi everyone, it was fantastic to get along to ROSCon (and the US) for the first time and meet so many of you!

Some of you might have seen or heard me getting around interviewing a few people. The plan was to get the video uploaded straight away before we continued our journey but some delays meant it had to wait until we got home.

Itâ€™s a bit of a departure from my usual format and I think I have some room to grow, but I hope you enjoy it nonetheless

P.S. Apologies for the clickbait title

The Future of Robotics - What do the experts think? (ROSCon '23)

+ +

Thanks especially to everyone who was involved in organising this great week!

1 post - 1 participant

Read full topic

Join the ROS Ambassador Program

2023-11-02T19:21:54Z

Dear ROS community,
+We are thrilled to announce the re-launch of the ROS Ambassadors Program, an initiative
+dedicated to spreading ROS knowledge globally.

Our Mission: Learn, Teach, and Empower with ROS

Our goal is simple: to learn and teach ROS, empowering individuals to share this knowledge
+with the world.

ROS Ambassador Benefits

As a ROS Ambassador, you will enjoy:

● Full Learning Access:
+Gain complimentary access to The Construct’s learning platform with a learner license valued at €439.
+Explore over 70 ROS courses to enhance your robot programming skills.

● ROS Ambassador Pack:
+Progress through different levels within the program and unlock exciting rewards.
+Each new stage comes with corresponding gifts sent directly to you.

How It Works?

The ROS Ambassadors program is open to beginners with limited or no prior ROS knowledge.

Upon joining the ROS Ambassadors program, you will be required to complete one ROS course each month, answer related questions to assist others, and spread ROS knowledge by creating a Q&A video tutorial and blog post for the ROS community.

How To Apply?

You need to send your profile to ambassadors@theconstructsim.com.
+Including the following information:

Programming Proficiency

C++ (from 0 to 5)
Python (from 0 to 5)

Current ROS level

Basics of ROS (from 0 to 5)
ROS Navigation (from 0 to 5)
MoveIt (from 0 to 5)
Gazebo (from 0 to 5)
ROS Control(from 0 to 5)

Nationality and Native Language
Educational Background
Current educational or professional status (studying or working)

For questions or more information, please check out here:

+ +

Join us in this exciting journey of knowledge and discovery. Become a ROS Ambassador and
+contribute to the growth of the ROS community, supported by The Construct.

Warm regards,
+The Construct | theconstruct.ai
+Where Your Robotics Career Happens

2 posts - 1 participant

Read full topic

Franka Emika <-> Agile Robots

2023-11-02T15:32:02Z

For the information of those concerned about Franka Emika financial problem

According to German Financial Newspaper “Handelsblatt” Agile Robots “takes over” Franka Emika for 28.5 million Euro. German Business Insider speaks of more than 33 million Euro. [Edit: Meanwhile Handelsblatt corrected their article to “over 30 million Euro” as well.]

Both companies are seated in Munich, Bavaria, Germany and have a DLR-background.

Correct wording should be found soon on the corresponding news website of the companies:

4 posts - 3 participants

Read full topic

Nav2 User Requests Survey Results

2023-10-31T17:47:36Z

Howdy yal,

Its yur rip-rawrin’ rootin’-tootin’ gun-slingin’ navigator in here parts I’m going as a cowboy for halloween today !

I wanted to highlight the newest post on Open Navigation’s blog going over the results of the 2023 Nav2 / ROS 2 User Survey I announced in conjunction with ROSCon in the discourse post below:

+ + +

You can check out the results:

+ + +

While you’re visiting, checkout some of the other blog posts we have! Especially the really neat ones introducing Open Navigation’s sponsors – they go over what these companies do as well as highlight how they use ROS 2 and Nav2 in their various products and services. They contain some special insight into how you can use Nav2 and ROS 2 to build product-quality robot systems and some of the features they leverage to make it happen!

Dexory

+ + +

Stereolabs

+ + +

Polymath

+ + +

Yeeeeee Hawwww

Marshall S. Macenski

1 post - 1 participant

Read full topic

Open Sourcing NVIDIA Isaac Sim URDF and MJCF Importer Extensions

2023-10-30T22:26:29Z

We are releasing the source code of the URDF and MJCF importer extensions for Isaac Sim, part of NVIDIA Omniverse.

Although Isaac Sim already comes with the precompiled versions of both extensions, having access to the source code allows a developer to enhance their functionality. In addition, the source code of those extensions can be used as an example to implement importer extensions to convert other file formats into the native OpenUSD used by Omniverse and Isaac Sim.

The URDF Importer Extension is available now at GitHub - NVIDIA-Omniverse/urdf-importer-extension: Omniverse URDF Importer under the permissive Apache 2 license. The source code can be built on both Linux and Windows following the instructions.

After building the extension, use the steps in this documentation to try out the URDF importer extension.

You can use the extension in Isaac Sim (or any other Omniverse application) using the following steps:

Go to Window->Extensions
Go to Settings (Hamburger menu on the right)
To Extension Search Paths section, add new extension folder to point to this downloaded repo root/_build/platform/release/exts (no slash at the end)
Check the extensions 3rd party (second tab on the left)
Enable omni.importer.urdf extension

The URDF Importer Extension is also used in the open source Orbit modular framework for robot learning powered by NVIDIA Isaac Sim. Orbit contains the convert_urdf.py example how to use the URDF Importer Extension programmatically from Python to convert URDF into USD.

See also GitHub - NVIDIA-Omniverse/kit-extension-template-cpp: Omniverse Kit C++ Extension Template for more information on how to develop a C++ extension for Omniverse from scratch.

Similarly, the MJCF Importer Extension is available at GitHub - NVIDIA-Omniverse/mjcf-importer-extension: Omniverse MJCF Importer Extension.

6 posts - 3 participants

Read full topic

ROS News for the Week of October 23rd, 2023

2023-10-28T00:27:17Z

ROS News for October 22nd, 2023

We did it! ROSCon 2023 and PX4 Summit are in the bag! We’ll have the videos up in the next couple of weeks! Thank you to everyone who made it possible! If one of the core maintainers owes you a PR or an e-mail please be patient, we’ve had a long couple of weeks.

Now is a great time to start thinking about joining us in Odense in 2024.

+
+

+ROS 2 TSC Community Representative Election results are in! Welcome your new reps @DLu and @smac!
+

+Nvidia was busy at ROSCon. They released a new robotics reference design called the Nova Carter. Nvidia also had multiple other announcements on topics like Jetson and Issac ROS – More – Even More
+

+Make sure to purchase your ROSCon Germany tickets asap! – Also the ROSCon India CFP is now open!

+
+

+Join us for a very spooky Gazebo Community Meeting w/ O3DE on 2023-10-31

+
+

Events

News

ROS 2 TSC Community Representative Election Results
Cruise has had a crazy couple weeks! Two weeks ago Cruise announced plans to expand to Houston. The following week Cruise, GM, and Honda announced plans to enter the Japanese market. Just hours later Cruise’s taxi permit was yanked in SF for safety concerns.
Open Hardware Creators in Academia – Over the past year and a half I’ve been helping the Open Source Hardware Association work on a grant to study the role of open hardware in academic research. That work just got released.
Reflections on ROS in Asia
Nvidia brings generative AI compatibility to robotics platforms – More - More
Humanoid robots face a major test with Amazon’s Digit pilots
These 27 Robotics Companies are Hiring
Amazon begins testing Agility’s Digit robot for warehouse work
Auterion Launches Skynode X, Its Next-Generation All-in-One Brain for Autonomous Drones and More
Building a full-stack robotics company in the age of large AI models
Computer Vision for Agriculture
New AMR safety standard available with release of ANSI/A3 R15.08-2
ROS 2 Laser-Based Weeding
Present and Future of SLAM in Extreme Environments: The DARPA SubT Challenge
“TurtleBot” for PX4 by ModalAI
OSHWA on OpenCV Livestream
Advanced Simulation and Perception Tools on NVIDIA Isaac Platform
ROS + Clearpath Robots for Landmine Detection
Delivery Robots used in a Bomb Threat – More
RoMe: Towards Large Scale Road Surface Reconstruction via Mesh Representation
V2V4Real: A large-scale real-world dataset for Vehicle-to-Vehicle Cooperative Perception
Framework for LiDAR-based moving object segmentation
GNSS Measurement Simulator (handy)
PC-NeRF: Parent-Child Neural Radiance Fields under Partial Sensor Data Loss in Autonomous Driving Environments
Instant-angelo: Build high-fidelity Digital Twin within 20 Minutes!
Japanese Traffic Light Detection Model
Awesome list for autonomous driving
What’s Next for Clearpath Robotics?
The South Pole has Roombas (ROS on all 7 continents!!!)

ROS

ROS Questions

Take a moment to help out your fellow developers on Robotics Stack Exchange.

1 post - 1 participant

Read full topic

ROS Discourse General: ROS 2 TSC Meeting Minutes 2023-11-16

Katherine_Scott — 2023-11-20T23:28:00+00:00

ROS 2 TSC Meeting Minutes 2023-11-16

ROS 2 TSC Contribution Report 2023-11-16.pdf (111.8 KB)

+
Attendees
+
- TSC Members +
  - Microsoft / Lou Amadio
  - eProsima / Jaime Martin Losa
  - Intrinsic.ai / Chris Lalancette
  - Intrinsic.ai / Katherine Scott
  - Canonical / Mirko Ferrati
  - OSRF / Geoff Biggs
  - Community / Francisco Martin Rico
  - Apex.AI / Michael Orlov
  - Bosch / Christian Henkel
  - Picknik / Henning Kayser
  - Devcom / Jerry Towler
  - iRobot / Alberto Soragna
  - iRobot / Brian Wilcox
  - Foxglove / Adrian Macneil
  - Wind River / Andrei Kholodnyi
  - Amazon / Aaron Blasdel
  - Toyota Research Institute / Ian McMahon
  - Sony / Tomoya Fujita
  +
- Observers +
  - Community / David Lu!! (observer until December)
  - Community / Steve Macenski (observer until December)
  - Locus Robotics / Bence Magyar
  +
- Absent (Please move to TSC Members Line): +
  - Apex.AI / Lyle Johnson
  - Intel / Harold Lang
  - Robotis / Will Son (excused)
  - ROS Industrial / Matt Robinson
  - Zettascale / Angelo Corsaro
  +
+
+
Preliminaries
+
- You should only have comment access to this document.
- [Kat ][1 min] Please remember to fill out your contribution report at the bottom of this document prior to the meeting.
+
+
Old business
+
- Welcome new TSC members. Steve and David +
  - Note: official start is in December but I’ve invited them to observe.
  - Full results can be found here.
  - 2023 ROS 2 Technical Steering Committee Community Representative Election Results
  +
- [20 min][Soragna] NEW TSC Production Working Group Proposal +
  - Charter on ROS Discourse
  - VOTE: FOR___14 / AGAINST 0 / TOTAL 18 / ABSTAIN 4
  - TODO: Add working group to Discourse and Docs
  +
+
+
New business
+
- [5 min][Kat] Do we want to change the next meeting date? +
  - Next meeting is 12/21/2023
  - Many people have Friday 12/22 off for the holiday.
  - Alternative date would be 12/14/2023 +
    - No objections. TODO: Move meeting.
    +
  +
- [25 min][Steve Macenski] – REP-2003 Sensor Data and Map QoS Settings +
  - Discuss this meeting, if no changes requested vote next meeting
  - REP 2003: Sensor Data and Map QoS Settings by SteveMacenski · Pull Request #212 · ros-infrastructure/rep · GitHub
  - TODO: Setup vote and send out e-mail
  +
+
+
Recurring business
+
- Next ROS 2 distro release +
  - Continued work on rmw_zenoh +
    - Working towards getting the graph cache actually working
    - Combining code with the old https://github.com/atolabs/rmw_zenoh +
      - Whole thing moved to GitHub - ros2/rmw_zenoh: RMW for ROS 2 using Zenoh as the middleware, development streams merged together
      +
    +
  - Update to REP-2000 for Jazzy happening soon +
    - Happened this week
    +
  - Switch to Ubuntu 24.04 +
    - Very early docker images now available
    - Will start working on various transitions in the next few weeks
    +
  +
- Working groups [<=5 mins each] +
  - [Bence] Control +
    - Finally branched for Iron +
      - Rolling getting breaking changes now
      - Controllers get URDF and CM update rate in init
      - diff_drive_controller doesn’t support non-stamped Twist anymore
      - Deprecations (warnings in place in Humble and Iron)
      +
    - Working on better nodeoptions configurability
    - (all versions) controller spawner accepts list of controllers and can spawn in order or at once
    - Discussions on Python support for both controllers and hardware components
    - More discussions to support async and distributed setups
    - Next WG meeting: mini-roadmapping session for next year
    +
  - [Martin Losa] Embedded +
    - No EWG meeting in october due ROSCON
    - Working in the Agenda for the November EWG (Nov 28th):
    - Pablo Garrido from eProsima will present a demo running Safe DDS across all three cores of the AMD KR260 platform – Cortex A53, Cortex R5, and MicroBlaze FPGA-softcore, interoperating with ROS2 +
      - You can see a video of the demo here
      +
    +
  - [Kayser] Manipulation +
    - Added support for node logging in moveit_ros and reverting it now since some ROS test went flaky
    - Discussing support for tool changing, requires dynamic robot model and possibly major API refactoring +
      - Early work has been implemented as MoveIt capability
      +
    - Refactoring MoveIt’s planner adapter chain +
      - intuitive call order
      - separate types for pre- and post-adapters
      - Better support for validation checks, step-wise result introspection and returning errors
      +
    +
  - [Woodall] Middleware +
    - No update (trying to schedule next meeting)
    +
  - [Macenski] Navigation +
    - Requested change to geometry_msgs/Polygon +
      - Adding unique identifer field to Polygon/Polygon Stamped · Issue #230 · ros2/common_interfaces · GitHub
      - Reviews please!
      +
    - Major rework on the MPPI critics to improve performance and behavior quality (Open Navigation)
    - Various threading violation fixes (Peanut, Open Navigation)
    - Collison Monitor upgrades: +
      - Watchdog for sensors to stop robot (Dexory)
      - Adding Polygon Source-type (Pixel Robotics)
      +
    - Starting collaboration with ROS 2 Control, Gazebo on TwistStamped migration from Twist for commanded velocities
    - New Coverage Navigator, Task Server! +
      - GitHub - open-navigation/opennav_coverage: Nav2 Compatible Complete Cover Task Server, Navigator, and BT Utils
      +
    +
  - [Andrei] Real-Time +
    - Real-time workshop at ROSCON +
      - ROScon 2023 real-time workshop
      - https://docs.google.com/presentation/d/1yHaHiukJe-87RhiN8WIkncY23HxFkJynCQ8j3dIFx_w/edit#slide=id.p
      - Different use cases for the real-time
      - Many participants want to understand the basics
      +
    - Raspberry Pi 5 image
    +
  - [Andrei] meta-ros (Open Embedded) +
    - Updated to the support humble and iron with the latest Yocto releases, GitHub - ros/meta-ros: OpenEmbedded Layers for ROS 1 and ROS 2
    - To update REP2000
    +
  - [Mirko] Security +
    - Last Security Working Group meeting happened on Nov. 14. The following points were discussed:
    - Progress on RustDDS, a memory-safe DDS implementation. Plan to have a presentation and discussion at a later meeting.
    - A vulnerability was reported to the FastDDS Github repo recently and shared on the group’s Matrix channel. We discussed the issue and supporting the reporter to get feedback from the project maintainers.
    +
  - [Orlov] Tooling +
    - Use enum values for offered_qos_profiles in code and string names in serialized metadata (rosbag2#1476)
    - Made progress on the following PRs: +
      +
    +
  +
+

1 post - 1 participant

Read full topic

ROS Discourse General: Upcoming API break in urdfdom

clalancette — 2023-11-20T18:51:06+00:00

Hi all,

Please bear with me on a long post about urdfdom.

For those who don’t know, GitHub - ros/urdfdom: URDF parser houses the source code that both ROS 1 and ROS 2 use to parse and interact with URDF files.

Please also respond if you have any other questions or concerns about this change. Thank you.

2 posts - 2 participants

Read full topic

ROS Discourse General: Important Announcement, Patch Release 3 and New Packages for Iron Irwini 2023-11-20

Yadunund — 2023-11-20T16:37:22+00:00

We’re happy to announce a new Iron release

The latest sync brings 11 new packages and 118 updates to ROS 2 Iron Irwini. This sync was tagged as iron/2023-11-20 .

Package Updates for iron

Added Packages [11]:

ros-iron-event-camera-codecs: 1.2.2-1
ros-iron-event-camera-codecs-dbgsym: 1.2.2-1
ros-iron-event-camera-msgs: 1.2.5-1
ros-iron-event-camera-msgs-dbgsym: 1.2.5-1
ros-iron-leo: 2.0.0-1
ros-iron-leo-description: 2.0.0-1
ros-iron-leo-desktop: 2.0.0-1
ros-iron-leo-msgs: 2.0.0-1
ros-iron-leo-msgs-dbgsym: 2.0.0-1
ros-iron-leo-teleop: 2.0.0-1
ros-iron-leo-viz: 2.0.0-1

Updated Packages [118]:

ros-iron-controller-interface: 3.20.0-1 → 3.21.0-1
ros-iron-controller-interface-dbgsym: 3.20.0-1 → 3.21.0-1
ros-iron-controller-manager: 3.20.0-1 → 3.21.0-1
ros-iron-controller-manager-dbgsym: 3.20.0-1 → 3.21.0-1
ros-iron-controller-manager-msgs: 3.20.0-1 → 3.21.0-1
ros-iron-controller-manager-msgs-dbgsym: 3.20.0-1 → 3.21.0-1
ros-iron-fastrtps-cmake-module: 3.0.1-1 → 3.0.2-1
ros-iron-hardware-interface: 3.20.0-1 → 3.21.0-1
ros-iron-hardware-interface-dbgsym: 3.20.0-1 → 3.21.0-1
ros-iron-joint-limits: 3.20.0-1 → 3.21.0-1
ros-iron-libstatistics-collector: 1.5.1-2 → 1.5.2-1
ros-iron-libstatistics-collector-dbgsym: 1.5.1-2 → 1.5.2-1
ros-iron-mcap-vendor: 0.22.4-1 → 0.22.5-1
ros-iron-mcap-vendor-dbgsym: 0.22.4-1 → 0.22.5-1
ros-iron-rcl: 6.0.3-1 → 6.0.4-1
ros-iron-rcl-action: 6.0.3-1 → 6.0.4-1
ros-iron-rcl-action-dbgsym: 6.0.3-1 → 6.0.4-1
ros-iron-rcl-dbgsym: 6.0.3-1 → 6.0.4-1
ros-iron-rcl-lifecycle: 6.0.3-1 → 6.0.4-1
ros-iron-rcl-lifecycle-dbgsym: 6.0.3-1 → 6.0.4-1
ros-iron-rcl-yaml-param-parser: 6.0.3-1 → 6.0.4-1
ros-iron-rcl-yaml-param-parser-dbgsym: 6.0.3-1 → 6.0.4-1
ros-iron-rclcpp: 21.0.3-1 → 21.0.4-1
ros-iron-rclcpp-action: 21.0.3-1 → 21.0.4-1
ros-iron-rclcpp-action-dbgsym: 21.0.3-1 → 21.0.4-1
ros-iron-rclcpp-components: 21.0.3-1 → 21.0.4-1
ros-iron-rclcpp-components-dbgsym: 21.0.3-1 → 21.0.4-1
ros-iron-rclcpp-dbgsym: 21.0.3-1 → 21.0.4-1
ros-iron-rclcpp-lifecycle: 21.0.3-1 → 21.0.4-1
ros-iron-rclcpp-lifecycle-dbgsym: 21.0.3-1 → 21.0.4-1
ros-iron-rclpy: 4.1.3-1 → 4.1.4-1
ros-iron-rcpputils: 2.6.1-3 → 2.6.2-1
ros-iron-rcpputils-dbgsym: 2.6.1-3 → 2.6.2-1
ros-iron-rcutils: 6.2.1-2 → 6.2.2-2
ros-iron-rcutils-dbgsym: 6.2.1-2 → 6.2.2-2
ros-iron-rmw-fastrtps-cpp: 7.1.1-2 → 7.1.2-1
ros-iron-rmw-fastrtps-cpp-dbgsym: 7.1.1-2 → 7.1.2-1
ros-iron-rmw-fastrtps-dynamic-cpp: 7.1.1-2 → 7.1.2-1
ros-iron-rmw-fastrtps-dynamic-cpp-dbgsym: 7.1.1-2 → 7.1.2-1
ros-iron-rmw-fastrtps-shared-cpp: 7.1.1-2 → 7.1.2-1
ros-iron-rmw-fastrtps-shared-cpp-dbgsym: 7.1.1-2 → 7.1.2-1
ros-iron-ros2-control: 3.20.0-1 → 3.21.0-1
ros-iron-ros2-control-test-assets: 3.20.0-1 → 3.21.0-1
ros-iron-ros2action: 0.25.3-1 → 0.25.4-1
ros-iron-ros2bag: 0.22.4-1 → 0.22.5-1
ros-iron-ros2cli: 0.25.3-1 → 0.25.4-1
ros-iron-ros2cli-test-interfaces: 0.25.3-1 → 0.25.4-1
ros-iron-ros2cli-test-interfaces-dbgsym: 0.25.3-1 → 0.25.4-1
ros-iron-ros2component: 0.25.3-1 → 0.25.4-1
ros-iron-ros2controlcli: 3.20.0-1 → 3.21.0-1
ros-iron-ros2doctor: 0.25.3-1 → 0.25.4-1
ros-iron-ros2interface: 0.25.3-1 → 0.25.4-1
ros-iron-ros2lifecycle: 0.25.3-1 → 0.25.4-1
ros-iron-ros2lifecycle-test-fixtures: 0.25.3-1 → 0.25.4-1
ros-iron-ros2lifecycle-test-fixtures-dbgsym: 0.25.3-1 → 0.25.4-1
ros-iron-ros2multicast: 0.25.3-1 → 0.25.4-1
ros-iron-ros2node: 0.25.3-1 → 0.25.4-1
ros-iron-ros2param: 0.25.3-1 → 0.25.4-1
ros-iron-ros2pkg: 0.25.3-1 → 0.25.4-1
ros-iron-ros2run: 0.25.3-1 → 0.25.4-1
ros-iron-ros2service: 0.25.3-1 → 0.25.4-1
ros-iron-ros2topic: 0.25.3-1 → 0.25.4-1
ros-iron-rosbag2: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-compression: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-compression-dbgsym: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-compression-zstd: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-compression-zstd-dbgsym: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-cpp: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-cpp-dbgsym: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-examples-cpp: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-examples-cpp-dbgsym: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-examples-py: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-interfaces: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-interfaces-dbgsym: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-performance-benchmarking: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-performance-benchmarking-msgs: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-py: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-storage: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-storage-dbgsym: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-storage-default-plugins: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-storage-mcap: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-storage-mcap-dbgsym: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-storage-sqlite3: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-storage-sqlite3-dbgsym: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-test-common: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-test-msgdefs: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-test-msgdefs-dbgsym: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-tests: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-transport: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-transport-dbgsym: 0.22.4-1 → 0.22.5-1
ros-iron-rosidl-dynamic-typesupport: 0.0.4-1 → 0.0.5-1
ros-iron-rosidl-dynamic-typesupport-dbgsym: 0.0.4-1 → 0.0.5-1
ros-iron-rosidl-typesupport-fastrtps-c: 3.0.1-1 → 3.0.2-1
ros-iron-rosidl-typesupport-fastrtps-c-dbgsym: 3.0.1-1 → 3.0.2-1
ros-iron-rosidl-typesupport-fastrtps-cpp: 3.0.1-1 → 3.0.2-1
ros-iron-rosidl-typesupport-fastrtps-cpp-dbgsym: 3.0.1-1 → 3.0.2-1
ros-iron-rqt-controller-manager: 3.20.0-1 → 3.21.0-1
ros-iron-rqt-reconfigure: 1.3.3-2 → 1.3.4-1
ros-iron-rviz-assimp-vendor: 12.4.4-1 → 12.4.5-1
ros-iron-rviz-common: 12.4.4-1 → 12.4.5-1
ros-iron-rviz-common-dbgsym: 12.4.4-1 → 12.4.5-1
ros-iron-rviz-default-plugins: 12.4.4-1 → 12.4.5-1
ros-iron-rviz-default-plugins-dbgsym: 12.4.4-1 → 12.4.5-1
ros-iron-rviz-ogre-vendor: 12.4.4-1 → 12.4.5-1
ros-iron-rviz-ogre-vendor-dbgsym: 12.4.4-1 → 12.4.5-1
ros-iron-rviz-rendering: 12.4.4-1 → 12.4.5-1
ros-iron-rviz-rendering-dbgsym: 12.4.4-1 → 12.4.5-1
ros-iron-rviz-rendering-tests: 12.4.4-1 → 12.4.5-1
ros-iron-rviz-visual-testing-framework: 12.4.4-1 → 12.4.5-1
ros-iron-rviz2: 12.4.4-1 → 12.4.5-1
ros-iron-rviz2-dbgsym: 12.4.4-1 → 12.4.5-1
ros-iron-shared-queues-vendor: 0.22.4-1 → 0.22.5-1
ros-iron-sqlite3-vendor: 0.22.4-1 → 0.22.5-1
ros-iron-transmission-interface: 3.20.0-1 → 3.21.0-1
ros-iron-transmission-interface-dbgsym: 3.20.0-1 → 3.21.0-1
ros-iron-twist-mux: 4.2.0-1 → 4.3.0-1
ros-iron-twist-mux-dbgsym: 4.2.0-1 → 4.3.0-1
ros-iron-zstd-vendor: 0.22.4-1 → 0.22.5-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:

+
Note: The list of contributors is incomplete as there may be an issue with the tool used to generate this report.
+

Alejandro Hernandez Cordero
Audrow Nash
Bence Magyar
Bernd Pfrommer
Brandon Ong
Dharini Dutia
Fictionlab
Foxglove
Geoffrey Biggs
Ivan Paunovic
Michael Orlov
ROS Tooling Working Group
Shane Loretz
geoff

1 post - 1 participant

Read full topic

ROS Discourse General: Again... Snapshot repo GPG key expired

peci1 — 2023-11-20T09:21:04+00:00

Since yesterday, there is a problem running Melodic Industrial CI:

$ sudo apt-get update -qq
+  W: GPG error: http://snapshots.ros.org/melodic/final/ubuntu bionic InRelease: The following signatures were invalid: EXPKEYSIG AD19BAB3CBF125EA ROS Snapshot builder <rosbuild@ros.org>
+  E: The repository 'http://snapshots.ros.org/melodic/final/ubuntu bionic InRelease' is not signed.
+

I know Melodic is EOL, but still, it should be usable from the snapshot repo, shouldnâ€™t it?

There is already another report on RSE, but I think this is a better place to discuss such problem.

8 posts - 6 participants

Read full topic

ROS Discourse General: Simple_launch approaching event handling

OlivierKermorgant — 2023-11-18T20:27:42+00:00

Hi,

A few posts on discourse and stackexchange have already highlighted the difficulty of writing Python launch files for ROS 2.

In particular, the syntax may be a bit verbose and the arguments somehow hard to handle as they are not raw Python types.

The current release allows easy handling of:

namespaces
conditions
finding a file inside a package (thanks os.walk)
container and composable nodes
spawning a robot_state_publisher from a xacro file with arguments, even if all of those come from launch arguments
uploading models to Gazebo
bridging topics with Gazebo (ros_gz_bridge wrapper)
setting use_sim_time for all nodes in the launch file
using the OpaqueFunction idiom (my favorite) without seeing perform or context everywhere, in case you really need raw Python types

6 posts - 4 participants

Read full topic

ROS Discourse General: ROS News for the Week of November 12th, 2023

Katherine_Scott — 2023-11-17T21:50:59+00:00

ROS News for the Week of November 12th, 2023

What's New and Upcoming in Open Source Robotics at ROSCon '23

Check out this fantastic PX4 and ROSCon recap video from our friends at PX4

+
+

+Our next Gazebo Community Meeting will include a report from the IIT Madras Aritra maritime robotics team.

+
+

+Check out this new ROS Noetic package that implements a Segment Anything Model as a ROS Service.

+
+

+All good things must come to an end. Audrow has stepped down from Sense, Think, Act.

+
+

Events

News

ROS

6 posts - 3 participants

Read full topic

ROS Discourse General: ROS Deployment Meeting (#1?)

tomoyafujita — 2023-11-16T19:18:23+00:00

Hi,

for those who are interested in how to manage and deploy the ROS application?, letâ€™s have a follow-up meeting as we promised at ROSCon 2023 BoF

revised from Automatic Deployment of ROS2 Based System to remote devices: Dual Copy or Containers?, besides we had 44 people registered to BoF: Deployment of ROS 2 to remote devices at ROSCon 2023.

with that, i think there are many interests about how to deploy and manage robot application. Please feel free to join the meeting

Date / Place

2023-12-04T17:00:00Z UTC

+ + +

(*) I am not able to do recording at this time.

Agenda

Really appreciate @ciandonovan , he is willing to share the experience and take the effort for ROS community.

ROSCon 2023 ROS with Kubernetes/KubeEdge Talk Follow-Up and QA/Discussion (@tomoyafujita ) 15-20mins +
- GitHub - fujitatomoya/ros_k8s: Kuberenetes / ROS&ROS2 Cluster Samples Issues / Explanation
+
ROS deployment control with podman and systemd. (@ciandonovan ) 25mins including QA/Discussion
Open Discussion (should we have regular meeting? other topics? problem sharing?) 5mins

How to join?

No registration is required, you can just jump in the meeting
Or if you do not want to miss, DM @tomoyafujita / tomoya.fujita825@gmail.com to get the meeting invitation.

Reference

+ + +

thanks,

14 posts - 8 participants

Read full topic

ROS Discourse General: New Packages for Noetic 2023-11-15

sloretz — 2023-11-16T00:47:59+00:00

We’re happy to announce 5 new packages and 51 updates are now available in ROS Noetic. This sync was tagged as noetic/2023-11-15.

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

Package Updates for ROS Noetic

Added Packages [5]:

ros-noetic-clearpath-onav-api-examples: 0.0.3-1
ros-noetic-clearpath-onav-api-examples-lib: 0.0.3-1
ros-noetic-clearpath-onav-examples: 0.0.3-1
ros-noetic-pr2eus-moveit: 0.3.15-3
ros-noetic-sick-scan-xd: 3.0.3-1

Updated Packages [51]:

ros-noetic-clearpath-configuration-msgs: 0.9.4-1 → 0.9.5-1
ros-noetic-clearpath-control-msgs: 0.9.4-1 → 0.9.5-1
ros-noetic-clearpath-dock-msgs: 0.9.4-1 → 0.9.5-1
ros-noetic-clearpath-localization-msgs: 0.9.4-1 → 0.9.5-1
ros-noetic-clearpath-mission-manager-msgs: 0.9.4-1 → 0.9.5-1
ros-noetic-clearpath-mission-scheduler-msgs: 0.9.4-1 → 0.9.5-1
ros-noetic-clearpath-msgs: 0.9.4-1 → 0.9.5-1
ros-noetic-clearpath-navigation-msgs: 0.9.4-1 → 0.9.5-1
ros-noetic-clearpath-platform-msgs: 0.9.4-1 → 0.9.5-1
ros-noetic-clearpath-safety-msgs: 0.9.4-1 → 0.9.5-1
ros-noetic-combined-robot-hw: 0.19.6-1 → 0.20.0-1
ros-noetic-combined-robot-hw-tests: 0.19.6-1 → 0.20.0-1
ros-noetic-controller-interface: 0.19.6-1 → 0.20.0-1
ros-noetic-controller-manager: 0.19.6-1 → 0.20.0-1
ros-noetic-controller-manager-msgs: 0.19.6-1 → 0.20.0-1
ros-noetic-controller-manager-tests: 0.19.6-1 → 0.20.0-1
ros-noetic-cpr-onav-description: 0.1.9-1 → 0.1.10-1
ros-noetic-cras-cpp-common: 2.3.3-1 → 2.3.4-1
ros-noetic-cras-docs-common: 2.3.3-1 → 2.3.4-1
ros-noetic-cras-py-common: 2.3.3-1 → 2.3.4-1
ros-noetic-cras-topic-tools: 2.3.3-1 → 2.3.4-1
ros-noetic-foxglove-bridge: 0.7.2-1 → 0.7.3-1
ros-noetic-hardware-interface: 0.19.6-1 → 0.20.0-1
ros-noetic-image-transport-codecs: 2.3.3-1 → 2.3.4-1
ros-noetic-joint-limits-interface: 0.19.6-1 → 0.20.0-1
ros-noetic-jsk-pr2eus: 0.3.15-1 → 0.3.15-3
ros-noetic-leo: 2.2.0-1 → 2.3.0-1
ros-noetic-leo-bringup: 2.3.0-1 → 2.4.0-1
ros-noetic-leo-description: 2.2.0-1 → 2.3.0-1
ros-noetic-leo-desktop: 0.2.3-1 → 0.3.0-1
ros-noetic-leo-fw: 2.3.0-1 → 2.4.0-1
ros-noetic-leo-msgs: 2.2.0-1 → 2.3.0-1
ros-noetic-leo-robot: 2.3.0-1 → 2.4.0-1
ros-noetic-leo-teleop: 2.2.0-1 → 2.3.0-1
ros-noetic-leo-viz: 0.2.3-1 → 0.3.0-1
ros-noetic-marti-can-msgs: 0.12.1-1 → 0.12.2-1
ros-noetic-marti-common-msgs: 0.12.1-1 → 0.12.2-1
ros-noetic-marti-dbw-msgs: 0.12.1-1 → 0.12.2-1
ros-noetic-marti-introspection-msgs: 0.12.1-1 → 0.12.2-1
ros-noetic-marti-nav-msgs: 0.12.1-1 → 0.12.2-1
ros-noetic-marti-perception-msgs: 0.12.1-1 → 0.12.2-1
ros-noetic-marti-sensor-msgs: 0.12.1-1 → 0.12.2-1
ros-noetic-marti-status-msgs: 0.12.1-1 → 0.12.2-1
ros-noetic-marti-visualization-msgs: 0.12.1-1 → 0.12.2-1
ros-noetic-mrpt2: 2.11.1-1 → 2.11.2-1
ros-noetic-openni2-camera: 1.6.0-1 → 1.6.1-1
ros-noetic-openni2-launch: 1.6.0-1 → 1.6.1-1
ros-noetic-pr2eus: 0.3.15-1 → 0.3.15-3
ros-noetic-ros-control: 0.19.6-1 → 0.20.0-1
ros-noetic-rqt-controller-manager: 0.19.6-1 → 0.20.0-1
ros-noetic-transmission-interface: 0.19.6-1 → 0.20.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:

Bence Magyar
Chris Iverach-Brereton
Fictionlab
Isaac I. Y. Saito
Jason Higgins
John Hurliman
Jose Mastrangelo
Jose-Luis Blanco-Claraco
José Mastrangelo
Kei Okada
Martin Pecka
Michael Ferguson
Roni Kreinin
Southwest Research Institute
YoheiKakiuchi
rostest

1 post - 1 participant

Read full topic

ROS Discourse General: Proposal for ROS 2 Production Working Group

bpwilcox — 2023-11-15T18:05:14+00:00

Call for Participation:
+If you are interested in updates or participating in working group meetings, please fill out the following google form survey:

+ +

4 posts - 2 participants

Read full topic

ROS Discourse General: Audrow Nash to step down from hosting the Sense, Think, Act podcast

Katherine_Scott — 2023-11-14T17:26:08+00:00

Hi Everyone,

5 posts - 5 participants

Read full topic

ROS Discourse General: ROS 2 Router for Remote Robotics and Topic Filtering

Nina — 2023-11-14T14:44:23+00:00

Hi everyone!

There’s no need to change your DDS settings. Simply run our Docker image alongside your existing ROS 2 application, regardless of whether it’s running on a host or inside Docker containers.

Our Docker image is based on the newest release of eProsima DDSRouter and it automatically integrates with the Husarnet VPN client via its HTTP API.

1 post - 1 participant

Read full topic

ROS Discourse General: ROS News for the Week of November 6th, 2023

Katherine_Scott — 2023-11-10T21:25:08+00:00

ROS News for November 5th, 2023

+ROSCon 2023 Videos and Slides Now Available! Our friends at PX4 have their event recaps up as well. Meanwhile, Odense Denmark is already planning ROSCon 2024.

+
+

+We’ve got a ROS Meetup Singapore at the end of the month. This event will focus on robot dev ops!
+

+
+

Events

News

Papers (Mainly CoRL, but also others)

ROS

+
+

Got a minute? Why not help out some other robot developers?

5 posts - 3 participants

Read full topic

ROS Discourse General: ⚜️ ROSCon 2023 Videos and Slides Now Available!

Katherine_Scott — 2023-11-09T17:38:33+00:00

ROSCon 2023 Videos and Slides Now Available

Hi Everyone,

Along with the videos and slides we’ve put together a quick wrap up post on openrobotics.org. If you want to see some of our professional photos from the event please take a look.

ROSCon 2023 Talks

10 posts - 4 participants

Read full topic

ROS Discourse General: CoppeliaSim V4.6 Released: enhanced Python integration

Marc — 2023-11-08T18:28:55+00:00

Robotics simulator: enhanced Python integration in CoppeliaSim

+I’m happy to share the latest update of CoppeliaSim: version 4.6 is out, with enhanced Python integration:

Effortless connection to CoppeliaSim from any Python script
Access to all of CoppeliaSim’s objects and API
CoppeliaSim library incorporation into a Python script
Efficiently scheduling, initiation, and execution of multiple embedded Python scripts

For more information, please visit https://www.coppeliarobotics.com

CoppeliaSim Edu is free to download and works out-of-the-box, no registration required

Cheers,
+Marc

1 post - 1 participant

Read full topic

ROS Discourse General: Update from the Deliberation Working Group

ct2034 — 2023-11-08T17:15:48+00:00

The next meeting will happen on 4 December, and I am looking forward to @grey presenting aspects of Deliberation in OpenRMF

1 post - 1 participant

Read full topic

ROS Discourse General: New Packages for Iron Irwini 2023-11-08

Yadunund — 2023-11-08T02:09:13+00:00

We’re happy to announce 2 new packages and 170 updates are now available in ROS 2 Iron Irwini . This sync was tagged as iron/2023-11-08 .

Package Updates for iron

Added Packages [2]:

ros-iron-interactive-marker-twist-server: 2.1.0-1
ros-iron-interactive-marker-twist-server-dbgsym: 2.1.0-1

Updated Packages [170]:

ros-iron-ackermann-steering-controller: 3.16.0-1 → 3.17.0-1
ros-iron-ackermann-steering-controller-dbgsym: 3.16.0-1 → 3.17.0-1
ros-iron-admittance-controller: 3.16.0-1 → 3.17.0-1
ros-iron-admittance-controller-dbgsym: 3.16.0-1 → 3.17.0-1
ros-iron-bicycle-steering-controller: 3.16.0-1 → 3.17.0-1
ros-iron-bicycle-steering-controller-dbgsym: 3.16.0-1 → 3.17.0-1
ros-iron-catch-ros2: 0.1.0-1 → 0.2.0-1
ros-iron-catch-ros2-dbgsym: 0.1.0-1 → 0.2.0-1
ros-iron-controller-interface: 3.19.1-1 → 3.20.0-1
ros-iron-controller-interface-dbgsym: 3.19.1-1 → 3.20.0-1
ros-iron-controller-manager: 3.19.1-1 → 3.20.0-1
ros-iron-controller-manager-dbgsym: 3.19.1-1 → 3.20.0-1
ros-iron-controller-manager-msgs: 3.19.1-1 → 3.20.0-1
ros-iron-controller-manager-msgs-dbgsym: 3.19.1-1 → 3.20.0-1
ros-iron-depthai-bridge: 2.8.1-1 → 2.8.2-1
ros-iron-depthai-bridge-dbgsym: 2.8.1-1 → 2.8.2-1
ros-iron-depthai-descriptions: 2.8.1-1 → 2.8.2-1
ros-iron-depthai-examples: 2.8.1-1 → 2.8.2-1
ros-iron-depthai-examples-dbgsym: 2.8.1-1 → 2.8.2-1
ros-iron-depthai-filters: 2.8.1-1 → 2.8.2-1
ros-iron-depthai-filters-dbgsym: 2.8.1-1 → 2.8.2-1
ros-iron-depthai-ros: 2.8.1-1 → 2.8.2-1
ros-iron-depthai-ros-driver: 2.8.1-1 → 2.8.2-1
ros-iron-depthai-ros-driver-dbgsym: 2.8.1-1 → 2.8.2-1
ros-iron-depthai-ros-msgs: 2.8.1-1 → 2.8.2-1
ros-iron-depthai-ros-msgs-dbgsym: 2.8.1-1 → 2.8.2-1
ros-iron-diff-drive-controller: 3.16.0-1 → 3.17.0-1
ros-iron-diff-drive-controller-dbgsym: 3.16.0-1 → 3.17.0-1
ros-iron-effort-controllers: 3.16.0-1 → 3.17.0-1
ros-iron-effort-controllers-dbgsym: 3.16.0-1 → 3.17.0-1
ros-iron-force-torque-sensor-broadcaster: 3.16.0-1 → 3.17.0-1
ros-iron-force-torque-sensor-broadcaster-dbgsym: 3.16.0-1 → 3.17.0-1
ros-iron-forward-command-controller: 3.16.0-1 → 3.17.0-1
ros-iron-forward-command-controller-dbgsym: 3.16.0-1 → 3.17.0-1
ros-iron-foxglove-bridge: 0.7.2-1 → 0.7.3-1
ros-iron-foxglove-bridge-dbgsym: 0.7.2-1 → 0.7.3-1
ros-iron-gripper-controllers: 3.16.0-1 → 3.17.0-1
ros-iron-gripper-controllers-dbgsym: 3.16.0-1 → 3.17.0-1
ros-iron-hardware-interface: 3.19.1-1 → 3.20.0-1
ros-iron-hardware-interface-dbgsym: 3.19.1-1 → 3.20.0-1
ros-iron-imu-sensor-broadcaster: 3.16.0-1 → 3.17.0-1
ros-iron-imu-sensor-broadcaster-dbgsym: 3.16.0-1 → 3.17.0-1
ros-iron-joint-limits: 3.19.1-1 → 3.20.0-1
ros-iron-joint-state-broadcaster: 3.16.0-1 → 3.17.0-1
ros-iron-joint-state-broadcaster-dbgsym: 3.16.0-1 → 3.17.0-1
ros-iron-joint-trajectory-controller: 3.16.0-1 → 3.17.0-1
ros-iron-joint-trajectory-controller-dbgsym: 3.16.0-1 → 3.17.0-1
ros-iron-joy: 3.2.0-1 → 3.3.0-1
ros-iron-joy-dbgsym: 3.2.0-1 → 3.3.0-1
ros-iron-joy-linux: 3.2.0-1 → 3.3.0-1
ros-iron-joy-linux-dbgsym: 3.2.0-1 → 3.3.0-1
ros-iron-joy-teleop: 1.4.0-2 → 1.5.0-1
ros-iron-key-teleop: 1.4.0-2 → 1.5.0-1
ros-iron-marti-can-msgs: 1.4.1-1 → 1.5.2-1
ros-iron-marti-can-msgs-dbgsym: 1.4.1-1 → 1.5.2-1
ros-iron-marti-common-msgs: 1.4.1-1 → 1.5.2-1
ros-iron-marti-common-msgs-dbgsym: 1.4.1-1 → 1.5.2-1
ros-iron-marti-dbw-msgs: 1.4.1-1 → 1.5.2-1
ros-iron-marti-dbw-msgs-dbgsym: 1.4.1-1 → 1.5.2-1
ros-iron-marti-introspection-msgs: 1.4.1-1 → 1.5.2-1
ros-iron-marti-introspection-msgs-dbgsym: 1.4.1-1 → 1.5.2-1
ros-iron-marti-nav-msgs: 1.4.1-1 → 1.5.2-1
ros-iron-marti-nav-msgs-dbgsym: 1.4.1-1 → 1.5.2-1
ros-iron-marti-perception-msgs: 1.4.1-1 → 1.5.2-1
ros-iron-marti-perception-msgs-dbgsym: 1.4.1-1 → 1.5.2-1
ros-iron-marti-sensor-msgs: 1.4.1-1 → 1.5.2-1
ros-iron-marti-sensor-msgs-dbgsym: 1.4.1-1 → 1.5.2-1
ros-iron-marti-status-msgs: 1.4.1-1 → 1.5.2-1
ros-iron-marti-status-msgs-dbgsym: 1.4.1-1 → 1.5.2-1
ros-iron-marti-visualization-msgs: 1.4.1-1 → 1.5.2-1
ros-iron-marti-visualization-msgs-dbgsym: 1.4.1-1 → 1.5.2-1
ros-iron-mcap-vendor: 0.22.3-1 → 0.22.4-1
ros-iron-mcap-vendor-dbgsym: 0.22.3-1 → 0.22.4-1
ros-iron-mouse-teleop: 1.4.0-2 → 1.5.0-1
ros-iron-mrpt2: 2.10.2-1 → 2.11.2-1
ros-iron-mrpt2-dbgsym: 2.10.2-1 → 2.11.2-1
ros-iron-ntrip-client-node: 0.5.1-1 → 0.5.2-1
ros-iron-ntrip-client-node-dbgsym: 0.5.1-1 → 0.5.2-1
ros-iron-position-controllers: 3.16.0-1 → 3.17.0-1
ros-iron-position-controllers-dbgsym: 3.16.0-1 → 3.17.0-1
ros-iron-range-sensor-broadcaster: 3.16.0-1 → 3.17.0-1
ros-iron-range-sensor-broadcaster-dbgsym: 3.16.0-1 → 3.17.0-1
ros-iron-ros-gz: 0.245.0-1 → 0.247.0-1
ros-iron-ros-gz-bridge: 0.245.0-1 → 0.247.0-1
ros-iron-ros-gz-bridge-dbgsym: 0.245.0-1 → 0.247.0-1
ros-iron-ros-gz-image: 0.245.0-1 → 0.247.0-1
ros-iron-ros-gz-image-dbgsym: 0.245.0-1 → 0.247.0-1
ros-iron-ros-gz-interfaces: 0.245.0-1 → 0.247.0-1
ros-iron-ros-gz-interfaces-dbgsym: 0.245.0-1 → 0.247.0-1
ros-iron-ros-gz-sim: 0.245.0-1 → 0.247.0-1
ros-iron-ros-gz-sim-dbgsym: 0.245.0-1 → 0.247.0-1
ros-iron-ros-gz-sim-demos: 0.245.0-1 → 0.247.0-1
ros-iron-ros-ign: 0.245.0-1 → 0.247.0-1
ros-iron-ros-ign-bridge: 0.245.0-1 → 0.247.0-1
ros-iron-ros-ign-bridge-dbgsym: 0.245.0-1 → 0.247.0-1
ros-iron-ros-ign-gazebo: 0.245.0-1 → 0.247.0-1
ros-iron-ros-ign-gazebo-dbgsym: 0.245.0-1 → 0.247.0-1
ros-iron-ros-ign-gazebo-demos: 0.245.0-1 → 0.247.0-1
ros-iron-ros-ign-image: 0.245.0-1 → 0.247.0-1
ros-iron-ros-ign-image-dbgsym: 0.245.0-1 → 0.247.0-1
ros-iron-ros-ign-interfaces: 0.245.0-1 → 0.247.0-1
ros-iron-ros-ign-interfaces-dbgsym: 0.245.0-1 → 0.247.0-1
ros-iron-ros2-control: 3.19.1-1 → 3.20.0-1
ros-iron-ros2-control-test-assets: 3.19.1-1 → 3.20.0-1
ros-iron-ros2-controllers: 3.16.0-1 → 3.17.0-1
ros-iron-ros2-controllers-test-nodes: 3.16.0-1 → 3.17.0-1
ros-iron-ros2bag: 0.22.3-1 → 0.22.4-1
ros-iron-ros2controlcli: 3.19.1-1 → 3.20.0-1
ros-iron-rosbag2: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-compression: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-compression-dbgsym: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-compression-zstd: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-compression-zstd-dbgsym: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-cpp: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-cpp-dbgsym: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-examples-cpp: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-examples-cpp-dbgsym: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-examples-py: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-interfaces: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-interfaces-dbgsym: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-performance-benchmarking: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-performance-benchmarking-msgs: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-py: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-storage: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-storage-dbgsym: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-storage-default-plugins: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-storage-mcap: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-storage-mcap-dbgsym: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-storage-sqlite3: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-storage-sqlite3-dbgsym: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-test-common: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-test-msgdefs: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-test-msgdefs-dbgsym: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-tests: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-transport: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-transport-dbgsym: 0.22.3-1 → 0.22.4-1
ros-iron-rqt-controller-manager: 3.19.1-1 → 3.20.0-1
ros-iron-rqt-joint-trajectory-controller: 3.16.0-1 → 3.17.0-1
ros-iron-sdl2-vendor: 3.2.0-1 → 3.3.0-1
ros-iron-shared-queues-vendor: 0.22.3-1 → 0.22.4-1
ros-iron-spacenav: 3.2.0-1 → 3.3.0-1
ros-iron-spacenav-dbgsym: 3.2.0-1 → 3.3.0-1
ros-iron-sqlite3-vendor: 0.22.3-1 → 0.22.4-1
ros-iron-steering-controllers-library: 3.16.0-1 → 3.17.0-1
ros-iron-steering-controllers-library-dbgsym: 3.16.0-1 → 3.17.0-1
ros-iron-teleop-tools: 1.4.0-2 → 1.5.0-1
ros-iron-teleop-tools-msgs: 1.4.0-2 → 1.5.0-1
ros-iron-teleop-tools-msgs-dbgsym: 1.4.0-2 → 1.5.0-1
ros-iron-transmission-interface: 3.19.1-1 → 3.20.0-1
ros-iron-transmission-interface-dbgsym: 3.19.1-1 → 3.20.0-1
ros-iron-tricycle-controller: 3.16.0-1 → 3.17.0-1
ros-iron-tricycle-controller-dbgsym: 3.16.0-1 → 3.17.0-1
ros-iron-tricycle-steering-controller: 3.16.0-1 → 3.17.0-1
ros-iron-tricycle-steering-controller-dbgsym: 3.16.0-1 → 3.17.0-1
ros-iron-ublox-dgnss: 0.5.1-1 → 0.5.2-1
ros-iron-ublox-dgnss-node: 0.5.1-1 → 0.5.2-1
ros-iron-ublox-dgnss-node-dbgsym: 0.5.1-1 → 0.5.2-1
ros-iron-ublox-nav-sat-fix-hp-node: 0.5.1-1 → 0.5.2-1
ros-iron-ublox-nav-sat-fix-hp-node-dbgsym: 0.5.1-1 → 0.5.2-1
ros-iron-ublox-ubx-interfaces: 0.5.1-1 → 0.5.2-1
ros-iron-ublox-ubx-interfaces-dbgsym: 0.5.1-1 → 0.5.2-1
ros-iron-ublox-ubx-msgs: 0.5.1-1 → 0.5.2-1
ros-iron-ublox-ubx-msgs-dbgsym: 0.5.1-1 → 0.5.2-1
ros-iron-velocity-controllers: 3.16.0-1 → 3.17.0-1
ros-iron-velocity-controllers-dbgsym: 3.16.0-1 → 3.17.0-1
ros-iron-wiimote: 3.2.0-1 → 3.3.0-1
ros-iron-wiimote-dbgsym: 3.2.0-1 → 3.3.0-1
ros-iron-wiimote-msgs: 3.2.0-1 → 3.3.0-1
ros-iron-wiimote-msgs-dbgsym: 3.2.0-1 → 3.3.0-1
ros-iron-zstd-vendor: 0.22.3-1 → 0.22.4-1

Removed Packages [0]:

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

Adam Serafin
Alejandro Hernandez
Bence Magyar
Brandon Ong
Chris Lalancette
Denis Štogl
Enrique Fernandez
Foxglove
Geoff Sokoll
John Hurliman
Jonathan Bohren
Jose-Luis Blanco-Claraco
Louise Poubel
Michael Orlov
Mike Purvis
Nick Hortovanyi
Nick Morales
ROS Tooling Working Group
Sachin Guruswamy
Southwest Research Institute
geoff
sachin

1 post - 1 participant

Read full topic

ROS Discourse General: BT-Studio 0.2 available (with video)

jmplaza — 2023-11-06T19:47:12+00:00

Hi folks,

we have just published today the 0.2 release of our BT Studio. This release introduces a web-based visual IDE that enhances the development of ROS 2 applications with Behavior Trees.

[BT Studio] Version 0.2 released: showcasing the Web IDE.

+ + + +

In addition, some clarifications regarding the last Deliberation Working group meeting (23-10-02) @ct2034 @fmrico :

+
JdeRobot is a non profit association for developing open source software in robotics and AI. We started informally in 2003 and finally registered formally in 2018. JdeRobot is not a “false spin off from URJC”, despite it was born at that university. We have contributors from several Spanish universities (URJC, UPM, UCM, UJI…) and from several countries. Since 2015 we have participated 8 times at Google Summer of Code developing open source robotics software projects.
+
+
We do not “hate ROS”. We developed an ICE based robotics middleware until 2018, then we changed our approach, deprecated such software code base and widely adopted ROS. Since then all our software is ROS friendly. Developing an alternative middleware does not mean to hate other available ones :-).
+
+
We are currently working on integrating BehaviorTrees in our robot programming website, named Unibotics, and continuously improving it, both in reliability and in new functionalities. Unibotics is fully ROS based, and available online for the robotics community for free. Our BT functionality currently includes a translator to Python files and a visual editor. It will soon (0.3 release) include the dockerized execution of BT robotics applications.
+

Hope it helps,

1 post - 1 participant

Read full topic

ROS Discourse General: Introducing launch-generator: A simplified launch description creation tool for ROS 2

Tacha-S — 2023-11-05T11:01:41+00:00

pip install launch-generator

I hope to alleviate the fatigue of writing launch files in Python by using this library.

1 post - 1 participant

Read full topic

ROS Discourse General: ROS News for the Week of October 30th, 2023

Katherine_Scott — 2023-11-03T20:00:45+00:00

ROS News for the Week of October 30th, 2023

+
+

The Future of Robotics - What do the experts think? (ROSCon '23)

+
+

Events

News

ROS

ROS Questions

Please take a moment to help out your fellow developers by answering a few questions on robotics.stackexchange.com

1 post - 1 participant

Read full topic

ROS Discourse General: Interviews from ROSCon '23

joshnewans — 2023-11-02T20:58:19+00:00

Hi everyone, it was fantastic to get along to ROSCon (and the US) for the first time and meet so many of you!

Itâ€™s a bit of a departure from my usual format and I think I have some room to grow, but I hope you enjoy it nonetheless

P.S. Apologies for the clickbait title

The Future of Robotics - What do the experts think? (ROSCon '23)

+ +

Thanks especially to everyone who was involved in organising this great week!

1 post - 1 participant

Read full topic

ROS Discourse General: Join the ROS Ambassador Program

Sonia_W — 2023-11-02T19:21:54+00:00

Dear ROS community,
+We are thrilled to announce the re-launch of the ROS Ambassadors Program, an initiative
+dedicated to spreading ROS knowledge globally.

Our Mission: Learn, Teach, and Empower with ROS

Our goal is simple: to learn and teach ROS, empowering individuals to share this knowledge
+with the world.

ROS Ambassador Benefits

As a ROS Ambassador, you will enjoy:

● ROS Ambassador Pack:
+Progress through different levels within the program and unlock exciting rewards.
+Each new stage comes with corresponding gifts sent directly to you.

How It Works?

The ROS Ambassadors program is open to beginners with limited or no prior ROS knowledge.

How To Apply?

You need to send your profile to ambassadors@theconstructsim.com.
+Including the following information:

Programming Proficiency

C++ (from 0 to 5)
Python (from 0 to 5)

Current ROS level

Basics of ROS (from 0 to 5)
ROS Navigation (from 0 to 5)
MoveIt (from 0 to 5)
Gazebo (from 0 to 5)
ROS Control(from 0 to 5)

Nationality and Native Language
Educational Background
Current educational or professional status (studying or working)

For questions or more information, please check out here:

+ +

Join us in this exciting journey of knowledge and discovery. Become a ROS Ambassador and
+contribute to the growth of the ROS community, supported by The Construct.

Warm regards,
+The Construct | theconstruct.ai
+Where Your Robotics Career Happens

2 posts - 1 participant

Read full topic

ROS Discourse General: Franka Emika <-> Agile Robots

ThiloZimmermann — 2023-11-02T15:32:02+00:00

For the information of those concerned about Franka Emika financial problem

Both companies are seated in Munich, Bavaria, Germany and have a DLR-background.

Correct wording should be found soon on the corresponding news website of the companies:

4 posts - 3 participants

Read full topic

ROS Discourse General: Nav2 User Requests Survey Results

smac — 2023-10-31T17:47:36+00:00

Howdy yal,

Its yur rip-rawrin’ rootin’-tootin’ gun-slingin’ navigator in here parts I’m going as a cowboy for halloween today !

I wanted to highlight the newest post on Open Navigation’s blog going over the results of the 2023 Nav2 / ROS 2 User Survey I announced in conjunction with ROSCon in the discourse post below:

+ + +

You can check out the results:

+ + +

Dexory

+ + +

Stereolabs

+ + +

Polymath

+ + +

Yeeeeee Hawwww

Marshall S. Macenski

1 post - 1 participant

Read full topic

ROS Discourse General: Open Sourcing NVIDIA Isaac Sim URDF and MJCF Importer Extensions

ErwinCoumans — 2023-10-30T22:26:29+00:00

We are releasing the source code of the URDF and MJCF importer extensions for Isaac Sim, part of NVIDIA Omniverse.

After building the extension, use the steps in this documentation to try out the URDF importer extension.

You can use the extension in Isaac Sim (or any other Omniverse application) using the following steps:

Go to Window->Extensions
Go to Settings (Hamburger menu on the right)
To Extension Search Paths section, add new extension folder to point to this downloaded repo root/_build/platform/release/exts (no slash at the end)
Check the extensions 3rd party (second tab on the left)
Enable omni.importer.urdf extension

See also GitHub - NVIDIA-Omniverse/kit-extension-template-cpp: Omniverse Kit C++ Extension Template for more information on how to develop a C++ extension for Omniverse from scratch.

Similarly, the MJCF Importer Extension is available at GitHub - NVIDIA-Omniverse/mjcf-importer-extension: Omniverse MJCF Importer Extension.

6 posts - 3 participants

Read full topic

ROS Discourse General: ROS News for the Week of October 23rd, 2023

Katherine_Scott — 2023-10-28T00:27:17+00:00

ROS News for October 22nd, 2023

Now is a great time to start thinking about joining us in Odense in 2024.

+
+

+ROS 2 TSC Community Representative Election results are in! Welcome your new reps @DLu and @smac!
+

+Make sure to purchase your ROSCon Germany tickets asap! – Also the ROSCon India CFP is now open!

+
+

+Join us for a very spooky Gazebo Community Meeting w/ O3DE on 2023-10-31

+
+

Events

News

ROS 2 TSC Community Representative Election Results
Cruise has had a crazy couple weeks! Two weeks ago Cruise announced plans to expand to Houston. The following week Cruise, GM, and Honda announced plans to enter the Japanese market. Just hours later Cruise’s taxi permit was yanked in SF for safety concerns.
Open Hardware Creators in Academia – Over the past year and a half I’ve been helping the Open Source Hardware Association work on a grant to study the role of open hardware in academic research. That work just got released.
Reflections on ROS in Asia
Nvidia brings generative AI compatibility to robotics platforms – More - More
Humanoid robots face a major test with Amazon’s Digit pilots
These 27 Robotics Companies are Hiring
Amazon begins testing Agility’s Digit robot for warehouse work
Auterion Launches Skynode X, Its Next-Generation All-in-One Brain for Autonomous Drones and More
Building a full-stack robotics company in the age of large AI models
Computer Vision for Agriculture
New AMR safety standard available with release of ANSI/A3 R15.08-2
ROS 2 Laser-Based Weeding
Present and Future of SLAM in Extreme Environments: The DARPA SubT Challenge
“TurtleBot” for PX4 by ModalAI
OSHWA on OpenCV Livestream
Advanced Simulation and Perception Tools on NVIDIA Isaac Platform
ROS + Clearpath Robots for Landmine Detection
Delivery Robots used in a Bomb Threat – More
RoMe: Towards Large Scale Road Surface Reconstruction via Mesh Representation
V2V4Real: A large-scale real-world dataset for Vehicle-to-Vehicle Cooperative Perception
Framework for LiDAR-based moving object segmentation
GNSS Measurement Simulator (handy)
PC-NeRF: Parent-Child Neural Radiance Fields under Partial Sensor Data Loss in Autonomous Driving Environments
Instant-angelo: Build high-fidelity Digital Twin within 20 Minutes!
Japanese Traffic Light Detection Model
Awesome list for autonomous driving
What’s Next for Clearpath Robotics?
The South Pole has Roombas (ROS on all 7 continents!!!)

ROS

ROS Questions

Take a moment to help out your fellow developers on Robotics Stack Exchange.

1 post - 1 participant

Read full topic

ROS Discourse General: ROS 2 TSC Meeting Minutes 2023-11-16

Mon, 20 Nov 2023 23:28:00 +0000

ROS 2 TSC Meeting Minutes 2023-11-16

ROS 2 TSC Contribution Report 2023-11-16.pdf (111.8 KB)

+
Attendees
+
- TSC Members +
  - Microsoft / Lou Amadio
  - eProsima / Jaime Martin Losa
  - Intrinsic.ai / Chris Lalancette
  - Intrinsic.ai / Katherine Scott
  - Canonical / Mirko Ferrati
  - OSRF / Geoff Biggs
  - Community / Francisco Martin Rico
  - Apex.AI / Michael Orlov
  - Bosch / Christian Henkel
  - Picknik / Henning Kayser
  - Devcom / Jerry Towler
  - iRobot / Alberto Soragna
  - iRobot / Brian Wilcox
  - Foxglove / Adrian Macneil
  - Wind River / Andrei Kholodnyi
  - Amazon / Aaron Blasdel
  - Toyota Research Institute / Ian McMahon
  - Sony / Tomoya Fujita
  +
- Observers +
  - Community / David Lu!! (observer until December)
  - Community / Steve Macenski (observer until December)
  - Locus Robotics / Bence Magyar
  +
- Absent (Please move to TSC Members Line): +
  - Apex.AI / Lyle Johnson
  - Intel / Harold Lang
  - Robotis / Will Son (excused)
  - ROS Industrial / Matt Robinson
  - Zettascale / Angelo Corsaro
  +
+
+
Preliminaries
+
- You should only have comment access to this document.
- [Kat ][1 min] Please remember to fill out your contribution report at the bottom of this document prior to the meeting.
+
+
Old business
+
- Welcome new TSC members. Steve and David +
  - Note: official start is in December but I’ve invited them to observe.
  - Full results can be found here.
  - 2023 ROS 2 Technical Steering Committee Community Representative Election Results
  +
- [20 min][Soragna] NEW TSC Production Working Group Proposal +
  - Charter on ROS Discourse
  - VOTE: FOR___14 / AGAINST 0 / TOTAL 18 / ABSTAIN 4
  - TODO: Add working group to Discourse and Docs
  +
+
+
New business
+
- [5 min][Kat] Do we want to change the next meeting date? +
  - Next meeting is 12/21/2023
  - Many people have Friday 12/22 off for the holiday.
  - Alternative date would be 12/14/2023 +
    - No objections. TODO: Move meeting.
    +
  +
- [25 min][Steve Macenski] – REP-2003 Sensor Data and Map QoS Settings +
  - Discuss this meeting, if no changes requested vote next meeting
  - REP 2003: Sensor Data and Map QoS Settings by SteveMacenski · Pull Request #212 · ros-infrastructure/rep · GitHub
  - TODO: Setup vote and send out e-mail
  +
+
+
Recurring business
+
- Next ROS 2 distro release +
  - Continued work on rmw_zenoh +
    - Working towards getting the graph cache actually working
    - Combining code with the old https://github.com/atolabs/rmw_zenoh +
      - Whole thing moved to GitHub - ros2/rmw_zenoh: RMW for ROS 2 using Zenoh as the middleware, development streams merged together
      +
    +
  - Update to REP-2000 for Jazzy happening soon +
    - Happened this week
    +
  - Switch to Ubuntu 24.04 +
    - Very early docker images now available
    - Will start working on various transitions in the next few weeks
    +
  +
- Working groups [<=5 mins each] +
  - [Bence] Control +
    - Finally branched for Iron +
      - Rolling getting breaking changes now
      - Controllers get URDF and CM update rate in init
      - diff_drive_controller doesn’t support non-stamped Twist anymore
      - Deprecations (warnings in place in Humble and Iron)
      +
    - Working on better nodeoptions configurability
    - (all versions) controller spawner accepts list of controllers and can spawn in order or at once
    - Discussions on Python support for both controllers and hardware components
    - More discussions to support async and distributed setups
    - Next WG meeting: mini-roadmapping session for next year
    +
  - [Martin Losa] Embedded +
    - No EWG meeting in october due ROSCON
    - Working in the Agenda for the November EWG (Nov 28th):
    - Pablo Garrido from eProsima will present a demo running Safe DDS across all three cores of the AMD KR260 platform – Cortex A53, Cortex R5, and MicroBlaze FPGA-softcore, interoperating with ROS2 +
      - You can see a video of the demo here
      +
    +
  - [Kayser] Manipulation +
    - Added support for node logging in moveit_ros and reverting it now since some ROS test went flaky
    - Discussing support for tool changing, requires dynamic robot model and possibly major API refactoring +
      - Early work has been implemented as MoveIt capability
      +
    - Refactoring MoveIt’s planner adapter chain +
      - intuitive call order
      - separate types for pre- and post-adapters
      - Better support for validation checks, step-wise result introspection and returning errors
      +
    +
  - [Woodall] Middleware +
    - No update (trying to schedule next meeting)
    +
  - [Macenski] Navigation +
    - Requested change to geometry_msgs/Polygon +
      - Adding unique identifer field to Polygon/Polygon Stamped · Issue #230 · ros2/common_interfaces · GitHub
      - Reviews please!
      +
    - Major rework on the MPPI critics to improve performance and behavior quality (Open Navigation)
    - Various threading violation fixes (Peanut, Open Navigation)
    - Collison Monitor upgrades: +
      - Watchdog for sensors to stop robot (Dexory)
      - Adding Polygon Source-type (Pixel Robotics)
      +
    - Starting collaboration with ROS 2 Control, Gazebo on TwistStamped migration from Twist for commanded velocities
    - New Coverage Navigator, Task Server! +
      - GitHub - open-navigation/opennav_coverage: Nav2 Compatible Complete Cover Task Server, Navigator, and BT Utils
      +
    +
  - [Andrei] Real-Time +
    - Real-time workshop at ROSCON +
      - ROScon 2023 real-time workshop
      - https://docs.google.com/presentation/d/1yHaHiukJe-87RhiN8WIkncY23HxFkJynCQ8j3dIFx_w/edit#slide=id.p
      - Different use cases for the real-time
      - Many participants want to understand the basics
      +
    - Raspberry Pi 5 image
    +
  - [Andrei] meta-ros (Open Embedded) +
    - Updated to the support humble and iron with the latest Yocto releases, GitHub - ros/meta-ros: OpenEmbedded Layers for ROS 1 and ROS 2
    - To update REP2000
    +
  - [Mirko] Security +
    - Last Security Working Group meeting happened on Nov. 14. The following points were discussed:
    - Progress on RustDDS, a memory-safe DDS implementation. Plan to have a presentation and discussion at a later meeting.
    - A vulnerability was reported to the FastDDS Github repo recently and shared on the group’s Matrix channel. We discussed the issue and supporting the reporter to get feedback from the project maintainers.
    +
  - [Orlov] Tooling +
    - Use enum values for offered_qos_profiles in code and string names in serialized metadata (rosbag2#1476)
    - Made progress on the following PRs: +
      +
    +
  +
+

1 post - 1 participant

Read full topic

ROS Discourse General: Upcoming API break in urdfdom

Mon, 20 Nov 2023 18:51:06 +0000

Hi all,

Please bear with me on a long post about urdfdom.

For those who don’t know, GitHub - ros/urdfdom: URDF parser houses the source code that both ROS 1 and ROS 2 use to parse and interact with URDF files.

Please also respond if you have any other questions or concerns about this change. Thank you.

2 posts - 2 participants

Read full topic

ROS Discourse General: Important Announcement, Patch Release 3 and New Packages for Iron Irwini 2023-11-20

Mon, 20 Nov 2023 16:37:22 +0000

We’re happy to announce a new Iron release

The latest sync brings 11 new packages and 118 updates to ROS 2 Iron Irwini. This sync was tagged as iron/2023-11-20 .

Package Updates for iron

Added Packages [11]:

ros-iron-event-camera-codecs: 1.2.2-1
ros-iron-event-camera-codecs-dbgsym: 1.2.2-1
ros-iron-event-camera-msgs: 1.2.5-1
ros-iron-event-camera-msgs-dbgsym: 1.2.5-1
ros-iron-leo: 2.0.0-1
ros-iron-leo-description: 2.0.0-1
ros-iron-leo-desktop: 2.0.0-1
ros-iron-leo-msgs: 2.0.0-1
ros-iron-leo-msgs-dbgsym: 2.0.0-1
ros-iron-leo-teleop: 2.0.0-1
ros-iron-leo-viz: 2.0.0-1

Updated Packages [118]:

ros-iron-controller-interface: 3.20.0-1 → 3.21.0-1
ros-iron-controller-interface-dbgsym: 3.20.0-1 → 3.21.0-1
ros-iron-controller-manager: 3.20.0-1 → 3.21.0-1
ros-iron-controller-manager-dbgsym: 3.20.0-1 → 3.21.0-1
ros-iron-controller-manager-msgs: 3.20.0-1 → 3.21.0-1
ros-iron-controller-manager-msgs-dbgsym: 3.20.0-1 → 3.21.0-1
ros-iron-fastrtps-cmake-module: 3.0.1-1 → 3.0.2-1
ros-iron-hardware-interface: 3.20.0-1 → 3.21.0-1
ros-iron-hardware-interface-dbgsym: 3.20.0-1 → 3.21.0-1
ros-iron-joint-limits: 3.20.0-1 → 3.21.0-1
ros-iron-libstatistics-collector: 1.5.1-2 → 1.5.2-1
ros-iron-libstatistics-collector-dbgsym: 1.5.1-2 → 1.5.2-1
ros-iron-mcap-vendor: 0.22.4-1 → 0.22.5-1
ros-iron-mcap-vendor-dbgsym: 0.22.4-1 → 0.22.5-1
ros-iron-rcl: 6.0.3-1 → 6.0.4-1
ros-iron-rcl-action: 6.0.3-1 → 6.0.4-1
ros-iron-rcl-action-dbgsym: 6.0.3-1 → 6.0.4-1
ros-iron-rcl-dbgsym: 6.0.3-1 → 6.0.4-1
ros-iron-rcl-lifecycle: 6.0.3-1 → 6.0.4-1
ros-iron-rcl-lifecycle-dbgsym: 6.0.3-1 → 6.0.4-1
ros-iron-rcl-yaml-param-parser: 6.0.3-1 → 6.0.4-1
ros-iron-rcl-yaml-param-parser-dbgsym: 6.0.3-1 → 6.0.4-1
ros-iron-rclcpp: 21.0.3-1 → 21.0.4-1
ros-iron-rclcpp-action: 21.0.3-1 → 21.0.4-1
ros-iron-rclcpp-action-dbgsym: 21.0.3-1 → 21.0.4-1
ros-iron-rclcpp-components: 21.0.3-1 → 21.0.4-1
ros-iron-rclcpp-components-dbgsym: 21.0.3-1 → 21.0.4-1
ros-iron-rclcpp-dbgsym: 21.0.3-1 → 21.0.4-1
ros-iron-rclcpp-lifecycle: 21.0.3-1 → 21.0.4-1
ros-iron-rclcpp-lifecycle-dbgsym: 21.0.3-1 → 21.0.4-1
ros-iron-rclpy: 4.1.3-1 → 4.1.4-1
ros-iron-rcpputils: 2.6.1-3 → 2.6.2-1
ros-iron-rcpputils-dbgsym: 2.6.1-3 → 2.6.2-1
ros-iron-rcutils: 6.2.1-2 → 6.2.2-2
ros-iron-rcutils-dbgsym: 6.2.1-2 → 6.2.2-2
ros-iron-rmw-fastrtps-cpp: 7.1.1-2 → 7.1.2-1
ros-iron-rmw-fastrtps-cpp-dbgsym: 7.1.1-2 → 7.1.2-1
ros-iron-rmw-fastrtps-dynamic-cpp: 7.1.1-2 → 7.1.2-1
ros-iron-rmw-fastrtps-dynamic-cpp-dbgsym: 7.1.1-2 → 7.1.2-1
ros-iron-rmw-fastrtps-shared-cpp: 7.1.1-2 → 7.1.2-1
ros-iron-rmw-fastrtps-shared-cpp-dbgsym: 7.1.1-2 → 7.1.2-1
ros-iron-ros2-control: 3.20.0-1 → 3.21.0-1
ros-iron-ros2-control-test-assets: 3.20.0-1 → 3.21.0-1
ros-iron-ros2action: 0.25.3-1 → 0.25.4-1
ros-iron-ros2bag: 0.22.4-1 → 0.22.5-1
ros-iron-ros2cli: 0.25.3-1 → 0.25.4-1
ros-iron-ros2cli-test-interfaces: 0.25.3-1 → 0.25.4-1
ros-iron-ros2cli-test-interfaces-dbgsym: 0.25.3-1 → 0.25.4-1
ros-iron-ros2component: 0.25.3-1 → 0.25.4-1
ros-iron-ros2controlcli: 3.20.0-1 → 3.21.0-1
ros-iron-ros2doctor: 0.25.3-1 → 0.25.4-1
ros-iron-ros2interface: 0.25.3-1 → 0.25.4-1
ros-iron-ros2lifecycle: 0.25.3-1 → 0.25.4-1
ros-iron-ros2lifecycle-test-fixtures: 0.25.3-1 → 0.25.4-1
ros-iron-ros2lifecycle-test-fixtures-dbgsym: 0.25.3-1 → 0.25.4-1
ros-iron-ros2multicast: 0.25.3-1 → 0.25.4-1
ros-iron-ros2node: 0.25.3-1 → 0.25.4-1
ros-iron-ros2param: 0.25.3-1 → 0.25.4-1
ros-iron-ros2pkg: 0.25.3-1 → 0.25.4-1
ros-iron-ros2run: 0.25.3-1 → 0.25.4-1
ros-iron-ros2service: 0.25.3-1 → 0.25.4-1
ros-iron-ros2topic: 0.25.3-1 → 0.25.4-1
ros-iron-rosbag2: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-compression: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-compression-dbgsym: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-compression-zstd: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-compression-zstd-dbgsym: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-cpp: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-cpp-dbgsym: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-examples-cpp: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-examples-cpp-dbgsym: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-examples-py: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-interfaces: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-interfaces-dbgsym: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-performance-benchmarking: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-performance-benchmarking-msgs: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-py: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-storage: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-storage-dbgsym: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-storage-default-plugins: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-storage-mcap: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-storage-mcap-dbgsym: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-storage-sqlite3: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-storage-sqlite3-dbgsym: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-test-common: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-test-msgdefs: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-test-msgdefs-dbgsym: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-tests: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-transport: 0.22.4-1 → 0.22.5-1
ros-iron-rosbag2-transport-dbgsym: 0.22.4-1 → 0.22.5-1
ros-iron-rosidl-dynamic-typesupport: 0.0.4-1 → 0.0.5-1
ros-iron-rosidl-dynamic-typesupport-dbgsym: 0.0.4-1 → 0.0.5-1
ros-iron-rosidl-typesupport-fastrtps-c: 3.0.1-1 → 3.0.2-1
ros-iron-rosidl-typesupport-fastrtps-c-dbgsym: 3.0.1-1 → 3.0.2-1
ros-iron-rosidl-typesupport-fastrtps-cpp: 3.0.1-1 → 3.0.2-1
ros-iron-rosidl-typesupport-fastrtps-cpp-dbgsym: 3.0.1-1 → 3.0.2-1
ros-iron-rqt-controller-manager: 3.20.0-1 → 3.21.0-1
ros-iron-rqt-reconfigure: 1.3.3-2 → 1.3.4-1
ros-iron-rviz-assimp-vendor: 12.4.4-1 → 12.4.5-1
ros-iron-rviz-common: 12.4.4-1 → 12.4.5-1
ros-iron-rviz-common-dbgsym: 12.4.4-1 → 12.4.5-1
ros-iron-rviz-default-plugins: 12.4.4-1 → 12.4.5-1
ros-iron-rviz-default-plugins-dbgsym: 12.4.4-1 → 12.4.5-1
ros-iron-rviz-ogre-vendor: 12.4.4-1 → 12.4.5-1
ros-iron-rviz-ogre-vendor-dbgsym: 12.4.4-1 → 12.4.5-1
ros-iron-rviz-rendering: 12.4.4-1 → 12.4.5-1
ros-iron-rviz-rendering-dbgsym: 12.4.4-1 → 12.4.5-1
ros-iron-rviz-rendering-tests: 12.4.4-1 → 12.4.5-1
ros-iron-rviz-visual-testing-framework: 12.4.4-1 → 12.4.5-1
ros-iron-rviz2: 12.4.4-1 → 12.4.5-1
ros-iron-rviz2-dbgsym: 12.4.4-1 → 12.4.5-1
ros-iron-shared-queues-vendor: 0.22.4-1 → 0.22.5-1
ros-iron-sqlite3-vendor: 0.22.4-1 → 0.22.5-1
ros-iron-transmission-interface: 3.20.0-1 → 3.21.0-1
ros-iron-transmission-interface-dbgsym: 3.20.0-1 → 3.21.0-1
ros-iron-twist-mux: 4.2.0-1 → 4.3.0-1
ros-iron-twist-mux-dbgsym: 4.2.0-1 → 4.3.0-1
ros-iron-zstd-vendor: 0.22.4-1 → 0.22.5-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:

+
Note: The list of contributors is incomplete as there may be an issue with the tool used to generate this report.
+

Alejandro Hernandez Cordero
Audrow Nash
Bence Magyar
Bernd Pfrommer
Brandon Ong
Dharini Dutia
Fictionlab
Foxglove
Geoffrey Biggs
Ivan Paunovic
Michael Orlov
ROS Tooling Working Group
Shane Loretz
geoff

1 post - 1 participant

Read full topic

ROS Discourse General: Again... Snapshot repo GPG key expired

Mon, 20 Nov 2023 09:21:04 +0000

Since yesterday, there is a problem running Melodic Industrial CI:

$ sudo apt-get update -qq
+  W: GPG error: http://snapshots.ros.org/melodic/final/ubuntu bionic InRelease: The following signatures were invalid: EXPKEYSIG AD19BAB3CBF125EA ROS Snapshot builder <rosbuild@ros.org>
+  E: The repository 'http://snapshots.ros.org/melodic/final/ubuntu bionic InRelease' is not signed.
+

I know Melodic is EOL, but still, it should be usable from the snapshot repo, shouldnâ€™t it?

There is already another report on RSE, but I think this is a better place to discuss such problem.

8 posts - 6 participants

Read full topic

ROS Discourse General: Simple_launch approaching event handling

Sat, 18 Nov 2023 20:27:42 +0000

Hi,

A few posts on discourse and stackexchange have already highlighted the difficulty of writing Python launch files for ROS 2.

In particular, the syntax may be a bit verbose and the arguments somehow hard to handle as they are not raw Python types.

The current release allows easy handling of:

namespaces
conditions
finding a file inside a package (thanks os.walk)
container and composable nodes
spawning a robot_state_publisher from a xacro file with arguments, even if all of those come from launch arguments
uploading models to Gazebo
bridging topics with Gazebo (ros_gz_bridge wrapper)
setting use_sim_time for all nodes in the launch file
using the OpaqueFunction idiom (my favorite) without seeing perform or context everywhere, in case you really need raw Python types

6 posts - 4 participants

Read full topic

ROS Discourse General: ROS News for the Week of November 12th, 2023

Fri, 17 Nov 2023 21:50:59 +0000

ROS News for the Week of November 12th, 2023

What's New and Upcoming in Open Source Robotics at ROSCon '23

Check out this fantastic PX4 and ROSCon recap video from our friends at PX4

+
+

+Our next Gazebo Community Meeting will include a report from the IIT Madras Aritra maritime robotics team.

+
+

+Check out this new ROS Noetic package that implements a Segment Anything Model as a ROS Service.

+
+

+All good things must come to an end. Audrow has stepped down from Sense, Think, Act.

+
+

Events

News

ROS

6 posts - 3 participants

Read full topic

ROS Discourse General: ROS Deployment Meeting (#1?)

Thu, 16 Nov 2023 19:18:23 +0000

Hi,

for those who are interested in how to manage and deploy the ROS application?, letâ€™s have a follow-up meeting as we promised at ROSCon 2023 BoF

revised from Automatic Deployment of ROS2 Based System to remote devices: Dual Copy or Containers?, besides we had 44 people registered to BoF: Deployment of ROS 2 to remote devices at ROSCon 2023.

with that, i think there are many interests about how to deploy and manage robot application. Please feel free to join the meeting

Date / Place

2023-12-04T17:00:00Z UTC

+ + +

(*) I am not able to do recording at this time.

Agenda

Really appreciate @ciandonovan , he is willing to share the experience and take the effort for ROS community.

ROSCon 2023 ROS with Kubernetes/KubeEdge Talk Follow-Up and QA/Discussion (@tomoyafujita ) 15-20mins +
- GitHub - fujitatomoya/ros_k8s: Kuberenetes / ROS&ROS2 Cluster Samples Issues / Explanation
+
ROS deployment control with podman and systemd. (@ciandonovan ) 25mins including QA/Discussion
Open Discussion (should we have regular meeting? other topics? problem sharing?) 5mins

How to join?

No registration is required, you can just jump in the meeting
Or if you do not want to miss, DM @tomoyafujita / tomoya.fujita825@gmail.com to get the meeting invitation.

Reference

+ + +

thanks,

14 posts - 8 participants

Read full topic

ROS Discourse General: New Packages for Noetic 2023-11-15

Thu, 16 Nov 2023 00:47:59 +0000

We’re happy to announce 5 new packages and 51 updates are now available in ROS Noetic. This sync was tagged as noetic/2023-11-15.

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

Package Updates for ROS Noetic

Added Packages [5]:

ros-noetic-clearpath-onav-api-examples: 0.0.3-1
ros-noetic-clearpath-onav-api-examples-lib: 0.0.3-1
ros-noetic-clearpath-onav-examples: 0.0.3-1
ros-noetic-pr2eus-moveit: 0.3.15-3
ros-noetic-sick-scan-xd: 3.0.3-1

Updated Packages [51]:

ros-noetic-clearpath-configuration-msgs: 0.9.4-1 → 0.9.5-1
ros-noetic-clearpath-control-msgs: 0.9.4-1 → 0.9.5-1
ros-noetic-clearpath-dock-msgs: 0.9.4-1 → 0.9.5-1
ros-noetic-clearpath-localization-msgs: 0.9.4-1 → 0.9.5-1
ros-noetic-clearpath-mission-manager-msgs: 0.9.4-1 → 0.9.5-1
ros-noetic-clearpath-mission-scheduler-msgs: 0.9.4-1 → 0.9.5-1
ros-noetic-clearpath-msgs: 0.9.4-1 → 0.9.5-1
ros-noetic-clearpath-navigation-msgs: 0.9.4-1 → 0.9.5-1
ros-noetic-clearpath-platform-msgs: 0.9.4-1 → 0.9.5-1
ros-noetic-clearpath-safety-msgs: 0.9.4-1 → 0.9.5-1
ros-noetic-combined-robot-hw: 0.19.6-1 → 0.20.0-1
ros-noetic-combined-robot-hw-tests: 0.19.6-1 → 0.20.0-1
ros-noetic-controller-interface: 0.19.6-1 → 0.20.0-1
ros-noetic-controller-manager: 0.19.6-1 → 0.20.0-1
ros-noetic-controller-manager-msgs: 0.19.6-1 → 0.20.0-1
ros-noetic-controller-manager-tests: 0.19.6-1 → 0.20.0-1
ros-noetic-cpr-onav-description: 0.1.9-1 → 0.1.10-1
ros-noetic-cras-cpp-common: 2.3.3-1 → 2.3.4-1
ros-noetic-cras-docs-common: 2.3.3-1 → 2.3.4-1
ros-noetic-cras-py-common: 2.3.3-1 → 2.3.4-1
ros-noetic-cras-topic-tools: 2.3.3-1 → 2.3.4-1
ros-noetic-foxglove-bridge: 0.7.2-1 → 0.7.3-1
ros-noetic-hardware-interface: 0.19.6-1 → 0.20.0-1
ros-noetic-image-transport-codecs: 2.3.3-1 → 2.3.4-1
ros-noetic-joint-limits-interface: 0.19.6-1 → 0.20.0-1
ros-noetic-jsk-pr2eus: 0.3.15-1 → 0.3.15-3
ros-noetic-leo: 2.2.0-1 → 2.3.0-1
ros-noetic-leo-bringup: 2.3.0-1 → 2.4.0-1
ros-noetic-leo-description: 2.2.0-1 → 2.3.0-1
ros-noetic-leo-desktop: 0.2.3-1 → 0.3.0-1
ros-noetic-leo-fw: 2.3.0-1 → 2.4.0-1
ros-noetic-leo-msgs: 2.2.0-1 → 2.3.0-1
ros-noetic-leo-robot: 2.3.0-1 → 2.4.0-1
ros-noetic-leo-teleop: 2.2.0-1 → 2.3.0-1
ros-noetic-leo-viz: 0.2.3-1 → 0.3.0-1
ros-noetic-marti-can-msgs: 0.12.1-1 → 0.12.2-1
ros-noetic-marti-common-msgs: 0.12.1-1 → 0.12.2-1
ros-noetic-marti-dbw-msgs: 0.12.1-1 → 0.12.2-1
ros-noetic-marti-introspection-msgs: 0.12.1-1 → 0.12.2-1
ros-noetic-marti-nav-msgs: 0.12.1-1 → 0.12.2-1
ros-noetic-marti-perception-msgs: 0.12.1-1 → 0.12.2-1
ros-noetic-marti-sensor-msgs: 0.12.1-1 → 0.12.2-1
ros-noetic-marti-status-msgs: 0.12.1-1 → 0.12.2-1
ros-noetic-marti-visualization-msgs: 0.12.1-1 → 0.12.2-1
ros-noetic-mrpt2: 2.11.1-1 → 2.11.2-1
ros-noetic-openni2-camera: 1.6.0-1 → 1.6.1-1
ros-noetic-openni2-launch: 1.6.0-1 → 1.6.1-1
ros-noetic-pr2eus: 0.3.15-1 → 0.3.15-3
ros-noetic-ros-control: 0.19.6-1 → 0.20.0-1
ros-noetic-rqt-controller-manager: 0.19.6-1 → 0.20.0-1
ros-noetic-transmission-interface: 0.19.6-1 → 0.20.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:

Bence Magyar
Chris Iverach-Brereton
Fictionlab
Isaac I. Y. Saito
Jason Higgins
John Hurliman
Jose Mastrangelo
Jose-Luis Blanco-Claraco
José Mastrangelo
Kei Okada
Martin Pecka
Michael Ferguson
Roni Kreinin
Southwest Research Institute
YoheiKakiuchi
rostest

1 post - 1 participant

Read full topic

ROS Discourse General: Proposal for ROS 2 Production Working Group

Wed, 15 Nov 2023 18:05:14 +0000

Call for Participation:
+If you are interested in updates or participating in working group meetings, please fill out the following google form survey:

+ +

4 posts - 2 participants

Read full topic

ROS Discourse General: Audrow Nash to step down from hosting the Sense, Think, Act podcast

Tue, 14 Nov 2023 17:26:08 +0000

Hi Everyone,

5 posts - 5 participants

Read full topic

ROS Discourse General: ROS 2 Router for Remote Robotics and Topic Filtering

Tue, 14 Nov 2023 14:44:23 +0000

Hi everyone!

There’s no need to change your DDS settings. Simply run our Docker image alongside your existing ROS 2 application, regardless of whether it’s running on a host or inside Docker containers.

Our Docker image is based on the newest release of eProsima DDSRouter and it automatically integrates with the Husarnet VPN client via its HTTP API.

1 post - 1 participant

Read full topic

ROS Discourse General: ROS News for the Week of November 6th, 2023

Fri, 10 Nov 2023 21:25:08 +0000

ROS News for November 5th, 2023

+ROSCon 2023 Videos and Slides Now Available! Our friends at PX4 have their event recaps up as well. Meanwhile, Odense Denmark is already planning ROSCon 2024.

+
+

+We’ve got a ROS Meetup Singapore at the end of the month. This event will focus on robot dev ops!
+

+
+

Events

News

Papers (Mainly CoRL, but also others)

ROS

+
+

Got a minute? Why not help out some other robot developers?

5 posts - 3 participants

Read full topic

ROS Discourse General: ⚜️ ROSCon 2023 Videos and Slides Now Available!

Thu, 09 Nov 2023 17:38:33 +0000

ROSCon 2023 Videos and Slides Now Available

Hi Everyone,

Along with the videos and slides we’ve put together a quick wrap up post on openrobotics.org. If you want to see some of our professional photos from the event please take a look.

ROSCon 2023 Talks

10 posts - 4 participants

Read full topic

ROS Discourse General: CoppeliaSim V4.6 Released: enhanced Python integration

Wed, 08 Nov 2023 18:28:55 +0000

Robotics simulator: enhanced Python integration in CoppeliaSim

+I’m happy to share the latest update of CoppeliaSim: version 4.6 is out, with enhanced Python integration:

Effortless connection to CoppeliaSim from any Python script
Access to all of CoppeliaSim’s objects and API
CoppeliaSim library incorporation into a Python script
Efficiently scheduling, initiation, and execution of multiple embedded Python scripts

For more information, please visit https://www.coppeliarobotics.com

CoppeliaSim Edu is free to download and works out-of-the-box, no registration required

Cheers,
+Marc

1 post - 1 participant

Read full topic

ROS Discourse General: Update from the Deliberation Working Group

Wed, 08 Nov 2023 17:15:48 +0000

The next meeting will happen on 4 December, and I am looking forward to @grey presenting aspects of Deliberation in OpenRMF

1 post - 1 participant

Read full topic

ROS Discourse General: New Packages for Iron Irwini 2023-11-08

Wed, 08 Nov 2023 02:09:13 +0000

We’re happy to announce 2 new packages and 170 updates are now available in ROS 2 Iron Irwini . This sync was tagged as iron/2023-11-08 .

Package Updates for iron

Added Packages [2]:

ros-iron-interactive-marker-twist-server: 2.1.0-1
ros-iron-interactive-marker-twist-server-dbgsym: 2.1.0-1

Updated Packages [170]:

ros-iron-ackermann-steering-controller: 3.16.0-1 → 3.17.0-1
ros-iron-ackermann-steering-controller-dbgsym: 3.16.0-1 → 3.17.0-1
ros-iron-admittance-controller: 3.16.0-1 → 3.17.0-1
ros-iron-admittance-controller-dbgsym: 3.16.0-1 → 3.17.0-1
ros-iron-bicycle-steering-controller: 3.16.0-1 → 3.17.0-1
ros-iron-bicycle-steering-controller-dbgsym: 3.16.0-1 → 3.17.0-1
ros-iron-catch-ros2: 0.1.0-1 → 0.2.0-1
ros-iron-catch-ros2-dbgsym: 0.1.0-1 → 0.2.0-1
ros-iron-controller-interface: 3.19.1-1 → 3.20.0-1
ros-iron-controller-interface-dbgsym: 3.19.1-1 → 3.20.0-1
ros-iron-controller-manager: 3.19.1-1 → 3.20.0-1
ros-iron-controller-manager-dbgsym: 3.19.1-1 → 3.20.0-1
ros-iron-controller-manager-msgs: 3.19.1-1 → 3.20.0-1
ros-iron-controller-manager-msgs-dbgsym: 3.19.1-1 → 3.20.0-1
ros-iron-depthai-bridge: 2.8.1-1 → 2.8.2-1
ros-iron-depthai-bridge-dbgsym: 2.8.1-1 → 2.8.2-1
ros-iron-depthai-descriptions: 2.8.1-1 → 2.8.2-1
ros-iron-depthai-examples: 2.8.1-1 → 2.8.2-1
ros-iron-depthai-examples-dbgsym: 2.8.1-1 → 2.8.2-1
ros-iron-depthai-filters: 2.8.1-1 → 2.8.2-1
ros-iron-depthai-filters-dbgsym: 2.8.1-1 → 2.8.2-1
ros-iron-depthai-ros: 2.8.1-1 → 2.8.2-1
ros-iron-depthai-ros-driver: 2.8.1-1 → 2.8.2-1
ros-iron-depthai-ros-driver-dbgsym: 2.8.1-1 → 2.8.2-1
ros-iron-depthai-ros-msgs: 2.8.1-1 → 2.8.2-1
ros-iron-depthai-ros-msgs-dbgsym: 2.8.1-1 → 2.8.2-1
ros-iron-diff-drive-controller: 3.16.0-1 → 3.17.0-1
ros-iron-diff-drive-controller-dbgsym: 3.16.0-1 → 3.17.0-1
ros-iron-effort-controllers: 3.16.0-1 → 3.17.0-1
ros-iron-effort-controllers-dbgsym: 3.16.0-1 → 3.17.0-1
ros-iron-force-torque-sensor-broadcaster: 3.16.0-1 → 3.17.0-1
ros-iron-force-torque-sensor-broadcaster-dbgsym: 3.16.0-1 → 3.17.0-1
ros-iron-forward-command-controller: 3.16.0-1 → 3.17.0-1
ros-iron-forward-command-controller-dbgsym: 3.16.0-1 → 3.17.0-1
ros-iron-foxglove-bridge: 0.7.2-1 → 0.7.3-1
ros-iron-foxglove-bridge-dbgsym: 0.7.2-1 → 0.7.3-1
ros-iron-gripper-controllers: 3.16.0-1 → 3.17.0-1
ros-iron-gripper-controllers-dbgsym: 3.16.0-1 → 3.17.0-1
ros-iron-hardware-interface: 3.19.1-1 → 3.20.0-1
ros-iron-hardware-interface-dbgsym: 3.19.1-1 → 3.20.0-1
ros-iron-imu-sensor-broadcaster: 3.16.0-1 → 3.17.0-1
ros-iron-imu-sensor-broadcaster-dbgsym: 3.16.0-1 → 3.17.0-1
ros-iron-joint-limits: 3.19.1-1 → 3.20.0-1
ros-iron-joint-state-broadcaster: 3.16.0-1 → 3.17.0-1
ros-iron-joint-state-broadcaster-dbgsym: 3.16.0-1 → 3.17.0-1
ros-iron-joint-trajectory-controller: 3.16.0-1 → 3.17.0-1
ros-iron-joint-trajectory-controller-dbgsym: 3.16.0-1 → 3.17.0-1
ros-iron-joy: 3.2.0-1 → 3.3.0-1
ros-iron-joy-dbgsym: 3.2.0-1 → 3.3.0-1
ros-iron-joy-linux: 3.2.0-1 → 3.3.0-1
ros-iron-joy-linux-dbgsym: 3.2.0-1 → 3.3.0-1
ros-iron-joy-teleop: 1.4.0-2 → 1.5.0-1
ros-iron-key-teleop: 1.4.0-2 → 1.5.0-1
ros-iron-marti-can-msgs: 1.4.1-1 → 1.5.2-1
ros-iron-marti-can-msgs-dbgsym: 1.4.1-1 → 1.5.2-1
ros-iron-marti-common-msgs: 1.4.1-1 → 1.5.2-1
ros-iron-marti-common-msgs-dbgsym: 1.4.1-1 → 1.5.2-1
ros-iron-marti-dbw-msgs: 1.4.1-1 → 1.5.2-1
ros-iron-marti-dbw-msgs-dbgsym: 1.4.1-1 → 1.5.2-1
ros-iron-marti-introspection-msgs: 1.4.1-1 → 1.5.2-1
ros-iron-marti-introspection-msgs-dbgsym: 1.4.1-1 → 1.5.2-1
ros-iron-marti-nav-msgs: 1.4.1-1 → 1.5.2-1
ros-iron-marti-nav-msgs-dbgsym: 1.4.1-1 → 1.5.2-1
ros-iron-marti-perception-msgs: 1.4.1-1 → 1.5.2-1
ros-iron-marti-perception-msgs-dbgsym: 1.4.1-1 → 1.5.2-1
ros-iron-marti-sensor-msgs: 1.4.1-1 → 1.5.2-1
ros-iron-marti-sensor-msgs-dbgsym: 1.4.1-1 → 1.5.2-1
ros-iron-marti-status-msgs: 1.4.1-1 → 1.5.2-1
ros-iron-marti-status-msgs-dbgsym: 1.4.1-1 → 1.5.2-1
ros-iron-marti-visualization-msgs: 1.4.1-1 → 1.5.2-1
ros-iron-marti-visualization-msgs-dbgsym: 1.4.1-1 → 1.5.2-1
ros-iron-mcap-vendor: 0.22.3-1 → 0.22.4-1
ros-iron-mcap-vendor-dbgsym: 0.22.3-1 → 0.22.4-1
ros-iron-mouse-teleop: 1.4.0-2 → 1.5.0-1
ros-iron-mrpt2: 2.10.2-1 → 2.11.2-1
ros-iron-mrpt2-dbgsym: 2.10.2-1 → 2.11.2-1
ros-iron-ntrip-client-node: 0.5.1-1 → 0.5.2-1
ros-iron-ntrip-client-node-dbgsym: 0.5.1-1 → 0.5.2-1
ros-iron-position-controllers: 3.16.0-1 → 3.17.0-1
ros-iron-position-controllers-dbgsym: 3.16.0-1 → 3.17.0-1
ros-iron-range-sensor-broadcaster: 3.16.0-1 → 3.17.0-1
ros-iron-range-sensor-broadcaster-dbgsym: 3.16.0-1 → 3.17.0-1
ros-iron-ros-gz: 0.245.0-1 → 0.247.0-1
ros-iron-ros-gz-bridge: 0.245.0-1 → 0.247.0-1
ros-iron-ros-gz-bridge-dbgsym: 0.245.0-1 → 0.247.0-1
ros-iron-ros-gz-image: 0.245.0-1 → 0.247.0-1
ros-iron-ros-gz-image-dbgsym: 0.245.0-1 → 0.247.0-1
ros-iron-ros-gz-interfaces: 0.245.0-1 → 0.247.0-1
ros-iron-ros-gz-interfaces-dbgsym: 0.245.0-1 → 0.247.0-1
ros-iron-ros-gz-sim: 0.245.0-1 → 0.247.0-1
ros-iron-ros-gz-sim-dbgsym: 0.245.0-1 → 0.247.0-1
ros-iron-ros-gz-sim-demos: 0.245.0-1 → 0.247.0-1
ros-iron-ros-ign: 0.245.0-1 → 0.247.0-1
ros-iron-ros-ign-bridge: 0.245.0-1 → 0.247.0-1
ros-iron-ros-ign-bridge-dbgsym: 0.245.0-1 → 0.247.0-1
ros-iron-ros-ign-gazebo: 0.245.0-1 → 0.247.0-1
ros-iron-ros-ign-gazebo-dbgsym: 0.245.0-1 → 0.247.0-1
ros-iron-ros-ign-gazebo-demos: 0.245.0-1 → 0.247.0-1
ros-iron-ros-ign-image: 0.245.0-1 → 0.247.0-1
ros-iron-ros-ign-image-dbgsym: 0.245.0-1 → 0.247.0-1
ros-iron-ros-ign-interfaces: 0.245.0-1 → 0.247.0-1
ros-iron-ros-ign-interfaces-dbgsym: 0.245.0-1 → 0.247.0-1
ros-iron-ros2-control: 3.19.1-1 → 3.20.0-1
ros-iron-ros2-control-test-assets: 3.19.1-1 → 3.20.0-1
ros-iron-ros2-controllers: 3.16.0-1 → 3.17.0-1
ros-iron-ros2-controllers-test-nodes: 3.16.0-1 → 3.17.0-1
ros-iron-ros2bag: 0.22.3-1 → 0.22.4-1
ros-iron-ros2controlcli: 3.19.1-1 → 3.20.0-1
ros-iron-rosbag2: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-compression: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-compression-dbgsym: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-compression-zstd: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-compression-zstd-dbgsym: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-cpp: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-cpp-dbgsym: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-examples-cpp: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-examples-cpp-dbgsym: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-examples-py: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-interfaces: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-interfaces-dbgsym: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-performance-benchmarking: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-performance-benchmarking-msgs: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-py: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-storage: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-storage-dbgsym: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-storage-default-plugins: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-storage-mcap: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-storage-mcap-dbgsym: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-storage-sqlite3: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-storage-sqlite3-dbgsym: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-test-common: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-test-msgdefs: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-test-msgdefs-dbgsym: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-tests: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-transport: 0.22.3-1 → 0.22.4-1
ros-iron-rosbag2-transport-dbgsym: 0.22.3-1 → 0.22.4-1
ros-iron-rqt-controller-manager: 3.19.1-1 → 3.20.0-1
ros-iron-rqt-joint-trajectory-controller: 3.16.0-1 → 3.17.0-1
ros-iron-sdl2-vendor: 3.2.0-1 → 3.3.0-1
ros-iron-shared-queues-vendor: 0.22.3-1 → 0.22.4-1
ros-iron-spacenav: 3.2.0-1 → 3.3.0-1
ros-iron-spacenav-dbgsym: 3.2.0-1 → 3.3.0-1
ros-iron-sqlite3-vendor: 0.22.3-1 → 0.22.4-1
ros-iron-steering-controllers-library: 3.16.0-1 → 3.17.0-1
ros-iron-steering-controllers-library-dbgsym: 3.16.0-1 → 3.17.0-1
ros-iron-teleop-tools: 1.4.0-2 → 1.5.0-1
ros-iron-teleop-tools-msgs: 1.4.0-2 → 1.5.0-1
ros-iron-teleop-tools-msgs-dbgsym: 1.4.0-2 → 1.5.0-1
ros-iron-transmission-interface: 3.19.1-1 → 3.20.0-1
ros-iron-transmission-interface-dbgsym: 3.19.1-1 → 3.20.0-1
ros-iron-tricycle-controller: 3.16.0-1 → 3.17.0-1
ros-iron-tricycle-controller-dbgsym: 3.16.0-1 → 3.17.0-1
ros-iron-tricycle-steering-controller: 3.16.0-1 → 3.17.0-1
ros-iron-tricycle-steering-controller-dbgsym: 3.16.0-1 → 3.17.0-1
ros-iron-ublox-dgnss: 0.5.1-1 → 0.5.2-1
ros-iron-ublox-dgnss-node: 0.5.1-1 → 0.5.2-1
ros-iron-ublox-dgnss-node-dbgsym: 0.5.1-1 → 0.5.2-1
ros-iron-ublox-nav-sat-fix-hp-node: 0.5.1-1 → 0.5.2-1
ros-iron-ublox-nav-sat-fix-hp-node-dbgsym: 0.5.1-1 → 0.5.2-1
ros-iron-ublox-ubx-interfaces: 0.5.1-1 → 0.5.2-1
ros-iron-ublox-ubx-interfaces-dbgsym: 0.5.1-1 → 0.5.2-1
ros-iron-ublox-ubx-msgs: 0.5.1-1 → 0.5.2-1
ros-iron-ublox-ubx-msgs-dbgsym: 0.5.1-1 → 0.5.2-1
ros-iron-velocity-controllers: 3.16.0-1 → 3.17.0-1
ros-iron-velocity-controllers-dbgsym: 3.16.0-1 → 3.17.0-1
ros-iron-wiimote: 3.2.0-1 → 3.3.0-1
ros-iron-wiimote-dbgsym: 3.2.0-1 → 3.3.0-1
ros-iron-wiimote-msgs: 3.2.0-1 → 3.3.0-1
ros-iron-wiimote-msgs-dbgsym: 3.2.0-1 → 3.3.0-1
ros-iron-zstd-vendor: 0.22.3-1 → 0.22.4-1

Removed Packages [0]:

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

Adam Serafin
Alejandro Hernandez
Bence Magyar
Brandon Ong
Chris Lalancette
Denis Štogl
Enrique Fernandez
Foxglove
Geoff Sokoll
John Hurliman
Jonathan Bohren
Jose-Luis Blanco-Claraco
Louise Poubel
Michael Orlov
Mike Purvis
Nick Hortovanyi
Nick Morales
ROS Tooling Working Group
Sachin Guruswamy
Southwest Research Institute
geoff
sachin

1 post - 1 participant

Read full topic

ROS Discourse General: BT-Studio 0.2 available (with video)

Mon, 06 Nov 2023 19:47:12 +0000

Hi folks,

we have just published today the 0.2 release of our BT Studio. This release introduces a web-based visual IDE that enhances the development of ROS 2 applications with Behavior Trees.

[BT Studio] Version 0.2 released: showcasing the Web IDE.

+ + + +

In addition, some clarifications regarding the last Deliberation Working group meeting (23-10-02) @ct2034 @fmrico :

+
JdeRobot is a non profit association for developing open source software in robotics and AI. We started informally in 2003 and finally registered formally in 2018. JdeRobot is not a “false spin off from URJC”, despite it was born at that university. We have contributors from several Spanish universities (URJC, UPM, UCM, UJI…) and from several countries. Since 2015 we have participated 8 times at Google Summer of Code developing open source robotics software projects.
+
+
We do not “hate ROS”. We developed an ICE based robotics middleware until 2018, then we changed our approach, deprecated such software code base and widely adopted ROS. Since then all our software is ROS friendly. Developing an alternative middleware does not mean to hate other available ones :-).
+
+
We are currently working on integrating BehaviorTrees in our robot programming website, named Unibotics, and continuously improving it, both in reliability and in new functionalities. Unibotics is fully ROS based, and available online for the robotics community for free. Our BT functionality currently includes a translator to Python files and a visual editor. It will soon (0.3 release) include the dockerized execution of BT robotics applications.
+

Hope it helps,

1 post - 1 participant

Read full topic

ROS Discourse General: Introducing launch-generator: A simplified launch description creation tool for ROS 2

Sun, 05 Nov 2023 11:01:41 +0000

pip install launch-generator

I hope to alleviate the fatigue of writing launch files in Python by using this library.

1 post - 1 participant

Read full topic

ROS Discourse General: ROS News for the Week of October 30th, 2023

Fri, 03 Nov 2023 20:00:45 +0000

ROS News for the Week of October 30th, 2023

+
+

The Future of Robotics - What do the experts think? (ROSCon '23)

+
+

Events

News

ROS

ROS Questions

Please take a moment to help out your fellow developers by answering a few questions on robotics.stackexchange.com

1 post - 1 participant

Read full topic

ROS Discourse General: Interviews from ROSCon '23

Thu, 02 Nov 2023 20:58:19 +0000

Hi everyone, it was fantastic to get along to ROSCon (and the US) for the first time and meet so many of you!

Itâ€™s a bit of a departure from my usual format and I think I have some room to grow, but I hope you enjoy it nonetheless

P.S. Apologies for the clickbait title

The Future of Robotics - What do the experts think? (ROSCon '23)

+ +

Thanks especially to everyone who was involved in organising this great week!

1 post - 1 participant

Read full topic

ROS Discourse General: Join the ROS Ambassador Program

Thu, 02 Nov 2023 19:21:54 +0000

Dear ROS community,
+We are thrilled to announce the re-launch of the ROS Ambassadors Program, an initiative
+dedicated to spreading ROS knowledge globally.

Our Mission: Learn, Teach, and Empower with ROS

Our goal is simple: to learn and teach ROS, empowering individuals to share this knowledge
+with the world.

ROS Ambassador Benefits

As a ROS Ambassador, you will enjoy:

● ROS Ambassador Pack:
+Progress through different levels within the program and unlock exciting rewards.
+Each new stage comes with corresponding gifts sent directly to you.

How It Works?

The ROS Ambassadors program is open to beginners with limited or no prior ROS knowledge.

How To Apply?

You need to send your profile to ambassadors@theconstructsim.com.
+Including the following information:

Programming Proficiency

C++ (from 0 to 5)
Python (from 0 to 5)

Current ROS level

Basics of ROS (from 0 to 5)
ROS Navigation (from 0 to 5)
MoveIt (from 0 to 5)
Gazebo (from 0 to 5)
ROS Control(from 0 to 5)

Nationality and Native Language
Educational Background
Current educational or professional status (studying or working)

For questions or more information, please check out here:

+ +

Join us in this exciting journey of knowledge and discovery. Become a ROS Ambassador and
+contribute to the growth of the ROS community, supported by The Construct.

Warm regards,
+The Construct | theconstruct.ai
+Where Your Robotics Career Happens

2 posts - 1 participant

Read full topic

ROS Discourse General: Franka Emika <-> Agile Robots

Thu, 02 Nov 2023 15:32:02 +0000

For the information of those concerned about Franka Emika financial problem

Both companies are seated in Munich, Bavaria, Germany and have a DLR-background.

Correct wording should be found soon on the corresponding news website of the companies:

4 posts - 3 participants

Read full topic

ROS Discourse General: Nav2 User Requests Survey Results

Tue, 31 Oct 2023 17:47:36 +0000

Howdy yal,

Its yur rip-rawrin’ rootin’-tootin’ gun-slingin’ navigator in here parts I’m going as a cowboy for halloween today !

I wanted to highlight the newest post on Open Navigation’s blog going over the results of the 2023 Nav2 / ROS 2 User Survey I announced in conjunction with ROSCon in the discourse post below:

+ + +

You can check out the results:

+ + +

Dexory

+ + +

Stereolabs

+ + +

Polymath

+ + +

Yeeeeee Hawwww

Marshall S. Macenski

1 post - 1 participant

Read full topic

ROS Discourse General: Open Sourcing NVIDIA Isaac Sim URDF and MJCF Importer Extensions

Mon, 30 Oct 2023 22:26:29 +0000

We are releasing the source code of the URDF and MJCF importer extensions for Isaac Sim, part of NVIDIA Omniverse.

After building the extension, use the steps in this documentation to try out the URDF importer extension.

You can use the extension in Isaac Sim (or any other Omniverse application) using the following steps:

Go to Window->Extensions
Go to Settings (Hamburger menu on the right)
To Extension Search Paths section, add new extension folder to point to this downloaded repo root/_build/platform/release/exts (no slash at the end)
Check the extensions 3rd party (second tab on the left)
Enable omni.importer.urdf extension

See also GitHub - NVIDIA-Omniverse/kit-extension-template-cpp: Omniverse Kit C++ Extension Template for more information on how to develop a C++ extension for Omniverse from scratch.

Similarly, the MJCF Importer Extension is available at GitHub - NVIDIA-Omniverse/mjcf-importer-extension: Omniverse MJCF Importer Extension.

6 posts - 3 participants

Read full topic

ROS Discourse General: ROS News for the Week of October 23rd, 2023

Sat, 28 Oct 2023 00:27:17 +0000

ROS News for October 22nd, 2023

Now is a great time to start thinking about joining us in Odense in 2024.

+
+

+ROS 2 TSC Community Representative Election results are in! Welcome your new reps @DLu and @smac!
+

+Make sure to purchase your ROSCon Germany tickets asap! – Also the ROSCon India CFP is now open!

+
+

+Join us for a very spooky Gazebo Community Meeting w/ O3DE on 2023-10-31

+
+

Events

News

ROS 2 TSC Community Representative Election Results
Cruise has had a crazy couple weeks! Two weeks ago Cruise announced plans to expand to Houston. The following week Cruise, GM, and Honda announced plans to enter the Japanese market. Just hours later Cruise’s taxi permit was yanked in SF for safety concerns.
Open Hardware Creators in Academia – Over the past year and a half I’ve been helping the Open Source Hardware Association work on a grant to study the role of open hardware in academic research. That work just got released.
Reflections on ROS in Asia
Nvidia brings generative AI compatibility to robotics platforms – More - More
Humanoid robots face a major test with Amazon’s Digit pilots
These 27 Robotics Companies are Hiring
Amazon begins testing Agility’s Digit robot for warehouse work
Auterion Launches Skynode X, Its Next-Generation All-in-One Brain for Autonomous Drones and More
Building a full-stack robotics company in the age of large AI models
Computer Vision for Agriculture
New AMR safety standard available with release of ANSI/A3 R15.08-2
ROS 2 Laser-Based Weeding
Present and Future of SLAM in Extreme Environments: The DARPA SubT Challenge
“TurtleBot” for PX4 by ModalAI
OSHWA on OpenCV Livestream
Advanced Simulation and Perception Tools on NVIDIA Isaac Platform
ROS + Clearpath Robots for Landmine Detection
Delivery Robots used in a Bomb Threat – More
RoMe: Towards Large Scale Road Surface Reconstruction via Mesh Representation
V2V4Real: A large-scale real-world dataset for Vehicle-to-Vehicle Cooperative Perception
Framework for LiDAR-based moving object segmentation
GNSS Measurement Simulator (handy)
PC-NeRF: Parent-Child Neural Radiance Fields under Partial Sensor Data Loss in Autonomous Driving Environments
Instant-angelo: Build high-fidelity Digital Twin within 20 Minutes!
Japanese Traffic Light Detection Model
Awesome list for autonomous driving
What’s Next for Clearpath Robotics?
The South Pole has Roombas (ROS on all 7 continents!!!)

ROS

ROS Questions

Take a moment to help out your fellow developers on Robotics Stack Exchange.

1 post - 1 participant

Read full topic