May 2014 Archives

These are recent job postings collected from ros-users@. Below are advertisements of openings from Vecna, hiDOF, UT Austin Nuclear and Applied Robotics Group, and BZ Robot

Robotics research internships/co-op positions at Vecna Robotics

Vecna Robotics has openings for several intern and Co-op positions in manipulation, controls, vision, and task planning as described below.


* Manipulation and Controls Intern/Co-op *

We are looking for an intern or co-op to work on a project developing (multi-sensor) kinematic/dynamic parameter estimation techniques for robotic arms.

Desired Qualifications:
 - Currently pursuing MS/PhD in Computer Science, Electrical Engineering, Mechanical Engineering, or equivalent engineering field with a focus on robotics
 - Working understanding of robot kinematics and dynamics
 - Experience in control and optimization
 - Proficient in Python and C/C++ development
 - Proficient in a Linux environment
 - Experience with ROS/MoveIt!
 - Experience with computer vision is a plus
 - Experience with real world robotic arms is a plus


* Task planning Intern/Co-op *

We are looking for an intern or co-op to work on a project developing task planning and scheduling techniques for coordinating teams of autonomous robots.

Desired Qualifications:
  - Currently pursuing MS/PhD in Computer Science or engineering field with a focus on robotics
  - Experience with task planning and scheduling algorithms
  - Strong programming skills in C/C++ and Java
  - Proficient in a Linux environment
  - Experience with ROS
  - Experience with real robots is a plus


* Computer Vision Intern/Co-op *

We are looking for an intern or co-op to work on computer vision techniques for robot navigation and obstacle avoidance.

Desired Qualifications:
 - Currently pursuing PhD in Computer Science, Electrical Engineering, Mechanical Engineering, or equivalent engineering field with a focus on robotics
 - Strong background in computer vision, image processing, and related fields
 - Hands-on experience in computer vision especially in 3D reconstruction, camera pose estimation, 2D and 3D tracking, and object recognition
 - Proficient with C/C++ and computer vision libraries (OpenCV)
 - Proficient in a Linux environment
 - Experience with ROS
 - Preferably have experience in research projects that published in top venues (ICCV/CVPR/ECCV/ISMAR/VR, etc)
 - Preferably have experience in real-time computer vision systems


Interested candidates should apply online at http://www.vecna.com/careers?m_id=1017605 to the "Robotics Graduate Student Internship/Co-op" job opening. Please indicate for which project you would like to be considered.

Please do not reply to me directly, I cannot respond to individual requests. General questions can be sent torecruiting@vecna.com.



Software Engineering Positions at hiDOF

About hiDOF:
hiDOF was founded by former Willow Garage engineers and seeks to solve challenging problems in robotics, 3D computer vision, sensor processing, motion control, and motion planning spaces. We've worked on everything from giant industrial robots, to autonomous vehicles, to 3D SLAM on mobile platforms, to medical image processing, to visualizing and processing large 3D point clouds.  Google's Project Tango and SSS Manufacturing are great examples of this.

We focus on technology transfer applications, leveraging our academic ties and strong software engineering fundamentals. We are roboticists that possess the programming chops, tools, and infrastructure to take technologies explored in research applications to hardened, deployed products.

Job Description:
At hiDOF, we're looking to add talented individuals to our team. If you're looking to join a small team of passionate engineers, looking for a fun, engaging, and technically challenging environment, hiDOF is the place for you. On our side, we look for applicants who:
  • Have a MS or PhD in a robotics related field. (A BS with relevant work experience is also acceptable)
  • Are solid software engineers and experienced C++ programmers
  • Are comfortable working in a Linux environment
  • Have experience with the ROS toolchain :-)
  • Possess solid communication skills, are comfortable joining in on a passionate technical discussion, love working in teams, and are fun to be around.
  • Have expertise in any of the following areas:
    • 3D Vision and VSLAM
    • 2D Image Processing
    • Real Time control
    • Planar Robot Path Planning
    • Robot Arm Motion Planning
    • Nonlinear Optimization
    • Machine Learning
    • Mobile Device Development

Application Materials:
  • Cover letter
  • Resume/CV
  • Downloadable code sample(s)
  • Two references and/or two letters of recommendation
  • A recent publication or statement of past experiences
Send your Application Materials and links to any projects you'd like us to take a look at to jobs@hidof.com.


UT Austin Nuclear & Applied Robotics Group

The Nuclear & Applied Robotics Group (robotics.me.utexas.edu) at the University of Texas at Austin is looking for one outstanding candidate to fill a postdoctoral position in the area of mobile manipulation. The appointment is for one year and renewable yearly by mutual agreement. The candidate must have completed their degree within the last three years and be a US citizen. The start date for the position is ideally September 1, 2014.


The successful candidate will have a PhD with an emphasis on robotics within mechanical engineering, electrical engineering, computer science or a related field. The candidate must be prepared to complete a security background check to work in nuclear and/or government facilities.

A successful candidate will have completed a dissertation that is topical to mobile manipulation and also must have extensive experience using ROS. U.T. Austin has recently acquired a mobile manipulation system consisting of a Husky mobile platform with two UR5 manipulators. More detail is available on our web site.

The candidate will be expected to take a leadership role in developing new capabilities for the platform relevant to our sponsor as well as coordinate and mentor graduate/undergraduate research associates contributing to the project. Key areas of interest are task planning, navigation, manipulation in the presence of the uncertainty, and sensor (vision, IMU, radiation, etc.) data fusion for visualization and decision making. The candidate will also be expected to help maintain and coordinate collaboratively developed software packages. Candidates will have the opportunity to propose and pursue new and novel avenues for advancing the autonomy or manipulation capabilities for this system.

To apply, email a single file containing your CV and a one page summary of your research interests to mpryor@utexas.edu. Please keep the file below 2MB and use the subject line LANL Postdoc Application: Last name, First name. Applications received by June 15, 2014 will receive full consideration and applications will continue to be accepted until the position is filled. For more information, visit robotics.me.utexas.edu.

Control Hardware/Software Engineer at BZ Robot, Mountain View, California

BZ Robot Inc, an exciting startup in Mountain View, California, USA, is
looking for excellent candidates with expertise in real-time control
systems (hardware/software), machine vision, autonomous navigation and
robotic manipulation. Opportunities of being a member of the founding team
that consists of top-tier robotics experts are provided.

BZ Robot Inc. offers a fast-paced work environment, very competitive
compensation, stock option, medical and 401K retirement plan benefits.

Degree Level: B.E with 5 years of prior experience, M.S. with at least 3
years experience or Ph.D.;
Fresh graduate students from top-tier universities are also welcome to apply

Major(s): Computer Science, Electrical Engineering, or a related field.

Position 1: Control Hardware Engineer
Your Duties and Tasks:
- Designing multilayer PCBs and firmware for functions including power
regulation, motor control, sensor interfaces, and communications; digital
circuit function testing, and verification
- Coordinate with the software team on verification of various algorithms

Skills / Job Requirements:
 - Excellent knowledge and proven expertise in microprocessors such as ARM,
FPGA, and DSP
 - Proven expertise in sensor electronics, including vision, laser, DIO,AIO
etc.
 - Excellent expertise in industrial data bus including Ethercat,
Ethernet/IP, CAN bus.
 - Knowledge of RTOS, preferring RTEMS and OROCOS
 - Proven system integration skills


Position 2: Control Software Engineer
Your Duties and Tasks:
 - Programming of various robot algorithms including motion planning,
kinematics, servo control, dynamics
 -  Algorithms for autonomous or semi-autonomous navigation
 -  Algorithms for robotic manipulation
 -  Computer vision
 -  Tracking algorithm

Skills / Job Requirements:
 - Excellent knowledge and proven expertise in software architecture -
Excellent C++ programming expertise required
 - Knowledge of Linux, and RTOS
 - The ability to develop, understand and implement complex algorithms
efficiently and correctly
 - Experience with modern software engineering tools
 - Experience working independently in a large software setting
 - Experience working on controller electronics hardware is a plus,
  - Experience with robot simulation environments and ROS is a plus
 - Excellent communication skills and demonstrate a proven ability to
multitask and deliver on challenging software development tasks
 - experience bringing a product to market

The VLAB will be hosting a robotics event this Thursday featuring several ROS using companies. Details below: 

VLAB MAY 29th:  ROBOTS LIVING AMONGST US

A new generation of innovative robotic platforms is emerging with human cadenceand more adaptable automation solutionsRobots are learning to perform complex tasks and to interact with humans in boundless environments. 

Will these robots facilitate the predicted re-shoring or renaissance in US manufacturing? And what will be the economic consequences of this new co-habitation?  Join us on Thursday, May 29th, 2014 to find out!

Moderator:
Andra Keay, Managing Director, Silicon Valley Robotics 

Panelists:
Melonee Wise, CEO & Founder, Unbounded Robotics
Milan Shah, VP of Software Engineering,Rethink Robotics 
John Dulchinos, Vice President of Automation, Jabil Circuits 
Peter Hebert, Co-Founder, Lux Capital

Demos:
Aldebaran | Dash Robotics | OSRF (Open Source Robotics Foundation) | Otherlab | Precise Automation | Revolve Robotics | Tempo Automation

ROS Kong Presentation Abstracts

| No Comments | No TrackBacks

We're looking forward to ROS Kong in two weeks. In preparation for the event we're happy to publish the abstracts of the presentations.

Open Source Robotics at JSK/Tokyo

Kei Okada

Robotics, specially Humanoids research requires long-term vision and efforts due to it's complexity and synthesis. This talk will show research history on humanoid robots last 20 years at JSK/U-Tokyo and discuss how we have been integrating and maintaining integrated humanoid software over different generation of both students and robots. Rapid-prototyping and contentious-development is the key of these environment and how these features are utilized in national/international projects and challenges. From this perspective, emergence of opensource robotics had great impact since we already had great deal of in-house software resources and had to cope with how to fuse and connect existing internal software and external open software. I'll not only explain strategy to this integration but also show our automatic translation system of different software component. Lastly, I'll explain our effort on commercializing our software in Tokyo to expand open robotics software not only academia but also robotic industries.

Robot Middleware Standard: RT-Middleware: Its architecture, implementation and standardization

Noriaki Ando

RT-Middleware (RTM) is an OMG standard specification of a component model and its implementations for robotic systems. We already have a dozen of implementations, and interoperability among implementations are guaranteed by the standard specification. Moreover its ports mechanism enables interoperability to other middlewares such as ROS DDS and so on, and the execution context feature of RTM realizes real-time capabilities, which is utilized in HRP, Hiro/Nextage and SHAFT's humanoid and so on. In this talk, the concept of RT-Middleware, architecture and implementations will be introduced. New standardization activity in OMG to define unified software component model will also be presented. As other topic, our collaboration with US DoD in DARPA DRC and new projects will be mentioned.

ROS at CSIRO

Paulo Borges

In this talk we will discuss how our team at CSIRO is using ROS in our robotic platforms, including internal projects and development processes.

CSIRO is Australia's national research agency and our lab, the Autonomous Systems Laboratory, has a very strong focus on field robots, carrying out research on ground, air, and underwater vehicles.

The ROS-based platforms we will present include autonomous industrial ground vehicles, air vehicles, thermal-camera based 3D mapping and the Zebedee 3D laser-scanner.

I will show how the platforms combine out-of-the-box ROS packages with in-house developed packages, indicating where ROS works perfectly as well as some of the issues we face.

Finally, we will also contrast ROS with DDX (Dynamic Data Exchange), which was our successful alternative before ROS was made available.

ROS, Atlas and the DARPA Robotics Challenge

Wyatt Newman and Chris Swetenham

