[meetings] Barcelona ROS Intensive Course Week

Dear roboticists,

I would like to introduce the intensive courses on ROS learning that we are preparing, to provide along the month of July. These courses are available for students and teachers of any level and are provided for FREE.


ABOUT THE EVENT
================

Learn in a single week the basics of ROS in the beautiful city of Barcelona. Classes will be provided in the morning from 9:30 to 13:30 in two blocks of 1h50min. Afternoons are free time. Classes are reduced to 5 students.

THIS COURSE IS FREE. Students must pay themselves travel to Barcelona, as well as meals and stay during the course. ONLY 4 WEEKS AVAILABLE

There are four different weeks(courses) available. You can only attend to one of them:
* 4th to 8th of July
* 11th to 15th of July
* 18th to 22nd of July
* 25th to 29th of July

SCHEDULE
=========

* 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

REQUIREMENTS FOR ATTENDANCE
==============================

* Basic knowledge of Python programming
* A laptop (can have any operating system)

IMPORTANT LINK
==============

* You can enroll the course here: http://env.theconstructsim.com/ROS-Courses

CONTACT US
===========

* You can contact us with questions and doubts here: info-0lXLkTl3c71MJ1yGCERxX0EOCMrvLtNR@public.gmane.org
<div><div dir="ltr">
<div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">
<span>Dear roboticists,</span><div><span><br></span></div>
<div><span>I would like to introduce the intensive courses on ROS learning that we are preparing, to provide along the month of July. These courses are available for students and teachers of any level and are provided for FREE.</span></div>
<div><span><br></span></div>
<br><span>ABOUT THE EVENT</span><br><span>================</span><br><br><span>Learn in a single week the basics of ROS in the beautiful city of Barcelona. Classes will be provided in the morning from 9:30 to 13:30 in two blocks of 1h50min. Afternoons are free time. Classes are reduced to 5 students.</span><br><br><span>THIS COURSE IS FREE. Students must pay themselves travel to Barcelona, as well as meals and stay during the course. ONLY 4 WEEKS AVAILABLE</span><br><br><span>There are four different weeks(courses) available. You can only attend to one of them:</span><div>* 4th to 8th of July<br>* 11th to 15th of July<br>* 18th to 22nd of July<br>* 25th to 29th of July</div>
<div><br></div>
<div>SCHEDULE</div>
<div>=========</div>
<br><span>* Monday: ROS BASICS: basic structure of ROS programs and its concepts</span><br><span>* Tuesday: ROS TOPICS: how to create topics and how to access them</span><br><span>* Wednesday: ROS SERVICES: how to create services and how to use them</span><br><span>* Thursday: ROS ACTIONS: how to create action servers and use them</span><br><span>* Friday: ROS DEBUG: ROS tools that allow to find errors and debug</span><div>
<br><div>REQUIREMENTS FOR ATTENDANCE<div>==============================</div>
<div>
<br>* Basic knowledge of Python programming<br>* A laptop (can have any operating system)<div>
<div><br></div>
<div>IMPORTANT LINK</div>
<div>==============</div>
<div><br></div>
<div>* You can enroll the course here:&nbsp;<a href="http://env.theconstructsim.com/ROS-Courses" target="_blank">http://env.theconstructsim.com/ROS-Courses</a>
</div>
<div><br></div>
<div>CONTACT US</div>
<div>===========</div>
<div><br></div>
<div>* You can contact us with questions and doubts here:&nbsp;<a href="mailto:info@..." target="_blank">info@...</a>
</div>
</div>
</div>
</div>
</div>
<div class=""></div>
</div></div>
</div></div>
Tully Foote via ros-users | 23 Jun 22:49 2016

New packages for Indigo

HI Everyone, 

We have another batch of packages available for Indigo. We continue to add many new packages as well as having a lot of maintenance releases. 

Thanks to everyone who contributed. The list of packages and maintainers are below. 

Your ROS Release Team


Updates to indigo
Added Packages [58]:
 * ros-indigo-alfred-bot: 0.1.121-0
 * ros-indigo-alfred-sr-linux: 0.1.20-0
 * ros-indigo-arm-components-name-manager: 1.0.0-0
 * ros-indigo-astra-camera: 0.1.5-0
 * ros-indigo-astra-launch: 0.1.0-0
 * ros-indigo-axcli: 0.1.0-0
 * ros-indigo-baselib-binding: 1.0.0-0
 * ros-indigo-bwi-joystick-teleop: 0.3.8-0
 * ros-indigo-catkin-pip: 0.1.8-0
 * ros-indigo-convenience-math-functions: 1.0.0-0
 * ros-indigo-convenience-ros-functions: 1.0.0-0
 * ros-indigo-gazebo-grasp-plugin: 1.0.1-0
 * ros-indigo-gazebo-state-plugins: 1.0.1-0
 * ros-indigo-gazebo-test-tools: 1.0.1-0
 * ros-indigo-gazebo-world-plugin-loader: 1.0.1-0
 * ros-indigo-jsk-fetch-startup: 1.0.6-2
 * ros-indigo-jsk-pr2-startup: 1.0.6-2
 * ros-indigo-jsk-robot: 1.0.6-2
 * ros-indigo-logger-binding: 1.0.0-0
 * ros-indigo-media-msgs: 0.1.58-0
 * ros-indigo-micros-mars-task-alloc: 0.0.5-1
 * ros-indigo-moveit-controller-multidof: 1.0.0-0
 * ros-indigo-moveit-object-handling: 1.0.0-0
 * ros-indigo-moveit-planning-helper: 1.0.0-0
 * ros-indigo-network-wakeonlan: 0.1.65-0
 * ros-indigo-object-msgs: 1.0.0-0
 * ros-indigo-object-msgs-tools: 1.0.0-0
 * ros-indigo-parrot-arsdk: 3.9.1-3
 * ros-indigo-path-navigation-msgs: 1.0.0-0
 * ros-indigo-pyros-config: 0.1.2-0
 * ros-indigo-pyros-utils: 0.1.2-0
 * ros-indigo-rosjava-dynamic-reconfigure: 0.2.4-0
 * ros-indigo-smarthome-comm-msgs: 0.1.19-0
 * ros-indigo-smarthome-comm-msgs-java: 0.1.15-0
 * ros-indigo-smarthome-common-driver: 0.1.61-0
 * ros-indigo-smarthome-heater-msgs: 0.1.21-0
 * ros-indigo-smarthome-heater-msgs-java: 0.1.21-0
 * ros-indigo-smarthome-light-msgs: 0.1.2-0
 * ros-indigo-smarthome-media-kodi-driver: 0.1.57-0
 * ros-indigo-smarthome-media-model: 0.1.60-0
 * ros-indigo-smarthome-media-msgs: 0.1.59-0
 * ros-indigo-smarthome-media-msgs-java: 0.1.82-0
 * ros-indigo-smarthome-media-onkyo-driver: 0.1.64-0
 * ros-indigo-smarthome-media-samsungtv-driver: 0.1.58-0
 * ros-indigo-smarthome-msgs: 0.1.3-0
 * ros-indigo-smarthome-msgs-java: 0.1.1-0
 * ros-indigo-smarthome-network-wakeonlan: 0.1.66-0
 * ros-indigo-smarthome-network-zeroconf: 0.1.66-0
 * ros-indigo-swri-console: 0.1.0-0
 * ros-indigo-trac-ik: 1.4.3-0
 * ros-indigo-trac-ik-examples: 1.4.3-0
 * ros-indigo-trac-ik-kinematics-plugin: 1.4.3-0
 * ros-indigo-trac-ik-lib: 1.4.3-0
 * ros-indigo-urdf-tools: 1.0.0-0
 * ros-indigo-urdf-transform: 1.0.0-0
 * ros-indigo-urdf-traverser: 1.0.0-0
 * ros-indigo-urdf-viewer: 1.0.0-0
 * ros-indigo-urdf2inventor: 1.0.0-0

