Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

Commit [362028] default Maximize Restore History

Updated help

tmodes tmodes 2013-10-20

removed src/hugin1/hugin/xrc/data/help_en_EN/Nona_gui.html
changed src/hugin1/hugin/xrc/data/help_en_EN/Hugin.html
changed src/hugin1/hugin/xrc/data/help_en_EN/Control_Point_Detector_Parameters.html
changed src/hugin1/hugin/xrc/data/help_en_EN/Hugin_translation_guide.html
changed src/hugin1/hugin/xrc/data/help_en_EN/Lens_correction_model.html
changed src/hugin1/hugin/xrc/data/help_en_EN/Hugin_Control_Points_tab.html
changed src/hugin1/hugin/xrc/data/help_en_EN/Nona.html
changed src/hugin1/hugin/xrc/data/help_en_EN/Hugin_Photos_tab.html
changed src/hugin1/hugin/xrc/data/help_en_EN/Fisheye_Projection.html
changed src/hugin1/hugin/xrc/data/help_en_EN/pages.txt
changed src/hugin1/hugin/xrc/data/help_en_EN/Pto_gen.html
changed src/hugin1/hugin/xrc/data/help_en_EN/Hugin_Scripting_Interface.html
changed src/hugin1/hugin/xrc/data/help_en_EN/Hugin_FAQ.html
changed src/hugin1/hugin/xrc/data/help_en_EN/Panorama_scripting_in_a_nutshell.html
changed src/hugin1/hugin/xrc/data/help_en_EN/Alpha_channel.html
changed src/hugin1/hugin/xrc/data/help_en_EN/help_index_en.hhk
changed src/hugin1/hugin/xrc/data/help_en_EN/Hugin_Stitcher_tab.html
changed src/hugin1/hugin/xrc/data/help_en_EN/help_toc_en.hhc
changed src/hugin1/hugin/xrc/data/help_en_EN/hugin_help_en_EN.hhp
changed src/hugin1/hugin/xrc/data/help_en_EN/Control_point_generators.html
copied src/hugin1/hugin/xrc/data/help_en_EN/MatchPoint.html -> src/hugin1/hugin/xrc/data/help_en_EN/Hugin_Panorama_Workflow.html
src/hugin1/hugin/xrc/data/help_en_EN/Hugin.html Diff Switch to side-by-side view
Loading...
src/hugin1/hugin/xrc/data/help_en_EN/Control_Point_Detector_Parameters.html Diff Switch to side-by-side view
Loading...
src/hugin1/hugin/xrc/data/help_en_EN/Hugin_translation_guide.html Diff Switch to side-by-side view
Loading...
src/hugin1/hugin/xrc/data/help_en_EN/Lens_correction_model.html Diff Switch to side-by-side view
Loading...
src/hugin1/hugin/xrc/data/help_en_EN/Hugin_Control_Points_tab.html Diff Switch to side-by-side view
Loading...
src/hugin1/hugin/xrc/data/help_en_EN/Nona.html Diff Switch to side-by-side view
Loading...
src/hugin1/hugin/xrc/data/help_en_EN/Hugin_Photos_tab.html Diff Switch to side-by-side view
Loading...
src/hugin1/hugin/xrc/data/help_en_EN/Fisheye_Projection.html Diff Switch to side-by-side view
Loading...
src/hugin1/hugin/xrc/data/help_en_EN/pages.txt Diff Switch to side-by-side view
Loading...
src/hugin1/hugin/xrc/data/help_en_EN/Pto_gen.html Diff Switch to side-by-side view
Loading...
src/hugin1/hugin/xrc/data/help_en_EN/Hugin_Scripting_Interface.html Diff Switch to side-by-side view
Loading...
src/hugin1/hugin/xrc/data/help_en_EN/Hugin_FAQ.html Diff Switch to side-by-side view
Loading...
src/hugin1/hugin/xrc/data/help_en_EN/Panorama_scripting_in_a_nutshell.html Diff Switch to side-by-side view
Loading...
src/hugin1/hugin/xrc/data/help_en_EN/Alpha_channel.html Diff Switch to side-by-side view
Loading...
src/hugin1/hugin/xrc/data/help_en_EN/help_index_en.hhk Diff Switch to side-by-side view
Loading...
src/hugin1/hugin/xrc/data/help_en_EN/Hugin_Stitcher_tab.html Diff Switch to side-by-side view
Loading...
src/hugin1/hugin/xrc/data/help_en_EN/help_toc_en.hhc Diff Switch to side-by-side view
Loading...
src/hugin1/hugin/xrc/data/help_en_EN/hugin_help_en_EN.hhp Diff Switch to side-by-side view
Loading...
src/hugin1/hugin/xrc/data/help_en_EN/Control_point_generators.html Diff Switch to side-by-side view
Loading...
src/hugin1/hugin/xrc/data/help_en_EN/MatchPoint.html to src/hugin1/hugin/xrc/data/help_en_EN/Hugin_Panorama_Workflow.html
--- a/src/hugin1/hugin/xrc/data/help_en_EN/MatchPoint.html
+++ b/src/hugin1/hugin/xrc/data/help_en_EN/Hugin_Panorama_Workflow.html
@@ -1,7 +1,7 @@
 <!DOCTYPE html>
 <html lang="en" dir="ltr" class="client-nojs">
 <head>