This presentation will review use of ROS in controlling a Boston Dynamics "Atlas" humanoid robot competing in the DARPA Robotics Challenge as "Team HKU" (Hong Kong University). Atlas robots were delivered in August, and the DRC "trials" were held in December, allowing very little time for interfacing to and programming of this new robot. Additionally, a challenging constraint of the DRC is limited communications between the robot in the field and a remote operator. A specific ROS challenge was the need to run local and remote ROS cores to limit communications via a "net tunnel." Use of ROS will also be described in the contexts of locomotion planning, manipulation planning, vision-guided manipulation, balancing and force control. Live Atlas demonstrations will be performed.

Getting Into ROS: What's available and how to use it easily

Daniel Stonier

In this presentation I will discuss various approaches and technologies that are at your disposal when wishing to connect to a ROS robot. ROS has a large and sometimes bewildering variety of solutions in its arsenal - ssh tunnels, remotely networked ROS pc's, rqt plugins, robot web tools, java-android apps, pairing with application managers and also some more esoteric multimastering techniques. However, what is right for your team and your user's needs? This can be a complex question and a lack of documentation or knowledge about the technologies and languages they use often makes the answer non-trivial.

Here I will introduce each method with some tips and a list of pros and cons. Finally I will conclude with an overview and a few directional pointers so that you can get your own connectivity needs kickstarted without undue time consuming experimentation.

If you haven't already, there's still space to register.

ROS Indigo Igloo Beta Available

| No Comments | No TrackBacks
We're pleased to announce the availability of the first beta release of ROS Indigo Igloo in the repositories. ROS Indigo Igloo now has over 500 packages including everything in ros-indigo-desktop-full as defined in REP 142 [1]. 

ROS Indigo Igloo will be our first LTS release synchronized to pair with the Ubuntu Trusty Tahr release which came out last month. The support period and a summary of distributions can be found on the wiki [2]. 

As this is an LTS release most of the core components have been focused on minor incremental improvements for stability and maintainability. For a summary of updates important to all developers please see the migration guide [3]. This is an aggregation of package changes which maintainers would like the community to be aware of. If you are maintaining a package and have made major changes it is encouraged to fill this page in before the final release. 

This is the first beta release and we ask that people try out the system in the coming weeks. We have just recently detected a major issue with the Debian packaging system and thanks to the great community of ROS maintainers in one week we have rereleased over 300 packages.

To make sure that we have adequate testing we will delay the final release into June.  

Full details of updated packages in Indigo Hydro and Groovy are below. 





Updates to indigo (1 of 3)

Added Packages [28]:
 * ros-indigo-amcl: 1.11.8-0
 * ros-indigo-arbotix: 0.9.2-0
 * ros-indigo-arbotix-controllers: 0.9.2-0
 * ros-indigo-arbotix-firmware: 0.9.2-0
 * ros-indigo-arbotix-msgs: 0.9.2-0
 * ros-indigo-arbotix-python: 0.9.2-0
 * ros-indigo-arbotix-sensors: 0.9.2-0
 * ros-indigo-base-local-planner: 1.11.8-0
 * ros-indigo-carrot-planner: 1.11.8-0
 * ros-indigo-clear-costmap-recovery: 1.11.8-0
 * ros-indigo-costmap-2d: 1.11.8-0
 * ros-indigo-dwa-local-planner: 1.11.8-0
 * ros-indigo-fake-localization: 1.11.8-0
 * ros-indigo-global-planner: 1.11.8-0
 * ros-indigo-map-server: 1.11.8-0
 * ros-indigo-move-base: 1.11.8-0
 * ros-indigo-move-base-msgs: 1.11.8-0
 * ros-indigo-move-slow-and-clear: 1.11.8-0
 * ros-indigo-nav-core: 1.11.8-0
 * ros-indigo-navfn: 1.11.8-0
 * ros-indigo-navigation: 1.11.8-0
 * ros-indigo-openni2-launch: 0.2.1-0
 * ros-indigo-pocketsphinx: 0.3.0-0
 * ros-indigo-robot-pose-ekf: 1.11.8-0
 * ros-indigo-rotate-recovery: 1.11.8-0
 * ros-indigo-rviz-animated-view-controller: 0.1.1-0
 * ros-indigo-view-controller-msgs: 0.1.2-0
 * ros-indigo-voxel-grid: 1.11.8-0