Updated Packages [228]:
 * ros-indigo-amcl: 1.12.8-0 -> 1.12.11-0
 * ros-indigo-arm-navigation-msgs: 0.0.2-0 -> 0.0.3-0
 * ros-indigo-base-local-planner: 1.12.8-0 -> 1.12.11-0
 * ros-indigo-baxtereus: 1.0.5-1 -> 1.0.6-2
 * ros-indigo-bwi-common: 0.3.7-0 -> 0.3.8-0
 * ros-indigo-bwi-gazebo-entities: 0.3.7-0 -> 0.3.8-0
 * ros-indigo-bwi-interruptable-action-server: 0.3.7-0 -> 0.3.8-0
 * ros-indigo-bwi-kr-execution: 0.3.7-0 -> 0.3.8-0
 * ros-indigo-bwi-logging: 0.3.7-0 -> 0.3.8-0
 * ros-indigo-bwi-mapper: 0.3.7-0 -> 0.3.8-0
 * ros-indigo-bwi-msgs: 0.3.7-0 -> 0.3.8-0
 * ros-indigo-bwi-planning-common: 0.3.7-0 -> 0.3.8-0
 * ros-indigo-bwi-rqt-plugins: 0.3.7-0 -> 0.3.8-0
 * ros-indigo-bwi-scavenger: 0.3.7-0 -> 0.3.8-0
 * ros-indigo-bwi-tasks: 0.3.7-0 -> 0.3.8-0
 * ros-indigo-bwi-tools: 0.3.7-0 -> 0.3.8-0
 * ros-indigo-camera-pose-calibration: 0.1.2-0 -> 0.1.5-0
 * ros-indigo-carrot-planner: 1.12.8-0 -> 1.12.11-0
 * ros-indigo-catkin-pure-python: 0.0.8-0 -> 0.1.2-0
 * ros-indigo-clear-costmap-recovery: 1.12.8-0 -> 1.12.11-0
 * ros-indigo-collada-parser: 1.11.10-0 -> 1.11.11-0
 * ros-indigo-collada-robots: 0.0.2-0 -> 0.0.3-0
 * ros-indigo-collada-urdf: 1.11.10-0 -> 1.11.11-0
 * ros-indigo-costmap-2d: 1.12.8-0 -> 1.12.11-0
 * ros-indigo-diagnostic-aggregator: 1.8.9-0 -> 1.8.10-0
 * ros-indigo-diagnostic-analysis: 1.8.9-0 -> 1.8.10-0
 * ros-indigo-diagnostic-common-diagnostics: 1.8.9-0 -> 1.8.10-0
 * ros-indigo-diagnostic-updater: 1.8.9-0 -> 1.8.10-0
 * ros-indigo-diagnostics: 1.8.9-0 -> 1.8.10-0
 * ros-indigo-dji-sdk: 0.1.7-0 -> 0.1.9-0
 * ros-indigo-dji-sdk-demo: 0.1.7-0 -> 0.1.9-0
 * ros-indigo-dji-sdk-dji2mav: 0.1.7-0 -> 0.1.9-0
 * ros-indigo-dji-sdk-lib: 0.1.7-0 -> 0.1.9-0
 * ros-indigo-dji-sdk-web-groundstation: 0.1.7-0 -> 0.1.9-0
 * ros-indigo-dwa-local-planner: 1.12.8-0 -> 1.12.11-0
 * ros-indigo-dynamic-tf-publisher: 2.0.14-0 -> 2.0.16-1
 * ros-indigo-dynpick-driver: 0.0.9-0 -> 0.0.11-0
 * ros-indigo-ecl-command-line: 0.61.9-0 -> 0.61.14-0
 * ros-indigo-ecl-concepts: 0.61.9-0 -> 0.61.14-0
 * ros-indigo-ecl-config: 0.61.4-0 -> 0.61.6-0
 * ros-indigo-ecl-console: 0.61.4-0 -> 0.61.6-0
 * ros-indigo-ecl-containers: 0.61.9-0 -> 0.61.14-0
 * ros-indigo-ecl-converters: 0.61.9-0 -> 0.61.14-0
 * ros-indigo-ecl-converters-lite: 0.61.4-0 -> 0.61.6-0
 * ros-indigo-ecl-core: 0.61.9-0 -> 0.61.14-0
 * ros-indigo-ecl-core-apps: 0.61.9-0 -> 0.61.14-0
 * ros-indigo-ecl-devices: 0.61.9-0 -> 0.61.14-0
 * ros-indigo-ecl-eigen: 0.61.9-0 -> 0.61.14-0
 * ros-indigo-ecl-errors: 0.61.4-0 -> 0.61.6-0
 * ros-indigo-ecl-exceptions: 0.61.9-0 -> 0.61.14-0
 * ros-indigo-ecl-filesystem: 0.61.9-0 -> 0.61.14-0
 * ros-indigo-ecl-formatters: 0.61.9-0 -> 0.61.14-0
 * ros-indigo-ecl-geometry: 0.61.9-0 -> 0.61.14-0
 * ros-indigo-ecl-io: 0.61.4-0 -> 0.61.6-0
 * ros-indigo-ecl-ipc: 0.61.9-0 -> 0.61.14-0
 * ros-indigo-ecl-linear-algebra: 0.61.9-0 -> 0.61.14-0
 * ros-indigo-ecl-lite: 0.61.4-0 -> 0.61.6-0
 * ros-indigo-ecl-math: 0.61.9-0 -> 0.61.14-0
 * ros-indigo-ecl-mpl: 0.61.9-0 -> 0.61.14-0
 * ros-indigo-ecl-sigslots: 0.61.9-0 -> 0.61.14-0
 * ros-indigo-ecl-sigslots-lite: 0.61.4-0 -> 0.61.6-0
 * ros-indigo-ecl-statistics: 0.61.9-0 -> 0.61.14-0
 * ros-indigo-ecl-streams: 0.61.9-0 -> 0.61.14-0
 * ros-indigo-ecl-threads: 0.61.9-0 -> 0.61.14-0
 * ros-indigo-ecl-time: 0.61.9-0 -> 0.61.14-0
 * ros-indigo-ecl-time-lite: 0.61.4-0 -> 0.61.6-0
 * ros-indigo-ecl-type-traits: 0.61.9-0 -> 0.61.14-0
 * ros-indigo-ecl-utilities: 0.61.9-0 -> 0.61.14-0
 * ros-indigo-fake-localization: 1.12.8-0 -> 1.12.11-0
 * ros-indigo-fanuc: 0.4.0-1 -> 0.4.1-0
 * ros-indigo-fanuc-driver: 0.4.0-1 -> 0.4.1-0
 * ros-indigo-fanuc-lrmate200ic-moveit-config: 0.4.0-1 -> 0.4.1-0
 * ros-indigo-fanuc-lrmate200ic-moveit-plugins: 0.4.0-1 -> 0.4.1-0
 * ros-indigo-fanuc-lrmate200ic-support: 0.4.0-1 -> 0.4.1-0
 * ros-indigo-fanuc-lrmate200ic5h-moveit-config: 0.4.0-1 -> 0.4.1-0
 * ros-indigo-fanuc-lrmate200ic5l-moveit-config: 0.4.0-1 -> 0.4.1-0
 * ros-indigo-fanuc-m10ia-moveit-config: 0.4.0-1 -> 0.4.1-0
 * ros-indigo-fanuc-m10ia-moveit-plugins: 0.4.0-1 -> 0.4.1-0
 * ros-indigo-fanuc-m10ia-support: 0.4.0-1 -> 0.4.1-0
 * ros-indigo-fanuc-m16ib-moveit-plugins: 0.4.0-1 -> 0.4.1-0
 * ros-indigo-fanuc-m16ib-support: 0.4.0-1 -> 0.4.1-0
 * ros-indigo-fanuc-m16ib20-moveit-config: 0.4.0-1 -> 0.4.1-0
 * ros-indigo-fanuc-m20ia-moveit-config: 0.4.0-1 -> 0.4.1-0
 * ros-indigo-fanuc-m20ia-moveit-plugins: 0.4.0-1 -> 0.4.1-0
 * ros-indigo-fanuc-m20ia-support: 0.4.0-1 -> 0.4.1-0
 * ros-indigo-fanuc-m20ia10l-moveit-config: 0.4.0-1 -> 0.4.1-0
 * ros-indigo-fanuc-m430ia-moveit-plugins: 0.4.0-1 -> 0.4.1-0
 * ros-indigo-fanuc-m430ia-support: 0.4.0-1 -> 0.4.1-0
 * ros-indigo-fanuc-m430ia2f-moveit-config: 0.4.0-1 -> 0.4.1-0
 * ros-indigo-fanuc-m430ia2p-moveit-config: 0.4.0-1 -> 0.4.1-0
 * ros-indigo-fanuc-resources: 0.4.0-1 -> 0.4.1-0
 * ros-indigo-fetch-calibration: 0.7.5-0 -> 0.7.7-0
 * ros-indigo-fetch-depth-layer: 0.7.5-0 -> 0.7.7-0
 * ros-indigo-fetch-description: 0.7.5-0 -> 0.7.7-0
 * ros-indigo-fetch-maps: 0.7.5-0 -> 0.7.7-0
 * ros-indigo-fetch-moveit-config: 0.7.5-0 -> 0.7.7-0
 * ros-indigo-fetch-navigation: 0.7.5-0 -> 0.7.7-0
 * ros-indigo-fetch-teleop: 0.7.5-0 -> 0.7.7-0
 * ros-indigo-fetcheus: 1.0.5-1 -> 1.0.6-2
 * ros-indigo-global-planner: 1.12.8-0 -> 1.12.11-0
 * ros-indigo-grasp-planning-graspit: 0.1.5-0 -> 1.0.0-0
 * ros-indigo-grasp-planning-graspit-msgs: 0.1.5-0 -> 1.0.0-0
 * ros-indigo-grasp-planning-graspit-ros: 0.1.5-0 -> 1.0.0-0
 * ros-indigo-graspit-tools: 0.1.5-0 -> 1.0.0-0
 * ros-indigo-hironx-calibration: 1.1.14-0 -> 1.1.15-0
 * ros-indigo-hironx-moveit-config: 1.1.14-0 -> 1.1.15-0
 * ros-indigo-hironx-ros-bridge: 1.1.14-0 -> 1.1.15-0
 * ros-indigo-image-view2: 2.0.14-0 -> 2.0.16-1
 * ros-indigo-jackal-control: 0.5.2-1 -> 0.5.3-0
 * ros-indigo-jackal-description: 0.5.2-1 -> 0.5.3-0
 * ros-indigo-jackal-desktop: 0.3.1-0 -> 0.3.2-0
 * ros-indigo-jackal-msgs: 0.5.2-1 -> 0.5.3-0
 * ros-indigo-jackal-navigation: 0.5.2-1 -> 0.5.3-0
 * ros-indigo-jackal-tutorials: 0.5.2-1 -> 0.5.3-0
 * ros-indigo-jackal-viz: 0.3.1-0 -> 0.3.2-0
 * ros-indigo-jaco-graspit-sample: 0.1.5-0 -> 1.0.0-0
 * ros-indigo-joint-state-publisher: 1.11.10-0 -> 1.11.11-0
 * ros-indigo-jsk-2015-05-baxter-apc: 0.2.4-0 -> 0.8.0-2
 * ros-indigo-jsk-201504-miraikan: 1.0.5-1 -> 1.0.6-2
 * ros-indigo-jsk-apc2015-common: 0.2.4-0 -> 0.8.0-2
 * ros-indigo-jsk-apc2016-common: 0.2.4-0 -> 0.8.0-2
 * ros-indigo-jsk-baxter-desktop: 1.0.5-1 -> 1.0.6-2
 * ros-indigo-jsk-baxter-startup: 1.0.5-1 -> 1.0.6-2
 * ros-indigo-jsk-baxter-web: 1.0.5-1 -> 1.0.6-2
 * ros-indigo-jsk-common: 2.0.14-0 -> 2.0.16-1
 * ros-indigo-jsk-common-msgs: 2.0.1-0 -> 3.0.0-0
 * ros-indigo-jsk-data: 2.0.14-0 -> 2.0.16-1
 * ros-indigo-jsk-footstep-msgs: 2.0.1-0 -> 3.0.0-0
 * ros-indigo-jsk-gui-msgs: 2.0.1-0 -> 3.0.0-0
 * ros-indigo-jsk-hark-msgs: 2.0.1-0 -> 3.0.0-0
 * ros-indigo-jsk-nao-startup: 1.0.5-1 -> 1.0.6-2
 * ros-indigo-jsk-network-tools: 2.0.14-0 -> 2.0.16-1
 * ros-indigo-jsk-pepper-startup: 1.0.5-1 -> 1.0.6-2
 * ros-indigo-jsk-planning: 0.1.6-0 -> 0.1.7-0
 * ros-indigo-jsk-pr2-calibration: 1.0.5-1 -> 1.0.6-2
 * ros-indigo-jsk-pr2eus: 0.3.2-0 -> 0.3.4-0
 * ros-indigo-jsk-robot-startup: 1.0.5-1 -> 1.0.6-2
 * ros-indigo-jsk-robot-utils: 1.0.5-1 -> 1.0.6-2
 * ros-indigo-jsk-roseus: 1.5.1-0 -> 1.5.3-0
 * ros-indigo-jsk-tilt-laser: 2.0.14-0 -> 2.0.16-1
 * ros-indigo-jsk-tools: 2.0.14-0 -> 2.0.16-1
 * ros-indigo-jsk-topic-tools: 2.0.14-0 -> 2.0.16-1
 * ros-indigo-kdl-parser: 1.11.10-0 -> 1.11.11-0
 * ros-indigo-kdl-parser-py: 1.11.10-0 -> 1.11.11-0
 * ros-indigo-kobuki-core: 0.6.3-0 -> 0.6.4-0
 * ros-indigo-kobuki-dock-drive: 0.6.3-0 -> 0.6.4-0
 * ros-indigo-kobuki-driver: 0.6.3-0 -> 0.6.4-0
 * ros-indigo-kobuki-ftdi: 0.6.3-0 -> 0.6.4-0
 * ros-indigo-leap-motion: 0.0.9-0 -> 0.0.10-0
 * ros-indigo-map-server: 1.12.8-0 -> 1.12.11-0
 * ros-indigo-message-multiplexing: 0.2.3-0 -> 0.2.4-0
 * ros-indigo-micros-swarm-framework: 0.0.6-2 -> 0.0.8-0
 * ros-indigo-mm-core-msgs: 0.2.3-0 -> 0.2.4-0
 * ros-indigo-mm-eigen-msgs: 0.2.3-0 -> 0.2.4-0
 * ros-indigo-mm-messages: 0.2.3-0 -> 0.2.4-0
 * ros-indigo-mm-mux-demux: 0.2.3-0 -> 0.2.4-0
 * ros-indigo-mm-radio: 0.2.3-0 -> 0.2.4-0
 * ros-indigo-move-base: 1.12.8-0 -> 1.12.11-0
 * ros-indigo-move-base-msgs: 1.12.8-0 -> 1.12.11-0
 * ros-indigo-move-slow-and-clear: 1.12.8-0 -> 1.12.11-0
 * ros-indigo-moveit-core: 0.7.1-0 -> 0.7.2-0
 * ros-indigo-moveit-msgs: 0.7.1-0 -> 0.7.2-0
 * ros-indigo-moveit-ros: 0.7.1-0 -> 0.7.2-0
 * ros-indigo-moveit-ros-benchmarks: 0.7.1-0 -> 0.7.2-0
 * ros-indigo-moveit-ros-benchmarks-gui: 0.7.1-0 -> 0.7.2-0
 * ros-indigo-moveit-ros-manipulation: 0.7.1-0 -> 0.7.2-0
 * ros-indigo-moveit-ros-move-group: 0.7.1-0 -> 0.7.2-0
 * ros-indigo-moveit-ros-perception: 0.7.1-0 -> 0.7.2-0
 * ros-indigo-moveit-ros-planning: 0.7.1-0 -> 0.7.2-0
 * ros-indigo-moveit-ros-planning-interface: 0.7.1-0 -> 0.7.2-0
 * ros-indigo-moveit-ros-robot-interaction: 0.7.1-0 -> 0.7.2-0
 * ros-indigo-moveit-ros-visualization: 0.7.1-0 -> 0.7.2-0
 * ros-indigo-moveit-ros-warehouse: 0.7.1-0 -> 0.7.2-0
 * ros-indigo-multi-map-server: 2.0.14-0 -> 2.0.16-1
 * ros-indigo-naoeus: 1.0.5-1 -> 1.0.6-2
 * ros-indigo-naoqieus: 1.0.5-1 -> 1.0.6-2
 * ros-indigo-nav-core: 1.12.8-0 -> 1.12.11-0
 * ros-indigo-navfn: 1.12.8-0 -> 1.12.11-0
 * ros-indigo-navigation: 1.12.8-0 -> 1.12.11-0
 * ros-indigo-octomap-msgs: 0.3.2-0 -> 0.3.3-0
 * ros-indigo-ompl: 1.0.0003094-0 -> 1.0.3094-0
 * ros-indigo-opencv-apps: 1.11.12-0 -> 1.11.13-0
 * ros-indigo-openni2-camera: 0.2.6-0 -> 0.2.7-0
 * ros-indigo-openrave: 0.0.2-0 -> 0.0.3-0
 * ros-indigo-openrave-planning: 0.0.2-0 -> 0.0.3-0
 * ros-indigo-pddl-msgs: 0.1.6-0 -> 0.1.7-0
 * ros-indigo-pddl-planner: 0.1.6-0 -> 0.1.7-0
 * ros-indigo-pddl-planner-viewer: 0.1.6-0 -> 0.1.7-0
 * ros-indigo-peppereus: 1.0.5-1 -> 1.0.6-2
 * ros-indigo-posedetection-msgs: 2.0.1-0 -> 3.0.0-0
 * ros-indigo-pr2-base-trajectory-action: 1.0.5-1 -> 1.0.6-2
 * ros-indigo-pr2eus: 0.3.2-0 -> 0.3.4-0
 * ros-indigo-pr2eus-moveit: 0.3.2-0 -> 0.3.4-0
 * ros-indigo-pr2eus-tutorials: 0.3.2-0 -> 0.3.4-0
 * ros-indigo-pyros-test: 0.0.3-0 -> 0.0.4-0
 * ros-indigo-qglv-extras: 0.1.6-0 -> 0.1.7-0
 * ros-indigo-qglv-gallery: 0.1.6-0 -> 0.1.7-0
 * ros-indigo-qglv-opencv: 0.1.6-0 -> 0.1.7-0
 * ros-indigo-qglv-opengl: 0.1.6-0 -> 0.1.7-0
 * ros-indigo-qglv-pcl: 0.1.6-0 -> 0.1.7-0
 * ros-indigo-qglv-toolkit: 0.1.6-0 -> 0.1.7-0
 * ros-indigo-qwt-dependency: 1.0.0-0 -> 1.0.1-0
 * ros-indigo-robot-model: 1.11.10-0 -> 1.11.11-0
 * ros-indigo-robot-pose-ekf: 1.12.8-0 -> 1.12.11-0
 * ros-indigo-roseus: 1.5.1-0 -> 1.5.3-0
 * ros-indigo-roseus-mongo: 1.5.1-0 -> 1.5.3-0
 * ros-indigo-roseus-remote: 1.0.5-1 -> 1.0.6-2
 * ros-indigo-roseus-smach: 1.5.1-0 -> 1.5.3-0
 * ros-indigo-roseus-tutorials: 1.5.1-0 -> 1.5.3-0
 * ros-indigo-rotate-recovery: 1.12.8-0 -> 1.12.11-0
 * ros-indigo-rplidar-ros: 1.5.2-0 -> 1.5.4-0
 * ros-indigo-rtabmap: 0.11.5-0 -> 0.11.7-0
 * ros-indigo-rtabmap-ros: 0.11.5-0 -> 0.11.7-1
 * ros-indigo-rtmros-hironx: 1.1.14-0 -> 1.1.15-0
 * ros-indigo-self-test: 1.8.9-0 -> 1.8.10-0
 * ros-indigo-sophus: 0.9.0-2 -> 0.9.1-0
 * ros-indigo-speech-recognition-msgs: 2.0.1-0 -> 3.0.0-0
 * ros-indigo-stop-base: 0.3.7-0 -> 0.3.8-0
 * ros-indigo-task-compiler: 0.1.6-0 -> 0.1.7-0
 * ros-indigo-teb-local-planner: 0.4.1-0 -> 0.4.2-0
 * ros-indigo-test-diagnostic-aggregator: 1.8.9-0 -> 1.8.10-0
 * ros-indigo-ueye-cam: 1.0.13-0 -> 1.0.14-1
 * ros-indigo-urdf: 1.11.10-0 -> 1.11.11-0
 * ros-indigo-urdf-parser-plugin: 1.11.10-0 -> 1.11.11-0
 * ros-indigo-urdf2graspit: 0.1.5-0 -> 1.0.0-0
 * ros-indigo-utexas-gdc: 0.3.7-0 -> 0.3.8-0
 * ros-indigo-virtual-force-publisher: 2.0.14-0 -> 2.0.16-1
 * ros-indigo-voxel-grid: 1.12.8-0 -> 1.12.11-0

