August 18, 2017
Announcing ROS Docker Images for ARM and Debian

@ruffsl wrote:

TL;DR: Support for both ARM and Debian with ROS is now reflected in the Official DockerHub library! :whale:

Hello everyone!

As you might have noticed, DockerHub is beginning to support additional architectures other than amd64 [1]. So I’ve expanded upon our dockerfile maintenance infrastructure for the official ROS images to enable arm support.

Additionally while refactoring, support for multiple operating systems, i.e. debian based ROS images, has also been enabled, while also extending to supported arm architectures. To see the listing of supported suites, distros and architectures for the official DockerHub library, you can view the manifest for ROS here [2]:

Notes:

  • New tags have been added to specify the operating system suite via appended suffix
    • E.g. kinetic-ros-base-xenial, kinetic-ros-base-jessie
  • There are no changes to the original set of tags, as they still point to the same suite
    • E.g. kinetic <=> kinetic-ros-base <=> kinetic-ros-base-xenial
    • Additionally true for amd64 tagged images hosted from osrf/ros automated repo
  • Presently, the multi-architecture ROS images are hosted under separate docker hub organizations
    • E.g. docker pull arm64v8/ros OR docker pull arm32v7/ros:indigo
    • You may reference <arch>/ros:<tag> to specifically pull a given architecture
    • OR try out the temporary manifest enabled test rolling repo: docker pull trollin/ros
  • Forthcoming, the official registry will internally negotiate what arch is pulled via the manifest
    • E.g. if docker-engine host is arm64v8, docker pull ros should pull an arm64v8 image
  • There is some build scaffolding you can follow for multi-architecture image builds for ROS

This is all fairly new, so if you’d like to start learning more, here’s a relatively recent article on the subject [3]:

Of course, if you’d like to play around with any of the arm images, but don’t have raspberry pie or other arm based platform laying around, you can easily emulate via qemu-user and binfmt-support. By mounting in the necessary qemu-user static binaries into the container, and installing the necessary binfmt-support kernel module to the host, you can run commands within the arm environment on your amd64 workstation.

E.g. a small script, such as in cross-docker for example [4], can be used like so:

$ sudo apt install qemu-user-static
...

$ uname -a
Linux ubuntu 4.8.0-58-generic #63~16.04.1-Ubuntu SMP 
 Mon Jun 26 18:08:51 UTC 2017 
 x86_64 x86_64 x86_64 GNU/Linux

$ ./cross-docker run -it arm64v8/ros:lunar-ros-core-stretch uname -a
Unable to find image 'arm64v8/ros:lunar-ros-core-stretch' locally
lunar-ros-core-stretch: Pulling from arm64v8/ros
774bc81cd4dd: Pull complete 
...
Digest: sha256:dd88dce3f840cc963a61881a1da4f36f1c66214dd1b0029fa433580a4f5a142f
Status: Downloaded newer image for arm64v8/ros:lunar-ros-core-stretch
Linux a2a63cc39389 4.8.0-58-generic #63~16.04.1-Ubuntu SMP
 Mon Jun 26 18:08:51 UTC 2017
 aarch64 GNU/Linux

$ ./cross-docker run -it arm64v8/ros:lunar-ros-core-stretch cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 9 (stretch)"
NAME="Debian GNU/Linux"
VERSION_ID="9"
VERSION="9 (stretch)"
ID=debian
...

If you find issues with the images, please be sure to ticket them here [5]:

Also don’t forget to share our official repo [6] so others might discover it!

best,
@ruffsl

[1] https://github.com/docker-library/official-images#architectures-other-than-amd64
[2] https://github.com/docker-library/official-images/blob/master/library/ros
[3] https://developer.ibm.com/linuxonpower/2017/07/27/create-multi-architecture-docker-image/
[4] https://github.com/justincormack/cross-docker , https://docs.docker.com/docker-for-mac/multi-arch/
[5] https://github.com/osrf/docker_images
[6] https://hub.docker.com/_/ros/

P.S.

For arm32v7, there is a blocking issue upstream with cloud image used in docker hub. If you would like to expedite arm32v7 support for ROS docker images, you may make your concerns know and follow the bug report:
https://bugs.launchpad.net/cloud-images/+bug/1711735

Although some i386 binaries are supplied by the ROS buildfarm, I’ve deliberately omitted it for now, given:

  1. i386 binaries for docker-engine are not officially shipped or supported by Docker
  2. Current traffic for i386 ROS packages is below that for arm

Posts: 1

Participants: 1

Read full topic

by @ruffsl ruffsl on August 18, 2017 07:30 PM

August 15, 2017
New Packages for Kinetic 2017-08-14

@tfoote wrote:

We’re happy to announce another batch of packages for ROS Kinetic Kame. This sync includes both the usual bunch of updates as well as a large set of new packages.

Full details are below. Thanks to everyone who has contributed!

Package Updates for kinetic

Added Packages [76]:

  • ros-kinetic-cob-android: 0.1.3-0
  • ros-kinetic-cob-android-msgs: 0.1.3-0
  • ros-kinetic-cob-android-resource-server: 0.1.3-0
  • ros-kinetic-cob-android-script-server: 0.1.3-0
  • ros-kinetic-cob-android-settings: 0.1.3-0
  • ros-kinetic-cob-bringup: 0.6.7-1
  • ros-kinetic-cob-bringup-sim: 0.6.8-0
  • ros-kinetic-cob-collision-monitor: 0.7.0-0
  • ros-kinetic-cob-command-gui: 0.6.6-0
  • ros-kinetic-cob-command-tools: 0.6.6-0
  • ros-kinetic-cob-dashboard: 0.6.6-0
  • ros-kinetic-cob-default-robot-behavior: 0.6.7-1
  • ros-kinetic-cob-default-robot-config: 0.6.7-1
  • ros-kinetic-cob-gazebo: 0.6.8-0
  • ros-kinetic-cob-gazebo-objects: 0.6.8-0
  • ros-kinetic-cob-gazebo-worlds: 0.6.8-0
  • ros-kinetic-cob-grasp-generation: 0.7.0-0
  • ros-kinetic-cob-hardware-config: 0.6.7-1
  • ros-kinetic-cob-helper-tools: 0.6.6-0
  • ros-kinetic-cob-interactive-teleop: 0.6.6-0
  • ros-kinetic-cob-linear-nav: 0.6.5-0
  • ros-kinetic-cob-lookat-action: 0.7.0-0
  • ros-kinetic-cob-manipulation: 0.7.0-0
  • ros-kinetic-cob-map-accessibility-analysis: 0.6.5-0
  • ros-kinetic-cob-mapping-slam: 0.6.5-0
  • ros-kinetic-cob-monitoring: 0.6.6-0
  • ros-kinetic-cob-moveit-bringup: 0.7.0-0
  • ros-kinetic-cob-moveit-config: 0.6.7-1
  • ros-kinetic-cob-moveit-interface: 0.7.0-0
  • ros-kinetic-cob-navigation: 0.6.5-0
  • ros-kinetic-cob-navigation-config: 0.6.5-0
  • ros-kinetic-cob-navigation-global: 0.6.5-0
  • ros-kinetic-cob-navigation-local: 0.6.5-0
  • ros-kinetic-cob-navigation-slam: 0.6.5-0
  • ros-kinetic-cob-obstacle-distance-moveit: 0.7.0-0
  • ros-kinetic-cob-pick-place-action: 0.7.0-0
  • ros-kinetic-cob-robots: 0.6.7-1
  • ros-kinetic-cob-script-server: 0.6.6-0
  • ros-kinetic-cob-simulation: 0.6.8-0
  • ros-kinetic-cob-teleop: 0.6.6-0
  • ros-kinetic-denso: 2.0.1-0
  • ros-kinetic-denso-launch: 2.0.1-0
  • ros-kinetic-denso-ros-control: 2.0.1-0
  • ros-kinetic-generic-throttle: 0.6.6-0
  • ros-kinetic-hironx-calibration: 2.0.0-0
  • ros-kinetic-hironx-moveit-config: 2.0.0-0
  • ros-kinetic-hironx-ros-bridge: 2.0.0-0
  • ros-kinetic-hrpsys-ros-bridge: 1.4.0-1
  • ros-kinetic-hrpsys-tools: 1.4.0-1
  • ros-kinetic-hugin-panorama: 0.1.0-0
  • ros-kinetic-lost-comms-recovery: 0.1.0-0
  • ros-kinetic-openrtm-ros-bridge: 1.4.0-1
  • ros-kinetic-openrtm-tools: 1.4.0-1
  • ros-kinetic-parameter-pa: 1.1.0-0
  • ros-kinetic-pyros-interfaces-ros: 0.4.0-0
  • ros-kinetic-rosnode-rtc: 1.4.0-1
  • ros-kinetic-rtmbuild: 1.4.0-1
  • ros-kinetic-rtmros-common: 1.4.0-1
  • ros-kinetic-rtmros-hironx: 2.0.0-0
  • ros-kinetic-service-tools: 0.6.6-0
  • ros-kinetic-sick-visionary-t: 0.0.5-0
  • ros-kinetic-sick-visionary-t-driver: 0.0.5-0
  • ros-kinetic-simple-drive: 0.1.0-0
  • ros-kinetic-universal-robot: 1.2.0-0
  • ros-kinetic-ur-bringup: 1.2.0-0
  • ros-kinetic-ur-description: 1.2.0-0
  • ros-kinetic-ur-driver: 1.2.0-0
  • ros-kinetic-ur-gazebo: 1.2.0-0
  • ros-kinetic-ur-kinematics: 1.2.0-0
  • ros-kinetic-ur-msgs: 1.2.0-0
  • ros-kinetic-ur10-moveit-config: 1.2.0-0
  • ros-kinetic-ur3-moveit-config: 1.2.0-0
  • ros-kinetic-ur5-moveit-config: 1.2.0-0
  • ros-kinetic-vs060: 2.0.1-0
  • ros-kinetic-vs060-gazebo: 2.0.1-0
  • ros-kinetic-vs060-moveit-config: 2.0.1-0

