Jonathan Bohren | 5 Mar 17:56 2015
Picon

Some ROS devs got frustrated with Catkin. You won't believe what happened next!

All,

This is what they built: http://catkin-tools.readthedocs.org/

Quick summary:
- `catkin_tools` is an improved toolchain for building catkin workspaces
- this toolchain is ready for beta testing, and we want your feedback
- the CLI command is simply called `catkin`
- the build sub-command is `catkin build`
- it builds packages with isolated build directories (no CMake crosstalk)
- it builds packages in parallel
- it builds "pure" CMake packages that don't use Catkin macros
- it lets you build selected packages in a workspace
- it lets you build packages without cd'ing to the workspace root
- it needs to be tested more before being recommended over `catkin_make`
- the documentation for all the additional features can be found here: http://catkin-tools.readthedocs.org/

Install it now (from the ROS debian repos):
sudo apt-get install python-catkin-tools

Or install it now (from PIP):
sudo pip install -U catkin_tools

Take a look at the cheat sheet:

Give it a try and report issues or feature requests here:

For some background and the relationship to the current top-level `catkin_make` command:

Many thanks to Contributors:
William Woodall
Jonathan Bohren
Nikolaus Demmel
Dave Coleman
Felix Ruess
Dirk Thomas
Kartik Mohta
Thibault Kruse
Ian McMahon
Kei Okada

Those of us who've put time into this project over the last year hope that `catkin build` makes your lives less stressful and helps you build robotic systems faster. 

best,
catkin_tools contributors
<div><div dir="ltr">All,<div><br></div>
<div>This is what they built:&nbsp;<span><a href="http://catkin-tools.readthedocs.org/">http://catkin-tools.readthedocs.org/</a></span>
</div>
<div><br></div>
<div>Quick summary:</div>
<div><span>- `catkin_tools` is an improved toolchain for building catkin workspaces</span></div>
<div>
<span>- this toolchain is ready for beta testing, and we want your feedback</span><br>
</div>
<div><span>- the CLI command is simply called `catkin`</span></div>
<div><span>- the build sub-command is `catkin build`</span></div>
<div>
<span>- it builds packages with isolated build directories (no CMake crosstalk)</span><br>
</div>
<div>
<span>- it builds packages in parallel</span><br>
</div>
<div><span>- it builds "pure" CMake packages that don't use Catkin macros</span></div>
<div>- it lets you build selected packages in a workspace</div>
<div>- it lets you build packages without cd'ing to the workspace root</div>
<div>- it needs to be tested more before being recommended over `catkin_make`</div>
<div>- the documentation for all the additional features can be found here: <a href="http://catkin-tools.readthedocs.org/">http://catkin-tools.readthedocs.org/</a>
</div>
<div><br></div>
<div>Install it now (from the ROS debian repos):</div>
<div>
<span>sudo apt-get install python-catkin-tools</span><br>
</div>
<div>
<div><br></div>
<div>Or install it now (from PIP):</div>
</div>
<div>sudo pip install -U catkin_tools<br>
</div>
<div><br></div>
<div>Take a look at the cheat sheet:</div>
<div>
<a href="http://catkin-tools.readthedocs.org/en/latest/cheat_sheet.html">http://catkin-tools.readthedocs.org/en/latest/cheat_sheet.html</a><br>
</div>
<div><br></div>
<div>Give it a try and report issues or feature requests here:</div>
<div><div><a href="https://github.com/catkin/catkin_tools/issues">https://github.com/catkin/catkin_tools/issues</a></div></div>
<div><br></div>
<div>For some background and the relationship to the current top-level `catkin_make` command:</div>
<div>
<a href="http://catkin-tools.readthedocs.org/en/latest/mechanics.html#understanding-the-build-process">http://catkin-tools.readthedocs.org/en/latest/mechanics.html#understanding-the-build-process</a><br>
</div>
<div><br></div>
<div>
<span>Many thanks to Contributors:</span><br>
</div>
<div>William Woodall</div>
<div>Jonathan Bohren</div>
<div>Nikolaus Demmel<br>
</div>
<div>Dave Coleman<br>
</div>
<div>Felix Ruess<br>
</div>
<div>Dirk Thomas</div>
<div>Kartik Mohta<br>
</div>
<div>Thibault Kruse<br>
</div>
<div>Ian McMahon</div>
<div>Kei Okada<br>
</div>
<div><br></div>
<div>
<div>Those of us who've put time into this project over the last year hope that `catkin build` makes your lives less stressful and helps you build robotic systems faster.&nbsp;</div>
<div><br></div>
</div>
<div>best,</div>
<div>catkin_tools contributors</div>
</div></div>
Ugo Cupcic | 5 Mar 08:58 2015