Updated Packages [222]:
 * ros-indigo-actionlib: 1.11.1-0 -> 1.11.2-0
 * ros-indigo-actionlib-msgs: 1.11.3-0 -> 1.11.3-1
 * ros-indigo-bond: 1.7.14-0 -> 1.7.14-1
 * ros-indigo-bond-core: 1.7.14-0 -> 1.7.14-1
 * ros-indigo-bondcpp: 1.7.14-0 -> 1.7.14-1
 * ros-indigo-bondpy: 1.7.14-0 -> 1.7.14-1
 * ros-indigo-camera-calibration-parsers: 1.11.3-0 -> 1.11.3-1
 * ros-indigo-camera-info-manager: 1.11.3-0 -> 1.11.3-1
 * ros-indigo-class-loader: 0.2.4-0 -> 0.2.5-1
 * ros-indigo-common-msgs: 1.11.3-0 -> 1.11.3-1
 * ros-indigo-control-msgs: 1.3.0-1 -> 1.3.0-2
 * ros-indigo-control-toolbox: 1.11.0-0 -> 1.11.0-1
 * ros-indigo-controller-interface: 0.8.0-0 -> 0.8.0-1
 * ros-indigo-controller-manager: 0.8.0-0 -> 0.8.0-1
 * ros-indigo-controller-manager-msgs: 0.8.0-0 -> 0.8.0-1
 * ros-indigo-controller-manager-tests: 0.8.0-0 -> 0.8.0-1
 * ros-indigo-cpp-common: 0.5.0-0 -> 0.5.0-1
 * ros-indigo-cv-bridge: 1.11.2-0 -> 1.11.2-1
 * ros-indigo-diagnostic-msgs: 1.11.3-0 -> 1.11.3-1
 * ros-indigo-diff-drive-controller: 0.8.0-0 -> 0.8.0-1
 * ros-indigo-dynamic-reconfigure: 1.5.36-0 -> 1.5.36-1
 * ros-indigo-eigen-conversions: 1.11.3-0 -> 1.11.3-1
 * ros-indigo-fcl: 0.3.0-1 -> 0.3.1-0
 * ros-indigo-force-torque-sensor-controller: 0.8.0-0 -> 0.8.0-1
 * ros-indigo-forward-command-controller: 0.8.0-0 -> 0.8.0-1
 * ros-indigo-freenect-camera: 0.3.2-0 -> 0.3.2-1
 * ros-indigo-freenect-launch: 0.3.2-0 -> 0.3.2-1
 * ros-indigo-freenect-stack: 0.3.2-0 -> 0.3.2-1
 * ros-indigo-gazebo-msgs: 2.4.3-0 -> 2.4.3-1
 * ros-indigo-gazebo-plugins: 2.4.3-0 -> 2.4.3-1
 * ros-indigo-gazebo-ros: 2.4.3-0 -> 2.4.3-1
 * ros-indigo-gazebo-ros-pkgs: 2.4.3-0 -> 2.4.3-1
 * ros-indigo-geometric-shapes: 0.3.8-1 -> 0.3.8-2
 * ros-indigo-geometry: 1.11.3-0 -> 1.11.3-1
 * ros-indigo-geometry-msgs: 1.11.3-0 -> 1.11.3-1
 * ros-indigo-gripper-action-controller: 0.8.0-0 -> 0.8.0-1
 * ros-indigo-hardware-interface: 0.8.0-0 -> 0.8.0-1
 * ros-indigo-humanoid-msgs: 0.3.0-0 -> 0.3.0-1
 * ros-indigo-humanoid-nav-msgs: 0.3.0-0 -> 0.3.0-1
 * ros-indigo-image-common: 1.11.3-0 -> 1.11.3-1
 * ros-indigo-image-geometry: 1.11.2-0 -> 1.11.2-1
 * ros-indigo-image-transport: 1.11.3-0 -> 1.11.3-1
 * ros-indigo-imu-sensor-controller: 0.8.0-0 -> 0.8.0-1
 * ros-indigo-interaction-cursor-3d: 0.0.3-0 -> 0.0.3-1
 * ros-indigo-interaction-cursor-demo: 0.0.3-0 -> 0.0.3-1
 * ros-indigo-interaction-cursor-msgs: 0.0.3-0 -> 0.0.3-1
 * ros-indigo-interaction-cursor-rviz: 0.0.3-0 -> 0.0.3-1
 * ros-indigo-joint-limits-interface: 0.8.0-0 -> 0.8.0-1
 * ros-indigo-joint-state-controller: 0.8.0-0 -> 0.8.0-1
 * ros-indigo-joint-trajectory-controller: 0.8.0-0 -> 0.8.0-1
 * ros-indigo-kdl-conversions: 1.11.3-0 -> 1.11.3-1
 * ros-indigo-libccd: 1.5.0-0 -> 1.5.0-1
 * ros-indigo-libfreenect: 0.1.2-1 -> 0.1.2-2
 * ros-indigo-message-filters: 1.11.2-0 -> 1.11.3-0
 * ros-indigo-mk: 1.11.1-0 -> 1.11.1-1
 * ros-indigo-moveit-core: 0.5.8-0 -> 0.5.8-1
 * ros-indigo-moveit-fake-controller-manager: 0.5.6-0 -> 0.5.6-1
 * ros-indigo-moveit-planners: 0.5.5-0 -> 0.5.5-1
 * ros-indigo-moveit-planners-ompl: 0.5.5-0 -> 0.5.5-1
 * ros-indigo-moveit-plugins: 0.5.6-0 -> 0.5.6-1
 * ros-indigo-moveit-python: 0.2.1-0 -> 0.2.2-0
 * ros-indigo-moveit-ros: 0.5.18-0 -> 0.5.18-1
 * ros-indigo-moveit-ros-benchmarks: 0.5.18-0 -> 0.5.18-1
 * ros-indigo-moveit-ros-benchmarks-gui: 0.5.18-0 -> 0.5.18-1
 * ros-indigo-moveit-ros-manipulation: 0.5.18-0 -> 0.5.18-1
 * ros-indigo-moveit-ros-move-group: 0.5.18-0 -> 0.5.18-1
 * ros-indigo-moveit-ros-perception: 0.5.18-0 -> 0.5.18-1
 * ros-indigo-moveit-ros-planning: 0.5.18-0 -> 0.5.18-1
 * ros-indigo-moveit-ros-planning-interface: 0.5.18-0 -> 0.5.18-1
 * ros-indigo-moveit-ros-robot-interaction: 0.5.18-0 -> 0.5.18-1
 * ros-indigo-moveit-ros-visualization: 0.5.18-0 -> 0.5.18-1
 * ros-indigo-moveit-ros-warehouse: 0.5.18-0 -> 0.5.18-1
 * ros-indigo-moveit-simple-controller-manager: 0.5.6-0 -> 0.5.6-1
 * ros-indigo-nao-bringup: 0.2.3-0 -> 0.2.3-1
 * ros-indigo-nao-description: 0.2.3-0 -> 0.2.3-1
 * ros-indigo-nao-driver: 0.2.3-0 -> 0.2.3-1
 * ros-indigo-nao-msgs: 0.2.3-0 -> 0.2.3-1
 * ros-indigo-nao-pose: 0.2.3-0 -> 0.2.3-1
 * ros-indigo-nao-robot: 0.2.3-0 -> 0.2.3-1
 * ros-indigo-nav-msgs: 1.11.3-0 -> 1.11.3-1
 * ros-indigo-nmea-msgs: 0.1.0-0 -> 0.1.0-1
 * ros-indigo-nodelet: 1.8.3-0 -> 1.8.3-1
 * ros-indigo-nodelet-core: 1.8.3-0 -> 1.8.3-1
 * ros-indigo-nodelet-topic-tools: 1.8.3-0 -> 1.8.3-1
 * ros-indigo-octomap: 1.6.4-1 -> 1.6.5-0
 * ros-indigo-octomap-msgs: 0.3.1-4 -> 0.3.1-5
 * ros-indigo-octomap-ros: 0.4.0-0 -> 0.4.0-1
 * ros-indigo-octomap-rviz-plugins: 0.0.5-0 -> 0.0.5-1
 * ros-indigo-octovis: 1.6.4-1 -> 1.6.5-0
 * ros-indigo-openni2-camera: 0.1.2-0 -> 0.2.0-0
 * ros-indigo-orocos-kdl: 1.2.2-1 -> 1.2.2-2
 * ros-indigo-pluginlib: 1.10.0-0 -> 1.10.0-1
 * ros-indigo-polled-camera: 1.11.3-0 -> 1.11.3-1
 * ros-indigo-position-controllers: 0.8.0-0 -> 0.8.0-1
 * ros-indigo-python-orocos-kdl: 1.2.2-1 -> 1.2.2-2
 * ros-indigo-qt-dotgraph: 0.2.23-0 -> 0.2.24-0
 * ros-indigo-qt-gui: 0.2.23-0 -> 0.2.24-0
 * ros-indigo-qt-gui-app: 0.2.23-0 -> 0.2.24-0
 * ros-indigo-qt-gui-core: 0.2.23-0 -> 0.2.24-0
 * ros-indigo-qt-gui-cpp: 0.2.23-0 -> 0.2.24-0
 * ros-indigo-qt-gui-py-common: 0.2.23-0 -> 0.2.24-0
 * ros-indigo-razer-hydra: 0.0.13-1 -> 0.0.13-2
 * ros-indigo-realtime-tools: 1.9.0-0 -> 1.9.0-1
 * ros-indigo-robot-localization: 2.1.2-0 -> 2.1.2-1
 * ros-indigo-ros: 1.11.1-0 -> 1.11.1-1
 * ros-indigo-ros-comm: 1.11.2-0 -> 1.11.3-0
 * ros-indigo-ros-control: 0.8.0-0 -> 0.8.0-1
 * ros-indigo-ros-ethercat: 0.1.6-1 -> 0.1.7-0
 * ros-indigo-ros-ethercat-eml: 0.1.6-1 -> 0.1.7-0
 * ros-indigo-ros-ethercat-hardware: 0.1.6-1 -> 0.1.7-0
 * ros-indigo-ros-ethercat-loop: 0.1.6-1 -> 0.1.7-0
 * ros-indigo-ros-ethercat-model: 0.1.6-1 -> 0.1.7-0
 * ros-indigo-ros-tutorials: 0.5.1-0 -> 0.5.1-1
 * ros-indigo-rosapi: 0.5.5-1 -> 0.6.0-0
 * ros-indigo-rosbag: 1.11.2-0 -> 1.11.3-0
 * ros-indigo-rosbag-storage: 1.11.2-0 -> 1.11.3-0
 * ros-indigo-rosbash: 1.11.1-0 -> 1.11.1-1
 * ros-indigo-rosboost-cfg: 1.11.1-0 -> 1.11.1-1
 * ros-indigo-rosbridge-library: 0.5.5-1 -> 0.6.0-0
 * ros-indigo-rosbridge-server: 0.5.5-1 -> 0.6.0-0
 * ros-indigo-rosbridge-suite: 0.5.5-1 -> 0.6.0-0
 * ros-indigo-rosbuild: 1.11.1-0 -> 1.11.1-1
 * ros-indigo-rosclean: 1.11.1-0 -> 1.11.1-1
 * ros-indigo-rosconsole: 1.11.2-0 -> 1.11.3-0
 * ros-indigo-roscpp: 1.11.2-0 -> 1.11.3-0
 * ros-indigo-roscpp-core: 0.5.0-0 -> 0.5.0-1
 * ros-indigo-roscpp-serialization: 0.5.0-0 -> 0.5.0-1
 * ros-indigo-roscpp-traits: 0.5.0-0 -> 0.5.0-1
 * ros-indigo-roscpp-tutorials: 0.5.1-0 -> 0.5.1-1
 * ros-indigo-roscreate: 1.11.1-0 -> 1.11.1-1
 * ros-indigo-rosgraph: 1.11.2-0 -> 1.11.3-0
 * ros-indigo-roslang: 1.11.1-0 -> 1.11.1-1
 * ros-indigo-roslaunch: 1.11.2-0 -> 1.11.3-0
 * ros-indigo-roslib: 1.11.1-0 -> 1.11.1-1
 * ros-indigo-roslz4: 1.11.2-0 -> 1.11.3-0
 * ros-indigo-rosmake: 1.11.1-0 -> 1.11.1-1
 * ros-indigo-rosmaster: 1.11.2-0 -> 1.11.3-0
 * ros-indigo-rosmsg: 1.11.2-0 -> 1.11.3-0
 * ros-indigo-rosnode: 1.11.2-0 -> 1.11.3-0
 * ros-indigo-rosout: 1.11.2-0 -> 1.11.3-0
 * ros-indigo-rospack: 2.2.3-0 -> 2.2.3-1
 * ros-indigo-rosparam: 1.11.2-0 -> 1.11.3-0
 * ros-indigo-rospy: 1.11.2-0 -> 1.11.3-0
 * ros-indigo-rospy-tutorials: 0.5.1-0 -> 0.5.1-1
 * ros-indigo-rosservice: 1.11.2-0 -> 1.11.3-0
 * ros-indigo-rostest: 1.11.2-0 -> 1.11.3-0
 * ros-indigo-rostime: 0.5.0-0 -> 0.5.0-1
 * ros-indigo-rostopic: 1.11.2-0 -> 1.11.3-0
 * ros-indigo-rosunit: 1.11.1-0 -> 1.11.1-1
 * ros-indigo-roswtf: 1.11.2-0 -> 1.11.3-0
 * ros-indigo-rqt: 0.2.14-0 -> 0.2.14-1
 * ros-indigo-rqt-action: 0.3.5-0 -> 0.3.5-1
 * ros-indigo-rqt-bag: 0.3.5-0 -> 0.3.5-1
 * ros-indigo-rqt-bag-plugins: 0.3.5-0 -> 0.3.5-1
 * ros-indigo-rqt-capabilities: 0.1.1-0 -> 0.1.2-0
 * ros-indigo-rqt-common-plugins: 0.3.5-0 -> 0.3.5-1
 * ros-indigo-rqt-console: 0.3.5-0 -> 0.3.5-1
 * ros-indigo-rqt-controller-manager: 0.8.0-0 -> 0.8.0-1
 * ros-indigo-rqt-dep: 0.3.5-0 -> 0.3.5-1
 * ros-indigo-rqt-graph: 0.3.5-0 -> 0.3.5-1
 * ros-indigo-rqt-gui: 0.2.14-0 -> 0.2.14-1
 * ros-indigo-rqt-gui-cpp: 0.2.14-0 -> 0.2.14-1
 * ros-indigo-rqt-gui-py: 0.2.14-0 -> 0.2.14-1
 * ros-indigo-rqt-image-view: 0.3.5-0 -> 0.3.5-1
 * ros-indigo-rqt-launch: 0.3.5-0 -> 0.3.5-1
 * ros-indigo-rqt-logger-level: 0.3.5-0 -> 0.3.5-1
 * ros-indigo-rqt-moveit: 0.3.4-0 -> 0.3.4-1
 * ros-indigo-rqt-msg: 0.3.5-0 -> 0.3.5-1
 * ros-indigo-rqt-nav-view: 0.3.4-0 -> 0.3.4-1
 * ros-indigo-rqt-plot: 0.3.5-0 -> 0.3.5-1
 * ros-indigo-rqt-pose-view: 0.3.4-0 -> 0.3.4-1
 * ros-indigo-rqt-publisher: 0.3.5-0 -> 0.3.5-1
 * ros-indigo-rqt-py-common: 0.3.5-0 -> 0.3.5-1
 * ros-indigo-rqt-py-console: 0.3.5-0 -> 0.3.5-1
 * ros-indigo-rqt-reconfigure: 0.3.5-0 -> 0.3.5-1
 * ros-indigo-rqt-robot-dashboard: 0.3.4-0 -> 0.3.4-1
 * ros-indigo-rqt-robot-monitor: 0.3.4-0 -> 0.3.4-1
 * ros-indigo-rqt-robot-plugins: 0.3.4-0 -> 0.3.4-1
 * ros-indigo-rqt-robot-steering: 0.3.4-0 -> 0.3.4-1
 * ros-indigo-rqt-runtime-monitor: 0.3.4-0 -> 0.3.4-1
 * ros-indigo-rqt-rviz: 0.3.4-0 -> 0.3.4-1
 * ros-indigo-rqt-service-caller: 0.3.5-0 -> 0.3.5-1
 * ros-indigo-rqt-shell: 0.3.5-0 -> 0.3.5-1
 * ros-indigo-rqt-srv: 0.3.5-0 -> 0.3.5-1
 * ros-indigo-rqt-tf-tree: 0.3.4-0 -> 0.3.4-1
 * ros-indigo-rqt-top: 0.3.5-0 -> 0.3.5-1
 * ros-indigo-rqt-topic: 0.3.5-0 -> 0.3.5-1
 * ros-indigo-rqt-web: 0.3.5-0 -> 0.3.5-1
 * ros-indigo-rviz-fixed-view-controller: 0.0.2-0 -> 0.0.2-1
 * ros-indigo-sensor-msgs: 1.11.3-0 -> 1.11.3-1
 * ros-indigo-shape-msgs: 1.11.3-0 -> 1.11.3-1
 * ros-indigo-smclib: 1.7.14-0 -> 1.7.14-1
 * ros-indigo-sr-ronex: 0.9.11-0 -> 0.9.13-0
 * ros-indigo-sr-ronex-controllers: 0.9.11-0 -> 0.9.13-0
 * ros-indigo-sr-ronex-drivers: 0.9.11-0 -> 0.9.13-0
 * ros-indigo-sr-ronex-examples: 0.9.11-0 -> 0.9.13-0
 * ros-indigo-sr-ronex-external-protocol: 0.9.11-0 -> 0.9.13-0
 * ros-indigo-sr-ronex-hardware-interface: 0.9.11-0 -> 0.9.13-0
 * ros-indigo-sr-ronex-launch: 0.9.11-0 -> 0.9.13-0
 * ros-indigo-sr-ronex-msgs: 0.9.11-0 -> 0.9.13-0
 * ros-indigo-sr-ronex-test: 0.9.11-0 -> 0.9.13-0
 * ros-indigo-sr-ronex-transmissions: 0.9.11-0 -> 0.9.13-0
 * ros-indigo-sr-ronex-utilities: 0.9.11-0 -> 0.9.13-0
 * ros-indigo-std-msgs: 0.5.9-0 -> 0.5.9-1
 * ros-indigo-stereo-msgs: 1.11.3-0 -> 1.11.3-1
 * ros-indigo-tf: 1.11.3-0 -> 1.11.3-1
 * ros-indigo-tf-conversions: 1.11.3-0 -> 1.11.3-1
 * ros-indigo-topic-tools: 1.11.2-0 -> 1.11.3-0
 * ros-indigo-trajectory-msgs: 1.11.3-0 -> 1.11.3-1
 * ros-indigo-transmission-interface: 0.8.0-0 -> 0.8.0-1
 * ros-indigo-turtlesim: 0.5.1-0 -> 0.5.1-1
 * ros-indigo-velocity-controllers: 0.8.0-0 -> 0.8.0-1
 * ros-indigo-vision-opencv: 1.11.2-0 -> 1.11.2-1
 * ros-indigo-vision-visp: 0.7.3-0 -> 0.7.3-1
 * ros-indigo-visp: 2.9.0-10 -> 2.9.0-11
 * ros-indigo-visp-auto-tracker: 0.7.3-0 -> 0.7.3-1
 * ros-indigo-visp-bridge: 0.7.3-0 -> 0.7.3-1
 * ros-indigo-visp-camera-calibration: 0.7.3-0 -> 0.7.3-1
 * ros-indigo-visp-hand2eye-calibration: 0.7.3-0 -> 0.7.3-1
 * ros-indigo-visp-tracker: 0.7.3-0 -> 0.7.3-1
 * ros-indigo-visualization-msgs: 1.11.3-0 -> 1.11.3-1
 * ros-indigo-xmlrpcpp: 1.11.2-0 -> 1.11.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:
 * Aaron Blasdel
 * Adam Leeper
 * Adolfo Rodriguez Tsouroukdissian
 * Armin Hornung
 * Ben Charrow
 * Bence Magyar
 * Brandon Alexander
 * Dan Lazewatsky
 * David Lu!!
 * David V. Lu!!
 * Dirk Thomas
 * Dorian Scholz
 * Eric Perko
 * Esteve Fernandez
 * Fabien Spindler
 * Ioan Sucan
 * Isaac Isao Saito
 * Isaac Saito
 * Jack O'Quin
 * John Hsu
 * Julius Kammerl
 * Kelsey Hawkins
 * Manos Nikolaidis
 * Michael Ferguson
 * Mirza A. Shah
 * Ruben Smits
 * Sachin Chitta
 * Scott K Logan
 * Severin Lemaignan
 * Shadow Robot's software team
 * Stuart Glaser
 * Tom Moore
 * Tully Foote
 * Vijay Pradeep
 * Vincent Rabaud
 * William Woodall
 * Willow Garage
 * Wim Meeussen
 * Ze'ev Klapow