-<title>MatchPoint - PanoTools.org Wiki</title>
+<title>Hugin Panorama Workflow - PanoTools.org Wiki</title>
 <meta charset="UTF-8" />
 <meta name="generator" content="MediaWiki 1.19.0" />
 
@@ -21,7 +21,7 @@
 
 
 <!--[if lt IE 7]><style type="text/css">body{behavior:url("/skins/vector/csshover.min.htc")}</style><![endif]--></head>
-<body class="mediawiki ltr sitedir-ltr ns-0 ns-subject page-MatchPoint skin-vector action-view">
+<body class="mediawiki ltr sitedir-ltr ns-0 ns-subject page-Hugin_Panorama_Workflow skin-vector action-view">
 		
 		
 		<!-- content -->
@@ -30,7 +30,7 @@
 			
 						<!-- firstHeading -->
 			<h1 id="firstHeading" class="firstHeading">
-				<span dir="auto">MatchPoint</span>
+				<span dir="auto">Hugin Panorama Workflow</span>
 			</h1>
 			<!-- /firstHeading -->
 			<!-- bodyContent -->
@@ -45,87 +45,81 @@
 				
 				<!-- /jumpto -->
 								<!-- bodycontent -->
-				<div id="mw-content-text" lang="en" dir="ltr" class="mw-content-ltr">
-<h2> <span class="mw-headline" id="Introduction"> Introduction </span></h2>
-<p>MatchPoint is a next generation CP generator. The result of a GSoC2007 project SoC2007_project_Feature_Descriptor<a class="external" href="http://wiki.panotools.org/SoC2007_project_Feature_Descriptor">[*]</a>. Currently it offers only keypoint detection but not matching (matching was part of other GSoC 07 project that was not carried out) and can currently be used only as a replacement for generatekeys from <a href="Autopano-sift.html" title="Autopano-sift">autopano-sift</a> or <a href="Autopano-sift-C.html" title="Autopano-sift-C">autopano-sift-C</a>. 
-</p><p>A current version of matchpoint can be obtained via the <a href="Hugin.html" title="Hugin">hugin</a> project.
-</p><p>Goal of this MatchPoint is to create a complete control point suite that will be used by <a href="Hugin.html" title="Hugin">hugin</a> as a replacement(or at least an alternative) to existing autopano suites.
-</p><p>If you want to use MatchPoint in the process of creating panoramic images now(when not all features are implemented) you will have to use autopano-sift also.
-</p><p>Usage:<br />
-// first extract features from the first image and output them to the image1.key: <br />
-MatchPoint image1.jpg image1.key 
-</p><p>// for second image: <br />
-MatchPoint image2.jpg image2.key 
-</p><p>// match features from the two generated files using autopano: <br />
-autopano project.pto image1.key image2.key 
-</p><p>// open the project file in hugin: <br />
-hugin project.pto
+				<div id="mw-content-text" lang="en" dir="ltr" class="mw-content-ltr"><p>Hugin provides different work flows for generating panoramas. This page will list some possibility and give you some suggestions for your own work flow.
+</p><p>This is not a step by step instruction. Not all projects will need all steps. It will give you some ideas for your own projects.
+</p><p>The panorama creating consists of two major steps: 
 </p>