Removed Packages [2]:
- ros-indigo-jsk-2016-01-baxter-apc
- ros-indigo-jsk-apc

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: 
 * Alex Gonzales
 * AlexV
 * Anqi Xu
 * Armin Hornung
 * Austin Hendrix
 * Brice Rebsamen
 * Chris Liu
 * Christoph Rösmann
 * Daniel Stonier
 * David V. Lu!!
 * Devon Ash
 * Dirk Thomas
 * Elliot Johnson
 * Erwan Le Huitouze
 * Florian Lier
 * G.A. vd. Hoorn (TU Delft Robotics Institute)
 * Ioan Sucan
 * Jack O'Quin
 * Jackie Kay
 * Jennifer Buehler
 * KazutoMurase
 * Kei Okada
 * Kentaro Wada
 * Mani Monajjemi
 * Mathieu Labbe
 * Michael Ferguson
 * Mickael Gaillard
 * Mickaël Gaillard
 * Mike Purvis
 * Minglong Li
 * Norman Li
 * Patrick Beeson
 * Paul Mathieu
 * Piyush Khandelwal
 * Ronald Ensing
 * Ryohei Ueda
 * Sachin Chitta
 * Shohei Fujii
 * Slamtec ROS Maintainer
 * TORK
 * Tim Liu
 * William Wu
 * Xuefeng Chang
 * YoheiKakiuchi
 * Younghun Ju
 * Yuki Furuta
 * Yuto Inagaki
 * inagaki
 * saito
