Planet ROS
Planet ROS - http://planet.ros.org
Planet ROS - http://planet.ros.org http://planet.ros.org
ROS Discourse General: ROS on Windows: Foxy Release v20201211.0.0.2012290002
The Microsoft Azure Edge Robotics team is happy to announce the Foxy Release v20201211.0.0.2012290002 for Windows developers.
As usual, you can install it by the following steps:
mkdir c:\opt\chocolatey
set ChocolateyInstall=c:\opt\chocolatey
choco source add -n=ros-win -s="https://aka.ms/ros/public" --priority=1
choco upgrade ros-foxy-desktop -y --execution-timeout=0
Some highlights of this release:
- Based on the Foxy release sync 2020-12-11.
- Enabled composition:
- Libraries and Python runtime:
- Boost 1.73.0
- CMake 3.18.2
- EmPY 3.3.4
- Gazebo 10.2.0
- OGRE 1.12.7
- OpenCV 4.3.0
- OpenSSL 1.1.1g
- PCL 1.9.1
- Poco 1.9.2
- Python 3.8.3 (embeddable distribution)
- Qt 5.15.0
Love your feedback and let us know on GitHub.
Also check out https://aka.ms/ros for ROS related components from Microsoft and partners which are supported on Linux and Windows. And more getting started tutorials on https://aka.ms/ros/docs.
Happy coding ROS Developers!
1 post - 1 participant
![[WWW] [WWW]](./rostheme/img/moin-www.png)
ROS Discourse General: FreeRobotics.tools is looking for a new Maintainer
Hey ROS,
I’m looking for a new maintainer of freerobotics.tools as I personally will not work in the Robotic area anymore. My focus will be on climate satellite engineering, OpenSustain.tech and LibreSelery.
By maintaining this list you will get very intensive insights about how the open-source robotics community is changing and which trends, projects, organizations and technologies are existing here. It is one of the central starting points for newcomers in the open-source robotics field and offers experts the possibility to analyze which projects are missing.
Of course, there would be a small introduction from me and I will support your work as far as I can in the future. Here is a rough description of the field of activity:
- Regular research of new projects.
- Evaluation of projects: Does documentation exist? Is the project still maintained? Is the project interesting for other users?
- Removal of inactive projects.
- Working on pull requests.
- Promotion of projects via Twitter. At the moment every new project is automatically promoted via the protontypes Twitter account by the awesome-twitter-action. We can also set up your Twitter account here. In this way people can just follow the Twitter account to get informed about listed new projects.
I would be very happy if we can keep the quality of the list in the future. If a person or organization can be found where the maintenance is secured over a long period of time, I am also willing to transfer the whole project to another namespace.
If you are interested, please contact me.
1 post - 1 participant
![[WWW] [WWW]](./rostheme/img/moin-www.png)
ROS Discourse General: ROS on Windows: Noetic Release v20201214.0.0.2012281717
The Microsoft Azure Edge Robotics team is happy to announce another Noetic Release v20201214.0.0.2012281717 for Windows developers.
As usual, you can install it by the following steps:
mkdir c:\opt\chocolatey
set ChocolateyInstall=c:\opt\chocolatey
choco source add -n=ros-win -s="https://aka.ms/ros/public" --priority=1
choco upgrade ros-noetic-desktop_full -y --execution-timeout=0
Some highlights of this release:
- Based on the Noetic release sync 2020-12-14
- Enabled packages:
- Desktop_full
- MoveIt
- Navigation
- ROSBridge_suite
- SLAM
- Cartographer
- OpenKarto
- Libraries and Python:
- Boost 1.73.0
- CMake 3.18.2
- EmPY 3.3.4
- Gazebo 10.2.0
- OGRE 1.12.7
- OpenCV 4.3.0
- OpenSSL 1.1.1g
- PCL 1.9.1
- Poco 1.9.2
- Python 3.8.3 (embeddable distribution)
- Qt 5.15.0
Love your feedback and let us know on GitHub.
Also check out https://aka.ms/ros for ROS related components from Microsoft and partners which are supported on Linux and Windows. And more getting started tutorials on https://aka.ms/ros/docs.
Happy coding ROS Developers!
1 post - 1 participant
![[WWW] [WWW]](./rostheme/img/moin-www.png)
ROS Discourse General: ROS 2 TSC Meeting Minutes: 2020-12-17
ROS 2 TSC Meeting Agenda 2020-12-17
Member contribution report (127.3 KB)
-
Attendees
- Steve Macenski - Samsung Research
- Aaron Blasdel - AWS RoboMaker (Amazon)
- Kyle Fazzari - Canonical
- Ralph Lange - Bosch
- Nick Fragale - Rover Robotics
- Jilada Eccleston - Tier IV
- Dave Coleman, Mark Moll, Henning Kayser - PickNik
- Brian Gerkey, Chris Lalancette, William Woodall, Geoff Biggs, Tully Foote, Kat Scott, Louise Poubel - Open Robotics
- Will Son - ROBOTIS
- Ian McMahon - Toyota Research Institute
- Lokesh Kumar Goel - LG Electronics
- Rob Woolley - Wind River (representing Andrei)
- Joe Speed - ADLINK
- Jaime Martin Losa - eProsima
- Jerry Towler - SwRI (representing GVSC)
-
Preliminaries
- [Gerkey] Fill in the contribution report in this doc!
-
Old business
-
New business
- [Gerkey][10 mins] Discuss new TSC applicants and call for vote
- Decision: Gerkey to open vote Dec 18, close Jan 8 to allow for holidays
- Opened late (Dec 22), so will also close late (Jan 12).
- Decision: Gerkey to open vote Dec 18, close Jan 8 to allow for holidays
- [Coleman, Kayser & Moll][15 mins] Update on MoveIt port to ROS 2
- Presentation Slides
- Extended discussion about the “chicken and egg” problem of ROS 2 / MoveIt 2 adoption: users wait for robots to be supported, but robot vendors wait for users to migrate.
- We have various experiences with encouraging adoption. We’re recommending that our customers move to ROS 2, but sometimes it’s a hard sell.
- Bigger companies are willing to make the jump earlier
- ROS 1 remains the biggest competitor to ROS 2.
- Can we do a better job of tracking what’s missing in ROS 2? (and what “business/migrations each missing item would unlock”) ROS 2 Product management / customer management?
- This will be useful, but it’s not uncommon for users to throw out issues that are “blocking” only to come up with more blockers after the initial block is removed.
- Selling based on new features (security, real-time, code quality, hybrid planning, etc.) is better than saying that they can do the same thing but with extra work.
- [Fragale][15 mins] Next-Gen Robotics Hardware Modularity
- [Pangercic][3min] Executor(s) in ROS 2
- Apex.AI started a survey document which we shared with the community experts: https://docs.google.com/document/d/1O53xOVlk4zwsfNukLaDbSWfT64wnoD9xh2EjWwX43qo/edit
- If anyone is interested in the topic of (improved) executors please consider chiming in
- [Lange][5 mins] briefly discuss about the PRs to add micro-ROS to REP-2005, i.e.
- https://github.com/ros-infrastructure/rep/pull/290
- https://github.com/ros-infrastructure/rep/pull/292
- https://github.com/ros-infrastructure/rep/pull/300
- Reminder: TSC members need to approve the PR:
- “The PR will be merged if and when the sum of TSC member vote values is >= 3 (votes of +0 and -0 are treated equally as 0 when computing the sum).”
- [Macenski][5 min] TSC Charter confidentiality proposal https://docs.google.com/document/d/1h0hXa7-7M7VlhQgAgG2VhuY34JsRz6IhuxBJqpo6BhY/edit?usp=sharing
- [Macenski][5 min] Self-reporting FTE analysis https://docs.google.com/spreadsheets/d/1IdGedh0dAvODBgs7vdKc1EeqqbidM2GLsBiq8t42R9A/edit?usp=sharing
- [Gerkey][10 mins] Discuss new TSC applicants and call for vote
-
Recurring business
- Next ROS 2 distro release
- [Lalancette][10 mins]
- Plan for setting CycloneDDS as the default RMW
- Open Robotics to post announcement of this decision on Discourse today
- C++17 - https://github.com/ros-infrastructure/rep/pull/291 - I haven’t heard any objections to this change, so we’ll probably go ahead with this
- macOS support - macOS support in ROS 2 Galactic and beyond - unless we get some kind of dedicated support for it, will probably drop it to Tier 3 in Galactic
- Follow-up about additional committers - crunched the numbers, found 3 obvious candidates for inviting to core committers. Will be sending out invitations tomorrow/early next week
- Plan for setting CycloneDDS as the default RMW
- [Pangercic][3min] Follow-up on signing up for the items in ROS 2 G
- There were no additional volunteers for the implementation of the features https://index.ros.org/doc/ros2/Roadmap/#id2
- Where is the problem? What could be improved to get these features in?
- [Lalancette][10 mins]
- Working groups [<5 mins each] [Not discussed live in the meeting]
-
[Knese] Control
-
[Speed] Edge AI
- recording and meeting minutes
- Amey Kulkarni at NVIDIA presented new ROS 2 packages for human pose estimation, classification, and object detection being provided as eloquent & foxy cyclonedds Jetson dockers.
- presentation slides
- - NVIDIA-AI-IOT/ros2_trt_pose : ROS 2 package for “trt_pose”: real-time human pose estimation on NVIDIA Jetson Platform
- - NVIDIA-AI-IOT/ros2_deepstream : ROS 2 package for NVIDIA DeepStream applications on Jetson Platforms
- - NVIDIA-AI-IOT/ros2_torch_trt : ROS 2 packages for PyTorch and TensorRT for real-time classification and object detection on Jetson Platforms
- - NVIDIA-AI-IOT/ros2_jetson_stats : ROS 2 package for monitoring and controlling NVIDIA Jetson Platform resources
- Nav2 WG needs help to get optimized Mask R-CNN on Nvidia Jetson or GPUs
- Nav2 WG needs help getting NVIDIA GPU optimized Mask-RCNN available in ROS 2. Nav2 WG has been working on a navigation pipeline for detection, tracking, and avoidance for some time and this is the last blocking thing to releasing and demos https://github.com/ros-planning/navigation2_dynamic/
- This is blocking meaningful use of GPUs in navigation.
- NVIDIA and Arm trying to figure out solution for Nav2 WG
-
[Martin Losa] Embedded
-
[Coleman] Manipulation
- Prepping for MoveIt 2 Rolling Ridley release
- ROS2_Control collaborations between MoveIt and PickNik
- Alpha UR driver for ROS 2 underway
- Developing 2021 roadmap for MoveIt 2, let us know what you’re working on!
- New Cartesian planning functionality nearly ready to be merged in
- Hybrid planning for MoveIt being built
-
[Macenski] Navigation
- New speed restricted zone capabilities merged! Docs update and discourse announcement to follow.
- Working on pure pursuit variant for integration into the stack before year’s end https://github.com/ros-planning/navigation2_tutorials/pull/17
- Various cleanup leading up to year end to start 2021 with a fresher slate.
- New first-time user startup guide to be merged before years end on TF/URDF
- GPS waypoint follower additions being reviewed and likely merged before week’s end https://github.com/ros-planning/navigation2/pulls/2111
-
[Pangercic] Real-time
- Working on the bench setup for performance testing
- Executor Design draft
-
[Biggs] Safety
- Planning two sessions on requirements elicitation and writing in January (1st and 3rd Wednesdays, in our usual meeting slot). Please join if this topic interests you.
- Have had some discussion about what we could add to REP 2004 regarding requirements.
- Safety watchdogs library and contracts library are seeing some use, judging from the issue tracker.
-
[Fazzari] Security
- Exploring a reference security implementation of a moderately complex, fairly independent real-world system.
- This will be useful as an example for others to follow, as well as a proving ground for NoDL and testing different security policies.
- Next step is to identify one or more prototypes. Demos scheduled in January for MoveIt and the Robotics Middleware Framework (community invites will be posted to discourse in January)
- Hosted a discussion on Privaros, A Framework for Privacy-Compliant Delivery Drones.
- Vulnerability remediation procedure PR approved. This is the workflow for handling vulnerabilities reported through REP 2006, ROS 2 Vulnerability Disclosure Policy.
- Future meeting minutes have moved to the ros-security community github site.
- Exploring a reference security implementation of a moderately complex, fairly independent real-world system.
-
[Blasdel] Tooling
- Rosbag2
- Evaluated new LevelDB storage implementation. Sony will contribute and release it from their own repository to avoid adding even more packages to rosbag2 repository - but it looks like a promising option for users. Performance looks good, with a smaller disk footprint than SQLite.
- New compression multithreading improves data retention in high bandwidth compression use cases
- We are considering starting a landing page like navigation.ros.org for Tooling maintained projects, most importantly Rosbag2. Question for Steve / TSC: how was access for the “navigation” subdomain granted?
- CI Actions
- Deprecation of a GitHub Action core function caused all builds using action-ros-ci to break. The fix process prompted a new release model:
- All CI actions have been bumped to minor version 0.1.0, which promises a stable API
- Have started releasing tag “v0.1” in addition to the patch-level tags e.g. “0.1.4” - Consumers can point at tag “v0.1” to receive all patch releases automatically without change to their code so that the roll-out of a fix like this can happen without intervention
- New known user: ros2_control
- Deprecation of a GitHub Action core function caused all builds using action-ros-ci to break. The fix process prompted a new release model:
- REP-2005 RCP requests
- Rosbag2
-
[Woodall] Middleware
- Agenda, minutes, and further notes:
- Had a presentation of zenoh-plugin-dds as a bridge across problematic networks.
- Progress continuing on the Events based Executor proposal from iRobot
- Review of proof of concept of network flow id’s with FastDDS, from Ericsson and eProsima
-
- Next ROS 2 distro release
1 post - 1 participant
![[WWW] [WWW]](./rostheme/img/moin-www.png)
ROS Discourse General: Detect Low Obstacles using Tilted 2D Lidar [experimental]
This method described in the article is experimental. It could satisfy my environment. Please do more tests if you want to use the idea on your product.
Best,
Marshal
1 post - 1 participant
![[WWW] [WWW]](./rostheme/img/moin-www.png)
ROS Discourse General: New packages for Kinetic Kame 2020-12-21
We’re happy to announce 6 new packages and 43 updated packages for Kinetic Kame.
Thank you to all the maintainers and contributors who have helped make these updates possible. A full listing is below.
Package Updates for kinetic
Added Packages [6]:
- ros-kinetic-color-util: 0.3.0-1
- ros-kinetic-nav-grid-server: 0.3.0-1
- ros-kinetic-robot-nav-rviz-plugins: 0.3.0-1
- ros-kinetic-robot-nav-tools: 0.3.0-1
- ros-kinetic-robot-nav-viz-demos: 0.3.0-1
- ros-kinetic-stag-ros: 0.1.1-6
Updated Packages [43]:
- ros-kinetic-cob-collision-monitor: 0.7.4-1 -> 0.7.5-1
- ros-kinetic-cob-grasp-generation: 0.7.4-1 -> 0.7.5-1
- ros-kinetic-cob-lookat-action: 0.7.4-1 -> 0.7.5-1
- ros-kinetic-cob-manipulation: 0.7.4-1 -> 0.7.5-1
- ros-kinetic-cob-moveit-bringup: 0.7.4-1 -> 0.7.5-1
- ros-kinetic-cob-moveit-interface: 0.7.4-1 -> 0.7.5-1
- ros-kinetic-cob-obstacle-distance-moveit: 0.7.4-1 -> 0.7.5-1
- ros-kinetic-costmap-queue: 0.2.5-0 -> 0.3.0-1
- ros-kinetic-dlux-global-planner: 0.2.5-0 -> 0.3.0-1
- ros-kinetic-dlux-plugins: 0.2.5-0 -> 0.3.0-1
- ros-kinetic-dwb-critics: 0.2.5-0 -> 0.3.0-1
- ros-kinetic-dwb-local-planner: 0.2.5-0 -> 0.3.0-1
- ros-kinetic-dwb-msgs: 0.2.5-0 -> 0.3.0-1
- ros-kinetic-dwb-plugins: 0.2.5-0 -> 0.3.0-1
- ros-kinetic-flexbe-behavior-engine: 1.3.0-1 -> 1.3.1-1
- ros-kinetic-flexbe-core: 1.3.0-1 -> 1.3.1-1
- ros-kinetic-flexbe-input: 1.3.0-1 -> 1.3.1-1
- ros-kinetic-flexbe-mirror: 1.3.0-1 -> 1.3.1-1
- ros-kinetic-flexbe-msgs: 1.3.0-1 -> 1.3.1-1
- ros-kinetic-flexbe-onboard: 1.3.0-1 -> 1.3.1-1
- ros-kinetic-flexbe-states: 1.3.0-1 -> 1.3.1-1
- ros-kinetic-flexbe-testing: 1.3.0-1 -> 1.3.1-1
- ros-kinetic-flexbe-widget: 1.3.0-1 -> 1.3.1-1
- ros-kinetic-global-planner-tests: 0.2.5-0 -> 0.3.0-1
- ros-kinetic-locomotor: 0.2.5-0 -> 0.3.0-1
- ros-kinetic-locomotor-msgs: 0.2.5-0 -> 0.3.0-1
- ros-kinetic-locomove-base: 0.2.5-0 -> 0.3.0-1
- ros-kinetic-mavlink: 2020.11.11-1 -> 2020.12.12-1
- ros-kinetic-nav-2d-msgs: 0.2.5-0 -> 0.3.0-1
- ros-kinetic-nav-2d-utils: 0.2.5-0 -> 0.3.0-1
- ros-kinetic-nav-core-adapter: 0.2.5-0 -> 0.3.0-1
- ros-kinetic-nav-core2: 0.2.5-0 -> 0.3.0-1
- ros-kinetic-nav-grid: 0.2.5-0 -> 0.3.0-1
- ros-kinetic-nav-grid-iterators: 0.2.5-0 -> 0.3.0-1
- ros-kinetic-nav-grid-pub-sub: 0.2.5-0 -> 0.3.0-1
- ros-kinetic-robot-navigation: 0.2.5-0 -> 0.3.0-1
- ros-kinetic-rosapi: 0.11.12-1 -> 0.11.13-1
- ros-kinetic-rosbridge-library: 0.11.12-1 -> 0.11.13-1
- ros-kinetic-rosbridge-msgs: 0.11.12-1 -> 0.11.13-1
- ros-kinetic-rosbridge-server: 0.11.12-1 -> 0.11.13-1
- ros-kinetic-rosbridge-suite: 0.11.12-1 -> 0.11.13-1
- ros-kinetic-rtabmap: 0.20.0-1 -> 0.20.7-2
- ros-kinetic-rtabmap-ros: 0.20.0-1 -> 0.20.7-1
Removed Packages [0]:
Thanks to all ROS maintainers who make packages available to the ROS community. The above list of packages was made possible by the work of the following maintainers:
- Brennan Cain
- David V. Lu!!
- Felix Messmer
- Hans-Joachim Krauch
- Mathieu Labbe
- Philipp Schillinger
- Russell Toris
- Vladimir Ermakov
1 post - 1 participant
![[WWW] [WWW]](./rostheme/img/moin-www.png)
ROS Discourse General: New packages for Melodic 2020-12-21
We’re happy to announce the next update of ROS Melodic. There are 29 new packages as well as 108 updated packages. Full details are below.
Package Updates for melodic
Added Packages [29]:
- ros-melodic-cmd-vel-smoother: 0.1.15-1
- ros-melodic-color-util: 0.3.0-1
- ros-melodic-contact-states-observer: 0.1.15-1
- ros-melodic-eus-nlopt: 0.1.15-1
- ros-melodic-eus-qp: 0.1.15-1
- ros-melodic-eus-qpoases: 0.1.15-1
- ros-melodic-gazebo-video-monitor-msgs: 0.6.0-2
- ros-melodic-gazebo-video-monitors: 0.6.0-2
- ros-melodic-heifu-diagnostic: 0.7.2-1
- ros-melodic-heifu-mavros: 0.7.2-1
- ros-melodic-heifu-msgs: 0.7.2-1
- ros-melodic-heifu-safety: 0.7.2-1
- ros-melodic-heifu-simple-waypoint: 0.7.2-1
- ros-melodic-heifu-tools: 0.7.2-1
- ros-melodic-joy-mouse: 0.1.15-1
- ros-melodic-jsk-calibration: 0.1.15-1
- ros-melodic-jsk-ik-server: 0.1.15-1
- ros-melodic-jsk-teleop-joy: 0.1.15-1
- ros-melodic-mesh-client: 1.0.0-1
- ros-melodic-nav-grid-server: 0.3.0-1
- ros-melodic-robot-nav-rviz-plugins: 0.3.0-1
- ros-melodic-robot-nav-tools: 0.3.0-1
- ros-melodic-robot-nav-viz-demos: 0.3.0-1
- ros-melodic-stag-ros: 0.2.1-1
- ros-melodic-tvm-vendor: 0.7.2-1
- ros-melodic-vesc: 1.1.0-1
- ros-melodic-vesc-ackermann: 1.1.0-1
- ros-melodic-vesc-driver: 1.1.0-1
- ros-melodic-vesc-msgs: 1.1.0-1
Updated Packages [108]:
- ros-melodic-ackermann-steering-controller: 0.17.0-1 -> 0.17.1-1
- ros-melodic-chomp-motion-planner: 1.0.6-1 -> 1.0.7-1
- ros-melodic-cob-collision-monitor: 0.7.4-1 -> 0.7.5-1
- ros-melodic-cob-grasp-generation: 0.7.4-1 -> 0.7.5-1
- ros-melodic-cob-lookat-action: 0.7.4-1 -> 0.7.5-1
- ros-melodic-cob-manipulation: 0.7.4-1 -> 0.7.5-1
- ros-melodic-cob-moveit-bringup: 0.7.4-1 -> 0.7.5-1
- ros-melodic-cob-moveit-interface: 0.7.4-1 -> 0.7.5-1
- ros-melodic-cob-obstacle-distance-moveit: 0.7.4-1 -> 0.7.5-1
- ros-melodic-combined-robot-hw: 0.18.2-1 -> 0.18.3-1
- ros-melodic-combined-robot-hw-tests: 0.18.2-1 -> 0.18.3-1
- ros-melodic-controller-interface: 0.18.2-1 -> 0.18.3-1
- ros-melodic-controller-manager: 0.18.2-1 -> 0.18.3-1
- ros-melodic-controller-manager-msgs: 0.18.2-1 -> 0.18.3-1
- ros-melodic-controller-manager-tests: 0.18.2-1 -> 0.18.3-1
- ros-melodic-costmap-queue: 0.2.5-1 -> 0.3.0-1
- ros-melodic-diff-drive-controller: 0.17.0-1 -> 0.17.1-1
- ros-melodic-dlux-global-planner: 0.2.5-1 -> 0.3.0-1
- ros-melodic-dlux-plugins: 0.2.5-1 -> 0.3.0-1
- ros-melodic-dwb-critics: 0.2.5-1 -> 0.3.0-1
- ros-melodic-dwb-local-planner: 0.2.5-1 -> 0.3.0-1
- ros-melodic-dwb-msgs: 0.2.5-1 -> 0.3.0-1
- ros-melodic-dwb-plugins: 0.2.5-1 -> 0.3.0-1
- ros-melodic-effort-controllers: 0.17.0-1 -> 0.17.1-1
- ros-melodic-flexbe-behavior-engine: 1.3.0-1 -> 1.3.1-1
- ros-melodic-flexbe-core: 1.3.0-1 -> 1.3.1-1
- ros-melodic-flexbe-input: 1.3.0-1 -> 1.3.1-1
- ros-melodic-flexbe-mirror: 1.3.0-1 -> 1.3.1-1
- ros-melodic-flexbe-msgs: 1.3.0-1 -> 1.3.1-1
- ros-melodic-flexbe-onboard: 1.3.0-1 -> 1.3.1-1
- ros-melodic-flexbe-states: 1.3.0-1 -> 1.3.1-1
- ros-melodic-flexbe-testing: 1.3.0-1 -> 1.3.1-1
- ros-melodic-flexbe-widget: 1.3.0-1 -> 1.3.1-1
- ros-melodic-force-torque-sensor-controller: 0.17.0-1 -> 0.17.1-1
- ros-melodic-forward-command-controller: 0.17.0-1 -> 0.17.1-1
- ros-melodic-four-wheel-steering-controller: 0.17.0-1 -> 0.17.1-1
- ros-melodic-gazebo-video-monitor-plugins: 0.5.0-2 -> 0.6.0-2
- ros-melodic-global-planner-tests: 0.2.5-1 -> 0.3.0-1
- ros-melodic-gripper-action-controller: 0.17.0-1 -> 0.17.1-1
- ros-melodic-hardware-interface: 0.18.2-1 -> 0.18.3-1
- ros-melodic-imu-sensor-controller: 0.17.0-1 -> 0.17.1-1
- ros-melodic-iris-lama: 1.0.0-1 -> 1.1.0-2
- ros-melodic-iris-lama-ros: 1.0.0-1 -> 1.1.0-1
- ros-melodic-joint-limits-interface: 0.18.2-1 -> 0.18.3-1
- ros-melodic-joint-state-controller: 0.17.0-1 -> 0.17.1-1
- ros-melodic-joint-trajectory-controller: 0.17.0-1 -> 0.17.1-1
- ros-melodic-leo-gazebo: 0.1.2-1 -> 0.1.3-1
- ros-melodic-leo-simulator: 0.1.2-1 -> 0.1.3-1
- ros-melodic-locomotor: 0.2.5-1 -> 0.3.0-1
- ros-melodic-locomotor-msgs: 0.2.5-1 -> 0.3.0-1
- ros-melodic-locomove-base: 0.2.5-1 -> 0.3.0-1
- ros-melodic-lvr2: 20.11.1-1 -> 20.11.2-1
- ros-melodic-mavlink: 2020.11.11-1 -> 2020.12.12-1
- ros-melodic-moveit: 1.0.6-1 -> 1.0.7-1
- ros-melodic-moveit-chomp-optimizer-adapter: 1.0.6-1 -> 1.0.7-1
- ros-melodic-moveit-commander: 1.0.6-1 -> 1.0.7-1
- ros-melodic-moveit-controller-manager-example: 1.0.6-1 -> 1.0.7-1
- ros-melodic-moveit-core: 1.0.6-1 -> 1.0.7-1
- ros-melodic-moveit-fake-controller-manager: 1.0.6-1 -> 1.0.7-1
- ros-melodic-moveit-kinematics: 1.0.6-1 -> 1.0.7-1
- ros-melodic-moveit-planners: 1.0.6-1 -> 1.0.7-1
- ros-melodic-moveit-planners-chomp: 1.0.6-1 -> 1.0.7-1
- ros-melodic-moveit-planners-ompl: 1.0.6-1 -> 1.0.7-1
- ros-melodic-moveit-plugins: 1.0.6-1 -> 1.0.7-1
- ros-melodic-moveit-ros: 1.0.6-1 -> 1.0.7-1
- ros-melodic-moveit-ros-benchmarks: 1.0.6-1 -> 1.0.7-1
- ros-melodic-moveit-ros-control-interface: 1.0.6-1 -> 1.0.7-1
- ros-melodic-moveit-ros-manipulation: 1.0.6-1 -> 1.0.7-1
- ros-melodic-moveit-ros-move-group: 1.0.6-1 -> 1.0.7-1
- ros-melodic-moveit-ros-occupancy-map-monitor: 1.0.6-1 -> 1.0.7-1
- ros-melodic-moveit-ros-perception: 1.0.6-1 -> 1.0.7-1
- ros-melodic-moveit-ros-planning: 1.0.6-1 -> 1.0.7-1
- ros-melodic-moveit-ros-planning-interface: 1.0.6-1 -> 1.0.7-1
- ros-melodic-moveit-ros-robot-interaction: 1.0.6-1 -> 1.0.7-1
- ros-melodic-moveit-ros-visualization: 1.0.6-1 -> 1.0.7-1
- ros-melodic-moveit-ros-warehouse: 1.0.6-1 -> 1.0.7-1
- ros-melodic-moveit-runtime: 1.0.6-1 -> 1.0.7-1
- ros-melodic-moveit-servo: 1.0.6-1 -> 1.0.7-1
- ros-melodic-moveit-setup-assistant: 1.0.6-1 -> 1.0.7-1
- ros-melodic-moveit-simple-controller-manager: 1.0.6-1 -> 1.0.7-1
- ros-melodic-nav-2d-msgs: 0.2.5-1 -> 0.3.0-1
- ros-melodic-nav-2d-utils: 0.2.5-1 -> 0.3.0-1
- ros-melodic-nav-core-adapter: 0.2.5-1 -> 0.3.0-1
- ros-melodic-nav-core2: 0.2.5-1 -> 0.3.0-1
- ros-melodic-nav-grid: 0.2.5-1 -> 0.3.0-1
- ros-melodic-nav-grid-iterators: 0.2.5-1 -> 0.3.0-1
- ros-melodic-nav-grid-pub-sub: 0.2.5-1 -> 0.3.0-1
- ros-melodic-plotjuggler: 3.0.3-1 -> 3.0.5-2
- ros-melodic-position-controllers: 0.17.0-1 -> 0.17.1-1
- ros-melodic-psen-scan-v2: 0.1.2-1 -> 0.1.3-1
- ros-melodic-robot-localization: 2.6.7-1 -> 2.6.9-1
- ros-melodic-robot-navigation: 0.2.5-1 -> 0.3.0-1
- ros-melodic-ros-control: 0.18.2-1 -> 0.18.3-1
- ros-melodic-ros-controllers: 0.17.0-1 -> 0.17.1-1
- ros-melodic-rosapi: 0.11.12-1 -> 0.11.13-1
- ros-melodic-rosbridge-library: 0.11.12-1 -> 0.11.13-1
- ros-melodic-rosbridge-msgs: 0.11.12-1 -> 0.11.13-1
- ros-melodic-rosbridge-server: 0.11.12-1 -> 0.11.13-1
- ros-melodic-rosbridge-suite: 0.11.12-1 -> 0.11.13-1
- ros-melodic-rqt-controller-manager: 0.18.2-1 -> 0.18.3-1
- ros-melodic-rqt-joint-trajectory-controller: 0.17.0-1 -> 0.17.1-1
- ros-melodic-rtabmap: 0.20.0-2 -> 0.20.7-1
- ros-melodic-rtabmap-ros: 0.20.0-1 -> 0.20.7-1
- ros-melodic-sr-hand-detector: 0.0.2-1 -> 0.0.3-2
- ros-melodic-transmission-interface: 0.18.2-1 -> 0.18.3-1
- ros-melodic-urdfdom-py: 0.4.4-1 -> 0.4.5-1
- ros-melodic-velocity-controllers: 0.17.0-1 -> 0.17.1-1
- ros-melodic-video-stream-opencv: 1.1.5-0 -> 1.1.6-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:
- Alexander Gutenkunst
- Bence Magyar
- Blake Anderson
- Brennan Cain
- Błażej Sowa
- Chittaranjan Srinivas Swaminathan
- Chris Lalancette
- Dave Coleman
- David V. Lu!!
- Davide Faconti
- Eurico Pedrosa
- Felix Messmer
- Filipe Almeida
- Fábio Azevedo
- Hans-Joachim Krauch
- Isaac I. Y. Saito
- Johannes Betz
- Jon Binney
- Josh Whitley
- João Pedro Carvalho
- Masaru Morita
- Mathias Lüdtke
- Mathieu Labbe
- Michael Ferguson
- Michael Görner
- Nick Lamprianidis
- Noda Shintaro
- Philipp Schillinger
- Raghavender Sahdev
- Russell Toris
- Ryohei Ueda
- Sachin Chitta
- Sammy Pfeiffer
- Sebastian Pütz
- Shadow Robot’s Software Team
- Shunichi Nozawa
- Tom Moore
- Vincent Rousseau
- Vladimir Ermakov
- Yuki Furuta
- furuta
- nozawa
1 post - 1 participant
![[WWW] [WWW]](./rostheme/img/moin-www.png)
ROS Discourse General: [Poll] A possible new SBC for TurtleBot3?
Hi community,
I’m getting a good amount of inquiries about a new SBC that can replace the current RPi3B+ on TurtleBot3
and I’d like to see the actual ROS users’ preference.
Please understand that high performance modules will not be considered as possible options to keep TurtleBot3 within the affordable price.
Some users also requested to upgrade the sensor, but this may not be feasible at this time so let’s rule out the sensor part in this discussion.
SBC seems pretty dependent on the industries where the robot is deployed, so if you can also specify which the industry you are in, it’d be greatly appreciated and helpful to understand the result.
Please note that you can select multiple items for the SBC and items are listed in alphabetical order.
- Jetson Nano
- Raspberry Pi 4
- UP Squared
0 voters
In which industry do you use TurtleBot3?
- Commercial
- Educational
- Entertainment
- Industrial
- Logistics
- Research & Development
- Service
0 voters
Happy holidays and happy new year!
1 post - 1 participant
![[WWW] [WWW]](./rostheme/img/moin-www.png)
ROS Discourse General: ROS News for the Week of 12/14/2020
Christmas is Cancelled from FZI
CoBot Christmas
I was gifted this by an aspiring engineer this week. If you have similar awesome technical drawnings please drop them in the comments.
Seasons Greetings
- ROS 2 Advent Calendar in Japanese
- Note, there will be no update next week due to the holiday.
- Holiday: Man’s Best Robotic Friend
- Christmas Cancelled
Events
ROS Related
- ROS 2 Default Middleware for Galactic Selected
- 2020 ROS 2 Middleware Report – includes code and data
- Proposal for Common Messages in ROS 2
- macOS moved to Tier 3 for ROS 2 Galactic
- Last Update for ROS 2 Eloquent Elusor
- Input Needed: ROS OpenVINO Toolkit Roadmap
- ARViz – Augmented Reality RVIZ
- MOCAP 4 ROS 2
- ROS Noetic Update
- Italian ROS Group
- Slow Your Roll: Nav2 Speed Restriction Support
- Cargo Delivery ODD Kick-Off Meeting
- Multiwheel Differential Drive Plugin
- TurtleBot3 and Webots
- ROSout Log Monitoring Tool
- @fmrico pluginlib / github actions tools
News
- PickNik wins Good Robot Award
- James Bruton keeps building his ROS robot
- Plus One Robotics Podcast
- Cloud Simulation for CI/CD in Robotics
- QuadSAT ROS for Testing Satellite Equipment
- Google X on Robots and Puppets
- NanoSaur Robot
- ROS Industrial: Open Source is also establishing itself in industrial robotics
- ROS Industrial Video Competition
ROS Questions
- SystemD does not work with ROS 2
- Utility to Convert Point Cloud to Height Map
- Adding external c library to a ROS2 node
1 post - 1 participant
![[WWW] [WWW]](./rostheme/img/moin-www.png)
ROS Industrial: ROS-Industrial Asia Pacific Workshop 2020
The Annual ROS-Industrial Asia Pacific Workshop took place on the 29th October 2020, this year in a one day digital webinar format. The workshop was opened by our Guest-of-Honor, Prof. Quek Tong Boon, Chief Executive of the Singapore National Robotics Programme. After the opening, Erik Unemyr, Consortium Manager for ROS-Industrial Asia Pacific, shared updates on the topic of “Industry Ready ROS 2 – Easy to Adopt Modules with Quality”, which comprised of the current technology focus the team has been developing in-house, including:
- easy_perception_deployment – a ROS2 Package that aims to accelerate the training and deployment of Computer Vision models for industry use (which is now in Beta release, and you can find it here)
- easy_manipulation_deployment – a ROS2 Package that has a user-friendly Graphical User Interface (GUI) to create a robotic workcell, and supports a variety of commonly used industrial end-effectors using a flexible grasp implementation approach. This will package will be released soon, to be made available on the ROS-Industrial GitHub.
Next, we had the opportunity to invite Roger Barga, General Manager at AWS Robotics, to present on “The Role of the Cloud in Future of Robotics”. During his presentation, he addressed the importance and necessity of applications in cloud computing such as using it for development of robotic applications in simulation, testing and deployment. AWS also currently supports ROS, ROS2 & Gazebo within their services.
Matt Robinson, Programme Manager for our ROS-Industrial counterpart in Americas at the Southwest Research Institute (SwRI), presented on “Enabling Production Performance in ROS-Based Systems” where he brought up the value of ROS2 for various industrial use cases and also showcased some of the developments happening at SwRI.
Sharing more details about the activities at the Advanced Remanufacturing and Technology Centre, Bai Fengjun, Technical Lead from the Advanced Robotics Applications team at ARTC, presented development on the Next Generation Hyper-Personalization Line and how ROS has played a part in the development of such applications for the Fast Moving Consumer Goods sector.
Michael Sayre, CEO & Co-Founder of Cognicept Systems, one of our Consortium Members in the Asia Pacific Region, then presented on the importance of error handling and remote management for robotic fleets, and their latest development of the ROS2 Listener agent that was developed together with the ROS-Industrial Team at ARTC. You can find the repository here.
Shortly after, Albertus Hendrawan Adiawahono, Head of the Mobility Group at the ASTAR Institute for Infocomm Research (I2R) presented on their current efforts with the local healthcare ecosystem to develop modules that would aid robots to be more resilient in the hospital ward setting, where the environment rapidly changes. They currently have completed Proof of Concepts in which the robots are able to adapt to lifts, curtains and even simulating a blue code emergency drill.
After the lunch break, we invited Jack Sheng Kee, Lab Director of the Delta Research Centre, a ROS-Industrial Consortium Member, to share on “Reconfigurable and Flexible Automation in Manufacturing” where he presented some of the existing solutions Delta has developed, and how they are all ROS supported.
We also had the team from Open Robotics, Marco Gutierrez and Grey, to present on roadmap updates with new features and future plans for Ignition Gazebo, ROS2 and also the Robotics Middleware Framework (RMF). The development of RMF has become a key effort in driving the integration and deployment of wide-scale smart robotics systems, which includes the communication between robots, building infrastructure and other edge devices.
Christoph Hellmann Santos, Consortium Manager for ROS-Industrial Europe at Fraunhofer IPA presented on the latest updates and success stories of both the ROSIN and ROS-Industrial Projects, such as the toolbox for automated delivery for the DHL Streetscooter and the real-time mapping project with Bosch Rexroth.
Prof Trygve Thomessen, Managing Director of PPM Robotics AS also presented ROSIN updates with the ROSWELD project, an application and success story of ROS being deployed in heavy industrial applications such as robotic welding. Last but not least, we had Andrei Kholodnyi, Principal Technologist at Wind River to present on “A Mixed-Critical ROS2 Implementation on VxWorks RTOS, WRLinux & Hypervisor” where he highlighted the use and importance of safety compliant and real-time solutions for ROS2 Applications.
A summarized table of all the speakers, including presentation slides and recording, is now available here!














