Jonathan Bohren | 28 Jan 03:38 2015
Picon

ROS Index [beta] Announcement

This started as a holiday-hack / side-project, but now it's a pretty usable tool. 



Pretty much speaks for itself. Feedback (and contributions) welcome!

Now back to real work.
-jon
<div>
<p>This started as a holiday-hack / side-project, but now it's a pretty usable tool.&nbsp;</p>
<div><br></div>
<div><a href="http://rosindex.github.io/">http://rosindex.github.io/</a></div>
<div><br></div>
<div>Pretty much speaks for itself. Feedback (and contributions) welcome!<br>
</div>
<div><br></div>
<div>Now back to real work.</div>
<div>-jon</div>
</div>
Jordi Pages | 27 Jan 11:09 2015

New Mobile Manipulator: TIAGo robot

At Pal Robotics we are passionate for robotics. Today we are proud to introduce you to our latest robot the Mobile Manipulator TIAGo (Take It And Go), aimed at becoming your best research partner. 

TIAGo is a mobile research platform enabled for perception, manipulation and interaction tasks. The robot comprises a sensorized pan-tilt head, a lifting torso and an arm that ensure a large manipulation workspace. It has been designed to have a versatile hand contributing to its manipulation and interaction skills. TIAGo is flexible, configurable, open, upgradable and affordable. An advanced robot to boost research areas from low level control to high level applications and service robotics. 
  
It is fully compatible with ROS and furthermore it comes with multiple out-of-the-box functionalities like: 

* Multi-sensor navigation 
* Collision free motion planning 
* Detection of people, faces and objects 
* Speech recognition and synthesis 

All of which can be replaced for your own implementations: our system is open for you and adapts to your needs. 

Discover more about TIAGo at the website: 

www.tiago.pal-robotics.com

We envision a robotic platform that will help you create service robotics solutions. As always, we welcome partners that pursue our interest in advancing the field of robotics. 

For further information contact us at tiago-3MzGGok7BHU5ffrT631h+Q@public.gmane.org. We will be pleased to answer any doubts and help you with your research. 

We look forward to hearing back from you. 

Kindest regards, 

The PAL Robotics team 

P.S.: A peek of some of the other things we do: 

PAL Robotics at Humanoids 2014
PMB2 Mobile base
REEM-C

<div><div dir="ltr">
<div>
<span>At Pal Robotics we are passionate for robotics. Today we are proud to introduce you to our latest robot the Mobile Manipulator TIAGo (Take It And Go), aimed at becoming your best research partner.&nbsp;</span><br><br><a href="http://tiago.pal-robotics.com/" target="_top" rel="nofollow" link="external">TIAGo</a><span>&nbsp;is a mobile research platform enabled for perception, manipulation and interaction tasks. The robot comprises a sensorized pan-tilt head, a lifting torso and an arm that ensure a large manipulation workspace. It has been designed to have a versatile hand contributing to its manipulation and interaction skills. TIAGo is flexible, configurable, open, upgradable and affordable. An advanced robot to boost research areas from low level control to high level applications and service robotics.&nbsp;</span><br><span>&nbsp;&nbsp;</span><br><span>It is fully compatible with ROS and furthermore it comes with multiple out-of-the-box functionalities like:&nbsp;</span><br><br><span>* Multi-sensor navigation&nbsp;</span><br><span>* Collision free motion planning&nbsp;</span><br><span>* Detection of people, faces and objects&nbsp;</span><br><span>* Speech recognition and synthesis&nbsp;</span><br><br><span>All of which can be replaced for your own implementations: our system is open for you and adapts to your needs.&nbsp;</span><br><br><span>Discover more about TIAGo at the website:&nbsp;</span><br><br><a href="http://tiago.pal-robotics.com/" target="_top" rel="nofollow" link="external">www.tiago.pal-robotics.com</a><br><br><span>We envision a robotic platform that will help you create service robotics solutions. As always, we welcome partners that pursue our interest in advancing the field of robotics.&nbsp;</span><br><br><span>For further information contact us at&nbsp;</span><a href="mailto:tiago@..." target="_top" rel="nofollow" link="external">tiago@...</a><span>. We will be pleased to answer any doubts and help you with your research.&nbsp;</span><br><br><span>We look forward to hearing back from you.&nbsp;</span><br><br><span>Kindest regards,&nbsp;</span><br><br><span>The PAL Robotics team&nbsp;</span><br><br><span>P.S.: A peek of some of the other things we do:&nbsp;</span><br><br><a href="http://pal-robotics.us8.list-manage1.com/track/click?u=c08e8ca1fb3efd38740b5a9a3&amp;id=802417c3ca&amp;e=8c20580269" target="_top" rel="nofollow" link="external">PAL Robotics at Humanoids 2014</a><br><a href="http://pal-robotics.us8.list-manage.com/track/click?u=c08e8ca1fb3efd38740b5a9a3&amp;id=c40794a2df&amp;e=8c20580269" target="_top" rel="nofollow" link="external">PMB2 Mobile base</a><br><a href="http://pal-robotics.us8.list-manage.com/track/click?u=c08e8ca1fb3efd38740b5a9a3&amp;id=e3427bf9a5&amp;e=8c20580269" target="_top" rel="nofollow" link="external">REEM-C</a><br>
</div>
<br>
</div></div>
Tully Foote | 27 Jan 03:15 2015

New Indigo Packages

Hi Everyone,

We have another installment of ROS Indigo updates. There are over 100 new packages as well as 143 updated packages. This is all thanks to the contributions of maintainers from all around the world. Maintainers with updated packages in this update are listed below.

Your ROS Release Team



Updates to indigo

Added Packages [120]:
 * ros-indigo-anj-featurenav: 0.1.1-0
 * ros-indigo-care-o-bot-desktop: 0.6.3-0
 * ros-indigo-carl-phidgets: 0.0.13-0
 * ros-indigo-crossing-detector: 0.1.8-0
 * ros-indigo-dfs-explorer: 0.1.8-0
 * ros-indigo-eigen-typekit: 2.8.0-0
 * ros-indigo-ethercat-trigger-controllers: 1.10.12-0
 * ros-indigo-featurenav-base: 0.1.1-0
 * ros-indigo-fingertip-pressure: 1.8.13-1
 * ros-indigo-goto-crossing: 0.1.8-0
 * ros-indigo-husky-base: 0.1.2-0
 * ros-indigo-husky-bringup: 0.1.0-0
 * ros-indigo-husky-control: 0.0.2-0
 * ros-indigo-husky-description: 0.1.1-0
 * ros-indigo-husky-desktop: 0.1.0-0
 * ros-indigo-husky-gazebo: 0.1.1-1
 * ros-indigo-husky-msgs: 0.0.1-0
 * ros-indigo-husky-navigation: 0.1.0-0
 * ros-indigo-husky-robot: 0.1.0-0
 * ros-indigo-husky-simulator: 0.1.1-1
 * ros-indigo-husky-viz: 0.1.0-0
 * ros-indigo-ivcon: 0.1.5-0
 * ros-indigo-joint-trajectory-action: 1.10.12-0
 * ros-indigo-kdl-typekit: 2.8.0-0
 * ros-indigo-kinect-aux: 0.0.1-0
 * ros-indigo-lama-common: 0.1.8-0
 * ros-indigo-lama-core: 0.1.1-4
 * ros-indigo-lama-interfaces: 0.1.1-4
 * ros-indigo-lama-jockeys: 0.1.1-4
 * ros-indigo-lama-msgs: 0.1.1-4
 * ros-indigo-lj-costmap: 0.1.2-0
 * ros-indigo-lj-laser: 0.1.3-0
 * ros-indigo-lj-laser-heading: 0.1.3-0
 * ros-indigo-local-map: 0.1.8-0
 * ros-indigo-log4cpp: 2.8.0-0
 * ros-indigo-map-ray-caster: 0.1.8-0
 * ros-indigo-metaruby: 1.0.0-3
 * ros-indigo-moveit-full: 0.6.1-0
 * ros-indigo-moveit-full-pr2: 0.6.1-0
 * ros-indigo-moveit-pr2: 0.6.1-0
 * ros-indigo-myo-ros: 0.1.2-0
 * ros-indigo-naoqi-bridge: 0.4.4-0
 * ros-indigo-naoqi-tools: 0.4.4-0
 * ros-indigo-nj-costmap: 0.1.2-0
 * ros-indigo-nj-escape-crossing: 0.1.8-0
 * ros-indigo-nj-laser: 0.1.3-0
 * ros-indigo-nj-oa-costmap: 0.1.2-0
 * ros-indigo-nj-oa-laser: 0.1.3-0
 * ros-indigo-nlj-dummy: 0.1.8-0
 * ros-indigo-object-recognition-linemod: 0.3.3-0
 * ros-indigo-object-recognition-renderer: 0.2.2-0
 * ros-indigo-ocean-battery-driver: 1.1.5-0
 * ros-indigo-ocl: 2.8.0-0
 * ros-indigo-openrtm-ros-bridge: 1.2.7-0
 * ros-indigo-pcan-topics: 1.0.11-0
 * ros-indigo-pm-fourier: 0.1.1-0
 * ros-indigo-pm-mcc: 0.1.1-0
 * ros-indigo-polygon-matcher: 0.1.1-0
 * ros-indigo-power-monitor: 1.1.5-0
 * ros-indigo-power-msgs: 0.1.1-0
 * ros-indigo-pr2-calibration-controllers: 1.10.12-0
 * ros-indigo-pr2-common: 1.11.8-0
 * ros-indigo-pr2-controller-interface: 1.8.16-0
 * ros-indigo-pr2-controller-manager: 1.8.16-0
 * ros-indigo-pr2-controllers: 1.10.12-0
 * ros-indigo-pr2-controllers-msgs: 1.10.12-0
 * ros-indigo-pr2-dashboard-aggregator: 1.11.8-0
 * ros-indigo-pr2-description: 1.11.8-0
 * ros-indigo-pr2-gripper-action: 1.10.12-0
 * ros-indigo-pr2-hardware-interface: 1.8.16-0
 * ros-indigo-pr2-head-action: 1.10.12-0
 * ros-indigo-pr2-machine: 1.11.8-0
 * ros-indigo-pr2-mechanism: 1.8.16-0
 * ros-indigo-pr2-mechanism-controllers: 1.10.12-0
 * ros-indigo-pr2-mechanism-diagnostics: 1.8.16-0
 * ros-indigo-pr2-mechanism-model: 1.8.16-0
 * ros-indigo-pr2-moveit-config: 0.6.1-0
 * ros-indigo-pr2-moveit-plugins: 0.6.1-0
 * ros-indigo-pr2-moveit-tutorials: 0.6.1-0
 * ros-indigo-pr2-msgs: 1.11.8-0
 * ros-indigo-pr2-power-board: 1.1.5-0
 * ros-indigo-pr2-power-drivers: 1.1.5-0
 * ros-indigo-rfsm: 1.0.0-0
 * ros-indigo-robot-mechanism-controllers: 1.10.12-0
 * ros-indigo-ros-package-web-server: 0.0.1-0
 * ros-indigo-roseus-tutorials: 1.2.1-0
 * ros-indigo-rtt: 2.8.0-1
 * ros-indigo-rtt-actionlib: 2.8.0-0
 * ros-indigo-rtt-actionlib-msgs: 2.8.0-0
 * ros-indigo-rtt-common-msgs: 2.8.0-0
 * ros-indigo-rtt-diagnostic-msgs: 2.8.0-0
 * ros-indigo-rtt-dynamic-reconfigure: 2.8.0-0
 * ros-indigo-rtt-geometry: 2.8.0-0
 * ros-indigo-rtt-geometry-msgs: 2.8.0-0
 * ros-indigo-rtt-kdl-conversions: 2.8.0-0
 * ros-indigo-rtt-nav-msgs: 2.8.0-0
 * ros-indigo-rtt-ros: 2.8.0-0
 * ros-indigo-rtt-ros-comm: 2.8.0-0
 * ros-indigo-rtt-ros-integration: 2.8.0-0
 * ros-indigo-rtt-ros-msgs: 2.8.0-0
 * ros-indigo-rtt-rosclock: 2.8.0-0
 * ros-indigo-rtt-roscomm: 2.8.0-0
 * ros-indigo-rtt-rosdeployment: 2.8.0-0
 * ros-indigo-rtt-rosgraph-msgs: 2.8.0-0
 * ros-indigo-rtt-rosnode: 2.8.0-0
 * ros-indigo-rtt-rospack: 2.8.0-0
 * ros-indigo-rtt-rosparam: 2.8.0-0
 * ros-indigo-rtt-sensor-msgs: 2.8.0-0
 * ros-indigo-rtt-shape-msgs: 2.8.0-0
 * ros-indigo-rtt-std-msgs: 2.8.0-0
 * ros-indigo-rtt-std-srvs: 2.8.0-0
 * ros-indigo-rtt-stereo-msgs: 2.8.0-0
 * ros-indigo-rtt-tf: 2.8.0-0
 * ros-indigo-rtt-trajectory-msgs: 2.8.0-0
 * ros-indigo-rtt-visualization-msgs: 2.8.0-0
 * ros-indigo-single-joint-position-action: 1.10.12-0
 * ros-indigo-spatial-world-model: 0.0.3-0
 * ros-indigo-ueye-cam: 1.0.8-0
 * ros-indigo-utilrb: 2.8.0-1
 * ros-indigo-zbar-ros: 0.0.4-0