<div><div dir="ltr">
<div>HI Everyone,&nbsp;</div>
<div><br></div>
<div>We have another batch of packages available for Indigo. We continue to add many new packages as well as having a lot of maintenance releases.&nbsp;</div>
<div><br></div>
<div>Thanks to everyone who contributed. The list of packages and maintainers are below.&nbsp;</div>
<div><br></div>
<div>Your ROS Release Team</div>
<div><br></div>
<div><br></div>
<div>
<div>Updates to indigo</div>
<div>Added Packages [58]:</div>
<div>&nbsp;* ros-indigo-alfred-bot: 0.1.121-0</div>
<div>&nbsp;* ros-indigo-alfred-sr-linux: 0.1.20-0</div>
<div>&nbsp;* ros-indigo-arm-components-name-manager: 1.0.0-0</div>
<div>&nbsp;* ros-indigo-astra-camera: 0.1.5-0</div>
<div>&nbsp;* ros-indigo-astra-launch: 0.1.0-0</div>
<div>&nbsp;* ros-indigo-axcli: 0.1.0-0</div>
<div>&nbsp;* ros-indigo-baselib-binding: 1.0.0-0</div>
<div>&nbsp;* ros-indigo-bwi-joystick-teleop: 0.3.8-0</div>
<div>&nbsp;* ros-indigo-catkin-pip: 0.1.8-0</div>
<div>&nbsp;* ros-indigo-convenience-math-functions: 1.0.0-0</div>
<div>&nbsp;* ros-indigo-convenience-ros-functions: 1.0.0-0</div>
<div>&nbsp;* ros-indigo-gazebo-grasp-plugin: 1.0.1-0</div>
<div>&nbsp;* ros-indigo-gazebo-state-plugins: 1.0.1-0</div>
<div>&nbsp;* ros-indigo-gazebo-test-tools: 1.0.1-0</div>
<div>&nbsp;* ros-indigo-gazebo-world-plugin-loader: 1.0.1-0</div>
<div>&nbsp;* ros-indigo-jsk-fetch-startup: 1.0.6-2</div>
<div>&nbsp;* ros-indigo-jsk-pr2-startup: 1.0.6-2</div>
<div>&nbsp;* ros-indigo-jsk-robot: 1.0.6-2</div>
<div>&nbsp;* ros-indigo-logger-binding: 1.0.0-0</div>
<div>&nbsp;* ros-indigo-media-msgs: 0.1.58-0</div>
<div>&nbsp;* ros-indigo-micros-mars-task-alloc: 0.0.5-1</div>
<div>&nbsp;* ros-indigo-moveit-controller-multidof: 1.0.0-0</div>
<div>&nbsp;* ros-indigo-moveit-object-handling: 1.0.0-0</div>
<div>&nbsp;* ros-indigo-moveit-planning-helper: 1.0.0-0</div>
<div>&nbsp;* ros-indigo-network-wakeonlan: 0.1.65-0</div>
<div>&nbsp;* ros-indigo-object-msgs: 1.0.0-0</div>
<div>&nbsp;* ros-indigo-object-msgs-tools: 1.0.0-0</div>
<div>&nbsp;* ros-indigo-parrot-arsdk: 3.9.1-3</div>
<div>&nbsp;* ros-indigo-path-navigation-msgs: 1.0.0-0</div>
<div>&nbsp;* ros-indigo-pyros-config: 0.1.2-0</div>
<div>&nbsp;* ros-indigo-pyros-utils: 0.1.2-0</div>
<div>&nbsp;* ros-indigo-rosjava-dynamic-reconfigure: 0.2.4-0</div>
<div>&nbsp;* ros-indigo-smarthome-comm-msgs: 0.1.19-0</div>
<div>&nbsp;* ros-indigo-smarthome-comm-msgs-java: 0.1.15-0</div>
<div>&nbsp;* ros-indigo-smarthome-common-driver: 0.1.61-0</div>
<div>&nbsp;* ros-indigo-smarthome-heater-msgs: 0.1.21-0</div>
<div>&nbsp;* ros-indigo-smarthome-heater-msgs-java: 0.1.21-0</div>
<div>&nbsp;* ros-indigo-smarthome-light-msgs: 0.1.2-0</div>
<div>&nbsp;* ros-indigo-smarthome-media-kodi-driver: 0.1.57-0</div>
<div>&nbsp;* ros-indigo-smarthome-media-model: 0.1.60-0</div>
<div>&nbsp;* ros-indigo-smarthome-media-msgs: 0.1.59-0</div>
<div>&nbsp;* ros-indigo-smarthome-media-msgs-java: 0.1.82-0</div>
<div>&nbsp;* ros-indigo-smarthome-media-onkyo-driver: 0.1.64-0</div>
<div>&nbsp;* ros-indigo-smarthome-media-samsungtv-driver: 0.1.58-0</div>
<div>&nbsp;* ros-indigo-smarthome-msgs: 0.1.3-0</div>
<div>&nbsp;* ros-indigo-smarthome-msgs-java: 0.1.1-0</div>
<div>&nbsp;* ros-indigo-smarthome-network-wakeonlan: 0.1.66-0</div>
<div>&nbsp;* ros-indigo-smarthome-network-zeroconf: 0.1.66-0</div>
<div>&nbsp;* ros-indigo-swri-console: 0.1.0-0</div>
<div>&nbsp;* ros-indigo-trac-ik: 1.4.3-0</div>
<div>&nbsp;* ros-indigo-trac-ik-examples: 1.4.3-0</div>
<div>&nbsp;* ros-indigo-trac-ik-kinematics-plugin: 1.4.3-0</div>
<div>&nbsp;* ros-indigo-trac-ik-lib: 1.4.3-0</div>
<div>&nbsp;* ros-indigo-urdf-tools: 1.0.0-0</div>
<div>&nbsp;* ros-indigo-urdf-transform: 1.0.0-0</div>
<div>&nbsp;* ros-indigo-urdf-traverser: 1.0.0-0</div>
<div>&nbsp;* ros-indigo-urdf-viewer: 1.0.0-0</div>
<div>&nbsp;* ros-indigo-urdf2inventor: 1.0.0-0</div>
<div><br></div>
<div>Updated Packages [228]:</div>
<div>&nbsp;* ros-indigo-amcl: 1.12.8-0 -&gt; 1.12.11-0</div>
<div>&nbsp;* ros-indigo-arm-navigation-msgs: 0.0.2-0 -&gt; 0.0.3-0</div>
<div>&nbsp;* ros-indigo-base-local-planner: 1.12.8-0 -&gt; 1.12.11-0</div>
<div>&nbsp;* ros-indigo-baxtereus: 1.0.5-1 -&gt; 1.0.6-2</div>
<div>&nbsp;* ros-indigo-bwi-common: 0.3.7-0 -&gt; 0.3.8-0</div>
<div>&nbsp;* ros-indigo-bwi-gazebo-entities: 0.3.7-0 -&gt; 0.3.8-0</div>
<div>&nbsp;* ros-indigo-bwi-interruptable-action-server: 0.3.7-0 -&gt; 0.3.8-0</div>
<div>&nbsp;* ros-indigo-bwi-kr-execution: 0.3.7-0 -&gt; 0.3.8-0</div>
<div>&nbsp;* ros-indigo-bwi-logging: 0.3.7-0 -&gt; 0.3.8-0</div>
<div>&nbsp;* ros-indigo-bwi-mapper: 0.3.7-0 -&gt; 0.3.8-0</div>
<div>&nbsp;* ros-indigo-bwi-msgs: 0.3.7-0 -&gt; 0.3.8-0</div>
<div>&nbsp;* ros-indigo-bwi-planning-common: 0.3.7-0 -&gt; 0.3.8-0</div>
<div>&nbsp;* ros-indigo-bwi-rqt-plugins: 0.3.7-0 -&gt; 0.3.8-0</div>
<div>&nbsp;* ros-indigo-bwi-scavenger: 0.3.7-0 -&gt; 0.3.8-0</div>
<div>&nbsp;* ros-indigo-bwi-tasks: 0.3.7-0 -&gt; 0.3.8-0</div>
<div>&nbsp;* ros-indigo-bwi-tools: 0.3.7-0 -&gt; 0.3.8-0</div>
<div>&nbsp;* ros-indigo-camera-pose-calibration: 0.1.2-0 -&gt; 0.1.5-0</div>
<div>&nbsp;* ros-indigo-carrot-planner: 1.12.8-0 -&gt; 1.12.11-0</div>
<div>&nbsp;* ros-indigo-catkin-pure-python: 0.0.8-0 -&gt; 0.1.2-0</div>
<div>&nbsp;* ros-indigo-clear-costmap-recovery: 1.12.8-0 -&gt; 1.12.11-0</div>
<div>&nbsp;* ros-indigo-collada-parser: 1.11.10-0 -&gt; 1.11.11-0</div>
<div>&nbsp;* ros-indigo-collada-robots: 0.0.2-0 -&gt; 0.0.3-0</div>
<div>&nbsp;* ros-indigo-collada-urdf: 1.11.10-0 -&gt; 1.11.11-0</div>
<div>&nbsp;* ros-indigo-costmap-2d: 1.12.8-0 -&gt; 1.12.11-0</div>
<div>&nbsp;* ros-indigo-diagnostic-aggregator: 1.8.9-0 -&gt; 1.8.10-0</div>
<div>&nbsp;* ros-indigo-diagnostic-analysis: 1.8.9-0 -&gt; 1.8.10-0</div>
<div>&nbsp;* ros-indigo-diagnostic-common-diagnostics: 1.8.9-0 -&gt; 1.8.10-0</div>
<div>&nbsp;* ros-indigo-diagnostic-updater: 1.8.9-0 -&gt; 1.8.10-0</div>
<div>&nbsp;* ros-indigo-diagnostics: 1.8.9-0 -&gt; 1.8.10-0</div>
<div>&nbsp;* ros-indigo-dji-sdk: 0.1.7-0 -&gt; 0.1.9-0</div>
<div>&nbsp;* ros-indigo-dji-sdk-demo: 0.1.7-0 -&gt; 0.1.9-0</div>
<div>&nbsp;* ros-indigo-dji-sdk-dji2mav: 0.1.7-0 -&gt; 0.1.9-0</div>
<div>&nbsp;* ros-indigo-dji-sdk-lib: 0.1.7-0 -&gt; 0.1.9-0</div>
<div>&nbsp;* ros-indigo-dji-sdk-web-groundstation: 0.1.7-0 -&gt; 0.1.9-0</div>
<div>&nbsp;* ros-indigo-dwa-local-planner: 1.12.8-0 -&gt; 1.12.11-0</div>
<div>&nbsp;* ros-indigo-dynamic-tf-publisher: 2.0.14-0 -&gt; 2.0.16-1</div>
<div>&nbsp;* ros-indigo-dynpick-driver: 0.0.9-0 -&gt; 0.0.11-0</div>
<div>&nbsp;* ros-indigo-ecl-command-line: 0.61.9-0 -&gt; 0.61.14-0</div>
<div>&nbsp;* ros-indigo-ecl-concepts: 0.61.9-0 -&gt; 0.61.14-0</div>
<div>&nbsp;* ros-indigo-ecl-config: 0.61.4-0 -&gt; 0.61.6-0</div>
<div>&nbsp;* ros-indigo-ecl-console: 0.61.4-0 -&gt; 0.61.6-0</div>
<div>&nbsp;* ros-indigo-ecl-containers: 0.61.9-0 -&gt; 0.61.14-0</div>
<div>&nbsp;* ros-indigo-ecl-converters: 0.61.9-0 -&gt; 0.61.14-0</div>
<div>&nbsp;* ros-indigo-ecl-converters-lite: 0.61.4-0 -&gt; 0.61.6-0</div>
<div>&nbsp;* ros-indigo-ecl-core: 0.61.9-0 -&gt; 0.61.14-0</div>
<div>&nbsp;* ros-indigo-ecl-core-apps: 0.61.9-0 -&gt; 0.61.14-0</div>
<div>&nbsp;* ros-indigo-ecl-devices: 0.61.9-0 -&gt; 0.61.14-0</div>
<div>&nbsp;* ros-indigo-ecl-eigen: 0.61.9-0 -&gt; 0.61.14-0</div>
<div>&nbsp;* ros-indigo-ecl-errors: 0.61.4-0 -&gt; 0.61.6-0</div>
<div>&nbsp;* ros-indigo-ecl-exceptions: 0.61.9-0 -&gt; 0.61.14-0</div>
<div>&nbsp;* ros-indigo-ecl-filesystem: 0.61.9-0 -&gt; 0.61.14-0</div>
<div>&nbsp;* ros-indigo-ecl-formatters: 0.61.9-0 -&gt; 0.61.14-0</div>
<div>&nbsp;* ros-indigo-ecl-geometry: 0.61.9-0 -&gt; 0.61.14-0</div>
<div>&nbsp;* ros-indigo-ecl-io: 0.61.4-0 -&gt; 0.61.6-0</div>
<div>&nbsp;* ros-indigo-ecl-ipc: 0.61.9-0 -&gt; 0.61.14-0</div>
<div>&nbsp;* ros-indigo-ecl-linear-algebra: 0.61.9-0 -&gt; 0.61.14-0</div>
<div>&nbsp;* ros-indigo-ecl-lite: 0.61.4-0 -&gt; 0.61.6-0</div>
<div>&nbsp;* ros-indigo-ecl-math: 0.61.9-0 -&gt; 0.61.14-0</div>
<div>&nbsp;* ros-indigo-ecl-mpl: 0.61.9-0 -&gt; 0.61.14-0</div>
<div>&nbsp;* ros-indigo-ecl-sigslots: 0.61.9-0 -&gt; 0.61.14-0</div>
<div>&nbsp;* ros-indigo-ecl-sigslots-lite: 0.61.4-0 -&gt; 0.61.6-0</div>
<div>&nbsp;* ros-indigo-ecl-statistics: 0.61.9-0 -&gt; 0.61.14-0</div>
<div>&nbsp;* ros-indigo-ecl-streams: 0.61.9-0 -&gt; 0.61.14-0</div>
<div>&nbsp;* ros-indigo-ecl-threads: 0.61.9-0 -&gt; 0.61.14-0</div>
<div>&nbsp;* ros-indigo-ecl-time: 0.61.9-0 -&gt; 0.61.14-0</div>
<div>&nbsp;* ros-indigo-ecl-time-lite: 0.61.4-0 -&gt; 0.61.6-0</div>
<div>&nbsp;* ros-indigo-ecl-type-traits: 0.61.9-0 -&gt; 0.61.14-0</div>
<div>&nbsp;* ros-indigo-ecl-utilities: 0.61.9-0 -&gt; 0.61.14-0</div>
<div>&nbsp;* ros-indigo-fake-localization: 1.12.8-0 -&gt; 1.12.11-0</div>
<div>&nbsp;* ros-indigo-fanuc: 0.4.0-1 -&gt; 0.4.1-0</div>
<div>&nbsp;* ros-indigo-fanuc-driver: 0.4.0-1 -&gt; 0.4.1-0</div>
<div>&nbsp;* ros-indigo-fanuc-lrmate200ic-moveit-config: 0.4.0-1 -&gt; 0.4.1-0</div>
<div>&nbsp;* ros-indigo-fanuc-lrmate200ic-moveit-plugins: 0.4.0-1 -&gt; 0.4.1-0</div>
<div>&nbsp;* ros-indigo-fanuc-lrmate200ic-support: 0.4.0-1 -&gt; 0.4.1-0</div>
<div>&nbsp;* ros-indigo-fanuc-lrmate200ic5h-moveit-config: 0.4.0-1 -&gt; 0.4.1-0</div>
<div>&nbsp;* ros-indigo-fanuc-lrmate200ic5l-moveit-config: 0.4.0-1 -&gt; 0.4.1-0</div>
<div>&nbsp;* ros-indigo-fanuc-m10ia-moveit-config: 0.4.0-1 -&gt; 0.4.1-0</div>
<div>&nbsp;* ros-indigo-fanuc-m10ia-moveit-plugins: 0.4.0-1 -&gt; 0.4.1-0</div>
<div>&nbsp;* ros-indigo-fanuc-m10ia-support: 0.4.0-1 -&gt; 0.4.1-0</div>
<div>&nbsp;* ros-indigo-fanuc-m16ib-moveit-plugins: 0.4.0-1 -&gt; 0.4.1-0</div>
<div>&nbsp;* ros-indigo-fanuc-m16ib-support: 0.4.0-1 -&gt; 0.4.1-0</div>
<div>&nbsp;* ros-indigo-fanuc-m16ib20-moveit-config: 0.4.0-1 -&gt; 0.4.1-0</div>
<div>&nbsp;* ros-indigo-fanuc-m20ia-moveit-config: 0.4.0-1 -&gt; 0.4.1-0</div>
<div>&nbsp;* ros-indigo-fanuc-m20ia-moveit-plugins: 0.4.0-1 -&gt; 0.4.1-0</div>
<div>&nbsp;* ros-indigo-fanuc-m20ia-support: 0.4.0-1 -&gt; 0.4.1-0</div>
<div>&nbsp;* ros-indigo-fanuc-m20ia10l-moveit-config: 0.4.0-1 -&gt; 0.4.1-0</div>
<div>&nbsp;* ros-indigo-fanuc-m430ia-moveit-plugins: 0.4.0-1 -&gt; 0.4.1-0</div>
<div>&nbsp;* ros-indigo-fanuc-m430ia-support: 0.4.0-1 -&gt; 0.4.1-0</div>
<div>&nbsp;* ros-indigo-fanuc-m430ia2f-moveit-config: 0.4.0-1 -&gt; 0.4.1-0</div>
<div>&nbsp;* ros-indigo-fanuc-m430ia2p-moveit-config: 0.4.0-1 -&gt; 0.4.1-0</div>
<div>&nbsp;* ros-indigo-fanuc-resources: 0.4.0-1 -&gt; 0.4.1-0</div>
<div>&nbsp;* ros-indigo-fetch-calibration: 0.7.5-0 -&gt; 0.7.7-0</div>
<div>&nbsp;* ros-indigo-fetch-depth-layer: 0.7.5-0 -&gt; 0.7.7-0</div>
<div>&nbsp;* ros-indigo-fetch-description: 0.7.5-0 -&gt; 0.7.7-0</div>
<div>&nbsp;* ros-indigo-fetch-maps: 0.7.5-0 -&gt; 0.7.7-0</div>
<div>&nbsp;* ros-indigo-fetch-moveit-config: 0.7.5-0 -&gt; 0.7.7-0</div>
<div>&nbsp;* ros-indigo-fetch-navigation: 0.7.5-0 -&gt; 0.7.7-0</div>
<div>&nbsp;* ros-indigo-fetch-teleop: 0.7.5-0 -&gt; 0.7.7-0</div>
<div>&nbsp;* ros-indigo-fetcheus: 1.0.5-1 -&gt; 1.0.6-2</div>
<div>&nbsp;* ros-indigo-global-planner: 1.12.8-0 -&gt; 1.12.11-0</div>
<div>&nbsp;* ros-indigo-grasp-planning-graspit: 0.1.5-0 -&gt; 1.0.0-0</div>
<div>&nbsp;* ros-indigo-grasp-planning-graspit-msgs: 0.1.5-0 -&gt; 1.0.0-0</div>
<div>&nbsp;* ros-indigo-grasp-planning-graspit-ros: 0.1.5-0 -&gt; 1.0.0-0</div>
<div>&nbsp;* ros-indigo-graspit-tools: 0.1.5-0 -&gt; 1.0.0-0</div>
<div>&nbsp;* ros-indigo-hironx-calibration: 1.1.14-0 -&gt; 1.1.15-0</div>
<div>&nbsp;* ros-indigo-hironx-moveit-config: 1.1.14-0 -&gt; 1.1.15-0</div>
<div>&nbsp;* ros-indigo-hironx-ros-bridge: 1.1.14-0 -&gt; 1.1.15-0</div>
<div>&nbsp;* ros-indigo-image-view2: 2.0.14-0 -&gt; 2.0.16-1</div>
<div>&nbsp;* ros-indigo-jackal-control: 0.5.2-1 -&gt; 0.5.3-0</div>
<div>&nbsp;* ros-indigo-jackal-description: 0.5.2-1 -&gt; 0.5.3-0</div>
<div>&nbsp;* ros-indigo-jackal-desktop: 0.3.1-0 -&gt; 0.3.2-0</div>
<div>&nbsp;* ros-indigo-jackal-msgs: 0.5.2-1 -&gt; 0.5.3-0</div>
<div>&nbsp;* ros-indigo-jackal-navigation: 0.5.2-1 -&gt; 0.5.3-0</div>
<div>&nbsp;* ros-indigo-jackal-tutorials: 0.5.2-1 -&gt; 0.5.3-0</div>
<div>&nbsp;* ros-indigo-jackal-viz: 0.3.1-0 -&gt; 0.3.2-0</div>
<div>&nbsp;* ros-indigo-jaco-graspit-sample: 0.1.5-0 -&gt; 1.0.0-0</div>
<div>&nbsp;* ros-indigo-joint-state-publisher: 1.11.10-0 -&gt; 1.11.11-0</div>
<div>&nbsp;* ros-indigo-jsk-2015-05-baxter-apc: 0.2.4-0 -&gt; 0.8.0-2</div>
<div>&nbsp;* ros-indigo-jsk-201504-miraikan: 1.0.5-1 -&gt; 1.0.6-2</div>
<div>&nbsp;* ros-indigo-jsk-apc2015-common: 0.2.4-0 -&gt; 0.8.0-2</div>
<div>&nbsp;* ros-indigo-jsk-apc2016-common: 0.2.4-0 -&gt; 0.8.0-2</div>
<div>&nbsp;* ros-indigo-jsk-baxter-desktop: 1.0.5-1 -&gt; 1.0.6-2</div>
<div>&nbsp;* ros-indigo-jsk-baxter-startup: 1.0.5-1 -&gt; 1.0.6-2</div>
<div>&nbsp;* ros-indigo-jsk-baxter-web: 1.0.5-1 -&gt; 1.0.6-2</div>
<div>&nbsp;* ros-indigo-jsk-common: 2.0.14-0 -&gt; 2.0.16-1</div>
<div>&nbsp;* ros-indigo-jsk-common-msgs: 2.0.1-0 -&gt; 3.0.0-0</div>
<div>&nbsp;* ros-indigo-jsk-data: 2.0.14-0 -&gt; 2.0.16-1</div>
<div>&nbsp;* ros-indigo-jsk-footstep-msgs: 2.0.1-0 -&gt; 3.0.0-0</div>
<div>&nbsp;* ros-indigo-jsk-gui-msgs: 2.0.1-0 -&gt; 3.0.0-0</div>
<div>&nbsp;* ros-indigo-jsk-hark-msgs: 2.0.1-0 -&gt; 3.0.0-0</div>
<div>&nbsp;* ros-indigo-jsk-nao-startup: 1.0.5-1 -&gt; 1.0.6-2</div>
<div>&nbsp;* ros-indigo-jsk-network-tools: 2.0.14-0 -&gt; 2.0.16-1</div>
<div>&nbsp;* ros-indigo-jsk-pepper-startup: 1.0.5-1 -&gt; 1.0.6-2</div>
<div>&nbsp;* ros-indigo-jsk-planning: 0.1.6-0 -&gt; 0.1.7-0</div>
<div>&nbsp;* ros-indigo-jsk-pr2-calibration: 1.0.5-1 -&gt; 1.0.6-2</div>
<div>&nbsp;* ros-indigo-jsk-pr2eus: 0.3.2-0 -&gt; 0.3.4-0</div>
<div>&nbsp;* ros-indigo-jsk-robot-startup: 1.0.5-1 -&gt; 1.0.6-2</div>
<div>&nbsp;* ros-indigo-jsk-robot-utils: 1.0.5-1 -&gt; 1.0.6-2</div>
<div>&nbsp;* ros-indigo-jsk-roseus: 1.5.1-0 -&gt; 1.5.3-0</div>
<div>&nbsp;* ros-indigo-jsk-tilt-laser: 2.0.14-0 -&gt; 2.0.16-1</div>
<div>&nbsp;* ros-indigo-jsk-tools: 2.0.14-0 -&gt; 2.0.16-1</div>
<div>&nbsp;* ros-indigo-jsk-topic-tools: 2.0.14-0 -&gt; 2.0.16-1</div>
<div>&nbsp;* ros-indigo-kdl-parser: 1.11.10-0 -&gt; 1.11.11-0</div>
<div>&nbsp;* ros-indigo-kdl-parser-py: 1.11.10-0 -&gt; 1.11.11-0</div>
<div>&nbsp;* ros-indigo-kobuki-core: 0.6.3-0 -&gt; 0.6.4-0</div>
<div>&nbsp;* ros-indigo-kobuki-dock-drive: 0.6.3-0 -&gt; 0.6.4-0</div>
<div>&nbsp;* ros-indigo-kobuki-driver: 0.6.3-0 -&gt; 0.6.4-0</div>
<div>&nbsp;* ros-indigo-kobuki-ftdi: 0.6.3-0 -&gt; 0.6.4-0</div>
<div>&nbsp;* ros-indigo-leap-motion: 0.0.9-0 -&gt; 0.0.10-0</div>
<div>&nbsp;* ros-indigo-map-server: 1.12.8-0 -&gt; 1.12.11-0</div>
<div>&nbsp;* ros-indigo-message-multiplexing: 0.2.3-0 -&gt; 0.2.4-0</div>
<div>&nbsp;* ros-indigo-micros-swarm-framework: 0.0.6-2 -&gt; 0.0.8-0</div>
<div>&nbsp;* ros-indigo-mm-core-msgs: 0.2.3-0 -&gt; 0.2.4-0</div>
<div>&nbsp;* ros-indigo-mm-eigen-msgs: 0.2.3-0 -&gt; 0.2.4-0</div>
<div>&nbsp;* ros-indigo-mm-messages: 0.2.3-0 -&gt; 0.2.4-0</div>
<div>&nbsp;* ros-indigo-mm-mux-demux: 0.2.3-0 -&gt; 0.2.4-0</div>
<div>&nbsp;* ros-indigo-mm-radio: 0.2.3-0 -&gt; 0.2.4-0</div>
<div>&nbsp;* ros-indigo-move-base: 1.12.8-0 -&gt; 1.12.11-0</div>
<div>&nbsp;* ros-indigo-move-base-msgs: 1.12.8-0 -&gt; 1.12.11-0</div>
<div>&nbsp;* ros-indigo-move-slow-and-clear: 1.12.8-0 -&gt; 1.12.11-0</div>
<div>&nbsp;* ros-indigo-moveit-core: 0.7.1-0 -&gt; 0.7.2-0</div>
<div>&nbsp;* ros-indigo-moveit-msgs: 0.7.1-0 -&gt; 0.7.2-0</div>
<div>&nbsp;* ros-indigo-moveit-ros: 0.7.1-0 -&gt; 0.7.2-0</div>
<div>&nbsp;* ros-indigo-moveit-ros-benchmarks: 0.7.1-0 -&gt; 0.7.2-0</div>
<div>&nbsp;* ros-indigo-moveit-ros-benchmarks-gui: 0.7.1-0 -&gt; 0.7.2-0</div>
<div>&nbsp;* ros-indigo-moveit-ros-manipulation: 0.7.1-0 -&gt; 0.7.2-0</div>
<div>&nbsp;* ros-indigo-moveit-ros-move-group: 0.7.1-0 -&gt; 0.7.2-0</div>
<div>&nbsp;* ros-indigo-moveit-ros-perception: 0.7.1-0 -&gt; 0.7.2-0</div>
<div>&nbsp;* ros-indigo-moveit-ros-planning: 0.7.1-0 -&gt; 0.7.2-0</div>
<div>&nbsp;* ros-indigo-moveit-ros-planning-interface: 0.7.1-0 -&gt; 0.7.2-0</div>
<div>&nbsp;* ros-indigo-moveit-ros-robot-interaction: 0.7.1-0 -&gt; 0.7.2-0</div>
<div>&nbsp;* ros-indigo-moveit-ros-visualization: 0.7.1-0 -&gt; 0.7.2-0</div>
<div>&nbsp;* ros-indigo-moveit-ros-warehouse: 0.7.1-0 -&gt; 0.7.2-0</div>
<div>&nbsp;* ros-indigo-multi-map-server: 2.0.14-0 -&gt; 2.0.16-1</div>
<div>&nbsp;* ros-indigo-naoeus: 1.0.5-1 -&gt; 1.0.6-2</div>
<div>&nbsp;* ros-indigo-naoqieus: 1.0.5-1 -&gt; 1.0.6-2</div>
<div>&nbsp;* ros-indigo-nav-core: 1.12.8-0 -&gt; 1.12.11-0</div>
<div>&nbsp;* ros-indigo-navfn: 1.12.8-0 -&gt; 1.12.11-0</div>
<div>&nbsp;* ros-indigo-navigation: 1.12.8-0 -&gt; 1.12.11-0</div>
<div>&nbsp;* ros-indigo-octomap-msgs: 0.3.2-0 -&gt; 0.3.3-0</div>
<div>&nbsp;* ros-indigo-ompl: 1.0.0003094-0 -&gt; 1.0.3094-0</div>
<div>&nbsp;* ros-indigo-opencv-apps: 1.11.12-0 -&gt; 1.11.13-0</div>
<div>&nbsp;* ros-indigo-openni2-camera: 0.2.6-0 -&gt; 0.2.7-0</div>
<div>&nbsp;* ros-indigo-openrave: 0.0.2-0 -&gt; 0.0.3-0</div>
<div>&nbsp;* ros-indigo-openrave-planning: 0.0.2-0 -&gt; 0.0.3-0</div>
<div>&nbsp;* ros-indigo-pddl-msgs: 0.1.6-0 -&gt; 0.1.7-0</div>
<div>&nbsp;* ros-indigo-pddl-planner: 0.1.6-0 -&gt; 0.1.7-0</div>
<div>&nbsp;* ros-indigo-pddl-planner-viewer: 0.1.6-0 -&gt; 0.1.7-0</div>
<div>&nbsp;* ros-indigo-peppereus: 1.0.5-1 -&gt; 1.0.6-2</div>
<div>&nbsp;* ros-indigo-posedetection-msgs: 2.0.1-0 -&gt; 3.0.0-0</div>
<div>&nbsp;* ros-indigo-pr2-base-trajectory-action: 1.0.5-1 -&gt; 1.0.6-2</div>
<div>&nbsp;* ros-indigo-pr2eus: 0.3.2-0 -&gt; 0.3.4-0</div>
<div>&nbsp;* ros-indigo-pr2eus-moveit: 0.3.2-0 -&gt; 0.3.4-0</div>
<div>&nbsp;* ros-indigo-pr2eus-tutorials: 0.3.2-0 -&gt; 0.3.4-0</div>
<div>&nbsp;* ros-indigo-pyros-test: 0.0.3-0 -&gt; 0.0.4-0</div>
<div>&nbsp;* ros-indigo-qglv-extras: 0.1.6-0 -&gt; 0.1.7-0</div>
<div>&nbsp;* ros-indigo-qglv-gallery: 0.1.6-0 -&gt; 0.1.7-0</div>
<div>&nbsp;* ros-indigo-qglv-opencv: 0.1.6-0 -&gt; 0.1.7-0</div>
<div>&nbsp;* ros-indigo-qglv-opengl: 0.1.6-0 -&gt; 0.1.7-0</div>
<div>&nbsp;* ros-indigo-qglv-pcl: 0.1.6-0 -&gt; 0.1.7-0</div>
<div>&nbsp;* ros-indigo-qglv-toolkit: 0.1.6-0 -&gt; 0.1.7-0</div>
<div>&nbsp;* ros-indigo-qwt-dependency: 1.0.0-0 -&gt; 1.0.1-0</div>
<div>&nbsp;* ros-indigo-robot-model: 1.11.10-0 -&gt; 1.11.11-0</div>
<div>&nbsp;* ros-indigo-robot-pose-ekf: 1.12.8-0 -&gt; 1.12.11-0</div>
<div>&nbsp;* ros-indigo-roseus: 1.5.1-0 -&gt; 1.5.3-0</div>
<div>&nbsp;* ros-indigo-roseus-mongo: 1.5.1-0 -&gt; 1.5.3-0</div>
<div>&nbsp;* ros-indigo-roseus-remote: 1.0.5-1 -&gt; 1.0.6-2</div>
<div>&nbsp;* ros-indigo-roseus-smach: 1.5.1-0 -&gt; 1.5.3-0</div>
<div>&nbsp;* ros-indigo-roseus-tutorials: 1.5.1-0 -&gt; 1.5.3-0</div>
<div>&nbsp;* ros-indigo-rotate-recovery: 1.12.8-0 -&gt; 1.12.11-0</div>
<div>&nbsp;* ros-indigo-rplidar-ros: 1.5.2-0 -&gt; 1.5.4-0</div>
<div>&nbsp;* ros-indigo-rtabmap: 0.11.5-0 -&gt; 0.11.7-0</div>
<div>&nbsp;* ros-indigo-rtabmap-ros: 0.11.5-0 -&gt; 0.11.7-1</div>
<div>&nbsp;* ros-indigo-rtmros-hironx: 1.1.14-0 -&gt; 1.1.15-0</div>
<div>&nbsp;* ros-indigo-self-test: 1.8.9-0 -&gt; 1.8.10-0</div>
<div>&nbsp;* ros-indigo-sophus: 0.9.0-2 -&gt; 0.9.1-0</div>
<div>&nbsp;* ros-indigo-speech-recognition-msgs: 2.0.1-0 -&gt; 3.0.0-0</div>
<div>&nbsp;* ros-indigo-stop-base: 0.3.7-0 -&gt; 0.3.8-0</div>
<div>&nbsp;* ros-indigo-task-compiler: 0.1.6-0 -&gt; 0.1.7-0</div>
<div>&nbsp;* ros-indigo-teb-local-planner: 0.4.1-0 -&gt; 0.4.2-0</div>
<div>&nbsp;* ros-indigo-test-diagnostic-aggregator: 1.8.9-0 -&gt; 1.8.10-0</div>
<div>&nbsp;* ros-indigo-ueye-cam: 1.0.13-0 -&gt; 1.0.14-1</div>
<div>&nbsp;* ros-indigo-urdf: 1.11.10-0 -&gt; 1.11.11-0</div>
<div>&nbsp;* ros-indigo-urdf-parser-plugin: 1.11.10-0 -&gt; 1.11.11-0</div>
<div>&nbsp;* ros-indigo-urdf2graspit: 0.1.5-0 -&gt; 1.0.0-0</div>
<div>&nbsp;* ros-indigo-utexas-gdc: 0.3.7-0 -&gt; 0.3.8-0</div>
<div>&nbsp;* ros-indigo-virtual-force-publisher: 2.0.14-0 -&gt; 2.0.16-1</div>
<div>&nbsp;* ros-indigo-voxel-grid: 1.12.8-0 -&gt; 1.12.11-0</div>
<div><br></div>
<div>Removed Packages [2]:</div>
<div>- ros-indigo-jsk-2016-01-baxter-apc</div>
<div>- ros-indigo-jsk-apc</div>
<div><br></div>
<div>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:&nbsp;</div>
<div>&nbsp;* Alex Gonzales</div>
<div>&nbsp;* AlexV</div>
<div>&nbsp;* Anqi Xu</div>
<div>&nbsp;* Armin Hornung</div>
<div>&nbsp;* Austin Hendrix</div>
<div>&nbsp;* Brice Rebsamen</div>
<div>&nbsp;* Chris Liu</div>
<div>&nbsp;* Christoph R&ouml;smann</div>
<div>&nbsp;* Daniel Stonier</div>
<div>&nbsp;* David V. Lu!!</div>
<div>&nbsp;* Devon Ash</div>
<div>&nbsp;* Dirk Thomas</div>
<div>&nbsp;* Elliot Johnson</div>
<div>&nbsp;* Erwan Le Huitouze</div>
<div>&nbsp;* Florian Lier</div>
<div>&nbsp;* G.A. vd. Hoorn (TU Delft Robotics Institute)</div>
<div>&nbsp;* Ioan Sucan</div>
<div>&nbsp;* Jack O'Quin</div>
<div>&nbsp;* Jackie Kay</div>
<div>&nbsp;* Jennifer Buehler</div>
<div>&nbsp;* KazutoMurase</div>
<div>&nbsp;* Kei Okada</div>
<div>&nbsp;* Kentaro Wada</div>
<div>&nbsp;* Mani Monajjemi</div>
<div>&nbsp;* Mathieu Labbe</div>
<div>&nbsp;* Michael Ferguson</div>
<div>&nbsp;* Mickael Gaillard</div>
<div>&nbsp;* Micka&euml;l Gaillard</div>
<div>&nbsp;* Mike Purvis</div>
<div>&nbsp;* Minglong Li</div>
<div>&nbsp;* Norman Li</div>
<div>&nbsp;* Patrick Beeson</div>
<div>&nbsp;* Paul Mathieu</div>
<div>&nbsp;* Piyush Khandelwal</div>
<div>&nbsp;* Ronald Ensing</div>
<div>&nbsp;* Ryohei Ueda</div>
<div>&nbsp;* Sachin Chitta</div>
<div>&nbsp;* Shohei Fujii</div>
<div>&nbsp;* Slamtec ROS Maintainer</div>
<div>&nbsp;* TORK</div>
<div>&nbsp;* Tim Liu</div>
<div>&nbsp;* William Wu</div>
<div>&nbsp;* Xuefeng Chang</div>
<div>&nbsp;* YoheiKakiuchi</div>
<div>&nbsp;* Younghun Ju</div>
<div>&nbsp;* Yuki Furuta</div>
<div>&nbsp;* Yuto Inagaki</div>
<div>&nbsp;* inagaki</div>
<div>&nbsp;* saito</div>
</div>
</div></div>

