September 01, 2014
Multi robot Teleoperation in Gazebo



Finally, different type of robots in Gazebo are under control with Concert. See teleoperating multiple robots in Gazebo with concert teleop app


by Jihoon Lee (noreply@blogger.com) on September 01, 2014 05:06 AM

August 28, 2014
Breaking the Physics of ROS
Just as the universe has its rules written down in physics, ROS has a few of its own too. If there was a likely candidate, it would be the rule:

There can be only one node per process

Though not obvious...it is possible to break this golden rule of the ROS universe with a little bit of ecto:


ecto_ros.init(sys.argv, "foo", anonymous=False) # c++ cell initialisation
rospy.init_node("foo") # rospy initialisation for this ectoscript

$ [ WARN] [1409210302.714603865]: Shutdown request received.
$ [ WARN] [1409210302.714694875]: Reason given for shutdown: [new node registered with same name]

And providing a unique name for the ecto script (e.g. 'bar') then resolves the uniqueness problem and presto, you have two nodes. I suspect if we were to create universes, we would be hard pressed to be as infallible as the creator of ours!

by Daniel Stonier (noreply@blogger.com) on August 28, 2014 08:01 AM

August 27, 2014
ROS Dependency Analysis Graph
From Ben Arvey via @ros-users

Hello, my name is Ben Arvey and I've been developing a set of analysis tools for ROS under the direction of Dr. Bill Smart. Our lab is giving a talk at ROSCon concerning our research, of which this is one aspect.


I'm looking for some preliminary feedback from developers. Any information about what you need in an analysis tool would be very helpful!

Here's the web app (Chrome works best):
http://http404error.github.io/roseco/graph.html?id=ros.json

Here's a page with some basic documentation info and suggestions for feedback:

by Tully Foote on August 27, 2014 08:18 PM

August 26, 2014
TurtleBot arm is back on indigo!
TurtleBot: every day a bit more indigo! We have updated most of the turtlebot_arm stack to work with Indigo and MoveIt!. It’s released as version 0.3.x (while fuerte version was 0.2.x). The big missing parts are the turtlebot_arm_interactive_markers that are not really needed now because you can do the same with the RViz moveit plugin, and the turtlebot_block_manipulation, that relays on deprecated stuff. Instead, we added a simple pick and place demo to show the arm operating with MoveIt! Hopefully, we'll be able to add more sophisticated demos (like a MoveIt! version of the block manipulation demo).... as soon as we find time to do so!

We also updated the documentation and tutorials, but pretty sure there're many errors and fuerte-like staff that doesn't hold anymore, so please, please, please let us know (or better correct yourself!) any mistakes you find.

Enjoy it!


by jorge (noreply@blogger.com) on August 26, 2014 09:06 AM

August 25, 2014
Experimental Indigo binaries for ARM
From Austin Hendrix via ros-users@

I'm pleased to announce that I have experimental binary builds of ROS available for ARM and ready for wider testing.

I have builds of the ros-core and ros-base metapackages, along with PCL and the navigation stack.

Notably missing are the OpenNi drivers, rviz, moveit, and many other packages. I'm planning to work on them, but they're not currently available.

Installation instructions are available at http://wiki.ros.org/indigo/Installation/UbuntuARM , and the full build status is available at http://packages.namniart.com/repos/status/indigo.html (green packages are built, red packages failed to build).

Just to clarify, these are builds of ROS Indigo targeted at Ubuntu Trusty (14.04) running on armhf processors

by Tully Foote on August 25, 2014 08:29 PM

August 20, 2014
ROS Art
from the Shadow Robot Company

Over at Queen Mary University London, they run a postgraduate course in Media and Arts Technology, and one of the students there, Ed Burton, created this innovative performance using ROS and the RoNeX.

This is still a work in progress but here's a  teaser of Ed's work, using ROS for a beautiful project:



And here is a quick peak at his RoNeX installation:



by Ugo Cupcic on August 20, 2014 11:54 PM

Lasers, anyone?

We're happy to announce that SICK has donated hardware to OSRF for the ROS community to use in testing and development. We're now the proud owners of one each of the following laser scanners: TiM551, LMS111, and LMS511.

tim551.jpg lms111.jpg lms5xx.jpg

This generous donation was motivated by SICK's longstanding commitment to robotics, combined with their desire to see first-class support for their sensors in ROS. The LMS series is best known for providing reliable LiDAR data in tough conditions including the DARPA Urban Challenge and Boston Dynamics' LS3 AlphaDog. The TiM is a smaller version designed for great performance with low power consumption in indoor or outdoor environments.

The sensors are available for loan to members of the ROS community who want to use them for testing and development, and especially for improvement of the ROS drivers and associated tools. If you'd like to borrow one of these devices to try it out in your project, please let us know: info@osrfoundation.org

Thank you to our friends at SICK, and we look forward to even more robotics applications that are enabled by SICK sensors and ROS software!

by Tully Foote on August 20, 2014 05:18 PM

August 18, 2014
STDR Simulator v0.2 released
From Manos Tsardoulias 

Dear all,

We are happy to announce that the current version of STDR Simulator is 0.2! The changes compared to the v0.1.3 follow:

  • Several bugs were fixed
  • Code was refactored
  • Lidar resources were added
  • Added support of:
    • RFID tags and Readers
    • Thermal sources / sensors
    • CO2 sources / sensors
    • Sound sources / sensors

Special thanks to Sergey Alexandrov and Scott K Logan for code contributions.

Our future plans:
  • Make the sensor measurements more realistic
  • Add simulated battery in robots
  • Detection of robots footprint via other robots' distance sensors
  • Add a simple physics engine
It would be excellent if any of you would like to contribute either by code developmentissue reporting or features request!

Best,
The STDR team.

by Tully Foote on August 18, 2014 04:10 PM

August 15, 2014
Autonomous Vehicle Engineer and Intern Positions at Auro Robotics


from Jit Ray Chowdhury via ros-users@


Autonomous Vehicle Engineers and Interns


Job Summary:


Software and System Development for driverless car modules. 

You will be enganged in development, integration and testing of perception, motion planning and control systems involved in an autonomous vehicle. 

We are looking for roboticists and other passionate to join our journey in taking robotics from labs to masses. 

Detailed Job Description  

  1.  Autonomous Vehicle Software Engineer @ http://goo.gl/lALUHu 
  2.  Autonomous Vehicle Associate Engineer @ http://goo.gl/YNZ4nS
  3.  Autonomous Vehicle Intern @ http://goo.gl/3XMncG 

Skills in need:

  • Good Programming skills in C++ 
  • Experience with LINUX 
  • Familiarity with ROS  and autonomous robot concepts is a plus
  • Proven Expertise in one of the fields is a plus: Image Processing, SLAM(Localization and Mapping), Controls, Path Planning. 

