Eric Perko | 16 May 2013 05:49
Picon
Gravatar

nmea_gps_driver API review for Hydro

Hydro will include an updated version of the nmea_gps_driver package.

nmea_gps_driver is a simple NMEA driver. It supports reading NMEA strings from a serial port or topic and outputting the appropriate ROS messages. Currently supported output messages are sensor_msgs/NavSatFix for positional information, geometry_msgs/TwistStamped for velocity information reported by the GPS unit and sensor_msgs/TimeReference to output the current time according to the GPS unit. This driver is meant to be cross-platform and avoid a dependency on GPSd.

For convenience, the major API changes for Hydro are:
  • nmea_gps_driver.py is now deprecated and will be removed in I-Turtle. Replacement node is nmea_serial_driver.py .
  • Refactored code into NMEA parser, common ROS driver and added separate nodes for reading directly from serial or from topic.

I've created an API review page:


If you are interested in this driver, please take a look at the ROS API of the nmea_gps_driver package and share your comments on the review page. If you do leave a comment, please add your name to the list of reviewers and subscribe to the page in order to receive notifications of replies.

- Eric Perko
<div><div dir="ltr">Hydro will include an updated version of the nmea_gps_driver package.<div><br></div>
<div>
<div>
<span class="">nmea_gps_driver</span>&nbsp;is a simple&nbsp;<span class="">NMEA</span>&nbsp;<span class="">driver</span>. It supports reading&nbsp;<span class="">NMEA</span>&nbsp;strings from a serial port or topic and outputting the appropriate ROS messages. Currently supported output messages are sensor_msgs/NavSatFix for positional information, geometry_msgs/TwistStamped for velocity information reported by the&nbsp;<span class="">GPS</span>&nbsp;unit and sensor_msgs/TimeReference to output the current time according to the&nbsp;<span class="">GPS</span>&nbsp;unit. This&nbsp;<span class="">driver</span>&nbsp;is meant to be cross-platform and avoid a dependency on GPSd.</div>
<div><br></div>
<div>For convenience, the major API changes for Hydro are:</div>
<ul>
<li>nmea_gps_driver.py is now deprecated and will be removed in I-Turtle. Replacement node is nmea_serial_driver.py .<br>
</li>
<li>Refactored code into NMEA parser, common ROS driver and added separate nodes for reading directly from serial or from topic.<br>
</li>
</ul>
<div><br></div>
<div>
I've created an API&nbsp;<span class="">review</span>&nbsp;page:</div>
<div><br></div>
<div>
<a href="http://www.ros.org/wiki/nmea_gps_driver/Reviews/2013-05-22_API_Review">http://www.ros.org/wiki/nmea_gps_driver/Reviews/2013-05-22_API_Review</a><br>
</div>
<div><br></div>
<div>If you are interested in this&nbsp;<span class="">driver</span>, please take a look at the ROS API of the&nbsp;<span class="">nmea_gps_driver</span>&nbsp;package and share your comments on the&nbsp;<span class="">review</span>&nbsp;page. If you do leave a comment, please add your name to the list of reviewers and subscribe to the page in order to receive notifications of replies.</div>
</div>
<div><br></div>
<div>- Eric Perko</div>
</div></div>
Dan Lazewatsky | 13 May 2013 18:08
Gravatar

epydoc broken with rosdoc

Hi ros-users,