Updates to indigo (2 of 3)

Added Packages [0]:


Updated Packages [52]:
 * ros-indigo-catkin: 0.6.4-1 -> 0.6.5-0
 * ros-indigo-concert-msgs: 0.7.5-2 -> 0.7.5-3
 * ros-indigo-concert-service-msgs: 0.7.5-2 -> 0.7.5-3
 * ros-indigo-ecl: 0.60.0-0 -> 0.60.0-1
 * ros-indigo-ecl-build: 0.60.1-0 -> 0.60.1-1
 * ros-indigo-ecl-command-line: 0.60.9-0 -> 0.60.9-1
 * ros-indigo-ecl-concepts: 0.60.9-0 -> 0.60.9-1
 * ros-indigo-ecl-config: 0.60.1-0 -> 0.60.1-2
 * ros-indigo-ecl-containers: 0.60.9-0 -> 0.60.9-1
 * ros-indigo-ecl-converters: 0.60.9-0 -> 0.60.9-1
 * ros-indigo-ecl-converters-lite: 0.60.1-0 -> 0.60.1-2
 * ros-indigo-ecl-core: 0.60.9-0 -> 0.60.9-1
 * ros-indigo-ecl-core-apps: 0.60.9-0 -> 0.60.9-1
 * ros-indigo-ecl-devices: 0.60.9-0 -> 0.60.9-1
 * ros-indigo-ecl-eigen: 0.60.9-0 -> 0.60.9-1
 * ros-indigo-ecl-errors: 0.60.1-0 -> 0.60.1-2
 * ros-indigo-ecl-exceptions: 0.60.9-0 -> 0.60.9-1
 * ros-indigo-ecl-formatters: 0.60.9-0 -> 0.60.9-1
 * ros-indigo-ecl-geometry: 0.60.9-0 -> 0.60.9-1
 * ros-indigo-ecl-io: 0.60.1-0 -> 0.60.1-2
 * ros-indigo-ecl-ipc: 0.60.9-0 -> 0.60.9-1
 * ros-indigo-ecl-license: 0.60.1-0 -> 0.60.1-1
 * ros-indigo-ecl-linear-algebra: 0.60.9-0 -> 0.60.9-1
 * ros-indigo-ecl-lite: 0.60.1-0 -> 0.60.1-2
 * ros-indigo-ecl-manipulation: 0.60.0-0 -> 0.60.0-1
 * ros-indigo-ecl-manipulators: 0.60.0-0 -> 0.60.0-1
 * ros-indigo-ecl-math: 0.60.9-0 -> 0.60.9-1
 * ros-indigo-ecl-mobile-robot: 0.60.0-0 -> 0.60.0-1
 * ros-indigo-ecl-mpl: 0.60.9-0 -> 0.60.9-1
 * ros-indigo-ecl-navigation: 0.60.0-0 -> 0.60.0-1
 * ros-indigo-ecl-sigslots: 0.60.9-0 -> 0.60.9-1
 * ros-indigo-ecl-sigslots-lite: 0.60.1-0 -> 0.60.1-2
 * ros-indigo-ecl-statistics: 0.60.9-0 -> 0.60.9-1
 * ros-indigo-ecl-streams: 0.60.9-0 -> 0.60.9-1
 * ros-indigo-ecl-threads: 0.60.9-0 -> 0.60.9-1
 * ros-indigo-ecl-time: 0.60.9-0 -> 0.60.9-1
 * ros-indigo-ecl-time-lite: 0.60.1-0 -> 0.60.1-2
 * ros-indigo-ecl-tools: 0.60.1-0 -> 0.60.1-1
 * ros-indigo-ecl-type-traits: 0.60.9-0 -> 0.60.9-1
 * ros-indigo-ecl-utilities: 0.60.9-0 -> 0.60.9-1
 * ros-indigo-gateway-msgs: 0.7.5-2 -> 0.7.5-3
 * ros-indigo-rocon-app-manager-msgs: 0.7.5-2 -> 0.7.5-3
 * ros-indigo-rocon-device-msgs: 0.7.5-2 -> 0.7.5-3
 * ros-indigo-rocon-interaction-msgs: 0.7.5-2 -> 0.7.5-3
 * ros-indigo-rocon-msgs: 0.7.5-2 -> 0.7.5-3
 * ros-indigo-rocon-service-pair-msgs: 0.7.5-2 -> 0.7.5-3
 * ros-indigo-rocon-std-msgs: 0.7.5-2 -> 0.7.5-3
 * ros-indigo-rocon-tutorial-msgs: 0.7.5-2 -> 0.7.5-3
 * ros-indigo-scheduler-msgs: 0.7.5-2 -> 0.7.5-3
 * ros-indigo-zeroconf-avahi: 0.2.3-0 -> 0.2.3-1
 * ros-indigo-zeroconf-avahi-demos: 0.2.3-0 -> 0.2.3-1
 * ros-indigo-zeroconf-avahi-suite: 0.2.3-0 -> 0.2.3-1


Removed Packages [0]:


Thanks to all ROS maintainers who make packages available to the ROS community. The above list of packages was made possible by the work of the following maintainers:
 * Daniel Stonier
 * Dirk Thomas
 * Dongwook Lee


Updates to indigo (3 of 3)

Added Packages [0]:


Updated Packages [28]:
 * ros-indigo-moveit-python: 0.2.2-0 -> 0.2.3-0
 * ros-indigo-ompl: 0.14.1002831-0 -> 0.14.2002850-0
 * ros-indigo-rocon-app-manager: 0.7.0-0 -> 0.7.1-0
 * ros-indigo-rocon-app-platform: 0.7.0-0 -> 0.7.1-0
 * ros-indigo-rocon-app-utilities: 0.7.0-0 -> 0.7.1-0
 * ros-indigo-rocon-apps: 0.7.0-0 -> 0.7.1-0
 * ros-indigo-rocon-bubble-icons: 0.1.6-0 -> 0.1.8-0
 * ros-indigo-rocon-console: 0.1.6-0 -> 0.1.8-0
 * ros-indigo-rocon-ebnf: 0.1.6-0 -> 0.1.8-0
 * ros-indigo-rocon-gateway: 0.7.2-0 -> 0.7.3-0
 * ros-indigo-rocon-gateway-tests: 0.7.2-0 -> 0.7.3-0
 * ros-indigo-rocon-gateway-utils: 0.7.2-0 -> 0.7.3-0
 * ros-indigo-rocon-hub: 0.7.2-0 -> 0.7.3-0
 * ros-indigo-rocon-hub-client: 0.7.2-0 -> 0.7.3-0
 * ros-indigo-rocon-icons: 0.1.6-0 -> 0.1.8-0
 * ros-indigo-rocon-interactions: 0.1.6-0 -> 0.1.8-0
 * ros-indigo-rocon-launch: 0.1.6-0 -> 0.1.8-0
 * ros-indigo-rocon-master-info: 0.1.6-0 -> 0.1.8-0
 * ros-indigo-rocon-multimaster: 0.7.2-0 -> 0.7.3-0
 * ros-indigo-rocon-python-comms: 0.1.6-0 -> 0.1.8-0
 * ros-indigo-rocon-python-redis: 0.1.6-0 -> 0.1.8-0
 * ros-indigo-rocon-python-utils: 0.1.6-0 -> 0.1.8-0
 * ros-indigo-rocon-python-wifi: 0.1.6-0 -> 0.1.8-0
 * ros-indigo-rocon-semantic-version: 0.1.6-0 -> 0.1.8-0
 * ros-indigo-rocon-test: 0.7.2-0 -> 0.7.3-0
 * ros-indigo-rocon-tools: 0.1.6-0 -> 0.1.8-0
 * ros-indigo-rocon-unreliable-experiments: 0.7.2-0 -> 0.7.3-0
 * ros-indigo-rocon-uri: 0.1.6-0 -> 0.1.8-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:
 * Daniel Stonier
 * Ioan Sucan
 * Jihoon Lee
 * Michael Ferguson


Updates to hydro

Added Packages [35]:
 * ros-hydro-bayesian-belief-networks: 1.0.24-0
 * ros-hydro-data-vis-msgs: 0.0.2-0
 * ros-hydro-designator-integration-msgs: 0.0.2-0
 * ros-hydro-dna-extraction-msgs: 0.0.2-0
 * ros-hydro-grasp-stability-msgs: 0.0.2-0
 * ros-hydro-iai-common-msgs: 0.0.2-0
 * ros-hydro-iai-content-msgs: 0.0.2-0
 * ros-hydro-iai-kinematics-msgs: 0.0.2-0
 * ros-hydro-iai-pancake-perception-action: 0.0.2-0
 * ros-hydro-interaction-cursor-3d: 0.0.3-1
 * ros-hydro-interaction-cursor-demo: 0.0.3-1
 * ros-hydro-interaction-cursor-msgs: 0.0.3-1
 * ros-hydro-interaction-cursor-rviz: 0.0.3-1
 * ros-hydro-jsk-interactive-marker: 1.0.3-0
 * ros-hydro-jsk-rqt-plugins: 1.0.3-0
 * ros-hydro-jsk-rviz-plugins: 1.0.3-0
 * ros-hydro-ml-classifiers: 0.3.0-1
 * ros-hydro-mln-robosherlock-msgs: 0.0.2-0
 * ros-hydro-moveit-python: 0.2.2-0
 * ros-hydro-nav2d-exploration: 0.1.1-0
 * ros-hydro-nav2d-localizer: 0.1.1-0
 * ros-hydro-nav2d-msgs: 0.1.1-0
 * ros-hydro-nav2d-navigator: 0.1.1-0
 * ros-hydro-nav2d-operator: 0.1.1-0
 * ros-hydro-nav2d-remote: 0.1.1-0
 * ros-hydro-ros-ethercat: 0.1.7-0
 * ros-hydro-ros-ethercat-eml: 0.1.7-0
 * ros-hydro-ros-ethercat-loop: 0.1.7-0
 * ros-hydro-rviz-animated-view-controller: 0.1.1-0
 * ros-hydro-rviz-fixed-view-controller: 0.0.2-1
 * ros-hydro-saphari-msgs: 0.0.2-0
 * ros-hydro-scanning-table-msgs: 0.0.2-0
 * ros-hydro-sherlock-sim-msgs: 0.0.2-0
 * ros-hydro-sklearn: 1.0.24-0
 * ros-hydro-view-controller-msgs: 0.1.2-0