Updated Packages [122]:

  • ros-kinetic-catkin-pip: 0.2.1-0 -> 0.2.3-0
  • ros-kinetic-combined-robot-hw: 0.11.5-0 -> 0.12.0-0
  • ros-kinetic-combined-robot-hw-tests: 0.11.5-0 -> 0.12.0-0
  • ros-kinetic-controller-interface: 0.11.5-0 -> 0.12.0-0
  • ros-kinetic-controller-manager: 0.11.5-0 -> 0.12.0-0
  • ros-kinetic-controller-manager-msgs: 0.11.5-0 -> 0.12.0-0
  • ros-kinetic-controller-manager-tests: 0.11.5-0 -> 0.12.0-0
  • ros-kinetic-cost-map: 0.3.1-0 -> 0.3.2-0
  • ros-kinetic-cost-map-core: 0.3.1-0 -> 0.3.2-0
  • ros-kinetic-cost-map-cv: 0.3.1-0 -> 0.3.2-0
  • ros-kinetic-cost-map-demos: 0.3.1-0 -> 0.3.2-0
  • ros-kinetic-cost-map-msgs: 0.3.1-0 -> 0.3.2-0
  • ros-kinetic-cost-map-ros: 0.3.1-0 -> 0.3.2-0
  • ros-kinetic-cost-map-visualisations: 0.3.1-0 -> 0.3.2-0
  • ros-kinetic-diff-drive-controller: 0.12.3-0 -> 0.13.0-0
  • ros-kinetic-dynamixel-sdk: 3.4.5-0 -> 3.4.7-0
  • ros-kinetic-effort-controllers: 0.12.3-0 -> 0.13.0-0
  • ros-kinetic-eigen-conversions: 1.11.8-0 -> 1.11.9-0
  • ros-kinetic-eigen-typekit: 2.9.0-0 -> 2.9.1-0
  • ros-kinetic-force-torque-sensor-controller: 0.12.3-0 -> 0.13.0-0
  • ros-kinetic-forward-command-controller: 0.12.3-0 -> 0.13.0-0
  • ros-kinetic-fzi-icl-can: 1.0.9-0 -> 1.0.10-0
  • ros-kinetic-fzi-icl-core: 1.0.4-0 -> 1.0.6-0
  • ros-kinetic-geometry: 1.11.8-0 -> 1.11.9-0
  • ros-kinetic-geometry2: 0.5.15-0 -> 0.5.16-0
  • ros-kinetic-gripper-action-controller: 0.12.3-0 -> 0.13.0-0
  • ros-kinetic-hardware-interface: 0.11.5-0 -> 0.12.0-0
  • ros-kinetic-hrpsys: 315.10.1-0 -> 315.14.0-0
  • ros-kinetic-imu-sensor-controller: 0.12.3-0 -> 0.13.0-0
  • ros-kinetic-joint-limits-interface: 0.11.5-0 -> 0.12.0-0
  • ros-kinetic-joint-state-controller: 0.12.3-0 -> 0.13.0-0
  • ros-kinetic-joint-trajectory-controller: 0.12.3-0 -> 0.13.0-0
  • ros-kinetic-kdl-conversions: 1.11.8-0 -> 1.11.9-0
  • ros-kinetic-kdl-typekit: 2.9.0-0 -> 2.9.1-0
  • ros-kinetic-mapviz: 0.2.3-0 -> 0.2.4-0
  • ros-kinetic-mapviz-plugins: 0.2.3-0 -> 0.2.4-0
  • ros-kinetic-marti-data-structures: 0.3.0-0 -> 1.0.0-0
  • ros-kinetic-mavlink: 2017.7.7-0 -> 2017.8.8-0
  • ros-kinetic-moveit: 0.9.8-0 -> 0.9.9-0
  • ros-kinetic-moveit-commander: 0.9.8-0 -> 0.9.9-0
  • ros-kinetic-moveit-controller-manager-example: 0.9.8-0 -> 0.9.9-0
  • ros-kinetic-moveit-core: 0.9.8-0 -> 0.9.9-0
  • ros-kinetic-moveit-fake-controller-manager: 0.9.8-0 -> 0.9.9-0
  • ros-kinetic-moveit-kinematics: 0.9.8-0 -> 0.9.9-0
  • ros-kinetic-moveit-planners: 0.9.8-0 -> 0.9.9-0
  • ros-kinetic-moveit-planners-ompl: 0.9.8-0 -> 0.9.9-0
  • ros-kinetic-moveit-plugins: 0.9.8-0 -> 0.9.9-0
  • ros-kinetic-moveit-ros: 0.9.8-0 -> 0.9.9-0
  • ros-kinetic-moveit-ros-benchmarks: 0.9.8-0 -> 0.9.9-0
  • ros-kinetic-moveit-ros-control-interface: 0.9.8-0 -> 0.9.9-0
  • ros-kinetic-moveit-ros-manipulation: 0.9.8-0 -> 0.9.9-0
  • ros-kinetic-moveit-ros-move-group: 0.9.8-0 -> 0.9.9-0
  • ros-kinetic-moveit-ros-perception: 0.9.8-0 -> 0.9.9-0
  • ros-kinetic-moveit-ros-planning: 0.9.8-0 -> 0.9.9-0
  • ros-kinetic-moveit-ros-planning-interface: 0.9.8-0 -> 0.9.9-0
  • ros-kinetic-moveit-ros-robot-interaction: 0.9.8-0 -> 0.9.9-0
  • ros-kinetic-moveit-ros-visualization: 0.9.8-0 -> 0.9.9-0
  • ros-kinetic-moveit-ros-warehouse: 0.9.8-0 -> 0.9.9-0
  • ros-kinetic-moveit-runtime: 0.9.8-0 -> 0.9.9-0
  • ros-kinetic-moveit-setup-assistant: 0.9.8-0 -> 0.9.9-0
  • ros-kinetic-moveit-simple-controller-manager: 0.9.8-0 -> 0.9.9-0
  • ros-kinetic-multires-image: 0.2.3-0 -> 0.2.4-0
  • ros-kinetic-nav-pcontroller: 0.1.2-0 -> 0.1.4-0
  • ros-kinetic-openhrp3: 3.1.9-1 -> 3.1.9-3
  • ros-kinetic-oxford-gps-eth: 0.0.4-0 -> 0.0.5-0
  • ros-kinetic-p2os-doc: 2.0.6-0 -> 2.1.0-0
  • ros-kinetic-p2os-driver: 2.0.6-0 -> 2.1.0-0
  • ros-kinetic-p2os-launch: 2.0.6-0 -> 2.1.0-0
  • ros-kinetic-p2os-msgs: 2.0.6-0 -> 2.1.0-0
  • ros-kinetic-p2os-teleop: 2.0.6-0 -> 2.1.0-0
  • ros-kinetic-p2os-urdf: 2.0.6-0 -> 2.1.0-0
  • ros-kinetic-parrot-arsdk: 3.11.0-0 -> 3.12.61-0
  • ros-kinetic-position-controllers: 0.12.3-0 -> 0.13.0-0
  • ros-kinetic-pyros: 0.3.2-0 -> 0.4.1-1
  • ros-kinetic-pyzmp: 0.0.14-7 -> 0.0.15-0
  • ros-kinetic-robotis-controller: 0.2.5-0 -> 0.2.6-0
  • ros-kinetic-robotis-device: 0.2.5-0 -> 0.2.6-0
  • ros-kinetic-robotis-framework: 0.2.5-0 -> 0.2.6-0
  • ros-kinetic-robotis-framework-common: 0.2.5-0 -> 0.2.6-0
  • ros-kinetic-ros-control: 0.11.5-0 -> 0.12.0-0
  • ros-kinetic-ros-controllers: 0.12.3-0 -> 0.13.0-0
  • ros-kinetic-rqt-controller-manager: 0.11.5-0 -> 0.12.0-0
  • ros-kinetic-rqt-joint-trajectory-controller: 0.12.3-0 -> 0.13.0-0
  • ros-kinetic-rtt-geometry: 2.9.0-0 -> 2.9.1-0
  • ros-kinetic-rviz: 1.12.10-0 -> 1.12.11-0
  • ros-kinetic-swri-console-util: 0.3.0-0 -> 1.0.0-0
  • ros-kinetic-swri-geometry-util: 0.3.0-0 -> 1.0.0-0
  • ros-kinetic-swri-image-util: 0.3.0-0 -> 1.0.0-0
  • ros-kinetic-swri-math-util: 0.3.0-0 -> 1.0.0-0
  • ros-kinetic-swri-nodelet: 0.3.0-0 -> 1.0.0-0
  • ros-kinetic-swri-opencv-util: 0.3.0-0 -> 1.0.0-0
  • ros-kinetic-swri-prefix-tools: 0.3.0-0 -> 1.0.0-0
  • ros-kinetic-swri-roscpp: 0.3.0-0 -> 1.0.0-0
  • ros-kinetic-swri-rospy: 0.3.0-0 -> 1.0.0-0
  • ros-kinetic-swri-route-util: 0.3.0-0 -> 1.0.0-0
  • ros-kinetic-swri-serial-util: 0.3.0-0 -> 1.0.0-0
  • ros-kinetic-swri-string-util: 0.3.0-0 -> 1.0.0-0
  • ros-kinetic-swri-system-util: 0.3.0-0 -> 1.0.0-0
  • ros-kinetic-swri-transform-util: 0.3.0-0 -> 1.0.0-0
  • ros-kinetic-swri-yaml-util: 0.3.0-0 -> 1.0.0-0
  • ros-kinetic-tf: 1.11.8-0 -> 1.11.9-0
  • ros-kinetic-tf-conversions: 1.11.8-0 -> 1.11.9-0
  • ros-kinetic-tf2: 0.5.15-0 -> 0.5.16-0
  • ros-kinetic-tf2-bullet: 0.5.15-0 -> 0.5.16-0
  • ros-kinetic-tf2-eigen: 0.5.15-0 -> 0.5.16-0
  • ros-kinetic-tf2-geometry-msgs: 0.5.15-0 -> 0.5.16-0
  • ros-kinetic-tf2-kdl: 0.5.15-0 -> 0.5.16-0
  • ros-kinetic-tf2-msgs: 0.5.15-0 -> 0.5.16-0
  • ros-kinetic-tf2-py: 0.5.15-0 -> 0.5.16-0
  • ros-kinetic-tf2-ros: 0.5.15-0 -> 0.5.16-0
  • ros-kinetic-tf2-sensor-msgs: 0.5.15-0 -> 0.5.16-0
  • ros-kinetic-tf2-tools: 0.5.15-0 -> 0.5.16-0
  • ros-kinetic-tile-map: 0.2.3-0 -> 0.2.4-0
  • ros-kinetic-transmission-interface: 0.11.5-0 -> 0.12.0-0
  • ros-kinetic-turtlebot3: 0.1.5-0 -> 0.1.6-0
  • ros-kinetic-turtlebot3-bringup: 0.1.5-0 -> 0.1.6-0
  • ros-kinetic-turtlebot3-description: 0.1.5-0 -> 0.1.6-0
  • ros-kinetic-turtlebot3-navigation: 0.1.5-0 -> 0.1.6-0
  • ros-kinetic-turtlebot3-slam: 0.1.5-0 -> 0.1.6-0
  • ros-kinetic-turtlebot3-teleop: 0.1.5-0 -> 0.1.6-0
  • ros-kinetic-urdf-geometry-parser: 0.0.2-0 -> 0.0.3-0
  • ros-kinetic-velocity-controllers: 0.12.3-0 -> 0.13.0-0

Removed Packages [0]:

Mantainers

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:

  • Adolfo Rodriguez Tsouroukdissian
  • AlexV
  • Alexis Maldonado
  • Bence Magyar
  • Benjamin Maidel
  • D. Hood
  • Daniel Snider
  • Daniel Stonier
  • Dave Coleman
  • Ed Venator
  • Elliot Johnson
  • Felix Messmer
  • Florian Weisshardt
  • Georg Heppner
  • Hunter L. Allen
  • Ioan Sucan
  • Isaac I. Y. Saito
  • Jon Binney
  • Joshua Hampp
  • Kei Okada
  • Kelsey Hawkins
  • Kevin Hallenbeck
  • Koji Terada
  • Kris Kozak
  • Mahsa Parsapour
  • Mani Monajjemi
  • Marc Alban
  • Mathias Luedtke
  • Mathias Lüdtke
  • Matthias Gruhler
  • Michael Ferguson
  • Michael Görner
  • Nadia Hammoudeh Garcia
  • Orocos Developers
  • Peter Weissig
  • Pyo
  • Richard Bormann
  • Ryohei Ueda
  • Sachin Chitta
  • Shohei Fujii
  • TORK
  • Toni Oliver
  • Tully Foote
  • Vincent Rabaud
  • Vincent Rousseau
  • Vladimir Ermakov
  • heppner

Posts: 1

Participants: 1

Read full topic

by @tfoote Tully Foote on August 15, 2017 06:35 AM

August 14, 2017
Laszlo Nagy (PPM AS) The Intuitive ROS UI: FlexGui 4.0 - introduction and industrial applications

Looking foward to ROSCon 2017 we're highlighting presentations from last year. The ROSCon 2017 registration is currently open.

Video

Abstract

FlexGui 4.0 is based upon popular web technologies: HTML5, CSS and JavaScript. This way it is possible to run FlexGUI 4.0 on PC, Android, iPhone, Windows Phone and generally on every device with a modern browser, you will h ave exactly the same user experience on each of them. FlexGui 4.0 communicates using ROS, our choice of middleware for Industry 4.0, IoT. Join the session and let us introduce ourselves, see some of our industrial applications, ask us how could we help you with yours!

Slides

View the slides here

by Tully Foote on August 14, 2017 11:06 PM

Suspension of Debian packaging for EOL Ubuntu Yakkety

@marguedas wrote:

Hi ROS users!

Since we have support to turn off EOL distros on the buildfarm, we announced that we will disable distros soon after they become EOL.
Ubuntu Yakkety (16.10) has been EOL since July, and we are considering turning it off after the upcoming Lunar sync. This will allow the buildfarm to run faster and the maintainer-ship workload to be reduced for maintainers releasing in Lunar.