About us

We are Auro Robotics, a high-tech robotics startup building the first driverless car from India. The venture is a spin-off from a research group of IIT Kharagpur working on autonomous vehicles since the past 4 years. We are presently helping some of the leading automobile companies in building autonomous driving systems and ADAS for their cars.

Team Previous Experience: CMU, Qualcomm 

Here is a video of our self driving car demo.

Our profile @ https://angel.co/auro-robotics 


How to Apply

Send your resume at contact@aurobots.com or give us a call at +91-9002712425 (Srinivas) , +91-8588865823 (Nalin) , +91-9143299599 (Jit)

 

 

 Limited Positions, so hurry up!!


by Ugo Cupcic on August 15, 2014 08:41 PM

August 14, 2014
New Package: Behavior Trees pi_trees
From Patrick Goebel via ros-users@

Hello ROS Fans,

I have created a ROS package implementing behavior trees called pi_trees.  It is written in Python and is modeled after the most excellent executive_smach package (though without the visualizer).  The only documentation I have so far is a PDF which was copied out of a chapter from my latest ROS book mentioned earlier on the list.

The package consists of a standalone Python module and a ROS wrapper for connecting to ROS topics, services and actions.

Hopefully someone will find the package useful.  And if anyone can find problems with the code or a better way of doing things, I'd love to hear it.

by Tully Foote on August 14, 2014 06:45 PM

August 12, 2014
ROS Meetup Chicago!

From Krystian Gebis


ROS Meetup Chicago! Calling all Chicago-land ROS Users!

 

For the past year, University of Illinois at Chicago Engineering Design Team (EDT) has been implementing ROS in all of its autonomous robots. With the progress that has been made with the understanding and implementation of ROS, the idea of hosting a group in Chicago that would be open to all that are interested in ROS was apparent. By creating this group, everyone could help make significant advancements in the field of robotics through the exchange of ideas.

 

All ROS users are welcome! Here is a link to the Meetup website: http://www.meetup.com/ROS-Robot-Operating-System-in-Chicago/

 

First Meetup will be held on August 27th, 2014 at the University of Illinois at Chicago Science and Engineering office building (SEO).

 

Location and funding are both sponsored by the University of Illinois at Chicago College of Engineering.


chicago_robotics_meetup.jpg

by Tully Foote on August 12, 2014 04:27 PM

August 11, 2014
Reminder: ROSCon early registration deadline is Friday

Early registration for ROSCon 2014 closes this Friday, August 15th. Register today to confirm your spot, save money, and ensure that you get a ROSCon t-shirt.

In addition, the deadline for the reduced rate rooms at the Palmer House is next Thursday, August 21st. Book your room today.

ROSCon 2014 logo

We'd like to thank our generous sponsors, especially: Qualcomm, Clearpath Robotics, Rethink Robotics, and Cruise Automation.

by Brian Gerkey on August 11, 2014 11:38 PM

ROS-I Updates: FTP Status and ROSCon

Checkout the following ROS-Industrial news items:

  • We’ve added a new page to the ROS-Industrial website called FTP Status. It provides descriptions, media, and links related to ROS-Industrial Consortium Focused Technical Projects. Browse the list of “brewing” projects to see if any topics align with needs at your organization.
  • The agenda for ROSCon is posted. Organized by OSRF, ROSCon is the annual meeting of all ROS software developers, not just those contributing to ROS-Industrial. It takes place September 12-13 in Chicago. Take this opportunity to register. The following sessions will be of particular interest to the ROS-Industrial community:
    • ROS 2.0: Developer preview: Dirk Thomas, William Woodall, Esteve Fernandez
    • Next-generation ROS: Building on DDS: Dirk Thomas, William Woodall, Esteve Fernandez
    • ROS-Industrial calibration: Chris Lewis
  • We are planning to host a ROS-Industrial Community meeting at ROSCon on Sept. 13, 3:30 to 5 PM CST. We will present an update on the ROS-Industrial Consortia (Americas/EU) and the results of the ROS-Industrial roadmapping effort.
  • ROSCon is happening the Friday and Saturday between IMTS and IROS, so consider making your trip a double (or triple) header.

by Paul Hvass on August 11, 2014 01:50 AM

August 08, 2014
New Book: ROS By Example: Packages and Programs for Advanced Robot Behaviors
From Patrick Goebel via ros-users@

Hello ROS users,

I am pleased to announce that Volume 2 of ROS By Example is now available on Lulu.com.

rosbyexample2.jpg
The main chapter headings are as follows:

1. Scope of this Volume
2. Installing the ros-by-example Code
3. Task Execution using ROS
4. Creating a URDF Model for your Robot
5. Controlling Dynamixel Servos: Take 2
6. Robot Diagnostics
7. Dynamic Reconfigure
8. Multiplexing Topics with mux and yocs
9. Head Tracking in 3D
10. Detecting and Tracking AR Tags
11. Arm Navigation using MoveIt!
12. Gazebo: Simulating Worlds and Robots
13. Rosbridge: Building a Web GUI for your Robot
Appendix: Plug and Play USB Devices for ROS

A full table of contents can be found here.

Note that this first release is written for ROS Hydro and programming examples are written in Python.

The print version should be available by the end of August 2014.

by Tully Foote on August 08, 2014 05:08 PM

August 05, 2014
New Package: rqt_ez_publisher
From Takashi Ogura via ros-users@

I released rqt_ez_publisher for hydro and indigo.
rqt_ez_publisher automatically creates GUI for publishing topics.
(It is a plugin for rqt, which is standard GUI tool of ROS.)

It is similar to rqt_reconfigure, which is for parameters, but rqt_ez_publisher
is for topics.
Although rqt_reconfigure requires some config files,
rqt_ez_publisher needs nothing. All you have to do is select a topic from list.

This video shows how it works: https://www.youtube.com/watch?v=oajlOQfqJiw


For more detail, please read wiki page.

Any feedback is welcome. Please make a issue at GitHub.

by Tully Foote on August 05, 2014 05:20 PM

Nissan - ROS - Software Developer Opening

From  Adam Little via ros-users@

Link to the job offer

Job Summary

Under supervision of the Researcher (Principle, Sr, or Researcher), designs, develops, and installs software solutions in areas such as computer vision, sensor fusion, machine learning, object tracking, motion planning and human-machine interaction within 3 primary fields of focus:

1.  Autonomous Driving

2.  Connected Mobility Services

3.  Human-Machine Interfaces

Job Functions

The following job function statements describe the general nature and level of work being performed. They are not to be construed as an exhaustive list of all responsibilities, duties and skills required of personnel so classified. The job function statements reflect expectations of the fully trained, proficient incumbent who meets all performance criteria.

