ROS summary - Revision history

GiulioFontana at 10:28, 9 November 2016

2016-11-09T10:28:30Z

GiulioFontana at 10:26, 9 November 2016

2016-11-09T10:26:46Z

GiulioFontana at 10:22, 9 November 2016

2016-11-09T10:22:55Z

GiulioFontana: /* Gazebo wrapped into Groovy (a.k.a. Questo matrimonio non s'ha da fare) */

2016-11-09T09:38:55Z

‎Gazebo wrapped into Groovy (a.k.a. Questo matrimonio non s'ha da fare)

GiulioFontana: Restructured and simplified AIRWiki pages dealing with ROS (it was difficult to find stuff!)

2016-11-09T09:34:38Z

Restructured and simplified AIRWiki pages dealing with ROS (it was difficult to find stuff!)

GiulioFontana at 09:24, 9 November 2016

2016-11-09T09:24:53Z

GiulioFontana: Restructured and simplified AIRWiki pages dealing with ROS (it was difficult to find stuff!)

2016-11-09T09:24:26Z

Restructured and simplified AIRWiki pages dealing with ROS (it was difficult to find stuff!)

GiulioFontana at 09:20, 9 November 2016

2016-11-09T09:20:39Z

GiulioFontana at 09:09, 9 November 2016

2016-11-09T09:09:04Z

LucaCalabrese at 16:59, 30 May 2013

2013-05-30T16:59:06Z

@@ Line 2: / Line 2: @@
 The page you are reading provides additional information about installation and package management in ROS.
-General-purpose information about ROS and its basic elements is available in the [[ROS HOWTO]] page.
+Basic information about ROS and its elements is available in the [[ROS HOWTO]] page. Such page also includes links to other AIRWiki pages related to ROS.
-−
 Such page also includes links to other AIRWiki pages related to ROS.
 = ROS and IDE initial setup =

@@ Line 1: / Line 1: @@
-This page provides additional information about installation and package management in ROS.
+= ROS in AIRWiki =
 General-purpose information about ROS and its basic elements is available in the [[ROS HOWTO]] page.
 = ROS and IDE initial setup =

@@ Line 3: / Line 3: @@
 General-purpose information about ROS and its basic elements is available in the [[ROS HOWTO]] page.
-== ROS and IDE initial setup ==
+= ROS and IDE initial setup =
-=== Configure your environment ===
+== Configure your environment ==
 If you followed the [http://www.ros.org/wiki/ROS/Tutorials/InstallingandConfiguringROSEnvironment ROS tutorial] to configure your environment, the variable $ROS_PACKAGE_PATH should be set. This can be easily verified by check if the command <code> echo $ROS_PACKAGE_PATH </code> returns an output similar to:
@@ Line 17: / Line 17: @@
 : <code> source /opt/ros/<ROS DISTIBUTION>/setup.bash </code>
-=== Eclipse ===
+== Eclipse ==
 * '''To reuse your shell environment''' it is advisable to launch  [http://www.eclipse.org/ Eclipse] with the following command:
@@ Line 36: / Line 36: @@
 : Then import the project from the ''build/'' folder. A link named ''Source directory'' within the project is provided, and you can edit the source code from there.
-== Package management ==
+= Package management =
 ROS packages can be managed using your linux distribution package manager and/or with the built-in ROS package manager.
-=== Internal structure of a package ===
+== Internal structure of a package ==
 In ROS, each package has its own directory on disk: all the elements of the package are contained in such directory. The ROS package takes the name of the directory. Some of the package directories are installed by ROS, and reside somewhere on your hard disk (tip: to quickly reach a ROS package from the command line, and discover where it's located, simply use ''roscd name_of_the_package''). Other package directories are created by you, and you can put them wherever you like (usually somewhere in /home/your_username).
@@ Line 58: / Line 58: @@
 * MyPkg'''/manifest.xml''', which (by being present) specifies that MyPkg is a ROS package directory, and which defines some properties of the package; usually you won't need to modify [http://ros.org/wiki/Manifest manifest.xml] unless you need to add a '''dependency''' to your package.
-=== ROS package environment ===
+== ROS package environment ==
 * To initialize the ROS package management environment:
 ::<code> (as root) rosdep init </code>
@@ Line 65: / Line 65: @@
 ::<code> rosdep update </code>
-=== ROS package installation ===
+== ROS package installation ==
 * To find a package:
 ::browse to [http://www.ros.org/browse/ this page] to browse a list of available packages.
@@ Line 78: / Line 78: @@
 ::<code> (as root) rosdep install package_name </code>
-=== New package creation ===
+== New package creation ==
 This command creates a new package in the current directory:
@@ Line 85: / Line 85: @@
 Please note that package dependencies can be explicitly specified when the package is created, but they can also be manually added afterwards to the ''manifest.xml'' file or with the ''rospack command''. Take a look at [http://www.ros.org/wiki/ROS/Tutorials/CreatingPackage#ROS.2BAC8-Tutorials.2BAC8-rosbuild.2BAC8-CreatingPackage.First-order_package_dependencies this page] if you need further information.
-===== CMakeLists.txt =====
+==== CMakeLists.txt ====
 Official pages:<br />
@@ Line 152: / Line 152: @@
 </pre></code>
-===== Makefile =====
+==== Makefile ====
 Be sure that the following line is present in the Makefile in order for the command <code> make eclipse-project </code> to work:
 <code> include $(shell rospack find mk)/cmake.mk </code>
-===== Manifest.xml =====
+==== Manifest.xml ====
 <code><pre><nowiki>
 <package>
@@ Line 175: / Line 175: @@
 </nowiki></pre></code>
-== Gazebo wrapped into Groovy (a.k.a. ''Questo matrimonio non s'ha da fare'') ==
+= Gazebo wrapped into Groovy (a.k.a. ''Questo matrimonio non s'ha da fare'') =
 Don't waste your time trying to execute the tutorials available on the ROS website!!
 They are outdated and will almost surely not work in every ROS distribution later than electric. ([http://answers.gazebosim.org/question/1067/ros-groovy-gazebo-cannot-spawn-objects/ Source]). You can (almost) safely follow [http://gazebosim.org/wiki/Tutorials Gazebo's tutorials the gazebo standalone's tutorials], but be sure to select the right tutorials for the version of Gazebo included in your distribution of ROS (as of 15 March 2013, Groovy --> Gazebo 1.3) and to read the following instructions.
-==== How to correctly setup a Gazebo package with a plugin inside Groovy ====
+=== How to correctly setup a Gazebo package with a plugin inside Groovy ===
 Note: the following supposes a working and correctly configured ROS environment (follow the [http://www.ros.org/wiki/ROS/Tutorials/InstallingandConfiguringROSEnvironment ROS official installation guide] otherwise)
@@ Line 192: / Line 192: @@
 #'''Download and extract''' [[Media:zzz_launchers_autogenerator.zip|the following script]] in the package folder (in the main one, not inside the build folder). Read the included instructions (at the beginning of the script file) and modify the required variables. Then make it executable and run it to create the .launch file: <br /><code> chmod ugoa+x zzz_launchers_generator.sh;    ./zzz_launchers_generator.sh</code><br />
-==== Interesting links for the future (to be tested) ====
+=== Interesting links for the future (to be tested) ===
 *[http://answers.gazebosim.org/question/60/tutorial-for-simple-urdf-models/ This discussion] cites some model that seem to be working with the ROS-wrapped-Gazebo.
-==== Common error messages ====
+=== Common error messages ===
 * Trying to execute the wrapped-into-Groovy Gazebo, you could encounter the following error:
 ::<code> Error [Rendering.cc:37] Failed to load the Rendering engine subsystem unable to find OpenGL rendering system. OGRE is probably installed incorrectly. Double check the OGRE cmake output, and make sure OpenGL is enabled </code>

@@ Line 175: / Line 175: @@
 </nowiki></pre></code>
-=== Gazebo wrapped into Groovy (a.k.a. ''Questo matrimonio non s'ha da fare'') ===
+== Gazebo wrapped into Groovy (a.k.a. ''Questo matrimonio non s'ha da fare'') ==
 Don't waste your time trying to execute the tutorials available on the ROS website!!

@@ Line 1: / Line 1: @@
-This page is dedicated to experienced ROS users. Its purpose is to provide additional information about  a brief summary of the most useful commands and configurations for ROS and for the external programs, with few additional explanations.
+This page provides additional information about installation and package management in ROS.
-This page should not be used to provide general-purpose information about ROS or its elements, which is the task of [[ROS HOWTO]] and its secondary AIRWiki pages (e.g., [[ROS packages]], [[ROS commands]] or [[ROS components]]).
+General-purpose information about ROS and its basic elements is available in the [[ROS HOWTO]] page.
-−
-Please note that some of the most commonly used commands are already described in a condensed form in the [http://www.ros.org/wiki/Documentation?action=AttachFile&do=get&target=ROScheatsheet.pdf ROS Official Cheat Sheet].
 == ROS and IDE initial setup ==

← Older revision		Revision as of 09:20, 9 November 2016
Line 1:		Line 1:
−	This page is dedicated to ~~'''~~experienced ROS users~~'''~~. Its purpose is to provide a brief summary of the most useful commands and configurations for ROS and for the external programs, with few additional explanations.	+	This page is dedicated to experienced ROS users. Its purpose is to provide additional information about a brief summary of the most useful commands and configurations for ROS and for the external programs, with few additional explanations.

	This page should not be used to provide general-purpose information about ROS or its elements, which is the task of [[ROS HOWTO]] and its secondary AIRWiki pages (e.g., [[ROS packages]], [[ROS commands]] or [[ROS components]]).		This page should not be used to provide general-purpose information about ROS or its elements, which is the task of [[ROS HOWTO]] and its secondary AIRWiki pages (e.g., [[ROS packages]], [[ROS commands]] or [[ROS components]]).

@@ Line 24: / Line 24: @@
 : <code> bash -i -c /usr/lib/eclipse/eclipse </code>
-*  '''To let ROS create the Eclipse project files''' you can use the following command:
+*  '''To let ROS create the Eclipse project files''' you can use the following command (only for Fuerte or older releases):
 ::<code> make eclipse-project </code>
@@ Line 31: / Line 31: @@
 *  '''To add an existing project to Eclipse''' select File --> Import --> General --> Existing Projects into Workspace, select the project's root directory and be sure that the "Copy projects into workspace" option is NOT selected.
 == Package management ==