Announcing: KaCanOpen - An Open Plug&Play CANopen Stack for ROS in Modern C++

tl;dr: You use CANopen devices and ROS? Then checkout: http://wiki.ros.org/kacanopen (Repository: https://github.com/KITmedical/kacanopen)


Dear ROS community,

I'm happy to announce KaCanOpen, a plug&play ROS stack for CANopen devices (motors, remote I/Os, ...) written in modern C++.

KaCanOpen is an easy-to-use CANopen stack, which consists of four parts:

  • Drivers: A wide range of CAN hardware (USB, PCI, embedded) is supported using different CAN drivers. They have been developed by the CanFestival project. Follow the link for details.

  • Core: This is a library which implements basic CANopen protocols like NMT, SDO and PDO. As an example, you can easily fetch a value from a device (uploading in CANopen terminology) via core.sdo.upload(node_id, index, subindex). Furthermore, it allows you to register callbacks on certain events or any incoming messages, so one can build arbitrary CANopen nodes (master or slave) using this library.

  • Master: This library is intended to be used for a master node. It detects all nodes in a CAN network and gives direct access to them via standardized CiA® profiles. For example, on a motor device (profile CiA® 402) you can simply call mymotor.set_entry("Target velocity", 500). A main feature of this library is transparent SDO/PDO access to dictionary entries: By default a value is fetched and set via SDO. But you can also configure PDO mappings, which keep the value up-to-date in background via (much more lightweight) PDO messages. The call itself (mymotor.set_entry("Target velocity", 500)) remains unchanged.

  • ROS Bridge: This library provides a bridge to a ROS network, which makes KaCanOpen especially interesting for robotics. After setting up the CANopen network, the library can publish slave nodes so they are accessible through ROS messages. Special effort is put into the use of standardized message types which allows interaction with other software from the ROS universe. For example, motors can be operated using JointState messages.