Updated Packages [232]:
 * ros-hydro-amcl: 1.11.6-1 -> 1.11.8-0
 * ros-hydro-assimp-devel: 1.0.20-0 -> 1.0.24-0
 * ros-hydro-base-local-planner: 1.11.6-1 -> 1.11.8-0
 * ros-hydro-bride: 0.3.1-1 -> 0.3.2-1
 * ros-hydro-bride-compilers: 0.3.1-1 -> 0.3.2-1
 * ros-hydro-bride-plugin-source: 0.3.1-1 -> 0.3.2-1
 * ros-hydro-bride-templates: 0.3.1-1 -> 0.3.2-1
 * ros-hydro-bride-tutorials: 0.3.1-1 -> 0.3.2-1
 * ros-hydro-bwi-desktop: 0.2.0-0 -> 0.2.1-0
 * ros-hydro-bwi-desktop-full: 0.2.0-0 -> 0.2.1-0
 * ros-hydro-bwi-launch: 0.2.0-0 -> 0.2.1-0
 * ros-hydro-camera-calibration-parsers: 1.11.1-0 -> 1.11.3-1
 * ros-hydro-camera-info-manager: 1.11.1-0 -> 1.11.3-1
 * ros-hydro-camera-info-manager-py: 0.2.2-0 -> 0.2.3-0
 * ros-hydro-camera1394: 1.9.5-0 -> 1.9.5-1
 * ros-hydro-carrot-planner: 1.11.6-1 -> 1.11.8-0
 * ros-hydro-clear-costmap-recovery: 1.11.6-1 -> 1.11.8-0
 * ros-hydro-collada-urdf-jsk-patch: 1.0.20-0 -> 1.0.24-0
 * ros-hydro-control-msgs: 1.2.0-0 -> 1.2.0-1
 * ros-hydro-control-toolbox: 1.10.4-1 -> 1.10.4-2
 * ros-hydro-controller-interface: 0.7.2-0 -> 0.7.2-1
 * ros-hydro-controller-manager: 0.7.2-0 -> 0.7.2-1
 * ros-hydro-controller-manager-msgs: 0.7.2-0 -> 0.7.2-1
 * ros-hydro-controller-manager-tests: 0.7.2-0 -> 0.7.2-1
 * ros-hydro-costmap-2d: 1.11.6-1 -> 1.11.8-0
 * ros-hydro-create-dashboard: 2.2.2-0 -> 2.2.2-1
 * ros-hydro-create-description: 2.2.0-0 -> 2.2.0-1
 * ros-hydro-create-driver: 2.2.0-0 -> 2.2.0-1
 * ros-hydro-create-gazebo-plugins: 2.2.2-0 -> 2.2.2-1
 * ros-hydro-create-node: 2.2.0-0 -> 2.2.0-1
 * ros-hydro-cv-bridge: 1.10.17-0 -> 1.10.17-1
 * ros-hydro-depth-image-proc-jsk-patch: 1.0.20-0 -> 1.0.24-0
 * ros-hydro-diff-drive-controller: 0.7.2-0 -> 0.7.2-1
 * ros-hydro-downward: 1.0.20-0 -> 1.0.24-0
 * ros-hydro-dwa-local-planner: 1.11.6-1 -> 1.11.8-0
 * ros-hydro-dynamic-tf-publisher: 1.0.20-0 -> 1.0.24-0
 * ros-hydro-effort-controllers: 0.7.2-0 -> 0.7.2-1
 * ros-hydro-euslisp: 1.1.17-3 -> 1.1.18-0
 * ros-hydro-fake-localization: 1.11.6-1 -> 1.11.8-0
 * ros-hydro-fanuc: 0.2.0-0 -> 0.2.0-1
 * ros-hydro-fanuc-assets: 0.2.0-0 -> 0.2.0-1
 * ros-hydro-fanuc-driver: 0.2.0-0 -> 0.2.0-1
 * ros-hydro-fanuc-m10ia-support: 0.2.0-0 -> 0.2.0-1
 * ros-hydro-fanuc-m16ib-support: 0.2.0-0 -> 0.2.0-1
 * ros-hydro-fanuc-m430ia-support: 0.2.0-0 -> 0.2.0-1
 * ros-hydro-fanuc-resources: 0.2.0-0 -> 0.2.0-1
 * ros-hydro-ff: 1.0.20-0 -> 1.0.24-0
 * ros-hydro-ffha: 1.0.20-0 -> 1.0.24-0
 * ros-hydro-force-torque-sensor-controller: 0.7.2-0 -> 0.7.2-1
 * ros-hydro-forward-command-controller: 0.7.2-0 -> 0.7.2-1
 * ros-hydro-freenect-camera: 0.3.2-0 -> 0.3.2-1
 * ros-hydro-freenect-launch: 0.3.2-0 -> 0.3.2-1
 * ros-hydro-freenect-stack: 0.3.2-0 -> 0.3.2-1
 * ros-hydro-geneus: 1.1.17-3 -> 1.1.18-0
 * ros-hydro-global-planner: 1.11.6-1 -> 1.11.8-0
 * ros-hydro-gripper-action-controller: 0.7.2-0 -> 0.7.2-1
 * ros-hydro-hardware-interface: 0.7.2-0 -> 0.7.2-1
 * ros-hydro-hrpsys-ros-bridge: 1.0.12-0 -> 1.2.0-0
 * ros-hydro-hrpsys-tools: 1.0.12-0 -> 1.2.0-0
 * ros-hydro-humanoid-msgs: 0.3.0-0 -> 0.3.0-1
 * ros-hydro-humanoid-nav-msgs: 0.3.0-0 -> 0.3.0-1
 * ros-hydro-image-common: 1.11.1-0 -> 1.11.3-1
 * ros-hydro-image-geometry: 1.10.17-0 -> 1.10.17-1
 * ros-hydro-image-transport: 1.11.1-0 -> 1.11.3-1
 * ros-hydro-image-view-jsk-patch: 1.0.20-0 -> 1.0.24-0
 * ros-hydro-image-view2: 1.0.20-0 -> 1.0.24-0
 * ros-hydro-imu-sensor-controller: 0.7.2-0 -> 0.7.2-1
 * ros-hydro-ipa-canopen: 0.5.4-0 -> 0.5.5-0
 * ros-hydro-ipa-canopen-core: 0.5.4-0 -> 0.5.5-0
 * ros-hydro-ipa-canopen-ros: 0.5.4-0 -> 0.5.5-0
 * ros-hydro-joint-limits-interface: 0.7.2-0 -> 0.7.2-1
 * ros-hydro-joint-state-controller: 0.7.2-0 -> 0.7.2-1
 * ros-hydro-joint-trajectory-controller: 0.7.2-0 -> 0.7.2-1
 * ros-hydro-jsk-common: 1.0.20-0 -> 1.0.24-0
 * ros-hydro-jsk-footstep-msgs: 1.0.20-0 -> 1.0.24-0
 * ros-hydro-jsk-gui-msgs: 1.0.20-0 -> 1.0.24-0
 * ros-hydro-jsk-hark-msgs: 1.0.20-0 -> 1.0.24-0
 * ros-hydro-jsk-roseus: 1.1.17-3 -> 1.1.18-0
 * ros-hydro-jsk-tools: 1.0.20-0 -> 1.0.24-0
 * ros-hydro-jsk-topic-tools: 1.0.20-0 -> 1.0.24-0
 * ros-hydro-kobuki: 0.5.5-1 -> 0.5.6-0
 * ros-hydro-kobuki-auto-docking: 0.5.5-1 -> 0.5.6-0
 * ros-hydro-kobuki-bumper2pc: 0.5.5-1 -> 0.5.6-0
 * ros-hydro-kobuki-controller-tutorial: 0.5.5-1 -> 0.5.6-0
 * ros-hydro-kobuki-core: 0.5.3-0 -> 0.5.4-0
 * ros-hydro-kobuki-dashboard: 0.3.2-0 -> 0.3.2-1
 * ros-hydro-kobuki-description: 0.5.5-1 -> 0.5.6-0
 * ros-hydro-kobuki-desktop: 0.3.2-0 -> 0.3.2-1
 * ros-hydro-kobuki-dock-drive: 0.5.3-0 -> 0.5.4-0
 * ros-hydro-kobuki-driver: 0.5.3-0 -> 0.5.4-0
 * ros-hydro-kobuki-ftdi: 0.5.3-0 -> 0.5.4-0
 * ros-hydro-kobuki-gazebo: 0.3.2-0 -> 0.3.2-1
 * ros-hydro-kobuki-gazebo-plugins: 0.3.2-0 -> 0.3.2-1
 * ros-hydro-kobuki-keyop: 0.5.5-1 -> 0.5.6-0
 * ros-hydro-kobuki-msgs: 0.5.0-0 -> 0.5.0-1
 * ros-hydro-kobuki-node: 0.5.5-1 -> 0.5.6-0
 * ros-hydro-kobuki-qtestsuite: 0.3.2-0 -> 0.3.2-1
 * ros-hydro-kobuki-random-walker: 0.5.5-1 -> 0.5.6-0
 * ros-hydro-kobuki-rviz-launchers: 0.3.2-0 -> 0.3.2-1
 * ros-hydro-kobuki-safety-controller: 0.5.5-1 -> 0.5.6-0
 * ros-hydro-kobuki-testsuite: 0.5.5-1 -> 0.5.6-0
 * ros-hydro-laser-filters-jsk-patch: 1.0.20-0 -> 1.0.24-0
 * ros-hydro-libfreenect: 0.1.2-1 -> 0.1.2-2
 * ros-hydro-libsiftfast: 1.0.20-0 -> 1.0.24-0
 * ros-hydro-linux-hardware: 2.2.4-0 -> 2.2.5-0
 * ros-hydro-map-server: 1.11.6-1 -> 1.11.8-0
 * ros-hydro-move-base: 1.11.6-1 -> 1.11.8-0
 * ros-hydro-move-base-msgs: 1.11.6-1 -> 1.11.8-0
 * ros-hydro-move-slow-and-clear: 1.11.6-1 -> 1.11.8-0
 * ros-hydro-multi-map-server: 1.0.20-0 -> 1.0.24-0
 * ros-hydro-nao-bringup: 0.2.3-0 -> 0.2.3-1
 * ros-hydro-nao-description: 0.2.3-0 -> 0.2.3-1
 * ros-hydro-nao-driver: 0.2.3-0 -> 0.2.3-1
 * ros-hydro-nao-msgs: 0.2.3-0 -> 0.2.3-1
 * ros-hydro-nao-pose: 0.2.3-0 -> 0.2.3-1
 * ros-hydro-nao-robot: 0.2.3-0 -> 0.2.3-1
 * ros-hydro-nav-core: 1.11.6-1 -> 1.11.8-0
 * ros-hydro-navfn: 1.11.6-1 -> 1.11.8-0
 * ros-hydro-navigation: 1.11.6-1 -> 1.11.8-0
 * ros-hydro-nmea-msgs: 0.1.0-0 -> 0.1.0-1
 * ros-hydro-object-recognition-core: 0.6.1-0 -> 0.6.2-0
 * ros-hydro-octomap: 1.6.4-0 -> 1.6.5-0
 * ros-hydro-octomap-msgs: 0.3.1-1 -> 0.3.1-2
 * ros-hydro-octomap-ros: 0.3.1-0 -> 0.3.1-1
 * ros-hydro-octomap-rviz-plugins: 0.0.5-1 -> 0.0.5-3
 * ros-hydro-octovis: 1.6.4-0 -> 1.6.5-0
 * ros-hydro-openni-tracker-jsk-patch: 1.0.20-0 -> 1.0.24-0
 * ros-hydro-openni2-camera: 0.1.2-0 -> 0.1.3-0
 * ros-hydro-openni2-launch: 0.1.3-0 -> 0.1.4-0
 * ros-hydro-openrtm-ros-bridge: 1.0.12-0 -> 1.2.0-0
 * ros-hydro-openrtm-tools: 1.0.12-0 -> 1.2.0-0
 * ros-hydro-opt-camera: 1.0.20-0 -> 1.0.24-0
 * ros-hydro-pano-core: 2.2.5-0 -> 2.2.5-1
 * ros-hydro-pano-py: 2.2.5-0 -> 2.2.5-1
 * ros-hydro-pano-ros: 2.2.5-0 -> 2.2.5-1
 * ros-hydro-polled-camera: 1.11.1-0 -> 1.11.3-1
 * ros-hydro-posedetection-msgs: 1.0.20-0 -> 1.0.24-0
 * ros-hydro-position-controllers: 0.7.2-0 -> 0.7.2-1
 * ros-hydro-pr2-groovy-patches: 1.0.20-0 -> 1.0.24-0
 * ros-hydro-razer-hydra: 0.0.12-0 -> 0.0.12-2
 * ros-hydro-realtime-tools: 1.8.3-0 -> 1.8.3-1
 * ros-hydro-robot-localization: 1.1.2-0 -> 1.1.2-1
 * ros-hydro-robot-pose-ekf: 1.11.6-1 -> 1.11.8-0
 * ros-hydro-ros-control: 0.7.2-0 -> 0.7.2-1
 * ros-hydro-ros-controllers: 0.7.2-0 -> 0.7.2-1
 * ros-hydro-ros-ethercat-hardware: 0.1.2-0 -> 0.1.7-0
 * ros-hydro-ros-ethercat-model: 0.1.3-0 -> 0.1.7-0
 * ros-hydro-rosapi: 0.5.5-1 -> 0.6.0-0
 * ros-hydro-rosbridge-library: 0.5.5-1 -> 0.6.0-0
 * ros-hydro-rosbridge-server: 0.5.5-1 -> 0.6.0-0
 * ros-hydro-rosbridge-suite: 0.5.5-1 -> 0.6.0-0
 * ros-hydro-roseus: 1.1.17-3 -> 1.1.18-0
 * ros-hydro-roseus-msgs: 1.1.17-3 -> 1.1.18-0
 * ros-hydro-roseus-smach: 1.1.17-3 -> 1.1.18-0
 * ros-hydro-rosnode-rtc: 1.0.12-0 -> 1.2.0-0
 * ros-hydro-rospatlite: 1.0.20-0 -> 1.0.24-0
 * ros-hydro-rosping: 1.0.20-0 -> 1.0.24-0
 * ros-hydro-rotate-recovery: 1.11.6-1 -> 1.11.8-0
 * ros-hydro-rqt-capabilities: 0.1.1-0 -> 0.1.2-0
 * ros-hydro-rqt-controller-manager: 0.7.2-0 -> 0.7.2-1
 * ros-hydro-rtmbuild: 1.0.12-0 -> 1.2.0-0
 * ros-hydro-rtmros-common: 1.0.12-0 -> 1.2.0-0
 * ros-hydro-sr-ronex: 0.9.6-0 -> 0.9.12-0
 * ros-hydro-sr-ronex-controllers: 0.9.6-0 -> 0.9.12-0
 * ros-hydro-sr-ronex-drivers: 0.9.6-0 -> 0.9.12-0
 * ros-hydro-sr-ronex-examples: 0.9.6-0 -> 0.9.12-0
 * ros-hydro-sr-ronex-external-protocol: 0.9.6-0 -> 0.9.12-0
 * ros-hydro-sr-ronex-hardware-interface: 0.9.6-0 -> 0.9.12-0
 * ros-hydro-sr-ronex-launch: 0.9.6-0 -> 0.9.12-0
 * ros-hydro-sr-ronex-msgs: 0.9.6-0 -> 0.9.12-0
 * ros-hydro-sr-ronex-test: 0.9.6-0 -> 0.9.12-0
 * ros-hydro-sr-ronex-transmissions: 0.9.6-0 -> 0.9.12-0
 * ros-hydro-sr-ronex-utilities: 0.9.6-0 -> 0.9.12-0
 * ros-hydro-stereo-synchronizer: 1.0.20-0 -> 1.0.24-0
 * ros-hydro-transmission-interface: 0.7.2-0 -> 0.7.2-1
 * ros-hydro-turtlebot: 2.2.4-0 -> 2.2.5-0
 * ros-hydro-turtlebot-actions: 2.2.5-0 -> 2.2.5-1
 * ros-hydro-turtlebot-apps: 2.2.5-0 -> 2.2.5-1
 * ros-hydro-turtlebot-bringup: 2.2.4-0 -> 2.2.5-0
 * ros-hydro-turtlebot-calibration: 2.2.5-0 -> 2.2.5-1
 * ros-hydro-turtlebot-core-apps: 2.2.5-0 -> 2.2.5-1
 * ros-hydro-turtlebot-create: 2.2.0-0 -> 2.2.0-1
 * ros-hydro-turtlebot-create-desktop: 2.2.2-0 -> 2.2.2-1
 * ros-hydro-turtlebot-dashboard: 2.2.3-0 -> 2.2.3-1
 * ros-hydro-turtlebot-description: 2.2.4-0 -> 2.2.5-0
 * ros-hydro-turtlebot-follower: 2.2.5-0 -> 2.2.5-1
 * ros-hydro-turtlebot-gazebo: 2.1.1-0 -> 2.1.1-1
 * ros-hydro-turtlebot-interactive-markers: 2.2.3-0 -> 2.2.3-1
 * ros-hydro-turtlebot-msgs: 2.2.0-0 -> 2.2.0-1
 * ros-hydro-turtlebot-navigation: 2.2.5-0 -> 2.2.5-1
 * ros-hydro-turtlebot-panorama: 2.2.5-0 -> 2.2.5-1
 * ros-hydro-turtlebot-rviz-launchers: 2.2.3-0 -> 2.2.3-1
 * ros-hydro-turtlebot-simulator: 2.1.1-0 -> 2.1.1-1
 * ros-hydro-turtlebot-teleop: 2.2.5-0 -> 2.2.5-1
 * ros-hydro-turtlebot-viz: 2.2.3-0 -> 2.2.3-1
 * ros-hydro-underwater-sensor-msgs: 1.3.1-0 -> 1.3.1-1
 * ros-hydro-underwater-vehicle-dynamics: 1.3.1-0 -> 1.3.1-1
 * ros-hydro-universal-robot: 1.0.2-0 -> 1.0.2-1
 * ros-hydro-ur-bringup: 1.0.2-0 -> 1.0.2-1
 * ros-hydro-ur-description: 1.0.2-0 -> 1.0.2-1
 * ros-hydro-ur-driver: 1.0.2-0 -> 1.0.2-1
 * ros-hydro-ur-gazebo: 1.0.2-0 -> 1.0.2-1
 * ros-hydro-ur-kinematics: 1.0.2-0 -> 1.0.2-1
 * ros-hydro-ur10-moveit-config: 1.0.2-0 -> 1.0.2-1
 * ros-hydro-ur5-moveit-config: 1.0.2-0 -> 1.0.2-1
 * ros-hydro-uwsim: 1.3.1-0 -> 1.3.1-1
 * ros-hydro-uwsim-osgbullet: 3.0.1-0 -> 3.0.1-1
 * ros-hydro-uwsim-osgworks: 3.0.3-1 -> 3.0.3-2
 * ros-hydro-velocity-controllers: 0.7.2-0 -> 0.7.2-1
 * ros-hydro-velodyne: 1.1.2-0 -> 1.1.2-1
 * ros-hydro-velodyne-driver: 1.1.2-0 -> 1.1.2-1
 * ros-hydro-velodyne-msgs: 1.1.2-0 -> 1.1.2-1
 * ros-hydro-velodyne-pointcloud: 1.1.2-0 -> 1.1.2-1
 * ros-hydro-vision-opencv: 1.10.17-0 -> 1.10.17-1
 * ros-hydro-vision-visp: 0.7.3-0 -> 0.7.3-1
 * ros-hydro-visp: 2.9.0-3 -> 2.9.0-4
 * ros-hydro-visp-auto-tracker: 0.7.3-0 -> 0.7.3-1
 * ros-hydro-visp-bridge: 0.7.3-0 -> 0.7.3-1
 * ros-hydro-visp-camera-calibration: 0.7.3-0 -> 0.7.3-1
 * ros-hydro-visp-hand2eye-calibration: 0.7.3-0 -> 0.7.3-1
 * ros-hydro-visp-tracker: 0.7.3-0 -> 0.7.3-1
 * ros-hydro-voxel-grid: 1.11.6-1 -> 1.11.8-0
 * ros-hydro-xsens-driver: 1.0.2-0 -> 1.0.3-0
 * ros-hydro-yocs-cmd-vel-mux: 0.5.3-0 -> 0.5.3-1
 * ros-hydro-yocs-controllers: 0.5.3-0 -> 0.5.3-1
 * ros-hydro-yocs-diff-drive-pose-controller: 0.5.3-0 -> 0.5.3-1
 * ros-hydro-yocs-math-toolkit: 0.5.3-0 -> 0.5.3-1
 * ros-hydro-yocs-msgs: 0.5.2-0 -> 0.5.2-1
 * ros-hydro-yocs-velocity-smoother: 0.5.3-0 -> 0.5.3-1
 * ros-hydro-yocs-virtual-sensor: 0.5.3-0 -> 0.5.3-1
 * ros-hydro-yocs-waypoints-navi: 0.5.3-0 -> 0.5.3-1
 * ros-hydro-yujin-ocs: 0.5.3-0 -> 0.5.3-1