As a result, we will build Lunar binaries for:

  • Ubuntu Xenial and Zesty
  • Debian Stretch

Please comment here if you have any feedback !

Posts: 1

Participants: 1

Read full topic

by @marguedas Mikael Arguedas on August 14, 2017 04:58 PM

ROS Onsite Courses | Sep 2017

@YUHONG_LIN wrote:

ROS Onsite Courses | September 2017

Dear Roboticists,

The ROS Onsite Courses will be starting on September 4. These courses are ideal for start learning ROS from zero and advance ROS learning to next level.
You can select:

ROS IN 5 DAYS (Entering ROS)
ROS NAVIGATION + ROS Auto-Vehicles 101 (Mastering ROS)

You can enroll the courses here: http://www.theconstructsim.com/ros-onsite-course-sep2017/

Entirely practical Robot Operating System training which integrates theory and practice, learn by programming different simulated robots and full integrated development environment.

:: ABOUT THE COURSES

Class given in Barcelona.
Morning: teaching with exercises from 9:30 to 13:30
Afternoon: working on ROS project from 14:30 to 16:30

  • Exclusive for ONLY 5 individuals

  • Exam and ROS Certification: There will be an exam at the end of the course. Those who pass the exam will receive a ROS certification.

  • Duration:
    ROS IN 5 DAYS: Sep 4th to 8th, 2017
    ROS Navigation+ROS Auto-Vehicles 101: Sep 11th to 15th, 2017

  • Location: Gran Via de les Corts Catalanes, 608, 3ºD, 08007 Barcelona, SPAIN

:: SCHEDULE

ROS IN 5 DAYS (from 4th to 8th, September)

  • Monday: ROS BASICS: basic structure of ROS programs and its concepts
  • Tuesday: ROS TOPICS: how to create topics and how to access them
  • Wednesday: ROS SERVICES: how to create services and how to use them
  • Thursday: ROS ACTIONS: how to create action servers and use them
  • Friday: ROS DEBUG: ROS tools that allow to find errors and debug and EXAM

ROS NAVIGATION + ROS Autonomous Vehicles 101 (from 11th to 15th, September)

  • Monday: Navigation Basics concepts
  • Tuesday: Mapping
  • Wednesday: Localisation
  • Thursday: Path Planning + Obstacle Avoidance
  • Friday: ROS Autonous Vehicles 101 + EXAM

:: REQUIREMENTS FOR ATTENDANCE

  • Basic knowledge of Linux shell
  • Basic knowledge of Python programming
  • A laptop (can have any operating system)
  • NO PRIOR KNOWLEDGE OF ROS REQUIRED (for ROS IN 5 DAYS)
  • Basic ROS knowledge (for ROS Navigation + ROS Auto-Vehicles 101)

:: CONTACT US

Posts: 1

Participants: 1

Read full topic

by @YUHONG_LIN on August 14, 2017 10:56 AM

Invitation to the Second Danish ROS MeetUp

@kdhansen wrote:

Dear members of the Danish ROS community,

You are all cordially invited to the Second Danish ROS MeetUp, Wednesday, August 30th.

This year The Danish Technological Institute (DTI) in Odense will host the MeetUp. We will have a keynote from Dr. Mirko Bordignon, Fraunhofer IPA on ROS-I and local Danish members* will present their ROS-related work. There will be a guided tour around DTI with plenty of opportunities to look at some cool tech, and naturally ample time to network and meet new people during the lunch and intermissions.

If you are interested please got to http://www.teknologisk.dk/ros to sign up.

Please consider giving a presentation if you have anything you want to tell or want feedback on. We are a small informal group so everything is interesting. See how to on the sign up page.

* There are no membership fees or anything, everybody is invited. Just sign up, we all look forward to meeting you.

Posts: 1

Participants: 1

Read full topic

by @kdhansen Karl D. Hansen on August 14, 2017 09:50 AM

August 11, 2017
New Packages for Indigo 2017-08-10

@tfoote wrote:

We have another batch of packages released for Indigo. There are a couple of new packages as well as over 100 updated packages.

Thanks to everyone who contributed to these new packages! Including sync preparations and all the maintainers and contributors.

Full details are below.

Updates to indigo

Added Packages [5]:

  • ros-indigo-cob-moveit-bringup: 0.6.5-1
  • ros-indigo-fetch-ikfast-plugin: 0.7.12-0
  • ros-indigo-pcdfilter-pa: 1.1.0-0
  • ros-indigo-sick-visionary-t: 0.0.5-1
  • ros-indigo-tele-dir: 0.0.5-0

Updated Packages [135]:

  • ros-indigo-cob-bringup: 0.6.6-0 -> 0.6.7-1
  • ros-indigo-cob-bringup-sim: 0.6.7-0 -> 0.6.8-0
  • ros-indigo-cob-collision-monitor: 0.6.4-0 -> 0.6.5-1
  • ros-indigo-cob-default-robot-behavior: 0.6.6-0 -> 0.6.7-1
  • ros-indigo-cob-default-robot-config: 0.6.6-0 -> 0.6.7-1
  • ros-indigo-cob-gazebo: 0.6.7-0 -> 0.6.8-0
  • ros-indigo-cob-gazebo-objects: 0.6.7-0 -> 0.6.8-0
  • ros-indigo-cob-gazebo-worlds: 0.6.7-0 -> 0.6.8-0
  • ros-indigo-cob-grasp-generation: 0.6.4-0 -> 0.6.5-1
  • ros-indigo-cob-hardware-config: 0.6.6-0 -> 0.6.7-1
  • ros-indigo-cob-kinematics: 0.6.4-0 -> 0.6.5-1
  • ros-indigo-cob-lookat-action: 0.6.4-0 -> 0.6.5-1
  • ros-indigo-cob-manipulation: 0.6.4-0 -> 0.6.5-1
  • ros-indigo-cob-moveit-config: 0.6.4-0 -> 0.6.7-1
  • ros-indigo-cob-moveit-interface: 0.6.4-0 -> 0.6.5-1
  • ros-indigo-cob-obstacle-distance-moveit: 0.6.4-0 -> 0.6.5-1
  • ros-indigo-cob-pick-place-action: 0.6.4-0 -> 0.6.5-1
  • ros-indigo-cob-robots: 0.6.6-0 -> 0.6.7-1
  • ros-indigo-cob-simulation: 0.6.7-0 -> 0.6.8-0
  • ros-indigo-cost-map: 0.3.1-0 -> 0.3.2-0
  • ros-indigo-cost-map-core: 0.3.1-0 -> 0.3.2-0
  • ros-indigo-cost-map-cv: 0.3.1-0 -> 0.3.2-0
  • ros-indigo-cost-map-demos: 0.3.1-0 -> 0.3.2-0
  • ros-indigo-cost-map-msgs: 0.3.1-0 -> 0.3.2-0
  • ros-indigo-cost-map-ros: 0.3.1-0 -> 0.3.2-0
  • ros-indigo-cost-map-visualisations: 0.3.1-0 -> 0.3.2-0
  • ros-indigo-eigen-conversions: 1.11.8-0 -> 1.11.9-0
  • ros-indigo-eigen-typekit: 2.8.1-0 -> 2.8.1-1
  • ros-indigo-fetch-arm-control: 0.0.7-0 -> 0.0.8-0
  • ros-indigo-fetch-calibration: 0.7.9-0 -> 0.7.12-0
  • ros-indigo-fetch-depth-layer: 0.7.9-0 -> 0.7.12-0
  • ros-indigo-fetch-description: 0.7.9-0 -> 0.7.12-0
  • ros-indigo-fetch-maps: 0.7.9-0 -> 0.7.12-0
  • ros-indigo-fetch-moveit-config: 0.7.9-0 -> 0.7.12-0
  • ros-indigo-fetch-navigation: 0.7.9-0 -> 0.7.12-0
  • ros-indigo-fetch-pbd-interaction: 0.0.7-0 -> 0.0.8-0
  • ros-indigo-fetch-social-gaze: 0.0.7-0 -> 0.0.8-0
  • ros-indigo-fetch-teleop: 0.7.9-0 -> 0.7.12-0
  • ros-indigo-freight-calibration: 0.7.9-0 -> 0.7.12-0
  • ros-indigo-fzi-icl-can: 1.0.9-0 -> 1.0.10-0
  • ros-indigo-fzi-icl-core: 1.0.4-0 -> 1.0.6-0
  • ros-indigo-gazebo-msgs: 2.4.13-0 -> 2.4.15-0
  • ros-indigo-gazebo-plugins: 2.4.13-0 -> 2.4.15-0
  • ros-indigo-gazebo-ros: 2.4.13-0 -> 2.4.15-0
  • ros-indigo-gazebo-ros-control: 2.4.13-0 -> 2.4.15-0
  • ros-indigo-gazebo-ros-pkgs: 2.4.13-0 -> 2.4.15-0
  • ros-indigo-geometry: 1.11.8-0 -> 1.11.9-0
  • ros-indigo-geometry-experimental: 0.5.15-0 -> 0.5.16-0
  • ros-indigo-geometry2: 0.5.15-0 -> 0.5.16-0
  • ros-indigo-hironx-calibration: 1.1.25-0 -> 2.0.0-0
  • ros-indigo-hironx-moveit-config: 1.1.25-0 -> 2.0.0-0
  • ros-indigo-hironx-ros-bridge: 1.1.25-0 -> 2.0.0-0
  • ros-indigo-hrpsys: 315.12.1-0 -> 315.14.0-0
  • ros-indigo-kdl-conversions: 1.11.8-0 -> 1.11.9-0
  • ros-indigo-kdl-typekit: 2.8.1-0 -> 2.8.1-1
  • ros-indigo-mapviz: 0.0.7-0 -> 0.0.8-0
  • ros-indigo-mapviz-plugins: 0.0.7-0 -> 0.0.8-0
  • ros-indigo-marti-data-structures: 0.3.0-0 -> 1.0.0-0
  • ros-indigo-moveit: 0.7.11-0 -> 0.7.12-0
  • ros-indigo-moveit-commander: 0.7.11-0 -> 0.7.12-0
  • ros-indigo-moveit-controller-manager-example: 0.7.11-0 -> 0.7.12-0
  • ros-indigo-moveit-core: 0.7.11-0 -> 0.7.12-0
  • ros-indigo-moveit-fake-controller-manager: 0.7.11-0 -> 0.7.12-0
  • ros-indigo-moveit-full: 0.7.11-0 -> 0.7.12-0
  • ros-indigo-moveit-full-pr2: 0.7.11-0 -> 0.7.12-0
  • ros-indigo-moveit-goal-builder: 0.1.0-0 -> 0.1.1-0
  • ros-indigo-moveit-kinematics: 0.7.11-0 -> 0.7.12-0
  • ros-indigo-moveit-planners: 0.7.11-0 -> 0.7.12-0
  • ros-indigo-moveit-planners-ompl: 0.7.11-0 -> 0.7.12-0
  • ros-indigo-moveit-plugins: 0.7.11-0 -> 0.7.12-0
  • ros-indigo-moveit-pr2: 0.6.5-0 -> 0.6.6-0
  • ros-indigo-moveit-ros: 0.7.11-0 -> 0.7.12-0
  • ros-indigo-moveit-ros-benchmarks: 0.7.11-0 -> 0.7.12-0
  • ros-indigo-moveit-ros-benchmarks-gui: 0.7.11-0 -> 0.7.12-0
  • ros-indigo-moveit-ros-control-interface: 0.7.11-0 -> 0.7.12-0
  • ros-indigo-moveit-ros-manipulation: 0.7.11-0 -> 0.7.12-0
  • ros-indigo-moveit-ros-move-group: 0.7.11-0 -> 0.7.12-0
  • ros-indigo-moveit-ros-perception: 0.7.11-0 -> 0.7.12-0
  • ros-indigo-moveit-ros-planning: 0.7.11-0 -> 0.7.12-0
  • ros-indigo-moveit-ros-planning-interface: 0.7.11-0 -> 0.7.12-0
  • ros-indigo-moveit-ros-robot-interaction: 0.7.11-0 -> 0.7.12-0
  • ros-indigo-moveit-ros-visualization: 0.7.11-0 -> 0.7.12-0
  • ros-indigo-moveit-ros-warehouse: 0.7.11-0 -> 0.7.12-0
  • ros-indigo-moveit-runtime: 0.7.11-0 -> 0.7.12-0
  • ros-indigo-moveit-setup-assistant: 0.7.11-0 -> 0.7.12-0
  • ros-indigo-moveit-simple-controller-manager: 0.7.11-0 -> 0.7.12-0
  • ros-indigo-multires-image: 0.0.7-0 -> 0.0.8-0
  • ros-indigo-nav-pcontroller: 0.1.2-0 -> 0.1.4-0
  • ros-indigo-oxford-gps-eth: 0.0.4-0 -> 0.0.5-0
  • ros-indigo-parameter-pa: 1.0.0-0 -> 1.1.0-0
  • ros-indigo-pr2-moveit-config: 0.6.5-0 -> 0.6.6-0
  • ros-indigo-pr2-moveit-plugins: 0.6.5-0 -> 0.6.6-0
  • ros-indigo-rail-manipulation-msgs: 0.0.10-0 -> 0.0.11-0
  • ros-indigo-rtmros-hironx: 1.1.25-0 -> 2.0.0-0
  • ros-indigo-rtt-geometry: 2.8.1-0 -> 2.8.1-1
  • ros-indigo-rviz: 1.11.16-0 -> 1.11.17-0
  • ros-indigo-sick-visionary-t-driver: 0.0.3-1 -> 0.0.5-1
  • ros-indigo-swri-console-util: 0.3.0-0 -> 1.0.0-0
  • ros-indigo-swri-geometry-util: 0.3.0-0 -> 1.0.0-0
  • ros-indigo-swri-image-util: 0.3.0-0 -> 1.0.0-0
  • ros-indigo-swri-math-util: 0.3.0-0 -> 1.0.0-0
  • ros-indigo-swri-nodelet: 0.3.0-0 -> 1.0.0-0
  • ros-indigo-swri-opencv-util: 0.3.0-0 -> 1.0.0-0
  • ros-indigo-swri-prefix-tools: 0.3.0-0 -> 1.0.0-0
  • ros-indigo-swri-roscpp: 0.3.0-0 -> 1.0.0-0
  • ros-indigo-swri-rospy: 0.3.0-0 -> 1.0.0-0
  • ros-indigo-swri-route-util: 0.3.0-0 -> 1.0.0-0
  • ros-indigo-swri-serial-util: 0.3.0-0 -> 1.0.0-0
  • ros-indigo-swri-string-util: 0.3.0-0 -> 1.0.0-0
  • ros-indigo-swri-system-util: 0.3.0-0 -> 1.0.0-0
  • ros-indigo-swri-transform-util: 0.3.0-0 -> 1.0.0-0
  • ros-indigo-swri-yaml-util: 0.3.0-0 -> 1.0.0-0
  • ros-indigo-tf: 1.11.8-0 -> 1.11.9-0
  • ros-indigo-tf-conversions: 1.11.8-0 -> 1.11.9-0
  • ros-indigo-tf2: 0.5.15-0 -> 0.5.16-0
  • ros-indigo-tf2-bullet: 0.5.15-0 -> 0.5.16-0
  • ros-indigo-tf2-eigen: 0.5.15-0 -> 0.5.16-0
  • ros-indigo-tf2-geometry-msgs: 0.5.15-0 -> 0.5.16-0
  • ros-indigo-tf2-kdl: 0.5.15-0 -> 0.5.16-0
  • ros-indigo-tf2-msgs: 0.5.15-0 -> 0.5.16-0
  • ros-indigo-tf2-py: 0.5.15-0 -> 0.5.16-0
  • ros-indigo-tf2-ros: 0.5.15-0 -> 0.5.16-0
  • ros-indigo-tf2-sensor-msgs: 0.5.15-0 -> 0.5.16-0
  • ros-indigo-tf2-tools: 0.5.15-0 -> 0.5.16-0
  • ros-indigo-tile-map: 0.0.7-0 -> 0.0.8-0
  • ros-indigo-universal-robot: 1.1.9-0 -> 1.1.10-1
  • ros-indigo-ur-bringup: 1.1.9-0 -> 1.1.10-1
  • ros-indigo-ur-description: 1.1.9-0 -> 1.1.10-1
  • ros-indigo-ur-driver: 1.1.9-0 -> 1.1.10-1
  • ros-indigo-ur-gazebo: 1.1.9-0 -> 1.1.10-1
  • ros-indigo-ur-kinematics: 1.1.9-0 -> 1.1.10-1
  • ros-indigo-ur-msgs: 1.1.9-0 -> 1.1.10-1
  • ros-indigo-ur10-moveit-config: 1.1.9-0 -> 1.1.10-1
  • ros-indigo-ur3-moveit-config: 1.1.9-0 -> 1.1.10-1
  • ros-indigo-ur5-moveit-config: 1.1.9-0 -> 1.1.10-1