-<h2> <span class="mw-headline" id="Command_line_usage"> Command line usage </span></h2>
-<p>Usage: <br /> 
+<ol><li> generating project file and align images
+</li><li> stitching of project file
+</li></ol>
+<p>The following chapters will give you some details for both steps. You can combine both steps as you like. You can run all full automatic, or you can run all manual, or you can generate the project on the command line and stitch with PTBatcherGUI<a class="external" href="http://wiki.panotools.org/PTBatcherGUI">[*]</a>, or you can all do on the command line, or or or...
 </p>
-<dl><dt>MatchPoint [options] image1.jpg output.key</dt><dd><br />
-</dd></dl>
-<p>Parameters:
+
+<h2> <span class="mw-headline" id="Generating_project_file"> Generating project file </span></h2>
+<h3> <span class="mw-headline" id="Fully_automatic_generation"> Fully automatic generation </span></h3>
+<p>PTBatcherGUI<a class="external" href="http://wiki.panotools.org/PTBatcherGUI">[*]</a> provides an options to create a project file and run the assistant on these generated project files.
+Go to <b>File&gt;Search directory for...&gt;Images</b> and select the path to your images. After pressing <b>Start</b> PTBatcherGUI will search for possible projects depending on the EXIF information in the images. When the search is finished, the bottom list box displays all found panoramas. Select the panoramas you want to process and then click <b>Send selected panoramas to queue</b> to send these panoramas to the assistant queue. When you now start the batch processing, the assistant is running on all project files.
+</p><p>If you tick the option <b>Automatic stitch after assistant</b> the panorama will be stitched after running the assistant. This will give you a full automatic panorama processing from the input images to the final panorama.
+</p><p>Also in <a href="Hugin.html" title="Hugin">Hugin</a> an automatic alignment can be achieved. After adding the images run the assistant on this project. You can also send the projects to the assistant queue and process the project files later (e.g. during night).
 </p>
-<dl><dt>-v</dt><dd> verbose output
-</dd><dt>-t</dt><dd> generate keypoint file for matlab test suite(file name is generated using formula: image1.jpg.key)
-</dd></dl>
-<p>Arguments:
+<h3> <span class="mw-headline" id="Manual_generation"> Manual generation </span></h3>
+<p>Project file can be generated and aligned in <a href="Hugin.html" title="Hugin">Hugin</a>. A possible work flow would be
 </p>
-<dl><dt>image1.jpg</dt><dd> Path to image to be analyzed.
-</dd><dt>output.key</dt><dd> Output keypoint file.
-</dd></dl>
-<h2> <span class="mw-headline" id="Algorithm_description"> Algorithm description </span></h2>
-<h3> <span class="mw-headline" id="Integral_images"> Integral images </span></h3>
-<p>Before detection process images are integrated. Each element-pixel (x,y) of integral image represents sum of pixels from (0,0) to (x,y) on initial image. This makes calculating sum of a region much faster. In addition, convolution at any scale has equal time complexity.
-This part is neccessary only when using box filters for detection.
+<ol><li> Add images.
+</li><li> Assign lens and stacks.
+</li><li> Find control points, e.g. with <a href="Cpfind.html" title="Cpfind">cpfind</a>.
+</li><li> Control point checking (<a href="Celeste_standalone.html" title="Celeste standalone">celeste</a>, <a href="Cpclean.html" title="Cpclean">cpclean</a>, manual)
+</li><li> Geometric optimisation (<a href="Yaw.html" title="Yaw">yaw</a>, <a href="Pitch.html" title="Pitch">pitch</a>, <a href="Roll.html" title="Roll">roll</a>, <a href="Lens_distortion.html" title="Lens distortion">lens parameters</a>).
+</li><li> Photometric optimisation (exposure values, <a href="Vignetting.html" title="Vignetting">vignetting</a>, white balance<a class="external" href="http://wiki.panotools.org/White_balance">[*]</a>).
+</li><li> Select output parameters (projection, canvas size, ...)
+</li></ol>
+<h3> <span class="mw-headline" id="Scripting"> Scripting </span></h3>
+<p>The project can also be created and aligned with command line tools (see <a href="Panorama_scripting_in_a_nutshell.html#Creating_hugin_projects_on_the_command-line" title="Panorama scripting in a nutshell">here</a> for more details).
+</p><p>A workflow similar to the assistant would be look like:
 </p>
