[Personalrobots-commit] SF.net SVN: personalrobots:[22606] pkg/trunk/stacks

[<kur...@us...>]

Revision: 22606
          http://personalrobots.svn.sourceforge.net/personalrobots/?rev=22606&view=rev
Author:   kurtkonolige
Date:     2009-08-21 22:46:20 +0000 (Fri, 21 Aug 2009)

Log Message:
-----------
moved image_view to new imaging_pipeline stack

Added Paths:
-----------
    pkg/trunk/stacks/imaging_pipeline/
    pkg/trunk/stacks/imaging_pipeline/image_geometry/
    pkg/trunk/stacks/imaging_pipeline/image_geometry/ROS_BUILD_BLACKLIST
    pkg/trunk/stacks/imaging_pipeline/image_geometry/mainpage.dox
    pkg/trunk/stacks/imaging_pipeline/image_proc/
    pkg/trunk/stacks/imaging_pipeline/image_proc/ROS_BUILD_BLACKLIST
    pkg/trunk/stacks/imaging_pipeline/image_proc/mainpage.dox
    pkg/trunk/stacks/imaging_pipeline/image_view/
    pkg/trunk/stacks/imaging_pipeline/stack.xml
    pkg/trunk/stacks/imaging_pipeline/stereo_image_proc/
    pkg/trunk/stacks/imaging_pipeline/stereo_image_proc/ROS_BUILD_BLACKLIST
    pkg/trunk/stacks/imaging_pipeline/stereo_image_proc/mainpage.dox

Removed Paths:
-------------
    pkg/trunk/stacks/opencv/image_view/

Added: pkg/trunk/stacks/imaging_pipeline/image_geometry/ROS_BUILD_BLACKLIST
===================================================================
--- pkg/trunk/stacks/imaging_pipeline/image_geometry/ROS_BUILD_BLACKLIST	                        (rev 0)
+++ pkg/trunk/stacks/imaging_pipeline/image_geometry/ROS_BUILD_BLACKLIST	2009-08-21 22:46:20 UTC (rev 22606)
@@ -0,0 +1 @@
+Transfering from stereo packages

Added: pkg/trunk/stacks/imaging_pipeline/image_geometry/mainpage.dox
===================================================================
--- pkg/trunk/stacks/imaging_pipeline/image_geometry/mainpage.dox	                        (rev 0)
+++ pkg/trunk/stacks/imaging_pipeline/image_geometry/mainpage.dox	2009-08-21 22:46:20 UTC (rev 22606)
@@ -0,0 +1,119 @@
+/**
+\mainpage
+\htmlinclude manifest.html
+
+\b test_stereo_msgs is ... 
+
+<!-- 
+In addition to providing an overview of your package,
+this is the section where the specification and design/architecture 
+should be detailed. While the original specification may be done on the
+wiki, it should be transferred here once your package starts to take shape.
+You can then link to this documentation page from the Wiki. 
+-->
+
+
+\section codeapi Code API
+
+<!--
+Provide links to specific auto-generated API documentation within your
+package that is of particular interest to a reader. Doxygen will
+document pretty much every part of your code, so do your best here to
+point the reader to the actual API.
+
+If your codebase is fairly large or has different sets of APIs, you
+should use the doxygen 'group' tag to keep these APIs together. For
+example, the roscpp documentation has 'libros' group.
+-->
+
+\section rosapi ROS API
+
+<!--
+Names are very important in ROS because they can be remapped on the
+command-line, so it is VERY IMPORTANT THAT YOU LIST NAMES AS THEY
+APPEAR IN THE CODE. You should list names of every topic, service and
+parameter used in your code. There is a template below that you can
+use to document each node separately.
+
+List of nodes:
+- \b node_name1
+- \b node_name2
+-->
+
+<!-- START: copy from here to 'END' for each node 
+
+<hr>
+
+\subsection node_name node_name
+
+node_name does (provide a basic description of your node)
+
+\subsubsection Usage
+\verbatim
+$ node_type1 [standard ROS args]
+\endverbatim
+
+\par Example
+
+\verbatim
+$ node_type1
+\endverbatim
+
+
+\subsubsection topics ROS topics
+
+Subscribes to:
+- \b "in": [std_msgs/FooType] description of in
+
+Publishes to:
+- \b "out": [std_msgs/FooType] description of out
+
+
+\subsubsection parameters ROS parameters
+
+Reads the following parameters from the parameter server
+
+- \b "~param_name" : \b [type] description of param_name
+- \b "~my_param" : \b [string] description of my_param
+
+Sets the following parameters on the parameter server
+
+- \b "~param_name" : \b [type] description of param_name
+
+
+\subsubsection services ROS services
+- \b "foo_service": [std_srvs/FooType] description of foo_service
+
+
+END: copy for each node -->
+
+
+<!-- START: Uncomment if you have any command-line tools
+
+\section commandline Command-line tools
+
+This section is a catch-all for any additional tools that your package
+provides or uses that may be of use to the reader. For example:
+
+- tools/scripts (e.g. rospack, roscd)
+- roslaunch .launch files
+- xmlparam files
+
+\subsection script_name script_name
+
+Description of what this script/file does.
+
+\subsubsection Usage
+\verbatim
+$ ./script_name [args]
+\endverbatim
+
+\par Example
+
+\verbatim
+$ ./script_name foo bar
+\endverbatim
+
+END: Command-Line Tools Section -->
+
+*/
\ No newline at end of file

