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

Close

[362028]: src / hugin1 / hugin / xrc / data / help_en_EN / Hugin_Panorama_Workflow.html Maximize Restore History

Download this file

Hugin_Panorama_Workflow.html    125 lines (104 with data), 8.1 kB

  1
  2
  3
  4
  5
  6
  7
  8
  9
 10
 11
 12
 13
 14
 15
 16
 17
 18
 19
 20
 21
 22
 23
 24
 25
 26
 27
 28
 29
 30
 31
 32
 33
 34
 35
 36
 37
 38
 39
 40
 41
 42
 43
 44
 45
 46
 47
 48
 49
 50
 51
 52
 53
 54
 55
 56
 57
 58
 59
 60
 61
 62
 63
 64
 65
 66
 67
 68
 69
 70
 71
 72
 73
 74
 75
 76
 77
 78
 79
 80
 81
 82
 83
 84
 85
 86
 87
 88
 89
 90
 91
 92
 93
 94
 95
 96
 97
 98
 99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
<!DOCTYPE html>
<html lang="en" dir="ltr" class="client-nojs">
<head>
<title>Hugin Panorama Workflow - PanoTools.org Wiki</title>
<meta charset="UTF-8" />
<meta name="generator" content="MediaWiki 1.19.0" />
<style media="screen" type="text/css" title="Screen style sheet"> @import url(manual.css); </style>
<style>a:lang(ar),a:lang(ckb),a:lang(fa),a:lang(kk-arab),a:lang(mzn),a:lang(ps),a:lang(ur){text-decoration:none}a.new,#quickbar a.new{color:#ba0000}
/* cache key: pt_wikidb:resourceloader:filter:minify-css:7:c88e2bcd56513749bec09a7e29cb3ffa */
</style>
<!--[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-Hugin_Panorama_Workflow skin-vector action-view">
<!-- content -->
<div id="content" class="mw-body">
<a id="top"></a>
<!-- firstHeading -->
<h1 id="firstHeading" class="firstHeading">
<span dir="auto">Hugin Panorama Workflow</span>
</h1>
<!-- /firstHeading -->
<!-- bodyContent -->
<div id="bodyContent">
<!-- tagline -->
<div id="siteSub">From PanoTools.org Wiki</div>
<!-- /tagline -->
<!-- subtitle -->
<!-- /subtitle -->
<!-- jumpto -->
<!-- /jumpto -->
<!-- bodycontent -->
<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>
<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>
<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>
<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>
<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>
<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>
<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="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>
<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>
<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=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>