<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Arial, sans-serif; "><div>Hello,</div><div><br></div><div>Paul, you are totally right and I personally have purchased the two volumes of ROS by examples and fully read volume 1 and volume 2 is in progress. I found them excellent references and I am using them in one ongoing project. </div><div><br></div><div>Just let me explain that the idea of the handbook is to go beyond basics. In ROS community, there are several contributed packages and several industrial use cases that probably most of users do not know about. They can be scattered in research papers where the focus is on validation but not on ROS package development itself. The prospective handbook intends to give more value and more focus on such contributed packages, in addition to traditional concepts of ROS. </div><div><br></div><div>Take the example of UAVs. There are several UAVs that are supported by ROS but very small number have a sufficiently good documentation. One other example is for instance adding a new global or local path planner to ROS. You can find general docs about adding plugin but nothing specific to adding plugin to global and local planners. It happens I did a tutorial on adding a global path planner to ROS nav stack and add it to ROS wiki.</div><div>There are so many packages that can see the light through a handbook, because at least it will be worth a publication for the developers. </div><div><br></div><div>This is to give a clearer idea on the objective of a handbook and what contributions it can provide to ROS users. </div><div>It is not intended to be a competitor of existing books but to provide a complementary reference. </div><div><br></div><div>Just to keep you updated, I shall be sending an official call for chapters in a couple of weeks with some guidelines, and any valuable contribution will be welcome. </div><div><br></div><div>Thanks for all who send their feedback and proposals.</div><div>Anis</div><div><br></div><span id="OLK_SRC_BODY_SECTION"><div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt"><span style="font-weight:bold">From: </span> Paul Bouchier <<a href="mailto:bouchier@classicnet.net">bouchier@classicnet.net</a>><br><span style="font-weight:bold">Reply-To: </span> User discussions <<a href="mailto:ros-users@lists.ros.org">ros-users@lists.ros.org</a>><br><span style="font-weight:bold">Date: </span> Sunday, October 26, 2014 9:30 PM<br><span style="font-weight:bold">To: </span> <<a href="mailto:ros-users@lists.ros.org">ros-users@lists.ros.org</a>><br><span style="font-weight:bold">Subject: </span> Re: [ros-users] Interest and proposal intention survey for a ROS Handbook<br></div><div><br></div><div>
<meta content="text/html; charset=windows-1252" http-equiv="Content-Type">
<div bgcolor="#FFFFFF" text="#000000">
All,<br>
<br>
I want to give a shout out for the ROS By Example books by Patrick
Goebel. They are listed on the books wiki page Anis pointed to. They
explain many of the areas Mike cites as needing comprehensive
explanation, and also contain a lot of examples that help you follow
along, and are re-released with updates for each new version of ROS.
There's an active google group for asking questions about material
in the book. The two books are a level above the tutorials because
they tie many packages together into solutions. At $15 - $22 for the
e-book, or $25 - $38 for paperback, they are excellent value. If you
work with ROS and aren't one of the illuminati, you really should
have them on your disk or bookshelf. <br>
<br>
New books should take these books' contributions into account (IMHO)
and offer value in new areas - there's still a lot of ground that
should be covered.<br>
<br>
This is a public-service announcement for those who haven't looked
at the books that are already out there; I have no connection to the
author.<br>
<br>
Regards<br>
<br>
Paul Bouchier<br>
<br>
<div class="moz-cite-prefix">On 10/22/2014 12:29 PM, Mike Purvis
wrote:<br>
</div>
<blockquote cite="mid:CACsJT9OXrAoyNj-eGXrJwTvUQLXt8xc_rsjjKL9m-4MVipQdiQ@mail.gmail.com" type="cite">
<div dir="ltr">Hi Anis,
<div><br>
</div>
<div>I'm not sure how to express this through your form, but
something that's badly needed from Clearpath's perspective is
a modern take on what the parts are which make up a typical
ROS robot. This is beyond the "basics" of building a
workspace, creating publishers and subscribers, launching
things, etc, but it's not as high-level as specific packages
like navigation, moveit, etc.</div>
<div><br>
</div>
<div>Obviously there's a lot of variability out there, but if
someone were to build a robot today, from scratch, to use ROS,
they'd ask some fundamental questions like:</div>
<div>
<ul>
<li>How do I build a URDF for my robot? How do I name the
links and joints? Should I have a base_footprint? Should I
use xacro?</li>
<li>What's the deal with robot_state_publisher, and what's
the relationship between the joint_states topic and my TF
tree?</li>
<li>Where do the odom and map frames come from? Should I
always expect them to be there, or do they come and go
depending what's running? How do I handle REP-105 if my
robot has a GPS receiver? What about if it has an
integrated GPS-INS?</li>
<li>Now that I have a URDF, how do I bring my robot up in
Gazebo? How do I give my simulated robot an IMU, LIDAR,
and camera?</li>
<li>How does my robot know where it is? What is
localization, and what topics are consumed and produced by
it?</li>
<li>For a "typical" encoders + imu + LIDAR configuration,
what topics should I expect to see, where, and on what
frequencies?</li>
<li>How do I set up my robot to use ros_control and the
existing suite of available controllers? Should I have a
real-time control loop? If so, how do I set that up in
Ubuntu?</li>
<li>How should I set up ROS to launch automatically when I
turn on my robot? How do I manage logs, node output, and
bag files?</li>
</ul>
<div>There's been discussion in the past about specifying some
standards for this kind of thing, possibly in a REP, but a
great first step would be a book or other resource which
presented this material in an approachable, linear kind of
way.</div>
</div>
<div><br>
</div>
<div>Mike</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On 22 October 2014 05:31, Anis Koubaa
(COINS) <span dir="ltr"><<a moz-do-not-send="true" href="mailto:akoubaa@coins-lab.org" target="_blank">akoubaa@coins-lab.org</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word;color:rgb(0,0,0)">
<div style="font-size:14px;font-family:Arial,sans-serif">Hello
ROS users community,</div>
<div style="font-size:14px;font-family:Arial,sans-serif"><br>
</div>
<div style="font-size:14px;font-family:Arial,sans-serif">I
am coordinating with Springer publisher to edit a
handbook on Robot Operating System. </div>
<div style="font-size:14px;font-family:Arial,sans-serif">There
are only a few books on ROS <a moz-do-not-send="true" href="http://wiki.ros.org/Books" target="_blank">http://wiki.ros.org/Books</a> which
mainly represent a brief introduction to ROS and a few
basic applications. This does not translate the huge
amount of work being done in the community and I feel
the need to have a complete reference on the topic. </div>
<div style="font-size:14px;font-family:Arial,sans-serif"><br>
</div>
<div style="font-size:14px;font-family:Arial,sans-serif">The
prospective handbook will cover ROS from foundations and
basics to advanced research works from both academia and
industry. Tutorials and research papers will both be
sought. The book should cover several robotics areas
including but not limited to robot navigation, UAVs, arm
manipulation, multi-robot communication protocols, Web
and mobile interfaces using ROS, integration of new
robotic platform to ROS, computer vision applications,
development of service robots using ROS, development of
new libraries and packages for ROS, etc. Every book
chapter should be accompanied with a working code to be
put later in a common repository for the readers.</div>
<div style="font-size:14px;font-family:Arial,sans-serif"><br>
</div>
<div style="font-size:14px;font-family:Arial,sans-serif">To
express your interest to the handbook and your intention
of a chapter proposal, I would like to invite you fill
in the <a moz-do-not-send="true" href="https://docs.google.com/forms/d/1JD78gka1rtotjGhBre-UJcm7QogQWUeURjvx4X028vw/viewform" target="_blank">following form</a>. The proposed
chapters are just considered as an initial expression
of interest and will be included in the handbook
proposal. It does not mean any kind of commitment for
the author at this stage. An official call for chapters
with instructions and deadline will be announced soon. </div>
<div style="font-size:14px;font-family:Arial,sans-serif"><br>
</div>
<div style="font-size:14px;font-family:Arial,sans-serif">Thank
you and look forward to receive your feedback</div>
<div style="font-size:14px;font-family:Arial,sans-serif">Anis</div>
<div style="font-size:14px;font-family:Arial,sans-serif"><br>
</div>
<div>
<div style="font-size:14px"><font color="#000000"><font face="Courier"><b>-------------------------------------------------------------</b></font></font></div>
<div><font color="#000000" face="Courier"><b style="font-size:18px">Anis Koubaa</b></font></div>
<div style="font-size:14px"><font face="Courier"><font color="#000000">Associate Professor, </font>Prince
Sultan University, Saudi Arabia</font></div>
<div style="font-size:14px"><font face="Courier">Research
Associate, CISTER Research Unit, Portugal </font></div>
<div style="font-size:14px"><span style="font-family:Courier"><a moz-do-not-send="true" href="http://w" target="_blank">http://w</a></span><span style="font-family:Courier"><a moz-do-not-send="true" href="http://ww.dei.isep.ipp.pt/%7Eakoubaa/" target="_blank">ww.dei.isep.ipp.pt/~akoubaa/</a></span></div>
<div style="font-size:14px"><span style="font-family:Courier"><a moz-do-not-send="true" href="http://www.iroboapp.org" target="_blank">http://www.iroboapp.org</a></span></div>
<div style="font-size:14px"><font face="Courier">-------------------------------------------------------------</font></div>
</div>
<div style="font-size:14px;font-family:Arial,sans-serif"><br>
</div>
<div style="font-size:14px;font-family:Arial,sans-serif"><br>
</div>
<div style="font-size:14px;font-family:Arial,sans-serif"><br>
</div>
<div style="font-size:14px;font-family:Arial,sans-serif"><br>
</div>
<div style="font-size:14px;font-family:Arial,sans-serif"><br>
</div>
</div>
<br>
_______________________________________________<br>
ros-users mailing list<br>
<a moz-do-not-send="true" href="mailto:ros-users@lists.ros.org">ros-users@lists.ros.org</a><br>
<a moz-do-not-send="true" href="http://lists.ros.org/mailman/listinfo/ros-users" target="_blank">http://lists.ros.org/mailman/listinfo/ros-users</a><br>
<br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
ros-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:ros-users@lists.ros.org">ros-users@lists.ros.org</a><a class="moz-txt-link-freetext" href="http://lists.ros.org/mailman/listinfo/ros-users">http://lists.ros.org/mailman/listinfo/ros-users</a></pre>
</blockquote>
<br>
</div></div>
_______________________________________________
ros-users mailing list
<a href="mailto:ros-users@lists.ros.org">ros-users@lists.ros.org</a>
<a href="http://lists.ros.org/mailman/listinfo/ros-users">http://lists.ros.org/mailman/listinfo/ros-users</a>
</span></body></html>