To conclude this year’s ROS-Industrial Workshop Asia Pacific, Dr. Zhang Jing Bing, Technical Division Director for Smart Robotics and Automation (SRA) at ARTC gave his closing remarks.
The ROS-Industrial Consortium Asia Pacific @ ARTC continue with a multi-prong approach in bridging the gaps between the industry and the community in adoption of ROS and robotics, by working closely with our industry partners and to develop modules that can cater for industrial needs, providing training opportunities for aspiring roboticists as well as companies that are embarking on leveraging ROS to scale their robotics adoption.
On behalf of the ROS-Industrial Team at ARTC, we hope that you enjoyed the webinar as much as we did, and we look forward to meeting each other in 2021 for future ROS-Industrial activities!
![[WWW] [WWW]](./rostheme/img/moin-www.png)
ROS Discourse General: ROS 2 Galactic Default Middleware Announced
Hi All,
You may recall that one of our main motivations in designing ROS 2 with a middleware abstraction is to provide end users with a flexible transport layer supported by a rich ecosystem of vendors. This competitive approach has already yielded dividends such as the FastDDS discovery service, IceOryx zero copy memory passing, and multiple innovations in MicroROS for embedded hardware. While some have called this “The DDS Wars” I prefer to think of it as the “DDS Cambrian Explosion”, as we see more and more vendors of DDS and other middlewares become interested in ROS 2, and how their implementations can bring new features to bear on different parts of the robotics ecosystem.
ROS 2 has long supported multiple middlewares, and will continue to do so. But of course there has to be a default configuration that just works for most users. As discussed in previous posts, starting with Galactic Geochelone the default RMW configuration for each ROS 2 distro will be selected by the ROS 2 Technical Steering Committee (TSC) after a thorough vetting process. It is worth noting that when we say default, we really do mean default, and users can continue to choose non-default RMW configurations. The TSC aims to choose the best default for each distro, but that doesn’t mean that it will be the best choice for every application. Importantly, changing the RMW configuration on your robot is simply a matter of running a handful of commands.
I am happy to announce that after careful consideration the ROS 2 TSC has selected CycloneDDS to be the default RMW for ROS 2 Galactic Geochelone. This vote is the result of a thoughtful review and discussion of the available options by the ROS 2 TSC, including a comprehensive technical evaluation of the Tier 1 RMWs by the team at Open Robotics. That report, including source code and data, is available to all. The report includes performance statistics about each RMW implementation, simulated and real world testing of each RMW, a review of the code quality and responsiveness of each RMW vendor, and a community survey. On balance, the similarities among the Tier 1 RMWs are greater than their differences, and this was a hard decision for the TSC. We hope you make use of the report in selecting your RMW implementation, and feel free to send us your feedback. We intend this report and its future iterations, as well as the tools developed in generating it, to be a neutral source of RMW information for the ROS community.
We’ll start implementing the TSC’s decision soon. We expect the change of the default RMW to CycloneDDS to be merged by late January 2021, and available for testing in Rolling soon after. We realize that this change will impact many users, but we also believe the impacts will be minimal. One important difference is that, whereas Foxy’s default behavior via FastDDS is asynchronous publishing (similar to ROS 1), Galactic’s default behavior via CycloneDDS will be synchronous publishing. This will change the behavior of calls to publish on a Publisher when more data is being sent than the network can handle, and perhaps in other cases; we’ll include more details in the near future (you can also read the report). If you encounter issues related to this or other changes when you update to Galactic, please report them! And remember that, as is the case now with Foxy, you can change your RMW configuration with just a handful of commands. If you would like to help with this process or would like to beta test the latest ROS 2 release (particularly on a larger multi-robot scenario) please contact me or the core dev team.
2 posts - 2 participants
![[WWW] [WWW]](./rostheme/img/moin-www.png)
ROS Discourse General: Announcing bi-weekly Eclipse iceoryx developer meetup
Hi all!
I’m happy to announce a bi-weekly meetup for developers working on Eclipse iceoryx. It will start on 2021-01-07T16:00:00Z and happens always on the first and the third Thursday in the month.
The main goals of the meetup are:
- Give newcomers the ability to raise questions to core developers
- Discuss and propose feature
- Steer the project together with the community
Everyone interested is welcome to join. If you have agenda points, I’d kindly ask you to raise them beforehand on the mailing list or via Gitter.im. More info can be found here.
The meetup will happen on Zoom.
Special thanks to Andreas Riexinger and OpenADx for organising the event!
Looking forward to the first meeting!
Hope to see you then,
Simon
1 post - 1 participant
![[WWW] [WWW]](./rostheme/img/moin-www.png)
ROS Discourse General: Webots ROS2 Community Meeting
Webots is an open-source, high fidelity, and easy to use robot simulator. At Cyberbotics, we have been developing Webots + ROS2 integration since the Crystal days, and now we want to discuss with you how to further improve it.
Therefore, we would like to organize an online meeting and welcome every ROS2 users and Webots users!
Preliminary meeting agenda:
- Introduction to Webots and the current state of the ROS2 integration.
- Our current vision and objectives.
- Guest speaker: Webots + ROS2 use-case from the industry.
- Round table: attendees suggesting features, improvements, proposing contributions, collaborations, etc.
This is our first time organizing an open meeting with the ROS community. So, we need to know whether you are interested in learning more about ROS2 in Webots and participating to such a discussion.
If enough people are interested we will schedule the meeting in the middle of January.
Let us know if you would be interested to attend: either here, by e-mail to support@cyberbotics.com or in our Discord channels.
-Olivier Michel
Cyberbotics Ltd., CEO
12 posts - 11 participants
![[WWW] [WWW]](./rostheme/img/moin-www.png)
ROS Discourse General: New Packages for Eloquent 2020-12-14
We’re happy to announce 1 new package and 224 updated packages for Eloquent Elusor this week.
This will be the final sync for the Eloquent release
Thank you to all the maintainers and contributors who have helped make these packages possible!
Details are below:
Package Updates for eloquent
Added Packages [1]:
- ros-eloquent-rclc-lifecycle: 0.1.4-1
Updated Packages [224]:
- ros-eloquent-ament-clang-format: 0.8.1-1 -> 0.8.2-1
- ros-eloquent-ament-clang-tidy: 0.8.1-1 -> 0.8.2-1
- ros-eloquent-ament-cmake: 0.8.2-1 -> 0.8.3-1
- ros-eloquent-ament-cmake-auto: 0.8.2-1 -> 0.8.3-1
- ros-eloquent-ament-cmake-clang-format: 0.8.1-1 -> 0.8.2-1
- ros-eloquent-ament-cmake-clang-tidy: 0.8.1-1 -> 0.8.2-1
- ros-eloquent-ament-cmake-copyright: 0.8.1-1 -> 0.8.2-1
- ros-eloquent-ament-cmake-core: 0.8.2-1 -> 0.8.3-1
- ros-eloquent-ament-cmake-cppcheck: 0.8.1-1 -> 0.8.2-1
- ros-eloquent-ament-cmake-cpplint: 0.8.1-1 -> 0.8.2-1
- ros-eloquent-ament-cmake-export-definitions: 0.8.2-1 -> 0.8.3-1
- ros-eloquent-ament-cmake-export-dependencies: 0.8.2-1 -> 0.8.3-1
- ros-eloquent-ament-cmake-export-include-directories: 0.8.2-1 -> 0.8.3-1
- ros-eloquent-ament-cmake-export-interfaces: 0.8.2-1 -> 0.8.3-1
- ros-eloquent-ament-cmake-export-libraries: 0.8.2-1 -> 0.8.3-1
- ros-eloquent-ament-cmake-export-link-flags: 0.8.2-1 -> 0.8.3-1
- ros-eloquent-ament-cmake-flake8: 0.8.1-1 -> 0.8.2-1
- ros-eloquent-ament-cmake-gmock: 0.8.2-1 -> 0.8.3-1
- ros-eloquent-ament-cmake-gtest: 0.8.2-1 -> 0.8.3-1
- ros-eloquent-ament-cmake-include-directories: 0.8.2-1 -> 0.8.3-1
- ros-eloquent-ament-cmake-libraries: 0.8.2-1 -> 0.8.3-1
- ros-eloquent-ament-cmake-lint-cmake: 0.8.1-1 -> 0.8.2-1
- ros-eloquent-ament-cmake-mypy: 0.8.1-1 -> 0.8.2-1
- ros-eloquent-ament-cmake-nose: 0.8.2-1 -> 0.8.3-1
- ros-eloquent-ament-cmake-pclint: 0.8.1-1 -> 0.8.2-1
- ros-eloquent-ament-cmake-pep257: 0.8.1-1 -> 0.8.2-1
- ros-eloquent-ament-cmake-pep8: 0.8.1-1 -> 0.8.2-1
- ros-eloquent-ament-cmake-pyflakes: 0.8.1-1 -> 0.8.2-1
- ros-eloquent-ament-cmake-pytest: 0.8.2-1 -> 0.8.3-1
- ros-eloquent-ament-cmake-python: 0.8.2-1 -> 0.8.3-1
- ros-eloquent-ament-cmake-target-dependencies: 0.8.2-1 -> 0.8.3-1
- ros-eloquent-ament-cmake-test: 0.8.2-1 -> 0.8.3-1
- ros-eloquent-ament-cmake-uncrustify: 0.8.1-1 -> 0.8.2-1
- ros-eloquent-ament-cmake-version: 0.8.2-1 -> 0.8.3-1
- ros-eloquent-ament-cmake-xmllint: 0.8.1-1 -> 0.8.2-1
- ros-eloquent-ament-copyright: 0.8.1-1 -> 0.8.2-1
- ros-eloquent-ament-cppcheck: 0.8.1-1 -> 0.8.2-1
- ros-eloquent-ament-cpplint: 0.8.1-1 -> 0.8.2-1
- ros-eloquent-ament-flake8: 0.8.1-1 -> 0.8.2-1
- ros-eloquent-ament-lint: 0.8.1-1 -> 0.8.2-1
- ros-eloquent-ament-lint-auto: 0.8.1-1 -> 0.8.2-1
- ros-eloquent-ament-lint-cmake: 0.8.1-1 -> 0.8.2-1
- ros-eloquent-ament-lint-common: 0.8.1-1 -> 0.8.2-1
- ros-eloquent-ament-mypy: 0.8.1-1 -> 0.8.2-1
- ros-eloquent-ament-pclint: 0.8.1-1 -> 0.8.2-1
- ros-eloquent-ament-pep257: 0.8.1-1 -> 0.8.2-1
- ros-eloquent-ament-pep8: 0.8.1-1 -> 0.8.2-1
- ros-eloquent-ament-pyflakes: 0.8.1-1 -> 0.8.2-1
- ros-eloquent-ament-uncrustify: 0.8.1-1 -> 0.8.2-1
- ros-eloquent-ament-xmllint: 0.8.1-1 -> 0.8.2-1
- ros-eloquent-cyclonedds: 0.5.1-2 -> 0.7.0-4
- ros-eloquent-cyclonedds-cmake-module: 0.5.1-1 -> 0.7.0-1
- ros-eloquent-cyclonedds-dbgsym: 0.5.1-2 -> 0.7.0-4
- ros-eloquent-desktop: 0.8.4-1 -> 0.8.5-1
- ros-eloquent-examples-rclcpp-minimal-action-client: 0.8.2-1 -> 0.8.3-1
- ros-eloquent-examples-rclcpp-minimal-action-client-dbgsym: 0.8.2-1 -> 0.8.3-1
- ros-eloquent-examples-rclcpp-minimal-action-server: 0.8.2-1 -> 0.8.3-1
- ros-eloquent-examples-rclcpp-minimal-action-server-dbgsym: 0.8.2-1 -> 0.8.3-1
- ros-eloquent-examples-rclcpp-minimal-client: 0.8.2-1 -> 0.8.3-1
- ros-eloquent-examples-rclcpp-minimal-client-dbgsym: 0.8.2-1 -> 0.8.3-1
- ros-eloquent-examples-rclcpp-minimal-composition: 0.8.2-1 -> 0.8.3-1
- ros-eloquent-examples-rclcpp-minimal-composition-dbgsym: 0.8.2-1 -> 0.8.3-1
- ros-eloquent-examples-rclcpp-minimal-publisher: 0.8.2-1 -> 0.8.3-1
- ros-eloquent-examples-rclcpp-minimal-publisher-dbgsym: 0.8.2-1 -> 0.8.3-1
- ros-eloquent-examples-rclcpp-minimal-service: 0.8.2-1 -> 0.8.3-1
- ros-eloquent-examples-rclcpp-minimal-service-dbgsym: 0.8.2-1 -> 0.8.3-1
- ros-eloquent-examples-rclcpp-minimal-subscriber: 0.8.2-1 -> 0.8.3-1
- ros-eloquent-examples-rclcpp-minimal-subscriber-dbgsym: 0.8.2-1 -> 0.8.3-1
- ros-eloquent-examples-rclcpp-minimal-timer: 0.8.2-1 -> 0.8.3-1
- ros-eloquent-examples-rclcpp-minimal-timer-dbgsym: 0.8.2-1 -> 0.8.3-1
- ros-eloquent-examples-rclcpp-multithreaded-executor: 0.8.2-1 -> 0.8.3-1
- ros-eloquent-examples-rclcpp-multithreaded-executor-dbgsym: 0.8.2-1 -> 0.8.3-1
- ros-eloquent-examples-rclpy-executors: 0.8.2-1 -> 0.8.3-1
- ros-eloquent-examples-rclpy-minimal-action-client: 0.8.2-1 -> 0.8.3-1
- ros-eloquent-examples-rclpy-minimal-action-server: 0.8.2-1 -> 0.8.3-1
- ros-eloquent-examples-rclpy-minimal-client: 0.8.2-1 -> 0.8.3-1
- ros-eloquent-examples-rclpy-minimal-publisher: 0.8.2-1 -> 0.8.3-1
- ros-eloquent-examples-rclpy-minimal-service: 0.8.2-1 -> 0.8.3-1
- ros-eloquent-examples-rclpy-minimal-subscriber: 0.8.2-1 -> 0.8.3-1
- ros-eloquent-examples-tf2-py: 0.12.5-1 -> 0.12.6-1
- ros-eloquent-geometry2: 0.12.5-1 -> 0.12.6-1
- ros-eloquent-launch: 0.9.6-1 -> 0.9.7-1
- ros-eloquent-launch-ros: 0.9.5-1 -> 0.9.6-1
- ros-eloquent-launch-testing: 0.9.6-1 -> 0.9.7-1
- ros-eloquent-launch-testing-ament-cmake: 0.9.6-1 -> 0.9.7-1
- ros-eloquent-launch-testing-ros: 0.9.5-1 -> 0.9.6-1
- ros-eloquent-launch-xml: 0.9.6-1 -> 0.9.7-1
- ros-eloquent-launch-yaml: 0.9.6-1 -> 0.9.7-1
- ros-eloquent-marti-can-msgs: 1.1.0-1 -> 1.2.0-1
- ros-eloquent-marti-can-msgs-dbgsym: 1.1.0-1 -> 1.2.0-1
- ros-eloquent-marti-common-msgs: 1.1.0-1 -> 1.2.0-1
- ros-eloquent-marti-common-msgs-dbgsym: 1.1.0-1 -> 1.2.0-1
- ros-eloquent-marti-dbw-msgs: 1.1.0-1 -> 1.2.0-1
- ros-eloquent-marti-dbw-msgs-dbgsym: 1.1.0-1 -> 1.2.0-1
- ros-eloquent-marti-nav-msgs: 1.1.0-1 -> 1.2.0-1
- ros-eloquent-marti-nav-msgs-dbgsym: 1.1.0-1 -> 1.2.0-1
- ros-eloquent-marti-perception-msgs: 1.1.0-1 -> 1.2.0-1
- ros-eloquent-marti-perception-msgs-dbgsym: 1.1.0-1 -> 1.2.0-1
- ros-eloquent-marti-sensor-msgs: 1.1.0-1 -> 1.2.0-1
- ros-eloquent-marti-sensor-msgs-dbgsym: 1.1.0-1 -> 1.2.0-1
- ros-eloquent-marti-status-msgs: 1.1.0-1 -> 1.2.0-1
- ros-eloquent-marti-status-msgs-dbgsym: 1.1.0-1 -> 1.2.0-1
- ros-eloquent-marti-visualization-msgs: 1.1.0-1 -> 1.2.0-1
- ros-eloquent-marti-visualization-msgs-dbgsym: 1.1.0-1 -> 1.2.0-1
- ros-eloquent-mavlink: 2020.10.11-1 -> 2020.11.11-1
- ros-eloquent-pluginlib: 2.4.1-1 -> 2.4.2-1
- ros-eloquent-rc-genicam-api: 2.4.1-2 -> 2.4.4-1
- ros-eloquent-rc-genicam-api-dbgsym: 2.4.1-2 -> 2.4.4-1
- ros-eloquent-rcl: 0.8.4-1 -> 0.8.5-1
- ros-eloquent-rcl-action: 0.8.4-1 -> 0.8.5-1
- ros-eloquent-rcl-action-dbgsym: 0.8.4-1 -> 0.8.5-1
- ros-eloquent-rcl-dbgsym: 0.8.4-1 -> 0.8.5-1
- ros-eloquent-rcl-lifecycle: 0.8.4-1 -> 0.8.5-1
- ros-eloquent-rcl-lifecycle-dbgsym: 0.8.4-1 -> 0.8.5-1
- ros-eloquent-rcl-yaml-param-parser: 0.8.4-1 -> 0.8.5-1
- ros-eloquent-rcl-yaml-param-parser-dbgsym: 0.8.4-1 -> 0.8.5-1
- ros-eloquent-rclc: 0.1.2-1 -> 0.1.4-1
- ros-eloquent-rclc-dbgsym: 0.1.2-1 -> 0.1.4-1
- ros-eloquent-rclc-examples: 0.1.2-1 -> 0.1.4-1
- ros-eloquent-rclc-examples-dbgsym: 0.1.2-1 -> 0.1.4-1
- ros-eloquent-rclcpp: 0.8.4-1 -> 0.8.5-1
- ros-eloquent-rclcpp-action: 0.8.4-1 -> 0.8.5-1
- ros-eloquent-rclcpp-action-dbgsym: 0.8.4-1 -> 0.8.5-1
- ros-eloquent-rclcpp-components: 0.8.4-1 -> 0.8.5-1
- ros-eloquent-rclcpp-components-dbgsym: 0.8.4-1 -> 0.8.5-1
- ros-eloquent-rclcpp-dbgsym: 0.8.4-1 -> 0.8.5-1
- ros-eloquent-rclcpp-lifecycle: 0.8.4-1 -> 0.8.5-1
- ros-eloquent-rclcpp-lifecycle-dbgsym: 0.8.4-1 -> 0.8.5-1
- ros-eloquent-rclpy: 0.8.4-1 -> 0.8.5-1
- ros-eloquent-rclpy-dbgsym: 0.8.4-1 -> 0.8.5-1
- ros-eloquent-rcutils: 0.8.4-1 -> 0.8.5-1
- ros-eloquent-rcutils-dbgsym: 0.8.4-1 -> 0.8.5-1
- ros-eloquent-rmw-connext-cpp: 0.8.1-1 -> 0.8.2-1
- ros-eloquent-rmw-connext-cpp-dbgsym: 0.8.1-1 -> 0.8.2-1
- ros-eloquent-rmw-connext-shared-cpp: 0.8.1-1 -> 0.8.2-1
- ros-eloquent-rmw-connext-shared-cpp-dbgsym: 0.8.1-1 -> 0.8.2-1
- ros-eloquent-rmw-cyclonedds-cpp: 0.5.1-1 -> 0.7.0-1
- ros-eloquent-rmw-cyclonedds-cpp-dbgsym: 0.5.1-1 -> 0.7.0-1
- ros-eloquent-rmw-fastrtps-cpp: 0.8.1-1 -> 0.8.2-1
- ros-eloquent-rmw-fastrtps-cpp-dbgsym: 0.8.1-1 -> 0.8.2-1
- ros-eloquent-rmw-fastrtps-dynamic-cpp: 0.8.1-1 -> 0.8.2-1
- ros-eloquent-rmw-fastrtps-dynamic-cpp-dbgsym: 0.8.1-1 -> 0.8.2-1
- ros-eloquent-rmw-fastrtps-shared-cpp: 0.8.1-1 -> 0.8.2-1
- ros-eloquent-rmw-fastrtps-shared-cpp-dbgsym: 0.8.1-1 -> 0.8.2-1
- ros-eloquent-ros-base: 0.8.4-1 -> 0.8.5-1
- ros-eloquent-ros-core: 0.8.4-1 -> 0.8.5-1
- ros-eloquent-ros1-bridge: 0.8.2-3 -> 0.8.3-1
- ros-eloquent-ros1-bridge-dbgsym: 0.8.2-3 -> 0.8.3-1
- ros-eloquent-ros2action: 0.8.7-1 -> 0.8.8-1
- ros-eloquent-ros2cli: 0.8.7-1 -> 0.8.8-1
- ros-eloquent-ros2component: 0.8.7-1 -> 0.8.8-1
- ros-eloquent-ros2doctor: 0.8.7-1 -> 0.8.8-1
- ros-eloquent-ros2interface: 0.8.7-1 -> 0.8.8-1
- ros-eloquent-ros2launch: 0.9.5-1 -> 0.9.6-1
- ros-eloquent-ros2lifecycle: 0.8.7-1 -> 0.8.8-1
- ros-eloquent-ros2lifecycle-test-fixtures: 0.8.7-1 -> 0.8.8-1
- ros-eloquent-ros2lifecycle-test-fixtures-dbgsym: 0.8.7-1 -> 0.8.8-1
- ros-eloquent-ros2msg: 0.8.7-1 -> 0.8.8-1
- ros-eloquent-ros2multicast: 0.8.7-1 -> 0.8.8-1
- ros-eloquent-ros2node: 0.8.7-1 -> 0.8.8-1
- ros-eloquent-ros2param: 0.8.7-1 -> 0.8.8-1
- ros-eloquent-ros2pkg: 0.8.7-1 -> 0.8.8-1
- ros-eloquent-ros2run: 0.8.7-1 -> 0.8.8-1
- ros-eloquent-ros2service: 0.8.7-1 -> 0.8.8-1
- ros-eloquent-ros2srv: 0.8.7-1 -> 0.8.8-1
- ros-eloquent-ros2topic: 0.8.7-1 -> 0.8.8-1
- ros-eloquent-rosidl-adapter: 0.8.2-1 -> 0.8.3-1
- ros-eloquent-rosidl-cmake: 0.8.2-1 -> 0.8.3-1
- ros-eloquent-rosidl-generator-c: 0.8.2-1 -> 0.8.3-1
- ros-eloquent-rosidl-generator-c-dbgsym: 0.8.2-1 -> 0.8.3-1
- ros-eloquent-rosidl-generator-cpp: 0.8.2-1 -> 0.8.3-1
- ros-eloquent-rosidl-generator-py: 0.8.1-1 -> 0.8.2-1
- ros-eloquent-rosidl-parser: 0.8.2-1 -> 0.8.3-1
- ros-eloquent-rosidl-typesupport-c: 0.8.0-2 -> 0.8.1-1
- ros-eloquent-rosidl-typesupport-c-dbgsym: 0.8.0-2 -> 0.8.1-1
- ros-eloquent-rosidl-typesupport-cpp: 0.8.0-2 -> 0.8.1-1
- ros-eloquent-rosidl-typesupport-cpp-dbgsym: 0.8.0-2 -> 0.8.1-1
- ros-eloquent-rosidl-typesupport-interface: 0.8.2-1 -> 0.8.3-1
- ros-eloquent-rosidl-typesupport-introspection-c: 0.8.2-1 -> 0.8.3-1
- ros-eloquent-rosidl-typesupport-introspection-c-dbgsym: 0.8.2-1 -> 0.8.3-1
- ros-eloquent-rosidl-typesupport-introspection-cpp: 0.8.2-1 -> 0.8.3-1
- ros-eloquent-rosidl-typesupport-introspection-cpp-dbgsym: 0.8.2-1 -> 0.8.3-1
- ros-eloquent-rqt-robot-monitor: 1.0.3-1 -> 1.0.4-1
- ros-eloquent-rviz-assimp-vendor: 7.0.5-1 -> 7.0.7-1
- ros-eloquent-rviz-common: 7.0.5-1 -> 7.0.7-1
- ros-eloquent-rviz-common-dbgsym: 7.0.5-1 -> 7.0.7-1
- ros-eloquent-rviz-default-plugins: 7.0.5-1 -> 7.0.7-1
- ros-eloquent-rviz-default-plugins-dbgsym: 7.0.5-1 -> 7.0.7-1
- ros-eloquent-rviz-ogre-vendor: 7.0.5-1 -> 7.0.7-1
- ros-eloquent-rviz-ogre-vendor-dbgsym: 7.0.5-1 -> 7.0.7-1
- ros-eloquent-rviz-rendering: 7.0.5-1 -> 7.0.7-1
- ros-eloquent-rviz-rendering-dbgsym: 7.0.5-1 -> 7.0.7-1
- ros-eloquent-rviz-rendering-tests: 7.0.5-1 -> 7.0.7-1
- ros-eloquent-rviz-visual-testing-framework: 7.0.5-1 -> 7.0.7-1
- ros-eloquent-rviz2: 7.0.5-1 -> 7.0.7-1
- ros-eloquent-rviz2-dbgsym: 7.0.5-1 -> 7.0.7-1
- ros-eloquent-swri-console-util: 3.3.1-1 -> 3.3.2-1
- ros-eloquent-swri-dbw-interface: 3.3.1-1 -> 3.3.2-1
- ros-eloquent-swri-geometry-util: 3.3.1-1 -> 3.3.2-1
- ros-eloquent-swri-image-util: 3.3.1-1 -> 3.3.2-1
- ros-eloquent-swri-image-util-dbgsym: 3.3.1-1 -> 3.3.2-1
- ros-eloquent-swri-math-util: 3.3.1-1 -> 3.3.2-1
- ros-eloquent-swri-opencv-util: 3.3.1-1 -> 3.3.2-1
- ros-eloquent-swri-prefix-tools: 3.3.1-1 -> 3.3.2-1
- ros-eloquent-swri-roscpp: 3.3.1-1 -> 3.3.2-1
- ros-eloquent-swri-roscpp-dbgsym: 3.3.1-1 -> 3.3.2-1
- ros-eloquent-swri-route-util: 3.3.1-1 -> 3.3.2-1
- ros-eloquent-swri-serial-util: 3.3.1-1 -> 3.3.2-1
- ros-eloquent-swri-system-util: 3.3.1-1 -> 3.3.2-1
- ros-eloquent-swri-transform-util: 3.3.1-1 -> 3.3.2-1
- ros-eloquent-swri-transform-util-dbgsym: 3.3.1-1 -> 3.3.2-1
- ros-eloquent-tf2: 0.12.5-1 -> 0.12.6-1
- ros-eloquent-tf2-dbgsym: 0.12.5-1 -> 0.12.6-1
- ros-eloquent-tf2-eigen: 0.12.5-1 -> 0.12.6-1
- ros-eloquent-tf2-geometry-msgs: 0.12.5-1 -> 0.12.6-1
- ros-eloquent-tf2-kdl: 0.12.5-1 -> 0.12.6-1
- ros-eloquent-tf2-msgs: 0.12.5-1 -> 0.12.6-1
- ros-eloquent-tf2-msgs-dbgsym: 0.12.5-1 -> 0.12.6-1
- ros-eloquent-tf2-py: 0.12.5-1 -> 0.12.6-1
- ros-eloquent-tf2-py-dbgsym: 0.12.5-1 -> 0.12.6-1
- ros-eloquent-tf2-ros: 0.12.5-1 -> 0.12.6-1
- ros-eloquent-tf2-ros-dbgsym: 0.12.5-1 -> 0.12.6-1
- ros-eloquent-tf2-sensor-msgs: 0.12.5-1 -> 0.12.6-1
- ros-eloquent-xacro: 2.0.3-1 -> 2.0.4-1
Removed Packages [3]:
- ros-eloquent-cross-compile
- ros-eloquent-pinocchio
- ros-eloquent-pinocchio-dbgsym
Thanks to all ROS maintainers who make packages available to the ROS community. The above list of packages was made possible by the work of the following maintainers:
- Aaron Blasdel
- Alejandro Hernandez Cordero
- Anup Pemmaiah
- Chris Lalancette
- Claire Wang
- Dirk Thomas
- Eclipse Foundation, Inc.
- Erik Boasson
- Felix Ruess
- Ivan Paunovic
- Jacob Hassold
- Jacob Perron
- Jan Staschulat
- John Shepherd
- Juan Pablo Samper
- Karsten Knese
- Matthew Bries
- Michael Carroll
- Michel Hidalgo
- P. J. Reed
- Pete Baughman
- Robert Haschke
- Scott K Logan
- Shane Loretz
- Steven! Ragnarok
- Steven! Ragnarök
- Ted Kern
- Vladimir Ermakov
- William Woodall
6 posts - 4 participants
![[WWW] [WWW]](./rostheme/img/moin-www.png)
ROS Discourse General: New Packages for Noetic 2020/12/14
We’re happy to announce 37 new packages and 100 updates are now available in ROS Noetic. This sync was tagged as noetic/2020-12-14
.
Thank you to every maintainer and contributor who made these updates available!
Package Updates for ROS Noetic
Added Packages [37]:
- ros-noetic-carla-msgs: 1.2.0-1
- ros-noetic-cnpy: 0.0.2-1
- ros-noetic-cob-command-gui: 0.6.19-1
- ros-noetic-cob-command-tools: 0.6.19-1
- ros-noetic-cob-default-robot-behavior: 0.7.5-1
- ros-noetic-cob-default-robot-config: 0.7.5-1
- ros-noetic-cob-gazebo-objects: 0.7.5-1
- ros-noetic-cob-gazebo-tools: 0.7.5-1
- ros-noetic-cob-gazebo-worlds: 0.7.5-1
- ros-noetic-cob-hardware-config: 0.7.5-1
- ros-noetic-cob-moveit-config: 0.7.5-1
- ros-noetic-flexbe-behavior-engine: 1.3.0-1
- ros-noetic-flexbe-core: 1.3.0-1
- ros-noetic-flexbe-input: 1.3.0-1
- ros-noetic-flexbe-mirror: 1.3.0-1
- ros-noetic-flexbe-msgs: 1.3.0-1
- ros-noetic-flexbe-onboard: 1.3.0-1
- ros-noetic-flexbe-states: 1.3.0-1
- ros-noetic-flexbe-testing: 1.3.0-1
- ros-noetic-flexbe-widget: 1.3.0-1
- ros-noetic-librealsense2: 2.40.0-2
- ros-noetic-log-view: 0.1.2-1
- ros-noetic-odva-ethernetip: 0.1.5-1
- ros-noetic-pilz-industrial-motion-testutils: 0.7.0-1
- ros-noetic-pilz-msgs: 0.7.0-1
- ros-noetic-pilz-testutils: 0.7.0-1
- ros-noetic-pilz-utils: 0.7.0-1
- ros-noetic-plotjuggler-ros: 1.0.0-1
- ros-noetic-pr2-controller-interface: 1.8.18-1
- ros-noetic-pr2-controller-manager: 1.8.18-1
- ros-noetic-pr2-hardware-interface: 1.8.18-1
- ros-noetic-pr2-mechanism: 1.8.18-1
- ros-noetic-pr2-mechanism-diagnostics: 1.8.18-1
- ros-noetic-pr2-mechanism-model: 1.8.18-1
- ros-noetic-sob-layer: 0.1.0-1
- ros-noetic-stag-ros: 0.3.6-3
- ros-noetic-video-stream-opencv: 1.1.6-1
Updated Packages [100]:
- ros-noetic-ackermann-steering-controller: 0.17.0-1 -> 0.18.1-1
- ros-noetic-cob-dashboard: 0.6.18-1 -> 0.6.19-1
- ros-noetic-cob-helper-tools: 0.6.18-1 -> 0.6.19-1
- ros-noetic-cob-interactive-teleop: 0.6.18-1 -> 0.6.19-1
- ros-noetic-cob-monitoring: 0.6.18-1 -> 0.6.19-1
- ros-noetic-cob-script-server: 0.6.18-1 -> 0.6.19-1
- ros-noetic-cob-teleop: 0.6.18-1 -> 0.6.19-1
- ros-noetic-combined-robot-hw: 0.19.3-2 -> 0.19.4-1
- ros-noetic-combined-robot-hw-tests: 0.19.3-2 -> 0.19.4-1
- ros-noetic-controller-interface: 0.19.3-2 -> 0.19.4-1
- ros-noetic-controller-manager: 0.19.3-2 -> 0.19.4-1
- ros-noetic-controller-manager-msgs: 0.19.3-2 -> 0.19.4-1
- ros-noetic-controller-manager-tests: 0.19.3-2 -> 0.19.4-1
- ros-noetic-diagnostic-aggregator: 1.10.2-3 -> 1.10.3-1
- ros-noetic-diagnostic-analysis: 1.10.2-3 -> 1.10.3-1
- ros-noetic-diagnostic-common-diagnostics: 1.10.2-3 -> 1.10.3-1
- ros-noetic-diagnostic-updater: 1.10.2-3 -> 1.10.3-1
- ros-noetic-diagnostics: 1.10.2-3 -> 1.10.3-1
- ros-noetic-diff-drive-controller: 0.17.0-1 -> 0.18.1-1
- ros-noetic-effort-controllers: 0.17.0-1 -> 0.18.1-1
- ros-noetic-exotica: 6.0.1-1 -> 6.0.2-1
- ros-noetic-exotica-aico-solver: 6.0.1-1 -> 6.0.2-1
- ros-noetic-exotica-cartpole-dynamics-solver: 6.0.1-1 -> 6.0.2-1
- ros-noetic-exotica-collision-scene-fcl-latest: 6.0.1-1 -> 6.0.2-1
- ros-noetic-exotica-core: 6.0.1-1 -> 6.0.2-1
- ros-noetic-exotica-core-task-maps: 6.0.1-1 -> 6.0.2-1
- ros-noetic-exotica-ddp-solver: 6.0.1-1 -> 6.0.2-1
- ros-noetic-exotica-double-integrator-dynamics-solver: 6.0.1-1 -> 6.0.2-1
- ros-noetic-exotica-dynamics-solvers: 6.0.1-1 -> 6.0.2-1
- ros-noetic-exotica-examples: 6.0.1-1 -> 6.0.2-1
- ros-noetic-exotica-ik-solver: 6.0.1-1 -> 6.0.2-1
- ros-noetic-exotica-ilqg-solver: 6.0.1-1 -> 6.0.2-1
- ros-noetic-exotica-ilqr-solver: 6.0.1-1 -> 6.0.2-1
- ros-noetic-exotica-levenberg-marquardt-solver: 6.0.1-1 -> 6.0.2-1
- ros-noetic-exotica-ompl-control-solver: 6.0.1-1 -> 6.0.2-1
- ros-noetic-exotica-ompl-solver: 6.0.1-1 -> 6.0.2-1
- ros-noetic-exotica-pendulum-dynamics-solver: 6.0.1-1 -> 6.0.2-1
- ros-noetic-exotica-pinocchio-dynamics-solver: 6.0.1-1 -> 6.0.2-1
- ros-noetic-exotica-python: 6.0.1-1 -> 6.0.2-1
- ros-noetic-exotica-quadrotor-dynamics-solver: 6.0.1-1 -> 6.0.2-1
- ros-noetic-exotica-scipy-solver: 6.0.1-1 -> 6.0.2-1
- ros-noetic-exotica-time-indexed-rrt-connect-solver: 6.0.1-1 -> 6.0.2-1
- ros-noetic-fkie-master-discovery: 1.2.3-1 -> 1.2.5-2
- ros-noetic-fkie-master-sync: 1.2.3-1 -> 1.2.5-2
- ros-noetic-fkie-multimaster: 1.2.3-1 -> 1.2.5-2
- ros-noetic-fkie-multimaster-msgs: 1.2.3-1 -> 1.2.5-2
- ros-noetic-fkie-node-manager: 1.2.3-1 -> 1.2.5-2
- ros-noetic-fkie-node-manager-daemon: 1.2.3-1 -> 1.2.5-2
- ros-noetic-force-torque-sensor-controller: 0.17.0-1 -> 0.18.1-1
- ros-noetic-forward-command-controller: 0.17.0-1 -> 0.18.1-1
- ros-noetic-four-wheel-steering-controller: 0.17.0-1 -> 0.18.1-1
- ros-noetic-generic-throttle: 0.6.18-1 -> 0.6.19-1
- ros-noetic-gripper-action-controller: 0.17.0-1 -> 0.18.1-1
- ros-noetic-hardware-interface: 0.19.3-2 -> 0.19.4-1
- ros-noetic-imu-sensor-controller: 0.17.0-1 -> 0.18.1-1
- ros-noetic-joint-limits-interface: 0.19.3-2 -> 0.19.4-1
- ros-noetic-joint-state-controller: 0.17.0-1 -> 0.18.1-1
- ros-noetic-joint-trajectory-controller: 0.17.0-1 -> 0.18.1-1
- ros-noetic-leo-gazebo: 0.1.2-1 -> 0.1.3-1
- ros-noetic-leo-simulator: 0.1.2-1 -> 0.1.3-1
- ros-noetic-lvr2: 20.11.1-1 -> 20.11.2-1
- ros-noetic-mbf-abstract-core: 0.3.3-1 -> 0.3.4-1
- ros-noetic-mbf-abstract-nav: 0.3.3-1 -> 0.3.4-1
- ros-noetic-mbf-costmap-core: 0.3.3-1 -> 0.3.4-1
- ros-noetic-mbf-costmap-nav: 0.3.3-1 -> 0.3.4-1
- ros-noetic-mbf-msgs: 0.3.3-1 -> 0.3.4-1
- ros-noetic-mbf-simple-nav: 0.3.3-1 -> 0.3.4-1
- ros-noetic-mbf-utility: 0.3.3-1 -> 0.3.4-1
- ros-noetic-move-base-flex: 0.3.3-1 -> 0.3.4-1
- ros-noetic-ompl: 1.5.0-1 -> 1.5.1-1
- ros-noetic-plotjuggler: 3.0.1-1 -> 3.0.4-1
- ros-noetic-position-controllers: 0.17.0-1 -> 0.18.1-1
- ros-noetic-rc-common-msgs: 0.5.0-1 -> 0.5.3-1
- ros-noetic-rc-genicam-driver: 0.2.0-1 -> 0.4.0-1
- ros-noetic-rc-hand-eye-calibration-client: 3.0.5-1 -> 3.1.0-1
- ros-noetic-rc-pick-client: 3.0.5-1 -> 3.1.0-1
- ros-noetic-rc-roi-manager-gui: 3.0.5-1 -> 3.1.0-1
- ros-noetic-rc-silhouettematch-client: 3.0.5-1 -> 3.1.0-1
- ros-noetic-rc-tagdetect-client: 3.0.5-1 -> 3.1.0-1
- ros-noetic-rc-visard: 3.0.5-1 -> 3.1.0-1
- ros-noetic-rc-visard-description: 3.0.5-1 -> 3.1.0-1
- ros-noetic-rc-visard-driver: 3.0.5-1 -> 3.1.0-1
- ros-noetic-ros-control: 0.19.3-2 -> 0.19.4-1
- ros-noetic-ros-controllers: 0.17.0-1 -> 0.18.1-1
- ros-noetic-rosapi: 0.11.10-1 -> 0.11.12-1
- ros-noetic-rosbridge-library: 0.11.10-1 -> 0.11.12-1
- ros-noetic-rosbridge-msgs: 0.11.10-1 -> 0.11.12-1
- ros-noetic-rosbridge-server: 0.11.10-1 -> 0.11.12-1
- ros-noetic-rosbridge-suite: 0.11.10-1 -> 0.11.12-1
- ros-noetic-rosdiagnostic: 1.10.2-3 -> 1.10.3-1
- ros-noetic-rqt-controller-manager: 0.19.3-2 -> 0.19.4-1
- ros-noetic-rqt-joint-trajectory-controller: 0.17.0-1 -> 0.18.1-1
- ros-noetic-scenario-test-tools: 0.6.18-1 -> 0.6.19-1
- ros-noetic-self-test: 1.10.2-3 -> 1.10.3-1
- ros-noetic-service-tools: 0.6.18-1 -> 0.6.19-1
- ros-noetic-test-diagnostic-aggregator: 1.10.2-3 -> 1.10.3-1
- ros-noetic-transmission-interface: 0.19.3-2 -> 0.19.4-1
- ros-noetic-tsid: 1.4.1-2 -> 1.4.2-1
- ros-noetic-urdfdom-py: 0.4.4-1 -> 0.4.5-1
- ros-noetic-velocity-controllers: 0.17.0-1 -> 0.18.1-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:
- Alexander Gutenkunst
- Alexander Tiderko
- Bence Magyar
- Brennan Cain
- Błażej Sowa
- CARLA Simulator Team
- Chris Lalancette
- Christian Rauch
- Davide Faconti
- Dima Dorezyuk
- Felix Messmer
- Felix Ruess
- Guglielmo Gemignani
- Guilhem Saurel
- Guillaume Autran
- Hans-Joachim Krauch
- Jannik Abbenseth
- Jorge Santos
- Loy van Beek
- Marc Alban
- Mark Moll
- Masaru Morita
- Monika Florek-Jasinska
- Peter Mitrano
- Philipp Schillinger
- ROS Orphaned Package Maintainers
- Rein Appeldoorn
- Richard Bormann
- Russell Toris
- Sachin Chitta
- Sammy Pfeiffer
- Sebastian Pütz
- Sergey Dorodnicov
- Traiko Dinev
- Vincent Rousseau
- Vladimir Ivan
- Wolfgang Merkt
1 post - 1 participant
![[WWW] [WWW]](./rostheme/img/moin-www.png)
ROS Discourse General: Cybersecurity for Robotics Free online conference
Dear All,
Following our start last year in Bilbao, we’re still welcoming you to the up and coming CSfR2020 conference.
Looking forward joining in on two afternoons of great insights on the basics, the future and some hacks and vulnerabilities to keep you mindful about the security of the robots …
Register today for the CyberSecurity for Robotics conference taking place this Thursday and Friday afternoon, December 17th and 18th from 2pm CET, 8am EST.
During two afternoons we’ll be considering
industrial cybersecurity
standardization ,
up and coming approaches for a shared responsibility model,
current challenges in relation to cybersecurity and safety,
and approaches to improve cybersecurity including the ways AI and autonomous systems can be tricked.
Attendance is free, registration is mandatory. Upon registration, you will receive a link to the Zoom webinar for both
December 17th and
December 18th.
Please do also inform your networks, partners and stakeholders.
- The Basics : the IEC62443 – industrial cybersecurity vs robots … safety vs security
- SROS2 : howto, limitations and future perspectives
- Adversarial AI machine learning and behavioral learnings, some experiences from
- And … the guy that stole my Tesla … can steal your robot vacuum cleaner
(or basically any robot … )
- The future : industrial perspectives, SBOM, future of SROS, ISA99 and ofcourse the impact of AI on the robots.
For more information about the program and registration, please visit : https://cybersecurityforrobotics.com/conference-csfr2020/
1 post - 1 participant
![[WWW] [WWW]](./rostheme/img/moin-www.png)
ROS Discourse General: TurtleBot3 and Webots 🐞!
Since the release of ROS2 Foxy, we are determined to deliver new features and bug fixes on each Foxy sync. This time, we released a new package that demonstrates TurtleBot’s (TurtleBot3 Burger from ROBOTIS) mapping and navigation capabilities in Webots.
Upgrade your Foxy packages, install ros-foxy-webots-ros2
and try it out!
Cartographer Tutorial:
https://github.com/cyberbotics/webots_ros2/wiki/SLAM-with-TurtleBot3
Navigation2 Tutorial:
https://github.com/cyberbotics/webots_ros2/wiki/Navigate-TurtleBot3
We will be happy to hear your suggestions about it.
1 post - 1 participant
![[WWW] [WWW]](./rostheme/img/moin-www.png)
ROS Discourse General: ROS Tutorial 100% en español
Tutorial de ROS 100% en español!!!
1 post - 1 participant
![[WWW] [WWW]](./rostheme/img/moin-www.png)
ROS Discourse General: New packages and patch release for ROS 2 Foxy Fitzroy 2020-12-11
We’re happy to announce a new Foxy release!
This sync brings a number of new packages as well as updates to ROS 2 core packages. For a list of patches to core packages, see the project board on GitHub.
Package Updates for foxy
Added Packages [28]:
- ros-foxy-bond: 2.0.0-1
- ros-foxy-geometric-shapes: 2.0.0-1
- ros-foxy-moveit-msgs: 2.0.0-1
- ros-foxy-moveit-resources: 2.0.0-1
- ros-foxy-moveit-resources-fanuc-description: 2.0.0-1
- ros-foxy-moveit-resources-fanuc-moveit-config: 2.0.0-1
- ros-foxy-moveit-resources-panda-description: 2.0.0-1
- ros-foxy-moveit-resources-panda-moveit-config: 2.0.0-1
- ros-foxy-moveit-resources-pr2-description: 2.0.0-1
- ros-foxy-plotjuggler: 3.0.4-1
- ros-foxy-plotjuggler-ros: 1.0.0-2
- ros-foxy-raspimouse: 1.0.2-1
- ros-foxy-raspimouse-msgs: 1.0.2-1
- ros-foxy-rclc-lifecycle: 0.1.4-1
- ros-foxy-robot-controllers: 0.8.1-1
- ros-foxy-robot-controllers-interface: 0.8.1-1
- ros-foxy-robot-controllers-msgs: 0.8.1-1
- ros-foxy-rt-usb-9axisimu-driver: 2.0.1-1
- ros-foxy-simple-launch: 1.0.2-1
- ros-foxy-smac-planner: 0.4.5-1
- ros-foxy-smclib: 2.0.0-1
- ros-foxy-srdfdom: 2.0.0-1
- ros-foxy-tf2-eigen-kdl: 0.13.9-1
- ros-foxy-vrxperience-bridge: 1.0.0-1
- ros-foxy-vrxperience-msgs: 1.0.0-1
- ros-foxy-warehouse-ros: 2.0.0-1
- ros-foxy-webots-ros2-turtlebot: 1.0.3-1
- ros-foxy-webots-ros2-tutorials: 1.0.3-1
Updated Packages [228]:
- ros-foxy-ament-clang-format: 0.9.5-1 -> 0.9.6-1
- ros-foxy-ament-clang-tidy: 0.9.5-1 -> 0.9.6-1
- ros-foxy-ament-cmake: 0.9.7-1 -> 0.9.8-1
- ros-foxy-ament-cmake-auto: 0.9.7-1 -> 0.9.8-1
- ros-foxy-ament-cmake-clang-format: 0.9.5-1 -> 0.9.6-1
- ros-foxy-ament-cmake-clang-tidy: 0.9.5-1 -> 0.9.6-1
- ros-foxy-ament-cmake-copyright: 0.9.5-1 -> 0.9.6-1
- ros-foxy-ament-cmake-core: 0.9.7-1 -> 0.9.8-1
- ros-foxy-ament-cmake-cppcheck: 0.9.5-1 -> 0.9.6-1
- ros-foxy-ament-cmake-cpplint: 0.9.5-1 -> 0.9.6-1
- ros-foxy-ament-cmake-export-definitions: 0.9.7-1 -> 0.9.8-1
- ros-foxy-ament-cmake-export-dependencies: 0.9.7-1 -> 0.9.8-1
- ros-foxy-ament-cmake-export-include-directories: 0.9.7-1 -> 0.9.8-1
- ros-foxy-ament-cmake-export-interfaces: 0.9.7-1 -> 0.9.8-1
- ros-foxy-ament-cmake-export-libraries: 0.9.7-1 -> 0.9.8-1
- ros-foxy-ament-cmake-export-link-flags: 0.9.7-1 -> 0.9.8-1
- ros-foxy-ament-cmake-export-targets: 0.9.7-1 -> 0.9.8-1
- ros-foxy-ament-cmake-flake8: 0.9.5-1 -> 0.9.6-1
- ros-foxy-ament-cmake-gmock: 0.9.7-1 -> 0.9.8-1
- ros-foxy-ament-cmake-google-benchmark: 0.9.7-1 -> 0.9.8-1
- ros-foxy-ament-cmake-gtest: 0.9.7-1 -> 0.9.8-1
- ros-foxy-ament-cmake-include-directories: 0.9.7-1 -> 0.9.8-1
- ros-foxy-ament-cmake-libraries: 0.9.7-1 -> 0.9.8-1
- ros-foxy-ament-cmake-lint-cmake: 0.9.5-1 -> 0.9.6-1
- ros-foxy-ament-cmake-mypy: 0.9.5-1 -> 0.9.6-1
- ros-foxy-ament-cmake-nose: 0.9.7-1 -> 0.9.8-1
- ros-foxy-ament-cmake-pclint: 0.9.5-1 -> 0.9.6-1
- ros-foxy-ament-cmake-pep257: 0.9.5-1 -> 0.9.6-1
- ros-foxy-ament-cmake-pycodestyle: 0.9.5-1 -> 0.9.6-1
- ros-foxy-ament-cmake-pyflakes: 0.9.5-1 -> 0.9.6-1
- ros-foxy-ament-cmake-pytest: 0.9.7-1 -> 0.9.8-1
- ros-foxy-ament-cmake-python: 0.9.7-1 -> 0.9.8-1
- ros-foxy-ament-cmake-target-dependencies: 0.9.7-1 -> 0.9.8-1
- ros-foxy-ament-cmake-test: 0.9.7-1 -> 0.9.8-1
- ros-foxy-ament-cmake-uncrustify: 0.9.5-1 -> 0.9.6-1
- ros-foxy-ament-cmake-version: 0.9.7-1 -> 0.9.8-1
- ros-foxy-ament-cmake-xmllint: 0.9.5-1 -> 0.9.6-1
- ros-foxy-ament-copyright: 0.9.5-1 -> 0.9.6-1
- ros-foxy-ament-cppcheck: 0.9.5-1 -> 0.9.6-1
- ros-foxy-ament-cpplint: 0.9.5-1 -> 0.9.6-1
- ros-foxy-ament-flake8: 0.9.5-1 -> 0.9.6-1
- ros-foxy-ament-lint: 0.9.5-1 -> 0.9.6-1
- ros-foxy-ament-lint-auto: 0.9.5-1 -> 0.9.6-1
- ros-foxy-ament-lint-cmake: 0.9.5-1 -> 0.9.6-1
- ros-foxy-ament-lint-common: 0.9.5-1 -> 0.9.6-1
- ros-foxy-ament-mypy: 0.9.5-1 -> 0.9.6-1
- ros-foxy-ament-package: 0.9.2-1 -> 0.9.3-1
- ros-foxy-ament-pclint: 0.9.5-1 -> 0.9.6-1
- ros-foxy-ament-pep257: 0.9.5-1 -> 0.9.6-1
- ros-foxy-ament-pycodestyle: 0.9.5-1 -> 0.9.6-1
- ros-foxy-ament-pyflakes: 0.9.5-1 -> 0.9.6-1
- ros-foxy-ament-uncrustify: 0.9.5-1 -> 0.9.6-1
- ros-foxy-ament-xmllint: 0.9.5-1 -> 0.9.6-1
- ros-foxy-console-bridge-vendor: 1.2.2-1 -> 1.2.3-1
- ros-foxy-costmap-queue: 0.4.3-1 -> 0.4.5-1
- ros-foxy-dwb-core: 0.4.3-1 -> 0.4.5-1
- ros-foxy-dwb-critics: 0.4.3-1 -> 0.4.5-1
- ros-foxy-dwb-msgs: 0.4.3-1 -> 0.4.5-1
- ros-foxy-dwb-plugins: 0.4.3-1 -> 0.4.5-1
- ros-foxy-examples-rclcpp-minimal-action-client: 0.9.3-1 -> 0.9.4-1
- ros-foxy-examples-rclcpp-minimal-action-server: 0.9.3-1 -> 0.9.4-1
- ros-foxy-examples-rclcpp-minimal-client: 0.9.3-1 -> 0.9.4-1
- ros-foxy-examples-rclcpp-minimal-composition: 0.9.3-1 -> 0.9.4-1
- ros-foxy-examples-rclcpp-minimal-publisher: 0.9.3-1 -> 0.9.4-1
- ros-foxy-examples-rclcpp-minimal-service: 0.9.3-1 -> 0.9.4-1
- ros-foxy-examples-rclcpp-minimal-subscriber: 0.9.3-1 -> 0.9.4-1
- ros-foxy-examples-rclcpp-minimal-timer: 0.9.3-1 -> 0.9.4-1
- ros-foxy-examples-rclcpp-multithreaded-executor: 0.9.3-1 -> 0.9.4-1
- ros-foxy-examples-rclpy-executors: 0.9.3-1 -> 0.9.4-1
- ros-foxy-examples-rclpy-minimal-action-client: 0.9.3-1 -> 0.9.4-1
- ros-foxy-examples-rclpy-minimal-action-server: 0.9.3-1 -> 0.9.4-1
- ros-foxy-examples-rclpy-minimal-client: 0.9.3-1 -> 0.9.4-1
- ros-foxy-examples-rclpy-minimal-publisher: 0.9.3-1 -> 0.9.4-1
- ros-foxy-examples-rclpy-minimal-service: 0.9.3-1 -> 0.9.4-1
- ros-foxy-examples-rclpy-minimal-subscriber: 0.9.3-1 -> 0.9.4-1
- ros-foxy-examples-tf2-py: 0.13.6-1 -> 0.13.9-1
- ros-foxy-fastrtps: 2.0.1-1 -> 2.0.2-1
- ros-foxy-fastrtps-cmake-module: 1.0.1-1 -> 1.0.2-1
- ros-foxy-geometry2: 0.13.6-1 -> 0.13.9-1
- ros-foxy-gurumdds-cmake-module: 1.0.2-1 -> 1.0.3-1
- ros-foxy-interactive-markers: 2.1.2-1 -> 2.1.3-1
- ros-foxy-launch: 0.10.3-1 -> 0.10.4-1
- ros-foxy-launch-ros: 0.11.0-1 -> 0.11.1-1
- ros-foxy-launch-testing: 0.10.3-1 -> 0.10.4-1
- ros-foxy-launch-testing-ament-cmake: 0.10.3-1 -> 0.10.4-1
- ros-foxy-launch-testing-ros: 0.11.0-1 -> 0.11.1-1
- ros-foxy-launch-xml: 0.10.3-1 -> 0.10.4-1
- ros-foxy-launch-yaml: 0.10.3-1 -> 0.10.4-1
- ros-foxy-libcurl-vendor: 2.3.3-1 -> 2.3.4-1
- ros-foxy-marti-can-msgs: 1.1.0-1 -> 1.2.0-1
- ros-foxy-marti-common-msgs: 1.1.0-1 -> 1.2.0-1
- ros-foxy-marti-dbw-msgs: 1.1.0-1 -> 1.2.0-1
- ros-foxy-marti-nav-msgs: 1.1.0-1 -> 1.2.0-1
- ros-foxy-marti-perception-msgs: 1.1.0-1 -> 1.2.0-1
- ros-foxy-marti-sensor-msgs: 1.1.0-1 -> 1.2.0-1
- ros-foxy-marti-status-msgs: 1.1.0-1 -> 1.2.0-1
- ros-foxy-marti-visualization-msgs: 1.1.0-1 -> 1.2.0-1
- ros-foxy-mavlink: 2020.10.11-1 -> 2020.11.11-1
- ros-foxy-mimick-vendor: 0.2.2-1 -> 0.2.3-1
- ros-foxy-nav-2d-msgs: 0.4.3-1 -> 0.4.5-1
- ros-foxy-nav-2d-utils: 0.4.3-1 -> 0.4.5-1
- ros-foxy-nav2-amcl: 0.4.3-1 -> 0.4.5-1
- ros-foxy-nav2-behavior-tree: 0.4.3-1 -> 0.4.5-1
- ros-foxy-nav2-bringup: 0.4.3-1 -> 0.4.5-1
- ros-foxy-nav2-bt-navigator: 0.4.3-1 -> 0.4.5-1
- ros-foxy-nav2-common: 0.4.3-1 -> 0.4.5-1
- ros-foxy-nav2-controller: 0.4.3-1 -> 0.4.5-1
- ros-foxy-nav2-core: 0.4.3-1 -> 0.4.5-1
- ros-foxy-nav2-costmap-2d: 0.4.3-1 -> 0.4.5-1
- ros-foxy-nav2-dwb-controller: 0.4.3-1 -> 0.4.5-1
- ros-foxy-nav2-gazebo-spawner: 0.4.3-1 -> 0.4.5-1
- ros-foxy-nav2-lifecycle-manager: 0.4.3-1 -> 0.4.5-1
- ros-foxy-nav2-map-server: 0.4.3-1 -> 0.4.5-1
- ros-foxy-nav2-msgs: 0.4.3-1 -> 0.4.5-1
- ros-foxy-nav2-navfn-planner: 0.4.3-1 -> 0.4.5-1
- ros-foxy-nav2-planner: 0.4.3-1 -> 0.4.5-1
- ros-foxy-nav2-recoveries: 0.4.3-1 -> 0.4.5-1
- ros-foxy-nav2-rviz-plugins: 0.4.3-1 -> 0.4.5-1
- ros-foxy-nav2-system-tests: 0.4.3-1 -> 0.4.5-1
- ros-foxy-nav2-util: 0.4.3-1 -> 0.4.5-1
- ros-foxy-nav2-voxel-grid: 0.4.3-1 -> 0.4.5-1
- ros-foxy-nav2-waypoint-follower: 0.4.3-1 -> 0.4.5-1
- ros-foxy-navigation2: 0.4.3-1 -> 0.4.5-1
- ros-foxy-nodl-python: 0.3.0-1 -> 0.3.1-1
- ros-foxy-performance-test-fixture: 0.0.5-1 -> 0.0.6-1
- ros-foxy-pluginlib: 2.5.2-1 -> 2.5.3-1
- ros-foxy-py-trees: 2.1.1-1 -> 2.1.2-1
- ros-foxy-random-numbers: 1.0.0-1 -> 2.0.0-1
- ros-foxy-rcl: 1.1.9-1 -> 1.1.10-1
- ros-foxy-rcl-action: 1.1.9-1 -> 1.1.10-1
- ros-foxy-rcl-lifecycle: 1.1.9-1 -> 1.1.10-1
- ros-foxy-rcl-yaml-param-parser: 1.1.9-1 -> 1.1.10-1
- ros-foxy-rclc: 0.1.2-1 -> 0.1.4-1
- ros-foxy-rclc-examples: 0.1.2-1 -> 0.1.4-1
- ros-foxy-rclcpp: 2.2.0-1 -> 2.3.0-1
- ros-foxy-rclcpp-action: 2.2.0-1 -> 2.3.0-1
- ros-foxy-rclcpp-components: 2.2.0-1 -> 2.3.0-1
- ros-foxy-rclcpp-lifecycle: 2.2.0-1 -> 2.3.0-1
- ros-foxy-rcutils: 1.1.1-1 -> 1.1.2-1
- ros-foxy-resource-retriever: 2.3.3-1 -> 2.3.4-1
- ros-foxy-rmw-connext-cpp: 1.0.2-1 -> 1.0.3-1
- ros-foxy-rmw-connext-shared-cpp: 1.0.2-1 -> 1.0.3-1
- ros-foxy-rmw-cyclonedds-cpp: 0.7.5-1 -> 0.7.6-1
- ros-foxy-rmw-dds-common: 1.0.1-1 -> 1.0.2-1
- ros-foxy-rmw-fastrtps-cpp: 1.2.2-1 -> 1.2.4-1
- ros-foxy-rmw-fastrtps-dynamic-cpp: 1.2.2-1 -> 1.2.4-1
- ros-foxy-rmw-fastrtps-shared-cpp: 1.2.2-1 -> 1.2.4-1
- ros-foxy-rmw-gurumdds-cpp: 1.0.2-1 -> 1.0.3-1
- ros-foxy-rmw-gurumdds-shared-cpp: 1.0.2-1 -> 1.0.3-1
- ros-foxy-ros1-bridge: 0.9.4-1 -> 0.9.6-1
- ros-foxy-ros2action: 0.9.7-1 -> 0.9.8-1
- ros-foxy-ros2cli: 0.9.7-1 -> 0.9.8-1
- ros-foxy-ros2component: 0.9.7-1 -> 0.9.8-1
- ros-foxy-ros2doctor: 0.9.7-1 -> 0.9.8-1
- ros-foxy-ros2interface: 0.9.7-1 -> 0.9.8-1
- ros-foxy-ros2launch: 0.11.0-1 -> 0.11.1-1
- ros-foxy-ros2lifecycle: 0.9.7-1 -> 0.9.8-1
- ros-foxy-ros2lifecycle-test-fixtures: 0.9.7-1 -> 0.9.8-1
- ros-foxy-ros2multicast: 0.9.7-1 -> 0.9.8-1
- ros-foxy-ros2node: 0.9.7-1 -> 0.9.8-1
- ros-foxy-ros2nodl: 0.3.0-1 -> 0.3.1-1
- ros-foxy-ros2param: 0.9.7-1 -> 0.9.8-1
- ros-foxy-ros2pkg: 0.9.7-1 -> 0.9.8-1
- ros-foxy-ros2run: 0.9.7-1 -> 0.9.8-1
- ros-foxy-ros2service: 0.9.7-1 -> 0.9.8-1
- ros-foxy-ros2topic: 0.9.7-1 -> 0.9.8-1
- ros-foxy-rosidl-adapter: 1.1.0-1 -> 1.2.0-1
- ros-foxy-rosidl-cmake: 1.1.0-1 -> 1.2.0-1
- ros-foxy-rosidl-generator-c: 1.1.0-1 -> 1.2.0-1
- ros-foxy-rosidl-generator-cpp: 1.1.0-1 -> 1.2.0-1
- ros-foxy-rosidl-generator-py: 0.9.3-1 -> 0.9.4-1
- ros-foxy-rosidl-parser: 1.1.0-1 -> 1.2.0-1
- ros-foxy-rosidl-runtime-c: 1.1.0-1 -> 1.2.0-1
- ros-foxy-rosidl-runtime-cpp: 1.1.0-1 -> 1.2.0-1
- ros-foxy-rosidl-typesupport-c: 1.0.0-1 -> 1.0.1-1
- ros-foxy-rosidl-typesupport-cpp: 1.0.0-1 -> 1.0.1-1
- ros-foxy-rosidl-typesupport-fastrtps-c: 1.0.1-1 -> 1.0.2-1
- ros-foxy-rosidl-typesupport-fastrtps-cpp: 1.0.1-1 -> 1.0.2-1
- ros-foxy-rosidl-typesupport-interface: 1.1.0-1 -> 1.2.0-1
- ros-foxy-rosidl-typesupport-introspection-c: 1.1.0-1 -> 1.2.0-1
- ros-foxy-rosidl-typesupport-introspection-cpp: 1.1.0-1 -> 1.2.0-1
- ros-foxy-rqt-robot-monitor: 1.0.3-1 -> 1.0.4-1
- ros-foxy-rviz-assimp-vendor: 8.2.0-1 -> 8.2.1-1
- ros-foxy-rviz-common: 8.2.0-1 -> 8.2.1-1
- ros-foxy-rviz-default-plugins: 8.2.0-1 -> 8.2.1-1
- ros-foxy-rviz-ogre-vendor: 8.2.0-1 -> 8.2.1-1
- ros-foxy-rviz-rendering: 8.2.0-1 -> 8.2.1-1
- ros-foxy-rviz-rendering-tests: 8.2.0-1 -> 8.2.1-1
- ros-foxy-rviz-visual-testing-framework: 8.2.0-1 -> 8.2.1-1
- ros-foxy-rviz2: 8.2.0-1 -> 8.2.1-1
- ros-foxy-sros2: 0.9.3-1 -> 0.9.4-1
- ros-foxy-sros2-cmake: 0.9.3-1 -> 0.9.4-1
- ros-foxy-swri-console-util: 3.3.1-1 -> 3.3.2-1
- ros-foxy-swri-dbw-interface: 3.3.1-1 -> 3.3.2-1
- ros-foxy-swri-geometry-util: 3.3.1-1 -> 3.3.2-1
- ros-foxy-swri-image-util: 3.3.1-1 -> 3.3.2-1
- ros-foxy-swri-math-util: 3.3.1-1 -> 3.3.2-1
- ros-foxy-swri-opencv-util: 3.3.1-1 -> 3.3.2-1
- ros-foxy-swri-prefix-tools: 3.3.1-1 -> 3.3.2-1
- ros-foxy-swri-roscpp: 3.3.1-1 -> 3.3.2-1
- ros-foxy-swri-route-util: 3.3.1-1 -> 3.3.2-1
- ros-foxy-swri-serial-util: 3.3.1-1 -> 3.3.2-1
- ros-foxy-swri-system-util: 3.3.1-1 -> 3.3.2-1
- ros-foxy-swri-transform-util: 3.3.1-1 -> 3.3.2-1
- ros-foxy-teleop-twist-joy: 2.3.0-1 -> 2.4.1-1
- ros-foxy-tf2: 0.13.6-1 -> 0.13.9-1
- ros-foxy-tf2-bullet: 0.13.6-1 -> 0.13.9-1
- ros-foxy-tf2-eigen: 0.13.6-1 -> 0.13.9-1
- ros-foxy-tf2-geometry-msgs: 0.13.6-1 -> 0.13.9-1
- ros-foxy-tf2-kdl: 0.13.6-1 -> 0.13.9-1
- ros-foxy-tf2-msgs: 0.13.6-1 -> 0.13.9-1
- ros-foxy-tf2-py: 0.13.6-1 -> 0.13.9-1
- ros-foxy-tf2-ros: 0.13.6-1 -> 0.13.9-1
- ros-foxy-tf2-sensor-msgs: 0.13.6-1 -> 0.13.9-1
- ros-foxy-tf2-tools: 0.13.6-1 -> 0.13.9-1
- ros-foxy-v4l2-camera: 0.3.0-1 -> 0.3.1-1
- ros-foxy-webots-ros2: 1.0.2-1 -> 1.0.3-1
- ros-foxy-webots-ros2-abb: 1.0.2-1 -> 1.0.3-1
- ros-foxy-webots-ros2-core: 1.0.2-1 -> 1.0.3-1
- ros-foxy-webots-ros2-demos: 1.0.2-1 -> 1.0.3-1
- ros-foxy-webots-ros2-epuck: 1.0.2-1 -> 1.0.3-1
- ros-foxy-webots-ros2-examples: 1.0.2-1 -> 1.0.3-1
- ros-foxy-webots-ros2-importer: 1.0.2-1 -> 1.0.3-1
- ros-foxy-webots-ros2-msgs: 1.0.2-1 -> 1.0.3-1
- ros-foxy-webots-ros2-tiago: 1.0.2-1 -> 1.0.3-1
- ros-foxy-webots-ros2-universal-robot: 1.0.2-1 -> 1.0.3-1
- ros-foxy-webots-ros2-ur-e-description: 1.0.2-1 -> 1.0.3-1
- ros-foxy-xacro: 2.0.3-1 -> 2.0.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:
- Aaron Blasdel
- Adam Gotlib
- Alejandro Hernandez Cordero
- Anas M’chichou
- Anup Pemmaiah
- Brian Wilcox
- Carl Delsey
- Carlos Orduno
- Chris Lalancette
- Claire Wang
- Cyberbotics
- Daniel Stonier
- Dave Coleman
- David V. Lu!!
- Davide Faconti
- Dirk Thomas
- Erik Boasson
- Ivan Paunovic
- Jacob Hassold
- Jacob Perron
- Jan Staschulat
- John Shepherd
- Juan Pablo Samper
- Junho Lee
- Karsten Knese
- Matthew Bries
- Michael Carroll
- Michael Jeronimo
- Michel Hidalgo
- Mike Lautman
- Mohammad Haghighipanah
- MoveIt Release Team
- MoveIt! Release Team
- Olivier Kermorgant
- P. J. Reed
- Pete Baughman
- ROS Security Working Group
- RT Corporation
- Robert Haschke
- Russell Toris
- Sander G. van Dijk
- Scott K Logan
- Shane Loretz
- Soft_illusion
- Steve Macenski
- Steven! Ragnarok
- Steven! Ragnarök
- Ted Kern
- Ubuntu Robotics
- Vladimir Ermakov
- William Woodall
- lkumarbe
Cheers!
1 post - 1 participant
![[WWW] [WWW]](./rostheme/img/moin-www.png)
ROS Discourse General: New rosout Log Monitoring Tool, log_viewer
Hi,
I’ve released a new tool, log_viewer, for monitoring and filtering ROS log messages in the terminal without dropping messages. This is very similar
to swri_console, but is terminal based, using ncurses instead of Qt.
Log messages can be filtered based on:
- log level
- node
- whitelist text filter
- exclude text filter
log_viewer also supports text searches and jumping from match to match.
Log messages can be copied to the clipboard by selecting them.
log_viewer doesn’t need roscore to start and will automatically connect/reconnect with roscore when it
becomes available.
There is limited mouse support for selecting log messages and enabling/disabling the log level and node filters.
This is currently developed against ROS1, but I plan to support ROS2 in the future.
Marc
3 posts - 2 participants
![[WWW] [WWW]](./rostheme/img/moin-www.png)
ROS Discourse General: ROS Security WG Breakout Meeting | Invited Talk on Privaros
Hello folks,
The next ROS Security Working Group meeting will be: 2020-12-15T14:00:00Z
This’ll be a breakout session where we’ll invite researchers from the CSA department at IISC to present there recent work on Privaros, published this year at CCS '20, with follow up Q&A and discussions:
Rakesh Rajan Beck, Abhishek Vijeev, and Vinod Ganapathy. 2020. Privaros: A Framework for Privacy-Compliant Delivery Drones. In Proceedings of the 2020 ACM SIGSAC Conference on Computer and Communications Security (CCS '20). Association for Computing Machinery, New York, NY, USA, 181–194. DOI: https://doi.org/10.1145/3372297.3417858
We present Privaros, a framework to enforce privacy policies on drones. Privaros is designed for commercial delivery drones, such as the ones that will likely be used by Amazon Prime Air. Such drones visit various host airspaces, each of which may have different privacy requirements. Privaros uses mandatory access control to enforce the policies of these hosts on guest delivery drones. Privaros is tailored for ROS, a middleware popular in many drone platforms. This paper presents the design and implementation of Privaros’s policy-enforcement mechanisms, describes how policies are specified, and shows that policy specification can be integrated with India’s Digital Sky portal. Our evaluation shows that a drone running Privaros can robustly enforce various privacy policies specified by hosts, and that its core mechanisms only marginally increase communication latency and power consumption.
I’d encourage attendees to review the paper beforehand to foster deeper questions and discussions:
For more info, such as github repos and video demos, please view the web page for the paper here:
For those unable to attend, the session will be recorded and later uploaded, although feel free to post your questions below now, and we’ll do our best to incorporate them during the live event.
Agenda
- Privaros (~40min)
- Paper presentation from authors
- Q/A (~open ended)
- with follow up discussion
Minutes
As an update, the meeting minutes have been posted and can be reviewed here:
TODO
The video recording the meeting has been uploaded and can be viewed here:
TODO
Also, you can join the group via matrix chat at +rosorg-security:matrix.org
and subscribe to future ROS Security WG announcements by changing your default notification level for the wg-security
tag, or receive calendar email invites via ros-security-working-group-invites@googlegroups.com.
1 post - 1 participant
![[WWW] [WWW]](./rostheme/img/moin-www.png)
ROS Industrial: Perception-Based Region Selection for Human to Robot Collaboration
Background
The need for robotic systems that can collaborate with humans on the factory floor is in demand by the manufacturing community, but collaborative robotic solutions are still lacking in many respects. One such problem appears in quality control of subtractive manufacturing applications, such as sanding, grinding, and deburring, where material from a part is removed using an abrasive tool until a desired surface condition is obtained. In such scenario, the quality of the finish can be assessed by an expert human operator and therefore it would be very advantageous to leverage this expertise so as to guide semi-automated robotic systems to work on the regions that need further work until the desired quality is achieved. Given this challenge, this research focused on enhanced human-robot collaboration, by producing a capability that allows a human operator to guide the process by physically drawing a closed selection region on the part itself. This region will then be sensed by a vision system coupled with an algorithmic solution to crop out sections of the nominal process toolpaths that fall outside the confines of this region.
Approach
Initially, a small dataset of hand-drawn closed-region images was produced in order to aid the initial development of the 2D contour detection method and projection into 3D. These images were made with a dark marker on white paper laying on a flat surface and imaged with the Framos d435 camera. The 2D contour method that resulted from this dataset was implemented with the OpenCV open-source library and comprised the following filters/method: grayscaling, thresholding, dilation, canny edge detection and contour finding. The output of this operation was the 2D pixel coordinates of the detected contours (Figures 1.a and 1.b).

Figure 1a. amoeba 2d detection

Figure 1B. Box 2D Detection
The following stage used the 2D pixel coordinates and located the corresponding 3D points from the point cloud associated with the image; this was possible because both the 2D image and point cloud were of the same size. Following that, some additional filters were applied, and adjacent lines were merged in order to form larger segments. In the final steps, the segments were classified as open open and closed contours and then normal vectors were estimated. Results are shown in Figures 2.a and 2.b. Additional datasets were collected with varying conditions such as thicker, thinner lines, curved surfaces and multiple images containing parts of the same closed contour. These datasets allowed refining the method and addressed corner cases that emerged under more challenging conditions such as regions spanning multiple images (Figures 3.a, 3.b, 3.c).

Figure 2a. trianble region detection

figure 2b. amoeba region detection

Figure 3a. Box Multi-image 2d contour

figure 3b. Box multi-image 2d contour

Figure 3c. Box Multi-image region detection
Accomplishments
This research lead to the creation of an open-source C++ library that can be used to detect regions that have a similar need for human-robot collaboration. The repository can be found here https://github.com/swri-robotics/Region-Detection.
Furthermore, the work was featured as part of a recently ARM Insitute Project, with Spirit AeroSystems as prime investigator called Collaborative Robotic Sanding. An excerpt of that demonstration video highlighting the region detecion is included in the excerpt below.
![[WWW] [WWW]](./rostheme/img/moin-www.png)
ROS Discourse General: Ignition/Docker Tips and Tricks from Ignition Community Meeting
Hi All,
We had our third Ignition / Gazebo community meeting yesterday. I thought it was such a great event that I’ve decided to cross post it to ROS Discourse. The general theme for the event was “Docker tips and tricks for Ignition.”
You can watch the full recording on Vimeo.
To make life easier here are all the tools discussed at the event:
- OSRF Rocker tool for Docker
- Ignition Rocker
- GZDev Tool
- ROS Ignition Bridge
- Ignition Gazebo Crop Field Simulator
- Gazebo Battery Model
- Ignition MoveIt2
- ROS-Industrial Ignition/Tesseract
- Meeting Agenda
I want to do a quick straw poll, if I put together a monthly ROS user meeting would you show up?
- Yes, I would show up to a monthly community meeting.
- No, I’m not interested.
0 voters
1 post - 1 participant
![[WWW] [WWW]](./rostheme/img/moin-www.png)
ROS Discourse General: PlotJuggler 3 released
Hi,
I am happy to (finally) announce the release of PlotJuggler 3
Four years ago, I started this pet project with a clear goal in mind: to fill a gap in the ROS tool set, providing a time series visualization tool that could help developers to debug their complex robotic applications.
I wanted to build a powerful and intuitive tool and, with version 3, I think I eventually reached that goal.
If you haven’t, you may have a look at the ROSWorld video that introduces all the new features of PJ3 in just 2 minutes:
Many thanks to the people and companies that have beta-tested version 3 and to all the users that have shared their support and encouragement.
Cheers
Davide
4 posts - 2 participants
![[WWW] [WWW]](./rostheme/img/moin-www.png)
ROS Discourse General: Vision AI Standard Interfaces
Hi all, friendly neighborhood navigator here.
I wanted to bring up the migration of vision_msgs
so graciously donated by @Kukanani (https://github.com/Kukanani) from his personal GitHub to ros-perception
to aid in our use of vision_msgs
as the standardized AI Detection and Classification interfaces in both 2D and 3D.
vision_msgs
have been used for some time in various projects but until now it wasn’t “official” and not broadly adopted (projects define their own sets of messages to translate the same sets of information). The aim of bringing vision_msgs
into the ROS organization is to standardize around this package so that all future AI packages can be easily swapped out (as is enabled by sensor_msgs
, geometry_msgs
, etc.).
If you have a vested interest in AI detection / classification interfaces, please check out the link below and lets chat if there’s any changes we think are appropriate to adopt these at a community level.
It’s a great pleasure to be able to pull in some more wonderful work from the community. I want to again thank @Kukanani for his great work on this package and willingness to work with us to create this community standard.
If you have some wonderful work you’d like pulled into main ROS, feel free to drop me a PM.
Happy detecting,
Steve
1 post - 1 participant
![[WWW] [WWW]](./rostheme/img/moin-www.png)