ERF - ROS workshop

Hi all,

Just a reminder for those of you who are coming to the European Robotics Forum next week that we are organising a ROS community workshop on Friday 13th at 4.15pm (Room 2).

If you want to know more, or you have a definite lightning talk to give, then please get in touch. - see this link for the webpage with contact details!

Cheers,

Ugo

--
Ugo CupcicHead of Software+44 20 7700 2487ugo-JJwpZlUREJ7ZI5Z/Ik8r6w@public.gmane.orgwww.shadowrobot.com

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

RoNeX - Building Robots with ROS Made Easy 
<div>
<div dir="ltr">
<div><span>Hi all,</span></div>
<div><br></div>
<div>Just a reminder for those of you who are coming to the European Robotics Forum next week that we are organising a ROS community workshop on Friday 13th at 4.15pm (Room 2).</div>
<div><br></div>
<div>
<span>If you want to know more, or you have a definite lightning talk to give, t</span><span>hen please get in touch. - see&nbsp;<a href="http://www.shadowrobot.com/ros-community-workshop-at-erf-2015">this link</a>&nbsp;</span><span>for the w</span><span>ebpage with contact details!</span>
</div>
<div><span><br></span></div>
<div><span>Cheers,</span></div>
<div><span><br>Ugo</span></div>
<div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><span>Ugo CupcicHead of Software+44 20 7700 2487<a href="mailto:ugo@..." target="_blank">ugo@...</a><a href="http://www.shadowrobot.com" target="_blank">www.shadowrobot.com</a></span></div></div></div></div>
</div>

<br>Shadow Robot Company Ltd.<br>251 Liverpool Road, N1 1LX, UK<br>Registered Number 3308007 (England &amp; Wales)<div>
<br><div><span>RoNeX - Building Robots with ROS Made Easy&nbsp;</span></div>
<div>
<a href="http://www.shadowrobot.com/products/ronex/" target="_blank">http://www.shadowrobot.com/products/ronex/</a><br><br>
</div>
</div>
</div>
Markus Eich | 5 Mar 05:06 2015
Picon
Picon

Hand tracking using Kinect One (V2) under Linux

Hi all,

anyone aware of a project for sophisticated hand/finger/guesture tracking using a Kinect One (V2) sensor?