Removed Packages [2]:
- ros-hydro-ardrone-autonomy
- ros-hydro-bwi


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:
 * AI Robotics
 * Adam Leeper
 * Adolfo Rodriguez Tsouroukdissian
 * Alexander Bubeck
 * Andrei Haidu
 * Armin Hornung
 * Bence Magyar
 * Brandon Alexander
 * Daniel Stonier
 * David Lu!!
 * David V. Lu!!
 * Eric Perko
 * Fabien Spindler
 * Ferenc Balint-Benczedi
 * Francis Colas
 * G.A. vd. Hoorn (TU Delft Robotics Institute)
 * Georg Bartels
 * Hiroyuki Mikita
 * Jack O'Quin
 * Jan Winkler
 * Jihoon Lee
 * Jorge Santos
 * Jorge Santos Simon
 * Julius Kammerl
 * KazutoMurase
 * Kei Okada
 * Kelsey Hawkins
 * Manos Nikolaidis
 * Marcus Liebhardt
 * Mario Prats
 * Melonee Wise
 * Michael Ferguson
 * MoveIt Setup Assistant
 * Nate Koenig
 * OSRF
 * Ryohei Ueda
 * Sachin Chitta
 * Scott Niekum
 * Sebastian Kasperski
 * Severin Lemaignan
 * Shadow Robot's software team
 * Shaun Edwards
 * Shohei Fujii
 * Stuart Glaser
 * TODO
 * Takuya Nakaoka
 * Thiago de Freitas
 * Tom Moore
 * Vijay Pradeep
 * Vincent Rabaud
 * William Woodall
 * Willow Garage
 * Wim Meeussen
 * Yohei Kakiuchi
 * Younghun Ju
 * ferenc
 * ferko
 * furuta
 * jworch