KaCanOpen is designed to make use of modern C++11/14 features and to avoid redundant code on the user side wherever possible. Reusing all the available functionality, a custom node for a custom CANopen device can be written in less than 100 lines of code.


Although, I have the joy to announce KaCanOpen here, most credit goes to Thomas for all the effort he put into it!

Cheers,
Andreas
<div>
    tl;dr: You use CANopen devices and ROS? Then checkout: <a href="http://wiki.ros.org/kacanopen"></a><a class="moz-txt-link-freetext" href="http://wiki.ros.org/kacanopen">http://wiki.ros.org/kacanopen</a>
    (Repository: <a href="https://github.com/KITmedical/kacanopen">https://github.com/KITmedical/kacanopen</a>)<br><br><br>
    Dear ROS community,<br><br>
    I'm happy to announce <a href="http://wiki.ros.org/kacanopen">KaCanOpen</a>,
    a plug&amp;play ROS stack for CANopen devices (motors, remote I/Os,
    ...) written in modern C++.<br><br><p class="line867">KaCanOpen is an easy-to-use
      CANopen stack, which consists of four parts:<span class="anchor"></span></p>
    <ul>
<li>
        <p class="line891">Drivers: A wide range of CAN hardware (USB,
          PCI, embedded) is supported using different CAN drivers. They
          have been developed by the <a class="nonexistent" href="http://wiki.ros.org/CanFestival">CanFestival</a><span class="Apple-converted-space">&nbsp;</span>project. Follow the
          link for details.<span class="anchor"></span></p>
      </li>
      <li>
        <p class="line891">Core: This is a library which implements
          basic CANopen protocols like NMT, SDO and PDO. As an example,
          you can easily fetch a value from a device (uploading in<span class="Apple-converted-space">&nbsp;</span><a class="nonexistent" href="http://wiki.ros.org/CanOpen">CANopen</a><span class="Apple-converted-space">&nbsp;</span>terminology) via
            core.sdo.upload(node_id,&nbsp;index,&nbsp;subindex). Furthermore,
          it allows you to register callbacks on certain events or any
          incoming messages, so one can build arbitrary CANopen nodes
          (master or slave) using this library.<span class="anchor"></span></p>
      </li>
      <li>
        <p class="line891">Master: This library is intended to be used
          for a master node. It detects all nodes in a CAN network and
          gives direct access to them via standardized CiA&reg; profiles.
          For example, on a motor device (profile CiA&reg; 402) you can
          simply call mymotor.set_entry("Target&nbsp;velocity",&nbsp;500).
          A main feature of this library is transparent SDO/PDO access
          to dictionary entries: By default a value is fetched and set
          via SDO. But you can also configure PDO mappings, which keep
          the value up-to-date in background via (much more lightweight)
          PDO messages. The call itself (mymotor.set_entry("Target&nbsp;velocity",&nbsp;500))
          remains unchanged.<span class="anchor"></span></p>
      </li>
      <li>
        <p class="line891">ROS Bridge: This library provides a bridge
          to a ROS network, which makes KaCanOpen especially interesting
          for robotics. After setting up the CANopen network, the
          library can publish slave nodes so they are accessible through
          ROS messages. Special effort is put into the use of
          standardized message types which allows interaction with other
          software from the ROS universe. For example, motors can be
          operated using JointState messages.<span class="anchor"></span><span class="anchor"></span></p>
      </li>
    </ul>
<p class="line867">KaCanOpen is designed to
      make use of modern C++11/14 features and to avoid redundant code
      on the user side wherever possible. Reusing all the available
      functionality, a custom node for a custom CANopen device can be
      written in less than 100 lines of code.<br></p>
    <br>
    Although, I have the joy to announce KaCanOpen here, most credit
    goes to Thomas for all the effort he put into it!<br><br>
    Cheers,<br>
    Andreas<br>
</div>
Toni Oliver via ros-users | 20 Jun 17:54 2016

[jobs] Shadow Robot - looking for a new Software Engineer

Job description
The role of software engineers at Shadow Robot Ltd is to advance robotic systems, by implementing new solutions and algorithms, in order to realize complex tasks with a complex robots. Think about all the knowledge and skills a human requires to lift a simple glass of water, and try to imagine how you'd implement that with a highly sophisticated robotic system. 

Should you join our team your job would center on solving real world problems using robotics. We work on highly challenging and stimulating problems to deliver new solutions using advanced robotic systems. The job is quite versatile, ranging from driver development, to more high level cognition. Being part of a team of highly skilled individuals, we always strive to make you work on what you're best at.

Overall your goal will be making our robotic systems more reliable and easier to use for our customers. 


Company
We're a small central London based company formed in 1987 with a well established reputation for developing top end robotic systems. Our core product is our robotic Hand, but we're also involved in a list of Robotics based projects for research, nuclear, MOD, space and other applications. 

We're a close knit team, all passionate about robotics and will be happy to share our knowledge in different domains, ranging from electronics to manufacturing.

Shadow's mission is to use robotics technology to solve real-world problems.

Skills:
 Must have:
  - highly proficient in C++ or python
  - good knowledge of programming under Linux
 
 Nice to have:
  - previous experience or keen interest in robotics
  - previous experience using ROS (www.ros.org)
  

Experience:
 - minimum 2 years programming experience.

Contact:


--

Toni Oliver
Head of Software
+44 20 7700 2487
 

Shadow Robot Company Ltd.
251 Liverpool Road, N1 1LX, UK
Registered Number 3308007 (England & Wales)

 


Shadow Robot Company Ltd.
251 Liverpool Road, N1 1LX, UK
Registered Number 3308007 (England & Wales)
<div>
<div dir="ltr">
<div>Job&nbsp;description</div>
<div>The role of software engineers at Shadow Robot Ltd is to advance robotic systems, by implementing new solutions and algorithms, in order to realize complex tasks with a complex robots. Think about all the knowledge and skills a human requires to lift a simple glass of water, and try to imagine how you'd implement that with a highly sophisticated robotic system.&nbsp;</div>
<div><br></div>
<div>Should you join our team your&nbsp;job&nbsp;would center on solving real world problems using robotics. We work on highly challenging and stimulating problems to deliver new solutions using advanced robotic systems. The&nbsp;job&nbsp;is quite versatile, ranging from driver development, to more high level cognition. Being part of a team of highly skilled individuals, we always strive to make you work on what you're best at.</div>
<div><br></div>
<div>Overall your goal will be making our robotic systems more reliable and easier to use for our customers.&nbsp;</div>
<div><br></div>
<div><br></div>
<div>Company</div>
<div>We're a small central London based company formed in 1987 with a well established reputation for developing top end robotic systems. Our core product is our robotic Hand, but we're also involved in a list of Robotics based projects for research, nuclear, MOD, space and other applications.&nbsp;</div>
<div><br></div>
<div>We're a close knit team, all passionate about robotics and will be happy to share our knowledge in different domains, ranging from electronics to manufacturing.</div>
<div><br></div>
<div>Shadow's mission is to use robotics technology to solve real-world problems.</div>
<div><br></div>
<div>Skills:</div>
<div>&nbsp;Must have:</div>
<div>&nbsp; - highly proficient in C++ or python</div>
<div>&nbsp; - good knowledge of programming under Linux</div>
<div>&nbsp;</div>
<div>&nbsp;Nice to have:</div>
<div>&nbsp; - previous experience or keen interest in robotics</div>
<div>&nbsp; - previous experience using ROS (<a href="http://www.ros.org/" target="_blank">www.ros.org</a>)</div>
<div>&nbsp;&nbsp;</div>
<div><br></div>
<div>Experience:</div>
<div>&nbsp;- minimum 2 years programming experience.</div>
<div><br></div>
<div>Contact:</div>
<div>&nbsp;<a href="mailto:toni <at> shadowrobot.com" target="_blank">toni@...</a>
</div>
<div>&nbsp;<a href="http://www.shadowrobot.com/" target="_blank">www.shadowrobot.com</a>
</div>
<div><br></div>
<div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr">
<p><span>Toni Oliver<br></span><span>Head of Software<br></span><a href="tel:%2B44%2020%207700%202487" value="+442077002487" target="_blank">+44 20 7700 2487</a><br><span>&nbsp;</span><br></p>
<div><p></p></div>
<div align="center"></div>
<p><span>Shadow Robot Company Ltd.</span><br><span>251 Liverpool Road, N1 1LX, UK<br>Registered Number 3308007 (England &amp; Wales)</span></p>
<div><div>
<div align="center"></div>
<p>&nbsp;</p>
</div></div>
</div></div></div></div></div></div>
</div>

<br>Shadow Robot Company Ltd.<br>251 Liverpool Road, N1 1LX, UK<br>Registered Number 3308007 (England &amp; Wales)<div><div></div></div>
</div>

algorithms for image recognition, learning recognition

Hi,

Does ROS is suitable for algorithms for image recognition, learning recognition ? I also search experts in this field for our autonomous truck solution you can see us at www.vivifytrucks.com for more information about what we need.

--Jon
<div><div dir="ltr">
<span>Hi,</span><div><br></div>
<div>Does ROS is suitable for&nbsp;algorithms for image recognition, learning recognition ? I also search experts in this field for our autonomous truck solution you can see us at&nbsp;<a href="http://www.vivifytrucks.com/" target="_blank">www.vivifytrucks.com</a>&nbsp;for more information about what we need.</div>
<div><br></div>
<div>--Jon</div>
</div></div>
Qbotics Labs via ros-users | 17 Jun 11:58 2016

[news] ICRA 2016 Lookback Video | Robotics Exhibition | Created by Qbotics Labs

Hi all

I am Lentin Joseph, CEO of Qbotics Labs  | Author of two books in R.O.S. 

I like to share a lookback video of ICRA 2016 Robotics exhibitions which we have created!!

ICRA 2016 Lookback Video : https://www.youtube.com/watch?v=LyjPEIypl0Y

Hope you like it !!

Thanks & Regards

--


Thanks & Regards
Founder of Qbotics Labs

<div><div dir="ltr">
<span>Hi all</span><div><br></div>
<div>I am Lentin Joseph, CEO of Qbotics Labs &nbsp;| Author of two books in R.O.S.&nbsp;<br><br>I like to share a lookback video of ICRA 2016 Robotics exhibitions which we have created!!</div>
<div><br></div>
<div>ICRA 2016 Lookback Video :&nbsp;<a href="https://www.youtube.com/watch?v=LyjPEIypl0Y" target="_blank">https://www.youtube.com/watch?v=LyjPEIypl0Y</a>
</div>
<div><br></div>
<div>Hope you like it !!</div>
<div>
<span><br></span><span>Thanks &amp; Regards</span><span><br></span>
</div>
<div data-smartmail="gmail_signature"><div dir="ltr">
<div>
<div><span><br><a href="http://in.linkedin.com/in/lentinjoseph" target="_blank">Lentin Joseph</a></span></div>
<div><span><br>Founder of&nbsp;<a href="http://www.qboticslabs.com/" target="_blank">Qbotics Labs</a></span></div>
</div>
<div>
<br>Author of&nbsp;<br><a href="http://learn-robotics.com/" target="_blank">Learning Robotics using Python</a><br><br>
</div>
<div><a href="http://mastering-ros.com/" target="_blank">Mastering ROS for Robotics Programming</a></div>
</div></div>
<div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">
<div><br></div>
<br><div>
<div><span>Thanks &amp; Regards</span></div>
<div><span><a href="http://in.linkedin.com/in/lentinjoseph" target="_blank">Lentin Joseph</a></span></div>
<div><span>Founder of&nbsp;<a href="http://www.qboticslabs.com/" target="_blank">Qbotics Labs</a></span></div>
</div>
<div><br></div>
</div></div>
</div></div>

Re: Ideas for a robot

Hi Rohan,

Welcome to the community!

Shameless plug: we have just launched an Indiegogo campaign to produce
a cheap humanoid robot designed for teaching robotics and programming.
the platform is completely open source (both at software and hardware
level), 3D printable and supported by tutorials and guides.

Check us out at http://robotical.io - and feel free to ask me any
questions here or on the Indiegogo comment page.

Best,
-Nantas

On Thu, Jun 16, 2016 at 6:07 AM, Rohan Saxena via ros-users
<ros-users <at> lists.ros.org> wrote:
> Dear ROS users,
>
> My name is Rohan Saxena and I am a computer science sophomore at BITS
> Pilani, India. I have recently started pursuing my interest in robotics. I
> was looking for a robot which I could experiment and play around with, and
> watch my algorithms in action.
>
> I would really appreciate if roboticists, hobbyists or anyone in the field
> of robotics could point me in the direction of a robust, easy to use robot
> for a beginner looking to get into the thick of robotics.
>
> Thanks and cheers,
> Rohan Saxena.

--

-- 
λ Nantas Nardelli
λ Research assistant  <at>  IPAB (RAD)
λ http://rad.inf.ed.ac.uk/people/nardelli
λ University of Edinburgh
_______________________________________________
ros-users mailing list
ros-users <at> lists.ros.org
http://lists.ros.org/mailman/listinfo/ros-users
Rohan Saxena via ros-users | 16 Jun 07:07 2016

Ideas for a robot

Dear ROS users,

My name is Rohan Saxena and I am a computer science sophomore at BITS Pilani, India. I have recently started pursuing my interest in robotics. I was looking for a robot which I could experiment and play around with, and watch my algorithms in action.

I would really appreciate if roboticists, hobbyists or anyone in the field of robotics could point me in the direction of a robust, easy to use robot for a beginner looking to get into the thick of robotics.

Thanks and cheers,
Rohan Saxena.
<div><div dir="ltr">
<div>
<div>
<div>
<div>Dear ROS users,<br>
</div>
<br>My name is Rohan Saxena and I am a computer science sophomore at BITS Pilani, India. I have recently started pursuing my interest in robotics. I was looking for a robot which I could experiment and play around with, and watch my algorithms in action.<br>
</div>
<br>I would really appreciate if roboticists, hobbyists or anyone in the field of robotics could point me in the direction of a robust, easy to use robot for a beginner looking to get into the thick of robotics.<br><br>
</div>Thanks and cheers, <br>
</div>Rohan Saxena.<br>
</div></div>

Marty the Robot - a fund and educational walking robot!

Dear ROS users,

 We have just launched a crowdfunding campaign for a small educational bipedal robot aimed at getting both kids and hackers into robotics. We plan to develop and release a ROS API in the future to improve its ease of use and outreach. Please have a look:

 "Marty the Robot - a fun and educational walking robot! www.robotical.io

Marty is a cute little walking robot that's designed to give a great into to various aspects of robotics - from programming to electronics and even mechanics. He's WiFi enabled and programmable out of the box in Scratch, Python, C++, etc. If you have access to a 3D printer you can also customise its parts and expand it."

 We just began our campaign in indiegogo, any feedback or support would be greatly appreciated!

 Cheers,
           Alex
<div><div dir="ltr">Dear ROS users,<br><br>&nbsp;We have just launched a crowdfunding campaign for a small educational bipedal robot aimed at getting both kids and hackers into robotics. We plan to develop and release a ROS API in the future to improve its ease of use and outreach. Please have a look:<br><br>&nbsp;"<span>Marty the Robot - a fun and educational walking robot! <a href="http://www.robotical.io">www.robotical.io</a></span><br><br><span>Marty is a cute little walking robot that's designed to give a great into to various aspects of robotics - from programming to electronics and even mechanics. He's WiFi enabled and programmable out of the box in Scratch, Python, C++, etc. If you have access to a 3D printer you can also customise its parts and expand it."</span><div><span><br></span></div>
<div><span>&nbsp;We just began our campaign in indiegogo, any feedback or support would be greatly appreciated!<br><br>&nbsp;Cheers,<br>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Alex</span></div>
</div></div>

Re: Husqvarna Research Platform

Dear Stefan,

I’m very interested in your announcement of the HRP for the lawn mowers.
Are there any ideas about the public release  from Hasqvarna ?

1. Suggested lawn mower modell
2. Public available hardware interfaces for the robot
3. ROS-drivers

I’m happy to hear from you :-)