-<h3> <span class="mw-headline" id="Feature_detection"> Feature detection </span></h3>
-<p>Points are detected with Hessian Detector using box filters. Here is a description of detection process over time. This may not be entirely compatible flow with code's flow, because some parts are simultaneous(e.q. first two steps).
-</p><p><b> Convolution of pixels </b><br />
-Convolution of a pixel at certain scale is carried out with approximation of Gauss 2D function - this is called box filter detection. Each kernel has 4 convolution filters(3 of them are unique - xy and yx filters are the same). The resulting value is then the determinant of Hessian matrix where elements represent convolution values of 4 filters. 
-</p><p>Kernel sizes for convolution are:<br /> 
-9,15,21,27, (1st octave)<br />
-15,27,39,51, (2nd octave)<br />
-21,45,69,93 (3rd octave)<br />
-</p><p>MatchPoint features also offers two ways of convolution:
+<pre>    pto_gen -o project.pto *.jpg
+    cpfind -o project.pto --multirow --celeste project.pto
+    cpclean -o project.pto project.pto
+    linefind -o project.pto project.pto
+    autooptimiser -a -m -l -s -o project.pto project.pto
+    pano_modify --canvas=AUTO --crop=AUTO -o project.pto project.pto
+</pre>
+<p>An other approach for multi-row panoramas with featureless images could look like:
 </p>