Updated Packages [143]:
 * ros-indigo-care-o-bot: 0.6.0-0 -> 0.6.3-0
 * ros-indigo-care-o-bot-robot: 0.6.0-0 -> 0.6.3-0
 * ros-indigo-care-o-bot-simulation: 0.6.0-0 -> 0.6.3-0
 * ros-indigo-carl-bot: 0.0.11-0 -> 0.0.13-0
 * ros-indigo-carl-bringup: 0.0.11-0 -> 0.0.13-0
 * ros-indigo-carl-description: 0.0.11-0 -> 0.0.13-0
 * ros-indigo-carl-dynamixel: 0.0.11-0 -> 0.0.13-0
 * ros-indigo-carl-interactive-manipulation: 0.0.11-0 -> 0.0.13-0
 * ros-indigo-carl-moveit: 0.0.3-0 -> 0.0.5-0
 * ros-indigo-carl-teleop: 0.0.11-0 -> 0.0.13-0
 * ros-indigo-carl-tools: 0.0.11-0 -> 0.0.13-0
 * ros-indigo-default-cfg-fkie: 0.3.16-0 -> 0.3.17-0
 * ros-indigo-diagnostic-aggregator: 1.8.6-0 -> 1.8.7-0
 * ros-indigo-diagnostic-analysis: 1.8.6-0 -> 1.8.7-0
 * ros-indigo-diagnostic-common-diagnostics: 1.8.6-0 -> 1.8.7-0
 * ros-indigo-diagnostic-updater: 1.8.6-0 -> 1.8.7-0
 * ros-indigo-diagnostics: 1.8.6-0 -> 1.8.7-0
 * ros-indigo-euslisp: 9.1.0-2 -> 9.1.0-3
 * ros-indigo-grizzly-description: 0.3.0-0 -> 0.3.1-0
 * ros-indigo-grizzly-motion: 0.3.0-0 -> 0.3.1-0
 * ros-indigo-grizzly-msgs: 0.3.0-0 -> 0.3.1-0
 * ros-indigo-grizzly-navigation: 0.3.0-0 -> 0.3.1-0
 * ros-indigo-grizzly-teleop: 0.3.0-0 -> 0.3.1-0
 * ros-indigo-hrpsys: 315.2.8-1 -> 315.2.8-2
 * ros-indigo-innok-heros-driver: 1.0.0-0 -> 1.0.1-0
 * ros-indigo-innok-heros-lights: 1.0.0-1 -> 1.0.1-0
 * ros-indigo-interactive-marker-tutorials: 0.9.0-0 -> 0.9.1-0
 * ros-indigo-interactive-world: 0.0.2-0 -> 0.0.3-0
 * ros-indigo-interactive-world-msgs: 0.0.2-0 -> 0.0.3-0
 * ros-indigo-interactive-world-parser: 0.0.2-0 -> 0.0.3-0
 * ros-indigo-interactive-world-tools: 0.0.2-0 -> 0.0.3-0
 * ros-indigo-jackal-control: 0.4.1-0 -> 0.5.0-0
 * ros-indigo-jackal-description: 0.4.1-0 -> 0.5.0-0
 * ros-indigo-jackal-desktop: 0.3.0-0 -> 0.3.1-0
 * ros-indigo-jackal-gazebo: 0.2.3-0 -> 0.3.0-0
 * ros-indigo-jackal-msgs: 0.4.1-0 -> 0.5.0-0
 * ros-indigo-jackal-navigation: 0.4.1-0 -> 0.5.0-0
 * ros-indigo-jackal-simulator: 0.2.3-0 -> 0.3.0-0
 * ros-indigo-jackal-viz: 0.3.0-0 -> 0.3.1-0
 * ros-indigo-jaco-description: 0.0.11-0 -> 0.0.12-0
 * ros-indigo-jaco-interaction: 0.0.11-0 -> 0.0.12-0
 * ros-indigo-jaco-sdk: 0.0.11-0 -> 0.0.12-0
 * ros-indigo-jaco-teleop: 0.0.11-0 -> 0.0.12-0
 * ros-indigo-jinteractiveworld: 0.0.2-0 -> 0.0.3-0
 * ros-indigo-jsk-roseus: 1.1.29-0 -> 1.2.1-0
 * ros-indigo-jskeus: 1.0.1-1 -> 1.0.2-4
 * ros-indigo-libmavconn: 0.9.4-0 -> 0.10.0-0
 * ros-indigo-librviz-tutorial: 0.9.0-0 -> 0.9.1-0
 * ros-indigo-lms1xx: 0.1.1-0 -> 0.1.2-0
 * ros-indigo-master-discovery-fkie: 0.3.16-0 -> 0.3.17-0
 * ros-indigo-master-sync-fkie: 0.3.16-0 -> 0.3.17-0
 * ros-indigo-mavlink: 2014.12.12-1 -> 2015.1.21-1
 * ros-indigo-mavros: 0.9.4-0 -> 0.10.0-0
 * ros-indigo-mavros-extras: 0.9.4-0 -> 0.10.0-0
 * ros-indigo-moveit-core: 0.6.13-0 -> 0.6.15-0
 * ros-indigo-moveit-msgs: 0.6.0-0 -> 0.6.1-0
 * ros-indigo-moveit-ros: 0.6.4-0 -> 0.6.5-0
 * ros-indigo-moveit-ros-benchmarks: 0.6.4-0 -> 0.6.5-0
 * ros-indigo-moveit-ros-benchmarks-gui: 0.6.4-0 -> 0.6.5-0
 * ros-indigo-moveit-ros-manipulation: 0.6.4-0 -> 0.6.5-0
 * ros-indigo-moveit-ros-move-group: 0.6.4-0 -> 0.6.5-0
 * ros-indigo-moveit-ros-perception: 0.6.4-0 -> 0.6.5-0
 * ros-indigo-moveit-ros-planning: 0.6.4-0 -> 0.6.5-0
 * ros-indigo-moveit-ros-planning-interface: 0.6.4-0 -> 0.6.5-0
 * ros-indigo-moveit-ros-robot-interaction: 0.6.4-0 -> 0.6.5-0
 * ros-indigo-moveit-ros-visualization: 0.6.4-0 -> 0.6.5-0
 * ros-indigo-moveit-ros-warehouse: 0.6.4-0 -> 0.6.5-0
 * ros-indigo-moveit-visual-tools: 2.1.0-0 -> 2.2.0-0
 * ros-indigo-multimaster-fkie: 0.3.16-0 -> 0.3.17-0
 * ros-indigo-multimaster-msgs-fkie: 0.3.16-0 -> 0.3.17-0
 * ros-indigo-naoqi-driver: 0.4.3-1 -> 0.4.4-0
 * ros-indigo-naoqi-msgs: 0.4.3-1 -> 0.4.4-0
 * ros-indigo-naoqi-sensors: 0.4.3-1 -> 0.4.4-0
 * ros-indigo-node-manager-fkie: 0.3.16-0 -> 0.3.17-0
 * ros-indigo-ntpd-driver: 1.0.1-0 -> 1.0.2-0
 * ros-indigo-object-recognition-core: 0.6.3-0 -> 0.6.4-0
 * ros-indigo-ompl-visual-tools: 2.2.0-0 -> 2.2.1-0
 * ros-indigo-openni2-launch: 0.2.1-0 -> 0.2.2-0
 * ros-indigo-openrtm-aist: 1.1.0-24 -> 1.1.0-25
 * ros-indigo-openrtm-aist-python: 1.1.0-5 -> 1.1.0-6
 * ros-indigo-pano-core: 2.3.1-0 -> 2.3.2-0
 * ros-indigo-pano-py: 2.3.1-0 -> 2.3.2-0
 * ros-indigo-pano-ros: 2.3.1-0 -> 2.3.2-0
 * ros-indigo-pcl-ros: 1.2.2-0 -> 1.2.5-0
 * ros-indigo-perception-pcl: 1.2.2-0 -> 1.2.5-0
 * ros-indigo-pointcloud-to-laserscan: 1.2.2-0 -> 1.2.5-0
 * ros-indigo-rail-collada-models: 0.0.1-0 -> 0.0.2-0
 * ros-indigo-robot-upstart: 0.0.6-1 -> 0.1.1-0
 * ros-indigo-roboteq-diagnostics: 0.1.1-0 -> 0.1.2-0
 * ros-indigo-roboteq-driver: 0.1.1-0 -> 0.1.2-0
 * ros-indigo-roboteq-msgs: 0.1.1-0 -> 0.1.2-0
 * ros-indigo-rocon-app-manager: 0.7.4-0 -> 0.7.6-0
 * ros-indigo-rocon-app-platform: 0.7.4-0 -> 0.7.6-0
 * ros-indigo-rocon-app-utilities: 0.7.4-0 -> 0.7.6-0
 * ros-indigo-rocon-apps: 0.7.4-0 -> 0.7.6-0
 * ros-indigo-rocon-bubble-icons: 0.1.11-0 -> 0.1.13-0
 * ros-indigo-rocon-console: 0.1.11-0 -> 0.1.13-0
 * ros-indigo-rocon-ebnf: 0.1.11-0 -> 0.1.13-0
 * ros-indigo-rocon-icons: 0.1.11-0 -> 0.1.13-0
 * ros-indigo-rocon-interactions: 0.1.11-0 -> 0.1.13-0
 * ros-indigo-rocon-launch: 0.1.11-0 -> 0.1.13-0
 * ros-indigo-rocon-master-info: 0.1.11-0 -> 0.1.13-0
 * ros-indigo-rocon-python-comms: 0.1.11-0 -> 0.1.13-0
 * ros-indigo-rocon-python-redis: 0.1.11-0 -> 0.1.13-0
 * ros-indigo-rocon-python-utils: 0.1.11-0 -> 0.1.13-0
 * ros-indigo-rocon-python-wifi: 0.1.11-0 -> 0.1.13-0
 * ros-indigo-rocon-semantic-version: 0.1.11-0 -> 0.1.13-0
 * ros-indigo-rocon-tools: 0.1.11-0 -> 0.1.13-0
 * ros-indigo-rocon-uri: 0.1.11-0 -> 0.1.13-0
 * ros-indigo-ros-ethernet-rmp: 0.0.6-0 -> 0.0.7-0
 * ros-indigo-rosapi: 0.7.7-0 -> 0.7.8-0
 * ros-indigo-rosbridge-library: 0.7.7-0 -> 0.7.8-0
 * ros-indigo-rosbridge-server: 0.7.7-0 -> 0.7.8-0
 * ros-indigo-rosbridge-suite: 0.7.7-0 -> 0.7.8-0
 * ros-indigo-roseus: 1.1.29-0 -> 1.2.1-0
 * ros-indigo-roseus-smach: 1.1.29-0 -> 1.2.1-0
 * ros-indigo-rviz-plugin-tutorials: 0.9.0-0 -> 0.9.1-0
 * ros-indigo-rviz-python-tutorial: 0.9.0-0 -> 0.9.1-0
 * ros-indigo-rviz-visual-tools: 1.4.0-0 -> 1.5.0-0
 * ros-indigo-self-test: 1.8.6-0 -> 1.8.7-0
 * ros-indigo-sick-tim: 0.0.2-0 -> 0.0.3-0
 * ros-indigo-stage-ros: 1.7.2-0 -> 1.7.3-0
 * ros-indigo-test-diagnostic-aggregator: 1.8.6-0 -> 1.8.7-0
 * ros-indigo-turtlebot: 2.3.4-0 -> 2.3.5-0
 * ros-indigo-turtlebot-actions: 2.3.1-0 -> 2.3.2-0
 * ros-indigo-turtlebot-apps: 2.3.1-0 -> 2.3.2-0
 * ros-indigo-turtlebot-bringup: 2.3.4-0 -> 2.3.5-0
 * ros-indigo-turtlebot-calibration: 2.3.1-0 -> 2.3.2-0
 * ros-indigo-turtlebot-capabilities: 2.3.4-0 -> 2.3.5-0
 * ros-indigo-turtlebot-description: 2.3.4-0 -> 2.3.5-0
 * ros-indigo-turtlebot-follower: 2.3.1-0 -> 2.3.2-0
 * ros-indigo-turtlebot-navigation: 2.3.1-0 -> 2.3.2-0
 * ros-indigo-turtlebot-panorama: 2.3.1-0 -> 2.3.2-0
 * ros-indigo-turtlebot-rapps: 2.3.1-0 -> 2.3.2-0
 * ros-indigo-turtlebot-teleop: 2.3.4-0 -> 2.3.5-0
 * ros-indigo-um6: 1.0.0-0 -> 1.1.1-0
 * ros-indigo-usb-cam: 0.1.13-0 -> 0.3.0-0
 * ros-indigo-visualization-marker-tutorials: 0.9.0-0 -> 0.9.1-0
 * ros-indigo-visualization-tutorials: 0.9.0-0 -> 0.9.1-0
 * ros-indigo-wpi-jaco: 0.0.11-0 -> 0.0.12-0
 * ros-indigo-wpi-jaco-msgs: 0.0.11-0 -> 0.0.12-0
 * ros-indigo-wpi-jaco-wrapper: 0.0.11-0 -> 0.0.12-0
 * ros-indigo-xacro: 1.9.2-0 -> 1.9.3-0