Added: pkg/trunk/stacks/imaging_pipeline/image_proc/ROS_BUILD_BLACKLIST
===================================================================
--- pkg/trunk/stacks/imaging_pipeline/image_proc/ROS_BUILD_BLACKLIST	                        (rev 0)
+++ pkg/trunk/stacks/imaging_pipeline/image_proc/ROS_BUILD_BLACKLIST	2009-08-21 22:46:20 UTC (rev 22606)
@@ -0,0 +1 @@
+Transfering from stereo packages

Added: pkg/trunk/stacks/imaging_pipeline/image_proc/mainpage.dox
===================================================================
--- pkg/trunk/stacks/imaging_pipeline/image_proc/mainpage.dox	                        (rev 0)
+++ pkg/trunk/stacks/imaging_pipeline/image_proc/mainpage.dox	2009-08-21 22:46:20 UTC (rev 22606)
@@ -0,0 +1,119 @@
+/**
+\mainpage
+\htmlinclude manifest.html
+
+\b test_stereo_msgs is ... 
+
+<!-- 
+In addition to providing an overview of your package,
+this is the section where the specification and design/architecture 
+should be detailed. While the original specification may be done on the
+wiki, it should be transferred here once your package starts to take shape.
+You can then link to this documentation page from the Wiki. 
+-->
+
+
+\section codeapi Code API
+
+<!--
+Provide links to specific auto-generated API documentation within your
+package that is of particular interest to a reader. Doxygen will
+document pretty much every part of your code, so do your best here to
+point the reader to the actual API.
+
+If your codebase is fairly large or has different sets of APIs, you
+should use the doxygen 'group' tag to keep these APIs together. For
+example, the roscpp documentation has 'libros' group.
+-->
+
+\section rosapi ROS API
+
+<!--
+Names are very important in ROS because they can be remapped on the
+command-line, so it is VERY IMPORTANT THAT YOU LIST NAMES AS THEY
+APPEAR IN THE CODE. You should list names of every topic, service and
+parameter used in your code. There is a template below that you can
+use to document each node separately.
+
+List of nodes:
+- \b node_name1
+- \b node_name2
+-->
+
+<!-- START: copy from here to 'END' for each node 
+
+<hr>
+
+\subsection node_name node_name
+
+node_name does (provide a basic description of your node)
+
+\subsubsection Usage
+\verbatim
+$ node_type1 [standard ROS args]
+\endverbatim
+
+\par Example
+
+\verbatim
+$ node_type1
+\endverbatim
+
+
+\subsubsection topics ROS topics
+
+Subscribes to:
+- \b "in": [std_msgs/FooType] description of in
+
+Publishes to:
+- \b "out": [std_msgs/FooType] description of out
+
+
+\subsubsection parameters ROS parameters
+
+Reads the following parameters from the parameter server
+
+- \b "~param_name" : \b [type] description of param_name
+- \b "~my_param" : \b [string] description of my_param
+
+Sets the following parameters on the parameter server
+
+- \b "~param_name" : \b [type] description of param_name
+
+
+\subsubsection services ROS services
+- \b "foo_service": [std_srvs/FooType] description of foo_service
+
+
+END: copy for each node -->
+
+
+<!-- START: Uncomment if you have any command-line tools
+
+\section commandline Command-line tools
+
+This section is a catch-all for any additional tools that your package
+provides or uses that may be of use to the reader. For example:
+
+- tools/scripts (e.g. rospack, roscd)
+- roslaunch .launch files
+- xmlparam files
+
+\subsection script_name script_name
+
+Description of what this script/file does.
+
+\subsubsection Usage
+\verbatim
+$ ./script_name [args]
+\endverbatim
+
+\par Example
+
+\verbatim
+$ ./script_name foo bar
+\endverbatim
+
+END: Command-Line Tools Section -->
+
+*/
\ No newline at end of file

