October 20, 2017
ROS Lunar on OS X

@Mike_Purvis wrote:

Hey fellow humans, a bunch of you have discovered and used my ros-install-osx project. Unfortunately, it’s been broken for some time, for a variety of reasons, including the QT transition, plus chaos with Homebrew reorganizing things on their end— moving formulae around, dropping /usr/local/bin/python, and other stuff.

Anyway, the good news is that I’ve done some fiddling with it today and you should now be able to build an up to date ROS Lunar desktop full, including functional rviz, QT5, Gazebo 8, and all the other goodies. If you’re a Mac user who has been keeping your QT4 installation on life support, please give this a shot, try it out, and let me know on the github issue tracker where you run into trouble.

Posts: 2

Participants: 2

Read full topic

by @Mike_Purvis Mike Purvis on October 20, 2017 07:12 PM

October 14, 2017
Opensource software package maintenance in a cleaner, more thorough and verbose manner
There's various form of maintenance for software packages. ROS wiki spreads out well.
And, there's a recent discussion about the maintainership for "orphaned package"s.

I totally agree with the bigger picture in this thread; spending (even minimal) effort on making releases to make packages sustain for longer period rather than letting packages fade out. Yes.

Below is something I just wanted to chime in to the thread, but decided not to because it's a little off-topic, and I was afraid that I may sound opposing to the main idea in the thread. while I am not. So I decided to tweet in my own space.

It was triggered by someone's line:
In my experience, running the `catkin_generate_changelog`, `catkin_prepare_release`, `bloom-release` commands takes up maybe 1% of the time in maintaining a package.
As a release-maintainer of many long-lasting packages, I have to oppose here. So I just listed out the "release-maintainer"'s tasks I can think of, which may not be clear to the outside. These don't make a whole, and most of them may be optional, but still:
  • Release the package.
    • Changelog. Yes, `catkin_generate_changelog` populates raw commit logs per pkg.
      • Totally optional, but I tend to spend certain amount of time to edit changelogs to be more useful than just a set of commit history.
    • To what version to increment? Yes `catkin_prepare_release` handles this.
      • But you want to version it "right", which requires some idea about backward compatibility, features added etc. Typically this might require coordinating developers and/or going through the commits/PRs that have been added.
    • Run prerelease test.
      • Locally if your repo doesn't do it on cloud (btw industrial_ci offers a feature to run it on cloud).
      • For a ROS distro that supports multiple platform, run prerelease tests per each platforms if possible. For Kinetic, there was Wily until it went EOL, in addition to Xenial.
    • `bloom` can fail for whatever issues in your packages that you are almost automatically in charge of fixing.
      • Once issues occur on ROS buildfarm, a lot of times you're the only one to take (at least initial) action against it.
        • Hence, `prerelease test`, folks.
  • There's also "mental" responsibility. Not a big deal most of the times, but when something occurred like on buildfarm, you'd feel bad besides that it's you who people expect to fix the issues.
For larger set of packages, making a new release could take up some good time if done thoroughly (at least it does for me). But for doing things like above, only changelog is where volume matters, so releasing in a good manner is non trivial IMO.

I do believe by doing the release chores more thoroughly like this, there's a benefit for the users. Still, what's critical at first hand is that the package being available, as discussed in the referenced thread and again I fully agree with that.

by Isaac Saito (noreply@blogger.com) on October 14, 2017 12:15 AM

October 11, 2017
New Packages for Lunar 2017-10-11

@marguedas wrote:

We’re happy to announce the availability of 21 new packages and 24 updated packages for ROS Lunar.
As always thank you to all the maintainers who are making these releases as well as all the contributors who have helped contribute to these releases. Full details are below.

Package Updates for lunar

Added Packages [21]:

  • ros-lunar-abseil-cpp: 0.1.1-0
  • ros-lunar-costmap-converter: 0.0.7-0
  • ros-lunar-dynpick-driver: 0.2.0-0
  • ros-lunar-gcloud-speech: 0.0.4-0
  • ros-lunar-gcloud-speech-msgs: 0.0.4-0
  • ros-lunar-gcloud-speech-utils: 0.0.4-0
  • ros-lunar-image-exposure-msgs: 0.13.3-0
  • ros-lunar-imagezero: 0.2.4-0
  • ros-lunar-imagezero-image-transport: 0.2.4-0
  • ros-lunar-imagezero-ros: 0.2.4-0
  • ros-lunar-marti-status-msgs: 0.3.0-0
  • ros-lunar-nerian-stereo: 2.0.1-0
  • ros-lunar-openni2-launch: 0.2.3-0
  • ros-lunar-phidgets-high-speed-encoder: 0.7.4-0
  • ros-lunar-pointgrey-camera-description: 0.13.3-0
  • ros-lunar-pointgrey-camera-driver: 0.13.3-0
  • ros-lunar-statistics-msgs: 0.13.3-0
  • ros-lunar-teb-local-planner: 0.7.0-0
  • ros-lunar-teb-local-planner-tutorials: 0.2.1-0
  • ros-lunar-wfov-camera-msgs: 0.13.3-0
  • ros-lunar-wts-driver: 1.0.4-2

Updated Packages [24]:

  • ros-lunar-grpc: 0.0.2-0 -> 0.0.5-0
  • ros-lunar-libmavconn: 0.21.0-0 -> 0.21.2-0
  • ros-lunar-libphidget21: 0.7.3-0 -> 0.7.4-0
  • ros-lunar-libuvc: 0.0.5-3 -> 0.0.6-2
  • ros-lunar-libuvc-camera: 0.0.9-0 -> 0.0.9-1
  • ros-lunar-libuvc-ros: 0.0.9-0 -> 0.0.9-1
  • ros-lunar-marti-can-msgs: 0.2.0-0 -> 0.3.0-0
  • ros-lunar-marti-common-msgs: 0.2.0-0 -> 0.3.0-0
  • ros-lunar-marti-nav-msgs: 0.2.0-0 -> 0.3.0-0
  • ros-lunar-marti-perception-msgs: 0.2.0-0 -> 0.3.0-0
  • ros-lunar-marti-sensor-msgs: 0.2.0-0 -> 0.3.0-0
  • ros-lunar-marti-visualization-msgs: 0.2.0-0 -> 0.3.0-0
  • ros-lunar-mavlink: 2017.9.9-0 -> 2017.10.10-0
  • ros-lunar-mavros: 0.21.0-0 -> 0.21.2-0
  • ros-lunar-mavros-extras: 0.21.0-0 -> 0.21.2-0
  • ros-lunar-mavros-msgs: 0.21.0-0 -> 0.21.2-0
  • ros-lunar-novatel-gps-driver: 3.3.0-0 -> 3.4.0-0
  • ros-lunar-novatel-gps-msgs: 3.3.0-0 -> 3.4.0-0
  • ros-lunar-phidgets-api: 0.7.3-0 -> 0.7.4-0
  • ros-lunar-phidgets-drivers: 0.7.3-0 -> 0.7.4-0
  • ros-lunar-phidgets-imu: 0.7.3-0 -> 0.7.4-0
  • ros-lunar-rqt-pose-view: 0.5.7-0 -> 0.5.8-0
  • ros-lunar-rqt-robot-monitor: 0.5.7-0 -> 0.5.8-0
  • ros-lunar-test-mavros: 0.21.0-0 -> 0.21.2-0

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
  • Chittaranjan Srinivas Swaminathan
  • Christoph Rösmann
  • Dirk Thomas
  • Ed Venator
  • Edmond DuPont
  • Elliot Johnson
  • Geoff Viola
  • Ken Tossell
  • Konstantin Schauwecker
  • Marc Alban
  • Martin Guenther
  • Michael Ferguson
  • Mike Purvis
  • P. J. Reed
  • Shengye Wang
  • TORK
  • Tony Baltovski
  • Vladimir Ermakov
  • dfaconti