Removed Packages [0]:


Thanks to all ROS maintainers who make packages available to the ROS community. The above list of packages was made possible by the work of the following maintainers:
 * Alexander Tiderko
 * Alwin Heerklotz
 * Anqi Xu
 * Austin Hendrix
 * Brice Rebsamen
 * Daniel Stonier
 * Dave Coleman
 * David Kent
 * Devon Ash
 * Florian Weisshardt
 * Gaël Ecorchard
 * HJMeijdam
 * Ioan Sucan
 * Jihoon Lee
 * Jorge Santos
 * Kei Okada
 * Martin Günther
 * Melonee Wise
 * Michael Ferguson
 * Mikael Arguedas
 * Mike Purvis
 * Mitchell Wills
 * Morgan Quigley
 * MoveIt Setup Assistant
 * Murilo F. M.
 * OCL Development Team
 * OSRF
 * Orocos Developers
 * Orocos Developers Team
 * Orocos Development Team
 * Paul Bovbel
 * RTT Developers
 * Ruben Smits
 * Russell Toris
 * Ryan Gariepy
 * Sachin Chitta
 * Severin Lemaignan
 * Séverin Lemaignan
 * Vincent Rabaud
 * Vladimir Ermakov
 * William Woodall
 * Yan Ma
 * ruben smits