Updates to groovy

Added Packages [16]:
 * ros-groovy-bayesian-belief-networks: 1.0.24-0
 * ros-groovy-designator-integration: 0.0.0-1
 * ros-groovy-dna-extraction-msgs: 0.0.2-0
 * ros-groovy-ff: 1.0.24-0
 * ros-groovy-ffha: 1.0.24-0
 * ros-groovy-jsk-interactive-marker: 1.0.3-0
 * ros-groovy-jsk-planning: 0.1.2-1
 * ros-groovy-jsk-rqt-plugins: 1.0.3-0
 * ros-groovy-jsk-rviz-plugins: 1.0.3-0
 * ros-groovy-pddl-msgs: 0.1.2-1
 * ros-groovy-pddl-planner: 0.1.2-1
 * ros-groovy-pddl-planner-viewer: 0.1.2-1
 * ros-groovy-pr2eus: 0.1.6-3
 * ros-groovy-roseus-msgs: 1.1.18-0
 * ros-groovy-sklearn: 1.0.24-0
 * ros-groovy-task-compiler: 0.1.2-1


Updated Packages [83]:
 * ros-groovy-assimp-devel: 1.0.18-0 -> 1.0.24-0
 * ros-groovy-baxter-common: 0.7.0-0 -> 1.0.0-0
 * ros-groovy-baxter-core-msgs: 0.7.0-0 -> 1.0.0-0
 * ros-groovy-baxter-description: 0.7.0-0 -> 1.0.0-0
 * ros-groovy-baxter-examples: 0.7.0-0 -> 1.0.0-0
 * ros-groovy-baxter-interface: 0.7.0-0 -> 1.0.0-0
 * ros-groovy-baxter-maintenance-msgs: 0.7.0-0 -> 1.0.0-0
 * ros-groovy-baxter-sdk: 0.7.0-0 -> 1.0.0-0
 * ros-groovy-baxter-tools: 0.7.0-0 -> 1.0.0-0
 * ros-groovy-camera-calibration: 1.10.15-0 -> 1.10.17-0
 * ros-groovy-camera-info-manager-py: 0.2.2-0 -> 0.2.3-0
 * ros-groovy-collada-urdf-jsk-patch: 1.0.18-0 -> 1.0.24-0
 * ros-groovy-data-vis-msgs: 0.0.0-0 -> 0.0.2-0
 * ros-groovy-depth-image-proc: 1.10.15-0 -> 1.10.17-0
 * ros-groovy-depth-image-proc-jsk-patch: 1.0.18-0 -> 1.0.24-0
 * ros-groovy-designator-integration-msgs: 0.0.0-0 -> 0.0.2-0
 * ros-groovy-downward: 1.0.18-0 -> 1.0.24-0
 * ros-groovy-dynamic-tf-publisher: 1.0.18-0 -> 1.0.24-0
 * ros-groovy-euslisp: 1.1.11-2 -> 1.1.18-0
 * ros-groovy-geneus: 1.1.11-2 -> 1.1.18-0
 * ros-groovy-grasp-stability-msgs: 0.0.0-0 -> 0.0.2-0
 * ros-groovy-hrpsys: 315.1.9-2 -> 315.2.1-2
 * ros-groovy-hrpsys-ros-bridge: 1.0.11-0 -> 1.2.0-2
 * ros-groovy-hrpsys-tools: 1.0.11-0 -> 1.2.0-2
 * ros-groovy-humanoid-msgs: 0.3.0-0 -> 0.3.0-1
 * ros-groovy-humanoid-nav-msgs: 0.3.0-0 -> 0.3.0-1
 * ros-groovy-iai-common-msgs: 0.0.0-0 -> 0.0.2-0
 * ros-groovy-iai-content-msgs: 0.0.0-0 -> 0.0.2-0
 * ros-groovy-iai-kinematics-msgs: 0.0.0-0 -> 0.0.2-0
 * ros-groovy-iai-pancake-perception-action: 0.0.0-0 -> 0.0.2-0
 * ros-groovy-image-pipeline: 1.10.15-0 -> 1.10.17-0
 * ros-groovy-image-proc: 1.10.15-0 -> 1.10.17-0
 * ros-groovy-image-rotate: 1.10.15-0 -> 1.10.17-0
 * ros-groovy-image-view: 1.10.15-0 -> 1.10.17-0
 * ros-groovy-image-view-jsk-patch: 1.0.18-0 -> 1.0.24-0
 * ros-groovy-image-view2: 1.0.18-0 -> 1.0.24-0
 * ros-groovy-jsk-footstep-msgs: 1.0.18-0 -> 1.0.24-0
 * ros-groovy-jsk-gui-msgs: 1.0.18-0 -> 1.0.24-0
 * ros-groovy-jsk-hark-msgs: 1.0.18-0 -> 1.0.24-0
 * ros-groovy-jsk-pr2eus: 0.1.5-0 -> 0.1.6-3
 * ros-groovy-jsk-roseus: 1.1.11-2 -> 1.1.18-0
 * ros-groovy-jsk-tools: 1.0.18-0 -> 1.0.24-0
 * ros-groovy-jsk-topic-tools: 1.0.18-0 -> 1.0.24-0
 * ros-groovy-laser-filters-jsk-patch: 1.0.18-0 -> 1.0.21-2
 * ros-groovy-libsiftfast: 1.0.18-0 -> 1.0.24-0
 * ros-groovy-mln-robosherlock-msgs: 0.0.0-0 -> 0.0.2-0
 * ros-groovy-multi-map-server: 1.0.18-0 -> 1.0.21-2
 * ros-groovy-nao-bringup: 0.2.3-0 -> 0.2.3-1
 * ros-groovy-nao-description: 0.2.3-0 -> 0.2.3-1
 * ros-groovy-nao-driver: 0.2.3-0 -> 0.2.3-1
 * ros-groovy-nao-msgs: 0.2.3-0 -> 0.2.3-1
 * ros-groovy-nao-pose: 0.2.3-0 -> 0.2.3-1
 * ros-groovy-nao-robot: 0.2.3-0 -> 0.2.3-1
 * ros-groovy-object-recognition-core: 0.6.1-0 -> 0.6.2-0
 * ros-groovy-object-recognition-msgs: 0.4.0-0 -> 0.4.1-0
 * ros-groovy-octomap: 1.5.7-0 -> 1.5.7-1
 * ros-groovy-octomap-ros: 0.2.6-0 -> 0.2.6-1
 * ros-groovy-octomap-rviz-plugins: 0.0.4-0 -> 0.0.4-1
 * ros-groovy-octovis: 1.5.7-0 -> 1.5.7-1
 * ros-groovy-openni-tracker-jsk-patch: 1.0.18-0 -> 1.0.24-0
 * ros-groovy-openrtm-ros-bridge: 1.0.11-0 -> 1.2.0-2
 * ros-groovy-openrtm-tools: 1.0.11-0 -> 1.2.0-2
 * ros-groovy-opt-camera: 1.0.18-0 -> 1.0.24-0
 * ros-groovy-posedetection-msgs: 1.0.18-0 -> 1.0.24-0
 * ros-groovy-pr2-groovy-patches: 1.0.18-0 -> 1.0.24-0
 * ros-groovy-robot-localization: 0.1.0-0 -> 0.1.2-0
 * ros-groovy-rosapi: 0.5.4-0 -> 0.5.6-1
 * ros-groovy-rosbridge-library: 0.5.4-0 -> 0.5.6-1
 * ros-groovy-rosbridge-server: 0.5.4-0 -> 0.5.6-1
 * ros-groovy-rosbridge-suite: 0.5.4-0 -> 0.5.6-1
 * ros-groovy-roseus: 1.1.11-2 -> 1.1.18-0
 * ros-groovy-roseus-smach: 1.1.11-2 -> 1.1.18-0
 * ros-groovy-rosnode-rtc: 1.0.11-0 -> 1.2.0-2
 * ros-groovy-rospatlite: 1.0.18-0 -> 1.0.24-0
 * ros-groovy-rosping: 1.0.18-0 -> 1.0.24-0
 * ros-groovy-rqt-capabilities: 0.1.0-0 -> 0.1.2-3
 * ros-groovy-rtmbuild: 1.0.11-0 -> 1.2.0-2
 * ros-groovy-rtmros-common: 1.0.11-0 -> 1.2.0-2
 * ros-groovy-saphari-msgs: 0.0.0-0 -> 0.0.2-0
 * ros-groovy-scanning-table-msgs: 0.0.0-0 -> 0.0.2-0
 * ros-groovy-sherlock-sim-msgs: 0.0.0-0 -> 0.0.2-0
 * ros-groovy-stereo-image-proc: 1.10.15-0 -> 1.10.17-0
 * ros-groovy-stereo-synchronizer: 1.0.18-0 -> 1.0.24-0


Removed Packages [1]:
- ros-groovy-jsk-common


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:
 * AI Robotics
 * Andrei Haidu
 * Armin Hornung
 * Brandon Alexander
 * Ferenc Balint-Benczedi
 * Georg Bartels
 * Hiroyuki Mikita
 * Jack O'Quin
 * Jan Winkler
 * Julius Kammerl
 * KazutoMurase
 * Kei Okada
 * Rethink Robotics Inc.
 * Ryohei Ueda
 * Severin Lemaignan
 * Shohei Fujii
 * TODO
 * Takuya Nakaoka
 * Tom Moore
 * Vincent Rabaud
 * William Woodall
 * Yohei Kakiuchi
 * ferenc
 * ferko
 * furuta
 * jworch
 * winkler

From Sebastian Rockel

I'd just like to announce a related ICRA talk on Wednesday (15:40-16:00, Session WeC07.6, Room S225) held by myself.

Its about simulation-based prediction of action results in a plan-based robotic system. The system is heavily using ROS and Gazebo.

So if someone is interested I would be looking forward to see you then.

Abstract: In this work we ask whether an integrated system based on the concept of human imagination and realized as a hyperreal setup can improve system robustness and autonomy. In particular we focus on how non-nominal failures in a planning-based system can be detected before actual failure. To investigate, we integrated a system combining an accurate physics-based simulation, robust object recognition and a sym- bolic planner to achieve realistic prediction of robot actions. A Gazebo simulation was used to reason about and evaluate situations before and during plan execution. The simulation enabled re-planning to take place in advance of actual plan failure. We present a restaurant scenario in which our system prevents plan failure and successfully lets the robot serve a drink on a table cluttered with objects. The results give us confidence in our approach to improving situations where unavoidable abstractions of robot action planning meet the real world.

Kind regards,

Sebastian

New Package: handle_detector

| No Comments | No TrackBacks

From Andreas ten Pas via ros-users@

Hi all,

although it has been available in the packages for quite a while, I wanted to officially announce our ROS Hydro package for localizing handles in 3D point clouds: http://wiki.ros.org/handle_detector

You can see a demonstration of the localization on Rethink Robotics' Baxter robot that is clearing several objects from a table in this video:

A tutorial for using our software is available at the ROS wiki page given above.

If you find any problems, feel free to report them at: https://github.com/atenpas/handle_detector/issues

All the best,

Andreas

Making Juice at the High Tech Systems Fair 2014

| No Comments | No TrackBacks

From Jesse Scholtes, Eindhoven, the Netherlands