Removed Packages [1]:

  • ros-indigo-cob-controller-configuration-gazebo

Maintainers

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:

  • Alexis Maldonado
  • D. Hood
  • Daniel Stonier
  • Dave Coleman
  • David Kent
  • Ed Venator
  • Elliot Johnson
  • Felix Messmer
  • Florian Weisshardt
  • Georg Heppner
  • Ioan Sucan
  • Isaac I. Y. Saito
  • John Hsu
  • Jonathan Bohren
  • Joshua Hampp
  • Justin Huang
  • Kei Okada
  • Kevin Hallenbeck
  • Koji Terada
  • Kris Kozak
  • Marc Alban
  • Mathias Luedtke
  • Mathias Lüdtke
  • Michael Ferguson
  • MoveIt Setup Assistant
  • Nadia Hammoudeh Garcia
  • Orocos Developers
  • Peter Weissig
  • Rodrigo Delgado
  • Sachin Chitta
  • Sarah Elliott
  • TORK
  • Tully Foote
  • Vincent Rabaud
  • heppner

Posts: 1

Participants: 1

Read full topic

by @tfoote Tully Foote on August 11, 2017 07:02 PM

ROS-Industrial Training - Singapore in 2 weeks, spaces are still available!

@MinLing_C wrote:

The ROS-Industrial Consortium Asia Pacific is hosting our first ROS-Industrial Developer Training Class with a ROS-Industrial trainer, Levi Armstrong (SwRI, ROS-Industrial Americas). There are two training classes available these are:

  • A three-day ROS-Industrial Developers Training Class on August 21-23, 2017

  • A one-day ROS-Industrial Advanced Training Class on August 24, 2017.

Please bring a laptop to the class with the ROS-I training Virtual Machine pre-installed. This class is geared toward individuals with a C++ programming background who seek to learn to compose their own ROS nodes.

Register here!

Posts: 1

Participants: 1

Read full topic

by @MinLing_C Min Ling C on August 11, 2017 08:07 AM

August 10, 2017
CrazyPi Kit with 4K Lidar designed for ROS, with real-time remote video&audio and visual map building on web

@crazyou wrote:

a ROS Kit with visual SLAM and real-time video&audio stream
https://www.kickstarter.com/projects/crazypi/crazypi-the-maker-board-designed-for-diy-robot-mak

Posts: 1

Participants: 1

Read full topic

by @crazyou Crazyou on August 10, 2017 05:11 PM

August 08, 2017
Final in series on ROS-I development process – Publishing & Installation

This is the last post in a series detailing the ROS-Industrial software development process. We will discuss publishing and installing software. The first post described the process of contributing code to a project (item 1-3 in the figure above). The second post described the process of Continuous Integration, Pull Request (PR) peer review , and the release of a given repositories packages by the maintainer (item 4-7). Note that the starred numbers in the software development process illustrated above correspond to the outline below.

  1. The publishing of the released packages (item 8) is managed by OSRF and is not on a set schedule. This usually happens when all packages for a given distro are built successfully and stable. The current status for the distro kinetic can be found here . Navigating to other distros can be done by changing the distro name in the link.
  2. Once the package has been published, it is available to be installed by the developer (item 9).
  3. After the install of a new version, the developer may have questions, experience issues or it may not have the necessary functionality which should all be reported on the packages GitHub repository as an issue (item 10). If an issue is identified or there is missing functionality that the developer requires, the cycle starts back at (item 2).
The full series has been compiled and is now located on ROS-Industrial website here

by Levi Armstrong on August 08, 2017 03:29 PM

Participants for a Survey on Collaboration and Package Reuse in ROS

@pestefo wrote:

Hi ROS users,

As part of my PhD thesis, I’m studying the phenomenon of package reuse within the ROS community and the way that the community collaborates. To have a deeper insight on these topics, I designed a survey and your participation is extremely valuable. It should take 10 min. approximately to complete.

It is important to say that the answers are confidential and will be treated anonymously. If you would like a summary of the data collected, your e-mail will be requested at the end of the survey. Three Amazon Gift Cards will be raffled:star2: among participants that entered their e-mail address*, naturally.

:white_check_mark: Click here to take the survey

I will be grateful if you could spread it among your colleagues with any experience in ROS.

:warning: Answers will be received no later than August 15th! New deadline: Friday 18th :bangbang:

Thank you all in advance :grinning:

*: The e-mail is requested only to send the summary of the results and to be able to deliver the gift card to the raffle winners. It will not affect our confidentiality and anonymity policy on use of the data.

Posts: 2

Participants: 1

Read full topic

by @pestefo Pablo Estefó on August 08, 2017 02:09 AM

August 07, 2017
Levi Armstrong (SwRI) ROS Qt Creator Project Manager Plug-in

Looking foward to ROSCon 2017 we're highlighting presentations from last year. The ROSCon 2017 registration is currently open.

Here's Levi presenting his work to integrate ROS projects into the QT Creator pipeline.

Video

Abstract

The ROS Qt Creator Plug-in is developed specifically for ROS to increase developers' efficiency by simplifying tasks and creating a centralized location for ROS tools. Since it is built on top of the Qt Creator platform, users have access to all of its existing features like: syntax highlighting, editors (C++, Python, etc.), code completion, version control (Git, Subversion, etc.), debuggers (GDB, CDB, LLDB, etc.), and much more. The talk will cover: a description and motivation; overview of current and future features; and example of how to use the plug-in to manage a ROS Workspace.

Slides

View the slides here

by Tully Foote on August 07, 2017 10:31 PM

Mirko Bordignon et al. ROS-Industrial turns four and expands worldwide

Looking foward to ROSCon 2017 we're highlighting presentations from last year. The ROSCon 2017 registration is currently open.

Mirko Bordignon (Fraunhofer IPA) Min Ling (ARTC - A*STAR) Shaun Edwards (Southwest Research Institute) present the state of ROS-Industrial as it turns 4 years old and expands to add an Asia-Pacific chapter.

Video

Abstract

Four years after it was first launched by Shaun Edwards, ROS-Industrial is now a worldwide effort to expand and improve ROS adoption in manufacturing environments and industrial equipment. As an initiative, it is supported financially by OEMs and system integrators, whose interests are represented and requests are collected within three ROS-Industrial Consortia managed by non-profit, applied research institutions. As a software platform, it is developed by a free and open community gathering in monthly meetings and operating through a federated development model, much like the ROS developers community. The talk will showcase real-world examples and current efforts to expand the initiative and to continue addressing technical and non-technical concerns.

Slides

View the slides here

by Tully Foote on August 07, 2017 10:21 PM

August 03, 2017
Announcing the "rrt_exploration" package

@hasauino wrote:

Dear ROS users,
I’d like to announce the rrt_exploration package. It is a ROS package that implements a multi-robot RRT-based map exploration algorithm. It also has the image-based frontier detection that uses image processing to extract frontier points.

You can use it to make you robot do exploration. It can be used on a single or multiple robots.

Wiki page: http://wiki.ros.org/rrt_exploration
Section 7 of the wiki page is dedicated for tutorials.