<div><div dir="ltr">
<div>
<div>Hi Everyone, <br><br>
</div>We have another installment of ROS Indigo updates. There are over 100 new packages as well as 143 updated packages. This is all thanks to the contributions of maintainers from all around the world. Maintainers with updated packages in this update are listed below. <br><br>
</div>Your ROS Release Team<br><div><div><div>
<br><br><br>Updates to indigo<br><br>Added Packages [120]:<br>&nbsp;* ros-indigo-anj-featurenav: 0.1.1-0<br>&nbsp;* ros-indigo-care-o-bot-desktop: 0.6.3-0<br>&nbsp;* ros-indigo-carl-phidgets: 0.0.13-0<br>&nbsp;* ros-indigo-crossing-detector: 0.1.8-0<br>&nbsp;* ros-indigo-dfs-explorer: 0.1.8-0<br>&nbsp;* ros-indigo-eigen-typekit: 2.8.0-0<br>&nbsp;* ros-indigo-ethercat-trigger-controllers: 1.10.12-0<br>&nbsp;* ros-indigo-featurenav-base: 0.1.1-0<br>&nbsp;* ros-indigo-fingertip-pressure: 1.8.13-1<br>&nbsp;* ros-indigo-goto-crossing: 0.1.8-0<br>&nbsp;* ros-indigo-husky-base: 0.1.2-0<br>&nbsp;* ros-indigo-husky-bringup: 0.1.0-0<br>&nbsp;* ros-indigo-husky-control: 0.0.2-0<br>&nbsp;* ros-indigo-husky-description: 0.1.1-0<br>&nbsp;* ros-indigo-husky-desktop: 0.1.0-0<br>&nbsp;* ros-indigo-husky-gazebo: 0.1.1-1<br>&nbsp;* ros-indigo-husky-msgs: 0.0.1-0<br>&nbsp;* ros-indigo-husky-navigation: 0.1.0-0<br>&nbsp;* ros-indigo-husky-robot: 0.1.0-0<br>&nbsp;* ros-indigo-husky-simulator: 0.1.1-1<br>&nbsp;* ros-indigo-husky-viz: 0.1.0-0<br>&nbsp;* ros-indigo-ivcon: 0.1.5-0<br>&nbsp;* ros-indigo-joint-trajectory-action: 1.10.12-0<br>&nbsp;* ros-indigo-kdl-typekit: 2.8.0-0<br>&nbsp;* ros-indigo-kinect-aux: 0.0.1-0<br>&nbsp;* ros-indigo-lama-common: 0.1.8-0<br>&nbsp;* ros-indigo-lama-core: 0.1.1-4<br>&nbsp;* ros-indigo-lama-interfaces: 0.1.1-4<br>&nbsp;* ros-indigo-lama-jockeys: 0.1.1-4<br>&nbsp;* ros-indigo-lama-msgs: 0.1.1-4<br>&nbsp;* ros-indigo-lj-costmap: 0.1.2-0<br>&nbsp;* ros-indigo-lj-laser: 0.1.3-0<br>&nbsp;* ros-indigo-lj-laser-heading: 0.1.3-0<br>&nbsp;* ros-indigo-local-map: 0.1.8-0<br>&nbsp;* ros-indigo-log4cpp: 2.8.0-0<br>&nbsp;* ros-indigo-map-ray-caster: 0.1.8-0<br>&nbsp;* ros-indigo-metaruby: 1.0.0-3<br>&nbsp;* ros-indigo-moveit-full: 0.6.1-0<br>&nbsp;* ros-indigo-moveit-full-pr2: 0.6.1-0<br>&nbsp;* ros-indigo-moveit-pr2: 0.6.1-0<br>&nbsp;* ros-indigo-myo-ros: 0.1.2-0<br>&nbsp;* ros-indigo-naoqi-bridge: 0.4.4-0<br>&nbsp;* ros-indigo-naoqi-tools: 0.4.4-0<br>&nbsp;* ros-indigo-nj-costmap: 0.1.2-0<br>&nbsp;* ros-indigo-nj-escape-crossing: 0.1.8-0<br>&nbsp;* ros-indigo-nj-laser: 0.1.3-0<br>&nbsp;* ros-indigo-nj-oa-costmap: 0.1.2-0<br>&nbsp;* ros-indigo-nj-oa-laser: 0.1.3-0<br>&nbsp;* ros-indigo-nlj-dummy: 0.1.8-0<br>&nbsp;* ros-indigo-object-recognition-linemod: 0.3.3-0<br>&nbsp;* ros-indigo-object-recognition-renderer: 0.2.2-0<br>&nbsp;* ros-indigo-ocean-battery-driver: 1.1.5-0<br>&nbsp;* ros-indigo-ocl: 2.8.0-0<br>&nbsp;* ros-indigo-openrtm-ros-bridge: 1.2.7-0<br>&nbsp;* ros-indigo-pcan-topics: 1.0.11-0<br>&nbsp;* ros-indigo-pm-fourier: 0.1.1-0<br>&nbsp;* ros-indigo-pm-mcc: 0.1.1-0<br>&nbsp;* ros-indigo-polygon-matcher: 0.1.1-0<br>&nbsp;* ros-indigo-power-monitor: 1.1.5-0<br>&nbsp;* ros-indigo-power-msgs: 0.1.1-0<br>&nbsp;* ros-indigo-pr2-calibration-controllers: 1.10.12-0<br>&nbsp;* ros-indigo-pr2-common: 1.11.8-0<br>&nbsp;* ros-indigo-pr2-controller-interface: 1.8.16-0<br>&nbsp;* ros-indigo-pr2-controller-manager: 1.8.16-0<br>&nbsp;* ros-indigo-pr2-controllers: 1.10.12-0<br>&nbsp;* ros-indigo-pr2-controllers-msgs: 1.10.12-0<br>&nbsp;* ros-indigo-pr2-dashboard-aggregator: 1.11.8-0<br>&nbsp;* ros-indigo-pr2-description: 1.11.8-0<br>&nbsp;* ros-indigo-pr2-gripper-action: 1.10.12-0<br>&nbsp;* ros-indigo-pr2-hardware-interface: 1.8.16-0<br>&nbsp;* ros-indigo-pr2-head-action: 1.10.12-0<br>&nbsp;* ros-indigo-pr2-machine: 1.11.8-0<br>&nbsp;* ros-indigo-pr2-mechanism: 1.8.16-0<br>&nbsp;* ros-indigo-pr2-mechanism-controllers: 1.10.12-0<br>&nbsp;* ros-indigo-pr2-mechanism-diagnostics: 1.8.16-0<br>&nbsp;* ros-indigo-pr2-mechanism-model: 1.8.16-0<br>&nbsp;* ros-indigo-pr2-moveit-config: 0.6.1-0<br>&nbsp;* ros-indigo-pr2-moveit-plugins: 0.6.1-0<br>&nbsp;* ros-indigo-pr2-moveit-tutorials: 0.6.1-0<br>&nbsp;* ros-indigo-pr2-msgs: 1.11.8-0<br>&nbsp;* ros-indigo-pr2-power-board: 1.1.5-0<br>&nbsp;* ros-indigo-pr2-power-drivers: 1.1.5-0<br>&nbsp;* ros-indigo-rfsm: 1.0.0-0<br>&nbsp;* ros-indigo-robot-mechanism-controllers: 1.10.12-0<br>&nbsp;* ros-indigo-ros-package-web-server: 0.0.1-0<br>&nbsp;* ros-indigo-roseus-tutorials: 1.2.1-0<br>&nbsp;* ros-indigo-rtt: 2.8.0-1<br>&nbsp;* ros-indigo-rtt-actionlib: 2.8.0-0<br>&nbsp;* ros-indigo-rtt-actionlib-msgs: 2.8.0-0<br>&nbsp;* ros-indigo-rtt-common-msgs: 2.8.0-0<br>&nbsp;* ros-indigo-rtt-diagnostic-msgs: 2.8.0-0<br>&nbsp;* ros-indigo-rtt-dynamic-reconfigure: 2.8.0-0<br>&nbsp;* ros-indigo-rtt-geometry: 2.8.0-0<br>&nbsp;* ros-indigo-rtt-geometry-msgs: 2.8.0-0<br>&nbsp;* ros-indigo-rtt-kdl-conversions: 2.8.0-0<br>&nbsp;* ros-indigo-rtt-nav-msgs: 2.8.0-0<br>&nbsp;* ros-indigo-rtt-ros: 2.8.0-0<br>&nbsp;* ros-indigo-rtt-ros-comm: 2.8.0-0<br>&nbsp;* ros-indigo-rtt-ros-integration: 2.8.0-0<br>&nbsp;* ros-indigo-rtt-ros-msgs: 2.8.0-0<br>&nbsp;* ros-indigo-rtt-rosclock: 2.8.0-0<br>&nbsp;* ros-indigo-rtt-roscomm: 2.8.0-0<br>&nbsp;* ros-indigo-rtt-rosdeployment: 2.8.0-0<br>&nbsp;* ros-indigo-rtt-rosgraph-msgs: 2.8.0-0<br>&nbsp;* ros-indigo-rtt-rosnode: 2.8.0-0<br>&nbsp;* ros-indigo-rtt-rospack: 2.8.0-0<br>&nbsp;* ros-indigo-rtt-rosparam: 2.8.0-0<br>&nbsp;* ros-indigo-rtt-sensor-msgs: 2.8.0-0<br>&nbsp;* ros-indigo-rtt-shape-msgs: 2.8.0-0<br>&nbsp;* ros-indigo-rtt-std-msgs: 2.8.0-0<br>&nbsp;* ros-indigo-rtt-std-srvs: 2.8.0-0<br>&nbsp;* ros-indigo-rtt-stereo-msgs: 2.8.0-0<br>&nbsp;* ros-indigo-rtt-tf: 2.8.0-0<br>&nbsp;* ros-indigo-rtt-trajectory-msgs: 2.8.0-0<br>&nbsp;* ros-indigo-rtt-visualization-msgs: 2.8.0-0<br>&nbsp;* ros-indigo-single-joint-position-action: 1.10.12-0<br>&nbsp;* ros-indigo-spatial-world-model: 0.0.3-0<br>&nbsp;* ros-indigo-ueye-cam: 1.0.8-0<br>&nbsp;* ros-indigo-utilrb: 2.8.0-1<br>&nbsp;* ros-indigo-zbar-ros: 0.0.4-0<br><br><br>Updated Packages [143]:<br>&nbsp;* ros-indigo-care-o-bot: 0.6.0-0 -&gt; 0.6.3-0<br>&nbsp;* ros-indigo-care-o-bot-robot: 0.6.0-0 -&gt; 0.6.3-0<br>&nbsp;* ros-indigo-care-o-bot-simulation: 0.6.0-0 -&gt; 0.6.3-0<br>&nbsp;* ros-indigo-carl-bot: 0.0.11-0 -&gt; 0.0.13-0<br>&nbsp;* ros-indigo-carl-bringup: 0.0.11-0 -&gt; 0.0.13-0<br>&nbsp;* ros-indigo-carl-description: 0.0.11-0 -&gt; 0.0.13-0<br>&nbsp;* ros-indigo-carl-dynamixel: 0.0.11-0 -&gt; 0.0.13-0<br>&nbsp;* ros-indigo-carl-interactive-manipulation: 0.0.11-0 -&gt; 0.0.13-0<br>&nbsp;* ros-indigo-carl-moveit: 0.0.3-0 -&gt; 0.0.5-0<br>&nbsp;* ros-indigo-carl-teleop: 0.0.11-0 -&gt; 0.0.13-0<br>&nbsp;* ros-indigo-carl-tools: 0.0.11-0 -&gt; 0.0.13-0<br>&nbsp;* ros-indigo-default-cfg-fkie: 0.3.16-0 -&gt; 0.3.17-0<br>&nbsp;* ros-indigo-diagnostic-aggregator: 1.8.6-0 -&gt; 1.8.7-0<br>&nbsp;* ros-indigo-diagnostic-analysis: 1.8.6-0 -&gt; 1.8.7-0<br>&nbsp;* ros-indigo-diagnostic-common-diagnostics: 1.8.6-0 -&gt; 1.8.7-0<br>&nbsp;* ros-indigo-diagnostic-updater: 1.8.6-0 -&gt; 1.8.7-0<br>&nbsp;* ros-indigo-diagnostics: 1.8.6-0 -&gt; 1.8.7-0<br>&nbsp;* ros-indigo-euslisp: 9.1.0-2 -&gt; 9.1.0-3<br>&nbsp;* ros-indigo-grizzly-description: 0.3.0-0 -&gt; 0.3.1-0<br>&nbsp;* ros-indigo-grizzly-motion: 0.3.0-0 -&gt; 0.3.1-0<br>&nbsp;* ros-indigo-grizzly-msgs: 0.3.0-0 -&gt; 0.3.1-0<br>&nbsp;* ros-indigo-grizzly-navigation: 0.3.0-0 -&gt; 0.3.1-0<br>&nbsp;* ros-indigo-grizzly-teleop: 0.3.0-0 -&gt; 0.3.1-0<br>&nbsp;* ros-indigo-hrpsys: 315.2.8-1 -&gt; 315.2.8-2<br>&nbsp;* ros-indigo-innok-heros-driver: 1.0.0-0 -&gt; 1.0.1-0<br>&nbsp;* ros-indigo-innok-heros-lights: 1.0.0-1 -&gt; 1.0.1-0<br>&nbsp;* ros-indigo-interactive-marker-tutorials: 0.9.0-0 -&gt; 0.9.1-0<br>&nbsp;* ros-indigo-interactive-world: 0.0.2-0 -&gt; 0.0.3-0<br>&nbsp;* ros-indigo-interactive-world-msgs: 0.0.2-0 -&gt; 0.0.3-0<br>&nbsp;* ros-indigo-interactive-world-parser: 0.0.2-0 -&gt; 0.0.3-0<br>&nbsp;* ros-indigo-interactive-world-tools: 0.0.2-0 -&gt; 0.0.3-0<br>&nbsp;* ros-indigo-jackal-control: 0.4.1-0 -&gt; 0.5.0-0<br>&nbsp;* ros-indigo-jackal-description: 0.4.1-0 -&gt; 0.5.0-0<br>&nbsp;* ros-indigo-jackal-desktop: 0.3.0-0 -&gt; 0.3.1-0<br>&nbsp;* ros-indigo-jackal-gazebo: 0.2.3-0 -&gt; 0.3.0-0<br>&nbsp;* ros-indigo-jackal-msgs: 0.4.1-0 -&gt; 0.5.0-0<br>&nbsp;* ros-indigo-jackal-navigation: 0.4.1-0 -&gt; 0.5.0-0<br>&nbsp;* ros-indigo-jackal-simulator: 0.2.3-0 -&gt; 0.3.0-0<br>&nbsp;* ros-indigo-jackal-viz: 0.3.0-0 -&gt; 0.3.1-0<br>&nbsp;* ros-indigo-jaco-description: 0.0.11-0 -&gt; 0.0.12-0<br>&nbsp;* ros-indigo-jaco-interaction: 0.0.11-0 -&gt; 0.0.12-0<br>&nbsp;* ros-indigo-jaco-sdk: 0.0.11-0 -&gt; 0.0.12-0<br>&nbsp;* ros-indigo-jaco-teleop: 0.0.11-0 -&gt; 0.0.12-0<br>&nbsp;* ros-indigo-jinteractiveworld: 0.0.2-0 -&gt; 0.0.3-0<br>&nbsp;* ros-indigo-jsk-roseus: 1.1.29-0 -&gt; 1.2.1-0<br>&nbsp;* ros-indigo-jskeus: 1.0.1-1 -&gt; 1.0.2-4<br>&nbsp;* ros-indigo-libmavconn: 0.9.4-0 -&gt; 0.10.0-0<br>&nbsp;* ros-indigo-librviz-tutorial: 0.9.0-0 -&gt; 0.9.1-0<br>&nbsp;* ros-indigo-lms1xx: 0.1.1-0 -&gt; 0.1.2-0<br>&nbsp;* ros-indigo-master-discovery-fkie: 0.3.16-0 -&gt; 0.3.17-0<br>&nbsp;* ros-indigo-master-sync-fkie: 0.3.16-0 -&gt; 0.3.17-0<br>&nbsp;* ros-indigo-mavlink: 2014.12.12-1 -&gt; 2015.1.21-1<br>&nbsp;* ros-indigo-mavros: 0.9.4-0 -&gt; 0.10.0-0<br>&nbsp;* ros-indigo-mavros-extras: 0.9.4-0 -&gt; 0.10.0-0<br>&nbsp;* ros-indigo-moveit-core: 0.6.13-0 -&gt; 0.6.15-0<br>&nbsp;* ros-indigo-moveit-msgs: 0.6.0-0 -&gt; 0.6.1-0<br>&nbsp;* ros-indigo-moveit-ros: 0.6.4-0 -&gt; 0.6.5-0<br>&nbsp;* ros-indigo-moveit-ros-benchmarks: 0.6.4-0 -&gt; 0.6.5-0<br>&nbsp;* ros-indigo-moveit-ros-benchmarks-gui: 0.6.4-0 -&gt; 0.6.5-0<br>&nbsp;* ros-indigo-moveit-ros-manipulation: 0.6.4-0 -&gt; 0.6.5-0<br>&nbsp;* ros-indigo-moveit-ros-move-group: 0.6.4-0 -&gt; 0.6.5-0<br>&nbsp;* ros-indigo-moveit-ros-perception: 0.6.4-0 -&gt; 0.6.5-0<br>&nbsp;* ros-indigo-moveit-ros-planning: 0.6.4-0 -&gt; 0.6.5-0<br>&nbsp;* ros-indigo-moveit-ros-planning-interface: 0.6.4-0 -&gt; 0.6.5-0<br>&nbsp;* ros-indigo-moveit-ros-robot-interaction: 0.6.4-0 -&gt; 0.6.5-0<br>&nbsp;* ros-indigo-moveit-ros-visualization: 0.6.4-0 -&gt; 0.6.5-0<br>&nbsp;* ros-indigo-moveit-ros-warehouse: 0.6.4-0 -&gt; 0.6.5-0<br>&nbsp;* ros-indigo-moveit-visual-tools: 2.1.0-0 -&gt; 2.2.0-0<br>&nbsp;* ros-indigo-multimaster-fkie: 0.3.16-0 -&gt; 0.3.17-0<br>&nbsp;* ros-indigo-multimaster-msgs-fkie: 0.3.16-0 -&gt; 0.3.17-0<br>&nbsp;* ros-indigo-naoqi-driver: 0.4.3-1 -&gt; 0.4.4-0<br>&nbsp;* ros-indigo-naoqi-msgs: 0.4.3-1 -&gt; 0.4.4-0<br>&nbsp;* ros-indigo-naoqi-sensors: 0.4.3-1 -&gt; 0.4.4-0<br>&nbsp;* ros-indigo-node-manager-fkie: 0.3.16-0 -&gt; 0.3.17-0<br>&nbsp;* ros-indigo-ntpd-driver: 1.0.1-0 -&gt; 1.0.2-0<br>&nbsp;* ros-indigo-object-recognition-core: 0.6.3-0 -&gt; 0.6.4-0<br>&nbsp;* ros-indigo-ompl-visual-tools: 2.2.0-0 -&gt; 2.2.1-0<br>&nbsp;* ros-indigo-openni2-launch: 0.2.1-0 -&gt; 0.2.2-0<br>&nbsp;* ros-indigo-openrtm-aist: 1.1.0-24 -&gt; 1.1.0-25<br>&nbsp;* ros-indigo-openrtm-aist-python: 1.1.0-5 -&gt; 1.1.0-6<br>&nbsp;* ros-indigo-pano-core: 2.3.1-0 -&gt; 2.3.2-0<br>&nbsp;* ros-indigo-pano-py: 2.3.1-0 -&gt; 2.3.2-0<br>&nbsp;* ros-indigo-pano-ros: 2.3.1-0 -&gt; 2.3.2-0<br>&nbsp;* ros-indigo-pcl-ros: 1.2.2-0 -&gt; 1.2.5-0<br>&nbsp;* ros-indigo-perception-pcl: 1.2.2-0 -&gt; 1.2.5-0<br>&nbsp;* ros-indigo-pointcloud-to-laserscan: 1.2.2-0 -&gt; 1.2.5-0<br>&nbsp;* ros-indigo-rail-collada-models: 0.0.1-0 -&gt; 0.0.2-0<br>&nbsp;* ros-indigo-robot-upstart: 0.0.6-1 -&gt; 0.1.1-0<br>&nbsp;* ros-indigo-roboteq-diagnostics: 0.1.1-0 -&gt; 0.1.2-0<br>&nbsp;* ros-indigo-roboteq-driver: 0.1.1-0 -&gt; 0.1.2-0<br>&nbsp;* ros-indigo-roboteq-msgs: 0.1.1-0 -&gt; 0.1.2-0<br>&nbsp;* ros-indigo-rocon-app-manager: 0.7.4-0 -&gt; 0.7.6-0<br>&nbsp;* ros-indigo-rocon-app-platform: 0.7.4-0 -&gt; 0.7.6-0<br>&nbsp;* ros-indigo-rocon-app-utilities: 0.7.4-0 -&gt; 0.7.6-0<br>&nbsp;* ros-indigo-rocon-apps: 0.7.4-0 -&gt; 0.7.6-0<br>&nbsp;* ros-indigo-rocon-bubble-icons: 0.1.11-0 -&gt; 0.1.13-0<br>&nbsp;* ros-indigo-rocon-console: 0.1.11-0 -&gt; 0.1.13-0<br>&nbsp;* ros-indigo-rocon-ebnf: 0.1.11-0 -&gt; 0.1.13-0<br>&nbsp;* ros-indigo-rocon-icons: 0.1.11-0 -&gt; 0.1.13-0<br>&nbsp;* ros-indigo-rocon-interactions: 0.1.11-0 -&gt; 0.1.13-0<br>&nbsp;* ros-indigo-rocon-launch: 0.1.11-0 -&gt; 0.1.13-0<br>&nbsp;* ros-indigo-rocon-master-info: 0.1.11-0 -&gt; 0.1.13-0<br>&nbsp;* ros-indigo-rocon-python-comms: 0.1.11-0 -&gt; 0.1.13-0<br>&nbsp;* ros-indigo-rocon-python-redis: 0.1.11-0 -&gt; 0.1.13-0<br>&nbsp;* ros-indigo-rocon-python-utils: 0.1.11-0 -&gt; 0.1.13-0<br>&nbsp;* ros-indigo-rocon-python-wifi: 0.1.11-0 -&gt; 0.1.13-0<br>&nbsp;* ros-indigo-rocon-semantic-version: 0.1.11-0 -&gt; 0.1.13-0<br>&nbsp;* ros-indigo-rocon-tools: 0.1.11-0 -&gt; 0.1.13-0<br>&nbsp;* ros-indigo-rocon-uri: 0.1.11-0 -&gt; 0.1.13-0<br>&nbsp;* ros-indigo-ros-ethernet-rmp: 0.0.6-0 -&gt; 0.0.7-0<br>&nbsp;* ros-indigo-rosapi: 0.7.7-0 -&gt; 0.7.8-0<br>&nbsp;* ros-indigo-rosbridge-library: 0.7.7-0 -&gt; 0.7.8-0<br>&nbsp;* ros-indigo-rosbridge-server: 0.7.7-0 -&gt; 0.7.8-0<br>&nbsp;* ros-indigo-rosbridge-suite: 0.7.7-0 -&gt; 0.7.8-0<br>&nbsp;* ros-indigo-roseus: 1.1.29-0 -&gt; 1.2.1-0<br>&nbsp;* ros-indigo-roseus-smach: 1.1.29-0 -&gt; 1.2.1-0<br>&nbsp;* ros-indigo-rviz-plugin-tutorials: 0.9.0-0 -&gt; 0.9.1-0<br>&nbsp;* ros-indigo-rviz-python-tutorial: 0.9.0-0 -&gt; 0.9.1-0<br>&nbsp;* ros-indigo-rviz-visual-tools: 1.4.0-0 -&gt; 1.5.0-0<br>&nbsp;* ros-indigo-self-test: 1.8.6-0 -&gt; 1.8.7-0<br>&nbsp;* ros-indigo-sick-tim: 0.0.2-0 -&gt; 0.0.3-0<br>&nbsp;* ros-indigo-stage-ros: 1.7.2-0 -&gt; 1.7.3-0<br>&nbsp;* ros-indigo-test-diagnostic-aggregator: 1.8.6-0 -&gt; 1.8.7-0<br>&nbsp;* ros-indigo-turtlebot: 2.3.4-0 -&gt; 2.3.5-0<br>&nbsp;* ros-indigo-turtlebot-actions: 2.3.1-0 -&gt; 2.3.2-0<br>&nbsp;* ros-indigo-turtlebot-apps: 2.3.1-0 -&gt; 2.3.2-0<br>&nbsp;* ros-indigo-turtlebot-bringup: 2.3.4-0 -&gt; 2.3.5-0<br>&nbsp;* ros-indigo-turtlebot-calibration: 2.3.1-0 -&gt; 2.3.2-0<br>&nbsp;* ros-indigo-turtlebot-capabilities: 2.3.4-0 -&gt; 2.3.5-0<br>&nbsp;* ros-indigo-turtlebot-description: 2.3.4-0 -&gt; 2.3.5-0<br>&nbsp;* ros-indigo-turtlebot-follower: 2.3.1-0 -&gt; 2.3.2-0<br>&nbsp;* ros-indigo-turtlebot-navigation: 2.3.1-0 -&gt; 2.3.2-0<br>&nbsp;* ros-indigo-turtlebot-panorama: 2.3.1-0 -&gt; 2.3.2-0<br>&nbsp;* ros-indigo-turtlebot-rapps: 2.3.1-0 -&gt; 2.3.2-0<br>&nbsp;* ros-indigo-turtlebot-teleop: 2.3.4-0 -&gt; 2.3.5-0<br>&nbsp;* ros-indigo-um6: 1.0.0-0 -&gt; 1.1.1-0<br>&nbsp;* ros-indigo-usb-cam: 0.1.13-0 -&gt; 0.3.0-0<br>&nbsp;* ros-indigo-visualization-marker-tutorials: 0.9.0-0 -&gt; 0.9.1-0<br>&nbsp;* ros-indigo-visualization-tutorials: 0.9.0-0 -&gt; 0.9.1-0<br>&nbsp;* ros-indigo-wpi-jaco: 0.0.11-0 -&gt; 0.0.12-0<br>&nbsp;* ros-indigo-wpi-jaco-msgs: 0.0.11-0 -&gt; 0.0.12-0<br>&nbsp;* ros-indigo-wpi-jaco-wrapper: 0.0.11-0 -&gt; 0.0.12-0<br>&nbsp;* ros-indigo-xacro: 1.9.2-0 -&gt; 1.9.3-0<br><br><br>Removed Packages [0]:<br><br><br>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:<br>&nbsp;* Alexander Tiderko<br>&nbsp;* Alwin Heerklotz<br>&nbsp;* Anqi Xu<br>&nbsp;* Austin Hendrix<br>&nbsp;* Brice Rebsamen<br>&nbsp;* Daniel Stonier<br>&nbsp;* Dave Coleman<br>&nbsp;* David Kent<br>&nbsp;* Devon Ash<br>&nbsp;* Florian Weisshardt<br>&nbsp;* Ga&euml;l Ecorchard<br>&nbsp;* HJMeijdam<br>&nbsp;* Ioan Sucan<br>&nbsp;* Jihoon Lee<br>&nbsp;* Jorge Santos<br>&nbsp;* Kei Okada<br>&nbsp;* Martin G&uuml;nther<br>&nbsp;* Melonee Wise<br>&nbsp;* Michael Ferguson<br>&nbsp;* Mikael Arguedas<br>&nbsp;* Mike Purvis<br>&nbsp;* Mitchell Wills<br>&nbsp;* Morgan Quigley<br>&nbsp;* MoveIt Setup Assistant<br>&nbsp;* Murilo F. M.<br>&nbsp;* OCL Development Team<br>&nbsp;* OSRF<br>&nbsp;* Orocos Developers<br>&nbsp;* Orocos Developers Team<br>&nbsp;* Orocos Development Team<br>&nbsp;* Paul Bovbel<br>&nbsp;* RTT Developers<br>&nbsp;* Ruben Smits<br>&nbsp;* Russell Toris<br>&nbsp;* Ryan Gariepy<br>&nbsp;* Sachin Chitta<br>&nbsp;* Severin Lemaignan<br>&nbsp;* S&eacute;verin Lemaignan<br>&nbsp;* Vincent Rabaud<br>&nbsp;* Vladimir Ermakov<br>&nbsp;* William Woodall<br>&nbsp;* Yan Ma<br>&nbsp;* ruben smits<br><br>
</div></div></div>
</div></div>
Matteo Munaro | 23 Jan 12:04 2015
Picon