Posts: 1

Participants: 1

Read full topic

by @marguedas Mikael Arguedas on October 11, 2017 09:25 PM

ROS Webinar Series

@YUHONG_LIN wrote:


ROS Webinar Series | 2017

Dear Roboticists,

ROS Webinar series will be held during 18 Oct - 2 November, 2017 (http://www.theconstructsim.com/ros-webinars-train-team-ros/). Is a webinar series designed to help ROS learners smooth the learning curve and start ROS project quickly.

= Webinars Schedule =
1- Wednesday, Oct 18, 18:00-19:00 -> Using Movelt! with ROS Industrial
2- Thursday, Oct 19, 18:00-19:00 -> Webinar on how to teach ROS
3- Thursday, Oct 26, 18:00-19:00 -> Why you should train your team with ROS?
4- Thursday, Nov 2, 18:00-19:00 -> How to train your team with ROS for self-driving cars

= Topics =
*1- Using Movelt! with ROS Industrial
In this event we will teach you how to use MoveIt! for controlling an industrial robot with ROS. All the attendants will have full free access to the Robot Ignite Academy (www.robotigniteacademy.com) during the event. We will use that platform to do the exercises online, so the attendants will be able to practice with MoveIt!.

*2- Webinar on how to teach ROS
Learn a method to teach ROS fast with no hassle.
All the attendants will receive a 30 pages document explaining in detail all the techniques for fast ROS teaching.
The aim of this one-hour workshop is to show you how to change your classes from passive listening to active practising. Move away from a slides based teaching method to a notebook based one, where direct interaction with robots is embedded in the method itself.
(more inf: http://www.theconstructsim.com/webniar-how-to-teach-ros-fast/)

*3- Why you should train your team with ROS?
Why you should equip your team with ROS skills? How to give your team not only knowledge but also practical experience to create any ROS based robotics development? Come and get answers in this webinar.

*4- How to train your team with ROS for self-driving cars
The rapid development of auto-car has promoted a large demand for self-driving cars engineers. Among the skills required, knowing how to program with ROS is becoming an important one. In this webinar you will learn how to start with self-driving cars using ROS.

= Instructor =
RICARDO TÉLLEZ, Ph.D. (https://www.linkedin.com/in/ricardotellez/)

= Pre-registration =
To assist us in planning, pre-registration is required.
Pre-registration website: http://www.theconstructsim.com/ros-webinars-train-team-ros/

= Contact Us =
You can contact us with questions and doubts here: info@theconstructsim.com


YUHONG LIN
Business Assistant of R&D
The Construct

ylin@theconstructsim.com

Posts: 1

Participants: 1

Read full topic

by @YUHONG_LIN on October 11, 2017 05:35 PM

ROS Workshop India | Robocademy.com

@lentinjoseph wrote:

Hi all

We are conducting ROS workshops in India. Recently we have conducted an Advanced ROS workshop in one of Indian Premiere Institute, IIT Kharagpur. Glad to see they are using ROS vastly for their research.

Website: Robocademy

For offline workshop, shoot an email to qboticslabs@gmail.com

Here is a picture was taken at the end of the workshop.

Regards
Lentin Joseph

Posts: 1

Participants: 1

Read full topic

by @lentinjoseph Lentin Joseph on October 11, 2017 02:44 PM

ROSCon & IROS: Thank you, Vancouver!

This year ROSCon consolidated more than ever as the landmark event for the Robot Operating System developers community. Such general impression was encouraged by the rise of partners and sponsors – such as PAL Robotics – that broke all records. As usual, ROSCon organizers have conveniently made available all the conference talks online! These are very useful state of art resources for all the developers, even if some of them couldn’t make it to Vancouver.

PAL Robotics’ software developments and TALOS Space Robotics Challenge

Our CTO Luca Marchionni outlined PAL Robotics’ software development and how we use ROS tools at his talk in ROSCon. The Whole Body Control was one of the highlights, a software system customized by our team to develop high-level applications by abstracting the complexity of a robot, especially when it has a large number of DoF. This is the case with humanoids TALOS, REEM-C or TIAGo.

In fact, this software was extensively used by Team Olympus Mons, a team made up of current and former PAL members – including Marchionni – who won the 3rd place at the NASA Space Robotics Challenge. Thanks to our software modularity, PAL Robotics only spent two days implementing the developments achieved for the Space Robotics Challenge to our latest humanoid TALOS’ simulation, as shown by Marchionni in a video at the talk. And very soon we will see the actual TALOS humanoid robot performing those tasks!

TIAGo adventures at IROS&ROSCon

When we bring some of our TIAGo robots to an event, they always have such a productive time! After visiting Vancouver and listening to ROSCon conferences, TIAGo also spent five days enjoying the 30th anniversary of IROS.

IROS was a good occasion to share our latest developments; our CEO gave a talk within the frame of the RSJ-IAC Lunch surrounded by an attentive audience. Some of the latest advances we exposed are related to the European Projects that we are part of, such as Co4Robots, EnrichMe, SocSMCs, RobMoSys or GrowMeUp.

In short, IROS&ROSCon continue to be an absolute must to learn the latest cutting-edge developments in robotics. PAL Robotics team could speak with many researchers and companies that are making a great job. Our feeling was that the whole robotics community was making efforts to get these robotic platforms ready to enhance people’s quality of life. It was outstanding, and we are extremely glad to be part of this.

IROS has just ended and we are already looking forward to next year, IROS 2018 at Madrid; Meanwhile, do not miss our next adventures over at Birmingham for Humanoids 2017!

EnrichMe IROS2017venue IROS2018 Madrid IROS2017venue (2) ROSCon with TIAGo robot TIAGo at IROS2017 making friends

The post ROSCon & IROS: Thank you, Vancouver! appeared first on PAL Robotics Blog.

by Judith Viladomat on October 11, 2017 10:28 AM

October 10, 2017
Final week to submit videos for ROS 10 Year Montage

@tfoote wrote:

This is the last week left to submit your videos clips for consideration to be included in the ROS 10 year montage.

Submit your videos here by October 15th!

To show off the great variety of things people are doing with ROS we need your videos to share with the community. This will be one of the first things that people see when they start researching ROS and will be a great place to showcase your work.

Here are examples of past montages:

8 Years

5 Years

Posts: 1

Participants: 1

Read full topic

by @tfoote Tully Foote on October 10, 2017 03:34 PM

October 07, 2017
New Packages for Kinetic 2017-10-07

@tfoote wrote:

We’re happy to announce the availability of 32 new packages and 83 updated packages for Kinetic. As always thank you to all the maintainers who are making these releases as well as all the contributors who have helped contribute to these releases. Full details are below.

Package Updates for kinetic

Added Packages [32]:

  • ros-kinetic-abseil-cpp: 0.1.2-0
  • ros-kinetic-criutils: 0.1.0-0
  • ros-kinetic-ethercat-manager: 1.0.6-0
  • ros-kinetic-gcloud-speech: 0.0.3-1
  • ros-kinetic-gcloud-speech-msgs: 0.0.3-1
  • ros-kinetic-gcloud-speech-utils: 0.0.3-1
  • ros-kinetic-glkh-solver: 0.1.1-0
  • ros-kinetic-libfranka: 0.1.0-1
  • ros-kinetic-libmongocxx-ros: 0.3.6-0
  • ros-kinetic-lkh: 0.1.1-0
  • ros-kinetic-lkh-solver: 0.1.1-0
  • ros-kinetic-marti-status-msgs: 0.3.0-0
  • ros-kinetic-minas: 1.0.6-0
  • ros-kinetic-minas-control: 1.0.6-0
  • ros-kinetic-mongodb-log: 0.3.6-0
  • ros-kinetic-mongodb-store: 0.3.6-0
  • ros-kinetic-mongodb-store-msgs: 0.3.6-0
  • ros-kinetic-nerian-stereo: 2.0.1-0
  • ros-kinetic-pheeno-ros: 0.1.1-2
  • ros-kinetic-phidgets-high-speed-encoder: 0.7.4-0
  • ros-kinetic-python-trep: 1.0.3-1
  • ros-kinetic-roch-gazebo: 2.0.12-5
  • ros-kinetic-roch-simulator: 2.0.12-5
  • ros-kinetic-roch-viz: 2.0.10-0
  • ros-kinetic-ros-explorer: 0.1.0-0
  • ros-kinetic-teraranger: 1.0.1-0
  • ros-kinetic-teraranger-array: 1.0.1-0
  • ros-kinetic-teraranger-array-converter: 1.0.0-0
  • ros-kinetic-teraranger-description: 1.0.2-0
  • ros-kinetic-tra1-bringup: 1.0.6-0
  • ros-kinetic-tra1-description: 1.0.6-0
  • ros-kinetic-tra1-moveit-config: 1.0.6-0

Updated Packages [83]:

  • ros-kinetic-actionlib-lisp: 0.2.9-0 -> 0.2.10-0
  • ros-kinetic-cl-tf: 0.2.9-0 -> 0.2.10-0
  • ros-kinetic-cl-tf2: 0.2.9-0 -> 0.2.10-0
  • ros-kinetic-cl-transforms: 0.2.9-0 -> 0.2.10-0
  • ros-kinetic-cl-transforms-stamped: 0.2.9-0 -> 0.2.10-0
  • ros-kinetic-cl-urdf: 0.2.9-0 -> 0.2.10-0
  • ros-kinetic-cl-utils: 0.2.9-0 -> 0.2.10-0
  • ros-kinetic-costmap-converter: 0.0.5-0 -> 0.0.7-0
  • ros-kinetic-cv-camera: 0.1.0-0 -> 0.3.0-0
  • ros-kinetic-default-cfg-fkie: 0.7.5-0 -> 0.7.6-0
  • ros-kinetic-dynamic-tf-publisher: 2.2.2-0 -> 2.2.5-0
  • ros-kinetic-dynpick-driver: 0.1.1-0 -> 0.2.0-0
  • ros-kinetic-grpc: 0.0.2-0 -> 0.0.5-0
  • ros-kinetic-image-exposure-msgs: 0.13.1-0 -> 0.13.2-0
  • ros-kinetic-image-view2: 2.2.2-0 -> 2.2.5-0
  • ros-kinetic-imagezero: 0.2.3-0 -> 0.2.4-0
  • ros-kinetic-imagezero-image-transport: 0.2.3-0 -> 0.2.4-0
  • ros-kinetic-imagezero-ros: 0.2.3-0 -> 0.2.4-0
  • ros-kinetic-joint-state-publisher: 1.12.11-0 -> 1.12.12-0
  • ros-kinetic-jsk-common: 2.2.2-0 -> 2.2.5-0
  • ros-kinetic-jsk-data: 2.2.2-0 -> 2.2.5-0
  • ros-kinetic-jsk-network-tools: 2.2.2-0 -> 2.2.5-0
  • ros-kinetic-jsk-tilt-laser: 2.2.2-0 -> 2.2.5-0
  • ros-kinetic-jsk-tools: 2.2.2-0 -> 2.2.5-0
  • ros-kinetic-jsk-topic-tools: 2.2.2-0 -> 2.2.5-0
  • ros-kinetic-libmavconn: 0.21.0-0 -> 0.21.2-0
  • ros-kinetic-libphidget21: 0.7.3-0 -> 0.7.4-0
  • ros-kinetic-marti-can-msgs: 0.2.0-0 -> 0.3.0-0
  • ros-kinetic-marti-common-msgs: 0.2.0-0 -> 0.3.0-0
  • ros-kinetic-marti-nav-msgs: 0.2.0-0 -> 0.3.0-0
  • ros-kinetic-marti-perception-msgs: 0.2.0-0 -> 0.3.0-0
  • ros-kinetic-marti-sensor-msgs: 0.2.0-0 -> 0.3.0-0
  • ros-kinetic-marti-visualization-msgs: 0.2.0-0 -> 0.3.0-0
  • ros-kinetic-master-discovery-fkie: 0.7.5-0 -> 0.7.6-0
  • ros-kinetic-master-sync-fkie: 0.7.5-0 -> 0.7.6-0
  • ros-kinetic-mavros: 0.21.0-0 -> 0.21.2-0
  • ros-kinetic-mavros-extras: 0.21.0-0 -> 0.21.2-0
  • ros-kinetic-mavros-msgs: 0.21.0-0 -> 0.21.2-0
  • ros-kinetic-multi-map-server: 2.2.2-0 -> 2.2.5-0
  • ros-kinetic-multimaster-fkie: 0.7.5-0 -> 0.7.6-0
  • ros-kinetic-multimaster-msgs-fkie: 0.7.5-0 -> 0.7.6-0
  • ros-kinetic-nextage-calibration: 0.8.0-0 -> 0.8.2-0
  • ros-kinetic-nextage-description: 0.8.0-0 -> 0.8.2-0
  • ros-kinetic-nextage-gazebo: 0.8.0-0 -> 0.8.2-0
  • ros-kinetic-nextage-ik-plugin: 0.8.0-0 -> 0.8.2-0
  • ros-kinetic-nextage-moveit-config: 0.8.0-0 -> 0.8.2-0
  • ros-kinetic-nextage-ros-bridge: 0.8.0-0 -> 0.8.2-0
  • ros-kinetic-node-manager-fkie: 0.7.5-0 -> 0.7.6-0
  • ros-kinetic-novatel-gps-driver: 3.3.0-0 -> 3.4.0-0
  • ros-kinetic-novatel-gps-msgs: 3.3.0-0 -> 3.4.0-0
  • ros-kinetic-phidgets-api: 0.7.3-0 -> 0.7.4-0
  • ros-kinetic-phidgets-drivers: 0.7.3-0 -> 0.7.4-0
  • ros-kinetic-phidgets-imu: 0.7.3-0 -> 0.7.4-0
  • ros-kinetic-pointgrey-camera-description: 0.13.1-0 -> 0.13.2-0
  • ros-kinetic-pointgrey-camera-driver: 0.13.1-0 -> 0.13.2-0
  • ros-kinetic-roch: 2.0.11-0 -> 2.0.12-0
  • ros-kinetic-roch-base: 2.0.13-2 -> 2.0.15-0
  • ros-kinetic-roch-bringup: 2.0.13-2 -> 2.0.15-0
  • ros-kinetic-roch-capabilities: 2.0.13-2 -> 2.0.15-0
  • ros-kinetic-roch-control: 2.0.13-2 -> 2.0.15-0
  • ros-kinetic-roch-description: 2.0.13-2 -> 2.0.15-0
  • ros-kinetic-roch-follower: 2.0.11-0 -> 2.0.12-0
  • ros-kinetic-roch-ftdi: 2.0.13-2 -> 2.0.15-0
  • ros-kinetic-roch-msgs: 2.0.13-2 -> 2.0.15-0
  • ros-kinetic-roch-navigation: 2.0.11-0 -> 2.0.12-0
  • ros-kinetic-roch-rapps: 2.0.11-0 -> 2.0.12-0
  • ros-kinetic-roch-robot: 2.0.13-2 -> 2.0.15-0
  • ros-kinetic-roch-safety-controller: 2.0.13-2 -> 2.0.15-0
  • ros-kinetic-roch-sensorpc: 2.0.13-2 -> 2.0.15-0
  • ros-kinetic-roch-teleop: 2.0.11-0 -> 2.0.12-0
  • ros-kinetic-roslisp-common: 0.2.9-0 -> 0.2.10-0
  • ros-kinetic-roslisp-utilities: 0.2.9-0 -> 0.2.10-0
  • ros-kinetic-rtmros-nextage: 0.8.0-0 -> 0.8.2-0
  • ros-kinetic-statistics-msgs: 0.13.1-0 -> 0.13.2-0
  • ros-kinetic-teb-local-planner: 0.6.6-0 -> 0.6.7-0
  • ros-kinetic-test-mavros: 0.21.0-0 -> 0.21.2-0
  • ros-kinetic-turtlebot-gazebo: 2.2.2-0 -> 2.2.3-0
  • ros-kinetic-turtlebot-simulator: 2.2.2-0 -> 2.2.3-0
  • ros-kinetic-turtlebot-stage: 2.2.2-0 -> 2.2.3-0
  • ros-kinetic-turtlebot-stdr: 2.2.2-0 -> 2.2.3-0
  • ros-kinetic-ubiquity-motor: 0.5.2-0 -> 0.6.0-0
  • ros-kinetic-virtual-force-publisher: 2.2.2-0 -> 2.2.5-0
  • ros-kinetic-wfov-camera-msgs: 0.13.1-0 -> 0.13.2-0

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 Tiderko
  • Baptiste Potier
  • Carl
  • Chris Burbridge
  • Chris Lalancette
  • Christoph Rösmann
  • Ed Venator
  • Edmond DuPont
  • Elliot Johnson
  • Francisco Suarez-Ruiz
  • Franka Emika GmbH
  • Gayane Kazhoyan
  • Geoff Viola
  • IK Fast Plugin Creater
  • Jarvis Schultz
  • Jihoon Lee
  • Justin Huang
  • Kei Okada
  • Konstantin Schauwecker
  • Marc Alban
  • Marc Hanheide
  • Marcus Liebhardt
  • Martin Guenther
  • Mateusz Sadowski
  • Mehdi Tlili
  • Mike Purvis
  • Nick Hawes
  • OSRF
  • P. J. Reed
  • Pierre-Louis Kabaradjian
  • Rohan Agrawal
  • Ryohei Ueda
  • Ryosuke Tajima
  • Shengye Wang
  • TORK
  • Takashi Ogura
  • Tokyo Opensource Robotics Kyokai (TORK) Developer Team
  • Tony Baltovski
  • Vladimir Ermakov
  • YoheiKakiuchi
  • dfaconti
  • zmk5

Posts: 1

Participants: 1

Read full topic

by @tfoote Tully Foote on October 07, 2017 07:20 PM

October 06, 2017
Announcing the rosautodoc tool

@bponsler wrote:

Hello everyone,

I’d like to announce the rosautodoc tool.

This tool makes it possible to generate initial documentation of a node’s ROS interface. This tool generates markdown (or HTML) documentation for one or more nodes running on a system and documents: parameters used, services provided, topics published, and topics subscribed to.

For instructions and documentation see the github page.

Enjoy.

-Brett

Posts: 1

Participants: 1

Read full topic

by @bponsler Brett Ponsler on October 06, 2017 01:59 PM

October 05, 2017
New Packages for Indigo 2017-10-05

@tfoote wrote:

We have synced another batch of packages for Indigo. There are 6 new packages as well as 53 updated packages. Thank you to all the contributors. The full details are below.

Package Updates for indigo

Added Packages [6]:

  • ros-indigo-abseil-cpp: 0.1.2-0
  • ros-indigo-libmongocxx-ros: 0.3.6-1
  • ros-indigo-marti-status-msgs: 0.3.0-0
  • ros-indigo-pheeno-ros: 0.1.1-4
  • ros-indigo-pheeno-ros-sim: 0.1.4-0
  • ros-indigo-rail-face-detector: 0.0.2-0

Updated Packages [53]:

  • ros-indigo-actionlib-lisp: 0.2.9-0 -> 0.2.10-0
  • ros-indigo-cl-tf: 0.2.9-0 -> 0.2.10-0
  • ros-indigo-cl-tf2: 0.2.9-0 -> 0.2.10-0
  • ros-indigo-cl-transforms: 0.2.9-0 -> 0.2.10-0
  • ros-indigo-cl-transforms-stamped: 0.2.9-0 -> 0.2.10-0
  • ros-indigo-cl-urdf: 0.2.9-0 -> 0.2.10-0
  • ros-indigo-cl-utils: 0.2.9-0 -> 0.2.10-0
  • ros-indigo-default-cfg-fkie: 0.7.5-0 -> 0.7.6-0
  • ros-indigo-grpc: 0.0.2-0 -> 0.0.4-0
  • ros-indigo-imagezero: 0.2.3-0 -> 0.2.4-0
  • ros-indigo-imagezero-image-transport: 0.2.3-0 -> 0.2.4-0
  • ros-indigo-imagezero-ros: 0.2.3-0 -> 0.2.4-0
  • ros-indigo-joint-state-publisher: 1.11.14-0 -> 1.11.15-0
  • ros-indigo-marti-can-msgs: 0.2.0-0 -> 0.3.0-0
  • ros-indigo-marti-common-msgs: 0.2.0-0 -> 0.3.0-0
  • ros-indigo-marti-nav-msgs: 0.2.0-0 -> 0.3.0-0
  • ros-indigo-marti-perception-msgs: 0.2.0-0 -> 0.3.0-0
  • ros-indigo-marti-sensor-msgs: 0.2.0-0 -> 0.3.0-0
  • ros-indigo-marti-visualization-msgs: 0.2.0-0 -> 0.3.0-0
  • ros-indigo-master-discovery-fkie: 0.7.5-0 -> 0.7.6-0
  • ros-indigo-master-sync-fkie: 0.7.5-0 -> 0.7.6-0
  • ros-indigo-mongodb-log: 0.1.30-1 -> 0.3.6-1
  • ros-indigo-mongodb-store: 0.1.30-1 -> 0.3.6-1
  • ros-indigo-mongodb-store-msgs: 0.1.30-1 -> 0.3.6-1
  • ros-indigo-multimaster-fkie: 0.7.5-0 -> 0.7.6-0
  • ros-indigo-multimaster-msgs-fkie: 0.7.5-0 -> 0.7.6-0
  • ros-indigo-node-manager-fkie: 0.7.5-0 -> 0.7.6-0
  • ros-indigo-python-trep: 1.0.2-0 -> 1.0.3-0
  • ros-indigo-rapid-pbd: 0.1.3-0 -> 0.1.4-0
  • ros-indigo-roch: 1.0.13-0 -> 1.0.14-0
  • ros-indigo-roch-base: 1.0.14-0 -> 1.0.15-0
  • ros-indigo-roch-bringup: 1.0.13-0 -> 1.0.14-0
  • ros-indigo-roch-capabilities: 1.0.14-0 -> 1.0.15-0
  • ros-indigo-roch-control: 1.0.14-0 -> 1.0.15-0
  • ros-indigo-roch-description: 1.0.14-0 -> 1.0.15-0
  • ros-indigo-roch-follower: 1.0.13-0 -> 1.0.14-0
  • ros-indigo-roch-ftdi: 1.0.14-0 -> 1.0.15-0
  • ros-indigo-roch-gazebo: 1.0.11-0 -> 1.0.12-0
  • ros-indigo-roch-msgs: 1.0.14-0 -> 1.0.15-0
  • ros-indigo-roch-navigation: 1.0.13-0 -> 1.0.14-0
  • ros-indigo-roch-rapps: 1.0.13-0 -> 1.0.14-0
  • ros-indigo-roch-robot: 1.0.14-0 -> 1.0.15-0
  • ros-indigo-roch-safety-controller: 1.0.14-0 -> 1.0.15-0
  • ros-indigo-roch-sensorpc: 1.0.14-0 -> 1.0.15-0
  • ros-indigo-roch-simulator: 1.0.11-0 -> 1.0.12-0
  • ros-indigo-roch-teleop: 1.0.13-0 -> 1.0.14-0
  • ros-indigo-roch-viz: 1.0.9-3 -> 1.0.10-0
  • ros-indigo-roslisp-common: 0.2.9-0 -> 0.2.10-0
  • ros-indigo-roslisp-utilities: 0.2.9-0 -> 0.2.10-0
  • ros-indigo-turtlebot-gazebo: 2.2.2-0 -> 2.2.3-0
  • ros-indigo-turtlebot-simulator: 2.2.2-0 -> 2.2.3-0
  • ros-indigo-turtlebot-stage: 2.2.2-0 -> 2.2.3-0
  • ros-indigo-turtlebot-stdr: 2.2.2-0 -> 2.2.3-0

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 Tiderko
  • Andrew Silva
  • Carl
  • Chris Burbridge
  • Chris Lalancette
  • Edmond DuPont
  • Elliot Johnson
  • Gayane Kazhoyan
  • Jarvis Schultz
  • Jihoon Lee
  • Justin Huang
  • Marc Alban
  • Marc Hanheide
  • Marcus Liebhardt
  • Mehdi Tlili
  • Nick Hawes
  • OSRF
  • P. J. Reed
  • Shengye Wang
  • Zahi Kakish
  • dfaconti
  • zmk5

Posts: 1

Participants: 1

Read full topic

by @tfoote Tully Foote on October 05, 2017 06:00 PM

ROSIN EU project awards first grants to companies for ROS-Industrial software development

@gavanderhoorn wrote:

With this post I’d like to update the ROS and ROS-Industrial communities on the first two ROSIN grants that have been awarded.


Two European companies have received the first ROSIN grants. The ROSIN Focused-Technical Projects (FTPs) program funds robot software developments that contribute to the ROS and ROS-Industrial open-source communities.

Ensenso GmbH (Germany) has received a grant of € 15,000 to create a standardised ROS driver package for their Ensenso series of stereo cameras. Ensenso will continue the development and support of this driver and will support their customers looking to use ROS with their products.

Robot Care Systems (the Netherlands) has received € 52,000 to consolidate and open-source a robotics modelling language that is modular and extendable by users and allows to program robots in ROS at a more abstract and standardised level. Model driven design, code generation and automated documentation generation help developers increase productivity.

RCS receives grant at Mikrocentrum-Alten event: ROS-Industrial: advancing robotics in industry

The ROSIN project is offering more than € 3,000,000 in grants for robotic open-software development, documentation efforts, code audits and analyses and standardisation and integration efforts. The goal is to increase the ROS and ROS-Industrial codebase with tools to create more and “smarter” robot capabilities. The ROSIN call for FTPs is permanently open, and new applications are being evaluated periodically. Grants awarded may have a maximum of € 100,000 per FTP, with a total of € 250,000 over three projects.

The application and granting process is simple:

  1. Download the Applicants Guide
  2. Explain the purpose of your Focused technical Project and provide a clear work plan (approximately 5 pages)
  3. Submit your proposal at rosin-project.eu/ftps
  4. Your proposal is evaluated in a few weeks by robotic experts
  5. Receive your grant and start your project immediately

More information can be found at rosin-project.eu/ftps, and for any questions please contact us at info@rosin-project.eu.

Posts: 2

Participants: 2

Read full topic

by @gavanderhoorn gavanderhoorn on October 05, 2017 03:23 PM

October 04, 2017
Announcing Docker Images for Legacy ROS releases

@ruffsl wrote:

TL;DR: Docker Images for all Legacy ROS distros are now available at OSRF’s DockerHub profile! :whale:

Hello everyone,

For the 10th anniversary of ROS, @tfoote and I created docker images for legacy distros of ROS.
So, all previous EOL distros from boxturtle to hydro are now available from OSRF’s ros_legacy repo [1]:

docker run -it osrf/ros_legacy:boxturtle roscore

Because not all modern core metapackages preexisted legacy releases, the minimal install target is set to a roughly equivalent package, ros, that include most essential dependencies that you can build up from there.

Q: But why?

https://media.giphy.com/media/s239QJIh56sRW/giphy.gif

A: Because we could!

But in all seriousness, this should be beneficial for anyone who needs to research and run legacy ROS code from previous published literature or archives. Getting an old image of Ubuntu 10.04 to boot with a recent kernel for an m.2 drive, or spinning up an entire VM install to look into a driver package last released for cturtle is not something I’d ever like to spend much of my time on.

For example, after stumbled upon roboearth [2], only to find it cold and abandoned, I still wanted to check out the project and see how the system worked and what could gained from the previous design. However, having little desire in porting an entirely unfamiliar codebase to my current OS for some brief tutorials, I sort of stopped short after just reading through the source code. A far simpler and interactive approach could now be to just probe and run the legacy codebase from a linux container with the original release dependencies.

Q: Why not backport legacy images into the official docker library?
A: That ship has sort of sailed… :sailboat:

This was briefly discussed, but not pursued for a few reasons [3]:

  1. Recent improvements for multi architecture support in the official library registry makes now makes it tricky adding legacy distros that rely on ancient ubuntu images no longer in the build pipeline.
  2. Additionally, the dockerfiles are still new and could be improved, thus hosting them under osrf/ros_legacy keeps it simple to update, so PRs for legacy images are welcome.

ROS Legacy Docker Pulls Docker Stars

  • amd64 Docker Build Status

For current maintainers, please do not take this as cause to postpone the releasing of your package into current ROS releases, as these images will only be provided on a best effort basis. But for users who may be on the verge of adopting an abandoned package, I hope you find these useful reviving such projects.

Note:

The base images used are Ubuntu releases that are now also EOL :skull:, and thus no longer receive security updates :syringe:. I would strongly advise against using such derived images for anything other than just investigating or general posterity. However, at the time writing, all EOL related dockerfiles still do successfully build, and are hosted from an automated build repo. The dockerfiles also include some sugar and magic to account for some of the odd idiosyncrasies of the legacy environments.

cheers,
@ruffsl

P.S.

On a somewhat related milstone, the official ROS library repo has recently surpassed 1 million pulls!
Perhaps including such metrics into the annual ROS Community Metrics report would be a nice to show.
For starters, the information can be polled from the Docker Registry v2 API [4]:
And at the time of writing this post: Docker Pulls
"pull_count": 1101665
"star_count": 127

[1] https://hub.docker.com/r/osrf/ros_eol/
[2] http://wiki.ros.org/roboearth
[3] https://github.com/osrf/docker_images/issues/80
[4] https://hub.docker.com/v2/repositories/library/ros/

Posts: 1

Participants: 1

Read full topic

by @ruffsl ruffsl on October 04, 2017 11:53 PM

October 03, 2017
World MoveIt! Day 2017 - October 18th!

From Dave Coleman

world_moveit_day_2017.png

We're excited to announce that this year's World MoveIt! Day will be Wednesday October 18th! The event is a day long international hackathon to improve the MoveIt! code base, documentation, and community. We hope to close as many pull requests and issues as possible and explore new areas of features and improvements for the now five year old framework.

We will be having many event locations including:

  • Verb Surgical, San Francisco Bay Area
  • Magazino, Munich, Germany
  • Southwest Research Institute, San Antonio, USA
  • Xamla Robotics (PROVISIO GmbH), Münster, Germany
  • ROS-Industrial Asian Pacific Consortium, Singapore (THURSDAY OCTOBER 19th)
  • PickNik Robotics (Univ. Colorado), Boulder, USA
  • Shadow Robot Company, London, UK

You are encouraged to have your own event in your lab/organization/company and video conference in to all the other events.

For more details, see the event page.

by Tully Foote on October 03, 2017 10:36 PM

World MoveIt! Day 2017 - October 18th!

@davetcoleman wrote:

We’re excited to announce that this year’s World MoveIt! Day will be Wednesday October 18th! The event is a day long international hackathon to improve the MoveIt! code base, documentation, and community. We hope to close as many pull requests and issues as possible and explore new areas of features and improvements for the now five year old framework.

We will be having many event locations including:

  • Verb Surgical, San Francisco Bay Area
  • Magazino, Munich, Germany
  • Southwest Research Institute, San Antonio, USA
  • Xamla Robotics (PROVISIO GmbH), Münster, Germany
  • ROS-Industrial Asian Pacific Consortium, Singapore (THURSDAY OCTOBER 19th)
  • PickNik Robotics (Univ. Colorado), Boulder, USA
  • Shadow Robot Company, London, UK

You are encouraged to have your own event in your lab/organization/company and video conference in to all the other events.

For more details, see the event page.

Posts: 5

Participants: 4

Read full topic

by @davetcoleman Dave Coleman on October 03, 2017 09:44 PM

ROSCon 2017: Video recordings of presentations are available

We're happy to announce that the videos from ROSCon 2017 have been uploaded and are now linked from the program, thanks to the support of our video-archiving sponsor Ubuntu. If you were unable to attend, missed a talk, or want to listen again to get some more details now you can.

In addition we have posted slides from almost all the speakers as well. So if you want to get a link or other information you can do so now as well. The slides are linked alongside the videos from the program.

If you presented a Lightning Talk and want to provide more information, or if you were unable to secure a lightning talk slot I encourage you to make your announcement on Discourse in the ROS Projects category. If you're announcing a released ROS package send it to the General category. That way, more of the community will be aware of your projects and package contributions.

Thanks to everyone for coming and for your support! We sold out ROSCon for the third year in a row, with over 475 attendees. And thank you to our record-breaking 33 sponsors for the financial support that enabled the conference to grow!

  • Your friendly neighborhood ROSCon 2017 Organizing Committee

Thanks to our Platinum Sponsor: Intel.
Thanks to our Gold Sponsors: AIRA, Clearpath, Erle, Fetch, GaiTech, Locus, Rapyuta, ROBOTIS, and SICK.

by Tully Foote on October 03, 2017 07:03 PM

October 02, 2017
ROSCon 2017: Video recordings of presentations are available

@tfoote wrote:

We’re happy to announce that the videos from ROSCon 2017 have been uploaded and are now linked from the program, thanks to the support of our video-archiving sponsor Ubuntu. If you were unable to attend, missed a talk, or want to listen again to get some more details now you can.

In addition we have posted slides from almost all the speakers as well. So if you want to get a link or other information you can do so now as well. The slides are linked alongside the videos from the program.

If you presented a Lightning Talk and want to provide more information, or if you were unable to secure a lightning talk slot I encourage you to make your announcement on Discourse in the ROS Projects category. If you’re announcing a released ROS package send it to the General category. That way, more of the community will be aware of your projects and package contributions.

Thanks to everyone for coming and for your support! We sold out ROSCon for the third year in a row, with over 475 attendees. And thank you to our record-breaking 33 sponsors for the financial support that enabled the conference to grow!

  • Your friendly neighborhood ROSCon 2017 Organizing Committee

Thanks to our Platinum Sponsor: Intel.
Thanks to our Gold Sponsors: AIRA, Clearpath, Erle, Fetch, GaiTech, Locus, Rapyuta, ROBOTIS, and SICK.

Posts: 1

Participants: 1

Read full topic

by @tfoote Tully Foote on October 02, 2017 11:38 PM

September 29, 2017
Software engineering, dependencies and C++ library Abseil

@facontidavide wrote:

Dear ROS users,

I wanted to share with the community a very inspiring video that I saw recently.

If you care about software quality in large projects, you will not regret spending 1 hour of your life watching this.
I believe that the issue of dependencies is particularly relevant in the context of ROS, where it is the norm to reuse libraries developed by other people in the community.

Furthermore, they announced a utility library that is incredibly useful.

https://github.com/abseil/

I am planning to build a catkinized version over the weekend to make it easily available to others.
I took a look at it and it seems to be an extremely valuable addition to any programmer toolkit. I believe it should be considered by anyone writing new code or refactoring old one.

Cheers.

Davide

Posts: 1

Participants: 1

Read full topic

by @facontidavide Davide Faconti on September 29, 2017 12:45 PM

September 28, 2017
IMU Calibration on Ground Robot

@charlie wrote:

Hello,

I am working on a ground based robot, and now we are working to install an IMU.

At the moment we are using this IMU: https://www.adafruit.com/product/2472. We are trying to figure out calibration with it however - how do people typically install and allow for calibration of an IMU on a ground based robot? Do they typically install it on a lead such that it can be moved in patterns to calibrate it fully? Or are there calibration free IMUs that can be installed and simply work when turned on seamlessly?

If there are calibration free IMUs, what ones do people recommend?

Thanks!

Posts: 2

Participants: 2

Read full topic

by @charlie Charlie Andersen on September 28, 2017 07:03 PM

[notice] Removal of Arial in rviz caused breaking changes

@wjwwood wrote:

I recently removed the copy of the Arial font we were distributing in rviz and replaced it with Liberation Sans [1]. This was done in Indigo, Jade, Kinetic, and Lunar.

At the time I thought other plugins would be reusing the code that was used to do moving text in rviz (avoiding a reference to Arial themselves), but that doesn’t appear to be the case and several users have run into issues [2][3][4].

There’s not a workaround at the moment, but the fix should be straightforward. I’ll try to expedite the release of these packages to public if I can.

If anyone has time to do testing higher level packages in the “shadow repository”[5] between syncs to public that would help us catch these mistakes before they get to users and it would be much appreciated.

Thanks and sorry again for the disruption,

[1] https://github.com/ros-visualization/rviz/pull/1141
[2] https://answers.ros.org/question/271750/error-when-trying-to-launch-moveit-created-robot-model/
[3] https://github.com/ros-planning/moveit/issues/624
[4] https://github.com/orikuma/jsk_visualization/commit/69c456a5fc095a73b50cfd24fe7d7a605a5467cc
[5] http://wiki.ros.org/ShadowRepository

Posts: 7

Participants: 2

Read full topic

by @wjwwood William Woodall on September 28, 2017 06:17 PM

«Survey on Collaboration and Package Reuse in ROS», Summary of Results

@pestefo wrote:

Hey ROS users,

A couple of weeks ago I invited you to participate in a study about “Package Reuse” and “Collaboration Dynamics” of our community. Also, I promised to share a summary of the results… and here it is:

http://bit.ly/SurveyROSSummary :bar_chart:

I invite you to leave your comments and questions on the comment box at the bottom of the page. :mega:

By the way, the raffle winners have already received their Gift Card :credit_card::sparkles:.

We thank you all for your participation and time.

Sincerely,
Pablo Estefó, Jocelyn Simmonds and Romain Robbes.

Posts: 1

Participants: 1

Read full topic

by @pestefo Pablo Estefó on September 28, 2017 01:02 PM

September 27, 2017
ROS Kinetic install ubuntu17.04

@Teja_K wrote:

I am using ubuntu 16.04.3 and I have a problem with installing ROS. When I update and install ros-kinetic-desktop-full it says unable to locate package ros-kinetic-desktop-full. Can someone help me with this

Posts: 5

Participants: 4

Read full topic

by @Teja_K Teja K on September 27, 2017 06:24 AM

September 26, 2017
Goodbye, ROSCon 2017

After a gorgeous and enlightening couple of days in Vancouver, we bid farewell to ROSCon 2017. We sold out ROSCon for the third year in a row, with over 475 attendees.

Thanks to everyone for coming and for your support! And thank you to our record-breaking 33 sponsors for the financial support that enabled the conference to grow!

We're posting the slides as they come in from the speakers and we expect to have the videos posted by October 6th. As usual, all of that material is linked in the program.

ROSCon17_Group2.jpg

by Tully Foote on September 26, 2017 11:22 PM

September 25, 2017
Announcing the 'laser_odometry' package

@Jeremie wrote:

Dear ROS user,

please let me introduce the laser_odometry package.

This pluginlib-based ROS package aims at providing a unified API for laser scan matcher in the context of laser odometry.
While there are nowadays several publicly available scan matcher (csm, psm, rf2o to name a few), each and everyone of them uses it own internal data representation and API making it difficult to switch from one to another within a larger project for switching/testing/comparison purpose. This package aims at answering this difficulty.
By providing an abstract base class it allows one to declare a unique scan matcher object in a project leveraging the benefit of a unified API, while the laser_odometry_node is a stand alone ROS node which laser scan matcher type is selected at launch time by an argument (the plugin type) and publishes the estimated pose either as a geometry_msgs::Pose2D or a nav_msgs::Odometry.

The plugins already implemented are :

Please notice that as of today this is still an ongoing development thus the API is not completely stable and is likely to evolve with more extensive use of the package, feedback etc … However the project seems mature enough for other people to test it and possibly join the effort.
Please also notice that releases were made of a very early version of the package, thus are outdated. New ones are planned as soon as the project seems stable.

While hopping that some of you will find this project useful, I am definitely looking forward for comments and feedback !

Thanks.

Jeremie Deray.


Notes :

The laser_odometry_core package provides a base-class from which is derived plugins wrapping scan matchers. The base-class implements most of the scan matcher common operations (e.g. frames and covariances composition) reducing the work of the derived plugin to overloading a single function that computes the scan alignment. While enforcing the API, the base class is also flexible in its workflow by offering the possibility to overload several functions along the sequential execution of the overall scan matching (e.g. initialization, preProcessing, see the overall pseudo-code). Find more details on the wiki page dedicated to plugin creation.

The package aims at handling laser odometry, thus either 2D or 3D. While the 2D case has concentrated most of the effort so far, the API already handles sensor_msgs::PointCloud2 and hopefully the 3D case will be handled soon thanks to the laser_odometry_libpointmatcher plugin.

Posts: 1

Participants: 1

Read full topic

by @Jeremie Jeremie on September 25, 2017 11:10 AM

September 22, 2017
Ros2 is not recognized as internal command Windows 8.1

@Shreeram_Gopalakrish wrote:

Hi all,
I am trying to run ros2 and I have followed all the steps from https://github.com/ros2/ros2/wiki/Windows-Install-Binary except VS2017 which I had installed on my Windows 8.1 beforehand.
But when I try to execute ros2 run demo_nodes_cpp talker , I get the following error:

’ros2’ is not recognized as an internal or external command,
operable program or batch file.

Any help is appreciated .

Thanks in advance.

Posts: 1

Participants: 1

Read full topic

by @Shreeram_Gopalakrish Shreeram Gopalakrishnan on September 22, 2017 11:24 AM

Addition of Radar-Specific Message(s) to sensor_msgs

@JWhitleyAStuff wrote:

I work for a company that is very closely tied to the automotive industry. Many people in our industry are starting to use ROS as the basis for research and development efforts into autonomous vehicles. One of the primary sensing modalities is radar. Unfortunately, there isn’t really a basic message type in sensor_msgs that currently fits the output from a radar. The closest available is sensor_msgs/Range. However, while there are field_of_view, min_range, max_range and range properties associated with a radar detection, there are also other intrinsic properties like amplitude (a measure of the power of the returned signal - also applies to the other light-based sensor readings represented by Range) and angle (the angle of the detection within the lateral field of view - since radars have horizontal discrimination). Soon, there will also be 3D radars with vertical discrimination necessitating a splitting of field_of_view into lateral and vertical components.

Furthermore, many radars do not actually output the raw detection information but only output “tracks” which are filtered and grouped abstractions of single or multiple detections. Because of the tracking over several scans, they contain all the same readings as sensor_msgs/Range with the following exceptions:

  1. They do not contain “amplitude” since this is meaningless for a grouped/tracked single or set of detections.
  2. They also contain the following additional fields:
    a. lateral_rate: The lateral velocity of the object within the arc of the field of view of the radar (polar lateral velocity).
    b. width: A lateral measurement of the “track” from the most extreme lateral detections that make up the track.
    c. range_rate: A measurement of the longitudinal velocity of the track with respect to the detected angle (polar longitudinal velocity).
    d. range_accel: A measurement of the longitudinal acceleration of the track with respect to the detected angle.

We have our own versions of messages representing these data (see our package on Github [1] - specifically RadarDetection and RadarTrack) but I am now aware that these do not comply with REP 117 [2] and would much rather contribute to the standardized set of messages in common_msgs.

To the point: Does it make sense to try to extend sensor_msgs/Range to include the properties of a radar detection or should a new message be created? What about a track (when they are the only data available)?

[1] https://github.com/astuff/platform_automation_msgs/tree/master/radar_msgs/msg
[2] http://www.ros.org/reps/rep-0117.html

Posts: 6

Participants: 4

Read full topic

by @JWhitleyAStuff Joshua Whitley on September 22, 2017 05:45 AM


Powered by the awesome: Planet