1.    Writes computer language code for one more of the following: 1) to control or improve autonomous vehicle operation; 2) to connect vehicles to other technology (smartphones, the cloud, other cars, and traffic infrastructure, etc.).

2.    Collaborates in depth with other Silicon Valley Partners and seeks to understand integrate advanced technologies, ideas, and trends.

3.    Determines operational feasibility by evaluating analysis, problem definition, requirements, solution development, and proposed solutions.

4.    Documents and demonstrates solutions by developing documentation, flowcharts, layouts, diagrams, charts, code comments and clear code.

5.    Improves operations by conducting systems analysis; recommending changes in policies and procedures.

6.    Updates job knowledge by studying state-of-the-art development tools, programming techniques, and computing equipment; participating in educational opportunities; reading professional publications; maintaining personal networks; participating in professional organizations.

7.    Implements advanced algorithms from the robotics and artificial intelligence domains. Develops software solutions by studying information needs; conferring with users; studying systems flow, data usage, and work processes; investigating problem areas; following the software development lifecycle.

8.    Protects operations by keeping information confidential.

9.    Pushes relentlessly to make the research Nissan Research team among the most advanced and well respected teams in the world. As necessary, performs other related duties of which the above are representative.



Minimum Qualifications

The following qualification statements reflect the minimum skills and abilities required of the qualified applicant.

Job Knowledge and Skills:

  1. Thorough knowledge of software development/engineering.

  2. Ability to interpret technical contract requirements.

  3. Proficiency using programming languages such as 'C++; Python, Java, Maltlab, graphics or other developmental software are helpful.

  4. Ability to develop software in a UNIX, LINUX, SVN/Mercurial/git, Integrated Development Environments (IDEs) or other PC environment.

  5. Thorough knowledge of ROS, Boost, and Qt are preferred. Ability to effectively communicate verbally and in writing, interface with customers, subcontractors, and vendors. Ability to solve complex and difficult software problems.

Experience:

At least 4 years of relevant experience with BS degree; with MS degree, will consider related research or graduate level class projects related to Nissan Research Center-SV scope.

Supervisory Experience: None required. Project leadership preferred.

Education: BS Computer Science; MS Computer Science preferred

Computer Skills: In addition to job knowledge and skills listed above, general knowledge of standard office applications required.



Physical Requirements

The physical requirements described below are representative of those an employee must normally meet to successfully perform the essential functions of this job. Reasonable accommodations may be made to enable otherwise qualified individuals with disabilities to perform the essential job functions.

Travel:

Occasional day or overnight travel

by Ugo Cupcic on August 05, 2014 08:31 AM

August 01, 2014
ROSCon Sponsors Announced
We'd like to thank the many companies who have supported ROSCon this year through sponsorship. The support of our sponsors helps us provide the highest quality meeting possible while keeping the registration fees down. Below are our sponsors for this year. If you're not familiar with what they are doing in the ROS community come by and talk with them at ROSCon.  

As a quick reminder if you have not already registered. Early registration closes on August 15th. You can register here.













It's still possible to become a sponsor. If you'd like to lend your support to ROSCon, please contact us at roscon-2014-oc@osrfoundation.org.

by Tully Foote on August 01, 2014 10:05 PM

Turtlebot Navi - What You Should Be Getting Out Of It
When you start with the navistack it's not exactly clear what performance you can and should expect from it. Expectations are that it is good (hey, pr2 used this 24/7!), but you also hear that it isn't a solution that works for all use cases and might especially struggle with non PR2 style use cases (e.g. non-holonomic configurations) very well.

The following videos demonstrate what you can and should expect from a turtlebot in indigo as it moves, at speed, through a changing world. Start them together and you should be able to see them in stereo (err sync)!



These changes were mostly a result of tuning the velocity and acceleration parameters to match your robot as well as the local planning parameters to fit your use case (reactive distances, planning bias etc).

See dwa_local_planner_params.yaml for the reference parameter configuration.

by Daniel Stonier (noreply@blogger.com) on August 01, 2014 02:00 AM

July 30, 2014
ROSCon 2014 Program Posted and Registration Open!
We're happy to announce the program for ROSCon 2014 has been posted and that registration is now open.

The early registration deadline is August 15, 2014.

ROSConChicago_Layered-200x300.png

The program fills two days with talks on applications of ROS from outer space to inside mines as well as overviews of useful tools for both research and product development. There will also be presentations on upcoming development and ongoing efforts to make ROS available on more platforms. 

In addition to the talks ROSCon will feature two lightning talk sessions and two birds of a feather sessions, all organized on-site. The lightning talks are an opportunity for you to have 3 minutes to present a topic of your choice: introduce a new project, recruit collaborators or users to an existing project, announce a product, whatever you like.

Immediately follow the lightning talks are birds of a feather sessions, which are an opportunity to propose and find people to talk about topics of interest to subgroups at the conference. This will be a mostly unstructured time with topics proposed on site and groups forming organically. 

Before you come to ROSCon, think ahead about any topic you'd like to propose for the BoF sessions and have some slides ready to present a lightning talk (3 slides or fewer).

We look forward to seeing you in Chicago in September!

by Tully Foote on July 30, 2014 02:04 AM

July 29, 2014
New Package: MAVLink to ROS generator
From Pedro Marques da Silva via ros-users@

Hi all :)


I am pleased to announce that I created a kind of Mavlink generator for ROS.

You can see the pre-release here: https://github.com/posilva/mav2rosgenerator and download from here:https://pypi.python.org/pypi/mav2rosgenerator/0.1.2

I hope this could be helpful to the ROS guys to start using mavlink to control robots.

Best 

by Tully Foote on July 29, 2014 07:10 PM

July 28, 2014
New 1D ToF Range sensor looking for testing
From Luis Rodrigues via ros-users@

I'm one of the developers of a new ToF baser 1D ranging sensor, 
that was created in one of our research projects with CERN.

We've just finished the ROS module and would like to find people in the ROS 
community that would be willing to test it/use for their projects. 

The sensor is 20g, small and the refresh rate is up to 1kHz.

We have it on sale here: www.teraranger.com/product/teraranger-one  
but for people which can provide feedback we can offer a substantial discount.

If anyone here is interested in testing it/knowing more, please contact me at: luis.rodrigues@terabee.com 

by Tully Foote on July 28, 2014 08:33 PM

July 24, 2014
Ologic Announces integration between ROS and Project Tango
From Ted Larson