Introducing OpenPTrack - developers needed

Dear ROS users,

I would like to introduce OpenPTrack, an open source project for real time people tracking in RGB-D camera networks targeted towards applications in education, art, and culture (e.g. the Whorl installation, LASHP Welcome Center prototype, and this education research project.)

OpenPTrack is a joint effort of UCLA REMAP and Open Perception. Key collaborators include the University of PadovaElectroland and Indiana University Bloomington.

It consists of a collection of ROS packages whose main features are:
  • user-friendly network calibration
  • person detection from RGB/infrared/depth images
  • efficient multi-person tracking
  • UDP and NDN streaming of tracking data in JSON format
It currently supports networks of Kinect v1, SwissRanger SR4500 and stereo cameras custom-built with PointGrey cameras. Support for Kinect v2 will be added soon.

We have three  deployed multi-imager testbeds at the UCLA Lab School, UCLA Interpretive Media Laboratory, and University of Indiana, and will add a fourth this month. 

We are currently looking for developers interested in creating easy to use front-end interfaces for OpenPTrack, thus fully automating all of the steps of designing the camera network and setting up, configuring, calibrating, operating, and debugging the system.

* Required Skills: *
- Experience with C++.
- Experience with Robot Operating System (ROS).
 
* Nice To Have: *
- Experience developing web interfaces.
- Experience with ROS tools for developing web interfaces.
- Experience with OpenCV and PCL.
- Knowledge of people tracking algorithms.
- Knowledge of camera calibration algorithms.