Cheers
Christian

-------------------------------------------------------------------
Christian Mock, Head of IT-System Designer Team
Xnet Communications GmbH,  +49-40-89702-204
Stresemannstr. 375 Haus 3,  22761 Hamburg, DE

Geschäftsführer:
Mariusz Roznowski&  Wolfgang Falz
Amtsgericht Hamburg HRB 57563
USt.-Id-Nr.: DE 812 136 413
-------------------------------------------------------------------

<div>Dear Stefan,<div class=""><br class=""></div>
<div class="">I&rsquo;m very interested in your announcement of the HRP for the lawn mowers.</div>
<div class="">Are there any ideas about the public release &nbsp;from Hasqvarna ?</div>
<div class=""><br class=""></div>
<div class="">1. Suggested lawn mower modell</div>
<div class="">2. Public available hardware interfaces for the robot</div>
<div class="">3. ROS-drivers</div>
<div class=""><br class=""></div>
<div class="">I&rsquo;m happy to hear from you :-)</div>
<div class=""><br class=""></div>
<div class="">Cheers</div>
<div class="">Christian</div>
<div class="">
<br class=""><div apple-content-edited="true" class="">
<div class=""><div class="">
<span class="">-------------------------------------------------------------------</span><br class=""><span class="">Christian Mock, Head of IT-System Designer Team</span><br class=""><span class="">Xnet Communications GmbH, &nbsp;+49-40-89702-204</span><br class=""><span class="">Stresemannstr. 375 Haus 3, &nbsp;22761 Hamburg, DE</span><br class=""><br class=""><span class="">Gesch&auml;ftsf&uuml;hrer:</span><br class=""><span class="">Mariusz Roznowski&amp; &nbsp;Wolfgang Falz</span><br class=""><span class="">Amtsgericht Hamburg HRB 57563</span><br class=""><span class="">USt.-Id-Nr.: DE 812 136 413</span><br class=""><span class="">-------------------------------------------------------------------</span>
</div></div>
</div>
<br class="">
</div>
</div>