I found a nice solution (http://cvrlcode.ics.forth.gr/handtracking/) but this lib is hard-linked to some older libs, must have Cuda, and is not open source for adaptation.

Other solutions for Kinect 2 seem to be windows only. I would need a solution with ROS/Ubuntu and open source.

Anything out there that you guys are aware of?

--

Kind regards,

Dr. Markus Eich | Research Fellow
ARC Centre of Excellence for Robotic Vision | Science and Engineering Faculty | Queensland University of Technology
P: + 61 7 3138 2348 |E: markus.eich-OLQOJ2pKmJQQrrorzV6ljw@public.gmane.org |W: www.roboticvision.org
Gardens Point, S Block 1105 | 2 George Street, Brisbane, QLD 4000 | CRICOS No. 00213J


<div>
    Hi all,<br><br>
    anyone aware of a project for sophisticated hand/finger/guesture
    tracking using a Kinect One (V2) sensor?<br><br>
    I found a nice solution (<a class="moz-txt-link-freetext" href="http://cvrlcode.ics.forth.gr/handtracking/">http://cvrlcode.ics.forth.gr/handtracking/</a>)
    but this lib is hard-linked to some older libs, must have Cuda, and
    is not open source for adaptation.<br><br>
    Other solutions for Kinect 2 seem to be windows only. I would need a
    solution with ROS/Ubuntu and open source.<br><br>
    Anything out there that you guys are aware of?
    <div class="moz-signature">
<br>
      -- <br><br>
      Kind regards,<br><br>
      Dr. Markus Eich | Research Fellow<br>
      ARC Centre of Excellence for Robotic Vision | Science and
      Engineering Faculty | Queensland University of Technology<br>
      P: + 61 7 3138 2348 |E: <a class="moz-txt-link-abbreviated" href="mailto:markus.eich@...">markus.eich@...</a> |W:
      <a class="moz-txt-link-abbreviated" href="http://www.roboticvision.org">www.roboticvision.org</a><br>
      Gardens Point, S Block 1105 | 2 George Street, Brisbane, QLD 4000
      | CRICOS No. 00213J<br><br><br>
</div>
  </div>

[jobs] Autonomous Driving R&D Intern at Bosch in Palo Alto

The Autonomous Driving Team (http://robotics.boschresearch.com) of the Bosch Research and Technology
Center in Palo Alto is looking for highly motivated interns with a strong desire for solving complex and
interesting problems. We offer intern projects for a variety of topics, including ROS software
development, perception, sensor fusion, planning, physics/traffic simulation and computer vision. 

Interns will work closely with staff researchers on a directed research project related to the
candidate's background. Examples contain (but are not limited to):

- Perception: Topics in sensor calibration, on-line monitoring to detect out-of-calibration sensors,
turn signal detection, classification, etc. 
- Deep learning: Topics in computer vision (traffic light, vehicle turn signal, road surface detection)
and prediction (vehicle trajectories, driver intent, situation analysis)
- Localization: Improving vehicle localization in GPS-limited environments, e.g. using visual
localization and tight GPS/IMU coupling.
- Prediction: Improving behavioral prediction of traffic participants, e.g. through learning traffic
behavior patterns from data, or by incorporating turn signal information.  
- Planning: Motion & behavior planning, automated behavior testing via traffic scenario generation and
modeling in simulation.

Details and online application:
http://www.bosch.us/content/language1/html/12750.htm

Availability: all year

Jeff Johnson
Dirk Thomas | 4 Mar 15:14 2015

New release of the new Docker-based ROS build farm

Please see the announcement email on the ros-sig-buildsystem mailing list:
https://groups.google.com/forum/#!topic/ros-sig-buildfarm/rpooqNA5GaI

If you are interested in or already using this new infrastructure please make sure to subscribe to that mailing list since future announcement won't be posted to ros-users anymore.

Cheers,
- Dirk
<div><div dir="ltr">
<div>Please see the announcement email on the ros-sig-buildsystem mailing list:</div>
<a href="https://groups.google.com/forum/#!topic/ros-sig-buildfarm/rpooqNA5GaI">https://groups.google.com/forum/#!topic/ros-sig-buildfarm/rpooqNA5GaI</a><br><div><br></div>
<div>If you are interested in or already using this new infrastructure please make sure to subscribe to that mailing list since future announcement won't be posted to ros-users anymore.</div>
<div><br></div>
<div>Cheers,</div>
<div>- Dirk</div>
</div></div>
G.A. vd. Hoorn - 3ME | 4 Mar 09:44 2015
Picon
Picon

clarifying package installation 'best practices'?

All,

just wondering whether we should somehow clarify what the current 'best
practices' are for installing packages onto a ROS pc. I see a lot of
people that assume that building from source (after cloning from a
repository) is _the_ way to do things.

Apart from the fact that this is essentially a waste of time and effort,
it also often leads to problems (as they forget to check for and / or
install all dependencies first), which then results in numerous ROS
Answers questions. Having the sources locally also seems to invite some
users to start editing / hard coding parameters (such as IPs / serial
ports) into nodes, which is obviously unwanted.

Somehow I have a feeling that the prominent placing of the repository
URL in the Package Summary contributes to the confusion.

Would it perhaps be an idea to add a one-liner to the 'Package Summary'
on wiki pages of released packages that shows users how to install it
("Installation: sudo apt-get install ros-$release-pkg-name", although
that is distribution specific)? Or a link to a (new) wiki page that
explains how to install packages in general (with the from-source option
shown last)?

Gijs
William Woodall | 3 Mar 00:37 2015

New Versions of rviz

Hi guys,

We have new versions of rviz in both Indigo (1.11.7 up from 1.11.4) and Hydro (1.10.19 up from 1.10.18) in the shadow fixed repository, and I am looking for some help testing these new versions out.

You can see a summary of the changes here:


The shadow fixed repository, for those who do not know, is the staging repository which we use for testing before making new versions public. You can think of it as a place for release candidates. See http://wiki.ros.org/ShadowRepository for information about the process and how you can try out packages from it.

If you use rviz on Indigo or Hydro and have some spare cycles I would appreciate you testing out the new versions either from shadow fixed or by building it from source. Any issues you might find, please file them on the rviz issue tracker.

I'll keep the "release candidates" in the shadow fixed repository for about week unless we run into problems.

Thanks!

P.S. the link to the Indigo changes above may take some time to catch up, if you don't see 1.11.7, look here instead: https://github.com/ros-visualization/rviz/blob/11fcdadbbcc4c9d38a0bd4d580be6f0b49cbbc47/CHANGELOG.rst

--
<div><div dir="ltr">Hi guys,<div><br></div>
<div>We have new versions of rviz in both Indigo (1.11.7 up from 1.11.4) and Hydro (1.10.19 up from 1.10.18) in the shadow fixed repository, and I am looking for some help testing these new versions out.</div>
<div><br></div>
<div>You can see a summary of the changes here:</div>
<div><br></div>
<div>- Indigo:&nbsp;<a href="http://docs.ros.org/indigo/changelogs/rviz/changelog.html">http://docs.ros.org/indigo/changelogs/rviz/changelog.html</a>
</div>
<div>- Hydro:&nbsp;<a href="http://docs.ros.org/hydro/changelogs/rviz/changelog.html">http://docs.ros.org/hydro/changelogs/rviz/changelog.html</a>
</div>
<div><br></div>
<div>The shadow fixed repository, for those who do not know, is the staging repository which we use for testing before making new versions public. You can think of it as a place for release candidates. See&nbsp;<a href="http://wiki.ros.org/ShadowRepository">http://wiki.ros.org/ShadowRepository</a> for information about the process and how you can try out packages from it.</div>
<div><br></div>
<div>If you use rviz on Indigo or Hydro and have some spare cycles I would appreciate you testing out the new versions either from shadow fixed or by building it from source. Any issues you might find, please file them on the rviz issue tracker.</div>
<div><br></div>
<div>I'll keep the "release candidates" in the shadow fixed repository for about week unless we run into problems.</div>
<div><br></div>
<div>Thanks!</div>
<div><br></div>
<div>P.S. the link to the Indigo changes above may take some time to catch up, if you don't see 1.11.7, look here instead:&nbsp;<a href="https://github.com/ros-visualization/rviz/blob/11fcdadbbcc4c9d38a0bd4d580be6f0b49cbbc47/CHANGELOG.rst">https://github.com/ros-visualization/rviz/blob/11fcdadbbcc4c9d38a0bd4d580be6f0b49cbbc47/CHANGELOG.rst</a><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr">William Woodall<div>ROS Development Team</div>
<div><a href="mailto:william <at> osrfoundation.org" target="_blank">william@...</a></div>
<div><a href="http://wjwwood.io/" target="_blank">http://wjwwood.io/</a></div>
</div></div>
</div>
</div></div>
Daniel Stonier | 2 Mar 08:50 2015
Picon

Rosjava/Android Indigo Release


A quick heads up for the official rosjava/android release on indigo. This has been the result of some on and off work over the last couple of weeks - a big thank you to input from a few lads who were busy on the github rosjava issue trackers. Also to Damon for the android improvements since hydro.

Starting points:


Shiny new things (details in the Migration Guide):
  • Gradle version -> 2.2
  • More (and easier) methods of generating message artifacts.
  • Build rosjava debs on the build farm without special workarounds
  • Android Studio 1.x support
  • Android interactions/pairing now stable with tutorials.
  • Lots of other minor fixes and updates.
Enjoy!
Daniel.


<div><div dir="ltr">
<div class="gmail_signature"><div dir="ltr">
<div><div><br></div></div>
<div>A quick heads up for the official rosjava/android release on indigo. This has been the result of some on and off work over the last couple of weeks - a big thank you to input from a few lads who were busy on the github rosjava issue trackers. Also to Damon for the android improvements since hydro.<br>
</div>
<div><br></div>
<div>Starting points:</div>
<div><br></div>
<div>
<ul>
<li>
<a href="http://wiki.ros.org/rosjava">http://wiki.ros.org/rosjava</a><br>
</li>
<li><a href="http://wiki.ros.org/android">http://wiki.ros.org/android</a></li>
<li>
<a href="https://github.com/rosjava">https://github.com/rosjava</a>&nbsp;(indigo branches)<br>
</li>
</ul>
<div></div>
<div><br></div>
<div>Shiny new things (details in the&nbsp;<a href="http://wiki.ros.org/rosjava/Tutorials/indigo/Rosjava%20and%20Android%20Migration%20Guide">Migration Guide</a>):</div>
<ul>
<li>Gradle version -&gt; 2.2</li>
<li>More (and easier) methods of generating message artifacts.</li>
<li>Build rosjava debs on the build farm without special workarounds</li>
<li>Android Studio 1.x support</li>
<li>Android interactions/pairing now stable with tutorials.</li>
<li>Lots of other minor fixes and updates.</li>
</ul>
</div>
<div>Enjoy!</div>
<div>Daniel.</div>
<div><br></div>
<div><br></div>
</div></div>
</div></div>
Vincent Rabaud | 1 Mar 22:10 2015
Picon

REP 144 - ROS Package Naming

Hi all,

after not knowing how to properly name packages for NAO, I wrote a REP for how to name ROS packages:
https://github.com/ros-infrastructure/rep/blob/master/rep-0144.rst
The original discussion with awesome reviewers happened at:
https://github.com/ros-infrastructure/rep/pull/94

The draft is now in the process of becoming official (or rejected) so if you have any feedback, please continue the discussion here:
https://github.com/ros-infrastructure/rep/pull/96

Thx,
Vincent
<div><div dir="ltr">
<div>
<div>Hi all,<br><br>after not knowing how to properly name packages for NAO, I wrote a REP for how to name ROS packages:<br><a href="https://github.com/ros-infrastructure/rep/blob/master/rep-0144.rst">https://github.com/ros-infrastructure/rep/blob/master/rep-0144.rst</a><br>The original discussion with awesome reviewers happened at:<br><a href="https://github.com/ros-infrastructure/rep/pull/94">https://github.com/ros-infrastructure/rep/pull/94</a><br><br>The draft is now in the process of becoming official (or rejected) so if you have any feedback, please continue the discussion here:<br><a href="https://github.com/ros-infrastructure/rep/pull/96">https://github.com/ros-infrastructure/rep/pull/96</a><br><br>
</div>Thx,<br>
</div>Vincent<br>
</div></div>
Akhil Nagariya | 1 Mar 21:12 2015
Picon

Social navigation layer

Hi everyone,
  I have been using the navigation stack for quite some time and have developed a prediction algorithm for humans . I would like to integrate the prediction algorithm with the social navigation layer I don't know if this has been  done already and if not then how to go about it.
Regards,
Akhil Nagariya

<div><p dir="ltr">Hi everyone,<br>
&nbsp; I have been using the navigation stack for quite some time and have developed a prediction algorithm for humans . I would like to integrate the prediction algorithm with the social navigation layer I don't know if this has been&nbsp; done already and if not then how to go about it.<br>
 Regards,<br>
Akhil Nagariya</p></div>
Daniel Stonier | 1 Mar 07:03 2015
Picon

New 3rd party packages


This is just a heads up with regards to a few new third party packages on the ros apt-get server that others might find useful:


Google's optimization solver library. It is not a catkin 3rd party, but packaged by Vincent Rabaud and available via the usual ros apt-get server. We were doing everything by source for months before finding out Vincent had packaged it for us - thanks Vincent!


A really awesome c++ implementation of lie groups by Hauke Strasdat built on top of Eigen. Thanks Hauke!


Backports some useful features for qt's imshow from 3.0 to the ubuntu system release of 2.4.x. It lets you zoom, save, and run from parallel threads (great for use on top of ecto).


A new comms release from the author of zeromq (official web page). We often use this for lightweight communications on low level arm boards that can't support ros. Cross compile with catkin from source for the arm boards, or use the deb for the pc side.

Enjoy your robot'icking!
Daniel.

<div><div dir="ltr">
<div class="gmail_signature"><div dir="ltr">
<div><div><br></div></div>
<div>This is just a heads up with regards to a few new third party packages on the ros apt-get server that others might find useful:</div>
<div><br></div>
<div><a href="http://ceres-solver.org/">libceres-dev</a></div>
<div><br></div>
<div>Google's optimization solver library. It is not a catkin 3rd party, but packaged by Vincent Rabaud and available via the usual ros apt-get server. We were doing everything by source for months before finding out Vincent had packaged it for us - thanks Vincent!</div>
<div><br></div>
<div><a href="http://wiki.ros.org/sophus">ros-indigo-sophus</a></div>
<div><br></div>
<div>A really awesome c++ implementation of lie groups by Hauke Strasdat built on top of Eigen. Thanks Hauke!</div>
<div><br></div>
<div><a href="http://wiki.ros.org/cv_backports">ros-indigo-cv-backports</a></div>
<div><br></div>
<div>Backports some useful features for qt's imshow from 3.0 to the ubuntu system release of 2.4.x. It lets you zoom, save, and run from parallel threads (great for use on top of ecto).</div>
<div><br></div>
<div>
<a href="http://wiki.ros.org/nanomsg">ros-indigo-nanomsg</a>&nbsp;</div>
<div><br></div>
<div>A new comms release from the author of zeromq (<a href="http://nanomsg.org/">official web page</a>). We often use this for lightweight communications on low level arm boards that can't support ros. Cross compile with catkin from source for the arm boards, or use the deb for the pc side.</div>
<div><br></div>
<div>Enjoy your robot'icking!<br>
</div>
<div>Daniel.</div>
<div><br></div>
</div></div>
</div></div>

Gmane