In February, we are planning to launch a pilot crowdfunding campaign to help support getting OpenPTrack in the hands of more potential users, and would love to get these additional developers aboard by that time. 

For applications and any enquiries, please send an email to Jeff Burke (jburke <at> remap.ucla.edu) or Matteo Munaro (munaro-2/3W1wIP1CU+9D430DZnzg@public.gmane.org).

Best regards,
Matteo


References:
M. Munaro, A. Horn, R. Illum, J. Burke and R. B. Rusu. OpenPTrack: People Tracking for Heterogeneous Networks of Color-Depth Cameras. In IAS-13 Workshop Proceedings: 1st Intl. Workshop on 3D Robot Perception with Point Cloud Library, pp. 235-247, Padova, Italy, 2014 (paper|presentation).

___________________________________________

Matteo MUNARO, Ph.D.

Intelligent and Autonomous Systems Lab (IAS-Lab)
Department of Information Engineering (DEI)
Faculty of Engineering, The University of Padua
Via Ognissanti 72, I-35131 Padova, Italy

email: munaro-2/3W1wIP1CU+9D430DZnzg@public.gmane.org
phone: +390498277831
___________________________________________
<div><div dir="ltr">Dear ROS users,<br><span><div>
<div class="ecxhmmessage">
<div dir="ltr">
<br>
I would like to introduce <a href="http://openptrack.org/" target="_blank">OpenPTrack</a>,
 an open source project for real time people tracking in RGB-D camera 
networks targeted towards applications in education, art, and culture 
(e.g. the&nbsp;<a href="http://vimeo.com/109849929" target="_blank">Whorl</a>&nbsp;installation,
<a href="http://vimeo.com/114824779" target="_blank">LASHP Welcome Center</a>&nbsp;prototype, and <a href="http://ampersand.gseis.ucla.edu/noel-enyedy-motion-tracking-technology-enhances-k-12-learning/" target="_blank">
this</a> education research project.)</div>
</div>
</div>
</span><span>
<div class="ecxhmmessage">
<div dir="ltr">
<br>
OpenPTrack is a joint effort of <a href="http://remap.ucla.edu/" target="_blank">UCLA REMAP</a>&nbsp;and
<a href="http://www.openperception.org/" target="_blank">Open Perception</a>. Key collaborators include the
<a href="http://www.unipd.it/en/" target="_blank">University of Padova</a>,&nbsp;<a href="http://electroland.net" target="_blank">Electroland</a>&nbsp;and&nbsp;<a href="http://www.iub.edu/" target="_blank">Indiana University Bloomington</a>.
<br><br>
It consists of a collection of ROS packages whose main features are:<br><ul>
<li>user-friendly network calibration</li>
<li>person&nbsp;detection from RGB/infrared/depth images</li>
<li>efficient multi-person&nbsp;tracking</li>
<li>UDP&nbsp;and <a href="http://named-data.net/" target="_blank">NDN</a> streaming of tracking data in JSON format</li>
</ul>
</div>
</div>
</span><span>
<div>
<div class="ecxhmmessage">
<div dir="ltr">It currently supports networks of Kinect v1, SwissRanger SR4500 and
stereo cameras custom-built with PointGrey cameras. Support for Kinect v2 will be added soon.</div>
</div>
</div>
</span>
<div><br></div>
<div>We have three &nbsp;deployed&nbsp;multi-imager testbeds at the UCLA Lab School, UCLA Interpretive Media Laboratory, and University of Indiana, and will add a fourth this month.&nbsp;</div>
<span>
<div>
<div class="ecxhmmessage">
<div dir="ltr">
<br>
We are currently looking for developers interested in creating 
easy to use front-end interfaces for OpenPTrack, thus fully automating 
all of the steps of designing the camera network and setting up, 
configuring, calibrating, operating, and debugging
 the system.<br><br>
* Required Skills: *<br>
- Experience with C++.<br>
- Experience with Robot Operating System (ROS).<br>
&nbsp;<br>
* Nice To Have: *<br>
- Experience developing web interfaces.<br>
- Experience with ROS tools for developing web interfaces.<br>- Experience with OpenCV and PCL.<br>
- Knowledge of people tracking algorithms.<br>
- Knowledge of camera calibration algorithms.</div>
</div>
</div>
</span>
<div><br></div>
<span>
<div class="ecxhmmessage">
<div dir="ltr">In February, we are planning to launch a pilot 
crowdfunding campaign to help support getting OpenPTrack in the hands of
 more potential users, and would love to get these additional developers
 aboard by that time.&nbsp;</div>
</div>
</span>
<div><br></div>
<span>
<div>
<div class="ecxhmmessage">
<div dir="ltr">For applications and any enquiries, please send an email to Jeff Burke (<span><a href="mailto:jburke@...">jburke <at> remap.ucla.edu</a>) or Matteo Munaro (<a href="mailto:munaro@...">munaro@...</a>).</span>
</div>
</div>
</div>
</span>
<div><br></div>
<span>
<div>
<div class="ecxhmmessage">
<div dir="ltr">Best regards,<br>
Matteo<br><br><br>References:<br>
M. Munaro, A. Horn, R. Illum, J. Burke and R. B. Rusu. OpenPTrack: 
People Tracking for Heterogeneous Networks of Color-Depth Cameras. In 
IAS-13 Workshop Proceedings: 1st Intl. Workshop on 3D Robot Perception 
with Point Cloud Library, pp. 235-247, Padova, Italy,
 2014 (<a href="http://www.dei.unipd.it/%7Emunaro/media/Munaro_3DRP2014.pdf" target="_blank">paper</a>|<a href="http://www.pointclouds.org/assets/uploads/3DRP-PCL14_Munaro.pdf" target="_blank">presentation</a>).
<br>
</div>
</div>
</div></span><br><div>___________________________________________</div>
<div><br></div>
<div>Matteo MUNARO, Ph.D.</div>
<div><br></div>
<div>Intelligent and Autonomous Systems Lab (IAS-Lab)</div>
<div>Department of Information Engineering (DEI)</div>
<div>Faculty of Engineering, The University of Padua</div>
<div>Via Ognissanti 72, I-35131 Padova, Italy</div>
<div><br></div>
<div>email: munaro@...</div>
<div>phone: +390498277831</div>
<div><div>___________________________________________</div></div> 		 	   		  </div></div>
Duy Huynh | 22 Jan 01:11 2015
Picon

NEW ROS ROBOT DEVELOPMENT KIT

Hi eveyrone!  A year ago, we began to play with Turtlebot 2 & ROS, and we love it!  Over the last 12 months, we've added a lot of hardware and software components on top of it.  

We would love to share what we've built with the ROS community.  And if you're interested in getting the same unit for your own development or research, we're selling it on Kickstarter now.  


Pick the Research Edition ($1,495)


Hardware specs:
  • Kobuki Mobile Base
  • 3D Depth Camera
  • Qualcomm IFC6410 Development Board or Better 
  • 9" Screen or Larger
  • Servos
  • Microphone
  • Speaker
  • Humidity Sensor, Temperature Sensor, CO2 Meter
If you're doing research in the Internet of Things & Connected Devices space, this Research Robot is perfect for you.  It can interface with almost all the connected devices on the market already.  We have built it as a Smart Home Automation System as well.  It has:
  • Wireless Z-Wave Plus
  • Zigbee
  • BLE
  • Wi-Fi
We'll also release our AI SDK, including:
  • Facial Recognition
  • Object Recognition
  • Speech Recognition
  • Natural Language Processing
  • And more
As well as the remote control apps for the robot, so that you can control the robots from your phone locally or remotely.
  • Android
  • iOS
Of course, we'll pre-install ROS and Ubuntu on the robot.

Any question / comment / advice / feedback is much appreciated.  


Thanks!
Duy

Robotbase
<div><div dir="ltr">
<div>Hi eveyrone!&nbsp; A year ago, we began to play with Turtlebot 2 &amp; ROS, and we love it!&nbsp; Over the last 12 months, we've added a lot of hardware and software components on top of it.&nbsp;&nbsp;</div>
<div><br></div>
<div>We would love to share what we've built with the ROS community.&nbsp; And if you're interested in getting the same unit for your own development or research, we're selling it on Kickstarter now.&nbsp;&nbsp;</div>
<div><br></div>
<div>
<a href="https://www.kickstarter.com/projects/403524037/personal-robot" target="_blank">https://www.kickstarter.com/projects/403524037/personal-robot</a><br>
</div>
<div>
<div><br></div>
<div>Pick the Research Edition ($1,495)<br>
</div>
<div><br></div>
<div>Here is a <a href="https://www.youtube.com/watch?v=oBhJJKUIjCM">straightforward demo</a>.</div>
</div>
<div><br></div>
<div>Hardware specs:<br><ul>
<li>Kobuki Mobile Base<br>
</li>
<li>3D Depth Camera<br>
</li>
<li>Qualcomm IFC6410 Development Board or Better&nbsp;</li>
<li>9" Screen or Larger<br>
</li>
<li>Servos<br>
</li>
<li>Microphone<br>
</li>
<li>Speaker<br>
</li>
<li>Humidity Sensor, Temperature Sensor, CO2 Meter<br>
</li>
</ul>If you're doing research in the Internet of Things &amp; Connected Devices space, this Research Robot is perfect for you.&nbsp; It can interface with almost all the connected devices on the market already.&nbsp; We have built it as a Smart Home Automation System as well.&nbsp; It has:<br><ul>
<li>Wireless Z-Wave Plus<br>
</li>
<li>Zigbee<br>
</li>
<li>BLE<br>
</li>
<li>Wi-Fi</li>
</ul>We'll also release our AI SDK, including:<br><ul>
<li>Facial Recognition</li>
<li>Object Recognition</li>
<li>Speech Recognition</li>
<li>Natural Language Processing</li>
<li>And more<br>
</li>
</ul>
<div>As well as the remote control apps for the robot, so that you can control the robots from your phone locally or remotely.</div>
<div><ul>
<li>Android</li>
<li>iOS</li>
</ul></div>
<div>Of course, we'll pre-install ROS and Ubuntu on the robot.</div>
<div><br></div>
<div>Any question / comment / advice / feedback is much appreciated. &nbsp;</div>
<div><br></div>
<div>My email is&nbsp;<a href="mailto:duy@..." target="_blank">duy <at> robotbase.com</a>.</div>
<div><br></div>
<div>Thanks!</div>
<div>Duy</div>
<div><br></div>
<div>Robotbase</div>
<div><a href="http://www.robotbase.com">www.robotbase.com</a></div>
</div>
</div></div>
DottAntMaur Gal | 20 Jan 12:18 2015
Picon

Introducing ROS BaseCam camera stabilizer wrapper

Hi all,
I've made a ROS serial communication wrapper for the BaseCam Electronics 32bit camera stabilizer.
It helps you to get the imu data from that component and allow you to tilt pitch axis from a min to max angle.
I would like to share my work with the ROS comunity.
Thanks a lot