OLogic has been involved with Project Tango since the very beginning of the project, however we have always had our eyes on the goal of utilizing it for robotics applications.  The solution to the problem of indoor localization and mapping is one of several areas Project Tango is focused on, and when you overlap this with robotics, it is a perfect fit.    Google has provided several SDK's for working with project Tango in either Java, C, or Unity, and has shown some impressive demos using sparse mapping under Unity, to navigate around 3D virtual worlds, or games on the device.  The phone has the ability to perform Visual Inertial Odometery (VIO), and we wanted to extend this to use within the context of ROS.  We wrote some ROSJava Nodes that use the SDK to access the VIO to publish pose, transform frames (tf), and odometry messages.  This allowed us display a URDF of a floating phone on a map, in RViz and show the position information of where the phone is located in the office, in near-real-time.  We have several demo videos of our summer intern, roaming around the office with a Project Tango phone, while we visualize the phone's position and orientation in 3D space.  It is just a starting point for all the things we want to do with Project Tango and ROS, but we have a good framework in place to add other nodes into the puzzle, and get to the point soon where we will be able to navigate a robot around the office with only a Project Tango phone for the brains.  The project is available via a public project on Github https://github.com/ologic/Tango and all the build instructions for getting it running on a Tango device is there via the Wiki.  There are lots of helpful hints and tips on building 3D maps using the Tango Mapper application (the one that Google provides), and then taking those maps and bringing them into ROS to try to navigate a space using an existing ROS robot.   We will be adding to the project continually, as it is still definitely a work-in-progress.


by Tully Foote on July 24, 2014 09:27 PM

July 22, 2014
ROS Indigo Igloo Released!

indigoigloo_600.png

Hi Everyone,


We're pleased to announce the official release of ROS Indigo Igloo! This is the first LTS release of ROS; it will be supported until April 2019 in parallel with Ubuntu Trusty Tahr. It will also be available for Saucy Salamander during its duration of support from Canonical as outlined in the ROS Distributions page.


Thanks to our many active maintainers it can be seen on the Indigo Igloo build status page that 643 packages have already been released for Indigo Igloo. And we expect this number to continuously grow over the lifetime of the distribution.


The main focus of Indigo development has been to clean up the core packages in preparation for the LTS support cycle. Efforts have included integrating the ROS packages with packages officially taken up into the upstream Debian and Ubuntu repositories such as console_bridge, urdfdom, and OpenCV.


With the release of Indigo, development will be transitioned forward to the next ROS release, Jade Turtle.  ROS Jade Turtle will be targeted for release in May 2015, following the new 12 month release cycle. Also with the beginning of development for Jade Turtle, Groovy Galapagos will reach its end-of-life. Releases into Groovy have been winding down and in the near future the build infrastructure for Groovy will be taken offline.


To get started with Indigo see the installation page. A summary of updates for packages can be found in the migration guide.


Although Indigo is now officially available, ROS distributions are living entities built on the contributions of the community.  Hydro Medusa has almost doubled the number of packages available since it was initially released 9 months ago, and Indigo is tracking a similar trajectory through it's development phases.


We'd also like to take a moment to thank the many contributors to the community who improve documentation on the wiki as well as answering questions and moderating on answers.ros.org. One of the things that distinguishes ROS is the large helpful community. We now have dozens of moderators and thousands of contributors, thank you all for your contributions!


Details of the latest updated packages in Indigo are listed below as well as updated packages for Hydro.


Your ROS Indigo Igloo Release Team


Updates to indigo


Added Packages [43]:

 * ros-indigo-ax2550: 0.1.1-0

 * ros-indigo-gazebo-ros-control: 2.4.4-0

 * ros-indigo-image-exposure-msgs: 0.9.2-0

 * ros-indigo-nav2d: 0.1.3-0

 * ros-indigo-nav2d-exploration: 0.1.3-0

 * ros-indigo-nav2d-karto: 0.1.3-0

 * ros-indigo-nav2d-localizer: 0.1.3-0

 * ros-indigo-nav2d-msgs: 0.1.3-0

 * ros-indigo-nav2d-navigator: 0.1.3-0

 * ros-indigo-nav2d-operator: 0.1.3-0

 * ros-indigo-nav2d-remote: 0.1.3-0

 * ros-indigo-nav2d-tutorials: 0.1.3-0

 * ros-indigo-ntpd-driver: 1.0.1-0

 * ros-indigo-orocos-kinematics-dynamics: 1.3.0-0

 * ros-indigo-pointgrey-camera-driver: 0.9.2-0

 * ros-indigo-rosh: 1.0.5-0

 * ros-indigo-rosh-common: 1.0.1-0

 * ros-indigo-rosh-core: 1.0.5-0

 * ros-indigo-rosh-desktop: 1.0.2-0

 * ros-indigo-rosh-desktop-plugins: 1.0.2-0

 * ros-indigo-rosh-geometry: 1.0.1-0

 * ros-indigo-rosh-robot: 1.0.1-0

 * ros-indigo-rosh-robot-plugins: 1.0.1-0

 * ros-indigo-rosh-visualization: 1.0.2-0

 * ros-indigo-roshlaunch: 1.0.5-0

 * ros-indigo-serial-utils: 0.1.0-0

 * ros-indigo-shadow-robot: 1.3.2-0

 * ros-indigo-sr-description: 1.3.2-0

 * ros-indigo-sr-example: 1.3.2-0

 * ros-indigo-sr-gazebo-plugins: 1.3.2-0

 * ros-indigo-sr-hand: 1.3.2-0

 * ros-indigo-sr-hardware-interface: 1.3.2-0

 * ros-indigo-sr-mechanism-controllers: 1.3.2-0

 * ros-indigo-sr-mechanism-model: 1.3.2-0

 * ros-indigo-sr-moveit-config: 1.3.2-0

 * ros-indigo-sr-movements: 1.3.2-0

 * ros-indigo-sr-robot-msgs: 1.3.2-0

 * ros-indigo-sr-self-test: 1.3.2-0

 * ros-indigo-sr-standalone: 1.3.2-0

 * ros-indigo-sr-tactile-sensors: 1.3.2-0

 * ros-indigo-sr-utilities: 1.3.2-0

 * ros-indigo-statistics-msgs: 0.9.2-0

 * ros-indigo-wfov-camera-msgs: 0.9.2-0