It looks like for over a year, building epydoc based documentation has been broken. I submitted a pull request to fix this last week (https://github.com/ros/documentation/pull/1), but it doesn't appear that anyone really has ownership of the documentation code. What's the right thing to do in this situation?

Thanks,
-Dan
<div>
<p>Hi ros-users,</p>
<div>It looks like for over a year, building epydoc based documentation has been broken. I submitted a pull request to fix this last week (<a href="https://github.com/ros/documentation/pull/1">https://github.com/ros/documentation/pull/1</a>), but it doesn't appear that anyone really has ownership of the documentation code. What's the right thing to do in this situation?</div>
<div><br></div>
<div>Thanks,</div>
<div>-Dan</div>
</div>
Thomas Moulard | 13 May 2013 09:13
Picon
Gravatar

Submitting ROS software to Debian?

Hello there,
in the latest ROS releases, a lot of effort have been done to enhance
the way ROS is installed/distributed. However, I never heard of any
undergoing effort to submit the software to Debian directly. Is there
some discussion with Debian to see how it can be achieved?

In practice, I am trying to figure out currently whether the
stand-alone projects
(PCL, Ecto and Gazebo) could be included into Debian in an official way.
A bit of polishing is still needed to achieve this (man page redaction,
multiarch support, etc.) but I think this is definitively within reach.

The main issue being that as long as ROS is not available officially,
it will not be possible to compile the ROS bindings for these packages
and include
them in the official repositories.

See the following bug reports for more information:
- Gazebo: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=705440
- PCL: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703579

IMHO it is a good time for the ROS community and ros-science to start
discussing on how to make this happen. Especially knowing that some
preliminary work
is needed to ensure all 3rd party dependencies are available. I.e.
bullet have only be
migrated to Debian Testing last week (!).

What do you think? Any people interested in this?
--

-- 
Thomas Moulard(ムラー トマ)
CNRS-AIST JRL (Joint Robotics Laboratory), UMI3218/CRT, Tsukuba, Japan
http://thomas.moulard.net | GPG Key Id: 516FC68F31496D58
Add me on LinkedIn: http://www.linkedin.com/in/moulard
_______________________________________________
ros-users mailing list
ros-users <at> code.ros.org
https://code.ros.org/mailman/listinfo/ros-users
Jack O'Quin | 12 May 2013 18:15
Picon
Gravatar

Announcing geographic information SIG

I created a SIG for applications of geographic information systems technology to robotics. This replaces the Geographic Info project on kforge.ros.org.


Topics include: satellite navigation systems like GPS, cartography, geodesy and geographic coordinate transformations.

We mainly focus on defining common interfaces and best practices, so various classes of drivers and applications work consistently with other ROS components. Please join if you are interested and wish to contribute.
-- 
 joq
<div><div dir="ltr">
<div>I created a SIG for applications of geographic information systems technology to robotics. This replaces the Geographic Info project on <a href="http://kforge.ros.org">kforge.ros.org</a>.</div>
<div><br></div>
<div>&nbsp;<a href="http://ros.org/wiki/sig/GeographicInfo">http://ros.org/wiki/sig/GeographicInfo</a>
</div>
<br>Topics include: satellite navigation systems like GPS, cartography, geodesy and geographic coordinate transformations.<div>
<br><div>We mainly focus on defining common interfaces and best practices, so various classes of drivers and applications work consistently with other ROS components. Please join if you are interested and wish to contribute.<br>
--&nbsp;<br>
</div>
<div>&nbsp;joq
</div>
</div>
</div></div>
Sachin Chitta | 9 May 2013 15:43
Favicon

Announcing MoveIt!

http://youtu.be/vAeEEoxVhAo

Willow Garage is proud to announce the initial release of MoveIt! : new software targeted at allowing you to build advanced applications integrating motion planning, kinematics, collision checking with grasping, manipulation, navigation, perception, and control. MoveIt! is robot agnostic software that can be quickly set up with your robot if a URDF representation of the robot is available. The MoveIt! Setup Assistant lets you configure MoveIt! for any robot, allowing you to visualize and interact with the robot model quickly.

MoveIt! can incorporate both actual sensor data and simulated models to build an environment representation. Sensor information (3D) can be automatically integrated realtime in the representation of the world that MoveIt! maintains. CAD models can also be imported in the same world representation if desired. Collision-free motion planning, execution and monitoring are core capabilities that MoveIt! provides for any robot. MoveIt! updates its representation of the environment on the fly, enabling reactive motion planning and execution, which is essential for applications in human-robot collaborative environments.

MoveIt! interfaces with controllers through a standard ROS interface, allowing for ease of inter-operability, i.e. the ability to use the same higher-level software with a variety of robots without needing to change code. MoveIt! is architected to be flexible, using a plugin architecture to allow users to integrate their own custom components while still providing out-of-the-box functionality using default implementations. Furthermore, the ROS communication and configuration layer of MoveIt! is separated from core computational components such as motion planning or collision checking, the latter components being provided separately as C++ libraries.

Workspace analysis tools allow robot designers to test out the capabilities of their robot designs before building the hardware, using environment and object specific task specifications to quantify the workspace characteristics of different designs. This reduces costly mistakes and iterations in the design stage. We are actively working on completing the pick and place capabilities in MoveIt!, integrating with object recognition, perception, and grasping to allow manipulators to execute generalized pick and place actions.

Get MoveIt!

More Information about MoveIt!, including instructions on how to get and use it, can be found on the MoveIt! website. MoveIt! is currently an alpha release.

Catch the MoveIt! team at ICRA 2013 and ROSCON:

  • ICRA Booth Demo: The Willow Garage Booth will have a MoveIt! demo as part of the exhibit. The booth is open on Tuesday, Wednesday and Thursday (May 7-9, 2013).
  • ICRA Workshop Talk: Sachin Chitta is giving a talk on "MoveIt!: Software for Rapid Development of New Robotics Applications" at the ICRA Industrial Mobile Assistance Robots Workshop on Monday, May 6, 2013.
  • ICRA Tutorial: MoveIt! will be presented at a tutorial on Friday May 10, 2013: Motion Planning for Mobile Manipulation: State-of-the-art Methods and Tools, organized by Sachin Chitta, Ioan Sucan, Mark Moll, Lydia Kavraki and Maxim Likhachev.
  • ROSCON Keynote Talk: Sachin Chitta, Ioan Sucan and Acorn Pooley will be at ROSCON presenting MoveIt! at 9:30 AM on Saturday May 10, 2013.
Acknowledgements

Willow Garage gratefully acknowledges the contributions of the following people to MoveIt! and associated packages that MoveIt! uses and depends on:

  • Lydia Kavraki, Mark Moll, and associated members of the Kavraki Lab (Rice University) for developing OMPL - a suite of randomized planners that MoveIt! uses extensively.
  • Dinesh Manocha and Jia Pan of UNC Chapel Hill for developing FCL - a package of collision checking algorithm used extensively by MoveIt!
  • Maxim Likhachev (CMU), Ben Cohen (Penn) and Mike Phillips (CMU) for developing SBPL, a search-based planning library integrated with MoveIt!
  • Armin Hornung, Kai Wurm, Maren Bennewitz, Cyril Stachniss, and Wolfram Burgard for developing Octomap - software for 3D occupancy mapping used by MoveIt!
  • Mrinal Kalakrishnan, Peter Pastor and Stefan Schaal at USC for developing STOMP, the distance field components in MoveIt! and the implementation of the CHOMP algorithm in Arm Navigation
  • Dave Coleman from the University of Colorado, Boulder for developing the MoveIt! Setup Assistant and adding documentation to the MoveIt! website.

MoveIt! evolved from the Arm Navigation and Grasping Pipeline components of ROS and we gratefully acknowledge the seminal contributions of all developers and researchers to those packages, especially Edward Gil Jones, Matei Ciocarlie, Kaijen Hsiao, Adam Leeper, and Ken Anderson.

We also acknowledge the contributions of the Willow Garage interns who have worked on MoveIt!, Arm Navigation and associated components, members of the ROS and PR2 communities who have used, provided feedback and provided contributions to MoveIt! and Arm Navigation and members of the ROS community for developing the infrastructure that MoveIt! builds on.

We also acknowledge the contributions of the ROS-Industrial consortium led by the Southwest Research Institute for supporting and building up infrastructure for applying MoveIt! and Arm Navigation to industrial robots and environments. Similarly, we acknowledge the contributions of Fraunhofer IPA to MoveIt! and support for the ROS-Industrial effort in Europe.

For more information visit moveit.ros.org



--
Sachin Chitta
Manager and Research Scientist
Autonomous Mobile Manipulation Group
Willow Garage
<div><div dir="ltr">
<p><a href="http://youtu.be/vAeEEoxVhAo" target="_blank"></a></p>
<p><a href="http://youtu.be/vAeEEoxVhAo" target="_blank">http://youtu.be/vAeEEoxVhAo</a></p>

<p>

Willow Garage is proud to announce the initial release of MoveIt! : new 
software targeted at allowing you to build advanced applications 
integrating motion planning, kinematics, collision checking with 
grasping, manipulation, navigation, perception, and control. MoveIt! is 
robot agnostic software that can be quickly set up with your robot if a 
URDF representation of the robot is available. The MoveIt! Setup 
Assistant lets you configure MoveIt! for any robot, allowing you to 
visualize and interact with the robot model quickly.</p>MoveIt! can 
incorporate both actual sensor data and simulated models to build an 
environment representation. Sensor information (3D) can be automatically
 integrated realtime in the representation of the world that MoveIt! 
maintains. CAD models can also be imported in the same world 
representation if desired. Collision-free motion planning, execution and
 monitoring are core capabilities that MoveIt! provides for any robot. 
MoveIt! updates its representation of the environment on the fly, 
enabling reactive motion planning and execution, which is essential for 
applications in human-robot collaborative environments. <br><p>MoveIt! 
interfaces with controllers through a standard ROS interface, allowing 
for ease of inter-operability, i.e. the ability to use the same 
higher-level software with a variety of robots without needing to change
 code. MoveIt! is architected to be flexible, using a plugin 
architecture to allow users to integrate their own custom components 
while still providing out-of-the-box functionality using default 
implementations. Furthermore, the ROS communication and configuration 
layer of MoveIt! is separated from core computational components such as
 motion planning or collision checking, the latter components being 
provided separately as C++ libraries.</p>
<p>Workspace analysis tools 
allow robot designers to test out the capabilities of their robot 
designs before building the hardware, using environment and object 
specific task specifications to quantify the workspace characteristics 
of different designs. This reduces costly mistakes and iterations in the
 design stage. We are actively working on completing the pick and place 
capabilities in MoveIt!, integrating with object recognition, 
perception, and grasping to allow manipulators to execute generalized 
pick and place actions.</p>
<p>Get MoveIt!</p>
<p>More Information about MoveIt!, including instructions on how to get and use it, can be found on the <a title="http://moveit.ros.org" href="http://moveit.ros.org" target="_blank">MoveIt! website</a>. MoveIt! is currently an alpha release.</p>
<p>Catch the MoveIt! team at ICRA 2013 and ROSCON:<br></p>
<ul>
<li>ICRA Booth Demo:
 The Willow Garage Booth will have a MoveIt! demo as part of the 
exhibit. The booth is open on Tuesday, Wednesday and Thursday (May 7-9, 
2013).</li>
<li>ICRA Workshop Talk: Sachin Chitta is giving a talk
 on "MoveIt!: Software for Rapid Development of New Robotics 
Applications" at the ICRA Industrial Mobile Assistance Robots Workshop 
on Monday, May 6, 2013.</li>
<li>ICRA Tutorial: MoveIt! will be presented at a tutorial on Friday May 10, 2013: <a href="http://moveit.ros.org/wiki/index.php/Tutorials/ICRA2013" target="_blank">Motion Planning for Mobile Manipulation: State-of-the-art Methods and Tools</a>, organized by Sachin Chitta, Ioan Sucan, Mark Moll, Lydia Kavraki and Maxim Likhachev.</li>
<li>ROSCON Keynote Talk: Sachin Chitta, Ioan Sucan and Acorn Pooley will be at ROSCON presenting MoveIt! at 9:30 AM on Saturday May 10, 2013. </li>
</ul>Acknowledgements<p>Willow
 Garage gratefully acknowledges the contributions of the following 
people to MoveIt! and associated packages that MoveIt! uses and depends 
on:</p>
<ul>
<li>Lydia Kavraki, Mark Moll, and associated members of the <a title="http://www.kavrakilab.org" href="http://www.kavrakilab.org" target="_blank">Kavraki Lab</a> (Rice University) for developing OMPL - a suite of randomized planners that MoveIt! uses extensively.</li>

<li>Dinesh Manocha and Jia Pan of <a title="http://unc.edu" href="http://unc.edu" target="_blank">UNC Chapel Hill</a> for developing FCL - a package of collision checking algorithm used extensively by MoveIt!</li>
<li>Maxim Likhachev (<a title="http://www.ri.cmu.edu" href="http://www.ri.cmu.edu" target="_blank">CMU</a>), Ben Cohen (<a title="https://www.grasp.upenn.edu" href="https://www.grasp.upenn.edu" target="_blank">Penn</a>) and Mike Phillips (<a title="http://www.ri.cmu.edu" href="http://www.willowgarage.com/" target="_blank">CMU</a>) for developing <a title="http://www.ros.org/wiki/sbpl" href="http://www.ros.org/wiki/sbpl" target="_blank">SBPL</a>, a search-based planning library integrated with MoveIt!</li>

<li>Armin Hornung, Kai Wurm, Maren Bennewitz, Cyril Stachniss, and Wolfram Burgard for developing <a title="http://www.ros.org/wiki/octomap" href="http://www.ros.org/wiki/octomap" target="_blank">Octomap</a> - software for 3D occupancy mapping used by MoveIt!</li>

<li>Mrinal Kalakrishnan, Peter Pastor and Stefan Schaal at <a title="http://robotics.usc.edu" href="http://robotics.usc.edu" target="_blank">USC</a> for developing <a title="http://www.ros.org/wiki/Papers/ICRA2011_Kalakrishnan" href="http://www.ros.org/wiki/Papers/ICRA2011_Kalakrishnan" target="_blank">STOMP</a>, the distance field components in MoveIt! and the implementation of the <a title="http://www.ros.org/wiki/chomp_motion_planner" href="http://www.ros.org/wiki/chomp_motion_planner" target="_blank">CHOMP</a> algorithm in Arm Navigation</li>

<li>Dave Coleman from the <a title="http://www.colorado.edu" href="http://www.colorado.edu" target="_blank">University of Colorado, Boulder</a> for developing the MoveIt! Setup Assistant and adding documentation to the MoveIt! website.</li>

</ul>
<p>MoveIt!
 evolved from the Arm Navigation and Grasping Pipeline components of ROS
 and we gratefully acknowledge the seminal contributions of all 
developers and researchers to those packages, especially Edward Gil 
Jones, Matei Ciocarlie, Kaijen Hsiao, Adam Leeper, and Ken Anderson.</p>
<p>We
 also acknowledge the contributions of the Willow Garage interns who 
have worked on MoveIt!, Arm Navigation and associated components, 
members of the ROS and PR2 communities who have used, provided feedback 
and provided contributions to MoveIt! and Arm Navigation and members of 
the ROS community for developing the infrastructure that MoveIt! builds 
on.</p>
<p>We also acknowledge the contributions of the ROS-Industrial 
consortium led by the Southwest Research Institute for supporting and 
building up infrastructure for applying MoveIt! and Arm Navigation to 
industrial robots and environments. Similarly, we acknowledge the 
contributions of <a title="http://www.ipa.fraunhofer.de/index.php?L=2" href="http://www.ipa.fraunhofer.de/index.php?L=2" target="_blank">Fraunhofer IPA</a> to MoveIt! and support for the ROS-Industrial effort in Europe.</p>

<p>For more information visit <a title="moveit.ros.org" href="http://www.willowgarage.com/moveit.ros.org" target="_blank">moveit.ros.org</a></p>
<br clear="all"><br>-- <br>Sachin Chitta<br>Manager and Research Scientist<br>

Autonomous Mobile Manipulation Group<br>Willow Garage
</div></div>
Toris, Russell Charles | 8 May 2013 19:06
Favicon

Robot Web Tools Launches

Dear Robotics and JavaScript Communities-

It is our pleasure to announce the official launch of the Robot Web Tools organization. Robot Web Tools is a
collection of open-source modules and tools for building web-based robot apps.

A variety of routes are available for architecting a robot web application. A common route is building web
technologies on an existing robot framework. The Robot Operating System (ROS) is one of the top
frameworks to program robots and can run on a variety of robots, from a TurtleBot to a PR2 to an Arduino
connected to a computer. ROS - and other robot middleware frameworks - provide common robot
functionality, including drivers for interfacing with a variety of sensors and actuators and
algorithms for navigation, perception, and manipulation.

While ROS works great for applications on the robot, another layer is needed to connect external devices
and applications. rosbridge is both a JSON spec for interacting with ROS and a transport layer, providing
a WebSocket for clients to communicate over. In the browser layer sits the core JavaScript libraries:
roslibjs, ros2js, and ros3djs. These libraries communicate with ROS on the robot over rosbridge's
WebSocket server. It's a lightweight, evented library that provides a convenient abstraction to core
ROS functionality.

Robot Web Tools is being spearheaded by five supporting organizations: Brown University, Robert Bosch
LLC, Willow Garage Inc., Worcester Polytechnic Institute, and Yujin Robot.

The real benefits of the Robot Web Tools organization is JavaScript modules and tools that build off these
foundations. With this new effort, we have provided a new website, ample documentation, a new email list,
and a collection of tutorials and live demos. We encourage robot and web programmers of all levels to get
involved with the community, contribute their projects, and help to grow this emerging technology.

For more information, check us out on our homepage, http://robotwebtools.org/, or see our current
projects listed at http://robotwebtools.org/tools.html. Links to tutorials and wiki documentation
can be found in repository READMEs located at https://github.com/robotwebtools.

To keep up to date, be sure to subscribe to our Google Group email list at
https://groups.google.com/forum/?fromgroups#!forum/robot-web-tools (robot-web-tools@...)

-- Russell Toris, Community Manager & The Robot Web Tools Team

Melonee Wise | 8 May 2013 13:55
Gravatar

announcing sphero_ros

Hi Everyone -

I put together a stack for the sphero, sphero_ros: https://github.com/mmwise/sphero_ros

 The stack includes:
  * a standalone sphero python driver with extensive API documentation (http://mmwise.github.io/sphero_ros/api.html#id1)
  * standard ros node which provides all the standard goodies, odometry, imu data, tf frames, collision data etc
  * a urdf 
  * bringup with standard launch files to get you started

I only implemented the essentials of the base sphero API so there is room for people to implement more, so if you're interested please contribute and help the stack improve :)



-Melonee
<div><div dir="ltr">Hi Everyone -<div><br></div>
<div>I put together a stack for the sphero, sphero_ros:&nbsp;<a href="https://github.com/mmwise/sphero_ros">https://github.com/mmwise/sphero_ros</a>
</div>
<div><br></div>
<div>
&nbsp;The stack includes:</div>
<div>&nbsp; * a standalone sphero python driver with extensive API documentation (<a href="http://mmwise.github.io/sphero_ros/api.html#id1">http://mmwise.github.io/sphero_ros/api.html#id1</a>)</div>
<div>&nbsp; * standard ros node which provides all the standard goodies, odometry, imu data, tf frames, collision data etc</div>
<div>&nbsp; * a urdf&nbsp;</div>
<div>&nbsp; * bringup with standard launch files to get you started</div>
<div>&nbsp; * documentation!&nbsp;<a href="http://mmwise.github.io/sphero_ros/">http://mmwise.github.io/sphero_ros/</a>
</div>
<div><br></div>
<div>I only implemented the essentials of the base sphero API so there is room for people to implement more, so if you're interested please contribute and help the stack improve :)</div>
<div><br></div>
<div><br></div>
<div><br></div>
<div>-Melonee</div>
</div></div>
Tully Foote | 8 May 2013 10:20
Gravatar

New and Updated Groovy Packages

We're pleased to announce the release of more than a hundred new and updated packages into Groovy.  

See below for the full list.  

Your friendly ROS Release Team


Packages Added: 
ros-groovy-all : 1.0.0
ros-groovy-bride : 0.2.0
ros-groovy-chatter-concert : 0.3.5
ros-groovy-client-rosjava-jni : 0.1.11
ros-groovy-default-cfg-fkie : 0.2.2
ros-groovy-freenect-camera : 0.2.0
ros-groovy-freenect-launch : 0.2.0
ros-groovy-freenect-stack : 0.2.0
ros-groovy-glc : 0.5.8
ros-groovy-jsk-openni-kinect : 0.1.0
ros-groovy-jsk-rviz-plugins : 0.0.9
ros-groovy-knowrob : 0.3.0
ros-groovy-libcsm : 2013.03.26
ros-groovy-libfreenect : 0.1.2
ros-groovy-master-discovery-fkie : 0.2.2
ros-groovy-master-sync-fkie : 0.2.2
ros-groovy-moveit-planners-ompl : 0.3.11
ros-groovy-moveit-ros-benchmarks-gui : 0.3.32
ros-groovy-moveit-ros-robot-interaction : 0.3.32
ros-groovy-multi-level-map : 0.0.2
ros-groovy-multi-level-map-msgs : 0.0.2
ros-groovy-multi-level-map-server : 0.0.2
ros-groovy-multi-level-map-utils : 0.0.2
ros-groovy-multimaster-fkie : 0.2.2
ros-groovy-node-manager-fkie : 0.2.2
ros-groovy-octomap-rviz-plugins : 0.0.1
ros-groovy-open-karto : 1.0.0
ros-groovy-rocon : 0.3.5
ros-groovy-rocon-gateway-tutorials : 0.3.5
ros-groovy-rocon-tutorials : 0.3.5
ros-groovy-rosbridge-suite : 0.4.4
ros-groovy-rqt-moveit : 0.2.15
ros-groovy-rqt-tf-tree : 0.2.15
ros-groovy-turtle-concert : 0.3.5
ros-groovy-turtle-race-concert : 0.3.5
ros-groovy-turtle-race-controllers : 0.3.5
ros-groovy-turtle-stroll : 0.3.5
ros-groovy-usb-cam : 0.1.2
ros-groovy-uwsim-osgocean : 1.0.2
ros-groovy-uwsim-osgworks : 2.0.2

Packages Removed: 
ros-groovy-moveit-source-build-deps : 0.3.1
ros-groovy-turtlebot-simulator : 1.9.1

Packages Updated: 
ros-groovy-camera-calibration : 1.10.8 -> 1.10.9
ros-groovy-camera-info-manager-py : 0.2.0 -> 0.2.1
ros-groovy-clearpath-husky : 0.3.3 -> 0.3.4
ros-groovy-cmd-vel-mux : 0.2.2 -> 0.2.3
ros-groovy-collada-parser : 1.9.33 -> 1.9.35
ros-groovy-collada-urdf : 1.9.33 -> 1.9.35
ros-groovy-depth-image-proc : 1.10.8 -> 1.10.9
ros-groovy-driver-base : 1.6.5 -> 1.6.6
ros-groovy-driver-common : 1.6.5 -> 1.6.6
ros-groovy-ecto-opencv : 0.4.23 -> 0.4.24
ros-groovy-erratic-robot : 0.3.2 -> 0.3.3
ros-groovy-fcl : 0.2.8 -> 0.2.9
ros-groovy-geometric-shapes : 0.2.5 -> 0.2.6
ros-groovy-husky-simulator : 0.1.1 -> 0.1.2
ros-groovy-image-pipeline : 1.10.8 -> 1.10.9
ros-groovy-image-proc : 1.10.8 -> 1.10.9
ros-groovy-image-rotate : 1.10.8 -> 1.10.9
ros-groovy-image-view : 1.10.8 -> 1.10.9
ros-groovy-joy : 1.9.9 -> 1.9.10
ros-groovy-joystick-drivers : 1.9.9 -> 1.9.10
ros-groovy-kdl-parser : 1.9.33 -> 1.9.35
ros-groovy-kobuki : 0.3.5 -> 0.3.7
ros-groovy-kobuki-arm : 0.3.5 -> 0.3.7
ros-groovy-kobuki-auto-docking : 0.3.5 -> 0.3.7
ros-groovy-kobuki-bumper2pc : 0.3.5 -> 0.3.7
ros-groovy-kobuki-controller-tutorial : 0.3.5 -> 0.3.7
ros-groovy-kobuki-desktop : 0.1.5 -> 0.1.6
ros-groovy-kobuki-driver : 0.3.5 -> 0.3.7
ros-groovy-kobuki-ftdi : 0.3.5 -> 0.3.7
ros-groovy-kobuki-keyop : 0.3.5 -> 0.3.7
ros-groovy-kobuki-node : 0.3.5 -> 0.3.7
ros-groovy-kobuki-safety-controller : 0.3.5 -> 0.3.7
ros-groovy-kobuki-testsuite : 0.3.5 -> 0.3.7
ros-groovy-libsegwayrmp : 0.2.3 -> 0.2.7
ros-groovy-mjpeg-server : 1.0.2 -> 1.1.0
ros-groovy-moveit-commander : 0.3.2 -> 0.3.5
ros-groovy-moveit-core : 0.3.16 -> 0.3.19
ros-groovy-moveit-full : 0.3.1 -> 0.3.3
ros-groovy-moveit-full-pr2 : 0.3.1 -> 0.3.3
ros-groovy-moveit-msgs : 0.3.18 -> 0.3.20
ros-groovy-moveit-ompl-planners-core : 0.3.7 -> 0.3.11
ros-groovy-moveit-ompl-planners-ros-plugin : 0.3.11 -> 0.3.7
ros-groovy-moveit-planners : 0.3.11 -> 0.3.7
ros-groovy-moveit-pr2 : 0.3.11 -> 0.3.9
ros-groovy-moveit-ros : 0.3.25 -> 0.3.32
ros-groovy-moveit-ros-benchmarks : 0.3.25 -> 0.3.32
ros-groovy-moveit-ros-manipulation : 0.3.25 -> 0.3.32
ros-groovy-moveit-ros-move-group : 0.3.25 -> 0.3.32
ros-groovy-moveit-ros-perception : 0.3.25 -> 0.3.32
ros-groovy-moveit-ros-planning : 0.3.25 -> 0.3.32
ros-groovy-moveit-ros-planning-interface : 0.3.25 -> None
ros-groovy-moveit-ros-visualization : 0.3.25 -> 0.3.32
ros-groovy-moveit-ros-warehouse : 0.3.25 -> 0.3.32
ros-groovy-moveit-setup-assistant : 0.3.6 -> 0.3.8
ros-groovy-object-recognition-core : 0.5.1 -> 0.5.2
ros-groovy-object-recognition-linemod : 0.2.11 -> 0.2.12
ros-groovy-object-recognition-reconstruction : 0.2.22 -> 0.2.23
ros-groovy-object-recognition-tabletop : 0.2.21 -> 0.2.22
ros-groovy-object-recognition-tod : 0.4.14 -> 0.4.15
ros-groovy-object-recognition-transparent-objects : 0.3.14 -> 0.3.15
ros-groovy-ompl : 0.12.1002173 -> 0.12.2002293
ros-groovy-opencv2 : 2.4.4 -> 2.4.5
ros-groovy-orocos-toolchain : 2.6.0.9 -> 2.6.0.10
ros-groovy-pluginlib : 1.9.19 -> 1.9.20
ros-groovy-pr2-moveit-config : 0.3.9 -> 0.3.11
ros-groovy-pr2-moveit-plugins : 0.3.9 -> 0.3.11
ros-groovy-pr2-moveit-tutorials : 0.3.9 -> 0.3.11
ros-groovy-ps3joy : 1.9.9 -> 1.9.10
ros-groovy-python-qt-binding : 0.2.8 -> 0.2.9
ros-groovy-resource-retriever : 1.9.33 -> 1.9.35
ros-groovy-robot-model : 1.9.33 -> 1.9.35
ros-groovy-robot-pose-publisher : 0.2.1 -> 0.2.2
ros-groovy-rocon-gateway-graph : 0.3.0 -> 0.3.1
ros-groovy-rocon-rqt-plugins : 0.3.0 -> 0.3.1
ros-groovy-ros-http-video-streamer : 0.1.3 -> 0.1.5
ros-groovy-rosapi : 0.4.3 -> 0.4.4
ros-groovy-rosauth : 0.1.2 -> 0.1.3
ros-groovy-rosbridge-library : 0.4.3 -> 0.4.4
ros-groovy-rosbridge-server : 0.4.3 -> 0.4.4
ros-groovy-rospy-message-converter : 0.1.3 -> 0.1.4
ros-groovy-rqt-action : 0.2.14 -> 0.2.16
ros-groovy-rqt-bag : 0.2.14 -> 0.2.16
ros-groovy-rqt-bag-plugins : 0.2.14 -> 0.2.16
ros-groovy-rqt-common-plugins : 0.2.14 -> 0.2.16
ros-groovy-rqt-console : 0.2.14 -> 0.2.16
ros-groovy-rqt-dep : 0.2.14 -> 0.2.16
ros-groovy-rqt-graph : 0.2.14 -> 0.2.16
ros-groovy-rqt-image-view : 0.2.14 -> 0.2.16
ros-groovy-rqt-launch : 0.2.14 -> 0.2.16
ros-groovy-rqt-logger-level : 0.2.14 -> 0.2.16
ros-groovy-rqt-msg : 0.2.14 -> 0.2.16
ros-groovy-rqt-nav-view : 0.2.9 -> 0.2.15
ros-groovy-rqt-plot : 0.2.14 -> 0.2.16
ros-groovy-rqt-pose-view : 0.2.9 -> 0.2.15
ros-groovy-rqt-publisher : 0.2.14 -> 0.2.16
ros-groovy-rqt-py-common : 0.2.14 -> 0.2.16
ros-groovy-rqt-py-console : 0.2.14 -> 0.2.16
ros-groovy-rqt-reconfigure : 0.2.14 -> 0.2.16
ros-groovy-rqt-robot-dashboard : 0.2.9 -> 0.2.15
ros-groovy-rqt-robot-monitor : 0.2.9 -> 0.2.15
ros-groovy-rqt-robot-plugins : 0.2.9 -> 0.2.15
ros-groovy-rqt-robot-steering : 0.2.9 -> 0.2.15
ros-groovy-rqt-runtime-monitor : 0.2.9 -> 0.2.15
ros-groovy-rqt-rviz : 0.2.9 -> 0.2.15
ros-groovy-rqt-service-caller : 0.2.14 -> 0.2.16
ros-groovy-rqt-shell : 0.2.14 -> 0.2.16
ros-groovy-rqt-srv : 0.2.14 -> 0.2.16
ros-groovy-rqt-topic : 0.2.14 -> 0.2.16
ros-groovy-rqt-web : 0.2.14 -> 0.2.16
ros-groovy-rtt-geometry : 0.3.0 -> 0.3.2
ros-groovy-rtt-ros-integration : 2.6.0-1 -> 2.6.0.2
ros-groovy-rviz : 1.9.28 -> 1.9.29
ros-groovy-simulator-gazebo : 1.7.11 -> 1.7.12
ros-groovy-spacenav-node : 1.9.9 -> 1.9.10
ros-groovy-srdf : 1.9.33 -> 1.9.35
ros-groovy-stereo-image-proc : 1.10.8 -> 1.10.9
ros-groovy-timestamp-tools : 1.6.5 -> 1.6.6
ros-groovy-turtlebot-apps : 2.0.1 -> 2.0.2
ros-groovy-urdf : 1.9.33 -> 1.9.35
ros-groovy-urdf-interface : 1.9.33 -> 1.9.35
ros-groovy-urdf-parser : 1.9.33 -> 1.9.35
ros-groovy-wiimote : 1.9.9 -> 1.9.10
ros-groovy-yocs-controllers : 0.2.2 -> 0.2.3
ros-groovy-yocs-velocity-smoother : 0.2.2 -> 0.2.3
ros-groovy-yujin-ocs : 0.2.2 -> 0.2.3

<div><div dir="ltr">We're pleased to announce the release of more than a hundred new and updated packages into Groovy. &nbsp;<div><br></div>
<div>See below for the full list. &nbsp;</div>
<div><br></div>
<div>Your friendly ROS Release Team<br><div><br></div>
<div><br></div>
<div>
<div>Packages Added:&nbsp;</div>
<div>ros-groovy-all : 1.0.0</div>
<div>ros-groovy-bride : 0.2.0</div>
<div>ros-groovy-chatter-concert : 0.3.5</div>
<div>ros-groovy-client-rosjava-jni : 0.1.11</div>

<div>ros-groovy-default-cfg-fkie : 0.2.2</div>
<div>ros-groovy-freenect-camera : 0.2.0</div>
<div>ros-groovy-freenect-launch : 0.2.0</div>
<div>ros-groovy-freenect-stack : 0.2.0</div>
<div>ros-groovy-glc : 0.5.8</div>
<div>ros-groovy-jsk-openni-kinect : 0.1.0</div>

<div>ros-groovy-jsk-rviz-plugins : 0.0.9</div>
<div>ros-groovy-knowrob : 0.3.0</div>
<div>ros-groovy-libcsm : 2013.03.26</div>
<div>ros-groovy-libfreenect : 0.1.2</div>
<div>ros-groovy-master-discovery-fkie : 0.2.2</div>
<div>

ros-groovy-master-sync-fkie : 0.2.2</div>
<div>ros-groovy-moveit-planners-ompl : 0.3.11</div>
<div>ros-groovy-moveit-ros-benchmarks-gui : 0.3.32</div>
<div>ros-groovy-moveit-ros-robot-interaction : 0.3.32</div>
<div>ros-groovy-multi-level-map : 0.0.2</div>

<div>ros-groovy-multi-level-map-msgs : 0.0.2</div>
<div>ros-groovy-multi-level-map-server : 0.0.2</div>
<div>ros-groovy-multi-level-map-utils : 0.0.2</div>
<div>ros-groovy-multimaster-fkie : 0.2.2</div>
<div>ros-groovy-node-manager-fkie : 0.2.2</div>

<div>ros-groovy-octomap-rviz-plugins : 0.0.1</div>
<div>ros-groovy-open-karto : 1.0.0</div>
<div>ros-groovy-rocon : 0.3.5</div>
<div>ros-groovy-rocon-gateway-tutorials : 0.3.5</div>
<div>ros-groovy-rocon-tutorials : 0.3.5</div>

<div>ros-groovy-rosbridge-suite : 0.4.4</div>
<div>ros-groovy-rqt-moveit : 0.2.15</div>
<div>ros-groovy-rqt-tf-tree : 0.2.15</div>
<div>ros-groovy-turtle-concert : 0.3.5</div>
<div>ros-groovy-turtle-race-concert : 0.3.5</div>

<div>ros-groovy-turtle-race-controllers : 0.3.5</div>
<div>ros-groovy-turtle-stroll : 0.3.5</div>
<div>ros-groovy-usb-cam : 0.1.2</div>
<div>ros-groovy-uwsim-osgocean : 1.0.2</div>
<div>ros-groovy-uwsim-osgworks : 2.0.2</div>

<div><br></div>
<div>Packages Removed:&nbsp;</div>
<div>ros-groovy-moveit-source-build-deps : 0.3.1</div>
<div>ros-groovy-turtlebot-simulator : 1.9.1</div>
<div><br></div>
<div>Packages Updated:&nbsp;</div>
<div>ros-groovy-camera-calibration : 1.10.8 -&gt; 1.10.9</div>

<div>ros-groovy-camera-info-manager-py : 0.2.0 -&gt; 0.2.1</div>
<div>ros-groovy-clearpath-husky : 0.3.3 -&gt; 0.3.4</div>
<div>ros-groovy-cmd-vel-mux : 0.2.2 -&gt; 0.2.3</div>
<div>ros-groovy-collada-parser : 1.9.33 -&gt; 1.9.35</div>

<div>ros-groovy-collada-urdf : 1.9.33 -&gt; 1.9.35</div>
<div>ros-groovy-depth-image-proc : 1.10.8 -&gt; 1.10.9</div>
<div>ros-groovy-driver-base : 1.6.5 -&gt; 1.6.6</div>
<div>ros-groovy-driver-common : 1.6.5 -&gt; 1.6.6</div>

<div>ros-groovy-ecto-opencv : 0.4.23 -&gt; 0.4.24</div>
<div>ros-groovy-erratic-robot : 0.3.2 -&gt; 0.3.3</div>
<div>ros-groovy-fcl : 0.2.8 -&gt; 0.2.9</div>
<div>ros-groovy-geometric-shapes : 0.2.5 -&gt; 0.2.6</div>
<div>ros-groovy-husky-simulator : 0.1.1 -&gt; 0.1.2</div>

<div>ros-groovy-image-pipeline : 1.10.8 -&gt; 1.10.9</div>
<div>ros-groovy-image-proc : 1.10.8 -&gt; 1.10.9</div>
<div>ros-groovy-image-rotate : 1.10.8 -&gt; 1.10.9</div>
<div>ros-groovy-image-view : 1.10.8 -&gt; 1.10.9</div>

<div>ros-groovy-joy : 1.9.9 -&gt; 1.9.10</div>
<div>ros-groovy-joystick-drivers : 1.9.9 -&gt; 1.9.10</div>
<div>ros-groovy-kdl-parser : 1.9.33 -&gt; 1.9.35</div>
<div>ros-groovy-kobuki : 0.3.5 -&gt; 0.3.7</div>
<div>ros-groovy-kobuki-arm : 0.3.5 -&gt; 0.3.7</div>

<div>ros-groovy-kobuki-auto-docking : 0.3.5 -&gt; 0.3.7</div>
<div>ros-groovy-kobuki-bumper2pc : 0.3.5 -&gt; 0.3.7</div>
<div>ros-groovy-kobuki-controller-tutorial : 0.3.5 -&gt; 0.3.7</div>
<div>ros-groovy-kobuki-desktop : 0.1.5 -&gt; 0.1.6</div>

<div>ros-groovy-kobuki-driver : 0.3.5 -&gt; 0.3.7</div>
<div>ros-groovy-kobuki-ftdi : 0.3.5 -&gt; 0.3.7</div>
<div>ros-groovy-kobuki-keyop : 0.3.5 -&gt; 0.3.7</div>
<div>ros-groovy-kobuki-node : 0.3.5 -&gt; 0.3.7</div>
<div>
ros-groovy-kobuki-safety-controller : 0.3.5 -&gt; 0.3.7</div>
<div>ros-groovy-kobuki-testsuite : 0.3.5 -&gt; 0.3.7</div>
<div>ros-groovy-libsegwayrmp : 0.2.3 -&gt; 0.2.7</div>
<div>ros-groovy-mjpeg-server : 1.0.2 -&gt; 1.1.0</div>
<div>ros-groovy-moveit-commander : 0.3.2 -&gt; 0.3.5</div>

<div>ros-groovy-moveit-core : 0.3.16 -&gt; 0.3.19</div>
<div>ros-groovy-moveit-full : 0.3.1 -&gt; 0.3.3</div>
<div>ros-groovy-moveit-full-pr2 : 0.3.1 -&gt; 0.3.3</div>
<div>ros-groovy-moveit-msgs : 0.3.18 -&gt; 0.3.20</div>
<div>
ros-groovy-moveit-ompl-planners-core : 0.3.7 -&gt; 0.3.11</div>
<div>ros-groovy-moveit-ompl-planners-ros-plugin : 0.3.11 -&gt; 0.3.7</div>
<div>ros-groovy-moveit-planners : 0.3.11 -&gt; 0.3.7</div>
<div>ros-groovy-moveit-pr2 : 0.3.11 -&gt; 0.3.9</div>

<div>ros-groovy-moveit-ros : 0.3.25 -&gt; 0.3.32</div>
<div>ros-groovy-moveit-ros-benchmarks : 0.3.25 -&gt; 0.3.32</div>
<div>ros-groovy-moveit-ros-manipulation : 0.3.25 -&gt; 0.3.32</div>
<div>ros-groovy-moveit-ros-move-group : 0.3.25 -&gt; 0.3.32</div>

<div>ros-groovy-moveit-ros-perception : 0.3.25 -&gt; 0.3.32</div>
<div>ros-groovy-moveit-ros-planning : 0.3.25 -&gt; 0.3.32</div>
<div>ros-groovy-moveit-ros-planning-interface : 0.3.25 -&gt; None</div>
<div>ros-groovy-moveit-ros-visualization : 0.3.25 -&gt; 0.3.32</div>

<div>ros-groovy-moveit-ros-warehouse : 0.3.25 -&gt; 0.3.32</div>
<div>ros-groovy-moveit-setup-assistant : 0.3.6 -&gt; 0.3.8</div>
<div>ros-groovy-object-recognition-core : 0.5.1 -&gt; 0.5.2</div>
<div>ros-groovy-object-recognition-linemod : 0.2.11 -&gt; 0.2.12</div>

<div>ros-groovy-object-recognition-reconstruction : 0.2.22 -&gt; 0.2.23</div>
<div>ros-groovy-object-recognition-tabletop : 0.2.21 -&gt; 0.2.22</div>
<div>ros-groovy-object-recognition-tod : 0.4.14 -&gt; 0.4.15</div>
<div>ros-groovy-object-recognition-transparent-objects : 0.3.14 -&gt; 0.3.15</div>

<div>ros-groovy-ompl : 0.12.1002173 -&gt; 0.12.2002293</div>
<div>ros-groovy-opencv2 : 2.4.4 -&gt; 2.4.5</div>
<div>ros-groovy-orocos-toolchain : 2.6.0.9 -&gt; 2.6.0.10</div>
<div>ros-groovy-pluginlib : 1.9.19 -&gt; 1.9.20</div>

<div>ros-groovy-pr2-moveit-config : 0.3.9 -&gt; 0.3.11</div>
<div>ros-groovy-pr2-moveit-plugins : 0.3.9 -&gt; 0.3.11</div>
<div>ros-groovy-pr2-moveit-tutorials : 0.3.9 -&gt; 0.3.11</div>
<div>ros-groovy-ps3joy : 1.9.9 -&gt; 1.9.10</div>

<div>ros-groovy-python-qt-binding : 0.2.8 -&gt; 0.2.9</div>
<div>ros-groovy-resource-retriever : 1.9.33 -&gt; 1.9.35</div>
<div>ros-groovy-robot-model : 1.9.33 -&gt; 1.9.35</div>
<div>ros-groovy-robot-pose-publisher : 0.2.1 -&gt; 0.2.2</div>

<div>ros-groovy-rocon-gateway-graph : 0.3.0 -&gt; 0.3.1</div>
<div>ros-groovy-rocon-rqt-plugins : 0.3.0 -&gt; 0.3.1</div>
<div>ros-groovy-ros-http-video-streamer : 0.1.3 -&gt; 0.1.5</div>
<div>ros-groovy-rosapi : 0.4.3 -&gt; 0.4.4</div>

<div>ros-groovy-rosauth : 0.1.2 -&gt; 0.1.3</div>
<div>ros-groovy-rosbridge-library : 0.4.3 -&gt; 0.4.4</div>
<div>ros-groovy-rosbridge-server : 0.4.3 -&gt; 0.4.4</div>
<div>ros-groovy-rospy-message-converter : 0.1.3 -&gt; 0.1.4</div>

<div>ros-groovy-rqt-action : 0.2.14 -&gt; 0.2.16</div>
<div>ros-groovy-rqt-bag : 0.2.14 -&gt; 0.2.16</div>
<div>ros-groovy-rqt-bag-plugins : 0.2.14 -&gt; 0.2.16</div>
<div>ros-groovy-rqt-common-plugins : 0.2.14 -&gt; 0.2.16</div>

<div>ros-groovy-rqt-console : 0.2.14 -&gt; 0.2.16</div>
<div>ros-groovy-rqt-dep : 0.2.14 -&gt; 0.2.16</div>
<div>ros-groovy-rqt-graph : 0.2.14 -&gt; 0.2.16</div>
<div>ros-groovy-rqt-image-view : 0.2.14 -&gt; 0.2.16</div>
<div>

ros-groovy-rqt-launch : 0.2.14 -&gt; 0.2.16</div>
<div>ros-groovy-rqt-logger-level : 0.2.14 -&gt; 0.2.16</div>
<div>ros-groovy-rqt-msg : 0.2.14 -&gt; 0.2.16</div>
<div>ros-groovy-rqt-nav-view : 0.2.9 -&gt; 0.2.15</div>
<div>
ros-groovy-rqt-plot : 0.2.14 -&gt; 0.2.16</div>
<div>ros-groovy-rqt-pose-view : 0.2.9 -&gt; 0.2.15</div>
<div>ros-groovy-rqt-publisher : 0.2.14 -&gt; 0.2.16</div>
<div>ros-groovy-rqt-py-common : 0.2.14 -&gt; 0.2.16</div>
<div>ros-groovy-rqt-py-console : 0.2.14 -&gt; 0.2.16</div>

<div>ros-groovy-rqt-reconfigure : 0.2.14 -&gt; 0.2.16</div>
<div>ros-groovy-rqt-robot-dashboard : 0.2.9 -&gt; 0.2.15</div>
<div>ros-groovy-rqt-robot-monitor : 0.2.9 -&gt; 0.2.15</div>
<div>ros-groovy-rqt-robot-plugins : 0.2.9 -&gt; 0.2.15</div>

<div>ros-groovy-rqt-robot-steering : 0.2.9 -&gt; 0.2.15</div>
<div>ros-groovy-rqt-runtime-monitor : 0.2.9 -&gt; 0.2.15</div>
<div>ros-groovy-rqt-rviz : 0.2.9 -&gt; 0.2.15</div>
<div>ros-groovy-rqt-service-caller : 0.2.14 -&gt; 0.2.16</div>

<div>ros-groovy-rqt-shell : 0.2.14 -&gt; 0.2.16</div>
<div>ros-groovy-rqt-srv : 0.2.14 -&gt; 0.2.16</div>
<div>ros-groovy-rqt-topic : 0.2.14 -&gt; 0.2.16</div>
<div>ros-groovy-rqt-web : 0.2.14 -&gt; 0.2.16</div>
<div>ros-groovy-rtt-geometry : 0.3.0 -&gt; 0.3.2</div>

<div>ros-groovy-rtt-ros-integration : 2.6.0-1 -&gt; 2.6.0.2</div>
<div>ros-groovy-rviz : 1.9.28 -&gt; 1.9.29</div>
<div>ros-groovy-simulator-gazebo : 1.7.11 -&gt; 1.7.12</div>
<div>ros-groovy-spacenav-node : 1.9.9 -&gt; 1.9.10</div>

<div>ros-groovy-srdf : 1.9.33 -&gt; 1.9.35</div>
<div>ros-groovy-stereo-image-proc : 1.10.8 -&gt; 1.10.9</div>
<div>ros-groovy-timestamp-tools : 1.6.5 -&gt; 1.6.6</div>
<div>ros-groovy-turtlebot-apps : 2.0.1 -&gt; 2.0.2</div>

<div>ros-groovy-urdf : 1.9.33 -&gt; 1.9.35</div>
<div>ros-groovy-urdf-interface : 1.9.33 -&gt; 1.9.35</div>
<div>ros-groovy-urdf-parser : 1.9.33 -&gt; 1.9.35</div>
<div>ros-groovy-wiimote : 1.9.9 -&gt; 1.9.10</div>
<div>ros-groovy-yocs-controllers : 0.2.2 -&gt; 0.2.3</div>

<div>ros-groovy-yocs-velocity-smoother : 0.2.2 -&gt; 0.2.3</div>
<div>ros-groovy-yujin-ocs : 0.2.2 -&gt; 0.2.3</div>
</div>
<div><br></div>
</div>
</div></div>
Hal Gottfried | 7 May 2013 22:29
Gravatar

Re: ros-users Digest, Vol 39, Issue 6

Unsubscribe 

-- 
Hal Gottfried
Sent with Sparrow

On Tuesday, May 7, 2013 at 2:00 PM, ros-users-request <at> code.ros.org wrote:

Send ros-users mailing list submissions to
ros-users <at> code.ros.org

To subscribe or unsubscribe via the World Wide Web, visit
https://code.ros.org/mailman/listinfo/ros-users
or, via email, send a message with subject or body 'help' to
ros-users-request <at> code.ros.org

You can reach the person managing the list at
ros-users-owner <at> code.ros.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of ros-users digest..."


Today's Topics:

1. New packages for Fuerte and Hydro released (Tully Foote)
2. Ros Java + Android (Daniel Stonier)
3. Announcing orst-ros-pkg (Dan Lazewatsky)


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

Message: 1
Date: Tue, 7 May 2013 00:36:48 -0700
From: Tully Foote <tfoote <at> osrfoundation.org>
To: User discussions <ros-users <at> code.ros.org>
Subject: [ros-users] New packages for Fuerte and Hydro released
Message-ID:
<CAM7qi7UAcoaDQk4hjrDDrktLzE-OdtDddCeCtxtpw8CUkoj2yw <at> mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"

Hi Everyone,

We're pleased to announce the release of several new Hydro packages as well
as many update for both Hydro and Fuerte. This includes the patches which
fix the roslisp builds in Fuerte.

Thank you to all the maintainers who made releases!

Your friendly ROS Release Team


Updates to Fuerte:
Packages Added:
ros-fuerte-cram-core : 0.1.8
ros-fuerte-roslisp-common : 0.2.1
ros-fuerte-roslisp-support : 0.3.1

Packages Removed:
ros-fuerte-keyboardteleopjs : 0.1.1
ros-fuerte-map2djs : 0.1.0
ros-fuerte-mjpegcanvasjs : 0.1.0
ros-fuerte-nav2djs : 0.1.1
ros-fuerte-rms : 0.2.0
ros-fuerte-rosjs : 0.0.15

Packages Updated:
ros-fuerte-object-recognition-core : 0.5.1 -> 0.5.2
ros-fuerte-object-recognition-linemod : 0.2.11 -> 0.2.12
ros-fuerte-object-recognition-reconstruction : 0.2.22 -> 0.2.23
ros-fuerte-object-recognition-tabletop : 0.2.21 -> 0.2.22
ros-fuerte-object-recognition-tod : 0.4.14 -> 0.4.15
ros-fuerte-object-recognition-transparent-objects : 0.3.14 -> 0.3.15
ros-fuerte-orocos-toolchain : 2.6.0.9 -> 2.6.0.10
ros-fuerte-rospack : 2.0.13 -> 2.0.14
ros-fuerte-rtt-geometry : 0.3.0 -> 0.3.2
ros-fuerte-rtt-ros-integration : 2.6.0-1 -> 2.6.0.2


Updates to Hydro:
Packages Added:
ros-hydro-bfl : 0.7.0
ros-hydro-octomap-ros : 0.3.0
ros-hydro-pr2-dashboard-aggregator : 1.11.0
ros-hydro-pr2-machine : 1.11.0
ros-hydro-pr2-msgs : 1.11.0

Packages Removed:

Packages Updated:
ros-hydro-camera-calibration : 1.10.7 -> 1.10.9
ros-hydro-depth-image-proc : 1.10.7 -> 1.10.9
ros-hydro-driver-base : 1.6.5 -> 1.6.6
ros-hydro-driver-common : 1.6.5 -> 1.6.6
ros-hydro-image-pipeline : 1.10.7 -> 1.10.9
ros-hydro-image-proc : 1.10.7 -> 1.10.9
ros-hydro-image-rotate : 1.10.7 -> 1.10.9
ros-hydro-image-view : 1.10.7 -> 1.10.9
ros-hydro-libsegwayrmp : 0.2.6 -> 0.2.7
ros-hydro-sicktoolbox-wrapper : 2.5.1 -> 2.5.2
ros-hydro-stereo-image-proc : 1.10.7 -> 1.10.9
ros-hydro-timestamp-tools : 1.6.5 -> 1.6.6
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </lurker/list/ros-users.html/attachments/20130507/e4b9be74/attachment-0001.html>

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

Message: 2
Date: Tue, 7 May 2013 16:50:22 +0900
From: Daniel Stonier <d.stonier <at> gmail.com>
To: User discussions <ros-users <at> code.ros.org>
Subject: [ros-users] Ros Java + Android
Message-ID:
<CAP6aRqb7rrReCKz4Wgp-A36Gn0w2T_q2BhLhMrCgUT3ePb0CcQ <at> mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

I've been watching our devs struggling with the android build environment
for a while and decided to take a look at it for a couple of days recently.

The result of which was some work to help make it easier. In short (more
detail below) you can build in about the same manner as you would a typical
catkin workspace - one shot builds and dependency tracking across repos.

If you would like to get a handle on what's done, I've written up some
instructions on how to build the current turtlebot android apps (make sure
to use the '*legacy*' sources)
here<http://ros.org/wiki/turtlebot_android/Tutorials/hydro/Installation>
.

These are just tentative though. I'd like to get together with whoever's
interested to talk about how we can push this further (and re-integrate
with damon and chad's code) so we can have a convenient development
environment for android with hydro. Up until now it's felt terribly hackish.

Probably a good place to start some discussion would be at a BoF at RosCon.
We can then continue with a sig thereafter. Of course, if you're not going
to RosCon, let us know what you think and we can float any issues there.
Being a relative newbie with java/gradle/maven/android I have some starters:


- Should we setup a maven repo for rosjava jars or integrate with bloom?
- If maven, what is the best approach and how to do for android packages?
- Is it possible to speed up the android build process (what's making it
slow)?
- How best to organise android code?


Cheers,
Daniel

PS : A more detailed summary of the changes so far:

- catkinization
- Can use the usual tools (e.g. catkin_make)
- Parallel builds
- Chained workspaces (much lighter workspaces -> faster builds)
- catkin_rosjava_setup()
- Calls out to gradle in the compile step.
- catkin_android_setup()
- Adds library deps (from package.xml) to project.properties in the
cmake step
- Retargets the project (via ANDROID_TARGET cmake variable)
- Updates the project in the cmake step
- Calls out to gradle in the compile step
- catkin_create_android_library_pkg and catkin_create_android_pkg
- includes kazuto's minor patches into android_gingerbread
- moves kazuto's app manager patches into android_apps
- split gingerbread and honeycomb into separate stacks so it easy to
target a workspace for one or the other.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </lurker/list/ros-users.html/attachments/20130507/3e980d13/attachment-0001.html>

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

Message: 3
Date: Tue, 7 May 2013 10:56:02 -0500
From: Dan Lazewatsky <lazewatd <at> engr.orst.edu>
To: User discussions <ros-users <at> code.ros.org>
Subject: [ros-users] Announcing orst-ros-pkg
Message-ID:
<CAO0H620KzcJjc-VXRn9O=hvQn6fgagtPv6s0uG6MBmHEaZ8cmw <at> mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"

The Personal Robotics Lab in the School of Mechanical, Industrial and
Manufacturing Engineering at Oregon State University is proud to announce
our repository, orst-ros-pkg. Our current released stacks and packages are:

- http://ros.org/wiki/head_tracking - ROS Wrapper around Fanelli et al.'s
Real Time Head Pose Estimation from Consumer Depth Cameras [1]. Provides
6-dof head pose estimation using data from a Kinect or other similar device.
- http://ros.org/wiki/3d_interaction - Contains packages for projecting
interfaces into the world, and interacting with those interfaces, as well
as utilities for camera-projector calibration, and intersecting rays with
various types of world models.
- http://ros.org/wiki/projected_interface_builder - A utility for
graphically building projected interfaces to be used with the above stack.
- http://ros.org/wiki/ir_comm - A simple ROS interface to the phidgets_ir
board enabling learning IR codes, and using ROS messages to transmit codes.

The above packages were developed as part of the Robots for Humanity
Project [2].

- http://ros.org/wiki/rostop_gui - RQT plugin for monitoring ROS
processes, similar to Ubuntu's System Monitor.

[1] Fanelli et al.'s Real Time Head Pose Estimation from Consumer Depth
Cameras. 33rd Annual Symposium of the German Association for Pattern
Recognition (DAGM'11), 2011.
[2] Chen, T.L.; Ciocarlie, M.; Cousins, S.; Grice, P.M.; Hawkins, K.;
Kaijen Hsiao; Kemp, C.C.; Chih-Hung King; Lazewatsky, D.A.; Leeper, A.E.;
Hai Nguyen; Paepcke, A.; Pantofaru, C.; Smart, W.D.; Takayama, L., "Robots
for humanity: using assistive robotics to empower people with
disabilities," Robotics & Automation Magazine, IEEE , vol.20, no.1,
pp.30,39, March 2013
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </lurker/list/ros-users.html/attachments/20130507/33100668/attachment-0001.html>

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

_______________________________________________
ros-users mailing list
ros-users <at> code.ros.org
https://code.ros.org/mailman/listinfo/ros-users


End of ros-users Digest, Vol 39, Issue 6
****************************************

<div>
<div>
        Unsubscribe&nbsp;
    </div>
    <div>
<div><br></div>--&nbsp;<br>Hal Gottfried<br><div>Sent with <a href="http://www.sparrowmailapp.com/?sig">Sparrow</a>
</div>
<div><br></div>
</div>

    <p>On Tuesday, May 7, 2013 at 2:00 PM, ros-users-request <at> code.ros.org wrote:</p>
    <blockquote type="cite">
        <div><div>
<div>Send ros-users mailing list submissions to</div>
<div>	ros-users <at> code.ros.org</div>
<div><br></div>
<div>To subscribe or unsubscribe via the World Wide Web, visit</div>
<div>	https://code.ros.org/mailman/listinfo/ros-users</div>
<div>or, via email, send a message with subject or body 'help' to</div>
<div>	ros-users-request <at> code.ros.org</div>
<div><br></div>
<div>You can reach the person managing the list at</div>
<div>	ros-users-owner <at> code.ros.org</div>
<div><br></div>
<div>When replying, please edit your Subject line so it is more specific</div>
<div>than "Re: Contents of ros-users digest..."</div>
<div><br></div>
<div><br></div>
<div>Today's Topics:</div>
<div><br></div>
<div>   1. New packages for Fuerte and Hydro released (Tully Foote)</div>
<div>   2. Ros Java + Android (Daniel Stonier)</div>
<div>   3. Announcing orst-ros-pkg (Dan Lazewatsky)</div>
<div><br></div>
<div><br></div>
<div>----------------------------------------------------------------------</div>
<div><br></div>
<div>Message: 1</div>
<div>Date: Tue, 7 May 2013 00:36:48 -0700</div>
<div>From: Tully Foote &lt;tfoote <at> osrfoundation.org&gt;</div>
<div>To: User discussions &lt;ros-users <at> code.ros.org&gt;</div>
<div>Subject: [ros-users] New packages for Fuerte and Hydro released</div>
<div>Message-ID:</div>
<div>	&lt;CAM7qi7UAcoaDQk4hjrDDrktLzE-OdtDddCeCtxtpw8CUkoj2yw <at> mail.gmail.com&gt;</div>
<div>Content-Type: text/plain; charset="iso-8859-1"</div>
<div><br></div>
<div>Hi Everyone,</div>
<div><br></div>
<div>We're pleased to announce the release of several new Hydro packages as well</div>
<div>as many update for both Hydro and Fuerte.  This includes the patches which</div>
<div>fix the roslisp builds in Fuerte.</div>
<div><br></div>
<div>Thank you to all the maintainers who made releases!</div>
<div><br></div>
<div>Your friendly ROS Release Team</div>
<div><br></div>
<div><br></div>
<div>Updates to Fuerte:</div>
<div>Packages Added:</div>
<div>ros-fuerte-cram-core : 0.1.8</div>
<div>ros-fuerte-roslisp-common : 0.2.1</div>
<div>ros-fuerte-roslisp-support : 0.3.1</div>
<div><br></div>
<div>Packages Removed:</div>
<div>ros-fuerte-keyboardteleopjs : 0.1.1</div>
<div>ros-fuerte-map2djs : 0.1.0</div>
<div>ros-fuerte-mjpegcanvasjs : 0.1.0</div>
<div>ros-fuerte-nav2djs : 0.1.1</div>
<div>ros-fuerte-rms : 0.2.0</div>
<div>ros-fuerte-rosjs : 0.0.15</div>
<div><br></div>
<div>Packages Updated:</div>
<div>ros-fuerte-object-recognition-core : 0.5.1 -&gt; 0.5.2</div>
<div>ros-fuerte-object-recognition-linemod : 0.2.11 -&gt; 0.2.12</div>
<div>ros-fuerte-object-recognition-reconstruction : 0.2.22 -&gt; 0.2.23</div>
<div>ros-fuerte-object-recognition-tabletop : 0.2.21 -&gt; 0.2.22</div>
<div>ros-fuerte-object-recognition-tod : 0.4.14 -&gt; 0.4.15</div>
<div>ros-fuerte-object-recognition-transparent-objects : 0.3.14 -&gt; 0.3.15</div>
<div>ros-fuerte-orocos-toolchain : 2.6.0.9 -&gt; 2.6.0.10</div>
<div>ros-fuerte-rospack : 2.0.13 -&gt; 2.0.14</div>
<div>ros-fuerte-rtt-geometry : 0.3.0 -&gt; 0.3.2</div>
<div>ros-fuerte-rtt-ros-integration : 2.6.0-1 -&gt; 2.6.0.2</div>
<div><br></div>
<div><br></div>
<div>Updates to Hydro:</div>
<div>Packages Added:</div>
<div>ros-hydro-bfl : 0.7.0</div>
<div>ros-hydro-octomap-ros : 0.3.0</div>
<div>ros-hydro-pr2-dashboard-aggregator : 1.11.0</div>
<div>ros-hydro-pr2-machine : 1.11.0</div>
<div>ros-hydro-pr2-msgs : 1.11.0</div>
<div><br></div>
<div>Packages Removed:</div>
<div><br></div>
<div>Packages Updated:</div>
<div>ros-hydro-camera-calibration : 1.10.7 -&gt; 1.10.9</div>
<div>ros-hydro-depth-image-proc : 1.10.7 -&gt; 1.10.9</div>
<div>ros-hydro-driver-base : 1.6.5 -&gt; 1.6.6</div>
<div>ros-hydro-driver-common : 1.6.5 -&gt; 1.6.6</div>
<div>ros-hydro-image-pipeline : 1.10.7 -&gt; 1.10.9</div>
<div>ros-hydro-image-proc : 1.10.7 -&gt; 1.10.9</div>
<div>ros-hydro-image-rotate : 1.10.7 -&gt; 1.10.9</div>
<div>ros-hydro-image-view : 1.10.7 -&gt; 1.10.9</div>
<div>ros-hydro-libsegwayrmp : 0.2.6 -&gt; 0.2.7</div>
<div>ros-hydro-sicktoolbox-wrapper : 2.5.1 -&gt; 2.5.2</div>
<div>ros-hydro-stereo-image-proc : 1.10.7 -&gt; 1.10.9</div>
<div>ros-hydro-timestamp-tools : 1.6.5 -&gt; 1.6.6</div>
<div>-------------- next part --------------</div>
<div>An HTML attachment was scrubbed...</div>
<div>URL: &lt;/lurker/list/ros-users.html/attachments/20130507/e4b9be74/attachment-0001.html&gt;</div>
<div><br></div>
<div>------------------------------</div>
<div><br></div>
<div>Message: 2</div>
<div>Date: Tue, 7 May 2013 16:50:22 +0900</div>
<div>From: Daniel Stonier &lt;d.stonier <at> gmail.com&gt;</div>
<div>To: User discussions &lt;ros-users <at> code.ros.org&gt;</div>
<div>Subject: [ros-users] Ros Java + Android</div>
<div>Message-ID:</div>
<div>	&lt;CAP6aRqb7rrReCKz4Wgp-A36Gn0w2T_q2BhLhMrCgUT3ePb0CcQ <at> mail.gmail.com&gt;</div>
<div>Content-Type: text/plain; charset="utf-8"</div>
<div><br></div>
<div>I've been watching our devs struggling with the android build environment</div>
<div>for a while and decided to take a look at it for a couple of days recently.</div>
<div><br></div>
<div>The result of which was some work to help make it easier. In short (more</div>
<div>detail below) you can build in about the same manner as you would a typical</div>
<div>catkin workspace - one shot builds and dependency tracking across repos.</div>
<div><br></div>
<div>If you would like to get a handle on what's done, I've written up some</div>
<div>instructions on how to build the current turtlebot android apps (make sure</div>
<div>to use the '*legacy*' sources)</div>
<div>here&lt;http://ros.org/wiki/turtlebot_android/Tutorials/hydro/Installation&gt;</div>
<div>.</div>
<div><br></div>
<div>These are just tentative though. I'd like to get together with whoever's</div>
<div>interested to talk about how we can push this further (and re-integrate</div>
<div>with damon and chad's code) so we can have a convenient development</div>
<div>environment for android with hydro. Up until now it's felt terribly hackish.</div>
<div><br></div>
<div>Probably a good place to start some discussion would be at a BoF at RosCon.</div>
<div>We can then continue with a sig thereafter. Of course, if you're not going</div>
<div>to RosCon, let us know what you think and we can float any issues there.</div>
<div>Being a relative newbie with java/gradle/maven/android I have some starters:</div>
<div><br></div>
<div><br></div>
<div>   - Should we setup a maven repo for rosjava jars or integrate with bloom?</div>
<div>   - If maven, what is the best approach and how to do for android packages?</div>
<div>   - Is it possible to speed up the android build process (what's making it</div>
<div>   slow)?</div>
<div>   - How best to organise android code?</div>
<div><br></div>
<div><br></div>
<div>Cheers,</div>
<div>Daniel</div>
<div><br></div>
<div>PS : A more detailed summary of the changes so far:</div>
<div><br></div>
<div>   - catkinization</div>
<div>      - Can use the usual tools (e.g. catkin_make)</div>
<div>      - Parallel builds</div>
<div>      - Chained workspaces (much lighter workspaces -&gt; faster builds)</div>
<div>   - catkin_rosjava_setup()</div>
<div>      - Calls out to gradle in the compile step.</div>
<div>   - catkin_android_setup()</div>
<div>      - Adds library deps (from package.xml) to project.properties in the</div>
<div>      cmake step</div>
<div>      - Retargets the project (via ANDROID_TARGET cmake variable)</div>
<div>      - Updates the project in the cmake step</div>
<div>      - Calls out to gradle in the compile step</div>
<div>   - catkin_create_android_library_pkg and catkin_create_android_pkg</div>
<div>   - includes kazuto's minor patches into android_gingerbread</div>
<div>   - moves kazuto's app manager patches into android_apps</div>
<div>   - split gingerbread and honeycomb into separate stacks so it easy to</div>
<div>   target a workspace for one or the other.</div>
<div>-------------- next part --------------</div>
<div>An HTML attachment was scrubbed...</div>
<div>URL: &lt;/lurker/list/ros-users.html/attachments/20130507/3e980d13/attachment-0001.html&gt;</div>
<div><br></div>
<div>------------------------------</div>
<div><br></div>
<div>Message: 3</div>
<div>Date: Tue, 7 May 2013 10:56:02 -0500</div>
<div>From: Dan Lazewatsky &lt;lazewatd <at> engr.orst.edu&gt;</div>
<div>To: User discussions &lt;ros-users <at> code.ros.org&gt;</div>
<div>Subject: [ros-users] Announcing orst-ros-pkg</div>
<div>Message-ID:</div>
<div>	&lt;CAO0H620KzcJjc-VXRn9O=hvQn6fgagtPv6s0uG6MBmHEaZ8cmw <at> mail.gmail.com&gt;</div>
<div>Content-Type: text/plain; charset="iso-8859-1"</div>
<div><br></div>
<div>The Personal Robotics Lab in the School of Mechanical, Industrial and</div>
<div>Manufacturing Engineering at Oregon State University is proud to announce</div>
<div>our repository, orst-ros-pkg. Our current released stacks and packages are:</div>
<div><br></div>
<div> - http://ros.org/wiki/head_tracking - ROS Wrapper around Fanelli et al.'s</div>
<div>Real Time Head Pose Estimation from Consumer Depth Cameras [1]. Provides</div>
<div>6-dof head pose estimation using data from a Kinect or other similar device.</div>
<div> - http://ros.org/wiki/3d_interaction - Contains packages for projecting</div>
<div>interfaces into the world, and interacting with those interfaces, as well</div>
<div>as utilities for camera-projector calibration, and intersecting rays with</div>
<div>various types of world models.</div>
<div> - http://ros.org/wiki/projected_interface_builder - A utility for</div>
<div>graphically building projected interfaces to be used with the above stack.</div>
<div> - http://ros.org/wiki/ir_comm - A simple ROS interface to the phidgets_ir</div>
<div>board enabling learning IR codes, and using ROS messages to transmit codes.</div>
<div><br></div>
<div>The above packages were developed as part of the Robots for Humanity</div>
<div>Project [2].</div>
<div><br></div>
<div> - http://ros.org/wiki/rostop_gui - RQT plugin for monitoring ROS</div>
<div>processes, similar to Ubuntu's System Monitor.</div>
<div><br></div>
<div>[1] Fanelli et al.'s Real Time Head Pose Estimation from Consumer Depth</div>
<div>Cameras. 33rd Annual Symposium of the German Association for Pattern</div>
<div>Recognition (DAGM'11), 2011.</div>
<div>[2] Chen, T.L.; Ciocarlie, M.; Cousins, S.; Grice, P.M.; Hawkins, K.;</div>
<div>Kaijen Hsiao; Kemp, C.C.; Chih-Hung King; Lazewatsky, D.A.; Leeper, A.E.;</div>
<div>Hai Nguyen; Paepcke, A.; Pantofaru, C.; Smart, W.D.; Takayama, L., "Robots</div>
<div>for humanity: using assistive robotics to empower people with</div>
<div>disabilities," Robotics &amp; Automation Magazine, IEEE , vol.20, no.1,</div>
<div>pp.30,39, March 2013</div>
<div>-------------- next part --------------</div>
<div>An HTML attachment was scrubbed...</div>
<div>URL: &lt;/lurker/list/ros-users.html/attachments/20130507/33100668/attachment-0001.html&gt;</div>
<div><br></div>
<div>------------------------------</div>
<div><br></div>
<div>_______________________________________________</div>
<div>ros-users mailing list</div>
<div>ros-users <at> code.ros.org</div>
<div>https://code.ros.org/mailman/listinfo/ros-users</div>
<div><br></div>
<div><br></div>
<div>End of ros-users Digest, Vol 39, Issue 6</div>
<div>****************************************</div>
</div></div>

         

         
    </blockquote>

    <div>
        <br>
</div>
</div>
Dan Lazewatsky | 7 May 2013 17:56
Gravatar

Announcing orst-ros-pkg

The Personal Robotics Lab in the School of Mechanical, Industrial and Manufacturing Engineering at Oregon State University is proud to announce our repository, orst-ros-pkg. Our current released stacks and packages are:


 - http://ros.org/wiki/head_tracking - ROS Wrapper around Fanelli et al.'s Real Time Head Pose Estimation from Consumer Depth Cameras [1]. Provides 6-dof head pose estimation using data from a Kinect or other similar device.
 - http://ros.org/wiki/3d_interaction - Contains packages for projecting interfaces into the world, and interacting with those interfaces, as well as utilities for camera-projector calibration, and intersecting rays with various types of world models.
 - http://ros.org/wiki/projected_interface_builder - A utility for graphically building projected interfaces to be used with the above stack.
 - http://ros.org/wiki/ir_comm - A simple ROS interface to the phidgets_ir board enabling learning IR codes, and using ROS messages to transmit codes.

The above packages were developed as part of the Robots for Humanity Project [2].

 - http://ros.org/wiki/rostop_gui - RQT plugin for monitoring ROS processes, similar to Ubuntu's System Monitor.

[1] Fanelli et al.'s Real Time Head Pose Estimation from Consumer Depth Cameras. 33rd Annual Symposium of the German Association for Pattern Recognition (DAGM'11), 2011.
[2] Chen, T.L.; Ciocarlie, M.; Cousins, S.; Grice, P.M.; Hawkins, K.; Kaijen Hsiao; Kemp, C.C.; Chih-Hung King; Lazewatsky, D.A.; Leeper, A.E.; Hai Nguyen; Paepcke, A.; Pantofaru, C.; Smart, W.D.; Takayama, L., "Robots for humanity: using assistive robotics to empower people with disabilities," Robotics & Automation Magazine, IEEE , vol.20, no.1, pp.30,39, March 2013
<div>
<p>The Personal Robotics Lab in the School of&nbsp;Mechanical, Industrial and Manufacturing Engineering at Oregon State University is proud to announce our repository, orst-ros-pkg. Our current released stacks and packages are:</p>
<div>
<br><div>&nbsp;-&nbsp;<a href="http://ros.org/wiki/head_tracking">http://ros.org/wiki/head_tracking</a> - ROS Wrapper around&nbsp;Fanelli et al.'s Real Time Head Pose Estimation from Consumer Depth Cameras [1]. Provides 6-dof head pose estimation using data from a Kinect or other similar device.</div>
<div>&nbsp;-&nbsp;<a href="http://ros.org/wiki/3d_interaction">http://ros.org/wiki/3d_interaction</a> -&nbsp;Contains packages for projecting interfaces into the world, and interacting with those interfaces, as well as utilities for camera-projector calibration, and intersecting rays with various types of world models.</div>
<div>&nbsp;-&nbsp;<a href="http://ros.org/wiki/projected_interface_builder">http://ros.org/wiki/projected_interface_builder</a> -&nbsp;A utility for graphically building projected interfaces to be used with the above stack.</div>
<div>&nbsp;-&nbsp;<a href="http://ros.org/wiki/ir_comm">http://ros.org/wiki/ir_comm</a> - A simple ROS interface to the phidgets_ir board enabling learning IR codes, and using ROS messages to transmit codes.</div>
<div><br></div>
<div>The above packages were developed as part of the Robots for Humanity Project [2].</div>
<div><br></div>
<div>&nbsp;-&nbsp;<a href="http://ros.org/wiki/rostop_gui">http://ros.org/wiki/rostop_gui</a> -&nbsp;RQT plugin for monitoring ROS processes, similar to Ubuntu's System Monitor.</div>
<div><br></div>
<div>[1]&nbsp;Fanelli et al.'s Real Time Head Pose Estimation from Consumer Depth Cameras. 33rd Annual Symposium of the German Association for Pattern Recognition (DAGM'11), 2011.</div>
</div>
<div>[2]&nbsp;Chen, T.L.; Ciocarlie, M.; Cousins, S.; Grice, P.M.; Hawkins, K.; Kaijen Hsiao; Kemp, C.C.; Chih-Hung King; Lazewatsky, D.A.; Leeper, A.E.; Hai Nguyen; Paepcke, A.; Pantofaru, C.; Smart, W.D.; Takayama, L., "Robots for humanity: using assistive robotics to empower people with disabilities," Robotics &amp; Automation Magazine, IEEE , vol.20, no.1, pp.30,39, March 2013</div>
</div>
Daniel Stonier | 7 May 2013 09:50
Picon
Gravatar

Ros Java + Android


I've been watching our devs struggling with the android build environment for a while and decided to take a look at it for a couple of days recently. 

The result of which was some work to help make it easier. In short (more detail below) you can build in about the same manner as you would a typical catkin workspace - one shot builds and dependency tracking across repos.

If you would like to get a handle on what's done, I've written up some instructions on how to build the current turtlebot android apps (make sure to use the 'legacy' sources) here.

These are just tentative though. I'd like to get together with whoever's interested to talk about how we can push this further (and re-integrate with damon and chad's code) so we can have a convenient development environment for android with hydro. Up until now it's felt terribly hackish.

Probably a good place to start some discussion would be at a BoF at RosCon. We can then continue with a sig thereafter. Of course, if you're not going to RosCon, let us know what you think and we can float any issues there. Being a relative newbie with java/gradle/maven/android I have some starters:

  • Should we setup a maven repo for rosjava jars or integrate with bloom?
  • If maven, what is the best approach and how to do for android packages?
  • Is it possible to speed up the android build process (what's making it slow)?
  • How best to organise android code?

Cheers,
Daniel

PS : A more detailed summary of the changes so far:
  • catkinization
    • Can use the usual tools (e.g. catkin_make)
    • Parallel builds
    • Chained workspaces (much lighter workspaces -> faster builds)
  • catkin_rosjava_setup()
    • Calls out to gradle in the compile step.
  • catkin_android_setup()
    • Adds library deps (from package.xml) to project.properties in the cmake step
    • Retargets the project (via ANDROID_TARGET cmake variable)
    • Updates the project in the cmake step
    • Calls out to gradle in the compile step
  • catkin_create_android_library_pkg and catkin_create_android_pkg
  • includes kazuto's minor patches into android_gingerbread
  • moves kazuto's app manager patches into android_apps
  • split gingerbread and honeycomb into separate stacks so it easy to target a workspace for one or the other.








<div><div dir="ltr">
<div><br></div>
<div>I've been watching our devs struggling with the android build environment for a while and decided to take a look at it for a couple of days recently.&nbsp;</div>
<div><br></div>
<div>The result of which was some work to help make it easier. In short (more detail below) you can build in about the same manner as you would a typical catkin workspace - one shot builds and dependency tracking across repos.</div>
<div><br></div>
<div>If you would like to get a handle on what's done, I've written up some instructions on how to build the current turtlebot android apps (make sure to use the 'legacy' sources) <a href="http://ros.org/wiki/turtlebot_android/Tutorials/hydro/Installation">here</a>.</div>
<div><br></div>
<div>These are just tentative though. I'd like to get together with whoever's interested to talk about how we can push this further (and re-integrate with damon and chad's code) so we can have a convenient development environment for android with hydro. Up until now it's felt terribly hackish.</div>
<div><br></div>
<div>Probably a good place to start some discussion would be at a BoF at RosCon. We can then continue with a sig thereafter. Of course, if you're not going to RosCon, let us know what you think and we can float any issues there. Being a relative newbie with java/gradle/maven/android I have some starters:</div>
<div><br></div>
<div><ul>
<li>Should we setup a maven repo for rosjava jars or integrate with bloom?</li>
<li>If maven, what is the best approach and how to do for android packages?</li>
<li>
Is it possible to speed up the android build process (what's making it slow)?</li>
<li>How best to organise android code?</li>
</ul></div>
<div><br></div>
<div>Cheers,</div>
<div>Daniel</div>
<div>
<br>
</div>
<div>PS : A more detailed summary of the changes so far:<br>
</div>
<div>
<ul>
<li>catkinization</li>
<ul>
<li>Can use the usual tools (e.g. catkin_make)</li>
<li>Parallel builds</li>
<li>Chained workspaces (much lighter workspaces -&gt; faster builds)</li>
</ul>
<li>catkin_rosjava_setup()</li>
<ul><li>Calls out to gradle in the compile step.</li></ul>
<li>catkin_android_setup()</li>
<ul>
<li>Adds library deps (from package.xml) to project.properties in the cmake step</li>
<li>Retargets the project (via ANDROID_TARGET cmake variable)</li>
<li>Updates the project in the cmake step</li>
<li>Calls out to gradle in the compile step</li>
</ul>
<li>catkin_create_android_library_pkg and catkin_create_android_pkg</li>
<li>includes kazuto's minor patches into android_gingerbread</li>
<li>
moves kazuto's app manager patches into android_apps</li>
<li>split gingerbread and honeycomb into separate stacks so it easy to target a workspace for one or the other.</li>
</ul>
<div><br></div>
</div>
<div>
<br>
</div>
<div><br></div>
<div><br></div>
<div><br></div>
<div><br></div>
<div><br></div>
<div><br></div>
</div></div>

Gmane