ROS 2.0 tutorials

Hello everyone,

While ROS 2.0 is still under development (alpha releases), the good work of the OSRF team already allows many things to be done on top of it. After a few months working with ROS 2.0 and getting good preliminary results, our team decided to start contributing and switching towards ROS 2.0 for new products. While our contributions will take a bit to merge upstream we noticed that besides the fantastic resource put together by the OSRF and friends at design.ros2.org,  there were not many additional resources that newcomers could use to take the first steps. 

Our interns at Erle were having a bad time learning ROS 2.0 so we decided to have one of them create a video series about ROS 2.0 that others could benefit from. 
Asier, who now became a full time employee put together a series both in spanish and in english:

The content has proved to be useful for several people so we're glad to released it publicly and get your feedback. Feel free to send us your thinking. 

We've allocated some additional funding for this tutorial series so if you'd like to see some additional topic covered, let us know.

Regards,

Víctor Mayoral Vilches
CTO & Co-Founder



Erle Robotics
+34 616151561
skype: v.mayoral

<div><div dir="ltr">Hello everyone,<br><br>While ROS 2.0 is still under development (alpha releases), the good work of the OSRF team already allows many things to be done on top of it. After a few months working with ROS 2.0 and getting good preliminary results, our team decided to start contributing and switching towards ROS 2.0 for new products. While our contributions will take a bit to merge upstream we noticed that besides the fantastic resource put together by the OSRF and friends at&nbsp;<a href="http://design.ros2.org">design.ros2.org</a>, &nbsp;there were not many additional resources that newcomers could use to take the first steps.&nbsp;<div>
<div><br></div>
<div>Our interns at <a href="http://erlerobotics.com">Erle</a> were having a bad time learning ROS 2.0 so we decided to have one of them create a video series about ROS 2.0 that others could benefit from.&nbsp;</div>
<div>Asier, who now became a full time employee put together a series both in spanish and in english:</div>
<div>
<ul>
<li><a href="http://erlerobotics.com/docs/Robot_Operating_System/ROS_2/Tutoriales_(Spanish)/index.html">ROS 2.0 tutorials in spanish</a></li>
<li><a href="http://erlerobotics.com/docs/Robot_Operating_System/ROS_2/Tutorials/index.html">ROS 2.0 tutorials in english</a></li>
</ul>
<div>
<div><br></div>
<div>The content has proved to be useful for several people so we're glad to released it publicly and get your feedback. Feel free to send us your thinking.&nbsp;</div>
<div><br></div>
<div>We've allocated some additional funding for this tutorial series so if you'd like to see some additional topic covered, let us know.</div>
<div><br></div>
<div>Regards,</div>
<div><br></div>
<div><div>
<div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr">V&iacute;ctor Mayoral Vilches<div>CTO &amp; Co-Founder</div>
<div><br></div>
<div><br></div>
<div><br></div>
<div>Erle Robotics</div>
<div>
<a href="http://erlerobotics.com" target="_blank">erlerobotics.com</a> | <a href="mailto:victor <at> erlerobot.com" target="_blank">victor@...</a>
</div>
<div>+34 616151561<br>
</div>
<div>skype: v.mayoral<br>
</div>
<div><br></div>
</div></div></div></div></div></div></div></div></div>
</div></div>
</div>
</div>
</div>
</div></div>

Gmane