Updated Packages [94]:

 * ros-indigo-arbotix: 0.9.2-0 -> 0.10.0-0

 * ros-indigo-arbotix-controllers: 0.9.2-0 -> 0.10.0-0

 * ros-indigo-arbotix-firmware: 0.9.2-0 -> 0.10.0-0

 * ros-indigo-arbotix-msgs: 0.9.2-0 -> 0.10.0-0

 * ros-indigo-arbotix-python: 0.9.2-0 -> 0.10.0-0

 * ros-indigo-arbotix-sensors: 0.9.2-0 -> 0.10.0-0

 * ros-indigo-compressed-depth-image-transport: 1.9.0-0 -> 1.9.1-0

 * ros-indigo-compressed-image-transport: 1.9.0-0 -> 1.9.1-0

 * ros-indigo-flir-ptu-description: 0.1.3-0 -> 0.1.4-0

 * ros-indigo-flir-ptu-driver: 0.1.3-0 -> 0.1.4-0

 * ros-indigo-flir-ptu-viz: 0.1.3-0 -> 0.1.4-0

 * ros-indigo-gazebo-msgs: 2.4.3-1 -> 2.4.4-0

 * ros-indigo-gazebo-plugins: 2.4.3-1 -> 2.4.4-0

 * ros-indigo-gazebo-ros: 2.4.3-1 -> 2.4.4-0

 * ros-indigo-gazebo-ros-pkgs: 2.4.3-1 -> 2.4.4-0

 * ros-indigo-image-transport-plugins: 1.9.0-0 -> 1.9.1-0

 * ros-indigo-mavlink: 1.0.9-5 -> 1.0.9-7

 * ros-indigo-mavros: 0.5.0-0 -> 0.6.0-0

 * ros-indigo-message-filters: 1.11.6-0 -> 1.11.7-0

 * ros-indigo-mk: 1.11.2-0 -> 1.11.3-0

 * ros-indigo-opencv-candidate: 0.2.1-0 -> 0.2.3-0

 * ros-indigo-orocos-kdl: 1.2.2-2 -> 1.3.0-0

 * ros-indigo-python-orocos-kdl: 1.2.2-2 -> 1.3.0-0

 * ros-indigo-ros: 1.11.2-0 -> 1.11.3-0

 * ros-indigo-ros-comm: 1.11.6-0 -> 1.11.7-0

 * ros-indigo-ros-ethercat: 0.1.7-0 -> 0.1.8-0

 * ros-indigo-ros-ethercat-eml: 0.1.7-0 -> 0.1.8-0

 * ros-indigo-ros-ethercat-hardware: 0.1.7-0 -> 0.1.8-0

 * ros-indigo-ros-ethercat-loop: 0.1.7-0 -> 0.1.8-0

 * ros-indigo-ros-ethercat-model: 0.1.7-0 -> 0.1.8-0

 * ros-indigo-rosbag: 1.11.6-0 -> 1.11.7-0

 * ros-indigo-rosbag-storage: 1.11.6-0 -> 1.11.7-0

 * ros-indigo-rosbash: 1.11.2-0 -> 1.11.3-0

 * ros-indigo-rosboost-cfg: 1.11.2-0 -> 1.11.3-0

 * ros-indigo-rosbuild: 1.11.2-0 -> 1.11.3-0

 * ros-indigo-rosclean: 1.11.2-0 -> 1.11.3-0

 * ros-indigo-rosconsole: 1.11.6-0 -> 1.11.7-0

 * ros-indigo-rosconsole-bridge: 0.4.1-0 -> 0.4.2-0

 * ros-indigo-roscpp: 1.11.6-0 -> 1.11.7-0

 * ros-indigo-roscreate: 1.11.2-0 -> 1.11.3-0

 * ros-indigo-rosgraph: 1.11.6-0 -> 1.11.7-0

 * ros-indigo-roslang: 1.11.2-0 -> 1.11.3-0

 * ros-indigo-roslaunch: 1.11.6-0 -> 1.11.7-0

 * ros-indigo-roslib: 1.11.2-0 -> 1.11.3-0

 * ros-indigo-roslz4: 1.11.6-0 -> 1.11.7-0

 * ros-indigo-rosmake: 1.11.2-0 -> 1.11.3-0

 * ros-indigo-rosmaster: 1.11.6-0 -> 1.11.7-0

 * ros-indigo-rosmsg: 1.11.6-0 -> 1.11.7-0

 * ros-indigo-rosnode: 1.11.6-0 -> 1.11.7-0

 * ros-indigo-rosout: 1.11.6-0 -> 1.11.7-0

 * ros-indigo-rosparam: 1.11.6-0 -> 1.11.7-0

 * ros-indigo-rospy: 1.11.6-0 -> 1.11.7-0

 * ros-indigo-rosservice: 1.11.6-0 -> 1.11.7-0

 * ros-indigo-rostest: 1.11.6-0 -> 1.11.7-0

 * ros-indigo-rostopic: 1.11.6-0 -> 1.11.7-0

 * ros-indigo-rosunit: 1.11.2-0 -> 1.11.3-0

 * ros-indigo-roswtf: 1.11.6-0 -> 1.11.7-0

 * ros-indigo-rqt-action: 0.3.7-0 -> 0.3.8-0

 * ros-indigo-rqt-bag: 0.3.7-0 -> 0.3.8-0

 * ros-indigo-rqt-bag-plugins: 0.3.7-0 -> 0.3.8-0

 * ros-indigo-rqt-common-plugins: 0.3.7-0 -> 0.3.8-0

 * ros-indigo-rqt-console: 0.3.7-0 -> 0.3.8-0

 * ros-indigo-rqt-dep: 0.3.7-0 -> 0.3.8-0

 * ros-indigo-rqt-ez-publisher: 0.0.5-0 -> 0.2.0-0

 * ros-indigo-rqt-graph: 0.3.7-0 -> 0.3.8-0

 * ros-indigo-rqt-image-view: 0.3.7-0 -> 0.3.8-0

 * ros-indigo-rqt-launch: 0.3.7-0 -> 0.3.8-0

 * ros-indigo-rqt-logger-level: 0.3.7-0 -> 0.3.8-0

 * ros-indigo-rqt-msg: 0.3.7-0 -> 0.3.8-0

 * ros-indigo-rqt-plot: 0.3.7-0 -> 0.3.8-0

 * ros-indigo-rqt-publisher: 0.3.7-0 -> 0.3.8-0

 * ros-indigo-rqt-py-common: 0.3.7-0 -> 0.3.8-0

 * ros-indigo-rqt-py-console: 0.3.7-0 -> 0.3.8-0

 * ros-indigo-rqt-reconfigure: 0.3.7-0 -> 0.3.8-0

 * ros-indigo-rqt-service-caller: 0.3.7-0 -> 0.3.8-0

 * ros-indigo-rqt-shell: 0.3.7-0 -> 0.3.8-0

 * ros-indigo-rqt-srv: 0.3.7-0 -> 0.3.8-0

 * ros-indigo-rqt-top: 0.3.7-0 -> 0.3.8-0

 * ros-indigo-rqt-topic: 0.3.7-0 -> 0.3.8-0

 * ros-indigo-rqt-web: 0.3.7-0 -> 0.3.8-0

 * ros-indigo-sr-ronex: 0.9.14-0 -> 0.9.15-0

 * ros-indigo-sr-ronex-controllers: 0.9.14-0 -> 0.9.15-0

 * ros-indigo-sr-ronex-drivers: 0.9.14-0 -> 0.9.15-0

 * ros-indigo-sr-ronex-examples: 0.9.14-0 -> 0.9.15-0

 * ros-indigo-sr-ronex-external-protocol: 0.9.14-0 -> 0.9.15-0

 * ros-indigo-sr-ronex-hardware-interface: 0.9.14-0 -> 0.9.15-0

 * ros-indigo-sr-ronex-launch: 0.9.14-0 -> 0.9.15-0

 * ros-indigo-sr-ronex-msgs: 0.9.14-0 -> 0.9.15-0

 * ros-indigo-sr-ronex-test: 0.9.14-0 -> 0.9.15-0

 * ros-indigo-sr-ronex-transmissions: 0.9.14-0 -> 0.9.15-0

 * ros-indigo-sr-ronex-utilities: 0.9.14-0 -> 0.9.15-0

 * ros-indigo-theora-image-transport: 1.9.0-0 -> 1.9.1-0

 * ros-indigo-topic-tools: 1.11.6-0 -> 1.11.7-0

 * ros-indigo-xmlrpcpp: 1.11.6-0 -> 1.11.7-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

 * Ben Charrow

 * Dan Lazewatsky

 * David Gossow

 * Dirk Thomas

 * Dorian Scholz

 * Isaac Isao Saito

 * Isaac Saito

 * John Hsu

 * Jonathan Bohren

 * Julius Kammerl

 * Maintained by Dan Lazewatsky

 * Manos Nikolaidis

 * Michael Ferguson

 * Mike Purvis

 * MoveIt Setup Assistant

 * Orocos Developers

 * Ruben Smits

 * Scott K Logan

 * Sebastian Kasperski

 * Shadow Robot's software team

 * Takashi Ogura

 * Vincent Rabaud

 * Vladimir Ermakov

 * William Woodall