-<ul><li> box filter: faster and preferable way
-</li><li> sliding window(implemented for convenience but needs debug): slower, more accurate but also more sensitive to noise
-</li></ul>
-<p><b> Finding maxima </b><br />
-In order to achieve invariance to scaling, detection needs to find maxima of Hessian determinant across many scales. To handle this, octaves were introduced. Octaves are interpolation of determinants at various scales(usually two scales). MatchPoint offers detection at max 3 octaves(by setting a parameter). E.q. at first octave a point can be detected at scale 1.6(=((9+15/2)*1.2)/9 where 1.2 is initial scale and 9 is initial kernel size) or 3.2(=((21+27/2)*1.2)/9. Keypoint's main scale is then selected according to the highest value of Hessian determinant.
-</p><p><b> Selecting points </b><br />
-</p><p>Next step is to select points with high values of their determinants(regardless of scale where points where detected) that represent invariant keypoints that will be used further processing. This is achieved using a fixed threshold which should be set low(because otherwise it may happen that no points would be detected). 
-</p><p>Then non-maxima suppression is applied(only points with local maxima of determinants are selected).
-</p><p>At this point we have a list of points that can vary in length, because threshold from previous step is hardcoded. This can result in over 200.000 points for larger images and that is too much(regardless of image size we need the same amount of control points for all images - min 3 control point/overlapping images), so we need to strip down the list below 10.000 points (this number is set intuitively and it is based on consumed time). (Note: this work is progress).
+<pre>    pto_gen -o project.pto *.jpg
+    pto_var -o project.pto --set y=-100+(i%6)*40,p=(i&lt;6)?-30:30,r=0 project.pto
+    cpfind --prealigned -o project.pto project.pto
+    geocpset -o project.pto project.pto
+    linefind -o project.pto project.pto
+    autooptimiser -a -m -l -s -o project.pto project.pto
+    pano_modify --canvas=AUTO --crop=AUTO -o project.pto project.pto
+</pre>
+<h2> <span class="mw-headline" id="Stitching"> Stitching </span></h2>
+<p>All stitching engine uses the same code base. So there is no preferences for one or the other. It is a matter of taste, which one you use.
 </p>
-<h3> <span class="mw-headline" id="Feature_description"> Feature description </span></h3>
-<p><b> Orientation assignment </b><br />
-Scale invariance is achieved by assigning main orientation of the interest point using special algorithm proposed by Herbert Bay. Efficiency of this algorithm has not been yet tested, therefore the executable of MatchPoint does not use any orientation assignment.
-</p><p><b> Shape Context descriptors </b><br />
-To each interest point a 36 element descriptor is assigned. Elements of this descriptors are organized according to Shape Context descriptor proposed by <a rel="nofollow" class="external text" href="http://www.eecs.berkeley.edu/Research/Projects/CS/vision/shape/sc_digits.html">S. Belongie, J. Malik and J. Puzicha</a> and adapted by <a rel="nofollow" class="external text" href="http://www.robots.ox.ac.uk/~vgg/research/affine/index.html">K. Mikolajczyk</a> for the purpose of finding control points. 
-</p><p>Steps in creating descriptors:
+<h3> <span class="mw-headline" id="PTBatcherGUI"> PTBatcherGUI </span></h3>
+<p>The default stitching engine is PTBatcherGUI<a class="external" href="http://wiki.panotools.org/PTBatcherGUI">[*]</a>. You can add different projects to a queue and process the queue later without control. But it can also be configured to start immediately.
+</p><p>You can also stitch all project files in a given directory: After select the directory in <b>File&gt;Search directory for...&gt;Project</b> all project files will be added to the queue.
 </p>
-<ol><li> detect edges in the region around the interest point(region size depends on the scale at which point was detected). MatchPoint uses vigra's API(Canny edge detection) for this.
-</li><li> based on relative location of edge elements create a histogram with 36 values. Use log-polar values. Edge point contribution to the histogram is based on it's magnitude and orientation.
-</li></ol>
-<p>See reference papers for details.
+<h3> <span class="mw-headline" id="Hugin_stitch_project"> Hugin_stitch_project </span></h3>
+<p><a href="Hugin_stitch_project.html" title="Hugin stitch project">Hugin_stitch_project</a> can only stitch a single project. The processing starts immediately.
 </p>
-<h2> <span class="mw-headline" id="References">References</span></h2>
-<ul><li> <a rel="nofollow" class="external text" href="http://www.vision.ee.ethz.ch/~surf/">Speeded Up Robust Features - SURF</a>
-</li><li> <a rel="nofollow" class="external text" href="http://www.robots.ox.ac.uk/~vgg/research/affine">Matlab suite for testing, papers for detection, descriptors and evaluation by K. Mikolajczyk</a>
-</li><li> <a rel="nofollow" class="external text" href="http://www.eecs.berkeley.edu/Research/Projects/CS/vision/shape/sc_digits.html">Shape Context descriptors</a>
-</li></ul>
-
+<h3> <span class="mw-headline" id="Scripting_2"> Scripting </span></h3>
+<p>The stitching can also be started from the command line:
+</p>
+<pre>    pto2mk -o project.mk -p prefix project.pto
+    make -f project.mk all
+</pre>
+<p>Attention: <a href="Pto2mk.html" title="Pto2mk">pto2mk</a> does not use the preferences from <a href="Hugin_Preferences.html" title="Hugin Preferences">Hugin</a>. See <a href="Panorama_scripting_in_a_nutshell.html#Makefile_stitching_system" title="Panorama scripting in a nutshell">here</a> how to set these parameters in this use case.
+</p><p>The makefile can also created during project save in Hugin, if you select <b>Create makefile automatically during project save</b> in the <a href="Hugin_Preferences.html" title="Hugin Preferences">Hugin preferences</a>.
+</p>
 
 
 
 </div>				<!-- /bodycontent -->
 								<!-- printfooter -->
 				<div class="printfooter">
-				Retrieved from "http://wiki.panotools.org/index.php?title=MatchPoint&amp;oldid=10254<a class="external" href="http://wiki.panotools.org/index.php?title=MatchPoint&amp;oldid=10254">[*]</a>"				</div>
+				Retrieved from "http://wiki.panotools.org/index.php?title=Hugin_Panorama_Workflow&amp;oldid=15563<a class="external" href="http://wiki.panotools.org/index.php?title=Hugin_Panorama_Workflow&amp;oldid=15563">[*]</a>"				</div>
 				<!-- /printfooter -->
 												<!-- catlinks -->
 				</div></div></body></html>