Added: pkg/trunk/stacks/imaging_pipeline/stack.xml
===================================================================
--- pkg/trunk/stacks/imaging_pipeline/stack.xml	                        (rev 0)
+++ pkg/trunk/stacks/imaging_pipeline/stack.xml	2009-08-21 22:46:20 UTC (rev 22606)
@@ -0,0 +1,15 @@
+<stack name="imaging_pipeline" version="0.1.0">
+  <description brief="pipeline for processing monocular and stereo images">
+    pipeline for processing monocular and stereo images
+  </description>
+  <author>Kurt Konolige</author>
+  <license>BSD</license>  
+  <review status="unreviewed" notes=""/>
+  <url>http://pr.willowgarage.com/wiki/imaging_pipeline</url>
+  <depend stack="opencv"/> <!-- opencvpython, opencv_latest, opencv_latest --> 
+  <depend stack="diagnostics"/> <!-- diagnostic_updater --> 
+  <depend stack="ros"/> <!-- roscpp, rostest, rosrecord, roscpp --> 
+  <depend stack="common_msgs"/> <!-- sensor_msgs --> 
+  <depend stack="camera_drivers"/> <!-- libdc1394v2 --> 
+
+</stack>

Added: pkg/trunk/stacks/imaging_pipeline/stereo_image_proc/ROS_BUILD_BLACKLIST
===================================================================
--- pkg/trunk/stacks/imaging_pipeline/stereo_image_proc/ROS_BUILD_BLACKLIST	                        (rev 0)
+++ pkg/trunk/stacks/imaging_pipeline/stereo_image_proc/ROS_BUILD_BLACKLIST	2009-08-21 22:46:20 UTC (rev 22606)
@@ -0,0 +1 @@
+Transfering from stereo packages

Added: pkg/trunk/stacks/imaging_pipeline/stereo_image_proc/mainpage.dox
===================================================================
--- pkg/trunk/stacks/imaging_pipeline/stereo_image_proc/mainpage.dox	                        (rev 0)
+++ pkg/trunk/stacks/imaging_pipeline/stereo_image_proc/mainpage.dox	2009-08-21 22:46:20 UTC (rev 22606)
@@ -0,0 +1,119 @@
+/**
+\mainpage
+\htmlinclude manifest.html
+
+\b test_stereo_msgs is ... 
+
+<!-- 
+In addition to providing an overview of your package,
+this is the section where the specification and design/architecture 
+should be detailed. While the original specification may be done on the
+wiki, it should be transferred here once your package starts to take shape.
+You can then link to this documentation page from the Wiki. 
+-->
+
+
+\section codeapi Code API
+
+<!--
+Provide links to specific auto-generated API documentation within your
+package that is of particular interest to a reader. Doxygen will
+document pretty much every part of your code, so do your best here to
+point the reader to the actual API.
+
+If your codebase is fairly large or has different sets of APIs, you
+should use the doxygen 'group' tag to keep these APIs together. For
+example, the roscpp documentation has 'libros' group.
+-->
+
+\section rosapi ROS API
+
+<!--
+Names are very important in ROS because they can be remapped on the
+command-line, so it is VERY IMPORTANT THAT YOU LIST NAMES AS THEY
+APPEAR IN THE CODE. You should list names of every topic, service and
+parameter used in your code. There is a template below that you can
+use to document each node separately.
+
+List of nodes:
+- \b node_name1
+- \b node_name2
+-->
+
+<!-- START: copy from here to 'END' for each node 
+
+<hr>
+
+\subsection node_name node_name
+
+node_name does (provide a basic description of your node)
+
+\subsubsection Usage
+\verbatim
+$ node_type1 [standard ROS args]
+\endverbatim
+
+\par Example
+
+\verbatim
+$ node_type1
+\endverbatim
+
+
+\subsubsection topics ROS topics
+
+Subscribes to:
+- \b "in": [std_msgs/FooType] description of in
+
+Publishes to:
+- \b "out": [std_msgs/FooType] description of out
+
+
+\subsubsection parameters ROS parameters
+
+Reads the following parameters from the parameter server
+
+- \b "~param_name" : \b [type] description of param_name
+- \b "~my_param" : \b [string] description of my_param
+
+Sets the following parameters on the parameter server
+
+- \b "~param_name" : \b [type] description of param_name
+
+
+\subsubsection services ROS services
+- \b "foo_service": [std_srvs/FooType] description of foo_service
+
+
+END: copy for each node -->
+
+
+<!-- START: Uncomment if you have any command-line tools
+
+\section commandline Command-line tools
+
+This section is a catch-all for any additional tools that your package
+provides or uses that may be of use to the reader. For example:
+
+- tools/scripts (e.g. rospack, roscd)
+- roslaunch .launch files
+- xmlparam files
+
+\subsection script_name script_name
+
+Description of what this script/file does.
+
+\subsubsection Usage
+\verbatim
+$ ./script_name [args]
+\endverbatim
+
+\par Example
+
+\verbatim
+$ ./script_name foo bar
+\endverbatim
+
+END: Command-Line Tools Section -->
+
+*/
\ No newline at end of file


This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.