--
Dott. Galiano Antonio Mauro
Research grant' holder at the University of Bologna.

<div><div dir="ltr">
<div>
<div>
<div>
<div>
<div>Hi all,<br>
</div>I've made a ROS serial communication wrapper for the BaseCam Electronics 32bit camera stabilizer.<br>
</div>It helps you to get the imu data from that component and allow you to tilt pitch axis from a min to max angle.<br>
</div>I would like to share my work with the ROS comunity.<br>
</div>Thanks a lot<br><br>
</div>
<div><div><div><div><div><div>
<br>-- <br><div class="gmail_signature"><div dir="ltr">Dott. Galiano Antonio Mauro<br>Research grant' holder at the University of Bologna.<br><br>
</div></div>
</div></div></div></div></div></div>
</div></div>
Martin Peris Martorell | 20 Jan 08:47 2015
Picon

[jobs] Software Engineer position at Cyberdyne Inc. (Japan)

“Dreaming” or “Passion” is valuable, but a “Heart for Caring for Others” is much more important. If one has the heart to care for people and society, one cannot idly stand by, but will proactively think and take immediate actions for a brighter future. This is the heart of Cyberdyne and we are looking for a Software Engineer experienced in ROS to help shaping that future.

About the job

We require a software engineer with broad experience in ROS and its components: simulators, visualisation tools, navigation, sensors, actuators and others. You will have the chance to join a highly dynamic and creative group of engineers with different backgrounds and skills working on real-world robotic applications.

Your main responsibilities will be:
 - Develop and maintain ROS software packages.
 - Prototype robots in simulated environment.
 - Implement and test algorithms in both simulated and real robots.

Requirements
 - MSc in Computer Science or related field (preferible PhD)
 - ROS proficiency
 - Fluency in C/C++ (other languages are welcome)
 - Software Development experience under Linux/OS X environment
 - Hands-on experience with autonomous robots

Nice to have
 - PLC experience
 - Japanese language ability 
 - Currently residing in Japan (although we can sponsor a Visa)

If you feel you are the person we are looking for, let me know at martin_peris-Z9C1CWIyEMqKKnvmgvTJ0g@public.gmane.org, send your cover letter (max 1 page) and your CV (max 2 pages) in PDF format. And to proof that you are human (or at least a robotic life form advanced enough to understand this e-mail and fulfil the requirements of the job position) state “Hasta la vista, baby” in the subject of your e-mail.

We are looking forward to hearing from you.

Best regards.

--
Martin Peris Martorell, martin_peris-Z9C1CWIyEMqKKnvmgvTJ0g@public.gmane.org
CYBERDYNE株式会社 研究開発部
CYBERDYNE Inc., Research and Development Department
--------------------------------------------------------------------- 本電子メールが誤配信である場合には、大変お手数ではございますが、発信人宛に 電話又は電子メールにて、その旨ご連絡頂きますようにお願い申し上げます。 また、メール内容には当社の機密事項等が含まれている場合がありますので、 コピーや公開等をなさらず、本メールを削除頂きますように宜しくお願い申し上げます。 ---------------------------------------------------------------------
<div>&ldquo;Dreaming&rdquo; or &ldquo;Passion&rdquo; is valuable, but a &ldquo;Heart for Caring for Others&rdquo; is much more important. If one has the heart to care for people and society, one cannot idly stand by, but will proactively think and take immediate actions for a brighter future. This is the heart of Cyberdyne and we are looking for a Software Engineer experienced in ROS to help shaping that future.<br class=""><br class="">About the job<br class=""><br class="">We require a software engineer with broad experience in ROS and its components: simulators, visualisation tools, navigation, sensors, actuators and others. You will have the chance to join a highly dynamic and creative group of engineers with different backgrounds and skills working on real-world robotic applications.<br class=""><br class="">Your main responsibilities will be:<br class="">&nbsp;- Develop and maintain ROS software packages.<br class="">&nbsp;- Prototype robots in simulated environment.<br class="">&nbsp;- Implement and test algorithms in both simulated and real robots.<br class=""><br class="">Requirements<br class="">&nbsp;- MSc in Computer Science or related field (preferible PhD)<br class="">&nbsp;- ROS proficiency<br class="">&nbsp;- Fluency in C/C++ (other languages are welcome)<br class="">&nbsp;- Software Development experience under Linux/OS X environment<br class="">&nbsp;- Hands-on experience with autonomous robots<br class=""><br class="">Nice to have<br class="">&nbsp;- PLC experience<br class="">&nbsp;- Japanese language ability&nbsp;<br class="">&nbsp;- Currently residing in Japan (although we can sponsor a Visa)<br class=""><br class="">If you feel you are the person we are looking for, let me know at&nbsp;<a href="mailto:martin_peris@..." class="">martin_peris@...</a>, send your cover letter (max 1 page) and your CV (max 2 pages) in PDF format. And to proof that you are human (or at least a robotic life form advanced enough to understand this e-mail and fulfil the requirements of the job position) state &ldquo;Hasta la vista, baby&rdquo; in the subject of your e-mail.<br class=""><br class="">We are looking forward to hearing from you.<br class=""><br class="">Best regards.<div class=""><br class=""></div>
<div class="">--<br class="">Martin Peris Martorell, <a href="mailto:martin_peris@..." class="">martin_peris@...</a><div class="">CYBERDYNE&#26666;&#24335;&#20250;&#31038;&#12288;&#30740;&#31350;&#38283;&#30330;&#37096;</div>
</div>
<div class="">CYBERDYNE Inc., Research and Development Department</div>
<table><tr><td bgcolor="#ffffff">---------------------------------------------------------------------
&#26412;&#38651;&#23376;&#12513;&#12540;&#12523;&#12364;&#35492;&#37197;&#20449;&#12391;&#12354;&#12427;&#22580;&#21512;&#12395;&#12399;&#12289;&#22823;&#22793;&#12362;&#25163;&#25968;&#12391;&#12399;&#12372;&#12374;&#12356;&#12414;&#12377;&#12364;&#12289;&#30330;&#20449;&#20154;&#23451;&#12395;
&#38651;&#35441;&#21448;&#12399;&#38651;&#23376;&#12513;&#12540;&#12523;&#12395;&#12390;&#12289;&#12381;&#12398;&#26088;&#12372;&#36899;&#32097;&#38914;&#12365;&#12414;&#12377;&#12424;&#12358;&#12395;&#12362;&#39000;&#12356;&#30003;&#12375;&#19978;&#12370;&#12414;&#12377;&#12290;
&#12414;&#12383;&#12289;&#12513;&#12540;&#12523;&#20869;&#23481;&#12395;&#12399;&#24403;&#31038;&#12398;&#27231;&#23494;&#20107;&#38917;&#31561;&#12364;&#21547;&#12414;&#12428;&#12390;&#12356;&#12427;&#22580;&#21512;&#12364;&#12354;&#12426;&#12414;&#12377;&#12398;&#12391;&#12289;
&#12467;&#12500;&#12540;&#12420;&#20844;&#38283;&#31561;&#12434;&#12394;&#12373;&#12425;&#12378;&#12289;&#26412;&#12513;&#12540;&#12523;&#12434;&#21066;&#38500;&#38914;&#12365;&#12414;&#12377;&#12424;&#12358;&#12395;&#23452;&#12375;&#12367;&#12362;&#39000;&#12356;&#30003;&#12375;&#19978;&#12370;&#12414;&#12377;&#12290;
---------------------------------------------------------------------</td></tr></table>
</div>
Reiser, Ulrich | 18 Jan 22:08 2015
Picon

ROS-Industrial Community Meeting

Dear ros-users,

 

 

I would like to draw your attention to the upcoming ROS-Industrial Community Meeting:

 

-----------------------------------------------------------------------------------------------------------

Date: Thursday, January 29, 2015

Time: 9:00 AM - 10:30 AM (Central Time)

 

Link: http://rosindustrial.org/events/2015/1/29/ros-i-community-meeting

 

--------------------------------------------------------------------------------------------------------------

 

The community meeting consists of the following short talks and gives room for questions and discussions:

 

-          Welcome and update on RIC-Americas and EU | Paul Hvass (SwRI), Ulrich Reiser (Fraunhofer IPA)

-          Descartes Path Planner with Application to Robotic Routing | Shaun Edwards (SwRI)

-          Modelling of Realtime Communication Patterns | Arne Hamann (Bosch)

-          Amazon Picking Challenge | Dejan Pangercic (Bosch)

-          Why DDS for ROS 2.0? | Dirk Thomas (OSRF)

-          MoveIt! New Functionality and Status Update | Sachin Chitta (SRI)

 

If you are interested to join, please register on:

 

https://www.anymeeting.com/AccountManager/RegEv.aspx?PIID=EB53DC86814D3A

 

 

Best Regards,

Ulrich

 

 

 

 