Updates to hydro

Added Packages [24]:
 * ros-hydro-catkinize-this: 0.1.0-2
 * ros-hydro-easy-markers: 0.1.0-2
 * ros-hydro-laser-filtering: 0.0.1-0
 * ros-hydro-leg-detector: 1.0.4-0
 * ros-hydro-libpointmatcher: 1.2.0-0
 * ros-hydro-manifest-cleaner: 0.1.0-2
 * ros-hydro-map-laser: 0.0.1-0
 * ros-hydro-multisense-description: 1.0.0-1
 * ros-hydro-nlopt: 1.0.29-0
 * ros-hydro-object-recognition-clusters: 0.1.0-0
 * ros-hydro-orocos-kinematics-dynamics: 1.3.0-0
 * ros-hydro-people-tracking-filter: 1.0.4-0
 * ros-hydro-people-velocity-tracker: 1.0.4-0
 * ros-hydro-range-sensor-layer: 0.2.0-0
 * ros-hydro-rosbaglive: 0.1.0-2
 * ros-hydro-rosh-desktop: 1.0.2-0
 * ros-hydro-rosh-desktop-plugins: 1.0.2-0
 * ros-hydro-rosh-visualization: 1.0.2-0
 * ros-hydro-roswiki-node: 0.1.0-2
 * ros-hydro-rqt-ez-publisher: 0.2.0-0
 * ros-hydro-simple-robot-control: 0.0.2-0
 * ros-hydro-social-navigation-layers: 1.0.4-0
 * ros-hydro-speech-recognition-msgs: 1.0.29-0
 * ros-hydro-wu-ros-tools: 0.1.0-2