Github links:
- The package itself: https://github.com/hasauino/rrt_exploration
- Gazebo simulation files: https://github.com/hasauino/rrt_exploration_tutorials

Your feedback is appreciated.

Thanks,
Hassan Umari

Posts: 1

Participants: 1

Read full topic

by @hasauino Hassan Umari on August 03, 2017 07:07 AM

July 31, 2017
ROS connevity with MATLAB on Window and Docker

@ntmilkt wrote:

I am trying to set development environment for ROS Kinetic using Docker and MATLAB.

Host OS is Windows 10 that include MATLAB robotics system toolbox for ROS.
Docker4Windows is installed on Windows 10 with ROS:Kinetic.

Window10(ML:10.0.75.1) - Docker(Hyper-V:10.0.75.2) - Containers(Master, Listener and Talker under bridge network, 172.18.0.X)

I followed up tutorials to communicate container. But I couldn`t reach to communicate with Host.
MATLAB can see the topic list. But receiving message is not worked.
I searched a lot of page and did many approaches include dns, resolvable and other network mode.
Final target is send/receive ROS message between MATLAB on window and containers.

Do you have any idea? or solution?

Below github based modifications are what I have tried last few weeks.

Posts: 3

Participants: 2

Read full topic

by @ntmilkt Ntmilkt on July 31, 2017 09:00 AM

July 27, 2017
Gazebo8 ROS Lunar wrappers available

@jrivero wrote:

Hi all:

The stable repository packages.osrfoundation.org now hosts the ROS Lunar wrappers binaries for the latest release of Gazebo: gazebo8. This new version of the wrappers joins the Kinetic gazebo8 packages. Both are only available on Ubuntu Xenial since it is the only common platform supported by ROS and gazebo8.

Before using this alternative version of Gazebo in Lunar or Kinetic, please read carefully the documentation:
http://gazebosim.org/tutorials/?tut=ros_wrapper_versions

Enjoy.

Posts: 1

Participants: 1

Read full topic

by @jrivero Jose Luis Rivero on July 27, 2017 06:12 PM

July 26, 2017
New Packages for Kinetic 2017-07-25

@tfoote wrote:

We’re happy to announce another set of packages for Kinetic as well. We have 86 new packages as well as 78 updated packages in this sync.

Thank you to all the contributors and maintainers who make these packages available to the community.

Full details are below.

Package Updates for kinetic

Added Packages [86]:

  • ros-kinetic-cob-3d-mapping-msgs: 0.6.10-0
  • ros-kinetic-cob-base-drive-chain: 0.6.10-0
  • ros-kinetic-cob-base-velocity-smoother: 0.7.0-0
  • ros-kinetic-cob-bms-driver: 0.6.10-0
  • ros-kinetic-cob-calibration-data: 0.6.7-0
  • ros-kinetic-cob-cam3d-throttle: 0.6.10-0
  • ros-kinetic-cob-camera-sensors: 0.6.10-0
  • ros-kinetic-cob-canopen-motor: 0.6.10-0
  • ros-kinetic-cob-cartesian-controller: 0.7.0-0
  • ros-kinetic-cob-collision-velocity-filter: 0.7.0-0
  • ros-kinetic-cob-common: 0.6.7-0
  • ros-kinetic-cob-control: 0.7.0-0
  • ros-kinetic-cob-control-mode-adapter: 0.7.0-0
  • ros-kinetic-cob-control-msgs: 0.7.0-0
  • ros-kinetic-cob-default-env-config: 0.6.5-0
  • ros-kinetic-cob-description: 0.6.7-0
  • ros-kinetic-cob-docker-control: 0.6.6-0
  • ros-kinetic-cob-driver: 0.6.10-0
  • ros-kinetic-cob-elmo-homing: 0.6.10-0
  • ros-kinetic-cob-environments: 0.6.5-0
  • ros-kinetic-cob-extern: 0.6.11-0
  • ros-kinetic-cob-footprint-observer: 0.7.0-0
  • ros-kinetic-cob-frame-tracker: 0.7.0-0
  • ros-kinetic-cob-gazebo-plugins: 0.7.1-0
  • ros-kinetic-cob-gazebo-ros-control: 0.7.1-0
  • ros-kinetic-cob-generic-can: 0.6.10-0
  • ros-kinetic-cob-hand: 0.6.2-0
  • ros-kinetic-cob-hand-bridge: 0.6.2-0
  • ros-kinetic-cob-head-axis: 0.6.10-0
  • ros-kinetic-cob-image-flip: 0.6.10-0
  • ros-kinetic-cob-light: 0.6.10-0
  • ros-kinetic-cob-mimic: 0.6.10-0
  • ros-kinetic-cob-model-identifier: 0.7.0-0
  • ros-kinetic-cob-msgs: 0.6.7-0
  • ros-kinetic-cob-object-detection-msgs: 0.6.10-0
  • ros-kinetic-cob-object-detection-visualizer: 0.6.10-0
  • ros-kinetic-cob-obstacle-distance: 0.7.0-0
  • ros-kinetic-cob-omni-drive-controller: 0.7.0-0
  • ros-kinetic-cob-perception-common: 0.6.10-0
  • ros-kinetic-cob-perception-msgs: 0.6.10-0
  • ros-kinetic-cob-phidget-em-state: 0.6.10-0
  • ros-kinetic-cob-phidget-power-state: 0.6.10-0
  • ros-kinetic-cob-phidgets: 0.6.10-0
  • ros-kinetic-cob-reflector-referencing: 0.6.6-0
  • ros-kinetic-cob-relayboard: 0.6.10-0
  • ros-kinetic-cob-safety-controller: 0.6.6-0
  • ros-kinetic-cob-scan-unifier: 0.6.10-0
  • ros-kinetic-cob-sick-lms1xx: 0.6.10-0
  • ros-kinetic-cob-sick-s300: 0.6.10-0
  • ros-kinetic-cob-sound: 0.6.10-0
  • ros-kinetic-cob-srvs: 0.6.7-0
  • ros-kinetic-cob-substitute: 0.6.6-0
  • ros-kinetic-cob-supported-robots: 0.6.7-0
  • ros-kinetic-cob-trajectory-controller: 0.7.0-0
  • ros-kinetic-cob-twist-controller: 0.7.0-0
  • ros-kinetic-cob-undercarriage-ctrl: 0.6.10-0
  • ros-kinetic-cob-undercarriage-ctrl-node: 0.7.0-0
  • ros-kinetic-cob-utilities: 0.6.10-0
  • ros-kinetic-cob-vision-utils: 0.6.10-0
  • ros-kinetic-cob-voltage-control: 0.6.10-0
  • ros-kinetic-eband-local-planner: 0.3.1-0
  • ros-kinetic-follow-waypoints: 0.3.0-2
  • ros-kinetic-grid-map-costmap-2d: 1.5.2-0
  • ros-kinetic-grid-map-octomap: 1.5.2-0
  • ros-kinetic-image-overlay-scale-and-compass: 0.2.1-0
  • ros-kinetic-julius-ros: 2.1.4-0
  • ros-kinetic-libconcorde-tsp-solver: 0.6.11-0
  • ros-kinetic-libdlib: 0.6.11-0
  • ros-kinetic-libntcan: 0.6.11-0
  • ros-kinetic-libpcan: 0.6.11-0
  • ros-kinetic-libphidgets: 0.6.11-0
  • ros-kinetic-libqsopt: 0.6.11-0
  • ros-kinetic-opengm: 0.6.11-0
  • ros-kinetic-raw-description: 0.6.7-0
  • ros-kinetic-rostune: 1.0.5-1
  • ros-kinetic-safe-teleop-base: 0.0.2-0
  • ros-kinetic-safe-teleop-stage: 0.0.2-0
  • ros-kinetic-schunk-description: 0.6.9-0
  • ros-kinetic-schunk-libm5api: 0.6.9-0
  • ros-kinetic-schunk-modular-robotics: 0.6.9-0
  • ros-kinetic-schunk-powercube-chain: 0.6.9-0
  • ros-kinetic-schunk-sdh: 0.6.9-0
  • ros-kinetic-schunk-simulated-tactile-sensors: 0.6.9-0
  • ros-kinetic-soem: 1.3.0-0
  • ros-kinetic-urdf-geometry-parser: 0.0.2-0
  • ros-kinetic-urdf-sim-tutorial: 0.3.0-1

Updated Packages [78]:

  • ros-kinetic-aruco-detect: 0.7.2-0 -> 0.7.3-0
  • ros-kinetic-assimp-devel: 2.0.20-0 -> 2.1.4-0
  • ros-kinetic-bayesian-belief-networks: 2.0.20-0 -> 2.1.4-0
  • ros-kinetic-bin-pose-emulator: 0.1.2-0 -> 0.1.3-0
  • ros-kinetic-bin-pose-msgs: 0.1.2-0 -> 0.1.3-0
  • ros-kinetic-binpicking-utils: 0.1.2-0 -> 0.1.3-0
  • ros-kinetic-checkerboard-detector: 1.1.1-0 -> 1.1.3-0
  • ros-kinetic-default-cfg-fkie: 0.7.4-0 -> 0.7.5-0
  • ros-kinetic-diagnostic-aggregator: 1.9.0-0 -> 1.9.2-0
  • ros-kinetic-diagnostic-analysis: 1.9.0-0 -> 1.9.2-0
  • ros-kinetic-diagnostic-common-diagnostics: 1.9.0-0 -> 1.9.2-0
  • ros-kinetic-diagnostic-updater: 1.9.0-0 -> 1.9.2-0
  • ros-kinetic-diagnostics: 1.9.0-0 -> 1.9.2-0
  • ros-kinetic-downward: 2.0.20-0 -> 2.1.4-0
  • ros-kinetic-ff: 2.0.20-0 -> 2.1.4-0
  • ros-kinetic-ffha: 2.0.20-0 -> 2.1.4-0
  • ros-kinetic-fiducial-detect: 0.7.2-0 -> 0.7.3-0
  • ros-kinetic-fiducial-lib: 0.7.2-0 -> 0.7.3-0
  • ros-kinetic-fiducial-msgs: 0.7.2-0 -> 0.7.3-0
  • ros-kinetic-fiducial-pose: 0.7.2-0 -> 0.7.3-0
  • ros-kinetic-fiducial-slam: 0.7.2-0 -> 0.7.3-0
  • ros-kinetic-fiducials: 0.7.2-0 -> 0.7.3-0
  • ros-kinetic-grid-map: 1.4.2-0 -> 1.5.2-0
  • ros-kinetic-grid-map-core: 1.4.2-0 -> 1.5.2-0
  • ros-kinetic-grid-map-cv: 1.4.2-0 -> 1.5.2-0
  • ros-kinetic-grid-map-demos: 1.4.2-0 -> 1.5.2-0
  • ros-kinetic-grid-map-filters: 1.4.2-0 -> 1.5.2-0
  • ros-kinetic-grid-map-loader: 1.4.2-0 -> 1.5.2-0
  • ros-kinetic-grid-map-msgs: 1.4.2-0 -> 1.5.2-0
  • ros-kinetic-grid-map-pcl: 1.4.2-0 -> 1.5.2-0
  • ros-kinetic-grid-map-ros: 1.4.2-0 -> 1.5.2-0
  • ros-kinetic-grid-map-rviz-plugin: 1.4.2-0 -> 1.5.2-0
  • ros-kinetic-grid-map-visualization: 1.4.2-0 -> 1.5.2-0
  • ros-kinetic-imagesift: 1.1.1-0 -> 1.1.3-0
  • ros-kinetic-jsk-3rdparty: 2.0.20-0 -> 2.1.4-0
  • ros-kinetic-jsk-pcl-ros: 1.1.1-0 -> 1.1.3-0
  • ros-kinetic-jsk-pcl-ros-utils: 1.1.1-0 -> 1.1.3-0
  • ros-kinetic-jsk-perception: 1.1.1-0 -> 1.1.3-0
  • ros-kinetic-jsk-recognition: 1.1.1-0 -> 1.1.3-0
  • ros-kinetic-jsk-recognition-msgs: 1.1.1-0 -> 1.1.3-0
  • ros-kinetic-jsk-recognition-utils: 1.1.1-0 -> 1.1.3-0
  • ros-kinetic-julius: 2.0.20-0 -> 2.1.4-0
  • ros-kinetic-libcmt: 2.0.20-0 -> 2.1.4-0
  • ros-kinetic-libsiftfast: 2.0.20-0 -> 2.1.4-0
  • ros-kinetic-lpg-planner: 2.0.20-0 -> 2.1.4-0
  • ros-kinetic-magni-bringup: 0.1.0-0 -> 0.1.1-0
  • ros-kinetic-magni-demos: 0.1.0-0 -> 0.1.1-0
  • ros-kinetic-magni-description: 0.1.0-0 -> 0.1.1-0
  • ros-kinetic-magni-nav: 0.1.0-0 -> 0.1.1-0
  • ros-kinetic-magni-robot: 0.1.0-0 -> 0.1.1-0
  • ros-kinetic-magni-teleop: 0.1.0-0 -> 0.1.1-0
  • ros-kinetic-master-discovery-fkie: 0.7.4-0 -> 0.7.5-0
  • ros-kinetic-master-sync-fkie: 0.7.4-0 -> 0.7.5-0
  • ros-kinetic-mavlink: 2017.6.6-0 -> 2017.7.7-0
  • ros-kinetic-mini-maxwell: 2.0.20-0 -> 2.1.4-0
  • ros-kinetic-move-basic: 0.2.0-0 -> 0.2.1-0
  • ros-kinetic-multimaster-fkie: 0.7.4-0 -> 0.7.5-0
  • ros-kinetic-multimaster-msgs-fkie: 0.7.4-0 -> 0.7.5-0
  • ros-kinetic-multiwii: 2.0.0-0 -> 2.0.1-0
  • ros-kinetic-nlopt: 2.0.20-0 -> 2.1.4-0
  • ros-kinetic-node-manager-fkie: 0.7.4-0 -> 0.7.5-0
  • ros-kinetic-opencv-apps: 1.11.15-0 -> 1.12.0-0
  • ros-kinetic-opt-camera: 2.0.20-0 -> 2.1.4-0
  • ros-kinetic-pgm-learner: 2.0.20-0 -> 2.1.4-0
  • ros-kinetic-plotjuggler: 1.1.2-0 -> 1.1.3-0
  • ros-kinetic-resized-image-transport: 1.1.1-0 -> 1.1.3-0
  • ros-kinetic-rosdiagnostic: 1.9.0-0 -> 1.9.2-0
  • ros-kinetic-rosjava-core: 0.3.4-1 -> 0.3.5-0
  • ros-kinetic-roslisp: 1.9.20-0 -> 1.9.21-0
  • ros-kinetic-rospatlite: 2.0.20-0 -> 2.1.4-0
  • ros-kinetic-rosping: 2.0.20-0 -> 2.1.4-0
  • ros-kinetic-rqt-tf-tree: 0.5.7-0 -> 0.5.8-0
  • ros-kinetic-self-test: 1.9.0-0 -> 1.9.2-0
  • ros-kinetic-slic: 2.0.20-0 -> 2.1.4-0
  • ros-kinetic-test-diagnostic-aggregator: 1.9.0-0 -> 1.9.2-0
  • ros-kinetic-thormang3-tools: 0.1.0-0 -> 0.1.2-0
  • ros-kinetic-urdf-tutorial: 0.2.5-0 -> 0.3.0-1
  • ros-kinetic-voice-text: 2.0.20-0 -> 2.1.4-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
  • Alexander Bubeck
  • Alexander Tiderko
  • Austin Hendrix
  • Benjamin Maidel
  • Brice Rebsamen
  • Charles DuHadway (maintained by Benjamin Pitzer)
  • Christian Rauch
  • Damon Kohler
  • Daniel Snider
  • David V. Lu!!
  • Davide Faconti
  • Felix Messmer
  • Florian Weisshardt
  • Frantisek Durovsky
  • Georg Bartels
  • George Stavrinos
  • Guillaume Autran
  • Hitoshi Kamada
  • Jan Fischer
  • Jim Vaughan
  • Joshua Hampp
  • Kei Okada
  • Mathias Luedtke
  • Mathias Lüdtke
  • Matthias Gruhler
  • Matthias Luedtke
  • Nadia Hammoudeh Garcia
  • Noda Shintaro
  • Piyush Khandelwal
  • Pyo
  • Péter Fankhauser
  • Richard Bormann
  • Rohan Agrawal
  • Ruben Smits
  • Ryohei Ueda
  • Takuya Nakaoka
  • Vincent Rousseau
  • Vladimir Ermakov
  • Yohei Kakiuchi
  • Youhei Kakiuchi
  • Yuki Furuta
  • Yuto Inagaki
  • durovsky

Posts: 1

Participants: 1

Read full topic

by @tfoote Tully Foote on July 26, 2017 12:19 AM

New Packages for Indigo 2017-07-25

@tfoote wrote:

We’re happy to announce another set of new packages for Indigo. We have 20 new packages as well as over 200 updates available.

Full details are below. Thanks to all the contributors and maintainers who have made this possible.

Updates to indigo

Added Packages [20]:

  • ros-indigo-cob-helper-tools: 0.6.6-0
  • ros-indigo-cob-map-accessibility-analysis: 0.6.5-0
  • ros-indigo-cob-supported-robots: 0.6.7-0
  • ros-indigo-generic-throttle: 0.6.6-0
  • ros-indigo-grid-map-costmap-2d: 1.5.2-0
  • ros-indigo-grid-map-octomap: 1.5.2-0
  • ros-indigo-jsk-pr2-desktop: 1.1.0-1
  • ros-indigo-julius-ros: 2.1.4-0
  • ros-indigo-libconcorde-tsp-solver: 0.6.11-0
  • ros-indigo-libqsopt: 0.6.11-0
  • ros-indigo-moveit-goal-builder: 0.1.0-0
  • ros-indigo-opengm: 0.6.11-0
  • ros-indigo-parameter-pa: 1.0.0-0
  • ros-indigo-rostune: 1.0.5-1
  • ros-indigo-safe-teleop-base: 0.0.2-0
  • ros-indigo-safe-teleop-pr2: 0.0.2-0
  • ros-indigo-safe-teleop-stage: 0.0.2-0
  • ros-indigo-service-tools: 0.6.6-0
  • ros-indigo-spin-hokuyo: 1.0.0-0
  • ros-indigo-urdf-sim-tutorial: 0.3.0-0

Updated Packages [214]:

  • ros-indigo-assimp-devel: 2.0.20-0 -> 2.1.4-0
  • ros-indigo-baxtereus: 1.0.6-2 -> 1.1.0-1
  • ros-indigo-bayesian-belief-networks: 2.0.20-0 -> 2.1.4-0
  • ros-indigo-can-msgs: 0.6.7-0 -> 0.6.8-0
  • ros-indigo-canopen-402: 0.6.7-0 -> 0.6.8-0
  • ros-indigo-canopen-chain-node: 0.6.7-0 -> 0.6.8-0
  • ros-indigo-canopen-master: 0.6.7-0 -> 0.6.8-0
  • ros-indigo-canopen-motor-node: 0.6.7-0 -> 0.6.8-0
  • ros-indigo-checkerboard-detector: 1.1.2-0 -> 1.2.2-0
  • ros-indigo-cob-3d-mapping-msgs: 0.6.8-0 -> 0.6.10-0
  • ros-indigo-cob-android: 0.1.2-0 -> 0.1.3-0
  • ros-indigo-cob-android-msgs: 0.1.2-0 -> 0.1.3-0
  • ros-indigo-cob-android-resource-server: 0.1.2-0 -> 0.1.3-0
  • ros-indigo-cob-android-script-server: 0.1.2-0 -> 0.1.3-0
  • ros-indigo-cob-android-settings: 0.1.2-0 -> 0.1.3-0
  • ros-indigo-cob-base-drive-chain: 0.6.8-0 -> 0.6.10-0
  • ros-indigo-cob-base-velocity-smoother: 0.6.14-0 -> 0.6.15-0
  • ros-indigo-cob-bms-driver: 0.6.8-0 -> 0.6.10-0
  • ros-indigo-cob-calibration-data: 0.6.6-0 -> 0.6.7-0
  • ros-indigo-cob-cam3d-throttle: 0.6.8-0 -> 0.6.10-0
  • ros-indigo-cob-camera-sensors: 0.6.8-0 -> 0.6.10-0
  • ros-indigo-cob-canopen-motor: 0.6.8-0 -> 0.6.10-0
  • ros-indigo-cob-cartesian-controller: 0.6.14-0 -> 0.6.15-0
  • ros-indigo-cob-collision-velocity-filter: 0.6.14-0 -> 0.6.15-0
  • ros-indigo-cob-command-gui: 0.6.5-0 -> 0.6.6-0
  • ros-indigo-cob-command-tools: 0.6.5-0 -> 0.6.6-0
  • ros-indigo-cob-common: 0.6.6-0 -> 0.6.7-0
  • ros-indigo-cob-control: 0.6.14-0 -> 0.6.15-0
  • ros-indigo-cob-control-mode-adapter: 0.6.14-0 -> 0.6.15-0
  • ros-indigo-cob-control-msgs: 0.6.14-0 -> 0.6.15-0
  • ros-indigo-cob-dashboard: 0.6.5-0 -> 0.6.6-0
  • ros-indigo-cob-default-env-config: 0.6.4-0 -> 0.6.5-0
  • ros-indigo-cob-description: 0.6.6-0 -> 0.6.7-0
  • ros-indigo-cob-docker-control: 0.6.5-0 -> 0.6.6-0
  • ros-indigo-cob-driver: 0.6.8-0 -> 0.6.10-0
  • ros-indigo-cob-elmo-homing: 0.6.8-0 -> 0.6.10-0
  • ros-indigo-cob-environments: 0.6.4-0 -> 0.6.5-0
  • ros-indigo-cob-extern: 0.6.10-0 -> 0.6.11-0
  • ros-indigo-cob-footprint-observer: 0.6.14-0 -> 0.6.15-0
  • ros-indigo-cob-frame-tracker: 0.6.14-0 -> 0.6.15-0
  • ros-indigo-cob-gazebo-plugins: 0.6.4-0 -> 0.6.6-0
  • ros-indigo-cob-gazebo-ros-control: 0.6.4-0 -> 0.6.6-0
  • ros-indigo-cob-generic-can: 0.6.8-0 -> 0.6.10-0
  • ros-indigo-cob-hand: 0.6.1-0 -> 0.6.2-0
  • ros-indigo-cob-hand-bridge: 0.6.1-0 -> 0.6.2-0
  • ros-indigo-cob-head-axis: 0.6.8-0 -> 0.6.10-0
  • ros-indigo-cob-image-flip: 0.6.8-0 -> 0.6.10-0
  • ros-indigo-cob-interactive-teleop: 0.6.5-0 -> 0.6.6-0
  • ros-indigo-cob-light: 0.6.8-0 -> 0.6.10-0
  • ros-indigo-cob-linear-nav: 0.6.4-0 -> 0.6.5-0
  • ros-indigo-cob-mapping-slam: 0.6.4-0 -> 0.6.5-0
  • ros-indigo-cob-mimic: 0.6.8-0 -> 0.6.10-0
  • ros-indigo-cob-model-identifier: 0.6.14-0 -> 0.6.15-0
  • ros-indigo-cob-monitoring: 0.6.5-0 -> 0.6.6-0
  • ros-indigo-cob-msgs: 0.6.6-0 -> 0.6.7-0
  • ros-indigo-cob-navigation: 0.6.4-0 -> 0.6.5-0
  • ros-indigo-cob-navigation-config: 0.6.4-0 -> 0.6.5-0
  • ros-indigo-cob-navigation-global: 0.6.4-0 -> 0.6.5-0
  • ros-indigo-cob-navigation-local: 0.6.4-0 -> 0.6.5-0
  • ros-indigo-cob-navigation-slam: 0.6.4-0 -> 0.6.5-0
  • ros-indigo-cob-object-detection-msgs: 0.6.8-0 -> 0.6.10-0
  • ros-indigo-cob-object-detection-visualizer: 0.6.8-0 -> 0.6.10-0
  • ros-indigo-cob-obstacle-distance: 0.6.14-0 -> 0.6.15-0
  • ros-indigo-cob-omni-drive-controller: 0.6.14-0 -> 0.6.15-0
  • ros-indigo-cob-perception-common: 0.6.8-0 -> 0.6.10-0
  • ros-indigo-cob-perception-msgs: 0.6.8-0 -> 0.6.10-0
  • ros-indigo-cob-phidget-em-state: 0.6.8-0 -> 0.6.10-0
  • ros-indigo-cob-phidget-power-state: 0.6.8-0 -> 0.6.10-0
  • ros-indigo-cob-phidgets: 0.6.8-0 -> 0.6.10-0
  • ros-indigo-cob-reflector-referencing: 0.6.5-0 -> 0.6.6-0
  • ros-indigo-cob-relayboard: 0.6.8-0 -> 0.6.10-0
  • ros-indigo-cob-safety-controller: 0.6.5-0 -> 0.6.6-0
  • ros-indigo-cob-scan-unifier: 0.6.8-0 -> 0.6.10-0
  • ros-indigo-cob-script-server: 0.6.5-0 -> 0.6.6-0
  • ros-indigo-cob-sick-lms1xx: 0.6.8-0 -> 0.6.10-0
  • ros-indigo-cob-sick-s300: 0.6.8-0 -> 0.6.10-0
  • ros-indigo-cob-sound: 0.6.8-0 -> 0.6.10-0
  • ros-indigo-cob-srvs: 0.6.6-0 -> 0.6.7-0
  • ros-indigo-cob-substitute: 0.6.5-0 -> 0.6.6-0
  • ros-indigo-cob-teleop: 0.6.5-0 -> 0.6.6-0
  • ros-indigo-cob-trajectory-controller: 0.6.14-0 -> 0.6.15-0
  • ros-indigo-cob-twist-controller: 0.6.14-0 -> 0.6.15-0
  • ros-indigo-cob-undercarriage-ctrl: 0.6.8-0 -> 0.6.10-0
  • ros-indigo-cob-undercarriage-ctrl-node: 0.6.14-0 -> 0.6.15-0
  • ros-indigo-cob-utilities: 0.6.8-0 -> 0.6.10-0
  • ros-indigo-cob-vision-utils: 0.6.8-0 -> 0.6.10-0
  • ros-indigo-cob-voltage-control: 0.6.8-0 -> 0.6.10-0
  • ros-indigo-collada-urdf-jsk-patch: 2.0.20-0 -> 2.1.4-0
  • ros-indigo-default-cfg-fkie: 0.7.4-0 -> 0.7.5-0
  • ros-indigo-diagnostic-aggregator: 1.9.0-0 -> 1.9.2-0
  • ros-indigo-diagnostic-analysis: 1.9.0-0 -> 1.9.2-0
  • ros-indigo-diagnostic-common-diagnostics: 1.9.0-0 -> 1.9.2-0
  • ros-indigo-diagnostic-updater: 1.9.0-0 -> 1.9.2-0
  • ros-indigo-diagnostics: 1.9.0-0 -> 1.9.2-0
  • ros-indigo-diff-drive-controller: 0.9.3-0 -> 0.9.4-0
  • ros-indigo-downward: 2.0.20-0 -> 2.1.4-0
  • ros-indigo-effort-controllers: 0.9.3-0 -> 0.9.4-0
  • ros-indigo-fetcheus: 1.0.6-2 -> 1.1.0-1
  • ros-indigo-ff: 2.0.20-0 -> 2.1.4-0
  • ros-indigo-ffha: 2.0.20-0 -> 2.1.4-0
  • ros-indigo-force-torque-sensor-controller: 0.9.3-0 -> 0.9.4-0
  • ros-indigo-forward-command-controller: 0.9.3-0 -> 0.9.4-0
  • ros-indigo-grid-map: 1.4.2-0 -> 1.5.2-0
  • ros-indigo-grid-map-core: 1.4.2-0 -> 1.5.2-0
  • ros-indigo-grid-map-cv: 1.4.2-0 -> 1.5.2-0
  • ros-indigo-grid-map-demos: 1.4.2-0 -> 1.5.2-0
  • ros-indigo-grid-map-filters: 1.4.2-0 -> 1.5.2-0
  • ros-indigo-grid-map-loader: 1.4.2-0 -> 1.5.2-0
  • ros-indigo-grid-map-msgs: 1.4.2-0 -> 1.5.2-0
  • ros-indigo-grid-map-pcl: 1.4.2-0 -> 1.5.2-0
  • ros-indigo-grid-map-ros: 1.4.2-0 -> 1.5.2-0
  • ros-indigo-grid-map-rviz-plugin: 1.4.2-0 -> 1.5.2-0
  • ros-indigo-grid-map-visualization: 1.4.2-0 -> 1.5.2-0
  • ros-indigo-gripper-action-controller: 0.9.3-0 -> 0.9.4-0
  • ros-indigo-imagesift: 1.1.2-0 -> 1.2.2-0
  • ros-indigo-imu-sensor-controller: 0.9.3-0 -> 0.9.4-0
  • ros-indigo-joint-state-controller: 0.9.3-0 -> 0.9.4-0
  • ros-indigo-joint-trajectory-controller: 0.9.3-0 -> 0.9.4-0
  • ros-indigo-jsk-2015-05-baxter-apc: 3.0.3-0 -> 4.0.0-0
  • ros-indigo-jsk-201504-miraikan: 1.0.6-2 -> 1.1.0-1
  • ros-indigo-jsk-2016-01-baxter-apc: 3.0.3-0 -> 4.0.0-0
  • ros-indigo-jsk-3rdparty: 2.0.20-0 -> 2.1.4-0
  • ros-indigo-jsk-apc2015-common: 3.0.3-0 -> 4.0.0-0
  • ros-indigo-jsk-apc2016-common: 3.0.3-0 -> 4.0.0-0
  • ros-indigo-jsk-arc2017-common: 3.0.3-0 -> 4.0.0-0
  • ros-indigo-jsk-baxter-desktop: 1.0.6-2 -> 1.1.0-1
  • ros-indigo-jsk-baxter-startup: 1.0.6-2 -> 1.1.0-1
  • ros-indigo-jsk-baxter-web: 1.0.6-2 -> 1.1.0-1
  • ros-indigo-jsk-common-msgs: 4.2.0-0 -> 4.3.0-0
  • ros-indigo-jsk-fetch-startup: 1.0.6-2 -> 1.1.0-1
  • ros-indigo-jsk-footstep-msgs: 4.2.0-0 -> 4.3.0-0
  • ros-indigo-jsk-gui-msgs: 4.2.0-0 -> 4.3.0-0
  • ros-indigo-jsk-hark-msgs: 4.2.0-0 -> 4.3.0-0
  • ros-indigo-jsk-interactive: 2.1.0-0 -> 2.1.2-0
  • ros-indigo-jsk-interactive-marker: 2.1.0-0 -> 2.1.2-0
  • ros-indigo-jsk-interactive-test: 2.1.0-0 -> 2.1.2-0
  • ros-indigo-jsk-nao-startup: 1.0.6-2 -> 1.1.0-1
  • ros-indigo-jsk-pcl-ros: 1.1.2-0 -> 1.2.2-0
  • ros-indigo-jsk-pcl-ros-utils: 1.1.2-0 -> 1.2.2-0
  • ros-indigo-jsk-pepper-startup: 1.0.6-2 -> 1.1.0-1
  • ros-indigo-jsk-perception: 1.1.2-0 -> 1.2.2-0
  • ros-indigo-jsk-pr2-calibration: 1.0.6-2 -> 1.1.0-1
  • ros-indigo-jsk-pr2-startup: 1.0.6-2 -> 1.1.0-1
  • ros-indigo-jsk-pr2eus: 0.3.11-0 -> 0.3.13-0
  • ros-indigo-jsk-recognition: 1.1.2-0 -> 1.2.2-0
  • ros-indigo-jsk-recognition-msgs: 1.1.2-0 -> 1.2.2-0
  • ros-indigo-jsk-recognition-utils: 1.1.2-0 -> 1.2.2-0
  • ros-indigo-jsk-robot: 1.0.6-2 -> 1.1.0-1
  • ros-indigo-jsk-robot-startup: 1.0.6-2 -> 1.1.0-1
  • ros-indigo-jsk-robot-utils: 1.0.6-2 -> 1.1.0-1
  • ros-indigo-jsk-rqt-plugins: 2.1.0-0 -> 2.1.2-0
  • ros-indigo-jsk-rviz-plugins: 2.1.0-0 -> 2.1.2-0
  • ros-indigo-jsk-visualization: 2.1.0-0 -> 2.1.2-0
  • ros-indigo-julius: 2.0.20-0 -> 2.1.4-0
  • ros-indigo-laser-filters-jsk-patch: 2.0.20-0 -> 2.1.4-0
  • ros-indigo-libcmt: 2.0.20-0 -> 2.1.4-0
  • ros-indigo-libdlib: 0.6.10-0 -> 0.6.11-0
  • ros-indigo-libntcan: 0.6.10-0 -> 0.6.11-0
  • ros-indigo-libpcan: 0.6.10-0 -> 0.6.11-0
  • ros-indigo-libphidgets: 0.6.10-0 -> 0.6.11-0
  • ros-indigo-libsiftfast: 2.0.20-0 -> 2.1.4-0
  • ros-indigo-lpg-planner: 2.0.20-0 -> 2.1.4-0
  • ros-indigo-master-discovery-fkie: 0.7.4-0 -> 0.7.5-0
  • ros-indigo-master-sync-fkie: 0.7.4-0 -> 0.7.5-0
  • ros-indigo-mini-maxwell: 2.0.20-0 -> 2.1.4-0
  • ros-indigo-multimaster-fkie: 0.7.4-0 -> 0.7.5-0
  • ros-indigo-multimaster-msgs-fkie: 0.7.4-0 -> 0.7.5-0
  • ros-indigo-naoeus: 1.0.6-2 -> 1.1.0-1
  • ros-indigo-naoqieus: 1.0.6-2 -> 1.1.0-1
  • ros-indigo-nlopt: 2.0.20-0 -> 2.1.4-0
  • ros-indigo-node-manager-fkie: 0.7.4-0 -> 0.7.5-0
  • ros-indigo-opencv-apps: 1.11.15-0 -> 1.12.0-0
  • ros-indigo-opt-camera: 2.0.20-0 -> 2.1.4-0
  • ros-indigo-parrot-arsdk: 3.11.0-0 -> 3.12.6-0
  • ros-indigo-peppereus: 1.0.6-2 -> 1.1.0-1
  • ros-indigo-pgm-learner: 2.0.20-0 -> 2.1.4-0
  • ros-indigo-plotjuggler: 1.1.2-0 -> 1.1.3-0
  • ros-indigo-posedetection-msgs: 4.2.0-0 -> 4.3.0-0
  • ros-indigo-position-controllers: 0.9.3-0 -> 0.9.4-0
  • ros-indigo-pr2-base-trajectory-action: 1.0.6-2 -> 1.1.0-1
  • ros-indigo-pr2eus: 0.3.11-0 -> 0.3.13-0
  • ros-indigo-pr2eus-moveit: 0.3.11-0 -> 0.3.13-0
  • ros-indigo-pr2eus-tutorials: 0.3.11-0 -> 0.3.13-0
  • ros-indigo-rail-manipulation-msgs: 0.0.9-0 -> 0.0.10-0
  • ros-indigo-raw-description: 0.6.6-0 -> 0.6.7-0
  • ros-indigo-resized-image-transport: 1.1.2-0 -> 1.2.2-0
  • ros-indigo-ros-canopen: 0.6.7-0 -> 0.6.8-0
  • ros-indigo-ros-controllers: 0.9.3-0 -> 0.9.4-0
  • ros-indigo-rosauth: 0.1.7-0 -> 0.1.7-1
  • ros-indigo-rosdiagnostic: 1.9.0-0 -> 1.9.2-0
  • ros-indigo-roseus-remote: 1.0.6-2 -> 1.1.0-1
  • ros-indigo-roslisp: 1.9.20-0 -> 1.9.21-0
  • ros-indigo-rospatlite: 2.0.20-0 -> 2.1.4-0
  • ros-indigo-rosping: 2.0.20-0 -> 2.1.4-0
  • ros-indigo-rostwitter: 2.0.20-0 -> 2.1.4-0
  • ros-indigo-rqt-joint-trajectory-controller: 0.9.3-0 -> 0.9.4-0
  • ros-indigo-rqt-tf-tree: 0.5.7-0 -> 0.5.8-0
  • ros-indigo-schunk-description: 0.6.8-0 -> 0.6.9-0
  • ros-indigo-schunk-libm5api: 0.6.8-0 -> 0.6.9-0
  • ros-indigo-schunk-modular-robotics: 0.6.8-0 -> 0.6.9-0
  • ros-indigo-schunk-powercube-chain: 0.6.8-0 -> 0.6.9-0
  • ros-indigo-schunk-sdh: 0.6.8-0 -> 0.6.9-0
  • ros-indigo-schunk-simulated-tactile-sensors: 0.6.8-0 -> 0.6.9-0
  • ros-indigo-self-test: 1.9.0-0 -> 1.9.2-0
  • ros-indigo-slic: 2.0.20-0 -> 2.1.4-0
  • ros-indigo-socketcan-bridge: 0.6.7-0 -> 0.6.8-0
  • ros-indigo-socketcan-interface: 0.6.7-0 -> 0.6.8-0
  • ros-indigo-speech-recognition-msgs: 4.2.0-0 -> 4.3.0-0
  • ros-indigo-surface-perception: 0.1.1-0 -> 0.1.3-0
  • ros-indigo-test-diagnostic-aggregator: 1.9.0-0 -> 1.9.2-0
  • ros-indigo-transform-graph: 0.1.4-0 -> 0.2.1-0
  • ros-indigo-urdf-tutorial: 0.2.5-0 -> 0.3.0-0
  • ros-indigo-velocity-controllers: 0.9.3-0 -> 0.9.4-0
  • ros-indigo-voice-text: 2.0.20-0 -> 2.1.4-0

Removed Packages [2]:

  • ros-indigo-jsk-apc
  • ros-indigo-jsk-arc2017-baxter

Maintainers

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
  • Adolfo Rodriguez Tsouroukdissian
  • Alexander Bubeck
  • Alexander Tiderko
  • Austin Hendrix
  • Bence Magyar
  • Benjamin Maidel
  • Brice Rebsamen
  • Charles DuHadway (maintained by Benjamin Pitzer)
  • David Kent
  • David V. Lu!!
  • Davide Faconti
  • Felix Messmer
  • Florian Weisshardt
  • Georg Bartels
  • George Stavrinos
  • Guillaume Autran
  • Hasegawa Shun
  • Hitoshi Kamada
  • Jan Fischer
  • Joshua Hampp
  • Justin Huang
  • KazutoMurase
  • Kei Okada
  • Kentaro Wada
  • Mani Monajjemi
  • Mathias Luedtke
  • Mathias Lüdtke
  • Matthias Gruhler
  • Matthias Luedtke
  • Nadia Hammoudeh Garcia
  • Noda Shintaro
  • Peter Weissig
  • Péter Fankhauser
  • Richard Bormann
  • Russell Toris
  • Ryohei Ueda
  • Sachin Chitta
  • Sarah Bertussi
  • Shohei Fujii
  • Takuya Nakaoka
  • Yohei Kakiuchi
  • YoheiKakiuchi
  • Youhei Kakiuchi
  • Yuki Furuta
  • Yusuke Furuta
  • Yuto Inagaki
  • furuta
  • inagaki
  • k-okada

Posts: 1

Participants: 1

Read full topic

by @tfoote Tully Foote on July 26, 2017 12:16 AM

July 24, 2017
ROSCon 2017 early registration deadline: August 1st

The ROSCon registration rates increase next Tuesday, August 1st! Register now at: https://roscon2017.eventbrite.com/ to get the early registration discount.

We're anticipating another record year with more proposals, talks, and sponsors than ever before!

To save money, remember to book your hotel room soon as well. More information is available at: http://roscon.ros.org/2017/#location.

For more information about ROSCon including the program and information on the location please visit: https://roscon.ros.org/

We're happy to announce some great new sponsors for ROSCon: SICK, Apex.AI, NVIDIA, Voyage, and Ubuntu.

Thanks to our Platinum Sponsor: Intel. Thanks to our Gold Sponsors: Clearpath, Erle, Fetch, GaiTech, Locus, Rapyuta, and SICK. Thanks to our Video Archive Sponsor: Ubuntu

by Tully Foote on July 24, 2017 10:38 PM

ROSCon 2017 early registration deadline: August 1st

@tfoote wrote:

The ROSCon registration rates increase next Tuesday, August 1st! Register now at: https://roscon2017.eventbrite.com/ to get the early registration discount.

We’re anticipating another record year with more proposals, talks, and sponsors than ever before!

To save money, remember to book your hotel room soon as well. More information is available at: http://roscon.ros.org/2017/#location.

For more information about ROSCon including the program and information on the location please visit: http://roscon.ros.org/

We’re happy to announce some great new sponsors for ROSCon: SICK, Apex.AI, NVIDIA, Voyage, and Ubuntu.

– Your ROSCon Organizing Committee

Thanks to our Platinum Sponsor: Intel.
Thanks to our Gold Sponsors: Clearpath, Erle, Fetch, GaiTech, Locus, Rapyuta, and SICK.
Thanks to our Video Archive Sponsor: Ubuntu

Posts: 4

Participants: 1

Read full topic

by @tfoote Tully Foote on July 24, 2017 10:35 PM

ROSCon 2017 Diversity Scholarships

The ROSCon 2017 organizing committee aims for ROSCon to represent the entire ROS community, which is diverse and global. In addition to promoting technology that is open source, we also strive to ensure that our communities themselves are as open and accessible as possible, since we recognize that diversity benefits the ROS ecosystem as a whole.

Whoever you are, whatever you do, and wherever you do it, if you're interested in ROS, then we want you to join us at ROSCon. To help reduce the financial barriers to conference attendance, the ROSCon organizing committee is offering a number of scholarships to members of traditionally underrepresented groups in the tech community. Thanks to the support of the program's sponsors, these scholarships each include a complimentary conference registration pass and three nights' accommodation shared with another recipient*. Limited travel support is available for participants whose travel to the conference would otherwise be infeasible. Please note that all other expenses (including any visa requirements) will be the responsibility of the participant.

*To maximize the impact of the scholarship funds, scholarship recipients will be asked to share a room with another recipient. Under special circumstances alternative arrangements can be accommodated.

Eligibility

We invite applications from members of groups that have been traditionally underrepresented in the tech community (including but not limited to: women, LGBTQ+, people of color, people with disabilities, and people from ethnic minorities in their country of residence), who may not otherwise be able to attend ROSCon. Previous ROSCon Diversity Scholarship recipients are not eligible to re-apply.

Sponsors

The ROSCon 2017 Diversity Program has been made possible with support from the following sponsors:

Fetch.png

nvidia.png

openrobotics-logo-stacked.png

rapyuta.png

voyage.png

If your organization is interested in getting involved in the Diversity Program, please get in contact.

How to apply

To apply, fill out this form by June 25, describing how you are involved with ROS and the robotics community and what you hope to get out of attending ROSCon. Scholarships will be awarded based on a combination of need and impact. Every applicant will be notified of the outcome of their application.

For more information about ROSCon 2017, including the program, code of conduct, and childcare options, please see http://roscon.ros.org/2017

by Tully Foote on July 24, 2017 09:58 PM

Driver for Advanced Navigation INS devices released

@scott.obrien wrote:

I have created an example driver for the range of Advance Navigation INS devices eg Spatial, Spatial Dual, Spatial FOG, Spatial FOG Dual, Motus, and Orientus.

The repository can be found here: https://github.com/an-scott/Advanced_Navigation_driver.

If anyone has any questions, do not hesitate to contact me.

Scott

Application Support Engineer
www.advancednavigation.com.au

Posts: 1

Participants: 1

Read full topic

by @scott.obrien Scott O&#39;Brien on July 24, 2017 05:05 AM

July 23, 2017
Free ROS Live classes: Robocademy.com [Lentin Joseph]

@lentinjoseph wrote:

Hello Everyone

My name is Lentin Joseph. I am the founder of Qbotics Labs, a robotics software service provider company working on ROS. I have authored 3 books in ROS which are ROS Robotics Projects, Mastering ROS for Robotics Programming & Learning Robotics using Python.

Our company is planning to launch our new project called Robocademy, which is an exclusive learning platform for Robotics and associated technologies.

We are starting ROS live classes from next week, which is exclusive to people who are planning to work in ROS.

Interested candidates can share their CV link or Linkedin profile with us and after filtering, selected candidates will get a chance to learn ROS for free.

Here is the website of robocademy

Robocademy

Interested candidates can enroll to the course from the website itself. The details of course schedule will inform to the selected candidates.

Regards
Lentin Joseph
Author | Entrepreneur

Posts: 5

Participants: 2

Read full topic

by @lentinjoseph Lentin Joseph on July 23, 2017 06:49 AM

July 20, 2017
[Meetup] An intro to ROS programming for robots in Cambridge

@YUHONG_LIN wrote:

[Meetup] An introduction to ROS programming for robots in Cambridge

Join here: http://meetu.ps/3bX2MP

Date: Tuesday, August 8, 2017
Time: 6:30 PM
Venue: Caffe Nero (11 Market St, Cambridge CB2 3PA, Cambridge)
Free Event

Dear Roboticists,

If you like robots and you want to learn how to program them, that is your Meetup!

ROS is becoming the standard in robot programming. So you must master ROS if you want to work in robotics in the close future.

Come to this MeetUp and find a very fast way to learn ROS!

You will need to bring your laptop since this is going to be a hands up tutorial. But don’t worry, you can bring any type of laptop. No installations required for the tutorial. All the programming will be done online.

Please come 10-15 minutes earlier to connect on the Internet and grab a nice Coffee!

================
If you cannot attend to this event you have the option to attend the course online: http://www.robotigniteacademy.com/ or watch the free video tutorials in YouTube.

================
For more info send an email to the host (Angelos) at a.plastropoulos@gmail.com

Posts: 1

Participants: 1

Read full topic

by @YUHONG_LIN on July 20, 2017 08:22 AM

July 19, 2017
Jade EOL Announcement

@wjwwood wrote:

Now that ROS Lunar is out, it’s time for us to start shutting down our services for ROS Jade.

We’re already past the EOL date for Jade, but we’ve been busy with the Lunar release and other projects so we wanted to wait for things to settle down before starting to shutdown Jade.

What this means for everyone:

  • There will only be one more chance to release packages into Jade
    • This will happen in about two weeks unless we run into regressions or someone asks for more time
  • After we shutdown the Jade part of the build farm there will be no additional updates to Jade

Some other details of interest:

  • We will only do more Jade syncs after that iff critical bugs are discovered before we shutdown the Jade part of the build farm
    • There will be a short period between the last sync and shutting down the build farm where we can test Jade and make sure there are no blocking issues
  • After the last sync we will also:
    • stop taking new releases in ros/rosdistro for jade
    • stop building new binary packages for Jade
    • stop running devel jobs, pr jobs, and doc jobs for Jade
  • The existing Jade binaries and documentation will continue to be available

If you’re still using Jade you need to consider moving to one of the other ROS releases:

  • ROS Lunar (latest)
  • ROS Kinetic (latest LTS)
  • ROS Indigo (older LTS, older than Jade)

After this post, I’ll be making announcements and updates in the “Release and Package Maintenance” category here on discourse:

So be sure to check that out if you’re interested in updates on this.

Posts: 1

Participants: 1

Read full topic

by @wjwwood William Woodall on July 19, 2017 02:11 AM


Powered by the awesome: Planet