Difference between revisions of "Tutorials"

From Asibot & HOAP3 & TEO Wiki
Jump to navigation Jump to search
 
(14 intermediate revisions by 3 users not shown)
Line 3: Line 3:
 
|-  
 
|-  
 
! More Tutorials (continuation from Tutorial Section on [[Main Page]])
 
! More Tutorials (continuation from Tutorial Section on [[Main Page]])
 +
|-
 +
| Guidelines on how to write a document ([http://asrob.uc3m.es/index.php/Redactar Spanish]) - Templates can be found [[Asibot_-_Documentation|HERE]]
 
|-
 
|-
 
| Library Installation Guides ([[Modules_-_Library_Versioning|English]])
 
| Library Installation Guides ([[Modules_-_Library_Versioning|English]])
Line 8: Line 10:
 
| MediaWiki ([http://en.wikipedia.org/wiki/How_to_edit English])
 
| MediaWiki ([http://en.wikipedia.org/wiki/How_to_edit English])
 
|-
 
|-
| Subversion ([http://asrob.uc3m.es/w/index.php/Tutorial_SVN Spanish])
+
| Subversion ([http://asrob.uc3m.es/index.php/Tutorial_SVN Spanish])
 
|-
 
|-
 
| Blender for Engineers ([http://rab3d.com/tutorial.html English])
 
| Blender for Engineers ([http://rab3d.com/tutorial.html English])
Line 15: Line 17:
 
|-
 
|-
 
| How to use Blender for exporting models for OpenRAVE ([[Blender and Openrave |English]])
 
| How to use Blender for exporting models for OpenRAVE ([[Blender and Openrave |English]])
|-
 
| Basic guidelines on writing a document ([http://asrob.uc3m.es/w/index.php/Redactar Spanish])
 
 
|-
 
|-
 
| Google Style Guide for C++ ([http://google-styleguide.googlecode.com/svn/trunk/cppguide.xml English])
 
| Google Style Guide for C++ ([http://google-styleguide.googlecode.com/svn/trunk/cppguide.xml English])
Line 31: Line 31:
 
* [[Help on Doxygen]]
 
* [[Help on Doxygen]]
 
* [[Help on Eclipse]]
 
* [[Help on Eclipse]]
 +
* [[Help on Latex]]
 +
* [[Help on Linux Kernel]]
 +
* [[Help on Gcc]]
 
* [[Help on Gdb]]
 
* [[Help on Gdb]]
 +
* [[Help on Matlab]]
 +
* [[Help on Ssh]]
 
* [[Help on Trac]]
 
* [[Help on Trac]]
* [[Help on Vim]]
+
* [[Help on Vim|Help on Vim/Gvim]]
 +
* [[Help on Wine]]
 
* <u>Mobile Robot Programming Toolkit</u> (http://www.mrpt.org): Used by the University of Málaga. Can be found in the Ubuntu repositories.
 
* <u>Mobile Robot Programming Toolkit</u> (http://www.mrpt.org): Used by the University of Málaga. Can be found in the Ubuntu repositories.
 
* http://www.robotcub.org/index.php/robotcub/content/download/574/2075/file/D8.2.pdf
 
* http://www.robotcub.org/index.php/robotcub/content/download/574/2075/file/D8.2.pdf
Line 42: Line 48:
 
-->
 
-->
  
*  <u> Stream Visualizer</u>:[http://code.google.com/p/streamvis/]] can work with data received from files (including pipes), standard input, YARP ports and ROS topics
+
*  <u> Stream Visualizer</u>:[http://code.google.com/p/streamvis/]] can work with data received from files (including pipes), standard input, YARP ports and ROS topics. Also check icub/contrib/portscope.
 +
 
 +
* A simple  Eye-in-Hand Visual Servoing [http://groups.csail.mit.edu/drl/wiki/index.php?title=Eye-in-Hand_Visual_Servoing_Curriculum link] A camera is mounted on the arm itself, near the gripper, in an eye-in-hand configuration. This a practical example very easy to understand and with source code available (for explanation proposes). Ideal for starting a new PFC work.

Latest revision as of 17:48, 20 April 2012

More Tutorials (continuation from Tutorial Section on Main Page)
Guidelines on how to write a document (Spanish) - Templates can be found HERE
Library Installation Guides (English)
MediaWiki (English)
Subversion (Spanish)
Blender for Engineers (English)
How to connect YARP and MATLAB (English)
How to use Blender for exporting models for OpenRAVE (English)
Google Style Guide for C++ (English)

Mediawiki-Related Tutorials

Other Links of Interest

  • Stream Visualizer:[1]] can work with data received from files (including pipes), standard input, YARP ports and ROS topics. Also check icub/contrib/portscope.
  • A simple Eye-in-Hand Visual Servoing link A camera is mounted on the arm itself, near the gripper, in an eye-in-hand configuration. This a practical example very easy to understand and with source code available (for explanation proposes). Ideal for starting a new PFC work.