Updated Packages [159]:
 * ros-hydro-amcl: 1.11.9-0 -> 1.11.10-0
 * ros-hydro-assimp-devel: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-base-local-planner: 1.11.9-0 -> 1.11.10-0
 * ros-hydro-bayesian-belief-networks: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-bond: 1.7.13-0 -> 1.7.14-0
 * ros-hydro-bond-core: 1.7.13-0 -> 1.7.14-0
 * ros-hydro-bondcpp: 1.7.13-0 -> 1.7.14-0
 * ros-hydro-bondpy: 1.7.13-0 -> 1.7.14-0
 * ros-hydro-camera-umd: 0.2.1-0 -> 0.2.4-0
 * ros-hydro-capabilities: 0.1.1-0 -> 0.2.0-0
 * ros-hydro-carrot-planner: 1.11.9-0 -> 1.11.10-0
 * ros-hydro-checkerboard-detector: 0.1.7-0 -> 0.1.11-0
 * ros-hydro-clear-costmap-recovery: 1.11.9-0 -> 1.11.10-0
 * ros-hydro-collada-urdf-jsk-patch: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-costmap-2d: 1.11.9-0 -> 1.11.10-0
 * ros-hydro-default-cfg-fkie: 0.3.11-0 -> 0.3.12-0
 * ros-hydro-depth-image-proc-jsk-patch: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-downward: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-dwa-local-planner: 1.11.9-0 -> 1.11.10-0
 * ros-hydro-dynamic-tf-publisher: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-eus-assimp: 0.1.4-0 -> 0.1.6-0
 * ros-hydro-euscollada: 0.1.4-0 -> 0.1.6-0
 * ros-hydro-euslisp: 1.1.19-0 -> 1.1.21-0
 * ros-hydro-face-detector: 1.0.3-0 -> 1.0.4-0
 * ros-hydro-fake-localization: 1.11.9-0 -> 1.11.10-0
 * ros-hydro-ff: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-ffha: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-flir-ptu-description: 0.1.3-0 -> 0.1.4-0
 * ros-hydro-flir-ptu-driver: 0.1.3-0 -> 0.1.4-0
 * ros-hydro-flir-ptu-viz: 0.1.3-0 -> 0.1.4-0
 * ros-hydro-geneus: 1.1.19-0 -> 1.1.21-0
 * ros-hydro-global-planner: 1.11.9-0 -> 1.11.10-0
 * ros-hydro-gmapping: 1.3.2-1 -> 1.3.3-0
 * ros-hydro-hector-localization: 0.1.2-0 -> 0.1.3-0
 * ros-hydro-hector-pose-estimation: 0.1.2-0 -> 0.1.3-0
 * ros-hydro-hector-pose-estimation-core: 0.1.2-0 -> 0.1.3-0
 * ros-hydro-hironx-moveit-config: 1.0.14-0 -> 1.0.18-1
 * ros-hydro-hironx-ros-bridge: 1.0.14-0 -> 1.0.18-1
 * ros-hydro-image-exposure-msgs: 0.9.1-0 -> 0.9.2-0
 * ros-hydro-image-view-jsk-patch: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-image-view2: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-imagesift: 0.1.7-0 -> 0.1.11-0
 * ros-hydro-imu-compass: 0.0.3-0 -> 0.0.5-0
 * ros-hydro-jpeg-streamer: 0.2.1-0 -> 0.2.4-0
 * ros-hydro-jsk-common: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-jsk-footstep-msgs: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-jsk-gui-msgs: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-jsk-hark-msgs: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-jsk-interactive: 1.0.4-0 -> 1.0.5-0
 * ros-hydro-jsk-interactive-marker: 1.0.4-0 -> 1.0.5-0
 * ros-hydro-jsk-interactive-test: 1.0.4-0 -> 1.0.5-0
 * ros-hydro-jsk-model-tools: 0.1.4-0 -> 0.1.6-0
 * ros-hydro-jsk-pcl-ros: 0.1.7-0 -> 0.1.11-0
 * ros-hydro-jsk-perception: 0.1.7-0 -> 0.1.11-0
 * ros-hydro-jsk-recognition: 0.1.7-0 -> 0.1.11-0
 * ros-hydro-jsk-roseus: 1.1.19-0 -> 1.1.21-0
 * ros-hydro-jsk-rqt-plugins: 1.0.4-0 -> 1.0.5-0
 * ros-hydro-jsk-rviz-plugins: 1.0.4-0 -> 1.0.5-0
 * ros-hydro-jsk-tools: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-jsk-topic-tools: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-laser-filters-jsk-patch: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-libsiftfast: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-libuvc: 0.0.3-0 -> 0.0.5-0
 * ros-hydro-map-server: 1.11.9-0 -> 1.11.10-0
 * ros-hydro-master-discovery-fkie: 0.3.11-0 -> 0.3.12-0
 * ros-hydro-master-sync-fkie: 0.3.11-0 -> 0.3.12-0
 * ros-hydro-mavlink: 1.0.9-4 -> 1.0.9-5
 * ros-hydro-mavros: 0.5.0-0 -> 0.6.0-0
 * ros-hydro-message-to-tf: 0.1.2-0 -> 0.1.3-0
 * ros-hydro-move-base: 1.11.9-0 -> 1.11.10-0
 * ros-hydro-move-base-msgs: 1.11.9-0 -> 1.11.10-0
 * ros-hydro-move-slow-and-clear: 1.11.9-0 -> 1.11.10-0
 * ros-hydro-moveit-commander: 0.5.5-0 -> 0.5.7-0
 * ros-hydro-moveit-core: 0.5.8-0 -> 0.5.9-0
 * ros-hydro-moveit-planners: 0.5.4-0 -> 0.5.6-0
 * ros-hydro-moveit-planners-ompl: 0.5.4-0 -> 0.5.6-0
 * ros-hydro-moveit-python: 0.2.4-0 -> 0.2.5-0
 * ros-hydro-moveit-ros: 0.5.16-0 -> 0.5.19-0
 * ros-hydro-moveit-ros-benchmarks: 0.5.16-0 -> 0.5.19-0
 * ros-hydro-moveit-ros-benchmarks-gui: 0.5.16-0 -> 0.5.19-0
 * ros-hydro-moveit-ros-manipulation: 0.5.16-0 -> 0.5.19-0
 * ros-hydro-moveit-ros-move-group: 0.5.16-0 -> 0.5.19-0
 * ros-hydro-moveit-ros-perception: 0.5.16-0 -> 0.5.19-0
 * ros-hydro-moveit-ros-planning: 0.5.16-0 -> 0.5.19-0
 * ros-hydro-moveit-ros-planning-interface: 0.5.16-0 -> 0.5.19-0
 * ros-hydro-moveit-ros-robot-interaction: 0.5.16-0 -> 0.5.19-0
 * ros-hydro-moveit-ros-visualization: 0.5.16-0 -> 0.5.19-0
 * ros-hydro-moveit-ros-warehouse: 0.5.16-0 -> 0.5.19-0
 * ros-hydro-multi-map-server: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-multimaster-fkie: 0.3.11-0 -> 0.3.12-0
 * ros-hydro-multimaster-msgs-fkie: 0.3.11-0 -> 0.3.12-0
 * ros-hydro-nav-core: 1.11.9-0 -> 1.11.10-0
 * ros-hydro-navfn: 1.11.9-0 -> 1.11.10-0
 * ros-hydro-navigation: 1.11.9-0 -> 1.11.10-0
 * ros-hydro-nextage-description: 0.2.14-0 -> 0.2.15-1
 * ros-hydro-nextage-moveit-config: 0.2.14-0 -> 0.2.15-1
 * ros-hydro-nextage-ros-bridge: 0.2.14-0 -> 0.2.15-1
 * ros-hydro-node-manager-fkie: 0.3.11-0 -> 0.3.12-0
 * ros-hydro-opencv-candidate: 0.2.1-0 -> 0.2.3-0
 * ros-hydro-openni-tracker-jsk-patch: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-opt-camera: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-orocos-kdl: 1.2.2-0 -> 1.3.0-0
 * ros-hydro-pal-vision-segmentation: 0.0.1-0 -> 1.0.0-0
 * ros-hydro-people: 1.0.3-0 -> 1.0.4-0
 * ros-hydro-people-msgs: 1.0.3-0 -> 1.0.4-0
 * ros-hydro-pointgrey-camera-driver: 0.9.1-0 -> 0.9.2-0
 * ros-hydro-posedetection-msgs: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-pr2-groovy-patches: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-python-orocos-kdl: 1.2.2-0 -> 1.3.0-0
 * ros-hydro-qt-build: 0.2.5-0 -> 0.2.6-0
 * ros-hydro-qt-create: 0.2.5-0 -> 0.2.6-0
 * ros-hydro-qt-ros: 0.2.5-0 -> 0.2.6-0
 * ros-hydro-qt-tutorials: 0.2.5-0 -> 0.2.6-0
 * ros-hydro-resized-image-transport: 0.1.7-0 -> 0.1.11-0
 * ros-hydro-robot-pose-ekf: 1.11.9-0 -> 1.11.10-0
 * ros-hydro-ros-ethercat: 0.1.7-0 -> 0.1.7-1
 * ros-hydro-ros-ethercat-eml: 0.1.7-0 -> 0.1.7-1
 * ros-hydro-ros-ethercat-hardware: 0.1.7-0 -> 0.1.7-1
 * ros-hydro-ros-ethercat-loop: 0.1.7-0 -> 0.1.7-1
 * ros-hydro-ros-ethercat-model: 0.1.7-0 -> 0.1.7-1
 * ros-hydro-roseus: 1.1.19-0 -> 1.1.21-0
 * ros-hydro-roseus-msgs: 1.1.19-0 -> 1.1.21-0
 * ros-hydro-roseus-smach: 1.1.19-0 -> 1.1.21-0
 * ros-hydro-rosh: 1.0.3-0 -> 1.0.5-0
 * ros-hydro-rosh-core: 1.0.3-0 -> 1.0.5-0
 * ros-hydro-roshlaunch: 1.0.3-0 -> 1.0.5-0
 * ros-hydro-rosjava-bootstrap: 0.1.21-0 -> 0.1.22-0
 * ros-hydro-rospatlite: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-rosping: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-rostwitter: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-rotate-recovery: 1.11.9-0 -> 1.11.10-0
 * ros-hydro-rtmros-hironx: 1.0.14-0 -> 1.0.18-1
 * ros-hydro-rtmros-nextage: 0.2.14-0 -> 0.2.15-1
 * ros-hydro-sklearn: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-slam-gmapping: 1.3.2-1 -> 1.3.3-0
 * ros-hydro-smclib: 1.7.13-0 -> 1.7.14-0
 * ros-hydro-sr-ronex: 0.9.14-0 -> 0.9.14-2
 * ros-hydro-sr-ronex-controllers: 0.9.14-0 -> 0.9.14-2
 * ros-hydro-sr-ronex-drivers: 0.9.14-0 -> 0.9.14-2
 * ros-hydro-sr-ronex-examples: 0.9.14-0 -> 0.9.14-2
 * ros-hydro-sr-ronex-external-protocol: 0.9.14-0 -> 0.9.14-2
 * ros-hydro-sr-ronex-hardware-interface: 0.9.14-0 -> 0.9.14-2
 * ros-hydro-sr-ronex-launch: 0.9.14-0 -> 0.9.14-2
 * ros-hydro-sr-ronex-msgs: 0.9.14-0 -> 0.9.14-2
 * ros-hydro-sr-ronex-test: 0.9.14-0 -> 0.9.14-2
 * ros-hydro-sr-ronex-transmissions: 0.9.14-0 -> 0.9.14-2
 * ros-hydro-sr-ronex-utilities: 0.9.14-0 -> 0.9.14-2
 * ros-hydro-statistics-msgs: 0.9.1-0 -> 0.9.2-0
 * ros-hydro-stereo-synchronizer: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-uvc-camera: 0.2.1-0 -> 0.2.4-0
 * ros-hydro-vision-visp: 0.7.3-1 -> 0.7.4-0
 * ros-hydro-visp-auto-tracker: 0.7.3-1 -> 0.7.4-0
 * ros-hydro-visp-bridge: 0.7.3-1 -> 0.7.4-0
 * ros-hydro-visp-camera-calibration: 0.7.3-1 -> 0.7.4-0
 * ros-hydro-visp-hand2eye-calibration: 0.7.3-1 -> 0.7.4-0
 * ros-hydro-visp-tracker: 0.7.3-1 -> 0.7.4-0
 * ros-hydro-voxel-grid: 1.11.9-0 -> 1.11.10-0
 * ros-hydro-wfov-camera-msgs: 0.9.1-0 -> 0.9.2-0
 * ros-hydro-world-magnetic-model: 0.1.2-0 -> 0.1.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
 * Bence Magyar
 * Carnegie Robotics
 * Dan Lazewatsky
 * Daniel Stonier
 * David Lu!!
 * David V. Lu!!
 * Esteve Fernandez
 * Fabien Spindler
 * Francois Pomerleau
 * Hiroyuki Mikita
 * Ioan Sucan
 * Isaac Isao Saito
 * Johannes Meyer
 * KazutoMurase
 * Kei Okada
 * Ken Tossell
 * Manos Nikolaidis
 * Michael Ferguson
 * Mike Purvis
 * Noda Shintaro
 * Orocos Developers
 * Prasenjit Mukherjee
 * Ruben Smits
 * Ryohei Ueda
 * Sachin Chitta
 * Shadow Robot's software team
 * Shohei Fujii
 * Takashi Ogura
 * Takuya Nakaoka
 * Vincent Rabaud
 * Vladimir Ermakov
 * William Woodall
 * Yohei Kakiuchi
 * Youhei Kakiuchi
 * Yuki Furuta
 * Yusuke Furuta
 * furuta
 * k-okada
 * lil1pal