<div>
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US">Dear ros-users,<p></p></span></p>
<p class="MsoNormal"><span lang="EN-US"><p>&nbsp;</p></span></p>
<p class="MsoNormal"><span lang="EN-US"><p>&nbsp;</p></span></p>
<p class="MsoNormal"><span lang="EN-US">I would like to draw your attention to the upcoming ROS-Industrial Community Meeting:<p></p></span></p>
<p class="MsoNormal"><span lang="EN-US"><p>&nbsp;</p></span></p>
<p class="MsoNormal"><span lang="EN-US">-----------------------------------------------------------------------------------------------------------<p></p></span></p>
<p class="MsoNormal"><span lang="EN-US">Date: Thursday, January 29, 2015<p></p></span></p>
<p class="MsoNormal"><span lang="EN-US">Time: 9:00 AM - 10:30 AM (Central Time)<p></p></span></p>
<p class="MsoNormal"><span lang="EN-US"><p>&nbsp;</p></span></p>
<p class="MsoNormal"><span lang="EN-US">Link: </span><a href="http://rosindustrial.org/events/2015/1/29/ros-i-community-meeting"><span lang="EN-US">http://rosindustrial.org/events/2015/1/29/ros-i-community-meeting</span></a><span lang="EN-US"><p></p></span></p>
<p class="MsoNormal"><span lang="EN-US"><p>&nbsp;</p></span></p>
<p class="MsoNormal"><span lang="EN-US">--------------------------------------------------------------------------------------------------------------<p></p></span></p>
<p class="MsoNormal"><span lang="EN-US"><p>&nbsp;</p></span></p>
<p class="MsoNormal"><span lang="EN-US">The community meeting consists of the following short talks and gives room for questions and discussions:<p></p></span></p>
<p class="MsoNormal"><span lang="EN-US"><p>&nbsp;</p></span></p>
<p class="MsoListParagraph"><span lang="EN-US"><span>-<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><span lang="EN-US">Welcome and update on RIC-Americas and EU | Paul Hvass (SwRI), Ulrich Reiser (Fraunhofer IPA)<p></p></span></p>
<p class="MsoListParagraph"><span lang="EN-US"><span>-<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><span lang="EN-US">Descartes Path Planner with Application to Robotic Routing | Shaun Edwards (SwRI)<p></p></span></p>
<p class="MsoListParagraph"><span lang="EN-US"><span>-<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><span lang="EN-US">Modelling of Realtime Communication Patterns | Arne Hamann (Bosch)<p></p></span></p>
<p class="MsoListParagraph"><span lang="EN-US"><span>-<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><span lang="EN-US">Amazon Picking Challenge | Dejan Pangercic (Bosch)<p></p></span></p>
<p class="MsoListParagraph"><span lang="EN-US"><span>-<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><span lang="EN-US">Why DDS for ROS 2.0? | Dirk Thomas (OSRF)<p></p></span></p>
<p class="MsoListParagraph"><span lang="EN-US"><span>-<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><span lang="EN-US">MoveIt! New Functionality and Status Update | Sachin Chitta (SRI)<p></p></span></p>
<p class="MsoNormal"><span lang="EN-US"><p>&nbsp;</p></span></p>
<p class="MsoNormal"><span lang="EN-US">If you are interested to join, please register on:<p></p></span></p>
<p class="MsoNormal"><span lang="EN-US"><p>&nbsp;</p></span></p>
<p class="MsoNormal"><a href="https://www.anymeeting.com/AccountManager/RegEv.aspx?PIID=EB53DC86814D3A"><span lang="EN-US">https://www.anymeeting.com/AccountManager/RegEv.aspx?PIID=EB53DC86814D3A</span></a><span lang="EN-US"><p></p></span></p>
<p class="MsoNormal"><span lang="EN-US"><p>&nbsp;</p></span></p>
<p class="MsoNormal"><span lang="EN-US"><p>&nbsp;</p></span></p>
<p class="MsoNormal"><span lang="EN-US">Best Regards,<p></p></span></p>
<p class="MsoNormal"><span lang="EN-US">Ulrich<p></p></span></p>
<p class="MsoNormal"><span lang="EN-US"><p>&nbsp;</p></span></p>
<p class="MsoNormal"><span lang="EN-US"><p>&nbsp;</p></span></p>
<p class="MsoNormal"><span lang="EN-US"><p>&nbsp;</p></span></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
</div>
</div>
Anis Koubaa (COINS | 17 Jan 11:41 2015

Springer Book on ROS - Deadline Extension

I have received a couple of requests for extending the submission due date of chapters for the Springer Book on Robot Operating System due to conflict with IROS 2015 submission due date. As such,  the full chapter submission deadline is postponed with three weeks to avoid any overlap. The new submission due date is March 21, 2015.
I have also extended the abstract submission to Jan 31, 2015 (hard and final) to allow for more submissions since the full chapter submission deadline is extended.

The call for chapters is available on this page
http://events.coins-lab.org/springer/springer_ros_book.html 

We are looking for possible reviewers of the submitted book chapters. If you have interest to join the technical reviewers broad, please provide your information in this Google Form
https://docs.google.com/forms/d/11jTIXw8FnKyTIWr_GxKtZ4p3QSaRi-3LiBFfzdx0Ulo/viewform
Once your register, you will receive later an official reviewer invitation through EasyChair that you need to accept to join.

If you have any question, let me know.

Thank you
Anis
<div>
<div>
<span>I have received a couple of requests for extending the submission due date of chapters for the Springer Book on Robot Operating System due to conflict with IROS 2015 submission due date. As such,&nbsp; the full chapter submission deadline is postponed with three weeks to avoid any overlap. The new submission due date is March 21, 2015.</span><br><span>I have also extended the abstract submission to Jan 31, 2015 (hard&nbsp;and final) to allow for more submissions since the full chapter submission deadline is extended.</span>
</div>
<div><span><br></span></div>
<div><span>The call for chapters is available on this page</span></div>
<div>
<a href="http://events.coins-lab.org/springer/springer_ros_book.html">http://events.coins-lab.org/springer/springer_ros_book.html</a>&nbsp;<span><br></span><br><span>We are looking for possible reviewers of the submitted book chapters. If you have interest to join the technical reviewers broad, please provide your information in this Google Form</span><br><a href="https://docs.google.com/forms/d/11jTIXw8FnKyTIWr_GxKtZ4p3QSaRi-3LiBFfzdx0Ulo/viewform" target="_blank">https://docs.google.com/forms/d/11jTIXw8FnKyTIWr_GxKtZ4p3QSaRi-3LiBFfzdx0Ulo/viewform</a><br><span>Once your register, you will receive later an official reviewer invitation through EasyChair that you need to accept to join.</span><br><br><span>If you have any question, let me know.</span><br><br><span>Thank you</span><br><span>Anis</span>
</div>
</div>
Weißhardt, Florian | 16 Jan 13:41 2015
Picon

New modular Care-O-bot generation released: Care-O-bot 4

Dear ros-users,

 

We’ve finished the new modular service robot generation of Care-O-bot - Care-O-bot 4.

 

In comparison to its predecessors, Care-O-bot 4 stands out in its modular design, extraordinary agility and multi-modal  interactivity. The five independent modules - mobile base, torso, arms, sensor ring, head – are easily plugged through standard connectors.  Care-O-bot can be thus be individually configured depending on the intended application: you can use the compact omnidirectional mobile base alone as a compact transportation device for payloads up to 150 kg. Equip the robot with one arm for simple manipulation tasks or with two arms for bimanual manipulation. If your application requires a large workspace of the arms, a spherical joint can be integrated that allows the torso to roll, pitch and yaw. This can be particularly helpful for picking objects from a shelf at different levels. A camera in the one fingered gripper enables object detection even in regions that are not covered by the cameras in the sensor ring or in the torso. Equip the Care-O-bot with a second spherical joint between torso and head if you need a large sensor coverage. Or if you want to move the touch screen integrated in the robot’s head to a comfortable position for the individual user.

 

Discover all configuration options and all special features on the Care-O-bot website:

 

www.care-o-bot.de.

 

Watch Care-O-bot 4 as a gentleman at http://youtu.be/3n42WbbYGZI.

 

Like for Care-O-bot 3, open source ROS drivers and simulation models are provided for all modules (see http://wiki.ros.org/care-o-bot). We intend to make it available as research platform for service robotics soon.  A the same time we envision to build a platform to create individual service robot solutions for commercial applications.

 

We are always looking for partners to advance the state-of-the art in service robotics and enlarge the ROS-based Care-O-bot community. Additionally to that we’re searching for skilled ROS developers and have various open positions, see previous post at http://lists.ros.org/pipermail/ros-users/2014-October/069034.html.

 

Please let us know if you are interested to get more information on Care-O-bot 4. We are looking forward to any feedback!

 

Best Regards,

Florian

---
Dipl.-Ing.
Florian Weißhardt

Fraunhofer IPA, Abt. 320/Roboter- und Assistenzsysteme
Nobelstrasse 12, D-70569 Stuttgart (Germany)
Phone +49(0)711-970-1046,
Fax +49(0)711-970-1008
http://www.ipa.fraunhofer.de/

 

<div>
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US">Dear ros-users,<p></p></span></p>
<p class="MsoNormal"><span lang="EN-US"><p>&nbsp;</p></span></p>
<p class="MsoNormal"><span lang="EN-US">We&rsquo;ve finished the new modular service robot generation of Care-O-bot - Care-O-bot 4.<p></p></span></p>
<p class="MsoNormal"><span lang="EN-US"><p>&nbsp;</p></span></p>
<p class="MsoNormal"><span lang="EN-US">In comparison to its predecessors, Care-O-bot 4 stands out in its modular design, extraordinary agility and multi-modal &nbsp;interactivity. The five independent modules - mobile base, torso, arms, sensor ring, head &ndash; are
 easily plugged through standard connectors. &nbsp;Care-O-bot can be thus be individually configured depending on the intended application: you can use the compact omnidirectional mobile base alone as a compact transportation device for payloads up to 150 kg. Equip
 the robot with one arm for simple manipulation tasks or with two arms for bimanual manipulation. If your application requires a large workspace of the arms, a spherical joint can be integrated that allows the torso to roll, pitch and yaw. This can be particularly
 helpful for picking objects from a shelf at different levels. A camera in the one fingered gripper enables object detection even in regions that are not covered by the cameras in the sensor ring or in the torso. Equip the Care-O-bot with a second spherical
 joint between torso and head if you need a large sensor coverage. Or if you want to move the touch screen integrated in the robot&rsquo;s head to a comfortable position for the individual user.<p></p></span></p>
<p class="MsoNormal"><span lang="EN-US"><p>&nbsp;</p></span></p>
<p class="MsoNormal"><span lang="EN-US">Discover all configuration options and all special features on the Care-O-bot website:<p></p></span></p>
<p class="MsoNormal"><span lang="EN-US"><p>&nbsp;</p></span></p>
<p class="MsoNormal"><span lang="EN-US"><a href="http://www.care-o-bot.de">www.care-o-bot.de</a>.
<p></p></span></p>
<p class="MsoNormal"><span lang="EN-US"><p>&nbsp;</p></span></p>
<p class="MsoNormal"><span lang="EN-US">Watch Care-O-bot 4 as a gentleman at <a href="http://youtu.be/3n42WbbYGZI">
http://youtu.be/3n42WbbYGZI</a>. <p></p></span></p>
<p class="MsoNormal"><span lang="EN-US"><p>&nbsp;</p></span></p>
<p class="MsoNormal"><span lang="EN-US">Like for Care-O-bot 3, open source ROS drivers and simulation models are provided for all modules (see
<a href="http://wiki.ros.org/care-o-bot">http://wiki.ros.org/care-o-bot</a>). We intend to make it available as research platform for service robotics soon. &nbsp;A the same time we envision to build a platform to create individual service robot solutions for commercial
 applications.<p></p></span></p>
<p class="MsoNormal"><span lang="EN-US"><p>&nbsp;</p></span></p>
<p class="MsoNormal"><span lang="EN-US">We are always looking for partners to advance the state-of-the art in service robotics and enlarge the ROS-based Care-O-bot community. Additionally to that we&rsquo;re searching for skilled ROS developers and have various open
 positions, see previous post at <a href="http://lists.ros.org/pipermail/ros-users/2014-October/069034.html">
http://lists.ros.org/pipermail/ros-users/2014-October/069034.html</a>. <p></p></span></p>
<p class="MsoNormal"><span lang="EN-US"><p>&nbsp;</p></span></p>
<p class="MsoNormal"><span lang="EN-US">Please let us know if you are interested to get more information on Care-O-bot 4. We are looking forward to any feedback!<p></p></span></p>
<p class="MsoNormal"><span lang="EN-US"><p>&nbsp;</p></span></p>
<p class="MsoNormal"><span lang="EN-US">Best Regards,<p></p></span></p>
<p class="MsoNormal"><span lang="EN-US">Florian<p></p></span></p>
<p class="MsoNormal"><span lang="EN-US">---<br>
Dipl.-Ing. </span><span>Florian Wei&szlig;hardt<p></p></span></p>
<p class="MsoNormal"><span>Fraunhofer IPA, Abt. 320/Roboter- und Assistenzsysteme<br>
Nobelstrasse 12, D-70569 Stuttgart (Germany)<br>
Phone +49(0)711-970-1046,<br>
Fax +49(0)711-970-1008<br></span><span><a href="http://www.ipa.fraunhofer.de/" title="http://www.ipa.fraunhofer.de/"><span>http://www.ipa.fraunhofer.de/</span></a><p></p></span></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
</div>
</div>
Picon

some thoughts about nodelet

Hello everyone:

I have some thoughts about nodelet:
1. Would it be useful to develop a real-time nodelet? &
2. Is it possible to do this based on OROCOS, or at least use the tec of OROCOS(like lock-free data struct) for reference?

Thanks.
sukha19880831-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
<div>
<div>
<span></span><div>Hello everyone:</div>
<div><br></div>
<div>I have some thoughts about nodelet:</div>
<div>1. Would it be useful to develop a real-time nodelet? &amp;</div>
<div>2. Is it possible to do this based on OROCOS, or at least use the tec of OROCOS(like lock-free data struct) for reference?</div>
</div>
<div><br></div>
<div>Thanks.</div>
<div><span><div><div>sukha19880831@...</div></div></span></div>
</div>

Gmane