In December 2013, TMC and YASKAWA Benelux set out to make a technology demonstrator.

YASKAWA sees a shift in robotics, from welding, handling, painting to new application areas. Some recent developments of YASKAWA are 'milking-robots' and 'slaughter-robots'. And as we are aware of, Universities and research institutions are working hard on the introduction of robots in (health) care or other areas where human interaction is present and essential.

A new era of smart robotics is becoming a reality. The development of these new robots pose new technological problems and need different solutions. It raises questions about how a robot can be programmed to deal with changing environments? How an intuitive and user-friendly interface can be created? Or how flexible mechanics can be be designed to handle different object just like humans do. And more and foremost how to create smarter safety systems such that robots can safely operate among people.

The demonstrator sets out to do accomplish a number of things:

  • Use a 'higher' software environment like ROS
  • Integration of vision to make the robot aware of its surroundings;
  • Implementation of a flexible gripper to make it possible to perform different tasks;
  • Use a modern user interface like a tablet or smartphone to control the robot;
  • Make the robot perform some tasks that are expected from service robotics.

After a brainstorm we came up with the idea that the robot should pick, slice and squeeze an orange to make fresh orange juice, next to that it should also serve this glass to someone in the audience.

For 3½ months and with a team of 12 people we shared our Monday evenings and a lot of enthusiasm to build this orange crusher or as we call her nowadays: (Juicy) Lucy. The team consisted of people with different backgrounds: mechatronics, robotics, embedded software, mechanical design and electronics. Our deadline was the High Tech Systems Fair the 7th or 8th of May.

ROS enabled us to quickly prototype and realize our demonstrator. Using ROS we combined several piece of hardware:

  • An Android tablet where we designed two different apps. A user app to choose the amount of orange juice. And an engineering app that allowed us to control the robot gripper, provided ROS INFO messages plus control over the state machine.

  • A laptop and a mini pc; where the mini pc was used to perform the image processing.

  • A webcam, where its images were used to dynamically extract the X, Y coordinates of the oranges.

  • An Arduino board. Here, the Arduino board was used to control the gripper which was equipped with 4 x stepper motors, 4 end switches and a sonar sensor (the sonar was used to measure the height of the orange).

An example of the system overview can be seen here.

yasaka_system_overview.png

In the end we managed to deliver the first version of our demonstrator that serves as a platform for future enhancements and add more complexity. The fruits of our labor can be viewed in the following video.

Making Juice at the High Tech Systems Fair 2014 from YASK_dem on Vimeo.

At this point the HTS fair is the only fair were we presented our demonstrator. At the moment we are brainstorming on a follow up for the project.

From Pablo Gil

ROS-RM. Workshop on "ROS and his applications for Robotic Manipulation"

REGISTRATION

The fee for the ROS-RM 2014 Workshop is 100 Euros. Registration covers attendance to all lectures, handling material, two coffee breaks and one lunch from the University to Alicante city. Payment should be done by bank transfer (more information at the web site).

APPLICATION DEADLINE: 20 June 2014 (NO extensions will be given)

http://www.aurova.ua.es/index.php/es/rosrmapp

VENUE

ROS-RM Workshop 2014 will be held at the Polythecnic College of the University of Alicante, in San Vicente del Raspeig (Alicante), Spain. Alicante is located on south east at the Mediterranean coast. The University is 15 minutes from the center city of Alicante by tram, while the Alicante airport is 20 minutes by car.

SPEAKERS AND PROGRAMME

  • Juan Antonio Corrales, Marie Curie University, Paris-France
  • Sachin Chitta, SRI, USA.
  • Guillaume Walck, University of Bielefeld, Germany
  • Federico Tombari, University of Bologna, Italy
  • Toni Oliver, Shadow Robot Company, UK

  • Session 1: ROS Architecture. Introduction and basic concepts

  • Session 2: MoveIt! A Tool for Manipulation
  • Session 3: Manipulation with a Dexterous Hand
  • Session 4: 3D Object recognition with the PCL
  • Session 5: Shadow-hand with ROS

MOTIVATION AND DESCRIPTION

The hands-on will be delivered by world renowned experts in the field, from both academia and industry, and will cover both theoretical and practical aspects of different tools integrated in ROS.

The workshop aims to provide a stimulating opportunity for young researchers and Ph.D. students. The participants will benefit from direct interaction and discussions with world leaders in ROS framework.

ORGANIZERS

  • Automation, Robotic and Artificial Vision (http://www.aurova.ua.es)
  • University of Alicante (http://www.ua.es/)

ROS-RM SPONSORS

  • Valencia Regional Government (PROMETEO 2013/085).

ENDORSED BY:

MORE INFORMATION

From Jimmy Paulos to be presented at ICRA 2014




We will be presenting "Self-Assembly of a Swarm of Autonomous Boats
into Floating Structures" in the Monday session on Cellular and
Modular Robotics.  We present assembly planning techniques and scaled
experiments towards a vision for swarms of shipping-container sized
robotic boats which assemble man-made floating islands, hospitals, or
seaports on demand.  In our experiments, a poolside PC running the ROS
Master provided high level instructions and localization data to a
fleet of miniature boats running ROS nodes on Gumstix
computer-on-modules.

This work was a collaboration between the laboratories of Professor
Mark Yim and Professor Vijay Kumar of the GRASP Robotics Lab at the
University of Pennsylvania.  A link to videos is below, along with the
paper authors and title to appear.

http://modlabupenn.org/tactically-expandable-marine-platform-t-e-m-p/

Ian O'Hara, James Paulos, Jay Davey, Nick Eckenstein, Neel Doshi,
Tarik Tosun, Jonathan Greco, Jungwon Seo, Matthew Turpin, Vijay Kumar,
Mark Yim

Self-Assembly of a Swarm of Autonomous Boats into Floating Structures

ROS-related events at IAS 2014 conference

| No Comments | No TrackBacks
From Matteo Munaro

Dear all,

I'd like to draw your attention to the upcoming Intelligent Autonomous 
Systems (IAS) conference, to be held in Padova in July 2014. The 
conference is focused on the topic "Bring autonomous robots into 
industrial production", and is connected to several events about ROS and 
robot perception, including the following workshops:

- 3D Robot Perception with Point Cloud Library (PCL)
- ROS Industrial in European Research Projects
- Recent Advances in Agricultural Robotics
- Advances in Marine Robotics Applications
- Connected Service Robotics for Telecommunications Operators

and a tutorial on the Point Cloud Library (PCL).

You can find further information on the conference web page:

http://www.ias-13.org/

and on the specific section about workshops and tutorials:

http://www.ias-13.org/workshops-and-tutorials/

The deadline for early registration is today.

Best regards,
Matteo Munaro

Indigo Development Update

| No Comments | No TrackBacks
We're closing in on the Indigo Release quickly. Today our last package was released to fill out ros desktop and desktop full. There are a few packages which need to be fixed to make the release ready for testing. In preparation for the upcoming release we already have 430 packages released and building on the buildfarm. We expect many more to have been released by the final release planned for later this month. 

Also as a reminder coming up in June is ICRA and ROSKong. If you are presenting a paper in which you used ROS and think other ROS users would be interested, we would like to feature it on  ROS News blog please email us at ros-news@googlegroups.com 

And one last reminder that the Indigo Igloo T-Shirt is available for only 19 hours more hours. We've had a great response at the end of the campaign and want to make sure the you don't miss your opportunity. 

announcing matlab_rosbag v0.4

| No Comments | No TrackBacks
From Benjamin Charrow via ros-users@

I've released v0.4 of matlab_rosbag, a library for processing ROS bags in matlab.  In addition to some bugfixes the new version includes:

1) a class to work with the tf tree (transform queries, list frames, etc.) using stored tf or tf2 messages
2) ability to filter messages by time and get access to bag start/stop time.
3) Autocomplete paths to bags using ros.Bag.load()

Download for mac and linux:

Repo:

Announcing ROS support for LazeeEye

| No Comments | No TrackBacks
From Heuristic Labs via ros-users@

I'm writing to make you aware of an exciting new Kickstarter project, the "LazeeEye": http://kck.st/1gVCcrB

lazeePi.jpg

LazeeEye takes your existing smartphone and turns it into a depth camera using laser illuminator hardware and a stereo vision processing app. 

The goal is to produce hardware and software that can bring 3D perception to devices that have low-power/low-weight processing and a high-resolution, such as what you would find in your smartphone.

You as a ROS user can be particularly excited about using your existing smartphone in robotics applications. In fact, the inspiration for the LazeeEye was for lightweight aerial robots, where we were constrained by the redundancy, inefficiency, cost, and lack of portability of existing 3D sensors.

For more information, or to consider supporting the project, please check out the Kickstarter page: http://kck.st/1gVCcrB, and don't hesitate to spread the word!

I just wanted to affirm that ROS drivers will be made available for LazeeEye, including image capture through rosjava (if on Android). We'll make every attempt possible to match existing conventions for the RGB-D processing pipeline, so as to seamlessly replace your legacy Kinects and Xtions : )

Also wanted to mention hardware support for LazeePi (LazeeEye on a Raspberry Pi), and its camera module.

From ROS-Industrial

lease find the program and agenda for the ROS-Industrial Basic Developers' Training Class May 19-20, 2014. This class, similar to the one held in June 2013, is geared toward individuals with a programming background who seek to learn to compose their own ROS nodes (now in ROS Hydro). The first day will be in the classroom focused on background ROS/ROS-I skills, and the second day will be devoted to a lab programming exercise: a collision-free pick-and-place application (video below) with real industrial robot hardware. Bring a laptop to the class with the training exercise Virtual Machine pre-installed.

Register here: http://rosindustrial.org/training-registration.



From Sammy Omari of Skybotix AG and ETHZ ASL via ros-users@

We are 
happy to announce an Early Adopter Program for the visual-inertial sensor that is developed by the Autonomous Systems Lab, ETH Zurich and Skybotix AG.

vi-sensor-front.jpg

The VI-Sensor is a light-weight, fully-calibrated and time-synchronized hardware platform for visual-inertial odometry applications, e.g. for UAV navigation in cluttered environments. It features a high-quality global shutter HDR stereoscopic camera and an industrial-grade inertial measurement system. A detailed spec-sheet can be found here.


The Early Adopter package includes:

- VI-Sensor (factory calibrated: intrinsic, spatial & temporal inter-sensor)

- Linux driver (ROS enabled)

- SDK with example code for working with image and IMU data in openCV and/or ROS 

- Ready for stereo visual odometry framework viso2 

- Power supply cable kit

- Access to the Wiki page 

- Driver and firmware updates

- VI-Sensor protection case

 

A detailed spec-sheet can be found here.

 

Price: EUR 3'900.00 (*)


The program addresses research groups around the world that are eager to get their hands on the sensor early.

If you are interested in receiving an Early Adopter quotation, please contact us via sales@skybotix.com indicating your invoice and shipping address.

Please submit your purchase order until May 31th. Purchase orders received after this date cannot be taken into account for the Early Adopter Program.

https://ci3.googleusercontent.com/proxy/8CBWEZYl_gju-O0mEKjDNw0Eh_qIbYUu1oZBKfZqOypmLO1gU9NfBBUnKK5HrwoN-VKG8iQn_PvQpZDlbxq0IwVL9dQOy_HcGJ0=s0-d-e1-ft#https://mail.google.com/mail/u/0/images/cleardot.gif

We are looking forward to hearing from you.


Find this blog and more at planet.ros.org.


Please submit content to be reviewed by emailing ros-news@googlegroups.com.

Monthly Archives

About this Archive

This page is an archive of entries from May 2014 listed from newest to oldest.

April 2014 is the previous archive.

June 2014 is the next archive.

Find recent content on the main index or look in the archives to find all content.