by Tully Foote on July 22, 2014 08:38 PM

Robotnik AGVS: New ROS Open Platform for Logistics Transport

from Roberto Guzmán via ros-users@


Hi all :)

We are pleased to announce AGVS: the new Open ROS Platform for Logistics Transport. 

AGVS is an autonomous robot for indoor logistic intra-hospital transport. The robot has Ackermann kinematics and is provided with ROS architecture for simulation and control. 

This robot is currently serving in several European hospitals, and this is the first open version released. 

The provided software includes the packages for simulating the robot in several environments, generating maps, localize and define routes through a rviz interactive marker based interface.

It is an excellent starting point for anyone developing new generation logistics applications. 

You can find more info in:

Some additional information about the robot can be found in:

Enjoy it!,

  Roberto


by Ugo Cupcic on July 22, 2014 12:29 PM

July 21, 2014
Thanks for a great ROS Kong 2014!
IMG_20140606_175935760-SMILE.jpg
We want to express our thanks to everyone who made ROS Kong 2014 a great success. It was our first ROS event in Asia and it was great to see the enthusiasm from the nearby community as well as the community members who came from all around the globe. ROS Kong was designed as a complement to our annual conference ROSCon, which will happen in Chicago in September.

It took many people to make ROS Kong happen.  We'd like to give a special thanks to:

  • Our sponsors: Yujin Robot, ETRI, and GaiTech
  • Our host: The University of Hong Kong
  • Our organizers: Tully Foote, Brian Gerkey, Wyatt Newman, Daniel Stonier
  • Our volunteers: David Coleman, Annie Lam, Team HKU
  • Our speakers, who put together awesome talks.
  • Our attendees, without whom there would be no event!

The event included invited talks from ROS community members in the Australasia region. We started with a keynote from Kei Okada from the University of Tokyo. We also had talks from Paulo Borges, Chris Swetenham, Noriaki Ando, and Daniel Stonier. 

IMG_20140606_092859948.jpg
We have added links to video recordings of all the talks from the agenda and several of the presenters have provided their slides. 

We had two Lightning Talk sessions in which many attendees talked about their current work, put out calls for collaboration, or showed off new sensors or robots, such as Einstein from Hansen Robotics and the new RPLidar sensor from RoboPeak.  

IMG_20140606_152834850_HDR.jpg
In the afternoon we left a period open for Birds of a Feather sessions during which there were 16 different topics discussed. 

IMG_20140606_164334911.jpg

Over lunch, our host, The University of Hong Kong, provided us with live demos of ATLAS as well as a chance to check out the robot up close. 

IMG_20140606_125105864.jpg
We finished out the day with a reception overlooking Hong Kong in the HKU Faculty Club. 

IMG_20140606_175446460.jpg

If you'd like to see more pictures and videos of the event they are posted on the Google+ event page

 

by Tully Foote on July 21, 2014 05:44 PM


Powered by the awesome: Planet