PanoTools.org Wiki - User contributions [en]

Autooptimiser

2011-02-07T15:17:20Z

Seb Przd: Added usage information

'''autooptimiser''' is a smart optimiser replacement for [[PTOptimizer]] and [[vig_optimize]], it is part of the [[hugin]] suite of tools for panoramic imaging.

It is not a 100% drop-in replacement for '''PTOptimizer''' as it has a slightly different interface and some extra features:

* '''PTOptimizer''' will write the output of the optimisation into the input script file as 'o' lines, deleting any that already exist. This behaviour is a little strange, so '''autooptimiser''' writes the result to STDOUT or a new file, as is more usual for a command-line tool.
* Not clobbering the original file means that there is no need to create 'o' lines, the output file is in the same format as the input with optimised values applied to the 'i' lines.
* [[PTStitcher]] requires 'o' lines, so the output of '''autooptimiser''' isn't suitable for stitching with '''PTStitcher''' without further processing - Stitch these files with [[nona]] instead.

Additional features:

* '''autooptimiser''' can perform ''pairwise'' optimisation instead of trying to optimise all rotation parameters at the same time, this means that there is no need to pre-position images before optimisation.
* ''levelling'' the horizon in a set of images can be performed, this is the same functionality as the '''Straighten''' button in the [[hugin Preview window]].
* ''auto-align'' mode will pick an optimisation scheme suited to the distribution of [[control points]] in the project so there is no need to specify parameters to optimise.
* '''autooptimiser''' can adjust the panorama [[field of view]], dimensions and [[Projections|projection]] to suit the input images.
* the '''field of view''' of input images can be specified, this is useful as the project files created by [[autopano]] and [[autopano-sift]] don't specify the '''field of view''' of the input photos.
* '''autooptimiser''' can also perform photometric optimisation like the [[vig_optimize]] tool. Depending on the input images it selects automaticly these photometric parameters (exposure, white balance, [[vignetting]], [[camera response curve]]) which should be optimised.

== Usage ==
autooptimiser [options] project.pto

(- can be specified to read the project from stdio.)

=== Description ===

'''autooptimiser''' works similarly to '''PToptimizer''' but with extra command-
line options.

It is also different in that PToptimizer appends its output onto the
input file in the form of ’o’ lines which need further processing.
autooptimiser simply updates the project and writes it to a new file.

=== Options ===

<tt>-o file.pto</tt> Output file. If omitted, stdout is used.

* Optimisation options (if not specified, no optimisation takes place):

<tt>-a</tt> Auto align mode, includes various optimisation stages, depending on
the amount and distribution of the control points

<tt>-p</tt> Pairwise optimisation of yaw, pitch and roll, starting from first
image

<tt>-n</tt> Optimize parameters specified in script file (like PToptimizer).

* Post-processing options:

<tt>-l</tt> Level horizon (works best for horizontal panoramas)

<tt>-s</tt> Automatically select a suitable output projection and size

* Other options:

<tt>-q</tt> Quiet operation (no progress is reported)

<tt>-v HFOV</tt> Specify horizontal field of view of input images. Used if the .pto
file contains invalid HFOV values (autopano-SIFT writes .pto files
with invalid HFOV)

When -a, -l, and -s options are used together, an operation similar to
the one of the "Align" button in hugin is performed.

[[Category:Software:Platform:Windows]]
[[Category:Software:Platform:Mac OS X]]
[[Category:Software:Platform:Linux]]
[[Category:Software:Hugin]]

Control point generators

2009-09-14T11:52:00Z

Seb Przd: /* Specific purposes */

This stub is to hold the list of available [[Control points|control point]] generators in general, and how they can be configured in Hugin in particular (starting with version 2009.2)

This list should supersede the one available on the [[GUI_front-ends]] page.

== All-purpose CP generators ==

[[Autopano]]

[[Autopano-sift]]

[[Autopano-sift-C]]

[[Match-n-shift]] should have its own page, as it is only mentioned [[Hugin_Compiling_Ubuntu#Match-n-shift|here]].

[[Panomatic]]

=== Obsolete ===

[[PanoPoints]]

== Key feature generators ==

These programs do not include the matching part, but are able to generate key point descriptions that can then be matched by autopano.

[[MatchPoint]]

== Specific purposes ==

[[Align a stack of photos]]

[[Category:Software:Survey ]]

Control point generators

2009-09-14T11:49:17Z

Seb Przd: Page creation

Hugin Compiling Ubuntu

2009-09-11T19:09:33Z

Seb Przd: /* Building Enblend */

These instructions are work in progress and updated when newer versions of Ubuntu are released or when Hugin introduces new dependencies. They have worked, at the time of release or soon thereafter, with the following Ubuntu/Kubuntu versions:
* Ubuntu 9.04: on AMD64 computer
* Ubuntu 8.10: on AMD64 computer
* Ubuntu 8.04: on an Intel processor
* Ubuntu 7.10: on AMD Athlon XP
* Ubuntu 7.04: on AMD64 computer
* Ubuntu 6.06: on AMD64 computer

They are likely to work only for the latest one, but you can check this page's history at the time that the older Ubuntu version was the most recent one to find the specifics for that version.

Apart from the odd change in package name, nothing should be substantially different (and if does not work, please leave a comment on the [http://groups.google.com/group/hugin-ptx hugin-ptx mailing list]). Don't worry if the same package appears twice in an apt-get install line - apt-get will update existing packages if there is a newer version, and ignore duplicates if the latest version is already installed. On the other hand, if apt-get says that it can't find a package, it might be the odd change in package name. You can find a replacement package by using apt-cache search with a substring of the package required, e.g.
<pre>apt-cache search wxW
</pre>

The goal is to build hugin and the whole set of helper applications required.

== Building environment ==
Since we are going to build hugin, libpano13 and enblend we need to download and install all the development packages. This is very easy with apt-get.
In a terminal window (K menu -> System -> Konsole or Applications -> Accessories -> Terminal (in Kubuntu), Applications -> Accessories -> Terminal (in Ubuntu))

<pre>sudo apt-get install build-essential autoconf automake1.9 libtool flex bison gdb
</pre>

Unless you have an amd64 system prior to 7.10, add the following packages.
<pre>sudo apt-get install libc6-dev libgcc1
</pre>

For older amd64 environments, the packages have a slightly different name:
<pre>sudo apt-get install libc6-dev-amd64 lib64gcc1
</pre>

To get the bleeding edge we'll need access to the SVN, Mercurial and Bazaar repositories, and for this we need the correct tools:

<pre>
sudo apt-get install subversion mercurial bzr
</pre>

Not necessary, but useful if you want to move to the next level and build packages for distribution (list is incomplete):

<pre>
sudo apt-get install subversion-tools
</pre>

== Building Enblend ==

Get the dependencies. If you are working with large images (300 megapixels and up), you should have a libtiff-devel compiled with large file support and libstdc++6.

<pre>sudo apt-get install pkg-config libtiff4-dev libboost-graph-dev libboost-thread-dev \
liblcms1-dev libglew1.5-dev libplot-dev libglut3-dev libopenexr-dev libxi-dev libxmu-dev
</pre>

For Ubuntu systems prior to 8.10, you will also need

<pre>sudo apt-get install libopenexr2ldbl
</pre>

Once all dependencies are in place, get the code. The official repository has migrated from CVS to Mercurial:

<pre>
hg clone http://enblend.hg.sourceforge.net:8000/hgroot/enblend/enblend enblend
cd enblend
</pre>

If you already have checked out enblend, to update the code to the latest version you need to run:
<pre>
hg pull
hg update
</pre>

We are then ready to compile. The CXXFLAGS <tt>--param inline-unit-growth=60</tt> is a workaround for x86_64 systems, Feb 2009, and apparently no longer needed (set by default). If you have an SMP machine and you're building a recent version, <tt>--disable-image-cache</tt> and <tt>--enable-openmp</tt> will speed up enblend/enfuse massively but may cause segmentation faults; in that case you will be better off with <tt>--enable-image-cache</tt> and <tt>--disable-openmp.</tt> <tt>-march=native</tt> is also beneficial and -O2 is better than -O3.

<pre>
make --makefile=Makefile.scm
CXXFLAGS="--param inline-unit-growth=60 -march=native -O2" ./configure --disable-image-cache --enable-openmp
make
</pre>

The second make step can be very long and memory consuming. Make sure you have enough swap space, and go get a healthy snack while the computer is compiling.

If you encounter problems at any of these stages, please report back to the hugin-ptx mailing list. Report what command in the sequence you were executing, what machine/operating system, the revision checked out from CVS, and all other relevant information.

You are then ready to install with
<pre>sudo make install</pre>

== Building Libpano13 ==
libpano13 is the new version of the PanoTools libraries. This is a necessary component for hugin, and we need to build it first.
To build libpano13 we need some libraries and particularly their <code>dev</code> package:
<pre>sudo apt-get install zlib1g zlib1g-dev libpng12-dev libjpeg62-dev libtiff4-dev</pre>

On older distributions, zlib1g and zlib1g-dev may not be found. In that case, the same library may be available with the names lib64z1 and lib64z1-dev.

We then need to download the source code from SVN:
<pre>
svn co https://panotools.svn.sourceforge.net/svnroot/panotools/trunk/libpano libpano13
cd libpano13
</pre>

In the future there is no need to get the whole source again. Just issue the following commands to bring your source up to date:
<pre>
cd libpano13
svn up
</pre>

Now start the building process:
<pre>
./bootstrap
</pre>

If any libraries are missing, the script will complain (or at least, let you know that some library hasn't been found). In that case you probably need to install the library. To find in what package is that library, a general rule is to run the command <code>apt-cache search ''missingfile''</code>, find the relevant library and install both the library and the related <code>-dev</code> package.
Run the <code>./configure</code> script and repeat this process until you have met all the dependencies.
Then we are ready to launch the make process with
<pre>make</pre>

If the library successfully compiles, you have to install it with
<pre>sudo make install
sudo ldconfig</pre>
The last part is for the OS to be aware of the new library (that has been installed in <code>/usr/local/lib</code>).
We can now go back up one folder level and get ready for hugin.
<pre>cd ..</pre>

== Building Hugin ==

=== Dependencies ===

First we need to activate the <code>universe</code> repository (in adept package manager, or by editing the /etc/apt/sources.lst file for example) and get the dependencies:
<pre>
sudo apt-get install cmake libopenexr-dev libboost-dev boost-build libboost-thread-dev libboost-graph-dev \
gettext libwxgtk2.8-dev libexiv2-dev libimage-exiftool-perl libglew-dev liblapack-dev
</pre>

=== Fetch the Source Code from SVN ===

Next we download Hugin from SVN. But which Hugin? There are many [http://svnbook.red-bean.com/en/1.1/ch04.html#svn-ch-4-sect-1 branches] in SVN. Also SVN keeps track of every single change (revision) in time, so we can download a branch in its state at a specific point in time. For example <code>-r 4008 https://hugin.svn.sourceforge.net/svnroot/hugin/hugin/trunk/</code> will download the trunk branch at the point in time when revision [http://hugin.svn.sourceforge.net/viewvc/hugin?view=rev&revision=4008 4008] was committed, which happens to be Tue Jul 7 22:07:54 2009 UTC. It also happens to be the same as the 0.8.0 release. For a list of branches and revisions that build well, refer to these [http://wiki.panotools.org/Development_of_Open_Source_tools#Specific_revisions lists]. There is no guarantee that a particular branch and/or revision builds and/or performs as expected.

<pre>
svn co -r 4061 https://hugin.svn.sourceforge.net/svnroot/hugin/hugin/tags/hugin-2009.07.1/ hugin
</pre>

If you know what you are doing, you can replace /hugin-2009.07.1/ with another branch; and you can omit the -r and get the last revision of that branch.

In the future there is no need to get the whole source again. Just issue the following commands to bring your source up to date:
<pre>
cd hugin
svn up
</pre>

=== Set the Build Environment ===

Next we set up the build environment using cmake.

If you compiled and installed libpano to a non standard location set the variables CMAKE_INCLUDE_PATH and CMAKE_LIBRARY_PATH to point to your install location's include and lib directories.

If you are building for distribution, you want to set CMAKE_INSTALL_PREFIX=/usr

<pre>
mkdir hugin-build
cd hugin-build
cmake ../hugin -DENABLE_LAPACK=YES -DCPACK_BINARY_DEB:BOOL=ON -DCPACK_BINARY_NSIS:BOOL=OFF \
-DCPACK_BINARY_RPM:BOOL=OFF -DCPACK_BINARY_STGZ:BOOL=OFF -DCPACK_BINARY_TBZ2:BOOL=OFF \
-DCPACK_BINARY_TGZ:BOOL=OFF -DCPACK_BINARY_TZ:BOOL=OFF
</pre>

=== Build and Install ===

Finally, we use make to build the code and package it, and dpkg to install it. Look for the version number in the .deb file created and edit the lines below accordingly:

<pre>
make package
ls *.deb
sudo dpkg -i hugin-0000.00.0-Linux.deb
</pre>

'''Important:''' the package does not track dependencies yet, so it likely to fail on machines others than yours.

Reference: [http://theseblog.free.fr/2007/10/building-hugin-in-ubuntu-feisty-fawn.php]

== Autopano-sift-C ==

Pre-Requisites:
<pre>
sudo apt-get install libxml2-dev
</pre>

To build
<pre>
svn co https://hugin.svn.sourceforge.net/svnroot/hugin/autopano-sift-C/trunk/ autopano-sift-C
cd autopano-sift-C
cmake -DCMAKE_INSTALL_PREFIX=/usr/local .
make
sudo make install
</pre>

== Match-n-shift ==

Match-n-shift is yet an other Autopano-SIFT replacement. It comes in a bundle with pto file manipulation perl libraries and a rich selection of other tools that use nona, enblend, ImageMagick among other things. To use match-n-shift, you need to install at least the [http://search.cpan.org/dist/Panotools-Script/ Panotools::Script] library and some other perl modules. It requires:

* Image::Size 2.9
* Storable 2.0
* Image::ExifTool 6

Chances are that you do not need to update Storable which is a standard perl module. To check the version of installed versions of these modules, write these lines to the command prompt:

perl -MStorable -le 'print Storable->VERSION;'
perl -MImage::Size -le 'print Image::Size->VERSION;'
perl -MImage::ExifTool -le 'print Image::ExifTool->VERSION;'

There are various ways to install or upgrade these modules. Ubuntu has binary packages for many perl modules, you can skip the CPAN installation below and type:

sudo apt-get install libimage-size-perl libimage-exiftool-perl

Alternatively, perl is an interpreted language and these modules are pure perl, so installing from source is an easy thing.

The best place to install perl modules is directly from a CPAN archive. CPAN is short for Comprehensive Perl Archive Network. The program to interact with CPAN comes with all perl installations. Start it by running:

sudo cpan

If this is your first time running the program you will be asked a number of questions (you can safely accept the suggested values). Last question lets you select a number of CPAN mirrors nearest to you.

When all is done, you can enter the install commands after the 'cpan>' prompt:

install Image::Size Storable Image::ExifTool

Answer 'y' to any question of dependencies and wait for install to complete. 'exit' leaves the cpan shell.

Next, you need to retrieve and install the Panotools-Script collection
of perl libraries (Panotools::Script) and programs that use them -
including match-n-shift:

svn co https://panotools.svn.sourceforge.net/svnroot/panotools/trunk/Panotools-Script Panotools-Script
cd Panotools-Script
perl Makefile.PL
make
make test
sudo make install

Just to confuse you, you can also ignore everything above and just install Panotools::Script and all its dependencies from CPAN. From command line, type:

sudo cpan Panotools::Script

You can run match-n-shift from command line using the same parameters as autopano-c-complete.sh or you can modify hugin to run it for you:

* start Hugin
* navigate the menu File to Preferences
* In the Preferences window, open the Autopano tab
* Select Autopano -> Autopano-SIFT
* tick the checkbox for Use alternative Autopano-SIFT program
* enter the full path to match-n-shift (/usr/local/bin/match-n-shift) in the Autopano-SIFT field
* enter the following string in the Arguments field:
-f %f -v %v -c -p %p -o %o %i

== MatchPoint ==

MatchPoint is a next generation CP generator. The result of a GSoC2007 project, it is still very experimental. Experience reports needed. Read more [http://groups.google.com/group/hugin-ptx/browse_thread/thread/cba2b2ce94dd9054 here]

Matchpoint is now located inside the main hugin source tree, no need to checkout https://hugin.svn.sourceforge.net/svnroot/hugin/gsoc07_featuredetection anymore. It is compiled together with hugin, but not installed by default.

* copy the MatchPoint executable into /usr/local/bin manually
<pre>
sudo cp src/matchpoint/matchpoint /usr/local/bin/
</pre>
* edit /usr/local/bin/autopano-c-complete.sh (do it with sudo to have the necessary permission)
** line 79: replace the .key.gz extension with .key (not sure if matchpoint supports compression)
** lines 83 and 88: replace '''generatekeys "$arg" $FILENAME $SIZE''' with '''matchpoint "$arg" $FILENAME''' (not sure if the size option or any other options of the original generatekeys are applicable)

== Pan-o-matic ==

Yet another control point generator [http://aorlinsk2.free.fr/panomatic/?p=home Home Page]

<pre>sudo apt-get install libboost-dev</pre>

Download [http://aorlinsk2.free.fr/panomatic/download.php?d=7&v=0.9.4 Panomatic 0.9.4 bz2]

<pre>
tar xvfj panomatic-0.9.4-src.tar.bz2
cd panomatic-0.9.4
./configure
make
sudo make install
</pre>

To use Pano-o-matic, open Hugin

* In File > Preferences > Autopano :
* Select Autopano-SIFT
* Check "Use alternative autopaon-SIFT program"
* Choose the path to the binary ( /usr/local/bin )
* In Arguments, put : -o %o %i

== Exiftool ==

ExifTool is a platform-independent Perl library plus a command-line application for reading, writing and editing meta information in image, audio and video files.

<pre>
sudo apt-get purge libimage-exiftool-perl
</pre>

<pre>
wget http://www.sno.phy.queensu.ca/~phil/exiftool/Image-ExifTool-7.83.tar.gz
tar -xzf Image-ExifTool-7.83.tar.gz
cd Image-ExifTool-7.83
perl Makefile.PL
make test
sudo make install
</pre>

== Panoglview ==

PanoGLView is an OpenGL hardware accelerated interactive immersive viewer for equirectangular images.

Pre-Requisites:
<pre>sudo apt-get install wx-common</pre>

To build
<pre>
svn co https://hugin.svn.sourceforge.net/svnroot/hugin/panoglview/trunk panoglview
cd panoglview
./bootstrap
./configure
make
sudo make install
</pre>

== FreePV ==

Pre-Requisites:
<pre>
sudo apt-get install cmake make pkg-config g++ mozilla-dev freeglut-dev zlib1g-dev libjpeg-dev libxext-dev libxmu-dev \
x11proto-xf86vidmode-dev libxxf86vm-dev libnspr4-dev libxml2-dev libpng12-dev
</pre>
To build
<pre>
svn co https://freepv.svn.sourceforge.net/svnroot/freepv/freepv/trunk/ freepv
cd freepv
cmake .
make
sudo make install
</pre>

== Notes for Packagers ==
* before releasing a tarball, upgrade the Changelog with svn2cl
<pre>
$ svn up
$ svn2cl
$ svn ci
</pre>

[[Category:Software:Hugin]]
[[Category:Software:Platform:Linux]]

Hugin Compiling Ubuntu

2009-09-09T15:02:24Z

Seb Przd: /* Building Enblend */ adding cautions about disable-image-cache and openmp

These instructions are work in progress and updated when newer versions of Ubuntu are released or when Hugin introduces new dependencies. They have worked, at the time of release or soon thereafter, with the following Ubuntu/Kubuntu versions:
* Ubuntu 9.04: on AMD64 computer
* Ubuntu 8.10: on AMD64 computer
* Ubuntu 8.04: on an Intel processor
* Ubuntu 7.10: on AMD Athlon XP
* Ubuntu 7.04: on AMD64 computer
* Ubuntu 6.06: on AMD64 computer

They are likely to work only for the latest one, but you can check this page's history at the time that the older Ubuntu version was the most recent one to find the specifics for that version.

Apart from the odd change in package name, nothing should be substantially different (and if does not work, please leave a comment on the [http://groups.google.com/group/hugin-ptx hugin-ptx mailing list]). Don't worry if the same package appears twice in an apt-get install line - apt-get will update existing packages if there is a newer version, and ignore duplicates if the latest version is already installed. On the other hand, if apt-get says that it can't find a package, it might be the odd change in package name. You can find a replacement package by using apt-cache search with a substring of the package required, e.g.
<pre>apt-cache search wxW
</pre>

The goal is to build hugin and the whole set of helper applications required.

== Building environment ==
Since we are going to build hugin, libpano13 and enblend we need to download and install all the development packages. This is very easy with apt-get.
In a terminal window (K menu -> System -> Konsole or Applications -> Accessories -> Terminal (in Kubuntu), Applications -> Accessories -> Terminal (in Ubuntu))

<pre>sudo apt-get install build-essential autoconf automake1.9 libtool flex bison gdb
</pre>

Unless you have an amd64 system prior to 7.10, add the following packages.
<pre>sudo apt-get install libc6-dev libgcc1
</pre>

For older amd64 environments, the packages have a slightly different name:
<pre>sudo apt-get install libc6-dev-amd64 lib64gcc1
</pre>

To get the bleeding edge we'll need access to the SVN, Mercurial and Bazaar repositories, and for this we need the correct tools:

<pre>
sudo apt-get install subversion mercurial bzr
</pre>

Not necessary, but useful if you want to move to the next level and build packages for distribution (list is incomplete):

<pre>
sudo apt-get install subversion-tools
</pre>

== Building Enblend ==

Get the dependencies. If you are working with large images (300 megapixels and up), you should have a libtiff-devel compiled with large file support and libstdc++6.

<pre>sudo apt-get install pkg-config libtiff4-dev libboost-graph-dev libboost-thread-dev \
liblcms1-dev libglew1.5-dev libplot-dev libglut3-dev libopenexr-dev libxi-dev libxmu-dev
</pre>

For Ubuntu systems prior to 8.10, you will also need

<pre>sudo apt-get install libopenexr2ldbl
</pre>

Once all dependencies are in place, get the code. The official repository has migrated from CVS to Mercurial:

<pre>
hg clone http://enblend.hg.sourceforge.net:8000/hgroot/enblend/enblend enblend
cd enblend
</pre>

We are then ready to compile. The CXXFLAGS <tt>--param inline-unit-growth=60</tt> is a workaround for x86_64 systems, Feb 2009. If you have an SMP machine and you're building a recent version, <tt>--disable-image-cache</tt> and <tt>--enable-openmp</tt> will speed up enblend/enfuse massively but may cause segmentation faults; in that case you will be better off with <tt>--enable-image-cache</tt> and <tt>--disable-openmp.</tt> <tt>-march=native</tt> is also beneficial and -O2 is better than -O3.

<pre>
make --makefile=Makefile.scm
CXXFLAGS="--param inline-unit-growth=60 -march=native -O2" ./configure --disable-image-cache --enable-openmp
make
</pre>

The second make step can be very long and memory consuming. Make sure you have enough swap space, and go get a healthy snack while the computer is compiling.

If you encounter problems at any of these stages, please report back to the hugin-ptx mailing list. Report what command in the sequence you were executing, what machine/operating system, the revision checked out from CVS, and all other relevant information.

You are then ready to install with
<pre>sudo make install</pre>

== Building Libpano13 ==
libpano13 is the new version of the PanoTools libraries. This is a necessary component for hugin, and we need to build it first.
To build libpano13 we need some libraries and particularly their <code>dev</code> package:
<pre>sudo apt-get install zlib1g zlib1g-dev libpng12-dev libjpeg62-dev libtiff4-dev</pre>

On older distributions, zlib1g and zlib1g-dev may not be found. In that case, the same library may be available with the names lib64z1 and lib64z1-dev.

We then need to download the source code from SVN:
<pre>
svn co https://panotools.svn.sourceforge.net/svnroot/panotools/trunk/libpano libpano13
cd libpano13
</pre>

In the future there is no need to get the whole source again. Just issue the following commands to bring your source up to date:
<pre>
cd libpano13
svn up
</pre>

Now start the building process:
<pre>
./bootstrap
</pre>

If any libraries are missing, the script will complain (or at least, let you know that some library hasn't been found). In that case you probably need to install the library. To find in what package is that library, a general rule is to run the command <code>apt-cache search ''missingfile''</code>, find the relevant library and install both the library and the related <code>-dev</code> package.
Run the <code>./configure</code> script and repeat this process until you have met all the dependencies.
Then we are ready to launch the make process with
<pre>make</pre>

If the library successfully compiles, you have to install it with
<pre>sudo make install
sudo ldconfig</pre>
The last part is for the OS to be aware of the new library (that has been installed in <code>/usr/local/lib</code>).
We can now go back up one folder level and get ready for hugin.
<pre>cd ..</pre>

== Building Hugin ==

=== Dependencies ===

First we need to activate the <code>universe</code> repository (in adept package manager, or by editing the /etc/apt/sources.lst file for example) and get the dependencies:
<pre>
sudo apt-get install cmake libopenexr-dev libboost-dev boost-build libboost-thread-dev libboost-graph-dev \
gettext libwxgtk2.8-dev libexiv2-dev libimage-exiftool-perl libglew-dev liblapack-dev
</pre>

=== Fetch the Source Code from SVN ===

Next we download Hugin from SVN. But which Hugin? There are many [http://svnbook.red-bean.com/en/1.1/ch04.html#svn-ch-4-sect-1 branches] in SVN. Also SVN keeps track of every single change (revision) in time, so we can download a branch in its state at a specific point in time. For example <code>-r 4008 https://hugin.svn.sourceforge.net/svnroot/hugin/hugin/trunk/</code> will download the trunk branch at the point in time when revision [http://hugin.svn.sourceforge.net/viewvc/hugin?view=rev&revision=4008 4008] was committed, which happens to be Tue Jul 7 22:07:54 2009 UTC. It also happens to be the same as the 0.8.0 release. For a list of branches and revisions that build well, refer to these [http://wiki.panotools.org/Development_of_Open_Source_tools#Specific_revisions lists]. There is no guarantee that a particular branch and/or revision builds and/or performs as expected.

<pre>
svn co -r 4061 https://hugin.svn.sourceforge.net/svnroot/hugin/hugin/tags/hugin-2009.07.1/ hugin
</pre>

If you know what you are doing, you can replace /hugin-2009.07.1/ with another branch; and you can omit the -r and get the last revision of that branch.

In the future there is no need to get the whole source again. Just issue the following commands to bring your source up to date:
<pre>
cd hugin
svn up
</pre>

=== Set the Build Environment ===

Next we set up the build environment using cmake.

If you compiled and installed libpano to a non standard location set the variables CMAKE_INCLUDE_PATH and CMAKE_LIBRARY_PATH to point to your install location's include and lib directories.

If you are building for distribution, you want to set CMAKE_INSTALL_PREFIX=/usr

<pre>
mkdir hugin-build
cd hugin-build
cmake ../hugin -DENABLE_LAPACK=YES -DCPACK_BINARY_DEB:BOOL=ON -DCPACK_BINARY_NSIS:BOOL=OFF \
-DCPACK_BINARY_RPM:BOOL=OFF -DCPACK_BINARY_STGZ:BOOL=OFF -DCPACK_BINARY_TBZ2:BOOL=OFF \
-DCPACK_BINARY_TGZ:BOOL=OFF -DCPACK_BINARY_TZ:BOOL=OFF
</pre>

=== Build and Install ===

Finally, we use make to build the code and package it, and dpkg to install it. Look for the version number in the .deb file created and edit the lines below accordingly:

<pre>
make package
ls *.deb
sudo dpkg -i hugin-0000.00.0-Linux.deb
</pre>

'''Important:''' the package does not track dependencies yet, so it likely to fail on machines others than yours.

Reference: [http://theseblog.free.fr/2007/10/building-hugin-in-ubuntu-feisty-fawn.php]

== Autopano-sift-C ==

Pre-Requisites:
<pre>
sudo apt-get install libxml2-dev
</pre>

To build
<pre>
svn co https://hugin.svn.sourceforge.net/svnroot/hugin/autopano-sift-C/trunk/ autopano-sift-C
cd autopano-sift-C
cmake -DCMAKE_INSTALL_PREFIX=/usr/local .
make
sudo make install
</pre>

== Match-n-shift ==

Match-n-shift is yet an other Autopano-SIFT replacement. It comes in a bundle with pto file manipulation perl libraries and a rich selection of other tools that use nona, enblend, ImageMagick among other things. To use match-n-shift, you need to install at least the [http://search.cpan.org/dist/Panotools-Script/ Panotools::Script] library and some other perl modules. It requires:

* Image::Size 2.9
* Storable 2.0
* Image::ExifTool 6

Chances are that you do not need to update Storable which is a standard perl module. To check the version of installed versions of these modules, write these lines to the command prompt:

perl -MStorable -le 'print Storable->VERSION;'
perl -MImage::Size -le 'print Image::Size->VERSION;'
perl -MImage::ExifTool -le 'print Image::ExifTool->VERSION;'

There are various ways to install or upgrade these modules. Ubuntu has binary packages for many perl modules, you can skip the CPAN installation below and type:

sudo apt-get install libimage-size-perl libimage-exiftool-perl

Alternatively, perl is an interpreted language and these modules are pure perl, so installing from source is an easy thing.

The best place to install perl modules is directly from a CPAN archive. CPAN is short for Comprehensive Perl Archive Network. The program to interact with CPAN comes with all perl installations. Start it by running:

sudo cpan

If this is your first time running the program you will be asked a number of questions (you can safely accept the suggested values). Last question lets you select a number of CPAN mirrors nearest to you.

When all is done, you can enter the install commands after the 'cpan>' prompt:

install Image::Size Storable Image::ExifTool

Answer 'y' to any question of dependencies and wait for install to complete. 'exit' leaves the cpan shell.

Next, you need to retrieve and install the Panotools-Script collection
of perl libraries (Panotools::Script) and programs that use them -
including match-n-shift:

svn co https://panotools.svn.sourceforge.net/svnroot/panotools/trunk/Panotools-Script Panotools-Script
cd Panotools-Script
perl Makefile.PL
make
make test
sudo make install

Just to confuse you, you can also ignore everything above and just install Panotools::Script and all its dependencies from CPAN. From command line, type:

sudo cpan Panotools::Script

You can run match-n-shift from command line using the same parameters as autopano-c-complete.sh or you can modify hugin to run it for you:

* start Hugin
* navigate the menu File to Preferences
* In the Preferences window, open the Autopano tab
* Select Autopano -> Autopano-SIFT
* tick the checkbox for Use alternative Autopano-SIFT program
* enter the full path to match-n-shift (/usr/local/bin/match-n-shift) in the Autopano-SIFT field
* enter the following string in the Arguments field:
-f %f -v %v -c -p %p -o %o %i

== MatchPoint ==

MatchPoint is a next generation CP generator. The result of a GSoC2007 project, it is still very experimental. Experience reports needed. Read more [http://groups.google.com/group/hugin-ptx/browse_thread/thread/cba2b2ce94dd9054 here]

Matchpoint is now located inside the main hugin source tree, no need to checkout https://hugin.svn.sourceforge.net/svnroot/hugin/gsoc07_featuredetection anymore. It is compiled together with hugin, but not installed by default.

* copy the MatchPoint executable into /usr/local/bin manually
<pre>
sudo cp src/matchpoint/matchpoint /usr/local/bin/
</pre>
* edit /usr/local/bin/autopano-c-complete.sh (do it with sudo to have the necessary permission)
** line 79: replace the .key.gz extension with .key (not sure if matchpoint supports compression)
** lines 83 and 88: replace '''generatekeys "$arg" $FILENAME $SIZE''' with '''matchpoint "$arg" $FILENAME''' (not sure if the size option or any other options of the original generatekeys are applicable)

== Pan-o-matic ==

Yet another control point generator [http://aorlinsk2.free.fr/panomatic/?p=home Home Page]

<pre>sudo apt-get install libboost-dev</pre>

Download [http://aorlinsk2.free.fr/panomatic/download.php?d=7&v=0.9.4 Panomatic 0.9.4 bz2]

<pre>
tar xvfj panomatic-0.9.4-src.tar.bz2
cd panomatic-0.9.4
./configure
make
sudo make install
</pre>

To use Pano-o-matic, open Hugin

* In File > Preferences > Autopano :
* Select Autopano-SIFT
* Check "Use alternative autopaon-SIFT program"
* Choose the path to the binary ( /usr/local/bin )
* In Arguments, put : -o %o %i

== Exiftool ==

ExifTool is a platform-independent Perl library plus a command-line application for reading, writing and editing meta information in image, audio and video files.

<pre>
sudo apt-get purge libimage-exiftool-perl
</pre>

<pre>
wget http://www.sno.phy.queensu.ca/~phil/exiftool/Image-ExifTool-7.83.tar.gz
tar -xzf Image-ExifTool-7.83.tar.gz
cd Image-ExifTool-7.83
perl Makefile.PL
make test
sudo make install
</pre>

== Panoglview ==

PanoGLView is an OpenGL hardware accelerated interactive immersive viewer for equirectangular images.

Pre-Requisites:
<pre>sudo apt-get install wx-common</pre>

To build
<pre>
svn co https://hugin.svn.sourceforge.net/svnroot/hugin/panoglview/trunk panoglview
cd panoglview
./bootstrap
./configure
make
sudo make install
</pre>

== FreePV ==

Pre-Requisites:
<pre>
sudo apt-get install cmake make pkg-config g++ mozilla-dev freeglut-dev zlib1g-dev libjpeg-dev libxext-dev libxmu-dev \
x11proto-xf86vidmode-dev libxxf86vm-dev libnspr4-dev libxml2-dev libpng12-dev
</pre>
To build
<pre>
svn co https://freepv.svn.sourceforge.net/svnroot/freepv/freepv/trunk/ freepv
cd freepv
cmake .
make
sudo make install
</pre>

== Notes for Packagers ==
* before releasing a tarball, upgrade the Changelog with svn2cl
<pre>
$ svn up
$ svn2cl
$ svn ci
</pre>

[[Category:Software:Hugin]]
[[Category:Software:Platform:Linux]]

Development of Open Source tools

2009-09-08T18:48:59Z

Seb Przd: Add category Hugin tag

== Panorama Related Open Source tools ==

* [[Hugin]]
* [[Enblend]]
* [[Enfuse]]
* [[Panotools]]

== Contribution ==

=== Why contribute? ===

The above tools are free for you (and every other user), because volunteers have contributed their skills and time. They provide immense value to the whole community. They provide value to you, don't they? If they do, please consider contributing something back.

=== How to contribute? ===

Join the [http://groups.google.com/group/hugin-ptx hugin-ptx] mailing list to find out what is going on at the moment and how you can help.

If you don't have time, you are most likely a busy professional. You can donate money to [http://sourceforge.net/project/project_donations.php?group_id=77506 Hugin], [http://sourceforge.net/project/project_donations.php?group_id=123407 Enblend/Enfuse] on their project pages through Sourceforge.

At the time of updating this text (9-Jun-2009) the building process of hugin is robust and there are more and more people mastering it on the different platform. The 0.8.0 release cycle is coming to an end. Beyond that, a few exciting features such as nona-gpu are in line for future releases and we expect that the Google Summer of Code 2009 will add new features as well.

'''Don't be afraid of failures in the building process'''
* You may encounter errors when following the build processes linked below is high. Don't worry such errors will not compromise your computer.
* The failure of the building process is actually your success! Every time you report such a failure, with as much detail as possible to how it came about, you are contributing to the progress toward a stable release.

If you are fluent in other languages than English, you can help translate Hugin. There's a [[Hugin translation guide]] to help you get started or help when you run into translation problems.

== Processes ==

The goal of the new release process is to decouple the development process from the other processes, avoiding artificial slow downs (trunk freezes).

Hugin uses an asynchronous development process based on Subversion, which means that:
* trunk never freezes, and committers can continuously add improvements there
* anybody can branch out a development codeline from trunk to branches/ to implement major changes separately without disrupting the continuous flow.
* once a months, developers are polled as to whether it is worth issuing a release. if there is enough support and one person volunteers as release manager, that person branches out a release codeline from trunk. that release codeline is equivalent to a trunk freeze in traditional synchronous development. only bug fixes and translations should go into that codeline. Tarballs are to be released from release codelines only.

=== Development ===

* if you have a development branch, nothing changes. you can keep working on it as you please.
* if you are working on trunk there is an '''improvement''': no trunk freeze.
* you're encouraged to continue with your usual pace of bug fixing and development.
* to do things perfectly: commit all your changes to trunk; and those that are bugfixes also to the release codeline.
* if you forget about it and commit only to one codeline, do not worry. The release manager takes responsibility to port fixes from trunk to the release codeline or the other way around as the need arises.
* try not to add new features to the release codeline

=== Translation ===

* same as development
* please do not run extract-messages.sh while a release process is going on

=== Debugging ===

Working through [[Hugin Trackers]]

Clearing the bugs in the sourceforge bug tracker is an iterative process critical to the release cycle. Feedback from tester is essential for this process. Please take the time to check if the older bugs apply to a current snapshot, if you like to see a release soon.

We'll be releasing frequent snapshots until a release candidate emerges. This is an iterative process:
# '''Volunteers''' check the release-critical bugs listed in the [http://sourceforge.net/tracker/?group_id=77506&atid=550441&status=1 bug tracker] (sort open bugs by priority) against the most recent [http://panospace.wordpress.com/downloads/ snapshots] (scroll down on that page).
#* Install the latest snapshot.
#* Try to reproduce the bug on your system.
#* If you find that the bug no longer occurs, chances are that it has been fixed. Close it (assuming you have the required access), or simply leave a note that it has been fixed (together with the SVN revision and the system used for testing).
#* If you reproduce the bug, leave a note to confirm that it is still actual. Note the SVN revision and the system used for testing. Post detailed instructions how to reproduce the crash. Provide a test case if you can.
#* Add any comments you have to the ticket in the bug tracker. Let the community know you have tested. The bug-tracker is like a mailing list or forum thread, don't be afraid to post.
#* If you don't want to open an account with Sourceforge, post your observations on the hugin-ptx mailing list. It is possible to post comments to the bug tracker anonymously, but this interrupts the vital flow of feedback between testers and developers. Anonymous bug reports are likely to be discarded.
# The '''developers''' fix the bugs identified in the tracker.
# The '''builders''' build new snapshots including the fixes.

=== Development Codelines ===

It is recommended to work separately on major changes and integrate them in the main codeline when they are ready. The currently open development branches are [http://hugin.svn.sourceforge.net/viewvc/hugin/hugin/branches/ listed] in the repository. If you want to work on a major new feature, ask for SVN write access and open yourself a branch:

<pre>
$ svn cp https://hugin.svn.sourceforge.net/svnroot/hugin/hugin/trunk \
https://hugin.svn.sourceforge.net/svnroot/hugin/hugin/branches/NEW_DEVELOPMENT_BRANCH
</pre>

The branch owners are strongly encouraged to regularly sync their branch with trunk, i.e. merge the changes that have occurred since the last sync (or branching) into their branch.

When development is complete or has reached a milestone, it may be integrated it trunk. Before integrating in trunk it is recommended to:
* merge trunk's changes since the last sync into the branch
* test that the branch builds on the major supported plattforms
* test that the branch does not break existing functionality (unless the break is intended, e.g. when a new functionality replaces an existing one)

When the development branch has fulfilled its purpose; is supreceded or has been abandoned, move it to the obsolete_branches in the repository

<pre>
$ svn mv https://hugin.svn.sourceforge.net/svnroot/hugin/hugin/branches/NEW_DEVELOPMENT_BRANCH \
https://hugin.svn.sourceforge.net/svnroot/hugin/hugin/obsolete_branches/NEW_DEVELOPMENT_BRANCH
</pre>

=== Release ===

Once a month the developers are polled if there is reason to issue a release. If there is enough support for releasing, one developer takes on the role of release manager and undertakes the following steps:

The conditions to declare a release final are:
* the code builds on the major supported platforms (Ubuntu, Fedora, OSX, Windows)
* there is no (known) regression, unless intentional. This means: what worked with the previous release should work with the current one.

The next Hugin is likely to be released when these [http://sourceforge.net/search/index.php?group_id=77506&search_summary=1&search_details=1&type_of_search=artifact&group_artifact_id%5b%5d=550441&status_id%5b%5d=1&priority%5b%5d=9&form_submit=Search bugs] will have been fixed.

==== Branching Out For Release ====

1. [[Hugin_translation_guide#Developer_info|Identify]] and add the new strings for translation.

2. Branch out a new release-codeline (replace 2009.2 below with the appropriate version number. 2009 stands for the current year and 2 stands for the next even number in sequence, starting with 0 if the year has changed and this is the first release of the year).

<pre>
$ svn cp https://hugin.svn.sourceforge.net/svnroot/hugin/hugin/trunk \
https://hugin.svn.sourceforge.net/svnroot/hugin/hugin/releases/2009.2 \
-m "Branching 2009.2 for release"
</pre>

3. In the new release-codeline bump up the version number, e.g.

3.a. get the source
<pre>
$ svn co https://hugin.svn.sourceforge.net/svnroot/hugin/hugin/releases/2009.2 2009.2
$ cd 2009.2
$ gedit CMakeLists.txt
</pre>

3.b. edit the following lines in the top level CMakeLists.txt file
<pre>
# version
set(V_MAJOR 2009)
set(V_MINOR 2)
set(V_PATCH 0)
</pre>

3.c. edit the Mac version number in mac//Version.xcconfig

3.d. check the changes in
<pre>
$ svn ci
</pre>

4. in trunk bump up to the next odd version number, e.g. 2009.3 in this example.

4.a. get the source
<pre>
$ svn co https://hugin.svn.sourceforge.net/svnroot/hugin/trunk trunk
$ cd trunk
$ gedit CMakeLists.txt
</pre>

4.b. edit the following lines in the top level CMakeLists.txt file
<pre>
# version
set(V_MAJOR 2009)
set(V_MINOR 3)
set(V_PATCH 0)
</pre>

4.c. edit the Mac version number in mac//Version.xcconfig

4.d. check the changes in
<pre>
$ svn ci
</pre>

==== Keeping the Branch in Sync with Trunk ====

Committers have no obligation to help maintaining the release branch. As a release manager, you want to stay on top of the changes in trunk and synchronize them into your branch if relevant. E.g. if change 4312 to trunk is relevant to the release and has not been applied, do the following:

<pre>
$ cd trunk
$ svn up
$ svn diff -r 4311:4312 > 4312.patch
$ mv 4312.patc ../release
$ cd ../release
$ patch -p 0 < 4312.patch
</pre>

then build, test, commit.

==== Release ====

1. Start with a clean checkout

<pre>
$ svn co https://hugin.svn.sourceforge.net/svnroot/hugin/hugin/releases/2009.2 2009.2
$ cd 2009.2
</pre>

2. Update and commit the Changelog - this can be tricky since after the first branching there may already be significant differences between the trunk and the release codeline. What I found works best for me is to keep synchronized the relevant changes in trunk and in the release codeline; to create the Changelog from trunk; to edit out manually those parts of the trunk changelog that are not relevant to the release, and merge the trunk Changelog from the point of the last release to now into the current release.

<pre>
$ cd ../trunk
$ svn up
$ svn2cl
$ cp Changelog ../2009.2/Changelog.trunk
$ gedit Changelog.trunk &
$ gedit Changelog
$ svn ci
</pre>

3. Note down the SVN revision number - the release equivalent in the repository is the releases/2009.2 branch at the revision that you noted down.

4. Extract the relevant Changelog section for Sourceforge, Write a summary for the announcement.

5. Create tarball

<pre>
$ cd ..
$ mkdir hugin-build
$ cd hugin-build
$ cmake ../hugin -DENABLE_LAPACK=YES -DCPACK_BINARY_DEB:BOOL=OFF -DCPACK_BINARY_NSIS:BOOL=OFF \
-DCPACK_BINARY_RPM:BOOL=OFF -DCPACK_BINARY_STGZ:BOOL=OFF -DCPACK_BINARY_TBZ2:BOOL=OFF \
-DCPACK_BINARY_TGZ:BOOL=ON -DCPACK_BINARY_TZ:BOOL=OFF
$ make package_source
</pre>

6. Build an rpm or deb (depending on your distro) from the tarball as a sanity check. Test what you can test.

<pre>
$ tar xvfz hugin-2009.2.0.tar.gz
$ mkdir hugin.build
$ cd hugin.build
$ cmake ../hugin-2009.2.0 -DENABLE_LAPACK=YES -DCPACK_BINARY_DEB:BOOL=ON -DCPACK_BINARY_NSIS:BOOL=OFF \
-DCPACK_BINARY_RPM:BOOL=OFF -DCPACK_BINARY_STGZ:BOOL=OFF -DCPACK_BINARY_TBZ2:BOOL=OFF \
-DCPACK_BINARY_TGZ:BOOL=OFF -DCPACK_BINARY_TZ:BOOL=OFF
$ make package
$ sudo dpkg -i hugin-2009.2.0-Linux.deb
</pre>

7. Rename the tarball. For snapsnots, append _snapshotYYMMDD (replace YYMMDD with Year/Month/Day). For betas, append _betaX with X being an incremental number starting with 1. For release candidates, append _rcX with X being an incremental number starting with 1. Eventually the last candidate will be renamed "final" (by removing the appendix) after a few more tests prove that no further candidate is needed.

8. Determine the tarball's checksum for the announcement notice
<pre>
$ sha1sum hugin-2009.2.0_beta1.tar.gz
</pre>

9. Upload the tarball to sourceforge, you need to be a 'Release tech' to do this.

10. Tag the release. SVNNR is the revision number noted in 3. TAG_NAME is the same name as given to the tarball, e.g. hugin-2009.2.0_YYMMDD for snapshots and hugin-2009.2.0_rcN for release candidates.

<pre>
$ svn cp -r SVNNR https://hugin.svn.sourceforge.net/svnroot/hugin/hugin/releases/2009.2 \
https://hugin.svn.sourceforge.net/svnroot/hugin/hugin/tags/TAG_NAME \
-m "Branching 2009.2 for snapshot"
</pre>

11. Paste the announcement into the Sourceforge news system. You need to be a 'News Editor' to do this. Only for the final release, tick the "Submit my news to the Slashdot.org Firehose" box.

12. Mail the announcement to hugin-ptx. Only for the final release, mail it also to other relevant channels such as PanotoolsNG and QuickTimeVR.

13. Wait for feedback and fixes. Volunteers may fix critical bugs. Test that the codeline builds on the major supported platforms. Test that no major functionality is broken. Repeats steps 1-11 as often as necessary.

14. Once the codeline is final, port relevant "polish" commits that have not been ported yet to trunk (similar to merging a development codeline).

15. later on if patches are required, apply them to /releases/2009.2, bump up V_PATCH, tag, and release.

=== Testing ===

* There is only so much testing that can be done with our limited resources.
* Final releases are expected to build and work on the major supported platforms, however it is possible that a bug slips in due to lack of resources / systematic testing
* We may issue patch releases in case of security issues or other major issues reported after final release.

=== Distribution ===

* '''unchanged''': the Hugin project releases source code that is tested to build on the main supported platforms: Fedora, Ubuntu, Windows, OSX. It works on the developers machines. YMMV.
* Building and distributing binaries is left to the users communities. Once there are binaries of appropriate quality level for platforms that do not have a package manager (Windows and OSX) we add them as a courtesy to the SF archive - as usual "WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE." See the GNU General Public License for more details.

== Download Test Build ==

If you want to contribute testing but you don't want to go through the hassle of building the code, you can find the latest installer download for Windows and OSX [http://panospace.wordpress.com/downloads/ here].

== Build your Own Test Builds ==

If you are ready to go through the building process, here are the instructions.

{| style="margin: 1em auto 1em 1em;background:#FFFF99;color:#FF0000;text-align:left;border: solid #FF3300;"
|-valign="top"
! '''IMPORTANT:'''
! These builds are for your computer. If you decide to share them with others, be aware that you are subject to the GPL, and that the general public may need guidance regarding what you distribute. Read the information in the packaging and distribution section [[Development_of_Open_Source_tools#Packaging_and_Distribution | below]]. If you are unsure, ask on the hugin-ptx mailing list for advice before posting a file for download.
|}

=== Goal ===

an infrastructure for on-demand build and distribution of usable test-binaries for the most popular platforms. These builds are meant to enable users to test the newest features and report bugs. Ideally, on Pablo's demand all those who have a build chain will run it against the newest source code to produce the builds.

=== Process ===

# Experienced users will build the most current hugin and helpers (libpano, enblend, autopano, etc.) for the target platform of their choice, with support from coders.
# The build process will be documented for each of the supported platform.
# Users willing to spend some time learning how to build will reproduce the documented process.
# Power users will script and automate the building process.
# Users with packaging skills will package the builds for distribution (installers).
# The produced binaries/installers will be made available on the web.

=== Specific revisions ===

When building from the repository, some revisions have bugs. This process is meant to build the latest revision so that if the latest revision has bugs these can be identified and corrected. However sometimes these bugs can be more critical than other times. If you need a more or less working version of hugin, try applying the process to one of the following revisions. To stay on top of all changes, consult the revision logs.

==== hugin ====

{| style="margin: 1em auto 1em 1em;background:#FFFFDD;text-align:left;border-top: thin dotted #333333;"

|-valign="top"
! width="80" |
Revision
! width="300" |
Branch
! width="500" |
Comments

|-valign="top"
! style="border-top: thin dotted #333333;" |
4315
! style="border-top: thin dotted #333333;" |
/hugin/releases/2009.2
| style="border-top: thin dotted #333333;" |
2009.2_beta2

|-valign="top"
! style="border-top: thin dotted #333333;" |
4008
! style="border-top: thin dotted #333333;" |
/hugin/trunk
| style="border-top: thin dotted #333333;" |
official 0.8.0 release = RC5

|-valign="top"
! style="border-top: thin dotted #333333;" |
3465
! style="border-top: thin dotted #333333;" |
/hugin/trunk
| style="border-top: thin dotted #333333;" |
official 0.7.0 release
|}

* [[older hugin revision notes]]
* [http://hugin.svn.sourceforge.net/viewvc/hugin/hugin/trunk/?view=log revision log]

==== libpano ====

{| style="margin: 1em auto 1em 1em;background:#FFFFDD;text-align:left;border-top: thin dotted #333333;"

|-valign="top"
! width="80" |
Revision
! width="300" |
Branch
! width="500" |
Comments

|-valign="top"
! style="border-top: thin dotted #333333;" |
1036
| style="border-top: thin dotted #333333;" |
trunk
| style="border-top: thin dotted #333333;" |
tentative fix for the error introduced in 1017

|-valign="top"
! style="border-top: thin dotted #333333;" |
1017 +
| style="border-top: thin dotted #333333;" |
trunk
| style="border-top: thin dotted #333333;" |
builds but has a fatal error [http://groups.google.com/group/hugin-ptx/msg/d7beab28db615445]

|-valign="top"
! style="border-top: thin dotted #333333;" |
1016
| style="border-top: thin dotted #333333;" |
trunk
| style="border-top: thin dotted #333333;" |
builds and works but messes up locale

|-valign="top"
|}

* [[older libpano revision notes]]
* [http://panotools.svn.sourceforge.net/viewvc/panotools?view=log revision log]

==== enblend-enfuse ====

Use of CVS has been discontinued in favor of Mercurial. The information below is stale.

{| style="margin: 1em auto 1em 1em;background:#FFFFDD;text-align:left;border-top: thin dotted #333333;"
|-valign="top"
! width="100" |
Revision
! width="500" |
Comments
|-valign="top"
! style="border-top: thin dotted #333333;" |
2009-06-09
| style="border-top: thin dotted #333333;" |
builds on ubuntu 9.04 x86. Note: for experimental use there is a temporary fork by Christoph Spiel in Launchpad.
|-valign="top"
! style="border-top: thin dotted #333333;" |
2008-02-07
| style="border-top: thin dotted #333333;" |
builds on ubuntu 7.10 AMD64, OSX (used for snapshot package), Windows (used for first snapshot installer)
|-valign="top"
|}

* [[older enblend revision notes]]
* [http://enblend.hg.sourceforge.net/hgweb/enblend/enblend/log revision log]

=== Supported Platforms ===

* If you don't find your preferred platform listed below '''and''' you are willing to contribute your time and skills to build hugin on it, feel free to add it to the table. We will accommodate any well supported platform in the regular release process.
* The persons marked in bold in the '''credits''' are known to have currently access to a build chain on the selected platform and can possibly produce a snapshot on request, usually within a few days. If you have contributed to the build system, feel free to add yourself here.
* '''Redundancy is good'''. If you have access to one of the listed platforms, please try to run the documented process below and report success to hugin-ptx. If you think you could do this on a regular basis, enter yourself in the list, in bold.

{| style="margin: 1em auto 1em 1em;background:#FFFFDD;text-align:left;border-top: thin dotted #333333;"
|-valign="top"
! width="90" |
Platform
! width="130" |
Supported Versions
! width="60" |
Status
! width="220" |
Process
! width="400" |
Credits

|-valign="top"
! style="border-top: thin dotted #333333;" |
ubuntu
| style="border-top: thin dotted #333333;" |
32bit/64bit<br>8.04 8.10 9.04
| style="border-top: thin dotted #333333;" |
tbd
| style="border-top: thin dotted #333333;" |
[[Hugin Compiling Ubuntu | OK]]
| style="border-top: thin dotted #333333;" |
* Sébastien Perez-Duarte
* Yuval Levy
* Régis B.
* Kornel Benko

|-valign="top"
! style="border-top: thin dotted #333333;" |
Fedora
| style="border-top: thin dotted #333333;" |
32bit/64bit/ppc/ppc64<br>F-8 F-9
| style="border-top: thin dotted #333333;" |
tbd
| style="border-top: thin dotted #333333;" |
[[Hugin Compiling Fedora | tbd]]
| style="border-top: thin dotted #333333;" |
* Bruno Postle

|-valign="top"
! style="border-top: thin dotted #333333;" |
OSX
| style="border-top: thin dotted #333333;" |
IntelMac/PowerPC<br>10.3 10.4 10.5
| style="border-top: thin dotted #333333;" |
tbd
| style="border-top: thin dotted #333333;" |
* [[Hugin Compiling OSX | "roll your own" draft]]
* [[Build_a_MacOSX_Universal_Hugin_bundle_with_Xcode | universal bundle for distribution draft]]
| style="border-top: thin dotted #333333;" |
* Ippei Ukai
* JD Smith
* Daniel M. German
* Peter A. Crowley
* David Haberthür
* John Riley
* Roger Howard
* Harry van der Wolf
* Charlie Reiman

|-valign="top"
! style="border-top: thin dotted #333333;" |
Windows
| style="border-top: thin dotted #333333;" |
32bit/64bit<br>XP/Vista<br>(64bit officially supported only after 0.8.0)
| style="border-top: thin dotted #333333;" |
tbd
| style="border-top: thin dotted #333333;" |
*[[Build Hugin for Windows with SDK | OK, SDK based]] 32bit only.
*[[Hugin Compiling Windows | draft, from scratch]]
*[[Hugin_SDK_(MSVC_2008) | build the SDK]] 32bit & 64bit
*[[Hugin_SDK_(MSVC_2008)_Patches | SDK 64bit patches]]
| style="border-top: thin dotted #333333;" |
* Tom Sharpless
* John Navas
* Jean-Marc Paratte
* Yili Zhao
* Yuval Levy
* Guido Kohlmeyer
* Ad Huikeshoven (build automation)
* Ryan Sleevi (64 bit)

|-valign="top"
! style="border-top: thin dotted #333333;" |
OpenSuse
| style="border-top: thin dotted #333333;" |
32bit/64bit<br>10.2 10.3
| style="border-top: thin dotted #333333;" |
tbd
| style="border-top: thin dotted #333333;" |
[[Hugin Compiling OpenSuse | tbd]]
| style="border-top: thin dotted #333333;" |
* Kornel Benko (10.3)
* Peter Suetterlin (10.2)
* Stephan Hegel (10.3 x86_64)

|-valign="top"
! style="border-top: thin dotted #333333;" |
FreeBSD
| style="border-top: thin dotted #333333;" |
32bit/64bit<br>6.3 7.0
| style="border-top: thin dotted #333333;" |
n/a
| style="border-top: thin dotted #333333;" |
[[Hugin Compiling FreeBSD | OK]]
| style="border-top: thin dotted #333333;" |
* Vasil Dimov (6.2/i386)
* Vasil Dimov (7.0/amd64)

|-valign="top"
! style="border-top: thin dotted #333333;" |
Gentoo Linux
| style="border-top: thin dotted #333333;" |
32bit
| style="border-top: thin dotted #333333;" |
tbd
| style="border-top: thin dotted #333333;" |
[[Hugin_Compiling_Gentoo | OK]]
| style="border-top: thin dotted #333333;" |
* Thomas Pani

|-valign="top"
! style="border-top: thin dotted #333333;" |
all platforms
! style="border-top: thin dotted #333333;" colspan="4" |
a big thank you to '''Pablo d'Angelo''' for supporting all of those building efforts.
|-valign="top"
|}

=== Stati ===

'''Build Chain'''
* tbd: looking for responsible
* OK: mostly automated build process ready on request
* unavailable: temporarily unavailable (e.g. responsible on holiday)
* HW-broken: the hardware is temporarily unavailable
* SW-broken: temporarily dysfunctional, working on a fix
* broken: nobody is working on a fix
* unsupported: has been dropped for lack of support

'''Process'''
* tbd: status unknown
* auto: work as documented and has been automated to a reasonable extent
* OK: works as documented, could use automation / scripting
* draft: documented, needs validation / testing / cleaning
* incomplete: parts are missing (e.g. enblend, libpano)
* outdated: worked in the past but needs an update
* obsolete: nobody has the time to update

== Packaging and Distribution ==

Instructions for packaging binaries for distribution will follow. Some important points:

=== Snapshots ===
* comply with the GPL
** join a text of the GPL in the distribution
** give access to the source code
** credit the authors
* label clearly the snapshot as such, with a reference to the build date and/or the SVN revision number
* edit the text / readme files that come with the snapshot
** indicate clearly that it is unstable, experimental software
** indicate where to find the latest version
** indicate that the advertised features might or might not work

=== Release ===
* comply with the GPL
** join a text of the GPL in the distribution
** give access to the source code
** credit the authors

== Feedback ==

When running through the building process documented above chances are that something goes wrong. While it is disappointing when the process ends in a flurry of cryptic error messages it is not harmful. This is the nature of software development and you are now part of it. There is still a lot of value in your experience and you can help improve the process and get closer to the hoped for software package. Please don't be ashamed that it did not work. This happens even to the most expert coders. Give the developers feedback on the hugin-ptx mailing list. Only with your feedback they can know that something goes wrong, and a well crafted feedback helps them find out quickly what went wrong and devise a solution. Be a part of the solution, not a part of the problem!

To give good feedback, note down carefully all of this information while you are going through the instructions.
# details about your computer. CPU, operating system, other particularities
# the revision number of the code checked out with SVN (which appears at the end of the checkout process) or with CVS. Or, if you don't find a revision number, the date and time when you checked out the code.
# the last step / command you entered into the command line
# a copy of the last few lines displayed, from where you think the error messages started. Don't worry if you copy a couple of lines too many, it is better to give more lines than less lines.

Even the standard feedback is good feedback. For those wishing to dig deeper, you can try
* to use "make VERBOSE=1" when building hugin.
* to do a debug build "cmake -DCMAKE_BUILD_TYPE=DEBUG" and use oprofile for profiling.

[[Category:Community:Project]] [[Category:Software:Hugin]]

Enblend reference manual

2009-03-04T09:58:36Z

Seb Przd: /* {{NotTOC|2.2 }}Extended Options */ --depth not available in many versions

{{anchor|Top}} {{anchor|SEC_Top}}

This manual is for [[Enblend]] (version 3.2-cvs, Thu Sep 25 07:35:10 UTC 2008). It was written by Dr. Christoph L. Spiel, converted partly from the HTML version and corrected using the PDF version both found on http://panorama.dyndns.org/EandE-documentation/

{{anchor|Overview}} {{anchor|SEC1}}

=={{NotTOC|1. }}Overview==

Enblend overlays multiple TIFF images using the Burt-Adelson multiresolution spline algorithm.{{anchor|DOCF1}} [[#FOOT1|(1)]] This technique tries to make the seams between the input images invisible. The basic idea is that image features should be blended across a transition zone proportional in size to the spatial frequency of the features. For example, objects like trees and windowpanes have rapid changes in color. By blending these features in a narrow zone, you will not be able to see the seam because the eye already expects to see color changes at the edge of these features. Clouds and sky are the opposite. These features have to be blended across a wide transition zone because any sudden change in color will be immediately noticeable.

Enblend expects each input file to have an alpha channel. The alpha channel should indicate the region of the file that has valid image data. Enblend compares the alpha regions in the input files to find the areas where images overlap. Alpha channels can be used to indicate to Enblend that certain portions of an input image should not contribute to the final image.

{{anchor|IDX1}} {{anchor|IDX2}}

Enblend does ''not'' align images. Use a tool as <code>hugin</code> or PanoTools to do this. The TIFF files produced by these programs are exactly what Enblend is designed to work with. Sometimes these GUIs allow you to select feathering for the edges of your images. This treatment is detrimental to Enblend. Turn off feathering by deselecting it or setting the feather width to zero.

Enblend blends the images in the order they are specified on the command line. You should order your images according to the way that they overlap, for example from left-to-right across the panorama. If you are making a multi-row panorama, we recommend blending each horizontal row individually, and then running Enblend a last time to blend all of the rows together vertically.

Find out more about Enblend on its [http://enblend.sourceforge.net/ webpage].

----

{{anchor|Invocation}} {{anchor|SEC2}}

=={{NotTOC|2. }}Invocation==

<code>enblend</code> [<var>OPTIONS</var>] <code>-o</code> <var>OUTPUT-FILE</var> <var>INPUT-FILES</var><small class="enddots">....</small>

Assemble the sequence of images <var>INPUT-FILES</var><small class="enddots">....</small> into <var>OUTPUT-FILE</var>.

{| class="menu"
| align="left" |
[[#SEC3|{{NotTOC|2.1 }}Common Options]]
| align="left" | General options
|-
| align="left" |
[[#SEC4|{{NotTOC|2.2 }}Extended Options]]
| align="left" | Memory and GPU control
|-
| align="left" |
[[#SEC5|{{NotTOC|2.3 }}Mask Generation Options]]
| align="left" | Mask generation control
|}

----

{{anchor|Common-Options}} {{anchor|SEC3}}

==={{NotTOC|2.1 }}Common Options===

Common options control some overall features of Enblend.

; <code>-a</code>
: {{anchor|IDX3}} Pre-assemble non-overlapping images before each blending iteration.This overrides the default behavior which is to blend the images sequentially in the order given on the command line. Enblend will use fewer blending iterations, but it will do more work in each iteration.
; <code>--compression=<var>COMPRESSION</var></code>
: {{anchor|IDX4}} Write a compressed output file.Depending on the output file format Enblend accepts different values for <var>COMPRESSION</var>.
:; JPEG
:: <var>COMPRESSION</var> is a JPEG quality level ranging from 0–100.
:; TIFF
:: <var>COMPRESSION</var> is one of the keywords:
::; ‘NONE’
::: Do not compress. This is the default.
::; ‘DEFLATE’
::: {{anchor|IDX5}} {{anchor|IDX6}} Use the Deflate compression scheme also called ZIP-in-TIFF. Deflate is a lossless data compression algorithm that uses a combination of the LZ77 algorithm and Huffman coding.
::; ‘LZW’
::: {{anchor|IDX7}} {{anchor|IDX8}} Use Lempel-Ziv-Welch (LZW) adaptive compression scheme. LZW compression is lossless.
::; ‘PACKBITS’
::: {{anchor|IDX9}} {{anchor|IDX10}} Use PackBits compression scheme. PackBits is particular variant of run-length compression. It is lossless.
:; Any other format
:: Other formats like the PNG do not accept a <var>COMPRESSION</var> setting.
; <code>-h</code>
; <code>--help</code>
: {{anchor|IDX11}} {{anchor|IDX12}} Print information on the available options and exit.
; <code>-l <var>LEVELS</var></code>
: {{anchor|IDX13}} Use exactly this many <var>LEVELS</var> for pyramid blending.This trades off quality of results for shorter execution time and lower memory usage. The default is to use as many levels as is possible given the size of the overlap regions. Enblend may still use a smaller number of levels if the geometry of the images demands.
; <code>-o <var>OUTPUT-FILE</var></code>
: {{anchor|IDX14}} Required option that specifies the name of the <var>OUTPUT-FILE</var>.
; <code>-v</code>
; <code>--verbose</code>
: {{anchor|IDX15}} {{anchor|IDX16}} Increase the verbosity of progress reporting. Giving one or more ‘-v’ options will make Enblend more verbose.
; <code>-V</code>
; <code>--version</code>
: {{anchor|IDX17}} {{anchor|IDX18}} Output information on the Enblend version and some configuration details like extra features that have been compiled in.
; <code>-w</code>
: {{anchor|IDX19}} Blend around the ± 180° boundary. Useful for full 360° panoramas. Version 3.2-cvs of Enblend, the one described here, does not blend neither zenith nor or nadir, so you may still see some seams in these areas.
; <code>-x</code>
: {{anchor|IDX20}} Checkpoint partial results to the output file after each blending step.
; <code>-z</code>
: {{anchor|IDX21}} This option has been deprecated. It is kept for backward compatability with older scripts. Use ‘--compression=LZW’ instead.

----

{{anchor|Extended-Options}} {{anchor|SEC4}}

==={{NotTOC|2.2 }}Extended Options===

Extended options control the image cache, the color model, and the cropping of the output image.

; <code>-b <var>BLOCKSIZE</var></code>
: {{anchor|IDX22}} {{anchor|IDX23}} Set the <var>BLOCKSIZE</var> in kilobytes (KB) of Enblend's image cache.This is the amount of data that Enblend will move to and from the disk in one go. The default is 2048KB, which should be ok for most systems.
; <code>-c</code>
: {{anchor|IDX24}} {{anchor|IDX25}} {{anchor|IDX26}} Use the CIECAM02 color appearance model for blending colors.The input files should have embedded ICC profiles if this option is specified. If no ICC profile is present, Enblend will assume that the image uses the sRGB color space. The difference between this option and Enblend's default color blending algorithm is very slight and will be only noticeable when areas of different primary colors are blended together.
; <code>-d</code>
; <code>--depth=<var>DEPTH</var></code>
: {{anchor|IDX27}} {{anchor|IDX28}} {{anchor|IDX29}} Force the number of bits per channel and the numeric format of the output image. All <var>DEPTH</var> specifications are valid in lowercase as well as uppercase letters. This option is only available in specific builds of Enblend. For integer format use
:; <code>8</code>, <code>uint8</code>
:: Unsigned 8 bit; range: 0..255
:; <code>int16</code>
:: Signed 16 bit; range: -32768..32767
:; <code>16</code>, <code>uint16</code>
:: Unsigned 16 bit; range: 0..65536
:; <code>int32</code>
:: Signed 32 bit; range: -2147483648..2147483647
:; <code>32</code>, <code>uint32</code>
:: Unsigned 32 bit; range: 0..4294967295 For floating-point format use
:; <code>r32</code>, <code>real32</code>, <code>float</code>
:: IEEE754 single precision floating-point, 32 bits wide, 24 bit significant
::* - Minimal normalized value: 1.2 × 10<sup>-38</sup>
::* - Epsilon: 1.2 × 10<sup>-7</sup>
::* - Maximal finite value: 3.4 × 10<sup>38</sup>
:; <code>r64</code>, <code>real64</code>, <code>double</code>
:: IEEE754 double precision floating-point, 64 bits wide, 53 bit significant
::* - Minimal normalized value: 2.2 × 10<sup>-308</sup>
::* - Epsilon: 2.2 × 10<sup>-16</sup>
::* - Maximal finite value: 1.8 × 10<sup>308</sup> If the requested <var>DEPTH</var> is not supported by the output file format, Enblend warns and chooses the <var>DEPTH</var> that matches best.
; <code>-g</code>
: {{anchor|IDX30}} {{anchor|IDX31}} {{anchor|IDX32}} {{anchor|IDX33}} Gimp (before version 2.0) and Cinepaint (see section [[#SEC10|Helpful Additional Programs]]) exhibit unusual behavior when loading images with unassociated alpha channels. Use option ‘-g’ to work around this problem. With this flag Enblend creates the output image with the associated alpha tag set, even though the image is really unassociated alpha.
; <code>--gpu</code>
: {{anchor|IDX34}} Use the graphics card to accelerate some computations.This is an experimental feature that may not work on all systems. In this version of Enblend, 3.2-cvs, only mask optimization strategy 1 benefits from this option.
; <code>-f <var>WIDTH</var>x<var>HEIGHT</var></code>
; <code>-f <var>WIDTH</var>x<var>HEIGHT</var>+x<var>XOFFSET</var>+y<var>YOFFSET</var></code>
: {{anchor|IDX35}} {{anchor|IDX36}} Set the size of the output image manually to <var>WIDTH</var>× <var>HEIGHT</var>. Optionally specify the <var>X-OFFSET</var> and <var>Y-OFFSET</var>, too. {{anchor|IDX37}} {{anchor|IDX38}} This option is useful when the input images are cropped TIFF files, such as those produced by <code>nona</code>. The stitcher <code>nona</code> is part of Hugin. See section [[#SEC10|Helpful Additional Programs]].
; <code>-m <var>CACHESIZE</var></code>
: {{anchor|IDX39}} {{anchor|IDX40}} Set the <var>CACHESIZE</var> in megabytes (MB) of Enblend's image cache.This is the amount of memory Enblend will use for storing image data before swapping to disk. The default is 1024MB which is good for systems with 3–4gigabytes (GB) of RAM.
; <code>--visualize=<var>IMAGE-FILE</var></code>
: {{anchor|IDX41}} {{anchor|IDX42}} Create an <var>IMAGE-FILE</var> that visualizes the mask optimization process.This shows Enblend's view of the overlap region and how it decided to route the seam line. If you are experiencing artifacts or unexpected output, it may be useful to include this visualization image in your bug report.

----

{{anchor|Mask-Generation-Options}} {{anchor|SEC5}}

==={{NotTOC|2.3 }}Mask Generation Options===

These options control the generation and the usage of masks.

; <code>--coarse-mask</code>
: {{anchor|IDX43}} {{anchor|IDX44}} {{anchor|IDX45}} Use a scaled-down version of the input images to create the seam line. This is the default.
; <code>--fine-mask</code>
: {{anchor|IDX46}} {{anchor|IDX47}} {{anchor|IDX48}} Use the full-size images to create the seam line. This can be slow. Use ‘--fine-mask’ if you have very narrow overlap regions.
; <code>--load-mask=<var>IMAGE-FILE</var></code>
: {{anchor|IDX49}} {{anchor|IDX50}} {{anchor|IDX51}} Instead of generating a mask, use the one in <var>IMAGE-FILE</var>.
; <code>--no-optimize</code>
: {{anchor|IDX52}} {{anchor|IDX53}} {{anchor|IDX54}} Turn off seam line optimization. Combined with ‘--fine-mask’ this will produce the same type of mask as Enblend version 2.5.
; <code>--optimize</code>
: {{anchor|IDX55}} {{anchor|IDX56}} {{anchor|IDX57}} Use a two-strategy approach to route the seam line around mismatches in the overlap region. This is the default.
; <code>--save-mask=<var>IMAGE-FILE</var></code>
: {{anchor|IDX58}} {{anchor|IDX59}} {{anchor|IDX60}} Save the generated mask to <var>IMAGE-FILE</var>.Use this option if you wish to edit the location of the seam line by hand. This will give you a template of the right size that you can edit to make your changes. Later, use ‘--load-mask’ to blend the project with your custom seam line.

----

{{anchor|Understanding-Masks}} {{anchor|SEC6}}

=={{NotTOC|3. }}Understanding Masks==

A ''binary mask'' indicates for every pixel of an image if this pixel must be considered in further processing or ignored. For a ''weight mask'', the value of the mask determines how much the pixel contributes, zero again meaning “no contribution”.

Masks arise in two places: as part of the input files and as separate files, showing the actual pixel weights prior to image blendung or fusion. We shall explore both occurrences in the next sections.

----

{{anchor|SEC7}}

==={{NotTOC|3.1 }}Masks in Input Files===

Each of the input files for Enfuse and Enblend can contain its own mask. Both applications interpret them as binary masks no matter how many bits per image pixel they contain.

{{anchor|IDX61}} {{anchor|IDX62}}

Use ImageMagick's <code>identify</code> or, for TIFF files, <code>tiffinfo</code> to inquire quickly whether a file contains a mask. [[#SEC10|Helpful Additional Programs]] shows where to find these programs on the web.

{|
|
$ identify -format "%f %m %wx%h %r %q-bit" remapped-0000.tif
remapped-0000.tif TIFF 800x533 DirectClassRGBMatte 8-bit
^^^^^ mask
|}

{|
|
$ tiffinfo remapped-0000.tif
TIFF Directory at offset 0x1a398a (1718666)
Subfile Type: (0 = 0x0)
Image Width: 800 Image Length: 533
Resolution: 150, 150 pixels/inch
Position: 0, 0
Bits/Sample: 8
Sample Format: unsigned integer
Compression Scheme: PackBits
Photometric Interpretation: RGB color
Extra Samples: 1<unassoc-alpha> <<<<< mask
Orientation: row 0 top, col 0 lhs
Samples/Pixel: 4 <<<<< R, G, B, and mask
Rows/Strip: 327
Planar Configuration: single image plane
|}

The “Matte” part of the image class and the “Extra Samples” line tell us that the file features a mask. Also, many interactive image manipulation programs show the mask as a separate channel, sometimes called “Alpha”. There, the white (high mask value) parts of the mask enable pixels and black (low mask value) parts suppress them.

The multitude of terms all describing the concept of a mask is confusing.

; Mask
: A mask defines a selection of pixels. A value of zero represents an unselected pixel. The maximum value (“white”) represents a selected pixel and the values between zero and the maximum are partially selected pixels. See [http://gimp-savvy.com/BOOK/index.html$$$$node42.html Gimp-Savy].
; Alpha Channel
: The alpha channel stores the transpacency value for each pixel, typically in the range from zero to one. A value of zero means the pixel is completely transparent, thus does not contribute to the image. A value of one on the other hand means the pixel is completely opaque.
; Matte
: The notion “matte” as used by ImageMagick refers to an inverted alpha channel, more precisely: 1 - alpha. See [http://www.imagemagick.org/Usage/channels/#trans ImageMagick] for further explanations.

Enblend and Enfuse only consider pixels that have an associated mask value different from zero. If an input image does not have an alpha channel, Enblend warns and assumes a mask of all non-zero values, this is, it will use every pixel of the input image for fusion.

Stitchers like <code>nona</code> add a mask to their output images.

Sometimes it is helpful to manually modify a mask before fusion. For example to suppress unwanted objects (insects and cars come into mind) that moved across the scene during the exposures. If the masks of all input images are black at a certain position, the output image will have a hole there.

----

{{anchor|SEC8}}

==={{NotTOC|3.2 }}Weight Mask Files===

...

----

{{anchor|Tuning-Memory-Usage}} {{anchor|SEC9}}

=={{NotTOC|4. }}Tuning Memory Usage==

The default configuration of Enfuse assumes a system with 3–4GB of RAM.

{{anchor|IDX63}}

If Enfuse has been compiled with the C++-preprocessor symbol <code>ENBLEND_CACHE_IMAGES</code> it uses its own image cache, whose size is user configurable with the option ‘-m <var>CACHE-SIZE</var>’ (see section [[#SEC4|Extended Options]]). Furthermore, option ‘-b <var>BUFFER-SIZE</var>’ (see section [[#SEC4|Extended Options]]) allows for fine-tuning the size of a single buffer inside the image cache. Note that <var>CACHE-SIZE</var> is given in megabytes, whereas <var>BUFFER-SIZE</var> is given in kilobytes.

Usually the user lets the operating system take care of the memory management of all processes. However, a user of Enfuse might want to control the balance between the operating systems' Virtual Memory System and Enfuse's image cache for several reasons.

* Paging in or out parts of a process' image runs at kernel level and thus can make user processes appear unresponsive or “jumpy”. The caching mechanism of Enfuse of course runs as a user process, which is why it has less detrimental effects on the system's overall responsiveness.
* Enfuse's image cache has been optimized for accesses to image data. And all algorithms in Enfuse have been carefully arranged to play nice with the image cache. An operating system's cache has no knowledge of these particular memory access patterns.
* The disk access of the operating system to the swap device has been highly optimized. Enfuse on the other hand uses the standard IO-layer which is a slower interface.
* Limiting the amount of image cache prevents Enfuse from eating up most or all RAM, thereby forcing all user applications into the swap device.

The <var>CACHE-SIZE</var> should be set in a way as to reconcile all of the above aspects even for the biggest data sets (this is many images and large images).

Suggested cache- and buffer-sizes for different amounts of available RAM.

<div class="float">{{anchor|tab_003acache_002dsize_002dsettings}}

{| border="1"
! RAM
! ''CACHE-SIZE''
! ''BUFFER-SIZE''
! Comment
|-
! MB
! MB
! KB
|-
| 4096
| 1024
| 2048
| default
|-
| 2048
| 512–1024
| 1024
|-
| 1024
| 256–512
| 256–512
|}

</div>

'''Table 4.1: Suggested cache-size settings '''

----

{{anchor|Helpful-Programs}} {{anchor|SEC10}}

=={{NotTOC|5. }}Helpful Additional Programs==

Several libraries and programs have proven helpful when working with Enfuse and Enblend.

; '''Raw Image Conversion'''

:* {{anchor|IDX64}} {{anchor|IDX65}} [http://www.cybercom.net/~dcoffin/dcraw/ DCRaw] is a universal raw-converter.
:* {{anchor|IDX66}} {{anchor|IDX67}} {{anchor|IDX68}} [http://ufraw.sourceforge.net/ UFRaw], a raw converter based on DCRaw, adds a GUI (<code>ufraw</code>), versatile batch processing (<code>ufraw-batch</code>), and some additional features like, for example, cropping, noise reduction with wavelets, and automatic lens error correction.

; '''Image Alignment and Rendering'''

:* {{anchor|IDX69}} {{anchor|IDX70}} [http://auricle.dyndns.org/ALE/ ALE], David Hilvert's anti-lamenessing engine for the real die-hard command-line users aligns, filters, and renders images.
:* {{anchor|IDX71}} {{anchor|IDX72}} [http://hugin.sourceforge.net/ Hugin] is a GUI that aligns and stitches images. {{anchor|IDX73}} {{anchor|IDX74}} {{anchor|IDX75}} It comes with several command line tools, like <code>nona</code> to stitch panorama images, <code>align_image_stack</code> to align overlapping images for HDR or create focus stacks, and <code>fulla</code> to correct lens errors.
:* {{anchor|IDX76}} {{anchor|IDX77}} {{anchor|IDX78}} [http://panotools.sourceforge.net/ PanoTools] the successor of Helmut Dersch's [http://www.all-in-one.ee/~dersch/ original PanoTools] offers a set of command-line dirven applications to create panoramas. Most notable are <code>PTOptimizer</code> and <code>PTmender</code>.

; '''Image Manipulation'''

:* {{anchor|IDX79}} {{anchor|IDX80}} [http://www.cinepaint.org/ CinePaint] is a branch of an early Gimp forked off at version 1.0.4. It sports much less features than the current Gimp, but offers 8bit, 16bit and 32bit color channels, HDR (for example floating-point TIFF, and OpenEXR), and a tightly integrated color management system.
:* {{anchor|IDX81}} {{anchor|IDX82}} The [www.gimp.org/ Gimp] is a general purpose image manipulation program. At the time of this writing it is still limited to images with only 8bits per channel.
:* {{anchor|IDX83}} {{anchor|IDX84}} [http://www.imagemagick.org/ ImageMagick] and its clone [http://www.graphicsmagick.org/ GraphicsMagick] are general purpose command-line driven image manipulation programs.

; '''High Dynamic Range'''

:* {{anchor|IDX85}} [http://www.openexr.com/ OpenEXR] offers libraries and some programs to work with the EXR HDR format.
:* {{anchor|IDX86}} [http://pfstools.sourceforge.net/ PFSTools] create, modify, and tonemap high-dynamic range images.

; '''Libraries'''

:* {{anchor|IDX87}} [http://www.ijg.org/ LibJPEG] is a library for handling the JPEG (JFIF) image format.
:* {{anchor|IDX88}} [http://www.libpng.org/pub/png/libpng.html LibPNG] is a library that handles the Portable Network Graphics (PNG) image format.
:* {{anchor|IDX89}} [http://www.remotesensing.org/libtiff/ LibTIFF] offers a library and utility programs to manipulate the ubiquitous Tagged Image File Format, TIFF. {{anchor|IDX90}} The nifty <code>tiffinfo</code> command quickly inquires the properties of TIFF files.

; '''Meta-Data Handling'''

:* {{anchor|IDX91}} {{anchor|IDX92}} [http://www.sno.phy.queensu.ca/~phil/exiftool/ EXIFTool] reads and writes EXIF meta data. In particular it copies meta data from one image to another.
:* {{anchor|IDX93}} {{anchor|IDX94}} [http://www.littlecms.com/ LittleCMS] is the color management library used by Hugin, DCRaw, UFRaw, Enblend, and Enfuse. It supplies some binaries, too. <code>tifficc</code>, an ICC color profile applier, is of particular interest.

----

{{anchor|Authors}} {{anchor|SEC11}}

==A. Authors==

* Andrew Mihal [mailto:acmihal@users.sourceforge.net acmihal@users.sourceforge.net].

----

{{anchor|Program-Index}} {{anchor|SEC13}}

==Program Index==

{|
! Jump to:
|
[[#SEC13_0|'''A''']] [[#SEC13_1|'''C''']] [[#SEC13_2|'''D''']] [[#SEC13_3|'''E''']] [[#SEC13_4|'''F''']] [[#SEC13_5|'''G''']] [[#SEC13_6|'''H''']] [[#SEC13_7|'''I''']] [[#SEC13_8|'''L''']] [[#SEC13_9|'''N''']] [[#SEC13_10|'''O''']] [[#SEC13_11|'''P''']] [[#SEC13_12|'''T''']] [[#SEC13_13|'''U''']]
|}

{| class="index-pg"
! align="left" | Index Entry
! align="left" | Section
|-
| colspan="3" |
----
|-
! {{anchor|SEC13_0}} A
|-
|
[[#IDX69|<code>ALE</code>]]
|
[[#SEC10|{{NotTOC|5. }}Helpful Additional Programs]]
|-
|
[[#IDX74|<code>align_image_stack</code>]]
|
[[#SEC10|{{NotTOC|5. }}Helpful Additional Programs]]
|-
|
[[#IDX70|<code>Anti-Lamenessing Engine</code>]]
|
[[#SEC10|{{NotTOC|5. }}Helpful Additional Programs]]
|-
| colspan="3" |
----
|-
! {{anchor|SEC13_1}} C
|-
|
[[#IDX79|<code>CinePaint</code>]]
|
[[#SEC10|{{NotTOC|5. }}Helpful Additional Programs]]
|-
|
[[#IDX80|<code>cinepaint</code>]]
|
[[#SEC10|{{NotTOC|5. }}Helpful Additional Programs]]
|-
| colspan="3" |
----
|-
! {{anchor|SEC13_2}} D
|-
|
[[#IDX65|<code>dcraw</code>]]
|
[[#SEC10|{{NotTOC|5. }}Helpful Additional Programs]]
|-
|
[[#IDX64|<code>DCRaw</code>]]
|
[[#SEC10|{{NotTOC|5. }}Helpful Additional Programs]]
|-
| colspan="3" |
----
|-
! {{anchor|SEC13_3}} E
|-
|
[[#IDX92|<code>exiftool</code>]]
|
[[#SEC10|{{NotTOC|5. }}Helpful Additional Programs]]
|-
|
[[#IDX91|<code>EXIFTool</code>]]
|
[[#SEC10|{{NotTOC|5. }}Helpful Additional Programs]]
|-
| colspan="3" |
----
|-
! {{anchor|SEC13_4}} F
|-
|
[[#IDX75|<code>fulla</code>]]
|
[[#SEC10|{{NotTOC|5. }}Helpful Additional Programs]]
|-
| colspan="3" |
----
|-
! {{anchor|SEC13_5}} G
|-
|
[[#IDX82|<code>gimp</code>]]
|
[[#SEC10|{{NotTOC|5. }}Helpful Additional Programs]]
|-
|
[[#IDX81|<code>Gimp</code>]]
|
[[#SEC10|{{NotTOC|5. }}Helpful Additional Programs]]
|-
|
[[#IDX84|<code>GraphicsMagick</code>]]
|
[[#SEC10|{{NotTOC|5. }}Helpful Additional Programs]]
|-
| colspan="3" |
----
|-
! {{anchor|SEC13_6}} H
|-
|
[[#IDX1|<code>hugin</code>]]
|
[[#SEC1|{{NotTOC|1. }}Overview]]
|-
|
[[#IDX38|<code>Hugin</code>]]
|
[[#SEC4|{{NotTOC|2.2 }}Extended Options]]
|-
|
[[#IDX72|<code>hugin</code>]]
|
[[#SEC10|{{NotTOC|5. }}Helpful Additional Programs]]
|-
|
[[#IDX71|<code>Hugin</code>]]
|
[[#SEC10|{{NotTOC|5. }}Helpful Additional Programs]]
|-
| colspan="3" |
----
|-
! {{anchor|SEC13_7}} I
|-
|
[[#IDX61|<code>identify</code>]]
|
[[#SEC7|{{NotTOC|3.1 }}Masks in Input Files]]
|-
|
[[#IDX83|<code>ImageMagick</code>]]
|
[[#SEC10|{{NotTOC|5. }}Helpful Additional Programs]]
|-
| colspan="3" |
----
|-
! {{anchor|SEC13_8}} L
|-
|
[[#IDX87|<code>LibJPEG</code>]]
|
[[#SEC10|{{NotTOC|5. }}Helpful Additional Programs]]
|-
|
[[#IDX88|<code>LibPNG</code>]]
|
[[#SEC10|{{NotTOC|5. }}Helpful Additional Programs]]
|-
|
[[#IDX89|<code>LibTIFF</code>]]
|
[[#SEC10|{{NotTOC|5. }}Helpful Additional Programs]]
|-
|
[[#IDX93|<code>LittleCMS, TiffICC</code>]]
|
[[#SEC10|{{NotTOC|5. }}Helpful Additional Programs]]
|-
| colspan="3" |
----
|-
! {{anchor|SEC13_9}} N
|-
|
[[#IDX37|<code>nona</code>]]
|
[[#SEC4|{{NotTOC|2.2 }}Extended Options]]
|-
|
[[#IDX73|<code>nona</code>]]
|
[[#SEC10|{{NotTOC|5. }}Helpful Additional Programs]]
|-
| colspan="3" |
----
|-
! {{anchor|SEC13_10}} O
|-
|
[[#IDX85|<code>OpenEXR</code>]]
|
[[#SEC10|{{NotTOC|5. }}Helpful Additional Programs]]
|-
| colspan="3" |
----
|-
! {{anchor|SEC13_11}} P
|-
|
[[#IDX2|<code>PanoTools</code>]]
|
[[#SEC1|{{NotTOC|1. }}Overview]]
|-
|
[[#IDX76|<code>PanoTools</code>]]
|
[[#SEC10|{{NotTOC|5. }}Helpful Additional Programs]]
|-
|
[[#IDX86|<code>PFSTools</code>]]
|
[[#SEC10|{{NotTOC|5. }}Helpful Additional Programs]]
|-
|
[[#IDX78|<code>PTmender</code>]]
|
[[#SEC10|{{NotTOC|5. }}Helpful Additional Programs]]
|-
|
[[#IDX77|<code>PTOptimizer</code>]]
|
[[#SEC10|{{NotTOC|5. }}Helpful Additional Programs]]
|-
| colspan="3" |
----
|-
! {{anchor|SEC13_12}} T
|-
|
[[#IDX94|<code>tifficc</code>]]
|
[[#SEC10|{{NotTOC|5. }}Helpful Additional Programs]]
|-
|
[[#IDX62|<code>tiffinfo</code>]]
|
[[#SEC7|{{NotTOC|3.1 }}Masks in Input Files]]
|-
|
[[#IDX90|<code>tiffinfo</code>]]
|
[[#SEC10|{{NotTOC|5. }}Helpful Additional Programs]]
|-
| colspan="3" |
----
|-
! {{anchor|SEC13_13}} U
|-
|
[[#IDX66|<code>UFRaw</code>]]
|
[[#SEC10|{{NotTOC|5. }}Helpful Additional Programs]]
|-
|
[[#IDX67|<code>ufraw</code>]]
|
[[#SEC10|{{NotTOC|5. }}Helpful Additional Programs]]
|-
|
[[#IDX68|<code>ufraw-batch</code>]]
|
[[#SEC10|{{NotTOC|5. }}Helpful Additional Programs]]
|-
| colspan="3" |
----
|}

{|
! Jump to:
|
[[#SEC13_0|'''A''']] [[#SEC13_1|'''C''']] [[#SEC13_2|'''D''']] [[#SEC13_3|'''E''']] [[#SEC13_4|'''F''']] [[#SEC13_5|'''G''']] [[#SEC13_6|'''H''']] [[#SEC13_7|'''I''']] [[#SEC13_8|'''L''']] [[#SEC13_9|'''N''']] [[#SEC13_10|'''O''']] [[#SEC13_11|'''P''']] [[#SEC13_12|'''T''']] [[#SEC13_13|'''U''']]
|}

----

{{anchor|Option-Index}} {{anchor|SEC14}}

==Option Index==

{| class="index-op"
! align="left" | Index Entry
! align="left" | Section
|-
| colspan="3" |
----
|-
|
[[#IDX3|<code>-a</code>]]
|
[[#SEC3|{{NotTOC|2.1 }}Common Options]]
|-
|
[[#IDX22|<code>-b</code>]]
|
[[#SEC4|{{NotTOC|2.2 }}Extended Options]]
|-
|
[[#SEC9|<code>-b</code>]]
|
[[#SEC9|{{NotTOC|4. }}Tuning Memory Usage]]
|-
|
[[#IDX24|<code>-c</code>]]
|
[[#SEC4|{{NotTOC|2.2 }}Extended Options]]
|-
|
[[#IDX43|<code>--coarse-mask</code>]]
|
[[#SEC5|{{NotTOC|2.3 }}Mask Generation Options]]
|-
|
[[#IDX4|<code>--compression</code>]]
|
[[#SEC3|{{NotTOC|2.1 }}Common Options]]
|-
|
[[#IDX27|<code>-d</code>]]
|
[[#SEC4|{{NotTOC|2.2 }}Extended Options]]
|-
|
[[#IDX28|<code>--depth</code>]]
|
[[#SEC4|{{NotTOC|2.2 }}Extended Options]]
|-
|
[[#IDX35|<code>-f</code>]]
|
[[#SEC4|{{NotTOC|2.2 }}Extended Options]]
|-
|
[[#IDX46|<code>--fine-mask</code>]]
|
[[#SEC5|{{NotTOC|2.3 }}Mask Generation Options]]
|-
|
[[#IDX30|<code>-g</code>]]
|
[[#SEC4|{{NotTOC|2.2 }}Extended Options]]
|-
|
[[#IDX34|<code>--gpu</code>]]
|
[[#SEC4|{{NotTOC|2.2 }}Extended Options]]
|-
|
[[#IDX11|<code>-h</code>]]
|
[[#SEC3|{{NotTOC|2.1 }}Common Options]]
|-
|
[[#IDX12|<code>--help</code>]]
|
[[#SEC3|{{NotTOC|2.1 }}Common Options]]
|-
|
[[#IDX13|<code>-l</code>]]
|
[[#SEC3|{{NotTOC|2.1 }}Common Options]]
|-
|
[[#IDX49|<code>--load-mask</code>]]
|
[[#SEC5|{{NotTOC|2.3 }}Mask Generation Options]]
|-
|
[[#IDX39|<code>-m</code>]]
|
[[#SEC4|{{NotTOC|2.2 }}Extended Options]]
|-
|
[[#SEC9|<code>-m</code>]]
|
[[#SEC9|{{NotTOC|4. }}Tuning Memory Usage]]
|-
|
[[#IDX52|<code>--no-optimize</code>]]
|
[[#SEC5|{{NotTOC|2.3 }}Mask Generation Options]]
|-
|
[[#IDX14|<code>-o</code>]]
|
[[#SEC3|{{NotTOC|2.1 }}Common Options]]
|-
|
[[#IDX55|<code>--optimize</code>]]
|
[[#SEC5|{{NotTOC|2.3 }}Mask Generation Options]]
|-
|
[[#IDX58|<code>--save-mask</code>]]
|
[[#SEC5|{{NotTOC|2.3 }}Mask Generation Options]]
|-
|
[[#IDX17|<code>-V</code>]]
|
[[#SEC3|{{NotTOC|2.1 }}Common Options]]
|-
|
[[#IDX15|<code>-v</code>]]
|
[[#SEC3|{{NotTOC|2.1 }}Common Options]]
|-
|
[[#IDX16|<code>--verbose</code>]]
|
[[#SEC3|{{NotTOC|2.1 }}Common Options]]
|-
|
[[#IDX18|<code>--version</code>]]
|
[[#SEC3|{{NotTOC|2.1 }}Common Options]]
|-
|
[[#IDX41|<code>--visualize</code>]]
|
[[#SEC4|{{NotTOC|2.2 }}Extended Options]]
|-
|
[[#IDX19|<code>-w</code>]]
|
[[#SEC3|{{NotTOC|2.1 }}Common Options]]
|-
|
[[#IDX20|<code>-x</code>]]
|
[[#SEC3|{{NotTOC|2.1 }}Common Options]]
|-
|
[[#IDX21|<code>-z</code>]]
|
[[#SEC3|{{NotTOC|2.1 }}Common Options]]
|-
| colspan="3" |
----
|}

----

{{anchor|General-Index}} {{anchor|SEC15}}

==General Index==

{|
! Jump to:
|
[[#SEC15_0|'''A''']] [[#SEC15_1|'''B''']] [[#SEC15_2|'''C''']] [[#SEC15_3|'''D''']] [[#SEC15_4|'''E''']] [[#SEC15_5|'''F''']] [[#SEC15_6|'''G''']] [[#SEC15_7|'''H''']] [[#SEC15_8|'''I''']] [[#SEC15_9|'''L''']] [[#SEC15_10|'''M''']] [[#SEC15_11|'''O''']] [[#SEC15_12|'''P''']] [[#SEC15_13|'''S''']] [[#SEC15_14|'''U''']] [[#SEC15_15|'''W''']]
|}

{| class="index-cp"
! align="left" | Index Entry
! align="left" | Section
|-
| colspan="3" |
----
|-
! {{anchor|SEC15_0}} A
|-
|
[[#IDX31|alpha channels, unassociated]]
|
[[#SEC4|{{NotTOC|2.2 }}Extended Options]]
|-
| colspan="3" |
----
|-
! {{anchor|SEC15_1}} B
|-
|
[[#SEC6|binary mask]]
|
[[#SEC6|{{NotTOC|3. }}Understanding Masks]]
|-
|
[[#IDX29|bits per channel]]
|
[[#SEC4|{{NotTOC|2.2 }}Extended Options]]
|-
| colspan="3" |
----
|-
! {{anchor|SEC15_2}} C
|-
|
[[#IDX26|CIECAM02]]
|
[[#SEC4|{{NotTOC|2.2 }}Extended Options]]
|-
|
[[#IDX33|Cinepaint]]
|
[[#SEC4|{{NotTOC|2.2 }}Extended Options]]
|-
|
[[#IDX45|coarse mask]]
|
[[#SEC5|{{NotTOC|2.3 }}Mask Generation Options]]
|-
|
[[#IDX25|color appearance model]]
|
[[#SEC4|{{NotTOC|2.2 }}Extended Options]]
|-
|
[[#IDX6|compression, deflate]]
|
[[#SEC3|{{NotTOC|2.1 }}Common Options]]
|-
|
[[#IDX8|compression, LZW]]
|
[[#SEC3|{{NotTOC|2.1 }}Common Options]]
|-
|
[[#IDX10|compression, packbits]]
|
[[#SEC3|{{NotTOC|2.1 }}Common Options]]
|-
| colspan="3" |
----
|-
! {{anchor|SEC15_3}} D
|-
|
[[#IDX5|deflate compression]]
|
[[#SEC3|{{NotTOC|2.1 }}Common Options]]
|-
| colspan="3" |
----
|-
! {{anchor|SEC15_4}} E
|-
|
[[#IDX63|<code>ENBLEND_CACHE_IMAGES</code> (preprocessor symbol)]]
|
[[#SEC9|{{NotTOC|4. }}Tuning Memory Usage]]
|-
| colspan="3" |
----
|-
! {{anchor|SEC15_5}} F
|-
|
[[#IDX48|fine mask]]
|
[[#SEC5|{{NotTOC|2.3 }}Mask Generation Options]]
|-
| colspan="3" |
----
|-
! {{anchor|SEC15_6}} G
|-
|
[[#SEC15|general index]]
|
[[#SEC15|General Index]]
|-
|
[[#IDX32|Gimp]]
|
[[#SEC4|{{NotTOC|2.2 }}Extended Options]]
|-
| colspan="3" |
----
|-
! {{anchor|SEC15_7}} H
|-
|
[[#SEC10|helpful programs]]
|
[[#SEC10|{{NotTOC|5. }}Helpful Additional Programs]]
|-
| colspan="3" |
----
|-
! {{anchor|SEC15_8}} I
|-
|
[[#IDX23|image cache, block size]]
|
[[#SEC4|{{NotTOC|2.2 }}Extended Options]]
|-
|
[[#IDX40|image cache, cache size]]
|
[[#SEC4|{{NotTOC|2.2 }}Extended Options]]
|-
|
[[#SEC15|index, general]]
|
[[#SEC15|General Index]]
|-
|
[[#SEC14|index, option]]
|
[[#SEC14|Option Index]]
|-
|
[[#SEC13|index, program]]
|
[[#SEC13|Program Index]]
|-
|
[[#SEC7|input masks]]
|
[[#SEC7|{{NotTOC|3.1 }}Masks in Input Files]]
|-
|
[[#SEC2|invocation]]
|
[[#SEC2|{{NotTOC|2. }}Invocation]]
|-
| colspan="3" |
----
|-
! {{anchor|SEC15_9}} L
|-
|
[[#IDX51|load mask]]
|
[[#SEC5|{{NotTOC|2.3 }}Mask Generation Options]]
|-
|
[[#IDX7|LZW compression]]
|
[[#SEC3|{{NotTOC|2.1 }}Common Options]]
|-
| colspan="3" |
----
|-
! {{anchor|SEC15_10}} M
|-
|
[[#SEC6|mask, binary]]
|
[[#SEC6|{{NotTOC|3. }}Understanding Masks]]
|-
|
[[#IDX44|mask, coarse]]
|
[[#SEC5|{{NotTOC|2.3 }}Mask Generation Options]]
|-
|
[[#IDX47|mask, fine]]
|
[[#SEC5|{{NotTOC|2.3 }}Mask Generation Options]]
|-
|
[[#IDX50|mask, load]]
|
[[#SEC5|{{NotTOC|2.3 }}Mask Generation Options]]
|-
|
[[#IDX59|mask, save]]
|
[[#SEC5|{{NotTOC|2.3 }}Mask Generation Options]]
|-
|
[[#IDX42|mask, visualization]]
|
[[#SEC4|{{NotTOC|2.2 }}Extended Options]]
|-
|
[[#SEC6|mask, weight]]
|
[[#SEC6|{{NotTOC|3. }}Understanding Masks]]
|-
|
[[#SEC7|masks, input files]]
|
[[#SEC7|{{NotTOC|3.1 }}Masks in Input Files]]
|-
|
[[#SEC6|masks, undestanding]]
|
[[#SEC6|{{NotTOC|3. }}Understanding Masks]]
|-
|
[[#SEC8|masks, weight]]
|
[[#SEC8|{{NotTOC|3.2 }}Weight Mask Files]]
|-
|
[[#SEC9|memory, tuning usage of]]
|
[[#SEC9|{{NotTOC|4. }}Tuning Memory Usage]]
|-
| colspan="3" |
----
|-
! {{anchor|SEC15_11}} O
|-
|
[[#IDX53|optimize seam]]
|
[[#SEC5|{{NotTOC|2.3 }}Mask Generation Options]]
|-
|
[[#IDX56|optimize seam]]
|
[[#SEC5|{{NotTOC|2.3 }}Mask Generation Options]]
|-
|
[[#SEC14|option index]]
|
[[#SEC14|Option Index]]
|-
|
[[#SEC3|options, common]]
|
[[#SEC3|{{NotTOC|2.1 }}Common Options]]
|-
|
[[#SEC4|options, extended]]
|
[[#SEC4|{{NotTOC|2.2 }}Extended Options]]
|-
|
[[#SEC5|options, mask generation]]
|
[[#SEC5|{{NotTOC|2.3 }}Mask Generation Options]]
|-
|
[[#IDX36|output image, set size of]]
|
[[#SEC4|{{NotTOC|2.2 }}Extended Options]]
|-
|
[[#SEC1|overview]]
|
[[#SEC1|{{NotTOC|1. }}Overview]]
|-
| colspan="3" |
----
|-
! {{anchor|SEC15_12}} P
|-
|
[[#IDX9|packbits compression]]
|
[[#SEC3|{{NotTOC|2.1 }}Common Options]]
|-
|
[[#SEC13|program index]]
|
[[#SEC13|Program Index]]
|-
|
[[#SEC10|programs, helpful additional]]
|
[[#SEC10|{{NotTOC|5. }}Helpful Additional Programs]]
|-
| colspan="3" |
----
|-
! {{anchor|SEC15_13}} S
|-
|
[[#IDX60|save mask]]
|
[[#SEC5|{{NotTOC|2.3 }}Mask Generation Options]]
|-
|
[[#IDX54|seam optimization]]
|
[[#SEC5|{{NotTOC|2.3 }}Mask Generation Options]]
|-
|
[[#IDX57|seam optimization]]
|
[[#SEC5|{{NotTOC|2.3 }}Mask Generation Options]]
|-
| colspan="3" |
----
|-
! {{anchor|SEC15_14}} U
|-
|
[[#SEC6|undestanding masks]]
|
[[#SEC6|{{NotTOC|3. }}Understanding Masks]]
|-
| colspan="3" |
----
|-
! {{anchor|SEC15_15}} W
|-
|
[[#SEC6|weight mask]]
|
[[#SEC6|{{NotTOC|3. }}Understanding Masks]]
|-
|
[[#SEC8|weight masks]]
|
[[#SEC8|{{NotTOC|3.2 }}Weight Mask Files]]
|-
| colspan="3" |
----
|}

{|
! Jump to:
|
[[#SEC15_0|'''A''']] [[#SEC15_1|'''B''']] [[#SEC15_2|'''C''']] [[#SEC15_3|'''D''']] [[#SEC15_4|'''E''']] [[#SEC15_5|'''F''']] [[#SEC15_6|'''G''']] [[#SEC15_7|'''H''']] [[#SEC15_8|'''I''']] [[#SEC15_9|'''L''']] [[#SEC15_10|'''M''']] [[#SEC15_11|'''O''']] [[#SEC15_12|'''P''']] [[#SEC15_13|'''S''']] [[#SEC15_14|'''U''']] [[#SEC15_15|'''W''']]
|}

----

{{anchor|SEC_Foot}}

==Footnotes==

{{anchor|FOOT1}} [[#DOCF1|(1)]] Peter J. Burt and Edward H. Adelson, “A Multiresolution Spline With Application to Image Mosaics”, ACM Transactions on Graphics, Vol. 2, No. 4, October 1983, pages 217–236.

----

{{anchor|SEC_Contents}}

==Table of Contents==

<div class="contents">

* {{anchor|TOC1}} [[#SEC1|{{NotTOC|1. }}Overview]]
* {{anchor|TOC2}} [[#SEC2|{{NotTOC|2. }}Invocation]]
** {{anchor|TOC3}} [[#SEC3|{{NotTOC|2.1 }}Common Options]]
** {{anchor|TOC4}} [[#SEC4|{{NotTOC|2.2 }}Extended Options]]
** {{anchor|TOC5}} [[#SEC5|{{NotTOC|2.3 }}Mask Generation Options]]
* {{anchor|TOC6}} [[#SEC6|{{NotTOC|3. }}Understanding Masks]]
** {{anchor|TOC7}} [[#SEC7|{{NotTOC|3.1 }}Masks in Input Files]]
** {{anchor|TOC8}} [[#SEC8|{{NotTOC|3.2 }}Weight Mask Files]]
* {{anchor|TOC9}} [[#SEC9|{{NotTOC|4. }}Tuning Memory Usage]]
* {{anchor|TOC10}} [[#SEC10|{{NotTOC|5. }}Helpful Additional Programs]]
* {{anchor|TOC11}} [[#SEC11|A. Authors]]
* {{anchor|TOC13}} [[#SEC13|Program Index]]
* {{anchor|TOC14}} [[#SEC14|Option Index]]
* {{anchor|TOC15}} [[#SEC15|General Index]]

</div>
----

[[Category:Software:Platform:Linux]]
[[Category:Software:Platform:Windows]]
[[Category:Software:Platform:Mac OS X]]

Enfuse reference manual

2009-03-04T09:57:51Z

Seb Przd: /* {{NotTOC|2.2 }}Extended Options */ -d parameter not available in many versions

{{anchor|Overview}} {{anchor|SEC1}}

This manual is for Enfuse (version 3.2-cvs, Thu Sep 25 07:35:21 UTC 2008). It was written by Dr. Christoph L. Spiel, converted partly from the HTML version, formulas mainly from the TeX original and corrected using the PDF version all found on http://panorama.dyndns.org/EandE-documentation/

=={{NotTOC|1. }}Overview==

Enfuse merges overlapping images using the Mertens-Kautz-Van Reeth exposure fusion algorithm.{{anchor|DOCF1}} [[#FOOT1|(1)]] This is a quick way for example to blend differently exposed images into a nice output image, without producing intermediate high-dynamic range (HDR) images that are then tonemapped to a viewable image. This simplified process often works much better than tonemapping algorithms.

Enfuse can also be used to build extended depth-of-field (DOF) images by blending a focus stack.

The idea is that pixels in the input images are weighted according to qualities such as, for example, proper exposure, good contrast, or high saturation. These weights determine how much a given pixel will contribute to the final image.

{{anchor|IDX1}}

A Burt-Adelson multiresolution spline blender{{anchor|DOCF2}} [[#FOOT2|(2)]] is used to combine the images according to the weights. The multiresolution blending ensures that transitions between regions where different images contribute are difficult to spot.

Enfuse uses up to four criteria to judge the quality of a pixel, which [[#tab_003aweighting_002dcriteria|tab:weighting-criteria]] briefly describes.

<div class="float">{{anchor|tab_003aweighting_002dcriteria}}

; Exposure
: {{anchor|IDX2}} The exposure criteria favors pixels with luminance close to the middle of the range. These pixels are considered better exposed as those with high or low luminance levels.
; Saturation
: {{anchor|IDX3}} The saturation criteria favors highly-saturated pixels. (Note that saturation is only defined for color pixels.)
; Contrast
: {{anchor|IDX4}} The contrast criteria favors pixels inside a high-contrast neighborhood. Enfuse can use standard deviation or Laplacian magnitude or a blend of both as local contrast measure.
; Entropy
: {{anchor|IDX5}} The entropy criteria prefers pixels inside a high-entropy neighborhood. In addition, Enfuse allows the user to mitigate the problem of noisy images when using entropy weighting by setting a black threshold.

</div>

'''Table 1.1: Enfuse's four weighting criteria. '''

For the concept of pixel weighting and details on the different weighting functions see [[#SEC8|Weighting Functions]].

Adjust how much importance is given to each criterion by setting the weight parameters on the command line. For example, if you set ‘--wExposure=1.0’ and ‘--wSaturation=0.5’, Enfuse will favor well-exposed pixels over highly-saturated pixels when blending the source images. The effect of these parameters on the final result will not always be clear in advance. The quality of the result is subject to your artistic interpretation. Playing with the weights may or may not give a more pleasing result. The authors encourage you to experiment, perhaps using down-sized{{anchor|DOCF3}} [[#FOOT3|(3)]] or cropped images for speed.

{{anchor|IDX6}} {{anchor|IDX7}}

Enfuse expects but does not require each input image to have an alpha channel. By setting the alpha values of pixels to zero, users can manually remove those pixels from consideration when blending. If an input image lacks an alpha channel, Enfuse will issue a warning and continue assuming all pixels should contribute to the final output. Any alpha value other than zero is interpreted as “this pixel should contribute to the final image”.

Find out more about Enfuse on its [http://enblend.sourceforge.net/ webpage].

----

{{anchor|Invocation}} {{anchor|SEC2}}

=={{NotTOC|2. }}Invocation==

<code>enfuse</code> [<var>OPTIONS</var>] <code>-o</code> <var>OUTPUT-FILE</var> <var>INPUT-FILES</var><small class="enddots">....</small>

Fuse the sequence of images <var>INPUT-FILES</var>… into <var>OUTPUT-FILE</var>.

{| class="menu"
| align="left" |
[[#SEC3|{{NotTOC|2.1 }}Common Options]]
| align="left" | General options
|-
| align="left" |
[[#SEC4|{{NotTOC|2.2 }}Extended Options]]
| align="left" | Memory control and others
|-
| align="left" |
[[#SEC5|{{NotTOC|2.3 }}Fusion Options]]
| align="left" | Image fusion control
|-
| align="left" |
[[#SEC6|{{NotTOC|2.4 }}Expert Options]]
| align="left" | Contrast and entropy selection configuration
|-
| align="left" |
[[#SEC7|{{NotTOC|2.5 }}Option Delimiters]]
| align="left" | How to separate options' arguments
|}

----

{{anchor|Common-Options}} {{anchor|SEC3}}

==={{NotTOC|2.1 }}Common Options===

Common options control some overall features of Enfuse.

; <code>--compression=<var>COMPRESSION</var></code>
: {{anchor|IDX8}} {{anchor|IDX9}} {{anchor|IDX10}} Write a compressed output file.Depending on the output file format Enfuse accepts different values for <var>COMPRESSION</var>.
:; JPEG
:: <var>COMPRESSION</var> is a JPEG quality level ranging from 0–100.
:; TIFF
:: <var>COMPRESSION</var> is one of the keywords:
::; ‘NONE’
::: Do not compress. This is the default.
::; ‘DEFLATE’
::: {{anchor|IDX11}} {{anchor|IDX12}} Use the Deflate compression scheme also called ZIP-in-TIFF. Deflate is a lossless data compression algorithm that uses a combination of the LZ77 algorithm and Huffman coding.
::; ‘LZW’
::: {{anchor|IDX13}} {{anchor|IDX14}} Use Lempel-Ziv-Welch (LZW) adaptive compression scheme. LZW compression is lossless.
::; ‘PACKBITS’
::: {{anchor|IDX15}} {{anchor|IDX16}} Use PackBits compression scheme. PackBits is a particular variant of run-length compression; it is lossless.
:; Any other format
:: Other formats like the PNG do not accept a <var>COMPRESSION</var> setting.
; <code>-h</code>
; <code>--help</code>
: {{anchor|IDX17}} {{anchor|IDX18}} Print information on the available options then exit.
; <code>-l <var>LEVELS</var></code>
: {{anchor|IDX19}} {{anchor|IDX20}} {{anchor|IDX21}} Use exactly this many <var>LEVELS</var> for pyramid blending.This option allows to trades off quality of results for slightly shorter execution time and lower memory usage. The default is to use as many levels as possible given the size of the overlap region. Enfuse may still use a smaller number of levels if the geometry of the images demands it.
; <code>-o <var>OUTPUT-FILE</var></code>
: {{anchor|IDX22}} Required option that specifies the name of the <var>OUTPUT-FILE</var>.
; <code>-v</code>
; <code>--verbose</code>
: {{anchor|IDX23}} {{anchor|IDX24}} Increase the verbosity of progress reporting. Giving one or more ‘-v’ options will make Enfuse more verbose.
; <code>-V</code>
; <code>--version</code>
: {{anchor|IDX25}} {{anchor|IDX26}} Output information on the Enblend version and some configuration details like extra features that have been compiled in.
; <code>-w</code>
: {{anchor|IDX27}} {{anchor|IDX28}} Blend around the ± 180° boundary. This is useful for full 360° panoramas.Version 3.2-cvs of Enfuse, the one described here, does not blend neither zenith nor or nadir, so you may still see some seams in these areas.

----

{{anchor|Extended-Options}} {{anchor|SEC4}}

==={{NotTOC|2.2 }}Extended Options===

Extended options control the image cache, the color model, and the cropping of the output image.

; <code>-b <var>BLOCKSIZE</var></code>
: {{anchor|IDX29}} {{anchor|IDX30}} Set the <var>BLOCKSIZE</var> in kilobytes (KB) of Enfuse's image cache.This is the amount of data that Enfuse will move to and from the disk in one go. The default is 2048KB, which should be ok for most systems.See [[#SEC25|Tuning Memory Usage]] for details.
; <code>-c</code>
: {{anchor|IDX31}} {{anchor|IDX32}} {{anchor|IDX33}} Use the CIECAM02 color appearance model for blending colors.The input files should have embedded ICC profiles when this option is specified. If no ICC profile is present, Enfuse will assume that the image uses the sRGB color space. The difference between this option and Enfuse's default color blending algorithm is slight, and will be only noticeable when areas of different primary colors are blended together.
; <code>-d</code>
; <code>--depth=<var>DEPTH</var></code>
: {{anchor|IDX34}} {{anchor|IDX35}} {{anchor|IDX36}} Force the number of bits per channel and the numeric format of the output image. All <var>DEPTH</var> specifications are valid in lowercase as well as uppercase letters. This option is only available in specific builds of Enfuse. For integer format use
:; <code>8</code>, <code>uint8</code>
:: Unsigned 8 bit; range: 0..255
:; <code>int16</code>
:: Signed 16 bit; range: -32768..32767
:; <code>16</code>, <code>uint16</code>
:: Unsigned 16 bit; range: 0..65536
:; <code>int32</code>
:: Signed 32 bit; range: -2147483648..2147483647
:; <code>32</code>, <code>uint32</code>
:: Unsigned 32 bit; range: 0..4294967295For floating-point format use
:; <code>r32</code>, <code>real32</code>, <code>float</code>
:: IEEE754 single precision floating-point, 32 bits wide, 24 bit significant
::* - Minimal normalized value: 1.2 × 10<sup>-38</sup>
::* - Epsilon: 1.2 × 10<sup>-7</sup>
::* - Maximal finite value: 3.4 × 10<sup>38</sup>
:; <code>r64</code>, <code>real64</code>, <code>double</code>
:: IEEE754 double precision floating-point, 64 bits wide, 53 bit significant
::* - Minimal normalized value: 2.2 × 10<sup>-308</sup>
::* - Epsilon: 2.2 × 10<sup>-16</sup>
::* - Maximal finite value: 1.8 × 10<sup>308</sup> If the requested <var>DEPTH</var> is not supported by the output file format, Enblend warns and chooses the <var>DEPTH</var> that matches best.
; <code>-g</code>
: {{anchor|IDX37}} {{anchor|IDX38}} Save alpha channel as “associated”. {{anchor|IDX39}} {{anchor|IDX40}} Gimp (before version 2.0) and CinePaint (see section [[#SEC45|Helpful Additional Programs]]) exhibit unusual behavior when loading images with unassociated alpha channels. Use option ‘-g’ to work around this problem. With this flag Enfuse will create the output image with the associated alpha tag set, even though the image is really unassociated alpha.
; <code>-f <var>WIDTH</var>x<var>HEIGHT</var></code>
; <code>-f <var>WIDTH</var>x<var>HEIGHT</var>+x<var>X-OFFSET</var>+y<var>Y- OFFSET</var></code>
: {{anchor|IDX41}} {{anchor|IDX42}} Set the size of the output image manually to <var>WIDTH</var>× <var>HEIGHT</var>. Optionally specify the <var>X-OFFSET</var> and <var>Y-OFFSET</var>, too. {{anchor|IDX43}} {{anchor|IDX44}} This option is useful when the input images are cropped TIFF files, such as those produced by <code>nona</code>. The stitcher <code>nona</code> is part of Hugin. See section [[#SEC45|Helpful Additional Programs]].
; <code>-m <var>CACHESIZE</var></code>
: {{anchor|IDX45}} {{anchor|IDX46}} Set the <var>CACHESIZE</var> in megabytes (MB) of Enfuse's image cache.This is the amount of memory Enfuse will use for storing image data before swapping to disk. The default is 1024MB, which is good for systems with 3–4gigabytes (GB) of RAM.See [[#SEC25|Tuning Memory Usage]] for details.

----

{{anchor|Fusion-Options}} {{anchor|SEC5}}

==={{NotTOC|2.3 }}Fusion Options===

Fusion options define the proportion to which each input image's pixel contributes to the output image.

; <code>--wContrast=<var>WEIGHT</var></code>
: {{anchor|IDX47}} Sets the relative <var>WEIGHT</var> of high-contrast pixels. Default: 0.0. Valid range: 0 ≤ WEIGHT ≤ 1. See [[#SEC14|Contrast Weighting]] and [[#SEC6|Option ContrastWindowSize]].
; <code>--wEntropy=<var>WEIGHT</var></code>
: {{anchor|IDX48}} Sets the relative <var>WEIGHT</var> of high entropy pixels. Default: 0.0. Valid range: 0 ≤ WEIGHT ≤ 1. See [[#SEC21|Entropy Weighting]] and [[#SEC6|Options EntropyWindowSize and EntropyCutoff]].
; <code>--wExposure=<var>WEIGHT</var></code>
: {{anchor|IDX49}} Sets the relative <var>WEIGHT</var> of the well-exposedness criterion. Increasing this weight relative to the others will make well exposed pixels contribute more to the final output. Default: 1.0. Valid range: 0 ≤ WEIGHT ≤ 1 . See section [[#SEC12|Exposure Weighting]].
; <code>--wMu=<var>MEAN</var></code>
: {{anchor|IDX50}} Set the <var>MEAN</var> (this is, the center) of the Gaussian exposure weight curve. Default: 0.5. Valid range: 0 ≤ MEAN ≤ 1 .Use this option to fine-tune exposure weighting (see section [[#SEC12|Exposure Weighting]]).
; <code>--wSaturation=<var>WEIGHT</var></code>
: {{anchor|IDX51}} Sets the relative <var>WEIGHT</var> of high-saturation pixels. Increasing this weight makes pixels with high saturation contribute more to the final output. Default: 0.2. Valid range: 0 ≤ WEIGHT ≤ 1. Saturation weighting is only defined for color images. See section [[#SEC13|Saturation Weighting]].
; <code>--wSigma=<var>STD-DEV</var></code>
: {{anchor|IDX52}} Standard deviation <var>STD-DEV</var> of the Gaussian exposure weight curve. Default: 0.2. Low numbers give less weight to pixels that are far from ‘--wMu’ and vice versa. Valid range: 0 ≤ STD-DEV ≤ 1 .Use this option to fine-tune exposure weighting (see section [[#SEC12|Exposure Weighting]]).

----

{{anchor|Expert-Options}} {{anchor|SEC6}}

==={{NotTOC|2.4 }}Expert Options===

Expert options influence the workings of Enfuse that require the user to read the manual before applying them successfully.

; <code>--ContrastWindowSize=<var>SIZE</var></code>
: {{anchor|IDX53}} Set the window <var>SIZE</var> for local contrast analysis. The window will be a square of <var>SIZE</var>× <var>SIZE</var> pixels.For contrast analysis <var>SIZE</var> values larger than 5 might result in a blurry composite image. Values of 3 and 5 have given good results on focus stacks.Valid range: SIZE ≥ 3 .Given an even <var>SIZE</var> Enfuse will automatically use the next odd number.See also [[#SEC5|Option –wContrast]] and ‘--HardMask’ below.
; <code>--EdgeScale=<var>EDGE-SCALE</var></code>
; <code>--EdgeScale=<var>EDGE-SCALE</var>:<var>LCE-SCALE</var>:<var>LCE-FACTOR</var></code>
: {{anchor|IDX54}} A non-zero value for <var>EDGE-SCALE</var> switches on the Laplacian-of-Gaussian (LoG) edge detection algorithm. <var>EDGE-SCALE</var> is the radius of the Gaussian used in the search for edges. Default: 0 pixels.A positive <var>LCE-SCALE</var> turns on local contrast enhancement (LCE) before the LoG edge detection. <var>LCE-SCALE</var> is the radius of the Gaussian used in the enhancement step, <var>LCE-FACTOR</var> is the weight factor (“strength”).
:<math>enhanced = (1 + LCE-FACTOR) * original - LCE-FACTOR * GaussianSmooth(original, LCE-SCALE)</math>
:<var>LCE-SCALE</var> defaults to 0 pixels and <var>LCE-FACTOR</var> defaults to 0. Append ‘%’ to <var>LCE-SCALE</var> to specify the radius as a percentage of <var>EDGE-SCALE</var>. Append ‘%’ to <var>LCE-FACTOR</var> to specify the weight as a percentage.
; <code>--EntropyCutoff=<var>LOWER-CUTOFF</var></code>
; <code>--EntropyCutoff=<var>LOWER-CUTOFF</var>:<var>UPPER-CUTOFF</var></code>
: {{anchor|IDX55}} The first form defines the lower cutoff value below of which pixels are treated as pure black when calculating the local entropy. The second form also defines the upper cutoff value above of which pixels are treated as pure white.For color images <var>LOWER-CUTOFF</var> and <var>UPPER-CUTOFF</var> are applied separately and independently to each channel.Defaults: 0% for <var>LOWER-CUTOFF</var> and 100% for <var>UPPER-CUTOFF</var>, this is, all pixels' values are taken into account. Append a ‘%’ to specify the cutoff relative to maximum pixel value in the source image (for example 255 or 65535). [[#fig_003aentropy_002dcutoff|fig:entropy-cutoff]] shows an example.<div class="float">{{anchor|fig_003aentropy_002dcutoff}} [[Image:entropy-cutoff.png|602px|entropy-cutoff]]</div>'''Figure 2.1: Linear lightness <var>Y</var> in comparison with an entropy-cutoff function for <var>LOWER-CUTOFF</var> = 5% and <var>UPPER-CUTOFF</var> = 90% which are rather extreme values. '''Note that a high <var>LOWER-CUTOFF</var> value lightens the resulting image, as dark (and presumably noisy) pixels are averaged with ''equal'' weights. With ‘--EntropyCutoff=0’, the default, on the other hand, “noise” might be interpreted as high entropy and the noisy pixels get a high weight, which in turn renders the resulting image darker. Analogously, a low <var>UPPER-CUTOFF</var> darkens the output image.
; <code>--EntropyWindowSize=<var>SIZE</var></code>
: {{anchor|IDX56}} Window <var>SIZE</var> for local entropy analysis. The window will be a square of <var>SIZE</var>× <var>SIZE</var> pixels.In the entropy calculation <var>SIZE</var> values of 3 to 7 yield an acceptable compromise of the locality of the information and the significance of the local entropy value itself.Valid range: SIZE ≥ 3 .Given an even <var>SIZE</var> Enfuse will automatically use the next odd number.
; <code>--GrayProjector=<var>PROJECTOR</var></code>
: {{anchor|IDX57}} {{anchor|IDX58}} Use gray projector <var>PROJECTOR</var> for conversion of RGB images to grayscale masks: R G B &rightarrow; Y . In version 3.2-cvs of Enfuse, the option is effective for exposure weighting contrast weighting. Default: ‘average’.Valid values for <var>PROJECTOR</var> are:
; <code>average</code>
: {{anchor|IDX59}} Average red, green, and blue channel with equal weights. This is the default and it often is a good projector for gamma = 1 data.
: <math>Y = {(R + G + B)}/{3}</math>
; <code>l-star</code>
: {{anchor|IDX60}} {{anchor|IDX61}} {{anchor|IDX62}} Use the L-channel of the L*a*b*-conversion of the image as its grayscale representation. This is a useful projector for gamma = 1 data. It reveals minute contrast variations even in the shadows and the highlights. This projector is computationally expensive.See [[wikipedia:Lab_color_space]] for a detailed description of the Lab color space.
; <code>lightness</code>
: {{anchor|IDX63}} Compute the lightness of each RGB pixel as in an Hue-Saturation-Lightness (HSL) conversion of the image.
: <math>Y = {(max(R, G, B) + min(R, G, B))}/{2}</math>
; <code>value</code>
: {{anchor|IDX64}} Take the Value-channel of the Hue-Saturation-Value (HSV) conversion of the image.
: <math>Y = max(R, G, B)</math>
; <code>luminance</code>
: {{anchor|IDX65}} Use the weighted average of the RGB pixel's channels as defined by CIE (“Commission Internationale de l'Éclairage”) and the JPEG standard.
: <math>Y = 0.30 * R + 0.59 * G + 0.11 * B</math>
; <code>channel-mixer:<var>RED-WEIGHT</var>:<var>GREEN-WEIGHT</var>:<var>BLUE-WEIGHT</var></code>
: {{anchor|IDX66}} Weight the channels as given.
: <math>Y = RED-WEIGHT * R + GREEN-WEIGHT * G + BLUE-WEIGHT * B</math>
: The weights are automatically normalized to one, so
<pre>
--GrayProjector=channel-mixer:0.25:0.5:0.25
--GrayProjector=channel-mixer:1:2:1
--GrayProjector=channel-mixer:25:50:25
</pre>
:all define the same mixer configuration.The three weights <var>RED-WEIGHT</var>, <var>GREEN-WEIGHT</var>, and <var>BLUE-WEIGHT</var> define the relative weight of the respective color channel. The sum of all weights is normalized to one.
; <code>--HardMask</code>
: {{anchor|IDX67}} Force hard blend masks on the finest scale. This is the opposite flag of ‘--SoftMask’.This blending mode avoids averaging of fine details (only) at the expense of increasing the noise. However it considerably improvs the sharpness of focus stacks. Blending with hard masks has solely proven useful with focus stacks.See also [[#SEC5|Option –wContrast]] and ‘--ContrastWindowSize’ above.
; <code>--MinCurvature=<var>CURVATURE</var></code>
: {{anchor|IDX68}} Define the minimum <var>CURVATURE</var> for the LoG edge detection. Default: 0. Append a ‘%’ to specify the minimum curvature relative to maximum pixel value in the source image (for example 255 or 65535).A positive value makes Enfuse use the local contrast data (controlled with ‘--ContrastWindowSize’) for curvatures less than <var>CURVATURE</var> and LoG data for values above it.A negative value truncates all curvatures less than -<var>CURVATURE</var> to zero. Values above <var>CURVATURE</var> are left unchanged. This effectively suppresses weak edges.
; <code>--SoftMask</code>
: {{anchor|IDX69}} Consider all masks when fusing. This is the default.

----

{{anchor|Option-Delimiters}} {{anchor|SEC7}}

==={{NotTOC|2.5 }}Option Delimiters===

Enfuse allows the arguments supplied to the program's options to be separated by different separators. The online documentation and this manual, however, exclusively uses the colon ‘:’ in every syntax definition and in all examples. Valid delimiters are the comma ‘,’, the semicolon ‘;’, the colon ‘:’, and the slash ‘/’. All delimiters may be mixed within any option.

Examples:

; ‘--EdgeScale=0.667:6.67:3.5’
: Separate all arguments with colons.
; ‘--EdgeScale=0.667,6.67,3.5’
: Use commas.
; ‘--EdgeScale=0.667;6.67/3.5’
: Mix semicolon and slash in weird ways.
; ‘--EntropyCutoff=3%/99%’
: All delimiters also work in conjuction with percentages.
; ‘--GrayProjector=channel-mixer:3/6/1’
: Separate arguments with a colon and two slashes.
; ‘--GrayProjector=channel-mixer/30;60,10’
: Go wild and Enfuse will understand.

----

{{anchor|Weighting-Functions}} {{anchor|SEC8}}

=={{NotTOC|3. }}Weighting Functions==

As has been noted in the Overview (see section [[#SEC1|Overview]]), Enfuse supports four different types of weighting. The following subsections describe the concept of weighting and all weighting functions in detail.

{| class="menu"
| align="left" |
[[#SEC9|{{NotTOC|3.1 }}Weighting Pixels]]
| align="left" | General concept of weighting pixels
|-
| align="left" |
[[#SEC12|{{NotTOC|3.2 }}Exposure Weighting]]
| align="left" | Weighting by exposure
|-
| align="left" |
[[#SEC13|{{NotTOC|3.3 }}Saturation Weighting]]
| align="left" | Weighting by saturation
|-
| align="left" |
[[#SEC14|{{NotTOC|3.4 }}Contrast Weighting]]
| align="left" | Weighting by local contrast
|-
| align="left" |
[[#SEC21|{{NotTOC|3.5 }}Entropy Weighting]]
| align="left" | Weighting by local entropy
|}

----

{{anchor|Weighting-Pixels}} {{anchor|SEC9}}

==={{NotTOC|3.1 }}Weighting Pixels===

Image fusion maps each pixel ''P(i, x, y)'' of every input image ''i'' to a single pixel ''Q(x, y)'' in the output image:''P(i, x, y) ? Q(x, y),'' where ''x'' runs from 1 to the common width of the images, ''y'' from 1 to the common height, and ''i'' from 1 to the number of input images ''n''.

Enfuse allows for weighting the contribution of each ''P(i, x, y)'' to the final ''Q(x, y)'':<br> ''w(P(1, x, y)) * P(1, x, y) +... +w(P(n, x, y)) * P(n, x, y)? Q(x, y),'' (W)<br>
where

* each ''w'' is non-negative to yield a physical intensity and
* the sum of all ''w'' is one to leave the total intensity unchanged.

The pixel weights ''w'' themselves are weighted sums with the same constraints

''w(P) = w<sub>exp</sub> * f<sub>exp</sub>(P) +w<sub>sat</sub> * f<sub>sat</sub>(P) +w<sub>cont</sub> * f<sub>cont</sub>(P, r<sub>cont</sub>) +w<sub>ent</sub> * f<sub>ent</sub>(P, r<sub>ent</sub>)'',

where we have abbreviated ''P(i, x, y)'' to P for simplicity. The user defines the constants ''w<sub>exp</sub>'', ''w<sub>sat</sub>'', ''w<sub>cont</sub>'', and ''w<sub>ent</sub>'' with the options `<tt>--wExposure</tt>', `<tt>--wSaturation</tt>', `<tt>--wContrast</tt>', and `<tt>--wEntropy</tt>' respectively. The functions ''f<sub>exp</sub>'', ''f<sub>sat</sub>'', ''f<sub>cont</sub>'', and ''f<sub>ent</sub>'' along with the window sizes ''r<sub>cont</sub>'' and ''r<sub>ent</sub>'' are explained in the next sections.

{| class="menu"
| align="left" |
[[#SEC10|{{NotTOC|3.1.1 }}Weighted Average]]
| align="left" | Enfuse's default weighting algorithm
|-
| align="left" |
[[#SEC11|{{NotTOC|3.1.2 }}Disabling Averaging: Option ‘--HardMask’]]
| align="left" | “Super Trouper” weighting for focus stacks
|}

----

{{anchor|Weighted-Average}} {{anchor|SEC10}}

===={{NotTOC|3.1.1 }}Weighted Average====

By default, Enfuse uses a weighted average, where ''each'' pixel contributes as much as its weight demands. Of course the weights can be extreme, favouring only a few pixels or even only one pixel in the input stack. Extremes are untypical, however.

Equal weights are another extreme that turns (W) into an arithmetic average. this is why we sometimes speak of the “averaging property” of this weighting algorithm, like smoothing out noise.

----

{{anchor|Disabling-Averaging}} {{anchor|SEC11}}

===={{NotTOC|3.1.2 }}Disabling Averaging: Option ‘-- HardMask’====

The weighted average computation as described above has proven to be widely successful with the exception of one special case: focus stacking (see section [[#SEC34|Focus Stacks – Depth-of-Field Increase]]), where the averaging noticeably softens the final image.

Use ‘--HardMask’ to switch Enfuse into a different (“Super Trouper”) weighting mode, where the pixel with the highest weight wins, this is, gets weight one, and all other pixels get the weight of zero ([[wikipedia:The_Winner_Takes_It_All]). With ‘--HardMask’ Equation (W) becomes <br>''P(i, x, y) ? Q(x, y),'' where ''w(P(i, x, y)) ? w(P(j, x, y))'' for all ''1 ? j ? n''.

Note that this “averaging” scheme lacks the nice noise-reduction property of the weighted average (W), because only a single input pixel contributes to the output.

----

{{anchor|Exposure-Weighting}} {{anchor|SEC12}}

==={{NotTOC|3.2 }}Exposure Weighting===

Exposure weighting prefers pixels with a luminance ''Y'' close to the center of the normalized, real-valued luminance interval ''[0, 1]''.

RGB-pixels get converted to luminance using the grayscale projector given by ‘--GrayProjector’, which defaults to <code>average</code>. Grayscale pixels are identified with luminance.

In the normalized luminance interval 0.0 represents pure black and 1.0 represents pure white independently of the data type of the input image. This is, for a JPEG image the luminance 255 maps to 1.0 in the normalized interval and for a 32bit TIFF picture the highest luminance value 4294967295 also maps to 1.0. The middle if the luminance interval, 0.5, is where a neutral gray tone ends up with every camera that had no exposure correction dialed in, for example the image of a gray- or white-card.

The exposure weighting algorithm only looks at a single pixel at a time; the pixel's neighborhood is not taken into account.

The weighting function is the Gaussian <math>w_{exp}(Y) = exp \left( - \frac{1}{2} \left( \frac{Y - Mu}{Sigma} \right) ^2 \right), \,</math> whose center ''Mu'' and width ''Sigma'' are controlled by the command line options ‘--wMu’ and ‘-- wSigma’ respectively. ''Mu'' defaults to 0.5, the middle of the luminance interval. ''Sigma'' defaults to 0.2. [[#fig_003agaussian|fig:gaussian]] shows a Gaussian with these parameters.

<div class="float">{{anchor|fig_003agaussian}}

[[Image:gaussian.png|565px|gaussian]]

</div>

'''Figure 3.1: Gaussian function with Enfuse's default parameters <var>Mu</var> = 0.5 and <var>Sigma</var> = 0.2. '''

The options ‘--wMu’ and ‘--wSigma’ are for fine-tuning the final result without changing the set of input images. Option ‘--wMu’ sets the point <var>Mu</var> of optimum exposure. The default is <var>Mu</var> = 0.5, exactly the middle between pure black (0.0) and pure white (1.0). Increasing <var>Mu</var> makes Enfuse prefer lighter pixels, rendering the final image lighter and vice versa. Option ‘--wSigma’ defines the range <var>Sigma</var> of acceptable exposures. The default is <var>Sigma</var> = 0.2, which means at <var>Mu</var> ± 0.2 the weight will be approximately 0.88. Small values of <var>Sigma</var> penalize exposures deviant from <var>Mu</var> more and vice versa.

'''Summary of influential options'''

; ‘--wExposure’
: [[#SEC5|Fusion Options]]
; ‘--wMu’
: [[#SEC5|Fusion Options]]
; ‘--wSigma’
: [[#SEC5|Fusion Options]]
; ‘--GrayProjector’
: [[#SEC6|Expert Options]]

----

{{anchor|Saturation-Weighting}} {{anchor|SEC13}}

==={{NotTOC|3.3 }}Saturation Weighting===

Saturation weighting prefers pixels with a high saturation.

Enfuse computes the saturation of a pixel according to the following algorithm.
<source lang="pas">
max := maximum(R, G, B)
min := minimum(R, G, B)
if max = min then
saturation := 0
else
sum := max + min
difference := max - min
if sum <= 1 then
saturation := difference / sum
else
saturation := difference / (2 - sum)
end if
end if
</source>

Obviously, saturation weighting can only be defined for RGB images, not for grayscale ones! If you need something similar check out [[#SEC21|Entropy Weighting]]<nowiki>; entropy weighting works for both </nowiki>RGB and grayscale pictures.

The saturation weighting algorithm only looks at a single pixel at a time; the pixel's neighborhood is not taken into account.

'''Summary of influential options'''

; ‘--wSaturation’
: [[#SEC5|Fusion Options]]

----

{{anchor|Contrast-Weighting}} {{anchor|SEC14}}

==={{NotTOC|3.4 }}Contrast Weighting===

Contrast weighting favors pixels inside a high contrast neighborhood. The notion of “high contrast” is defined either by two different criteria or by a blend of both:

* The standard deviation (SDev) of all the pixels in the local analysis window is large. See section [[#SEC15|Standard Deviation]].
* The Laplacian-of-Gaussian (LoG) has a large magnitude. See section [[#SEC18|Laplacian of Gaussian]].
* If the LoG magnitude is below a given threshold, use SDev data, otherwise stick with LoG. See section [[#SEC19|Blend Standard Deviation and Laplacian of Gaussian]].

Enfuse converts every RGB image to grayscale before it determines its contrast. Option ‘--GrayProjector’ (see section [[#SEC6|Expert Options]]) controls the projector function. Depending on the subject one of several grayscale projectors may yield the best black-and-white contrast for image fusion.

In the following sections we describe each algorithm in detail.

{| class="menu"
| align="left" |
[[#SEC15|{{NotTOC|3.4.1 }}Standard Deviation]]
| align="left" |
Standard deviation (SDev)
|-
| align="left" |
[[#SEC18|{{NotTOC|3.4.2 }}Laplacian of Gaussian]]
| align="left" |
LoG, a second derivative method
|-
| align="left" |
[[#SEC19|{{NotTOC|3.4.3 }}Blend Standard Deviation and Laplacian of Gaussian]]
| align="left" |
Mix and match SDev and LoG
|-
| align="left" |
[[#SEC20|{{NotTOC|3.4.4 }}Scaling and Choice of Mode]]
| align="left" | How parameters do not scale; neither does mode
|}

----

{{anchor|Standard-Deviation}} {{anchor|SEC15}}

===={{NotTOC|3.4.1 }}Standard Deviation====

The pixel under consideration C sits exactly in the center of a square, the so-called ''local analysis window''. It always has an uneven edge length. The user sets the size with option ‘--ContrastWindowSize’. [[#fig_003alocal_002danalysis_002dwindow|fig:local-analysis-window]] shows two windows with different sizes.

<div class="float">{{anchor|fig_003alocal_002danalysis_002dwindow}}

[[Image:local-analysis-window.png|428px|local-analysis-window]]

</div>

'''Figure 3.2: Examples of local analysis windows for the sizes 3 and 5. “C” marks the center where the pixel gets the weight. “N” are neighboring pixels, which all contribute equally to the weight. '''

During the analysis Enfuse scans the local analysis window across all rows and all columns{{anchor|DOCF4}} [[#FOOT4|(4)]] of each of the input images to compute the contrast weight of every pixel.

'''Summary of influential options'''

; ‘--wContrast’
: [[#SEC5|Fusion Options]]
; ‘--HardMask’
: [[#SEC5|Fusion Options]]
; ‘--ContrastWindowSize’
: [[#SEC6|Expert Options]]
; ‘--GrayProjector’
: [[#SEC6|Expert Options]]

----

{{anchor|SEC16}}

====={{NotTOC|3.4.1.1 }}Statistical Moments=====

We start with the ''probability function'' ''w'' of the random variable <math>X \,</math>:

<math>w: x \rightarrow p(\{\omega: X(\omega) = x\}) \,</math>.

It associates a probability <math>p \,</math> with each of the <math>n \,</math> different possible outcomes <math>\omega \,</math> of the random variable <math>X \,</math>. {{anchor|IDX70}} Based on <math>w \,</math>, we define the ''expectation value'' or “First Moment” of the random variable <math>X \,</math>:

<math>\hbox{ Ex } X := \sum_{i = 1}^n x_i w(x_i). \,</math>.

{{anchor|IDX71}} Using the definition of the expectation value, we define the ''variance'', or “Second Moment” as

<math>\mbox{ Var } X := \mbox{Ex}\left( (X - \mbox{Ex} X)^2 \right)</math>.

{{anchor|IDX72}} and the ''standard deviation'' as

<math>\sigma X := \sqrt{\mbox{Var}\ X}</math>.

Obviously, the variance of <math>X \,</math> is the expectation value of the squared deviation from the expectation value of <math>X \,</math> itself. Note that the variance's dimension is <math>X \,</math>'s dimension squared; the standard deviation rectifies the dimension to make it comparable with <math>X \,</math> itself again.

----

{{anchor|SEC17}}

====={{NotTOC|3.4.1.2 }}Estimators=====

In Enfuse, we assume that <math>X \,</math> follows a uniform probability function ''w(x)'' = const. This is, all pixel values in the local analysis window are considered to be equally probable. Thus, the expectation value and the variance can be estimated from the pixel values like this

<math>\mbox{Ex}\ X := {1 \over n} \sum_{i = 1}^n x_i</math>.

In other words: the expectation value is the arithmetic mean of the lightness of all pixels in the local analysis window. Analogously, the variance becomes

<math>\mbox{Var}\ X := {1 \over {n - 1}} \, \mbox{Ex}\left( (X - \mbox{Ex}\ X)^2 \right)</math>.

----

{{anchor|Laplacian-of-Gaussian}} {{anchor|SEC18}}

===={{NotTOC|3.4.2 }}Laplacian of Gaussian====

The ''Laplacian of Gaussian'' (LoG) is an operator to detect edges in an image. Sometimes the LoG-operator is also called Marr-Hildreth operator. A Laplacian-of-Gaussian operator, [http://kogs-www.informatik.uni-hamburg.de/~koethe/vigra/doc/vigra/group__CommonConvolutionFilters.html <code>vigra::laplacianOf Gaussian</code>] is part of the package [http://kogs-www.informatik.uni-hamburg.de/~koethe/vigra/ Vigra] that Enfuse is built upon and is used for edge detection if option ‘--EdgeScale’ is non-zero and ‘--MinCurvature’ equal to or less than zero.

Let the Gaussian function be

<math>g(x, y) = {1 \over {2 \pi \sigma^2}} \, {\exp\left(-{{x^2 + y^2} \over {2 \sigma^2}}\right)}</math>

The parameter <math>\sigma \,</math>, the argument of option ‘--EdgeScale’, is the length scale on which edges are detected by ''g(x, y)''. We apply the Laplacian operator in Cartesian coordinates

<math>\triangle \equiv \nabla \cdot \nabla = {\partial^2 \over \partial x^2} + {\partial^2 \over \partial y^2}</math>

to ''g(x, y)'', to arrive at a continous representation of the two-dimensional filter kernel

<math>k(x, y) = {{\xi^2 - 1} \over {\pi \sigma^4}} \exp(-\xi^2)</math>,

where we have used the dimensionless distance <math>\xi \,</math> from the origin

<math>\xi^2 = {{x^2 + y^2} \over {2 \sigma^2}}</math>.

Enfuse uses a discrete approximation of ''k'' in the convolution with the image. The operator is radially symmetric with respect to the origin, which is why we can easily plot it in [[#fig_003alaplacian_002dof_002dgaussian|fig:laplacian-of-gaussian]], setting <math>R = \sqrt{x^2 + y^2}</math>.

<div class="float">{{anchor|fig_003alaplacian_002dof_002dgaussian}}

[[Image:laplacian-of-gaussian.png|586px|laplacian-of-gaussian]]

</div>

'''Figure 3.3: Laplacian-of-Gaussian function for ? = 0.5. '''

See also [http://homepages.inf.ed.ac.uk/rbf/HIPR2/log.htm HIPR2<nowiki>: Laplacian of Gaussian</nowiki>].

Sometimes the LoG is plagued by noise in the input images. After all it is a numerical approximation of the second derivative and deriving always “roughens” a function. The (normalized) mask files relentlessly disclose such problems. Use option ‘--MinCurvature’ with a ''negative'' argument <var>CURVATURE</var> to suppress all edges with a curvature below -<var>CURVATURE</var> (which is a positive value). Check the effects with the mask files and particularly the ‘<tt>mask####_wta.tif</tt>’ files if using option ‘--HardMask’.

To indicate the <var>CURVATURE</var> in relative terms, which is particularly comprehensible for humans, append a percent sign (‘%’). Try minimum curvatures starting from -0.5% to -3%.

'''Summary of influential options'''

; ‘--wContrast’
: [[#SEC5|Fusion Options]]
; ‘--HardMask’
: [[#SEC5|Fusion Options]]
; ‘--EdgeScale’
: [[#SEC6|Expert Options]]
; ‘--MinCurvature’
: [[#SEC6|Expert Options]]

----

{{anchor|Blend-SDev-and-LoG}} {{anchor|SEC19}}

===={{NotTOC|3.4.3 }}Blend Standard Deviation and Laplacian of Gaussian====

Enfuse can team the standard deviation computation and Laplacian of Gaussian to deliver the best of both methods. Use a ''positive'' argument <var>CURVATURE</var> with option ‘--MinCurvature’ to combine both algorithms. In this mode of operation Enfuse computes the SDev-weight and the LoG-weight, then uses the LoG to decide whether to go with that value or prefer the SDev data. If the LoG is greater than <var>CURVATURE</var> Enfuse uses the weight delivered by the LoG, otherwise the SDev-weight is rescaled such that its maximum is equal to <var>CURVATURE</var> and the scaled SDev is used as weight.

This technique merges the two edge detection methods where the are best. The LoG excels with clear edges and cannot be fooled by strong but smooth gradients. However, it is bad at detecting faint edges and it is susceptible to noise. The SDev on the othe hand shines with even the most marginal edges and resists noise quite well. Its weakness is that is is easily deceived by strong and smooth gradients. Tuning <var>CURVATURE</var> the user can pick the best threshold for a given set of images.

'''Summary of influential options'''

; ‘--wContrast’
: [[#SEC5|Fusion Options]]
; ‘--HardMask’
: [[#SEC5|Fusion Options]]
; ‘--ContrastWindowSize’
: [[#SEC6|Expert Options]]
; ‘--GrayProjector’
: [[#SEC6|Expert Options]]
; ‘--EdgeScale’
: [[#SEC6|Expert Options]]
; ‘--MinCurvature’
: [[#SEC6|Expert Options]]

----

{{anchor|Scaling-and-Choice-of-Mode}} {{anchor|SEC20}}

===={{NotTOC|3.4.4 }}Scaling and Choice of Mode====

Experience has shown that neither the parameters <var>EDGESCALE</var> and <var>CURVATURE</var> nor the mode of operation (SDev-only, LoG-only, or a blend of both) scales to different image sizes. In practice this means that if you start with a set of reduced size images, say 2808× 1872 pixels, carefully optimize <var>EDGESCALE</var>, <var>CURVATURE</var> and so on, moreover find LoG-only the best mode and then switch to the original resolution of 5616× 3744 pixels, multiplying (or dividing) the parameters by four and sticking to LoG-only might ''not'' result in the best fused image. For best quality perform the parameter optimization and the search for the most appropriate mode at the final resolution.

----

{{anchor|Entropy-Weighting}} {{anchor|SEC21}}

==={{NotTOC|3.5 }}Entropy Weighting===

Entropy weighting prefers pixels inside a high entropy neighborhood.

{{anchor|IDX73}}

Let ''S'' be an ''n''-ary source. Watching the output of ''S'' an observer on average gains the information

<math>H_a(n) := \sum_{x \in S} p(x) \log_a(1 / p(x))</math>

{{anchor|IDX74}} per emitted message, where we assume the knowledge of the probability function ''p(S)''. The expectation value ''H_a(n)'' is called ''entropy'' of the source ''S''. Entropy measures our uncertainty if we are to guess which message gets chosen by the source in the future. The unit of the entropy depends on the choice of the constant ''a > 1''. Obviously

<math>H_b(n) = H_a(n) / \log_a(b) \,</math>

holds for all ''b > 1''. We use ''a = 2'' for entropy weighting and set the entropy of the “impossible message” to zero according to

<math>\lim_{p \rightarrow 0} \, p \, \log_a(1 / p) = 0</math>.

[[#fig_003aentropy|fig:entropy]] shows an entropy function.

<div class="float">{{anchor|fig_003aentropy}}

[[Image:entropy.png|581px|entropy]]

</div>

'''Figure 3.4: Entropy function H for an experiment with exactly two outcomes. '''

For more on (information) entropy visit [[wikipedia:Information_entropy]].

Enfuse computes a pixel's entropy by considering the pixel itself and its surrounding pixels quite similar to [[#SEC14|Contrast Weighting]]. The size of the window is set by ‘--EntropyWindowSize’. Choosing the right size is difficult, because there is a serious tradeoff between the locality of the data and the size of the sample used to compute ''H''. A large window results in a large sample size and therefore in a reliable entropy, but considering pixels far away from the center degrades ''H'' into a non-local measure. For small windows the opposite holds true.

Another difficulty arises from the use of entropy as a weighting function in dark parts of an image, this is, in areas where the signal-to-noise ratio is low. Without any precautions high noise is taken to be high entropy, which might not be desired. Use option ‘--EntropyCutoff’ to control the black level when computing the entropy.

On the other extreme side of lightness, very light parts of an image, the sensor might already have overflown without the signal reaching 1.0 in the normalized luminance interval. For these pixels the entropy is zero and Enfuse can be told of the threshold by properly setting the second argument of ‘--EntropyCutoff’.

'''Summary of influential options'''

; ‘--wEntropy’
: [[#SEC5|Fusion Options]]
; ‘--EntropyWindowSize’
: [[#SEC6|Expert Options]]
; ‘--EntropyCutoff’
: [[#SEC6|Expert Options]]

----

{{anchor|Understanding-Masks}} {{anchor|SEC22}}

=={{NotTOC|4. }}Understanding Masks==

A ''binary mask'' indicates for every pixel of an image if this pixel must be considered in further processing or ignored. For a ''weight mask'', the value of the mask determines how much the pixel contributes, zero again meaning “no contribution”.

Masks arise in two places: as part of the input files and as separate files, showing the actual pixel weights prior to image blendung or fusion. We shall explore both occurrences in the next sections.

----

{{anchor|SEC23}}

==={{NotTOC|4.1 }}Masks in Input Files===

Each of the input files for Enfuse and Enblend can contain its own mask. Both applications interpret them as binary masks no matter how many bits per image pixel they contain.

{{anchor|IDX75}} {{anchor|IDX76}}

Use ImageMagick's <code>identify</code> or, for TIFF files, <code>tiffinfo</code> to inquire quickly whether a file contains a mask. [[#SEC45|Helpful Additional Programs]] shows where to find these programs on the web.

$ identify -format "%f %m %wx%h %r %q-bit" remapped-0000.tif
remapped-0000.tif TIFF 800x533 DirectClassRGBMatte 8-bit
^^^^^ mask

$ tiffinfo remapped-0000.tif
TIFF Directory at offset 0x1a398a (1718666)
Subfile Type: (0 = 0x0)
Image Width: 800 Image Length: 533
Resolution: 150, 150 pixels/inch
Position: 0, 0
Bits/Sample: 8
Sample Format: unsigned integer
Compression Scheme: PackBits
Photometric Interpretation: RGB color
Extra Samples: 1<unassoc-alpha> <<<<< mask
Orientation: row 0 top, col 0 lhs
Samples/Pixel: 4 <<<<< R, G, B, and mask
Rows/Strip: 327
Planar Configuration: single image plane

The “Matte” part of the image class and the “Extra Samples” line tell us that the file features a mask. Also, many interactive image manipulation programs show the mask as a separate channel, sometimes called “Alpha”. There, the white (high mask value) parts of the mask enable pixels and black (low mask value) parts suppress them.

The multitude of terms all describing the concept of a mask is confusing.

; Mask
: A mask defines a selection of pixels. A value of zero represents an unselected pixel. The maximum value (“white”) represents a selected pixel and the values between zero and the maximum are partially selected pixels. See [http://gimp-savvy.com/BOOK/index.html?node42.html Gimp-Savy].
; Alpha Channel
: The alpha channel stores the transpacency value for each pixel, typically in the range from zero to one. A value of zero means the pixel is completely transparent, thus does not contribute to the image. A value of one on the other hand means the pixel is completely opaque.
; Matte
: The notion “matte” as used by ImageMagick refers to an inverted alpha channel, more precisely: 1 - alpha. See [http://www.imagemagick.org/Usage/channels/#trans ImageMagick] for further explanations.

Enblend and Enfuse only consider pixels that have an associated mask value different from zero. If an input image does not have an alpha channel, Enblend warns and assumes a mask of all non-zero values, this is, it will use every pixel of the input image for fusion.

Stitchers like <code>nona</code> add a mask to their output images.

Sometimes it is helpful to manually modify a mask before fusion. For example to suppress unwanted objects (insects and cars come into mind) that moved across the scene during the exposures. If the masks of all input images are black at a certain position, the output image will have a hole there.

----

{{anchor|SEC24}}

==={{NotTOC|4.2 }}Weight Mask Files===

...

----

{{anchor|Tuning-Memory-Usage}} {{anchor|SEC25}}

=={{NotTOC|5. }}Tuning Memory Usage==

The default configuration of Enfuse assumes a system with 3–4GB of RAM.

{{anchor|IDX77}}

If Enfuse has been compiled with the C++-preprocessor symbol <code>ENBLEND_CACHE_IMAGES</code> it uses its own image cache, whose size is user configurable with the option ‘-m <var>CACHE-SIZE</var>’ (see section [[#SEC4|Extended Options]]). Furthermore, option ‘-b <var>BUFFER-SIZE</var>’ (see section [[#SEC4|Extended Options]]) allows for fine-tuning the size of a single buffer inside the image cache. Note that <var>CACHE-SIZE</var> is given in megabytes, whereas <var>BUFFER-SIZE</var> is given in kilobytes.

Usually the user lets the operating system take care of the memory management of all processes. However, a user of Enfuse might want to control the balance between the operating systems' Virtual Memory System and Enfuse's image cache for several reasons.

* Paging in or out parts of a process' image runs at kernel level and thus can make user processes appear unresponsive or “jumpy”. The caching mechanism of Enfuse of course runs as a user process, which is why it has less detrimental effects on the system's overall responsiveness.
* Enfuse's image cache has been optimized for accesses to image data. And all algorithms in Enfuse have been carefully arranged to play nice with the image cache. An operating system's cache has no knowledge of these particular memory access patterns.
* The disk access of the operating system to the swap device has been highly optimized. Enfuse on the other hand uses the standard IO-layer which is a slower interface.
* Limiting the amount of image cache prevents Enfuse from eating up most or all RAM, thereby forcing all user applications into the swap device.

The <var>CACHE-SIZE</var> should be set in a way as to reconcile all of the above aspects even for the biggest data sets (this is many images and large images).

Suggested cache- and buffer-sizes for different amounts of available RAM.

<div class="float">{{anchor|tab_003acache_002dsize_002dsettings}}

{| border="1"
! RAM
! ''CACHE-SIZE''
! ''BUFFER-SIZE''
! Comment
|-
! MB
! MB
! KB
|-
| 4096
| 1024
| 2048
| default
|-
| 2048
| 512–1024
| 1024
|-
| 1024
| 256–512
| 256–512
|}

</div>

'''Table 5.1: Suggested cache-size settings '''

----

{{anchor|Applications}} {{anchor|SEC26}}

=={{NotTOC|6. }}Applications of Enfuse==

The section describes some of the novel possibilities that Enfuse offers the photographer. In contrast to the previous chapters it centers around the image effects.

{| class="menu"
| align="left" |
[[#SEC27|{{NotTOC|6.1 }}What Makes Images Fusable? ]]
| align="left" | What makes images fusable?
|-
| align="left" |
[[#SEC28|{{NotTOC|6.2 }}Repetition – Noise Reduction]]
| align="left" | Just taking the same shot multiple times
|-
| align="left" |
[[#SEC29|{{NotTOC|6.3 }}Exposure Series – Dynamic Range Increase]]
| align="left" | Varying the exposure time
|-
| align="left" |
[[#SEC32|{{NotTOC|6.4 }}Flash Exposure Series – Directed Lighting]]
| align="left" | Varying the flash output
|-
| align="left" |
[[#SEC33|{{NotTOC|6.5 }}Polarization Series – Saturation Enhancement]]
| align="left" | Changing the polarizer angle
|-
| align="left" |
[[#SEC34|{{NotTOC|6.6 }}Focus Stacks – Depth-of-Field Increase]]
| align="left" | Stacking images with different in-focus distance
|}

----

{{anchor|What-Images}} {{anchor|SEC27}}

==={{NotTOC|6.1 }}What Makes Images Fusable?===

Images should align well to be suitable for fusion. However, there is no hard mathematical rule what “well” means. The alignment requirements for 16MPixel images to yield a sharp 4"× 6" print at 300dpi (“dpi” means dots per inch) or even for web presentation are relatively low, whereas the alignment of 8MPixel images for a 12"× 18" print ought to be tight.

{{anchor|IDX78}}

If the input images need to be aligned, Hugin (see section [[#SEC45|Helpful Additional Programs]]) is the tool of choice. It produces images exactly in the format that Enfuse expects.

Sometimes images naturally align extremely well so that no re-alignment is required. An image series with preprogrammed exposure steps taken in rapid succession where the camera is mounted on a heavy tripod and a humongous ball head, mirror lockup and a cable release are used comes into mind.

When in doubt what will work, try it, and judge for yourself.

Useful ideas for a good alignment:

* Fix all camera parameters that are not explicitely varied.
*; ''Aperture''
*: Engage full manual (<M>) or aperture-priority (<A>) mode.
*; ''Auto-focus''
*: Disable “Auto Focus”. Be aware that the auto-focus function could be linked to shutter-release button position “half pressed” or to the shutter release in insidious ways.
*; ''Closed eyepiece''
*: (This applies only to single lens reflex cameras.) Close the eyepiece when using a cable release to suppress variations in stray light.
*; ''Exposure time/Shutter speed''
*: Use the shortest possible exposure time or, in other words, use the fastest shutter speed to avoid blur caused by camera shake or motion blur.
*; ''Flash power''
*: Explicitely control the flash power of ''all'' flashes. This is sometimes called “flash exposure lock”.
*; ''Sensitivity''
*: Disable “Auto ISO”.
*; ''White balance''
*: Disable “Auto White Balance”. Instead use the most suitable fixed white balance or take the white balance off a white card. When in doubt use the setting “Daylight” or equivalent.
* Steady the camera by any means.
** Apply your best camera bracing technique combined with controlled breathing.
** Prefer a monopod or better rigid tripod with a heavy head.
** (This applies to cameras with a moving mirror only.) Engage “mirror lockup”.
** Consider automatic bracketing when applicable.
** Activate camera- or lens-based image stabilization if you are sure that it improves the image quality in your particular case, otherwise disengage the feature. For some lens-based image stabilization systems it is known that they “lock” into different positions every time they are activated. Moreover, some stabilization systems decrease the image quality when the lens is mounted on a tripod.
* Fire in rapid succession.

----

{{anchor|Repetition}} {{anchor|SEC28}}

==={{NotTOC|6.2 }}Repetition – Noise Reduction===

'''Main Purpose: ''' Reduce noise

With the default settings Enfuse computes a weighted average of the input pixels. For a series of images, repeated with identical settings this results in a reduction of (photon shot) noise. In other words, the dynamic range increases slightly, because the higher signal-to-noise ratio makes darker shades usable. Furthermore, smooth or glossy surfaces get a “cleaner” look and edges become visually sharper. The nitty-gritty reportage look that sometimes stems from a high sensitivity setting disappears.

Averaged images and therefore low-noise images are the base for a multitude of techniques like for example differences. The most prominent method in this class is dark-frame subtraction.

The defaults set ‘--wExposure=1.0’ and ‘-- wSaturation=0.2’. Eliminating the saturation component with ‘--wSaturation=0.0’ can be worth an extra run.

----

{{anchor|Exposure-Series}} {{anchor|SEC29}}

==={{NotTOC|6.3 }}Exposure Series – Dynamic Range Increase===

'''Main Purpose: ''' Increase manageable dynamic range

An exposure series is a set of images taken with identical parameters except for the exposure time. Some cameras even provide special functions to automate recording exposure series. See the instruction manual of your model for details.

Enfuse's defaults, ‘--wExposure=1.0’ and ‘-- wSaturation=0.2’ are well suited for fusion of ''color'' images. Remember that saturation weighting only works for RGB data. Option ‘--wSaturation’ helps controlling burnt-out highlights as these are heavily desaturated. If no image suffers from troublesome highlights, the relative saturation weight can be reduced and even be set to zero. For black and white images ‘--wEntropy’ can be an alternative to ‘-- wSaturation’ because it suppresses overexposed pixels as these contain little information. However, saturation weighting is not limited to grayscale data. It has been successfully applied to RGB images, too. Note that saturation weighting considers ''each'' color channel of an RGB image separately and chooses the channel with the minimum entropy as representative for the whole pixel.

Enfuse offers the photographer tremendous flexibility on fusing differenly exposed images. Whether you combine only two pictures or a series of 21, Enfuse imposes no limits on you. Accordingly, the photographic effects achieved range from subtle to surreal like the late 1980s “Max Headroom” TV-Series to really unreal. Like some time ago in the chemical days of photography a new developer opened unseen possibilities for artists, exposure fusion extends a photographer's expressive space in the digital age. Whether the results look good or bad, whether the images are dull or exciting is entirely up the artist.

In the next sections we give assistance to starters and rectify several misconceptions about Enfuse.

{| class="menu"
| align="left" |
[[#SEC30|{{NotTOC|6.3.1 }}Tips For Beginners]]
| align="left" | Some hints for beginners
|-
| align="left" |
[[#SEC31|{{NotTOC|6.3.2 }}Common Misconceptions]]
| align="left" | What works despite the hype
|}

----

{{anchor|Exposure-Series-Tips}} {{anchor|SEC30}}

===={{NotTOC|6.3.1 }}Tips For Beginners====

Here are some tips to get you in business quickly.

; ''Include the best single exposure.''
: Include the exposure you would have taken if you did not use Enfuse in your series. It gives you a solid starting point. Think of the other images as augmenting this best single exposure to bring out the light and dark features you would like to see.
; ''Begin with as little images as possible.''
: Pre-visualizing the results of Enfuse is difficult. The more images enter the fusion process and the wider their EV-spacing is, the more challenging thinking of the output image becomes. Therefore, start off with as little images as possible.You can take a larger series of images and only use part of it.
; ''Start with a moderate EV-spacing.''
: As has been pointed out in the previous item, a wide EV-spacing makes pre-visualization harder. So set out with a spacing of 2/3EV to 1+1/3EV.

----

{{anchor|Exposure-Series-Misconceptions}} {{anchor|SEC31}}

===={{NotTOC|6.3.2 }}Common Misconceptions====

Here are some surprisingly common misconceptions about exposure series.

; ''A single image cannot be the source of an exposure series.''
: {{anchor|IDX79}} {{anchor|IDX80}} Raw-files in particular lend themselves to be converted multiple times and the results being fused together. The technique is simpler, faster, and usually even looks better than [http://luminous-landscape.com/tutorials/digital-blending.shtml digital blending] (as opposed to using a graduated neutral density filter) or [http://www.gimpguru.org/Tutorials/BlendingExposures/ blending exposures] in an image manipulation program. Moreover, perfect alignment comes free of charge!
; ''An exposure series must feature symmetric exposures.''
: Twice wrong! Neither do the exposures have to be “symmetric” like {0EV, -2/3EV, +2/3EV}, nor does the number of exposures have to be odd. Series like {-1-1/3EV, -1/3EV, +1/3EV} or {-1EV, 1EV} might be just right. By the way, the order in which the images were taken does not matter either.
; ''An exposure series must cover the whole dynamic range of the scene.''
: {{anchor|IDX81}} Unless you do not want to cover the whole range, you do not have to. Some HDR programs require the user to take a light probe,{{anchor|DOCF5}} [[#FOOT5|(5)]] whereas Enfuse offers the user complete freedom of exposure.
; ''All exposure values must be different.''
: You can repeat any exposure as often as you like. That way you combine and exposure series with parts of [[#SEC28|Repetition – Noise Reduction]], emphasizing the multiply occuring exposures and reducing noise.

----

{{anchor|Flash-Exposure-Series}} {{anchor|SEC32}}

==={{NotTOC|6.4 }}Flash Exposure Series – Directed Lighting===

'''Main Purpose: ''' ???

...

----

{{anchor|Polarization-Series}} {{anchor|SEC33}}

==={{NotTOC|6.5 }}Polarization Series – Saturation Enhancement===

'''Main Purpose: ''' Reflection suppression, saturation enhancement

In the current implementation of Enfuse it is not possible in general to fuse a polarization series. Naïvely abusing ‘--wSaturation’ will not work.

----

{{anchor|Focus-Stacks}} {{anchor|SEC34}}

==={{NotTOC|6.6 }}Focus Stacks – Depth-of-Field Increase===

'''Main Purpose: ''' Synthetic Depth-of-Field Increase

A ''focus stack'' is a series of images where the distance of the focal plane from the sensor varies. Sloppyly speaking, the images were focussed at different distances. Fusing such a stack increases the depth-of-field (DOF) beyond the physical limits of diffraction.

{| class="menu"
| align="left" |
[[#SEC35|{{NotTOC|6.6.1 }}Why create focus stacks? ]]
| align="left" | Why take the hassle?
|-
| align="left" |
[[#SEC36|{{NotTOC|6.6.2 }}Preparing Focus Stacks]]
| align="left" | How to get suitable input images
|-
| align="left" |
[[#SEC37|{{NotTOC|6.6.3 }}Contrast Based Fusing]]
| align="left" | Fundamental command line options
|-
| align="left" |
[[#SEC38|{{NotTOC|6.6.4 }}Basic Focus Stacking]]
| align="left" | Simple, standard deviation method
|-
| align="left" |
[[#SEC39|{{NotTOC|6.6.5 }}Advanced Focus Stacking]]
| align="left" | Advanced, Laplacian technique
|-
| align="left" |
[[#SEC44|{{NotTOC|6.6.6 }}Tips For Focus Stacking Experts]]
| align="left" | Tips for focus stacking experts
|}

----

{{anchor|Why-Focus-Stacks}} {{anchor|SEC35}}

===={{NotTOC|6.6.1 }}Why create focus stacks?====

Given

* a fixed sensor or film size,
* a lens' particular focal length, and
* {{anchor|IDX82}} {{anchor|IDX83}} a notion about “sharpness”, technically speaking the size of the circle-of-confusion (CoC)

{{anchor|IDX84}} {{anchor|IDX85}}

the photographer controls the depth-of-field with the aperture. Smaller apertures – this is larger aperture numbers – increase the DOF and vice versa. However, smaller apertures increase diffraction which in turn renders the image unsharp. So, there is an optimum aperture where the photographer gets maximum DOF. Sadly, for some purposes like macro shots it is not enough. One way out is to combine the sharp parts of images focused at different distances, thereby artifically increasing the total DOF. This is exactly what Enfuse can do.

{{anchor|IDX86}} {{anchor|IDX87}}

All lenses have a so called “sweet spot” aperture, where their resolution is best. Taking pictures at this aperture the photographer squeezes the maximum quality out of the lens. But: the “sweet spot” aperture often is only one or two stops away from wide open. Wouldn't it be great to be able combine these best-possible images to form one high-quality, sufficient-DOF image? Welcome to Enfuse's contrast selection abilities.

----

{{anchor|Preparing-Focus-Stacks}} {{anchor|SEC36}}

===={{NotTOC|6.6.2 }}Preparing Focus Stacks====

We are going to combine images with limited DOF to increase their in-focus parts. The whole process is about image sharpness. Therefore, the input images must align very well, not just well, but very well. For optimum results the maximum controlpoint distance in Hugin (see section [[#SEC45|Helpful Additional Programs]]) should not exceed 0.3–0.5pixels to ensure perfect blending.

As in all image fusion operations it is preferable to use 16bit linear (gamma = 1) images throughout, but 8bit gamma encoded images will do. Naturally, high SNR input data always is welcome.

----

{{anchor|Contrast-Based-Fusing}} {{anchor|SEC37}}

===={{NotTOC|6.6.3 }}Contrast Based Fusing====

A bare bones call to Enfuse for focus stacking could look like this.

{|
|
enfuse \
--wExposure=0 \
--wSaturation=0 \
--wContrast={{NotTOC|1 }}\
--HardMask \
… \
-o output.tif \
input-<0000-9999>.tif
|}

Here is what the option cause.

; ‘--wExposure=0’
: Switch '''off''' exposure based pixel selection. The default weight is 1.
; ‘--wSaturation=0’
: Switch '''off''' saturation based pixel selection. The default weight is 0.2.
; ‘--wContrast=1’
: Switch '''on''' pixel selection based on contrast.
; ‘--HardMask’
: Select the best pixel from the image stack and ignore all others. Without this option Enfuse uses all pixels in the stack and weights them according to their respective quality, which in our case would be contrast. Without ‘--HardMask’ the result will always look a bit soft. See section [[#SEC14|Contrast Weighting]].

If you want to see some entertaining progress messages – contrast weighting takes a while –, also pass the ‘-v’ option for a verbose progress report.

----

{{anchor|Basic-Focus-Stacking}} {{anchor|SEC38}}

===={{NotTOC|6.6.4 }}Basic Focus Stacking====

For a large class of image stacks Enfuse's default algorithm, as selected in [[#SEC37|Contrast Based Fusing]], to determine the sharpness produces nice results. The algorithm uses a moving square window, the so called contrast window. It computes the standard deviation of the pixels inside of the window. The program then selects the window's center pixel of the image in the stack where the standard deviation is largest, this is the local contrast reaches the maximum.

However, the algorithm fails to deliver good masks for images which exhibit high contrast edges on the scale of the contrast window size. The typical artifacts that show up are

* faint dark seams on the light side of the high contrast edges and
* extremely soft, slighly lighter seams on the dark side of the high contrast edges,

where the distance of the seams from the middle of the edge is comparable to the contrast window size.

If your results do not show any of this artifacts, stick with the basic algorithm. Advanced focus stacking as described in the next sections delivers superior results in case of artifacts, though requires manually tuning several parameters.

----

{{anchor|Advanced-Focus-Stacking}} {{anchor|SEC39}}

===={{NotTOC|6.6.5 }}Advanced Focus Stacking====

If your fused image shows any of the defects described in the previous section, you can try a more difficult to use algorithm that effectively works around the seam artifacts. It is described in the next section.

{| class="menu"
| align="left" |
[[#SEC40|{{NotTOC|6.6.5.1 }}A Detailed Look at the Problem]]
| align="left" | What is the problem Kenneth?
|-
| align="left" |
[[#SEC41|{{NotTOC|6.6.5.2 }}Laplacian Edge Detection]]
| align="left" | Using a Laplacian-of- Gaussian to detect edges
|-
| align="left" |
[[#SEC42|{{NotTOC|6.6.5.3 }}Local Contrast Enhancement]]
| align="left" | Boosting local contrast before weighting
|-
| align="left" |
[[#SEC43|{{NotTOC|6.6.5.4 }}Suppressing Noise or Recognizing Faint Edges]]
| align="left" | The best of both worlds
|}

----

{{anchor|Local-Contrast-Problem}} {{anchor|SEC40}}

====={{NotTOC|6.6.5.1 }}A Detailed Look at the Problem=====

Let us use an example to illustrate the problem of relating the sharpness with the local contrast variations. Say we use a 5× 5 contrast window. Moreover, let <code>sharp_edge</code> and <code>smooth_edge</code> be two specific configurations:

{|
|
sharp_edge = #( 0, 0, 200, 0, 0;
0, 225, 0, 0, 0;
0, 255, 0, 0, 0;
215, 0, 0, 0, 0;
200, 0, 0, 0, 0)
|}

{|
|
smooth_edge = #( 0, 62, 125, 187, 250;
1, 63, 126, 188, 251;
2, 65, 127, 190, 252;
3, 66, 128, 191, 253;
5, 67, 130, 192, 255)
|}

Imagess [[#fig_003asharp_002dedge|fig:sharp-edge]] and [[#fig_003asmooth_002dedge|fig:smooth-edge]] show plots of the matrices <code>sharp_edge</code> and <code>smooth_edge</code>.

<div class="float">{{anchor|fig_003asharp_002dedge}}

[[Image:sharp-edge.png|545px|sharp-edge]]

</div>

'''Figure 6.1: 3D plot augmented by contour plot of the matrix <code>sharp_edge</code>. '''

<div class="float">{{anchor|fig_003asmooth_002dedge}}

[[Image:smooth-edge.png|531px|smooth-edge]]

</div>

'''Figure 6.2: 3D plot augmented by contour plot of the matrix <code>smooth_edge</code>. '''

Our intuition lets us “see” an extremely sharp edge in the first matrix, whereas the second one describes an extraordinarily smooth diagonal intensity ramp. Which one will be selected? Well, <code>sharp_edge</code> has a standard deviation of 88.07 and <code>smooth_edge</code> has 88.41. Thus, <code>smooth_edge</code> wins, contradicting our intuition and even worse our intention!

Sadly, configurations like <code>smooth_edge</code> occur more often with high-quality, good [http://www.luminous-landscape.com/essays/bokeh.shtml bokeh] lenses. In fact they are the very manifestation of “good bokeh”. Therefore, Laplacian edge detection plays an important role when working with high-quality lenses.

----

{{anchor|Laplacian-Edge-Detection}} {{anchor|SEC41}}

====={{NotTOC|6.6.5.2 }}Laplacian Edge Detection=====

Enfuse provides a Laplacian-based algorithm that can help in situations where weighting based on the standard deviation fails. It is activated with a positive value for <var>SCALE</var> in <code>--EdgeScale</code>=<var>SCALE</var>. The Laplacian will detect two-dimensional ''curvature'' on the scale of <var>SCALE</var>. Here and in the following we simply speak of “curvature” where we mean “magnitude of curvature”. This is, we shall not distinguish between convex and concave edges. Enfuse always use the magnitude of curvature for weighting.

Typically, <var>SCALE</var> ranges between 0.1pixels and 0.5pixels, where 0.3pixels is a good starting point. To find the best value for <var>SCALE</var> though, usually some experimentation will be necessary. Use the ‘--debug’ option to get all ‘<tt>mask####.tif</tt>’ and ‘<tt>mask####_wta.tif</tt>’ files (see section [[#SEC22|Understanding Masks]]) and check how different scales affect the artifacts.

----

{{anchor|Local-Contrast-Enhancement}} {{anchor|SEC42}}

====={{NotTOC|6.6.5.3 }}Local Contrast Enhancement=====

Sometimes Enfuse misses smoother edges with ‘--EdgeScale’ and a little local contrast enhancement (LCE) helps. Set <code>--EdgeScale</code>=<var>SCALE</var>:<var>LCE-SCALE</var>:<var>LCE-FACTOR</var>. where <var>LCE-SCALE</var> and <var>LCE-FACTOR</var> work like the [http://www.cambridgeincolour.com/tutorials/unsharp-mask.htm unsharp mask] filters in various image manipulation programs. Start with <var>LCE-SCALE</var> ten times the value of <var>SCALE</var> and a <var>LCE-FACTOR</var> of 2–5.

<var>LCE-SCALE</var> can be specified as a percentage of <var>SCALE</var>. <var>LCE-FACTOR</var> also can be specified as a percentage. Examples:

{|
|
--EdgeScale=0.3:3.0:3
--EdgeScale=0.3:1000%:3.0
--EdgeScale=0.3:3:300%
--EdgeScale=0.3:1000%:300%
|}

By default LCE is turned off.

----

{{anchor|Suppressing-Noise-or-Recognizing-Faint-Edges}} {{anchor|SEC43}}

====={{NotTOC|6.6.5.4 }}Suppressing Noise or Recognizing Faint Edges=====

The Laplacian-based algorithm much better resists the seam problem than the local-contrast algorithm, but it has two shortcomings:

# The Laplacian is very susceptible to noise and
# it fails to recognize faint edges.

The ‘--MinCurvature’ option helps to mitigate both flaws.

The argument to <code>--MinCurvature</code>=<var>CURVATURE</var> either is an absolute lightness value, for example 0..255 for 8bit data and 0..65535 for 16bit data, or, when given with a ‘%’-sign it is a relative lightness value ranging from 0% to 100%.

To suppress unreal edges or counter excessive noise use the ‘--MinCurvature’ option with a ''negative'' curvature measure <var>CURVATURE</var>. This forces all curvatures less than -<var>CURVATURE</var> to zero.

A ''positive'' curvature measure <var>CURVATURE</var> makes Enfuse merge the LoG data with the local-contrast data. Every curvature larger or equal to <var>CURVATURE</var> is left unchanged and every curvature less than <var>CURVATURE</var> gets replaced by the rescaled local-contrast data such that the largest local contrast is just below <var>CURVATURE</var>. This combines the best parts of both techniques and ensures a precise edge detection over the whole range of edge curvatures.

'''Summary'''

; --EdgeScale=0.3
: Use LoG to detect edges on a scale of 0.3 pixels. Apply the default grayscale projector: <code>average</code>.
; --EdgeScale=0.3 --GrayProjector=l-star
: Use LoG to detect edges on a scale of 0.3 pixels. Apply the L*-grayscale projector.
; --EdgeScale=0.3:3:300%
: Use LoG to detect edges on a scale of 0.3 pixels, pre-sharpen the input images by 300% on a scale of 3 pixels. Apply the default grayscale projector: <code>average</code>.
; --EdgeScale=0.3 --MinCurvature=-0.5%
: Use LoG to detect edges on a scale of 0.3 pixels. Apply the default grayscale projector: <code>average</code> and throw away all edges with a curvature of less than 0.5%.
; --EdgeScale=0.3 --MinCurvature=0.5% --ContrastWindowSize=7
: Use LoG to detect edges on a scale of 0.3 pixels. Apply the default grayscale projector: <code>average</code> and throw away all edges with a curvature of less than 0.5% and replace the LoG data between 0% and 0.5% with SDev data. Usa a window of 7× 7 pixel window to compute the SDev.

----

{{anchor|Expert-Stacking}} {{anchor|SEC44}}

===={{NotTOC|6.6.6 }}Tips For Focus Stacking Experts====

We have collected some advice of which even focus stacking adepts can benefit.

* {{anchor|IDX88}} Ensure that the sensor is clean. Aligning focus stacks requires varying the viewing angle, which corresponds to a changing focal length. Hence, the same pixel on the sensor gets mapped onto different positions in the final image. Dirt spots will occur not only once but as many times as there are images in the stack – something unfunny to correct in postprocessing. {{anchor|IDX89}} {{anchor|IDX90}} {{anchor|IDX91}} {{anchor|IDX92}} Along the same lines the photographer may want to consider to prepare dark frames before and possibly also after the shoot of the focus stack to subtract hot pixels before fusion.
* {{anchor|IDX93}} Prefer a low-sensitivity setting on the camera to get low-noise images. Fusing with ‘--HardMask’ does not average and thus does not suppress any noise in the input images.
* If the transition of in-focus to out-of-focus areas is too abrupt, record the images with closest and farthest focusing distances twice: first with the intended working aperture and a second time with a small aperture (large aperture number). {{anchor|IDX94}} {{anchor|IDX95}} The small aperture will give the fused image a more natural in-focus to out-of-focus transition and the working-aperture shots supply the detail in the in-focus regions.

----

{{anchor|Helpful-Programs}} {{anchor|SEC45}}

=={{NotTOC|7. }}Helpful Additional Programs==

Several libraries and programs have proven helpful when working with Enfuse and Enblend.

; '''Raw Image Conversion'''

:* {{anchor|IDX96}} {{anchor|IDX97}} [http://www.cybercom.net/~dcoffin/dcraw/ DCRaw] is a universal raw-converter.
:* {{anchor|IDX98}} {{anchor|IDX99}} {{anchor|IDX100}} [http://ufraw.sourceforge.net/ UFRaw], a raw converter based on DCRaw, adds a GUI (<code>ufraw</code>), versatile batch processing (<code>ufraw-batch</code>), and some additional features like, for example, cropping, noise reduction with wavelets, and automatic lens error correction.

; '''Image Alignment and Rendering'''

:* {{anchor|IDX101}} {{anchor|IDX102}} [http://auricle.dyndns.org/ALE/ ALE], David Hilvert's anti-lamenessing engine for the real die-hard command-line users aligns, filters, and renders images.
:* {{anchor|IDX103}} {{anchor|IDX104}} [http://hugin.sourceforge.net/ Hugin] is a GUI that aligns and stitches images. {{anchor|IDX105}} {{anchor|IDX106}} {{anchor|IDX107}} <br>It comes with several command line tools, like <code>nona</code> to stitch panorama images, <code>align_image_stack</code> to align overlapping images for HDR or create focus stacks, and <code>fulla</code> to correct lens errors.
:* {{anchor|IDX108}} {{anchor|IDX109}} {{anchor|IDX110}} [http://panotools.sourceforge.net/ PanoTools] the successor of Helmut Dersch's [http://www.all-in-one.ee/~dersch/ original PanoTools] offers a set of command-line dirven applications to create panoramas. Most notable are <code>PTOptimizer</code> and <code>PTmender</code>.

; '''Image Manipulation'''

:* {{anchor|IDX111}} {{anchor|IDX112}} [http://www.cinepaint.org/ CinePaint] is a branch of an early Gimp forked off at version 1.0.4. It sports much less features than the current Gimp, but offers 8bit, 16bit and 32bit color channels, HDR (for example floating-point TIFF, and OpenEXR), and a tightly integrated color management system.
:* {{anchor|IDX113}} {{anchor|IDX114}} The [www.gimp.org/ Gimp] is a general purpose image manipulation program. At the time of this writing it is still limited to images with only 8bits per channel.
:* {{anchor|IDX115}} {{anchor|IDX116}} [http://www.imagemagick.org/ ImageMagick] and its clone [http://www.graphicsmagick.org/ GraphicsMagick] are general purpose command-line driven image manipulation programs.

; '''High Dynamic Range'''

:* {{anchor|IDX117}} [http://www.openexr.com/ OpenEXR] offers libraries and some programs to work with the EXR HDR format.
:* {{anchor|IDX118}} [http://pfstools.sourceforge.net/ PFSTools] create, modify, and tonemap high-dynamic range images.

; '''Libraries'''

:* {{anchor|IDX119}} [http://www.ijg.org/ LibJPEG] is a library for handling the JPEG (JFIF) image format.
:* {{anchor|IDX120}} [http://www.libpng.org/pub/png/libpng.html LibPNG] is a library that handles the Portable Network Graphics (PNG) image format.
:* {{anchor|IDX121}} [http://www.remotesensing.org/libtiff/ LibTIFF] offers a library and utility programs to manipulate the ubiquitous Tagged Image File Format, TIFF. {{anchor|IDX122}} The nifty <code>tiffinfo</code> command quickly inquires the properties of TIFF files.

; '''Meta-Data Handling'''

:* {{anchor|IDX123}} {{anchor|IDX124}} [http://www.sno.phy.queensu.ca/~phil/exiftool/ EXIFTool] reads and writes EXIF meta data. In particular it copies meta data from one image to another.
:* {{anchor|IDX125}} {{anchor|IDX126}} [http://www.littlecms.com/ LittleCMS] is the color management library used by Hugin, DCRaw, UFRaw, Enblend, and Enfuse. It supplies some binaries, too. <code>tifficc</code>, an ICC color profile applier, is of particular interest.

----

{{anchor|Authors}} {{anchor|SEC46}}

==A. Authors==

* Andrew Mihal ([mailto:acmihal@users.sourceforge.net acmihal@users.sourceforge.net]) has written Enfuse.
* Thanks to Simon Andriot and Pablo Joubert for suggesting the Mertens-Kautz-Van Reeth technique and the name “Enfuse”.
* The contrast criteria was added by Pablo d'Angelo ([mailto:dangelo@users.sourceforge.net dangelo@users.sourceforge.net]).
* Dr. Christoph L. Spiel added the gray projectors, the LoG-based edge detection, an O(n)-algorithm for the calculation of local contrast, and entropy weighting.

----

{{anchor|List-of-Tables}} {{anchor|SEC48}}

==List of Tables==

; [[#tab_003aweighting_002dcriteria|Table 1.1]]
: Weighting criteria
; [[#tab_003acache_002dsize_002dsettings|Table 5.1]]
: Suggested cache-size settings

----

{{anchor|List-of-Figures}} {{anchor|SEC49}}

==List of Figures==

; [[#fig_003aentropy_002dcutoff|Figure 2.1]]
: Entropy cutoff function
; [[#fig_003agaussian|Figure 3.1]]
: Gaussian function
; [[#fig_003alocal_002danalysis_002dwindow|Figure 3.2]]
: Local analysis window
; [[#fig_003alaplacian_002dof_002dgaussian|Figure 3.3]]
: Laplacian-of- Gaussian
; [[#fig_003aentropy|Figure 3.4]]
: Entropy function
; [[#fig_003asharp_002dedge|Figure 6.1]]
: Sharp edge
; [[#fig_003asmooth_002dedge|Figure 6.2]]
: Smooth edge

----

{{anchor|Program-Index}} {{anchor|SEC50}}

==Program Index==

{|
! | Jump to:
|
[[#SEC50_0|'''A''']] [[#SEC50_1|'''C''']] [[#SEC50_2|'''D''']] [[#SEC50_3|'''E''']] [[#SEC50_4|'''F''']] [[#SEC50_5|'''G''']] [[#SEC50_6|'''H''']] [[#SEC50_7|'''I''']] [[#SEC50_8|'''L''']] [[#SEC50_9|'''N''']] [[#SEC50_10|'''O''']] [[#SEC50_11|'''P''']] [[#SEC50_12|'''T''']] [[#SEC50_13|'''U''']]
|}

{| class="index-pg"
! align="left" | Index Entry
! align="left" | Section
|-
| colspan="3" |
----
|-
! {{anchor|SEC50_0}} A
|-
| |
[[#IDX101|<code>ALE</code>]]
| |
[[#SEC45|{{NotTOC|7. }}Helpful Additional Programs]]
|-
| |
[[#IDX106|<code>align_image_stack</code>]]
| |
[[#SEC45|{{NotTOC|7. }}Helpful Additional Programs]]
|-
| |
[[#IDX102|<code>Anti-Lamenessing Engine</code>]]
| |
[[#SEC45|{{NotTOC|7. }}Helpful Additional Programs]]
|-
| colspan="3" |
----
|-
! {{anchor|SEC50_1}} C
|-
| |
[[#IDX112|<code>cinepaint</code>]]
| |
[[#SEC45|{{NotTOC|7. }}Helpful Additional Programs]]
|-
| |
[[#IDX40|<code>CinePaint</code>]]
| |
[[#SEC4|{{NotTOC|2.2 }}Extended Options]]
|-
| |
[[#IDX111|<code>CinePaint</code>]]
| |
[[#SEC45|{{NotTOC|7. }}Helpful Additional Programs]]
|-
| colspan="3" |
----
|-
! {{anchor|SEC50_2}} D
|-
| |
[[#IDX96|<code>DCRaw</code>]]
| |
[[#SEC45|{{NotTOC|7. }}Helpful Additional Programs]]
|-
| |
[[#IDX97|<code>dcraw</code>]]
| |
[[#SEC45|{{NotTOC|7. }}Helpful Additional Programs]]
|-
| colspan="3" |
----
|-
! {{anchor|SEC50_3}} E
|-
| |
[[#IDX123|<code>EXIFTool</code>]]
| |
[[#SEC45|{{NotTOC|7. }}Helpful Additional Programs]]
|-
| |
[[#IDX124|<code>exiftool</code>]]
| |
[[#SEC45|{{NotTOC|7. }}Helpful Additional Programs]]
|-
| colspan="3" |
----
|-
! {{anchor|SEC50_4}} F
|-
| |
[[#IDX107|<code>fulla</code>]]
| |
[[#SEC45|{{NotTOC|7. }}Helpful Additional Programs]]
|-
| colspan="3" |
----
|-
! {{anchor|SEC50_5}} G
|-
| |
[[#IDX39|<code>Gimp</code>]]
| |
[[#SEC4|{{NotTOC|2.2 }}Extended Options]]
|-
| |
[[#IDX114|<code>gimp</code>]]
| |
[[#SEC45|{{NotTOC|7. }}Helpful Additional Programs]]
|-
| |
[[#IDX113|<code>Gimp</code>]]
| |
[[#SEC45|{{NotTOC|7. }}Helpful Additional Programs]]
|-
| |
[[#IDX116|<code>GraphicsMagick</code>]]
| |
[[#SEC45|{{NotTOC|7. }}Helpful Additional Programs]]
|-
| colspan="3" |
----
|-
! {{anchor|SEC50_6}} H
|-
| |
[[#IDX104|<code>hugin</code>]]
| |
[[#SEC45|{{NotTOC|7. }}Helpful Additional Programs]]
|-
| |
[[#IDX44|<code>Hugin</code>]]
| |
[[#SEC4|{{NotTOC|2.2 }}Extended Options]]
|-
| |
[[#IDX78|<code>Hugin</code>]]
| |
[[#SEC27|{{NotTOC|6.1 }}What Makes Images Fusable?]]
|-
| |
[[#IDX103|<code>Hugin</code>]]
| |
[[#SEC45|{{NotTOC|7. }}Helpful Additional Programs]]
|-
| colspan="3" |
----
|-
! {{anchor|SEC50_7}} I
|-
| |
[[#IDX75|<code>identify</code>]]
| |
[[#SEC23|{{NotTOC|4.1 }}Masks in Input Files]]
|-
| |
[[#IDX115|<code>ImageMagick</code>]]
| |
[[#SEC45|{{NotTOC|7. }}Helpful Additional Programs]]
|-
| colspan="3" |
----
|-
! {{anchor|SEC50_8}} L
|-
| |
[[#IDX119|<code>LibJPEG</code>]]
| |
[[#SEC45|{{NotTOC|7. }}Helpful Additional Programs]]
|-
| |
[[#IDX120|<code>LibPNG</code>]]
| |
[[#SEC45|{{NotTOC|7. }}Helpful Additional Programs]]
|-
| |
[[#IDX121|<code>LibTIFF</code>]]
| |
[[#SEC45|{{NotTOC|7. }}Helpful Additional Programs]]
|-
| |
[[#IDX125|<code>LittleCMS, TiffICC</code>]]
| |
[[#SEC45|{{NotTOC|7. }}Helpful Additional Programs]]
|-
| colspan="3" |
----
|-
! {{anchor|SEC50_9}} N
|-
| |
[[#IDX43|<code>nona</code>]]
| |
[[#SEC4|{{NotTOC|2.2 }}Extended Options]]
|-
| |
[[#IDX105|<code>nona</code>]]
| |
[[#SEC45|{{NotTOC|7. }}Helpful Additional Programs]]
|-
| colspan="3" |
----
|-
! {{anchor|SEC50_10}} O
|-
| |
[[#IDX117|<code>OpenEXR</code>]]
| |
[[#SEC45|{{NotTOC|7. }}Helpful Additional Programs]]
|-
| colspan="3" |
----
|-
! {{anchor|SEC50_11}} P
|-
| |
[[#IDX108|<code>PanoTools</code>]]
| |
[[#SEC45|{{NotTOC|7. }}Helpful Additional Programs]]
|-
| |
[[#IDX118|<code>PFSTools</code>]]
| |
[[#SEC45|{{NotTOC|7. }}Helpful Additional Programs]]
|-
| |
[[#IDX110|<code>PTmender</code>]]
| |
[[#SEC45|{{NotTOC|7. }}Helpful Additional Programs]]
|-
| |
[[#IDX109|<code>PTOptimizer</code>]]
| |
[[#SEC45|{{NotTOC|7. }}Helpful Additional Programs]]
|-
| colspan="3" |
----
|-
! {{anchor|SEC50_12}} T
|-
| |
[[#IDX126|<code>tifficc</code>]]
| |
[[#SEC45|{{NotTOC|7. }}Helpful Additional Programs]]
|-
| |
[[#IDX76|<code>tiffinfo</code>]]
| |
[[#SEC23|{{NotTOC|4.1 }}Masks in Input Files]]
|-
| |
[[#IDX122|<code>tiffinfo</code>]]
| |
[[#SEC45|{{NotTOC|7. }}Helpful Additional Programs]]
|-
| colspan="3" |
----
|-
! {{anchor|SEC50_13}} U
|-
| |
[[#IDX98|<code>UFRaw</code>]]
| |
[[#SEC45|{{NotTOC|7. }}Helpful Additional Programs]]
|-
| |
[[#IDX99|<code>ufraw</code>]]
| |
[[#SEC45|{{NotTOC|7. }}Helpful Additional Programs]]
|-
| |
[[#IDX100|<code>ufraw-batch</code>]]
| |
[[#SEC45|{{NotTOC|7. }}Helpful Additional Programs]]
|-
| colspan="3" |
----
|}

{|
! | Jump to:
|
[[#SEC50_0|'''A''']] [[#SEC50_1|'''C''']] [[#SEC50_2|'''D''']] [[#SEC50_3|'''E''']] [[#SEC50_4|'''F''']] [[#SEC50_5|'''G''']] [[#SEC50_6|'''H''']] [[#SEC50_7|'''I''']] [[#SEC50_8|'''L''']] [[#SEC50_9|'''N''']] [[#SEC50_10|'''O''']] [[#SEC50_11|'''P''']] [[#SEC50_12|'''T''']] [[#SEC50_13|'''U''']]
|}

----

{{anchor|Option-Index}} {{anchor|SEC51}}

==Option Index==

{|
! | Jump to:
|
[[#SEC51_0|'''-''']]<br />[[#SEC51_1|'''S''']]
|}

{| class="index-op"
! align="left" | Index Entry
! align="left" | Section
|-
| colspan="3" |
----
|-
! {{anchor|SEC51_0}} -
|-
| |
[[#IDX29|<code>-b</code>]]
| |
[[#SEC4|{{NotTOC|2.2 }}Extended Options]]
|-
| |
[[#SEC25|<code>-b</code>]]
| |
[[#SEC25|{{NotTOC|5. }}Tuning Memory Usage]]
|-
| |
[[#IDX31|<code>-c</code>]]
| |
[[#SEC4|{{NotTOC|2.2 }}Extended Options]]
|-
| |
[[#IDX8|<code>--compression</code>]]
| |
[[#SEC3|{{NotTOC|2.1 }}Common Options]]
|-
| |
[[#IDX53|<code>--ContrastWindowSize</code>]]
| |
[[#SEC6|{{NotTOC|2.4 }}Expert Options]]
|-
| |
[[#IDX34|<code>-d</code>]]
| |
[[#SEC4|{{NotTOC|2.2 }}Extended Options]]
|-
| |
[[#IDX35|<code>--depth</code>]]
| |
[[#SEC4|{{NotTOC|2.2 }}Extended Options]]
|-
| |
[[#IDX54|<code>--EdgeScale</code>]]
| |
[[#SEC6|{{NotTOC|2.4 }}Expert Options]]
|-
| |
[[#IDX55|<code>--EntropyCutoff</code>]]
| |
[[#SEC6|{{NotTOC|2.4 }}Expert Options]]
|-
| |
[[#IDX56|<code>--EntropyWindowSize</code>]]
| |
[[#SEC6|{{NotTOC|2.4 }}Expert Options]]
|-
| |
[[#IDX41|<code>-f</code>]]
| |
[[#SEC4|{{NotTOC|2.2 }}Extended Options]]
|-
| |
[[#IDX37|<code>-g</code>]]
| |
[[#SEC4|{{NotTOC|2.2 }}Extended Options]]
|-
| |
[[#IDX57|<code>--GrayProjector</code>]]
| |
[[#SEC6|{{NotTOC|2.4 }}Expert Options]]
|-
| |
[[#IDX17|<code>-h</code>]]
| |
[[#SEC3|{{NotTOC|2.1 }}Common Options]]
|-
| |
[[#IDX67|<code>--HardMask</code>]]
| |
[[#SEC6|{{NotTOC|2.4 }}Expert Options]]
|-
| |
[[#SEC11|<code>--HardMask</code>]]
| |
[[#SEC11|{{NotTOC|3.1.2 }}Disabling Averaging: Option ‘-- HardMask’]]
|-
| |
[[#IDX93|<code>--HardMask</code>]]
| |
[[#SEC44|{{NotTOC|6.6.6 }}Tips For Focus Stacking Experts]]
|-
| |
[[#IDX18|<code>--help</code>]]
| |
[[#SEC3|{{NotTOC|2.1 }}Common Options]]
|-
| |
[[#IDX19|<code>-l</code>]]
| |
[[#SEC3|{{NotTOC|2.1 }}Common Options]]
|-
| |
[[#IDX45|<code>-m</code>]]
| |
[[#SEC4|{{NotTOC|2.2 }}Extended Options]]
|-
| |
[[#SEC25|<code>-m</code>]]
| |
[[#SEC25|{{NotTOC|5. }}Tuning Memory Usage]]
|-
| |
[[#IDX68|<code>--MinCurvature</code>]]
| |
[[#SEC6|{{NotTOC|2.4 }}Expert Options]]
|-
| |
[[#IDX22|<code>-o</code>]]
| |
[[#SEC3|{{NotTOC|2.1 }}Common Options]]
|-
| |
[[#IDX25|<code>-V</code>]]
| |
[[#SEC3|{{NotTOC|2.1 }}Common Options]]
|-
| |
[[#IDX23|<code>-v</code>]]
| |
[[#SEC3|{{NotTOC|2.1 }}Common Options]]
|-
| |
[[#IDX24|<code>--verbose</code>]]
| |
[[#SEC3|{{NotTOC|2.1 }}Common Options]]
|-
| |
[[#IDX26|<code>--version</code>]]
| |
[[#SEC3|{{NotTOC|2.1 }}Common Options]]
|-
| |
[[#IDX27|<code>-w</code>]]
| |
[[#SEC3|{{NotTOC|2.1 }}Common Options]]
|-
| |
[[#IDX47|<code>--wContrast</code>]]
| |
[[#SEC5|{{NotTOC|2.3 }}Fusion Options]]
|-
| |
[[#IDX48|<code>--wEntropy</code>]]
| |
[[#SEC5|{{NotTOC|2.3 }}Fusion Options]]
|-
| |
[[#IDX49|<code>--wExposure</code>]]
| |
[[#SEC5|{{NotTOC|2.3 }}Fusion Options]]
|-
| |
[[#IDX50|<code>--wMu</code>]]
| |
[[#SEC5|{{NotTOC|2.3 }}Fusion Options]]
|-
| |
[[#IDX51|<code>--wSaturation</code>]]
| |
[[#SEC5|{{NotTOC|2.3 }}Fusion Options]]
|-
| |
[[#IDX52|<code>--wSigma</code>]]
| |
[[#SEC5|{{NotTOC|2.3 }}Fusion Options]]
|-
| colspan="3" |
----
|-
! {{anchor|SEC51_1}} S
|-
| |
[[#IDX69|<code>SoftMask</code>]]
| |
[[#SEC6|{{NotTOC|2.4 }}Expert Options]]
|-
| colspan="3" |
----
|}

{|
! | Jump to:
|
[[#SEC51_0|'''-''']]<br />[[#SEC51_1|'''S''']]
|}

----

{{anchor|General-Index}} {{anchor|SEC52}}

==General Index==

{|
! | Jump to:
|
[[#SEC52_0|'''3''']]<br />[[#SEC52_1|'''A''']] [[#SEC52_2|'''B''']] [[#SEC52_3|'''C''']] [[#SEC52_4|'''D''']] [[#SEC52_5|'''E''']] [[#SEC52_6|'''F''']] [[#SEC52_7|'''G''']] [[#SEC52_8|'''H''']] [[#SEC52_9|'''I''']] [[#SEC52_10|'''L''']] [[#SEC52_11|'''M''']] [[#SEC52_12|'''N''']] [[#SEC52_13|'''O''']] [[#SEC52_14|'''P''']] [[#SEC52_15|'''S''']] [[#SEC52_16|'''T''']] [[#SEC52_17|'''U''']] [[#SEC52_18|'''V''']] [[#SEC52_19|'''W''']]
|}

{| class="index-cp"
! align="left" | Index Entry
! align="left" | Section
|-
| colspan="3" |
----
|-
! {{anchor|SEC52_0}} 3
|-
| |
[[#IDX28|360° panorama]]
| |
[[#SEC3|{{NotTOC|2.1 }}Common Options]]
|-
| colspan="3" |
----
|-
! {{anchor|SEC52_1}} A
|-
| |
[[#SEC39|advanced focus stacking]]
| |
[[#SEC39|{{NotTOC|6.6.5 }}Advanced Focus Stacking]]
|-
| |
[[#SEC43|advanced focus stacking, recognizing faint edges]]
| |
[[#SEC43|{{NotTOC|6.6.5.4 }}Suppressing Noise or Recognizing Faint Edges]]
|-
| |
[[#SEC43|advanced focus stacking, suppressing noise]]
| |
[[#SEC43|{{NotTOC|6.6.5.4 }}Suppressing Noise or Recognizing Faint Edges]]
|-
| |
[[#IDX6|alpha channel]]
| |
[[#SEC1|{{NotTOC|1. }}Overview]]
|-
| |
[[#IDX38|alpha channels, unassociated]]
| |
[[#SEC4|{{NotTOC|2.2 }}Extended Options]]
|-
| |
[[#IDX87|aperture, sweet spot]]
| |
[[#SEC35|{{NotTOC|6.6.1 }}Why create focus stacks?]]
|-
| |
[[#SEC26|applications of enfuse]]
| |
[[#SEC26|{{NotTOC|6. }}Applications of Enfuse]]
|-
| |
[[#SEC46|authors, list of]]
| |
[[#SEC46|A. Authors]]
|-
| |
[[#SEC10|average, weighted]]
| |
[[#SEC10|{{NotTOC|3.1.1 }}Weighted Average]]
|-
| |
[[#SEC11|averaging, disabling]]
| |
[[#SEC11|{{NotTOC|3.1.2 }}Disabling Averaging: Option ‘-- HardMask’]]
|-
| colspan="3" |
----
|-
! {{anchor|SEC52_2}} B
|-
| |
[[#SEC38|basic focus stacking]]
| |
[[#SEC38|{{NotTOC|6.6.4 }}Basic Focus Stacking]]
|-
| |
[[#SEC22|binary mask]]
| |
[[#SEC22|{{NotTOC|4. }}Understanding Masks]]
|-
| |
[[#IDX36|bits per channel]]
| |
[[#SEC4|{{NotTOC|2.2 }}Extended Options]]
|-
| |
[[#IDX80|blending exposures]]
| |
[[#SEC31|{{NotTOC|6.3.2 }}Common Misconceptions]]
|-
| |
[[#IDX1|Burt-Adelson multiresolution spline]]
| |
[[#SEC1|{{NotTOC|1. }}Overview]]
|-
| colspan="3" |
----
|-
! {{anchor|SEC52_3}} C
|-
| |
[[#IDX7|channel, alpha]]
| |
[[#SEC1|{{NotTOC|1. }}Overview]]
|-
| |
[[#IDX33|CIECAM02]]
| |
[[#SEC4|{{NotTOC|2.2 }}Extended Options]]
|-
| |
[[#IDX82|circle-of-confusion]]
| |
[[#SEC35|{{NotTOC|6.6.1 }}Why create focus stacks?]]
|-
| |
[[#IDX83|CoC]]
| |
[[#SEC35|{{NotTOC|6.6.1 }}Why create focus stacks?]]
|-
| |
[[#IDX32|color appearance model]]
| |
[[#SEC4|{{NotTOC|2.2 }}Extended Options]]
|-
| |
[[#IDX10|compression]]
| |
[[#SEC3|{{NotTOC|2.1 }}Common Options]]
|-
| |
[[#IDX12|compression, deflate]]
| |
[[#SEC3|{{NotTOC|2.1 }}Common Options]]
|-
| |
[[#IDX14|compression, LZW]]
| |
[[#SEC3|{{NotTOC|2.1 }}Common Options]]
|-
| |
[[#IDX16|compression, packbits]]
| |
[[#SEC3|{{NotTOC|2.1 }}Common Options]]
|-
| |
[[#SEC37|contrased-based fusing]]
| |
[[#SEC37|{{NotTOC|6.6.3 }}Contrast Based Fusing]]
|-
| |
[[#SEC42|contrast enhancement, local]]
| |
[[#SEC42|{{NotTOC|6.6.5.3 }}Local Contrast Enhancement]]
|-
| |
[[#SEC19|contrast weighting using a blend of methods]]
| |
[[#SEC19|{{NotTOC|3.4.3 }}Blend Standard Deviation and Laplacian of Gaussian]]
|-
| |
[[#SEC18|contrast weighting using laplacian- of–gaussian]]
| |
[[#SEC18|{{NotTOC|3.4.2 }}Laplacian of Gaussian]]
|-
| |
[[#SEC15|contrast weighting using standard deviation]]
| |
[[#SEC15|{{NotTOC|3.4.1 }}Standard Deviation]]
|-
| |
[[#IDX62|conversion, L*a*b*]]
| |
[[#SEC6|{{NotTOC|2.4 }}Expert Options]]
|-
| colspan="3" |
----
|-
! {{anchor|SEC52_4}} D
|-
| |
[[#IDX89|dark frame]]
| |
[[#SEC44|{{NotTOC|6.6.6 }}Tips For Focus Stacking Experts]]
|-
| |
[[#IDX11|deflate compression]]
| |
[[#SEC3|{{NotTOC|2.1 }}Common Options]]
|-
| |
[[#SEC7|delimiters, option]]
| |
[[#SEC7|{{NotTOC|2.5 }}Option Delimiters]]
|-
| |
[[#IDX84|depth-of-field]]
| |
[[#SEC35|{{NotTOC|6.6.1 }}Why create focus stacks?]]
|-
| |
[[#SEC34|depth-of-focus increase]]
| |
[[#SEC34|{{NotTOC|6.6 }}Focus Stacks – Depth-of-Field Increase]]
|-
| |
[[#IDX79|digital blending]]
| |
[[#SEC31|{{NotTOC|6.3.2 }}Common Misconceptions]]
|-
| |
[[#SEC11|disabling averaging]]
| |
[[#SEC11|{{NotTOC|3.1.2 }}Disabling Averaging: Option ‘-- HardMask’]]
|-
| |
[[#IDX85|DOF]]
| |
[[#SEC35|{{NotTOC|6.6.1 }}Why create focus stacks?]]
|-
| |
[[#SEC29|dynamic range increase]]
| |
[[#SEC29|{{NotTOC|6.3 }}Exposure Series – Dynamic Range Increase]]
|-
| |
[[#SEC32|dynamic range increase]]
| |
[[#SEC32|{{NotTOC|6.4 }}Flash Exposure Series – Directed Lighting]]
|-
| colspan="3" |
----
|-
! {{anchor|SEC52_5}} E
|-
| |
[[#SEC41|edge detection, laplacian]]
| |
[[#SEC41|{{NotTOC|6.6.5.2 }}Laplacian Edge Detection]]
|-
| |
[[#IDX77|<code>ENBLEND_CACHE_IMAGES</code> (preprocessor symbol)]]
| |
[[#SEC25|{{NotTOC|5. }}Tuning Memory Usage]]
|-
| |
[[#IDX74|entropy]]
| |
[[#SEC21|{{NotTOC|3.5 }}Entropy Weighting]]
|-
| |
[[#IDX73|entropy, definition]]
| |
[[#SEC21|{{NotTOC|3.5 }}Entropy Weighting]]
|-
| |
[[#SEC17|estimators]]
| |
[[#SEC17|{{NotTOC|3.4.1.2 }}Estimators]]
|-
| |
[[#IDX70|expectation value]]
| |
[[#SEC16|{{NotTOC|3.4.1.1 }}Statistical Moments]]
|-
| |
[[#SEC44|expert focus stacking ttops]]
| |
[[#SEC44|{{NotTOC|6.6.6 }}Tips For Focus Stacking Experts]]
|-
| |
[[#SEC29|exposure series]]
| |
[[#SEC29|{{NotTOC|6.3 }}Exposure Series – Dynamic Range Increase]]
|-
| |
[[#SEC31|exposure series, common misconceptions]]
| |
[[#SEC31|{{NotTOC|6.3.2 }}Common Misconceptions]]
|-
| |
[[#SEC30|exposure series, tips for beginners]]
| |
[[#SEC30|{{NotTOC|6.3.1 }}Tips For Beginners]]
|-
| colspan="3" |
----
|-
! {{anchor|SEC52_6}} F
|-
| |
[[#SEC32|flash exposure series]]
| |
[[#SEC32|{{NotTOC|6.4 }}Flash Exposure Series – Directed Lighting]]
|-
| |
[[#SEC39|focus stacking, advanced]]
| |
[[#SEC39|{{NotTOC|6.6.5 }}Advanced Focus Stacking]]
|-
| |
[[#SEC38|focus stacking, basic]]
| |
[[#SEC38|{{NotTOC|6.6.4 }}Basic Focus Stacking]]
|-
| |
[[#SEC34|focus stacks]]
| |
[[#SEC34|{{NotTOC|6.6 }}Focus Stacks – Depth-of-Field Increase]]
|-
| |
[[#SEC37|focus stacks, fusing]]
| |
[[#SEC37|{{NotTOC|6.6.3 }}Contrast Based Fusing]]
|-
| |
[[#SEC36|focus stacks, preparation]]
| |
[[#SEC36|{{NotTOC|6.6.2 }}Preparing Focus Stacks]]
|-
| |
[[#SEC35|focus stacks, why create them]]
| |
[[#SEC35|{{NotTOC|6.6.1 }}Why create focus stacks?]]
|-
| |
[[#SEC37|fusing, contrased-based]]
| |
[[#SEC37|{{NotTOC|6.6.3 }}Contrast Based Fusing]]
|-
| colspan="3" |
----
|-
! {{anchor|SEC52_7}} G
|-
| |
[[#SEC52|general index]]
| |
[[#SEC52|General Index]]
|-
| |
[[#IDX58|gray projector]]
| |
[[#SEC6|{{NotTOC|2.4 }}Expert Options]]
|-
| |
[[#IDX59|gray projector, ‘average’]]
| |
[[#SEC6|{{NotTOC|2.4 }}Expert Options]]
|-
| |
[[#IDX66|gray projector, ‘channel- mixer’]]
| |
[[#SEC6|{{NotTOC|2.4 }}Expert Options]]
|-
| |
[[#IDX60|gray projector, ‘l- star’]]
| |
[[#SEC6|{{NotTOC|2.4 }}Expert Options]]
|-
| |
[[#IDX63|gray projector, ‘lightness’]]
| |
[[#SEC6|{{NotTOC|2.4 }}Expert Options]]
|-
| |
[[#IDX65|gray projector, ‘luminance’]]
| |
[[#SEC6|{{NotTOC|2.4 }}Expert Options]]
|-
| |
[[#IDX64|gray projector, ‘value’]]
| |
[[#SEC6|{{NotTOC|2.4 }}Expert Options]]
|-
| colspan="3" |
----
|-
! {{anchor|SEC52_8}} H
|-
| |
[[#SEC45|helpful programs]]
| |
[[#SEC45|{{NotTOC|7. }}Helpful Additional Programs]]
|-
| |
[[#IDX91|hot pixels]]
| |
[[#SEC44|{{NotTOC|6.6.6 }}Tips For Focus Stacking Experts]]
|-
| colspan="3" |
----
|-
! {{anchor|SEC52_9}} I
|-
| |
[[#IDX30|image cache, block size]]
| |
[[#SEC4|{{NotTOC|2.2 }}Extended Options]]
|-
| |
[[#IDX46|image cache, cache size]]
| |
[[#SEC4|{{NotTOC|2.2 }}Extended Options]]
|-
| |
[[#SEC27|images, fusable]]
| |
[[#SEC27|{{NotTOC|6.1 }}What Makes Images Fusable?]]
|-
| |
[[#SEC52|index, general]]
| |
[[#SEC52|General Index]]
|-
| |
[[#SEC51|index, option]]
| |
[[#SEC51|Option Index]]
|-
| |
[[#SEC50|index, program]]
| |
[[#SEC50|Program Index]]
|-
| |
[[#SEC23|input masks]]
| |
[[#SEC23|{{NotTOC|4.1 }}Masks in Input Files]]
|-
| |
[[#SEC2|invocation]]
| |
[[#SEC2|{{NotTOC|2. }}Invocation]]
|-
| colspan="3" |
----
|-
! {{anchor|SEC52_10}} L
|-
| |
[[#IDX61|L*a*b* conversion]]
| |
[[#SEC6|{{NotTOC|2.4 }}Expert Options]]
|-
| |
[[#SEC41|laplacian edge detection]]
| |
[[#SEC41|{{NotTOC|6.6.5.2 }}Laplacian Edge Detection]]
|-
| |
[[#SEC18|Laplacian of Gaussian]]
| |
[[#SEC18|{{NotTOC|3.4.2 }}Laplacian of Gaussian]]
|-
| |
[[#IDX21|levels, pyramid]]
| |
[[#SEC3|{{NotTOC|2.1 }}Common Options]]
|-
| |
[[#IDX81|light probe]]
| |
[[#SEC31|{{NotTOC|6.3.2 }}Common Misconceptions]]
|-
| |
[[#SEC15|local analysis window]]
| |
[[#SEC15|{{NotTOC|3.4.1 }}Standard Deviation]]
|-
| |
[[#SEC42|local contrast enhancement]]
| |
[[#SEC42|{{NotTOC|6.6.5.3 }}Local Contrast Enhancement]]
|-
| |
[[#SEC40|local contrast problem]]
| |
[[#SEC40|{{NotTOC|6.6.5.1 }}A Detailed Look at the Problem]]
|-
| |
[[#SEC18|LoG]]
| |
[[#SEC18|{{NotTOC|3.4.2 }}Laplacian of Gaussian]]
|-
| |
[[#IDX13|LZW compression]]
| |
[[#SEC3|{{NotTOC|2.1 }}Common Options]]
|-
| colspan="3" |
----
|-
! {{anchor|SEC52_11}} M
|-
| |
[[#SEC22|mask, binary]]
| |
[[#SEC22|{{NotTOC|4. }}Understanding Masks]]
|-
| |
[[#SEC22|mask, weight]]
| |
[[#SEC22|{{NotTOC|4. }}Understanding Masks]]
|-
| |
[[#SEC23|masks, input files]]
| |
[[#SEC23|{{NotTOC|4.1 }}Masks in Input Files]]
|-
| |
[[#SEC22|masks, undestanding]]
| |
[[#SEC22|{{NotTOC|4. }}Understanding Masks]]
|-
| |
[[#SEC24|masks, weight]]
| |
[[#SEC24|{{NotTOC|4.2 }}Weight Mask Files]]
|-
| |
[[#SEC25|memory, tuning usage of]]
| |
[[#SEC25|{{NotTOC|5. }}Tuning Memory Usage]]
|-
| |
[[#SEC1|Mertens-Kautz-Van Reeth exposure fusion]]
| |
[[#SEC1|{{NotTOC|1. }}Overview]]
|-
| |
[[#SEC20|mode of operation (SDev, LoG, …)]]
| |
[[#SEC20|{{NotTOC|3.4.4 }}Scaling and Choice of Mode]]
|-
| colspan="3" |
----
|-
! {{anchor|SEC52_12}} N
|-
| |
[[#IDX94|natural sharp-unsharp transition]]
| |
[[#SEC44|{{NotTOC|6.6.6 }}Tips For Focus Stacking Experts]]
|-
| |
[[#SEC28|noise reduction]]
| |
[[#SEC28|{{NotTOC|6.2 }}Repetition – Noise Reduction]]
|-
| colspan="3" |
----
|-
! {{anchor|SEC52_13}} O
|-
| |
[[#SEC7|option delimiters]]
| |
[[#SEC7|{{NotTOC|2.5 }}Option Delimiters]]
|-
| |
[[#SEC51|option index]]
| |
[[#SEC51|Option Index]]
|-
| |
[[#SEC3|options, common]]
| |
[[#SEC3|{{NotTOC|2.1 }}Common Options]]
|-
| |
[[#SEC6|options, expert]]
| |
[[#SEC6|{{NotTOC|2.4 }}Expert Options]]
|-
| |
[[#SEC4|options, extended]]
| |
[[#SEC4|{{NotTOC|2.2 }}Extended Options]]
|-
| |
[[#SEC5|options, fusion]]
| |
[[#SEC5|{{NotTOC|2.3 }}Fusion Options]]
|-
| |
[[#IDX9|output file compression]]
| |
[[#SEC3|{{NotTOC|2.1 }}Common Options]]
|-
| |
[[#IDX42|output image, set size of]]
| |
[[#SEC4|{{NotTOC|2.2 }}Extended Options]]
|-
| |
[[#SEC1|overview]]
| |
[[#SEC1|{{NotTOC|1. }}Overview]]
|-
| colspan="3" |
----
|-
! {{anchor|SEC52_14}} P
|-
| |
[[#IDX15|packbits compression]]
| |
[[#SEC3|{{NotTOC|2.1 }}Common Options]]
|-
| |
[[#IDX92|pixels, hot]]
| |
[[#SEC44|{{NotTOC|6.6.6 }}Tips For Focus Stacking Experts]]
|-
| |
[[#SEC33|polarization series]]
| |
[[#SEC33|{{NotTOC|6.5 }}Polarization Series – Saturation Enhancement]]
|-
| |
[[#SEC16|probability function]]
| |
[[#SEC16|{{NotTOC|3.4.1.1 }}Statistical Moments]]
|-
| |
[[#SEC40|problem, local contrast]]
| |
[[#SEC40|{{NotTOC|6.6.5.1 }}A Detailed Look at the Problem]]
|-
| |
[[#SEC50|program index]]
| |
[[#SEC50|Program Index]]
|-
| |
[[#SEC45|programs, helpful additional]]
| |
[[#SEC45|{{NotTOC|7. }}Helpful Additional Programs]]
|-
| |
[[#IDX20|pyramid levels]]
| |
[[#SEC3|{{NotTOC|2.1 }}Common Options]]
|-
| colspan="3" |
----
|-
! {{anchor|SEC52_15}} S
|-
| |
[[#SEC33|saturation enhancement]]
| |
[[#SEC33|{{NotTOC|6.5 }}Polarization Series – Saturation Enhancement]]
|-
| |
[[#SEC20|scaling of parameters]]
| |
[[#SEC20|{{NotTOC|3.4.4 }}Scaling and Choice of Mode]]
|-
| |
[[#IDX88|sensor, use of clean]]
| |
[[#SEC44|{{NotTOC|6.6.6 }}Tips For Focus Stacking Experts]]
|-
| |
[[#SEC29|series, exposure]]
| |
[[#SEC29|{{NotTOC|6.3 }}Exposure Series – Dynamic Range Increase]]
|-
| |
[[#SEC32|series, flash exposure]]
| |
[[#SEC32|{{NotTOC|6.4 }}Flash Exposure Series – Directed Lighting]]
|-
| |
[[#SEC33|series, polarization]]
| |
[[#SEC33|{{NotTOC|6.5 }}Polarization Series – Saturation Enhancement]]
|-
| |
[[#SEC28|series, simple]]
| |
[[#SEC28|{{NotTOC|6.2 }}Repetition – Noise Reduction]]
|-
| |
[[#SEC28|simple series]]
| |
[[#SEC28|{{NotTOC|6.2 }}Repetition – Noise Reduction]]
|-
| |
[[#IDX72|standard deviation]]
| |
[[#SEC16|{{NotTOC|3.4.1.1 }}Statistical Moments]]
|-
| |
[[#SEC16|statistical moments]]
| |
[[#SEC16|{{NotTOC|3.4.1.1 }}Statistical Moments]]
|-
| |
[[#IDX90|subtraction of dark frame]]
| |
[[#SEC44|{{NotTOC|6.6.6 }}Tips For Focus Stacking Experts]]
|-
| |
[[#IDX86|sweet spot aperture]]
| |
[[#SEC35|{{NotTOC|6.6.1 }}Why create focus stacks?]]
|-
| colspan="3" |
----
|-
! {{anchor|SEC52_16}} T
|-
| |
[[#SEC44|tips, focus stacking experts]]
| |
[[#SEC44|{{NotTOC|6.6.6 }}Tips For Focus Stacking Experts]]
|-
| |
[[#IDX95|transition, natural sharp-unsharp]]
| |
[[#SEC44|{{NotTOC|6.6.6 }}Tips For Focus Stacking Experts]]
|-
| colspan="3" |
----
|-
! {{anchor|SEC52_17}} U
|-
| |
[[#SEC22|undestanding masks]]
| |
[[#SEC22|{{NotTOC|4. }}Understanding Masks]]
|-
| colspan="3" |
----
|-
! {{anchor|SEC52_18}} V
|-
| |
[[#IDX71|variance]]
| |
[[#SEC16|{{NotTOC|3.4.1.1 }}Statistical Moments]]
|-
| colspan="3" |
----
|-
! {{anchor|SEC52_19}} W
|-
| |
[[#SEC22|weight mask]]
| |
[[#SEC22|{{NotTOC|4. }}Understanding Masks]]
|-
| |
[[#SEC24|weight masks]]
| |
[[#SEC24|{{NotTOC|4.2 }}Weight Mask Files]]
|-
| |
[[#SEC10|weighted average]]
| |
[[#SEC10|{{NotTOC|3.1.1 }}Weighted Average]]
|-
| |
[[#SEC8|weighting functions]]
| |
[[#SEC8|{{NotTOC|3. }}Weighting Functions]]
|-
| |
[[#IDX4|weighting, contrast]]
| |
[[#SEC1|{{NotTOC|1. }}Overview]]
|-
| |
[[#SEC14|weighting, contrast]]
| |
[[#SEC14|{{NotTOC|3.4 }}Contrast Weighting]]
|-
| |
[[#SEC19|weighting, contrast using a blend of methods]]
| |
[[#SEC19|{{NotTOC|3.4.3 }}Blend Standard Deviation and Laplacian of Gaussian]]
|-
| |
[[#SEC18|weighting, contrast using laplacian- of–gaussian]]
| |
[[#SEC18|{{NotTOC|3.4.2 }}Laplacian of Gaussian]]
|-
| |
[[#SEC15|weighting, contrast using standard deviation]]
| |
[[#SEC15|{{NotTOC|3.4.1 }}Standard Deviation]]
|-
| |
[[#IDX5|weighting, entropy]]
| |
[[#SEC1|{{NotTOC|1. }}Overview]]
|-
| |
[[#SEC21|weighting, entropy]]
| |
[[#SEC21|{{NotTOC|3.5 }}Entropy Weighting]]
|-
| |
[[#IDX2|weighting, exposure]]
| |
[[#SEC1|{{NotTOC|1. }}Overview]]
|-
| |
[[#SEC12|weighting, exposure]]
| |
[[#SEC12|{{NotTOC|3.2 }}Exposure Weighting]]
|-
| |
[[#SEC9|weighting, general concept of]]
| |
[[#SEC9|{{NotTOC|3.1 }}Weighting Pixels]]
|-
| |
[[#IDX3|weighting, saturation]]
| |
[[#SEC1|{{NotTOC|1. }}Overview]]
|-
| |
[[#SEC13|weighting, saturation]]
| |
[[#SEC13|{{NotTOC|3.3 }}Saturation Weighting]]
|-
| |
[[#SEC15|window, local-analysis]]
| |
[[#SEC15|{{NotTOC|3.4.1 }}Standard Deviation]]
|-
| colspan="3" |
----
|}

{|
! | Jump to:
|
[[#SEC52_0|'''3''']]<br />[[#SEC52_1|'''A''']] [[#SEC52_2|'''B''']] [[#SEC52_3|'''C''']] [[#SEC52_4|'''D''']] [[#SEC52_5|'''E''']] [[#SEC52_6|'''F''']] [[#SEC52_7|'''G''']] [[#SEC52_8|'''H''']] [[#SEC52_9|'''I''']] [[#SEC52_10|'''L''']] [[#SEC52_11|'''M''']] [[#SEC52_12|'''N''']] [[#SEC52_13|'''O''']] [[#SEC52_14|'''P''']] [[#SEC52_15|'''S''']] [[#SEC52_16|'''T''']] [[#SEC52_17|'''U''']] [[#SEC52_18|'''V''']] [[#SEC52_19|'''W''']]
|}

----

{{anchor|SEC_Foot}}

==Footnotes==

{{anchor|FOOT1}} [[#DOCF1|(1)]] Tom Mertens, Jan Kautz, and Frank van Reeth, “Exposure Fusion”, Proceedings of the 15th Pacific Conference on Computer Graphics and Applications, pages 382–390.

{{anchor|FOOT2}} [[#DOCF2|(2)]] Peter J. Burt and Edward H. Adelson, “A Multiresolution Spline With Application to Image Mosaics”, ACM Transactions on Graphics, Vol. 2, No. 4, October 1983, pages 217–236.

{{anchor|FOOT3}} [[#DOCF3|(3)]] Downsampling with a good interpolator reduces noise, which might not desired to judge the image quality of the original-size image. Cropping might be an alternative, though.

{{anchor|FOOT4}} [[#DOCF4|(4)]] In the current implementation a <code>floor(ContrastWindowSize / 2)</code> wide border around the images remains unprocessed and gets a weight of zero.

{{anchor|FOOT5}} [[#DOCF5|(5)]] [http://www.debevec.org/ Paul E. Debevec] defines: “A ''light probe'' image is an omnidirectional, high dynamic range image that records the incident illumination conditions at a particular point in space.”

----

{{anchor|SEC_Contents}}

==Table of Contents==

<div class="contents">

* {{anchor|TOC1}} [[#SEC1|{{NotTOC|1. }}Overview]]
* {{anchor|TOC2}} [[#SEC2|{{NotTOC|2. }}Invocation]]
** {{anchor|TOC3}} [[#SEC3|{{NotTOC|2.1 }}Common Options]]
** {{anchor|TOC4}} [[#SEC4|{{NotTOC|2.2 }}Extended Options]]
** {{anchor|TOC5}} [[#SEC5|{{NotTOC|2.3 }}Fusion Options]]
** {{anchor|TOC6}} [[#SEC6|{{NotTOC|2.4 }}Expert Options]]
** {{anchor|TOC7}} [[#SEC7|{{NotTOC|2.5 }}Option Delimiters]]
* {{anchor|TOC8}} [[#SEC8|{{NotTOC|3. }}Weighting Functions]]
** {{anchor|TOC9}} [[#SEC9|{{NotTOC|3.1 }}Weighting Pixels]]
*** {{anchor|TOC10}} [[#SEC10|{{NotTOC|3.1.1 }}Weighted Average]]
*** {{anchor|TOC11}} [[#SEC11|{{NotTOC|3.1.2 }}Disabling Averaging: Option ‘-- HardMask’]]
** {{anchor|TOC12}} [[#SEC12|{{NotTOC|3.2 }}Exposure Weighting]]
** {{anchor|TOC13}} [[#SEC13|{{NotTOC|3.3 }}Saturation Weighting]]
** {{anchor|TOC14}} [[#SEC14|{{NotTOC|3.4 }}Contrast Weighting]]
*** {{anchor|TOC15}} [[#SEC15|{{NotTOC|3.4.1 }}Standard Deviation]]
**** {{anchor|TOC16}} [[#SEC16|{{NotTOC|3.4.1.1 }}Statistical Moments]]
**** {{anchor|TOC17}} [[#SEC17|{{NotTOC|3.4.1.2 }}Estimators]]
*** {{anchor|TOC18}} [[#SEC18|{{NotTOC|3.4.2 }}Laplacian of Gaussian]]
*** {{anchor|TOC19}} [[#SEC19|{{NotTOC|3.4.3 }}Blend Standard Deviation and Laplacian of Gaussian]]
*** {{anchor|TOC20}} [[#SEC20|{{NotTOC|3.4.4 }}Scaling and Choice of Mode]]
** {{anchor|TOC21}} [[#SEC21|{{NotTOC|3.5 }}Entropy Weighting]]
* {{anchor|TOC22}} [[#SEC22|{{NotTOC|4. }}Understanding Masks]]
** {{anchor|TOC23}} [[#SEC23|{{NotTOC|4.1 }}Masks in Input Files]]
** {{anchor|TOC24}} [[#SEC24|{{NotTOC|4.2 }}Weight Mask Files]]
* {{anchor|TOC25}} [[#SEC25|{{NotTOC|5. }}Tuning Memory Usage]]
* {{anchor|TOC26}} [[#SEC26|{{NotTOC|6. }}Applications of Enfuse]]
** {{anchor|TOC27}} [[#SEC27|{{NotTOC|6.1 }}What Makes Images Fusable?]]
** {{anchor|TOC28}} [[#SEC28|{{NotTOC|6.2 }}Repetition – Noise Reduction]]
** {{anchor|TOC29}} [[#SEC29|{{NotTOC|6.3 }}Exposure Series – Dynamic Range Increase]]
*** {{anchor|TOC30}} [[#SEC30|{{NotTOC|6.3.1 }}Tips For Beginners]]
*** {{anchor|TOC31}} [[#SEC31|{{NotTOC|6.3.2 }}Common Misconceptions]]
** {{anchor|TOC32}} [[#SEC32|{{NotTOC|6.4 }}Flash Exposure Series – Directed Lighting]]
** {{anchor|TOC33}} [[#SEC33|{{NotTOC|6.5 }}Polarization Series – Saturation Enhancement]]
** {{anchor|TOC34}} [[#SEC34|{{NotTOC|6.6 }}Focus Stacks – Depth-of-Field Increase]]
*** {{anchor|TOC35}} [[#SEC35|{{NotTOC|6.6.1 }}Why create focus stacks?]]
*** {{anchor|TOC36}} [[#SEC36|{{NotTOC|6.6.2 }}Preparing Focus Stacks]]
*** {{anchor|TOC37}} [[#SEC37|{{NotTOC|6.6.3 }}Contrast Based Fusing]]
*** {{anchor|TOC38}} [[#SEC38|{{NotTOC|6.6.4 }}Basic Focus Stacking]]
*** {{anchor|TOC39}} [[#SEC39|{{NotTOC|6.6.5 }}Advanced Focus Stacking]]
**** {{anchor|TOC40}} [[#SEC40|{{NotTOC|6.6.5.1 }}A Detailed Look at the Problem]]
**** {{anchor|TOC41}} [[#SEC41|{{NotTOC|6.6.5.2 }}Laplacian Edge Detection]]
**** {{anchor|TOC42}} [[#SEC42|{{NotTOC|6.6.5.3 }}Local Contrast Enhancement]]
**** {{anchor|TOC43}} [[#SEC43|{{NotTOC|6.6.5.4 }}Suppressing Noise or Recognizing Faint Edges]]
*** {{anchor|TOC44}} [[#SEC44|{{NotTOC|6.6.6 }}Tips For Focus Stacking Experts]]
* {{anchor|TOC45}} [[#SEC45|{{NotTOC|7. }}Helpful Additional Programs]]
* {{anchor|TOC46}} [[#SEC46|A. Authors]]
* {{anchor|TOC48}} [[#SEC48|List of Tables]]
* {{anchor|TOC49}} [[#SEC49|List of Figures]]
* {{anchor|TOC50}} [[#SEC50|Program Index]]
* {{anchor|TOC51}} [[#SEC51|Option Index]]
* {{anchor|TOC52}} [[#SEC52|General Index]]

</div>

[[Category:Software:Platform:Linux]]
[[Category:Software:Platform:Windows]]
[[Category:Software:Platform:Mac OS X]]

Hugin Compiling Ubuntu

2008-06-27T20:37:52Z

Seb Przd: Add panoglview

These instructions are work in progress. Initially tested on a blank installation of Kubuntu 6.06 (Edgy Eft) on a AMD64 computer, they have also been tested on Ubuntu 7.04 on a AMD64 computer, Ubuntu 7.10 on an AMD Athlon XP computer and Ubuntu 8.04 on an Intel processor. Apart from the odd change in package name, nothing should be substantially different (and if does not work, please leave a comment on the [http://groups.google.com/group/hugin-ptx hugin-ptx mailing list]). Don't worry if the same package appears twice in an apt-get install line - apt-get will update existing packages if there is a newer version, and ignore duplicates if the latest version is already installed. On the other hand, if apt-get says that it can't find a package, it might be the odd change in package name. You can find a replacement package by using apt-cache search with a substring of the package required, e.g.
<pre>apt-cache search wxW
</pre>

The goal is to build hugin and the whole set of helper applications required.

== Building environment ==
Since we are going to build hugin, libpano13 and enblend we need to download and install all the development packages. This is very easy with apt-get.
In a terminal window (K menu -> System -> Konsole or Applications -> Accessories -> Terminal)

<pre>sudo apt-get install build-essential autoconf automake1.9 libtool flex bison gdb
</pre>

Unless you have an amd64 system prior to 7.10, add the following packages.
<pre>sudo apt-get install libc6-dev libgcc1
</pre>

For older amd64 environments, these are the packages have a slightly different name.
<pre>sudo apt-get install libc6-dev-amd64 lib64gcc1
</pre>

To get the bleeding edge we'll need access to the SVN and CVS repositories, and for this we need the correct tools:
<pre> sudo apt-get install subversion cvs
</pre>

== Building Enblend ==

Get the dependencies. If you are working with large images (300 megapixels and up), you should have a libtiff-devel compiled with large file support and libstdc++6.

<pre>sudo apt-get install pkg-config libtiff4-dev libboost-graph-dev libboost-thread-dev \
liblcms1-dev libglew-dev libplot-dev libglut3-dev libopenexr-dev libopenexr2c2a libxi-dev
</pre>

'''Ubuntu 8.04:''' libopenexr2c2a does not seem to exist, nor to be needed.

Once all dependencies are in place, we get the code from CVS (simply press ENTER when prompted for a password on the login command) and build it.

<pre>cvs -d:pserver:anonymous@enblend.cvs.sourceforge.net:/cvsroot/enblend login
cvs -z3 -d:pserver:anonymous@enblend.cvs.sourceforge.net:/cvsroot/enblend co -P enblend
cd enblend</pre>
We are then ready to compile.
<pre>make -f Makefile.cvs
./configure
make
</pre>

The second make step can be very long and memory consuming. Make sure you have enough swap space, and go get a healthy snack while the computer is compiling.

If you encounter problems at any of these stages, please report back to the hugin-ptx mailing list. Report what command in the sequence you were executing, what machine/operating system, the revision checked out from CVS, and all other relevant information.

You are then ready to install with
<pre>sudo make install</pre>

== Building libpano13 ==
libpano13 is the new version of the PanoTools libraries. This is a necessary component for hugin, and we need to build it first.
To build libpano13 we need some libraries and particularly their <code>dev</code> package:
<pre>sudo apt-get install zlib1g zlib1g-dev libpng12-dev libjpeg62-dev libtiff4-dev</pre>

On older distributions, zlib1g and zlib1g-dev may not be found. In that case, the same library may be available with the names lib64z1 and lib64z1-dev.

We then need to download the source code from SVN:
<pre>svn co https://panotools.svn.sourceforge.net/svnroot/panotools/trunk/libpano libpano13
cd libpano13
./bootstrap</pre>

If any libraries are missing, the script will complain (or at least, let you know that some library hasn't been found). In that case you probably need to install the library. To find in what package is that library, a general rule is to run the command <code>apt-cache search ''missingfile''</code>, find the relevant library and install both the library and the related <code>-dev</code> package.
Run the <code>./configure</code> script and repeat this process until you have met all the dependencies.
Then we are ready to launch the make process with
<pre>make</pre>

If the library successfully compiles, you have to install it with
<pre>sudo make install
sudo ldconfig</pre>
The last part is for the OS to be aware of the new library (that has been installed in <code>/usr/local/lib</code>).
We can now go back up one folder level and get ready for hugin.
<pre>cd ..</pre>

== Building hugin ==

Some additional libraries are needed. We need first to activate the <code>universe</code> repository (in adept package manager, or by editing the /etc/apt/sources.lst file for example).
<pre>sudo apt-get install cmake libopenexr-dev libboost-dev boost-build libboost-thread-dev libboost-graph-dev \
gettext libwxgtk2.8-dev libexiv2-dev libimage-exiftool-perl
</pre>

We download the source from SVN, as before
<pre>svn co https://hugin.svn.sourceforge.net/svnroot/hugin/hugin/trunk/ hugin
cd hugin</pre>

'''Important:''' at the time of writing hugin is under development. The SVN trunk is likely to change often and can sometimes have critical bugs. Try the above first. If it does not work, please report back to the hugin-ptx mailing list. If you need a recent working version of hugin, find out from the mailing list what is the latest working revision number and plug it in after the -r switch in
<pre>svn co -r 2906 https://hugin.svn.sourceforge.net/svnroot/hugin/hugin/trunk/ hugin
cd hugin</pre>

hugin has to be built using cmake (which we installed before).
<pre>cmake -DCMAKE_INSTALL_PREFIX=/usr/local .</pre>

If you compiled and installed libpano to a non standard location set the variables CMAKE_INCLUDE_PATH and CMAKE_LIBRARY_PATH to point to your install location's include and lib directories.

Finally, launch the compilation and installation with
<pre>make
sudo make install
sudo ldconfig</pre>

Reference: [http://theseblog.free.fr/2007/10/building-hugin-in-ubuntu-feisty-fawn.php]

== Building panoglview ==
panoglview is a program that allows you to view an equirectangular image interactively.
You have to install
<pre>sudo apt-get install wx-common</pre>

To build
<pre>svn co https://hugin.svn.sourceforge.net/svnroot/hugin/panoglview/trunk panoglview
cd panoglview
./bootstrap
./configure
make
sudo make install</pre>

== Autopano-sift-C ==

<pre>
sudo apt-get install libxml2-dev
svn co https://hugin.svn.sourceforge.net/svnroot/hugin/autopano-sift-C/trunk/ autopano-sift-C
cd autopano-sift-C
cmake -DCMAKE_INSTALL_PREFIX=/usr/local .
make
sudo make install</pre>

== Match-n-shift ==

Match-n-shift is yet an other Autopano-SIFT replacement. It comes in a bundle with pto file manipulation perl libraries and a rich selection of other tools that use nona, enblend, ImageMagick among other things. To use match-n-shift, you need to install at least the [http://search.cpan.org/dist/Panotools-Script/ Panotools::Script] library and some other perl modules. It requires:

* Math::Matrix 0.4
* Image::Size 2.9
* Storable 2.0

Chances are that you do not need to update Storable which is a standard perl module. To check the version of installed versions of these modules, write these lines to the command prompt:

perl -MStorable -le 'print Storable->VERSION;'
perl -MMath::Matrix -le 'print Math::Matrix->VERSION;'
perl -MImage::Size -le 'print Image::Size->VERSION;'

There are various ways to install or upgrade these modules. Ubuntu has binary packages for many perl modules but unfortunately not for Math::Matrix. Perl is
interpreted language and these modules are pure perl, so installing
from source is an easy thing.

The best place to install perl modules is directly from a CPAN archive. CPAN is short for Comprehensive Perl Archive Network. The program to interact with CPAN comes with all perl installations. Start it by running:

sudo cpan

If this is your first time running the program you will be asked a number of questions (you can safely accept the suggested values). Last question lets you select a number of CPAN mirrors nearest to you.

When all is done, you can enter the install commands after the 'cpan>' prompt:

install Math::Matrix Image::Size Storable

Answer 'y' to any question of dependencies and wait for install to complete. 'exit' leaves the cpan shell.

If you rather use Ubuntu packages to install as much as you can, you can skip the Image::Size installation above and type:

sudo apt-get install libimage-size-perl

Lastly, you can download Math::Matrix tar ball from CPAN: http://search.cpan.org/~ulpfr/Math-Matrix-0.5/ and follow the installation instructions in the tar ball file.

Next, you need to retrive and install the Panotools-Script collection
of perl libraries (Panotools::Script) and programs that use them -
including match-n-shift:

svn co https://panotools.svn.sourceforge.net/svnroot/panotools/trunk/Panotools-Script Panotools-Script
cd Panotools-Script
perl Makefile.PL
make
make test
sudo make install

Just to confuse you, you can also ignore everything above and just install Panotools::Script and all its dependencies from CPAN. From command line, type:

sudo cpan Panotools::Script

You can run match-n-shift from command line using the same parameters as autopano-c-complete.sh or you can modify hugin to run it for you:

* start Hugin
* navigate the menu File to Preferences
* In the Preferences window, open the Autopano tab
* Select Autopano -> Autopano-SIFT
* tick the checkbox for Use alternative Autopano-SIFT program
* enter the full path to match-n-shift (/usr/local/bin/match-n-shift) in the Autopano-SIFT field
* enter the following string in the Arguments field:
-f %f -v %v -c -p %p -o %o %i

[[Category:Software:Hugin]]
[[Category:Software:Platform:Linux]]

== MatchPoint ==

MatchPoint is a next generation CP generator. The result of a GSoC2007 project, it is still very experimental. Experience reports needed. Read more [http://groups.google.com/group/hugin-ptx/browse_thread/thread/cba2b2ce94dd9054 here]

Matchpoint is now located inside the main hugin source tree, no need to checkout https://hugin.svn.sourceforge.net/svnroot/hugin/gsoc07_featuredetection anymore. It is compiled together with hugin, but not installed by default.

* copy the MatchPoint executable into /usr/local/bin manually
*:<pre>
*: sudo cp src/matchpoint/matchpoint /usr/local/bin/
*:</pre>
* edit /usr/local/bin/autopano-c-complete.sh (do it with sudo to have the necessary permission)
** line 79: replace the .key.gz extension with .key (not sure if matchpoint supports compression)
** lines 83 and 88: replace '''generatekeys "$arg" $FILENAME $SIZE''' with '''matchpoint "$arg" $FILENAME''' (not sure if the size option or any other options of the original generatekeys are applicable)

== Exiftool ==

To get the bleeding edge

<pre>
$ sudo apt-get remove libimage-exiftool-perl
$ wget http://www.sno.phy.queensu.ca/~phil/exiftool/Image-ExifTool-7.21.tar.gz (replace the version with the latest from the homepage)
$ tar -xzf Image-ExifTool-#.##.tar.gz
$ cd Image-ExifTool-#.##
$ perl Makefile.PL
$ make test
$ sudo make install
</pre>

Talk:Enblend Testcase 2008-05-02

2008-05-19T14:12:09Z

Seb Przd:

What happens if you use the option --fine-mask ?
[[User:Seb Przd|Seb Przd]] 16:12, 19 May 2008 (CEST)

Talk:Enblend Testcase 2008-05-02

2008-05-19T14:09:48Z

Seb Przd: New page: What happens if you use the option --fine-mask ?

What happens if you use the option --fine-mask ?

SoC 2008 application

2008-03-06T06:36:28Z

Seb Przd: /* Steering Comittee */ typo

=== Describe your organization ===
=== Why is your organization applying to participate in GSoC 2008? What do you hope to gain by participating? ===

http://www.flickr.com/search/groups/?q=hugin

http://www.flickr.com/photos/sbprzd/2126554118/

http://www.flickr.com/photos/sbprzd/2125768589/

=== Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation. ===
=== If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)? ===
=== Who will your organization administrator be? Please include Google Account information. ===
=== What license(s) does your project use? ===

Both hugin, enblend/enfuse, panotools and matchpoint use GPL v2 or above.

=== What is the URL for your ideas page? ===

http://wiki.panotools.org/SoC_2008_ideas

=== What is the main development mailing list or forum for your organization? ===

http://lists.sourceforge.net/lists/listinfo/panotools-devel

=== What is the main IRC channel for your organization? ===

We do not use IRC for communication. During GSoC 2007 we used Skype, but this is unlikely to happen again.

=== Does your organization have an application template you would like to see students use? If so, please provide it now. ===

=== Who will be your backup organization administrator? Please include Google Account information. ===
Yuval Levy is chosen to be backup admin. He did a perfect job as primary administrator during GSoC 2007.

=== Who will your mentors be? Please include Google Account information. ===

'''Pablo d'Angelo'''

Pablo d'Angelo is the initiator and main developer of the hugin project. He has studied computer engineering at the University of applied sciences Ulm, and is currently working at the DaimlerChrysler Research Center in Ulm, where he does research on advanced 3D reconstruction techniques for industrial quality inspection. He is also working towards a PhD in the field of computer vision at the University of Bielefeld, which will likely be granted in Summer 2007.

''' Andrew Mihal '''

''' Jim Watters '''

Jim Watters is a Software Engineer at JFL Peripheral Solution, in Ottawa, Ontario, Canada, where he designs software for scanners. An avid user of PanoTools since 2000. A growing contributer to the source code of PanoTools since Aug 2003 and a current maintainer of PanoTools (http://panotools.sourceforge.net). Before receiving his degree in Computer Software in 1999, he received a diploma of Fine Art in Photography in 1990.

Most recently his attention has been directed to creating Immersive Panoramic Video.

''' Daniel M German '''

He is assistant professor at the Department of Computer Science at the University of Victoria, in British Columbia, in Canada. He received his PhD in Computer Science from the University of Waterloo in Canada.

One of his areas of research is open source software development. He is interested in understanding how globally distributed individuals are able to work together to create commercial strength software. He has also explored the use of historical artifacts (such as version control logs, emails, defect tracking) to understand how a system has evolved and how this information can be used to continue its development.

More recently he has been interested in the field of computational photography. More specifically on how to project extreme wide-angle images and spherical panoramas into acceptable flat representations.

During the last year he has been the maintainer of Panotools (http://panotools.sourceforge.net).

As a university professor one of his jobs is the supervision of students. He has graduated 6 Master's students, and currently supervising 3 Master's, and 1 Ph.D. Student. He has supervised more than a dozen honours projects of undergraduate students in computer science.

He is an avid photographer. His works have been exhibited in several galleries.

''' Alexandre Jenny '''

=== What criteria did you use to select these individuals as mentors? Please be as specific as possible. ===
=== Steering Comittee ===

This year we also have a steering comittee - a group of professionals in panorama making.

'''Ken Turkowski'''

'''Bruno Postle'''

'''Thomas Rauscher'''

'''G. Donald Bain'''

G. Donald Bain manages the Geography Computing Facility at the University of California Berkeley, where he also teaches cartography and field studies. The rest of the time he devotes to VR.

Hi is a board member of IVRPA.

He travels and take panoramas for his web site: [http://virtualguidebooks.com/ Don Bain's Virtual Guidebooks]. This project (his wife refers to it as his obsession) has taken him from Tahiti to the Arctic, from the prehistoric ruins of the Southwest to the glaciers of the Canadian Rockies. As a compulsive educator it has been a real treat, documenting and sharing his landscapes with the world. He has taken over 4000 panoramas, with about 3500 currently on the site.

He co-founded the World Wide Panorama, the largest international collaborative effort showcasing over 3000 panoramas from VR-artists all over the world taken over 11 editions.

=== What is your plan for dealing with disappearing students? ===
=== What is your plan for dealing with disappearing mentors? ===
=== What steps will you take to encourage students to interact with your project's community before, during and after the program? ===
=== What will you do to ensure that your accepted students stick with the project after GSoC concludes? ===

[[Category:Community:Project]]

PTStitcher

2008-02-08T12:54:34Z

Seb Przd: Typo fix

{{Glossary|Main panorama tools stitcher application. Script driven.}}
== Preface ==
PTStitcher is one of the core applications of [[Panorama tools]], together with [[PTOptimizer]] and the [[Panorama Tools Plugins]].

For stitching panoramas you most probably won't get in contact with PTStitcher frequently, since the scripting is more or less completely done by the various [[GUI front-ends]] and some tools like [[PanoCube]].

However, there are several occasions where you might need to write or at least understand the scripts or call PTStitcher directly (for some batch tasks f.e.).

== Updates ==
The PTStitcher source code was never published, hence there are no changes possible to certain functions. But since a considerable part of it's functionality is in [[pano12]] library, PTStitcher benefits from every update of this core library.

You can take PTStitcher from any of the panotools distribution on one of the [[Mirrors]]. In order to use new functionality you need a recent copy of [[pano12]] library. Note that only ''win32'', ''i386 Linux'' and ''mac classic'' binary versions were ever made available, so you are out of luck if you use ''OS X'' or a 64bit operating system.

There is an open source replacement for PTStitcher called [[nona]] in the [[hugin]] project which has much (but not all) of the PTStitcher features. Another open source replacement is [[PTmender]], part of the [[pano12]] project at sourceforge.

== Intro ==
PTStitcher is script driven. The scripts are in pure text format and can be edited with any text or programming editor (on windows notepad will do).

They are processed on a line by line basis. Each line starts with a special character (case sensitive) that indicates the meaning of the rest of the line. All other first in line characters are ignored and considered comments.

== Features ==
Most features of PTStitcher are conveniently accessible by the usual GUIs ([[#Preface|see top]]), but some are not.

=== Accessible by GUI ===
PTStitcher can stitch
* [[Equirectangular Projection|spherical (equirectangular)]], [[Cylindrical Projection|cylindrical]], [[Rectilinear Projection|rectilinear]] and [[Fisheye Projection|fisheyed (or mirror ball)]] panoramas
* multi row panoramas
* panoramas from images that where shot tilted up or down.
* images from any lens (including spherical mirrors)
* images with different [[Focal Length]] into one panorama
* [[How to stitch flat images|flat images]] like scanned maps.

The capabilities of PTStitcher go far beyond panorama stitching: It can be used
* to remap images between different [[Projections]]
* to [[Extracting and inserting rectilinear Views|extract and insert rectilinear images]] from a spherical or cylindrical panorama.
* to [[Edit zenith and nadir in one go with PTGui|remap a spherical panorama]] such that [[Nadir]] and [[Zenith]] are editable.
* to down- or [[Upsampling a single image with ptstitcher|upsample images]] with high quality interpolators.
* to [[Perspective correction|correct perspective distortion]].

=== Accessible by Script or other Tool ===
PTStitcher can be used stand alone or with some other (non-GUI) Tool:
* together with some tool that separate color channels ([[ImageMagick]]) to correct [[Chromatic aberration]]
* assembling 6 cube faces to an equirectangular panorama can be done by GUI but is more conveniently done by script, [http://www.pinlady.net/vr/#anchor3 batch file] or [[PanoCube|PanoCube Plus]].

== Example Script ==
The updated original example script with lots of comments is below. Copied from [http://photocreations.ca/panotools/stitch.txt Jim Watters' page]
<pre>
############# Example Script ##########################
# to run PTStitcher
#
#
# Only lines starting with 'p','o', i', or 'm' are read,
# so you can add comments and info as you like by using
# other line starting characters.
# The * character at the first of a line indicated the end of the script file.

# The stitcher script must contain:
# one 'p'- line describing the output image (eg Panorama)
# one 'o'-line for each input image
# one 'i' line for each input image that is optional
# the 'm'-line is optional and allows you to specify modes for the optimization.
# the 'C'-line is optional and allows morphing of control points.
</pre>
=== p-line options ===
<pre>
# 'p'-line options
# w1000 width in pixels
# h600 height in pixels (default: width/2)
# f0 projection format,
# 0 - rectilinear (for printing and viewing)
# 1 - Cylindrical (for Printing and QTVR)
# 2 - Equirectangular ( for Spherical panos), default
# 3 - full-frame fisheye
# v360 horizontal field of view of panorama (default 360)
# nPICT Panorama file format, one of:
# PICT pict-file on macs, bmp-file on win (default)
# PSD single layer Photoshop file, 48bits supported
# PNG png-format, 48bits supported
# TIFF tiff-format, 48bits supported
# PSD_mask Photoshop file, one image per layer
# + shape mask & feathered clip mask at overlap center
# PSD_nomask Photoshop file, one image per layer,
# TIFF_mask tiff-format, multi-file, one image per file, 48bit supported
# alpha layer with feathered clip mask at overlap center
# TIFF_m tiff-format, multi-file, one image per file, 48bit supported
# alpha layer with non-feathered clip mask at image border
# + shape mask & non-feathered clip mask at image border
# JPEG Panoramic image in jpeg-format. Use with f1
# for IBM Hotmedia panoramas.
# PAN SmoothMove movie. Use only with f2.
# IVR LivePicture IVR movie
# cylindrical (format f1) or spherical (format f2)
# IVR_java LivePicture Java Panorama,
# cylindrical (format f1) or spherical (format f2)
# VRML VRML background node, use only with f2 for panoramas, or
# VRML-object for PTStereo
# QTVR Apple QTVR-panomovie. Use only with f1
# 3DMF 3DMF-object (PTStereo).
#
# n"QTVR w400 h300 c1" additional viewer options in a quoted string together with format
# the following options are recognized:
# w(width) and h(height) of viewer window (only QTVR on Macs)
# c(codec: 0-JPEG, 1-Cinepak, 2-Sorenson) (only QTVR on Macs)
# q(codec quality):
# 0-high,1-normal,2-low QTVR on Macs
# 0-100(highest) on other jpeg-formats (PAN, IVR, IVR_java, VRML)
# g progressive jpeg (0-no, 1-yes) (PAN, IVR, IVR_java, VRML)
# Optimized JPEG (0-on(default), 2-disabled), (3-progressive with optimized disabled)
# p initial pan angle ( QTVR on Macs, VRML, IVR)
# v field of view (QTVR, VRML, IVR)
# Many more options can be set by editing the viewer scripts
# u10 width of feather for stitching all images. default:10
# k1 attempt color & brightness correction using image number as anchor
# b1 attempt brightness correction with no color change using image number as anchor
# d1 attempt color correction with no brightness change using image number as anchor
# Do not use more than one of k, d, b.This is new method of correcting

p w800 nPSD_mask
</pre>
=== i-line options ===
<pre>
# The 'i' lines describe input images and is optional
# nName file name of the input image.
# over ridable with command line parameters to PTStitcher

i n"photo1.jpg"
</pre>
=== o-line options ===
<pre>
# The 'o' lines describe input images. One line per image is required
# The width and height of the image is obtained from image
# f0 projection format,
# 0 - rectilinear (normal lenses)
# 1 - Panoramic (Scanning cameras like Noblex)
# 2 - Circular fisheye
# 3 - full-frame fisheye
# 4 - PSphere, equirectangular
# v82 horizontal field of view of image (required)
# y0 yaw angle (required)
# p43 pitch angle (required)
# r0 roll angle (required)
# a,b,c lens correction coefficients (optional)
# (see http://www.fh-furtwangen.de/~dersch/barrel/barrel.html)
# d,e initial lens offset in pixels(defaults d0 e0, optional).
# Used to correct for offset from center of image
# d - horizontal offset,
# e - vertical offset
# g,t initial lens shear. Use to remove slight misalignment
# of the line scanner relative to the film transport
# g - horizontal shear
# t - vertical shear
# +buf (obsolete, -buf and +buf are now ignored when stitching)
# load and merge image with buffer
# -buf (obsolete, -buf and +buf are now ignored when stitching)
# save result to buffer. The first 'o' line should
# contain one '-buf' command, the last line one '+buf'
# command, and all other lines both '+buf -buf'
# Exception: remove all 'buf' commands when
# creating Photoshop-files to preserve the original images.
# u10 (obsolete, globally used on p line) width of feather for stitching. default:10
# S100,600,100,800 Selection(l,r,t,b), Only pixels inside the rectangle will be used for conversion.
# Original image size is used for all image parameters
# (e.g. field-of-view) refer to the original image.
# Selection can be outside image dimension.
# C100,600,100,800 Crop(l,r,t,b), Only pixels inside the rectangle will be used for conversion.
# Cropped image size is used for all image parameters
# (e.g. field-of-view) refer to the cropped part of the image.
# m20 (obsolete, use S & C) ignore a frame 20 pixels wide. default: 0
# mx100 (obsolete, use S & C) crop to brightest rectangle with size 100x200;
# my200 (obsolete, use S & C) used only for circular fisheye images (f2)
# s0 (obsolete, ignored, always blend) specify placement of seam between buffer and image:
# 0-middle of overlap('blend' ,default)
# 1- at edge of image ('paste').
# o (the small letter). Morph-to-fit using control points.
# k0 (obsolete, use p line correction still used with plugin)
# attempt color/brightness correction when merging image and buffer, one of:
# 0 - no correction(default);
# 1 - change image;
# 2 - change buffer;
# 3 - change both
# this feature does not work very well!

o f2 r0 p0 y0 v183 a0 b-0.1 c0 S100,600,100,800
o f2 r0 p0 y180 v183 a0 b-0.1 c0 S100,600,100,800
</pre>
=== m-line options ===
<pre>
# 'm'-line options
# ----------------
# Set mode for stitcher, not required
#
# g2.5 Set gamma value for internal computations (default 1.0)
# See <http://www.fh-furtwangen.de/~dersch/gamma/gamma.html>
# i2 Set interpolator, See <http://www.fh-furtwangen.de/~dersch/interpolator/interpolator.html>
# one of:
# 0 - poly3 (default)
# 1 - spline16,
# 2 - spline36,
# 3 - sinc256,
# 4 - spline64,
# 5 - bilinear,
# 6 - nearest neighbor,
# 7 - sinc1024
# \/ antialiasing filters \/ See <http://www.pano2qtvr.com/dll_patch/>
# 8 - Box
# 9 - Bartlett/Triangle
# 10 - Hermite
# 11 - Hanning
# 12 - Hamming
# 13 - Blackmann
# 14 - Gaussian 1/sqrt(2)
# 15 - Gaussian 1/2
# 16 - Quadardic
# 17 - Cubic
# 18 - Catmull-Rom
# 19 - Mitchell
# 20 - Lanczos2
# 21 - Lanczos3
# 22 - Blackman/Bessel
# 23 - Blackman/sinc
#
# f0 Invoke Faster Transformation also invoked by creating a file named "pano12_opt.txt"
# in the same foler as project with a line FAST_TRANSFORM

m g1.5 i6 f0
</pre>
=== z-line options ===
<pre>
# 'z'-lines options
# ----------------
# Extended Depth-Of-Field, not required
#
# Automatically determine, for every point in a picture, which of mumerous overlapping
# images has best focus. Masks are generated to reveale the best focused parts of
# each image. Feathering must be selected. Used with PSD_mask or TIFF_mask file format
# to edit the mask or with flattened file formats for flattened final result. Does not
# work if color and/or brightness correction are invoked.
#
# m2 mask type
# m0 hard-edged masks, mutually exclusive
# m1 hard-edged masks, stack of nested masks
# m2 blended masks, stack of nested masks (default & strongly recommended)
# (this option includes a smoothing computation that seems to help a lot.)
# fN focus estimation window size, N = halfwidth of window.
# Recommended value is 0.5% of image width, e.g. 4 pixels for an 800-pixel image.
# Computation cost for focus estimation increases proportional to N^2. Default f4.
# sN smoothing window size, N = halfwidth of window.
# Recommended value is 0.5% of image width, e.g. 4 pixels for an 800-pixel image.
# Computation cost for smoothing increases proportional to N^2. Default s4.

z m2 f4 s4
</pre>
=== C-line options ===
<pre>
# 'C' lines
# ----------------
# Morphing of control point lines
# One line per point
# Created automatically by optimizer
#
# i0 image
# x363.726 starting x point position
# y125.738 starting y point position
# X363.838 morphed x point position
# Y125.618 morphed y point position

C i0 x363.726 y125.738 X363.838 Y125.618

*
Every thing after * is ignored.

Enfuse

2008-02-03T13:12:23Z

Seb Przd: /* Known bugs */ enfuse 360° fixed in SVN

[[Image:2125768589_b.jpg|thumb|[[:Image:2125768589_b.jpg|Four exposure panorama blended with enfuse]]]]
Enfuse is {{glossary|a command-line program used to merge different exposures of the same scene to produce an image that looks very much like a [[Tone_mapping|tonemapped]] image (without the [[Halo|halos]]) but requires no creation of an [[HDR]] image|1}}. Therefore it is much simpler to use and allows the creation of very large multiple exposure panoramas.

Enfuse is based on a paper by Tom Mertens, Jan Kautz and Frank Van Reeth: [http://research.edm.uhasselt.be/~tmertens/papers/exposure_fusion_reduced.pdf "Exposure fusion"] The implementation was done by Andrew Mihal (developer of [[Enblend]]) and the [[hugin]] team around [[User:Pablo|Pablo d'Angelo]]

== State of development ==
Enfuse is currently in beta and available with the development version of [[Enblend]] from [http://panospace.wordpress.com/downloads/ panospace.wordpress] (scroll down on that page).

=== Known bugs ===
* '''Windows version only''': if used on too many and/or too large files enfuse terminates with an error message: <code>an exception occured [...] unable to create image swap file</code>
:: - fixed in version linked above

* If used on images with unaligned alpha mask (result of aligning handheld shots) there might be colored or dark spots.
: Workaround: crop the aligned images.
:: - fixed in version linked above

* If contrasty structures are near [[zenith]] or [[nadir]] in an [[equirectangular]] image, there might be an artifact (vortex) in the resulting pano.
: Workaround: use on zenith and nadir images separately and stitch them in the resulting pano afterwards.
:: - unknown, whether could be fixed easily

* actually not a bug: Default compression for [[JPEG]] output is relatively low.
: Workaround: Specify <code>--compression=100</code> on the command line if you need JPEG output.
:: - fixed in version linked above (defaults to 98)

* [[wikipedia:LZW|LZW]] compression for [[TIFF]] files is not supported if an older version of libtiff has been used. For various reasons most/all existing Windows binaries have this problem (Jan 2008). Fixed in version linked above.
: Workaround: use [[wikipedia:DEFLATE|DEFLATE]] (ZIP) compression instead.

* A slight seam (brightness difference) along the 360° joint of an [[equirectangular]] panorama, if there was a contrasty structure near the edge, even if the -w option was used.
: Workaround: use enfuse before stitching.
:: - fixed in SVN 3 February 2008.

== Description ==
Enfuse merges overlapping images using the Mertens-Kautz-Van Reeth exposure fusion algorithm. This is a quick way to produce blend differently exposed images into a nice output image, without producing intermediate [[HDR]] images that are then tonemapped to a viewable image. This simplified process often works much better than the currently known tonemapping algorithms.

Enfuse can also be used to build extended [[Depth_of_Field|DOF]] images, by blending a focus stack.

The basic idea is that pixels in the input images are weighted according to qualities such as proper exposure, good contrast, and high saturation. These weights determine how much a given pixel will contribute to the final image. A Burt & Adelson multiresolution spline blender is used to combine the images according to the weights. The multiresolution blending ensures that transitions between regions where different images contribute more heavily are difficult to see.

Enfuse uses three different criteria to judge the quality of a pixel: Exposure, saturation, and contrast. The exposure criteria favors pixels with luminance close to the middle of the range. These pixels are considered better-exposed than those with high or low luminance levels. The saturation criteria favors highly-saturated pixels. The contrast criteria favors high-contrast pixels. The local gray or color value standard deviation is used as a contrast measure. The Mertens-Kautz-Van Reeth paper suggest using a laplacian filter, but the standard deviation produces much better results for differently focussed images.

You can adjust how much importance is given to each criteria by setting the weight parameters on the command line. For example, if you set --wExposure=1.0 and --wSaturation=0.5, Enfuse will favor well-exposed pixels over highly-saturated pixels when blending the source images. The impact of these parameters on the final result will not always be clear. The quality of the result is subject to your artistic interpretation. Playing with the weights may or may not give you a more pleasing result. I encourage you to experiment (perhaps using downsized images for speed).

Enfuse expects each input image to have an alpha channel. By setting the alpha values of pixels to zero, users can manually remove those pixels from consideration when blending. If an input image lacks an alpha channel, Enfuse will print a warning and continue assuming all pixels should contribute to the final output. Any alpha value other than zero is interpreted as "this pixel should contribute to the final image".

== Usage ==
The usage below refers to the CVS version of the 21 Dec 2007. Use enfuse as follows:
enfuse <options> <input files>.
Input files can be a list of files or a wildcard (on windows f.e. <code>IMG*.jpg</code> for all jpg images that begin with IMG.

=== Common options ===

-h
Print information on the available options.
-l num
Use exactly this many levels for pyramid blending. A low number trades off quality of results for faster execution time and lower memory usage. The default is to use as many levels as possible given the source image size. If you specify a high number Enfuse may still use a smaller number of levels if the geometry of the images demands it.
-o output-file
Required. Specify the name of the output file.
-v
Verbose output.
-w
Blend around the -180/+180 boundary. Useful for full-360 panoramas. Enfuse currently does not blend the zenith or the nadir, so you may still see some seams in these areas.
--compression=COMP
Write a compressed output file. Valid values are [[LZW]] and [[DEFLATE]] for TIFF files, and numbers from 0-100 for JPEG files.

=== Extended options ===

-b kilobytes
Set the block size for Enfuse's image cache. This is the amount of data that Enfuse will move to and from the disk in one go. The default is 2 MiB which should be good for most systems.
-c
Use the CIECAM02 color appearance model for blending colors. Your input TIFF files should have embedded ICC profiles. If no ICC profile is present, Enfuse will assume that image uses the sRGB color space. The difference between using this option and Enfuse's default color blending algorithm is very slight, and will be most noticeable when you need to blend areas of different primary colors together.
-g
Gimp (ver. < 2) and Cinepaint exhibit unusual behaviors when loading images with unassociated alpha channels. Use the -g flag to work around this. With this flag Enfuse will create the output image with the associated alpha tag set, even though the image is really unassociated alpha.
-f WIDTHxHEIGHT+x0+y0
Set the size and position of the output image manually. This is useful when the input images are cropped TIFF files, such as those produced by Nona.
-m megabytes
Set the size of Enfuse's image cache. This is the amount of memory Enfuse will use for storing image data before swapping to disk. The default is 1 GiB.

=== Fusion options ===
<code>W</code> is a number between 0 (no weight) and 1 (full weight)
--wExposure=W
Sets the relative weight of the well-exposedness criteria. Increasing this weight relative to the others will make well-exposed pixels contribute more to the final output.
--wSaturation=W
Sets the relative weight of high-saturation pixels. Increasing this weight makes pixels with high saturation contribute more to the final output.
--wContrast=W
Sets the relative weight of high-contrast pixels.

=== Expert options ===

--ContrastWindowSize=s
Window size for local contrast analysis. Values larger than 5 might result in increased computation times. Values in the range of 3 to 7 have given good results on focus stacks. The impact on the result quality is not easy to define. You will have to experiment.

--HardMask
Force hard blend masks on the finest scale. This avoids averaging of fine details (only), at the expense of increasing the noise. This improves the sharpness of focus stacks considerably.

--debug
Output intermediate images for debugging.

[[Category:Software:Platform:Mac OS X]]
[[Category:Software:Platform:Linux]]
[[Category:Software:Platform:Windows]]

Hugin Compiling Ubuntu

2008-01-21T14:01:00Z

Seb Przd:

Enfuse

2007-12-21T15:59:28Z

Seb Przd: Added download link for windows

[[Image:2125768589_b.jpg|thumb|[[:Image:2125768589_b.jpg|Four exposure panorama blended with enfuse]]]]
Enfuse is a command-line program used to merge different exposures of the same scene to produce an image that looks very much like a tonemapped image (without the halos) but requires no creation of an HDR image. Therefore it is much simpler to use and allows the creation of very large multiple exposure panoramas.

Enfuse is based on a paper by Tom Mertens, Jan Kautz and Frank Van Reeth. The implementation was done by Andrew Mihal (developer of [[Enblend]]) - http://research.edm.uhasselt.be/~tmertens/exposure_fusion/

Enfuse is currently in beta and available with the development version of [[Enblend]] http://hugin.panotools.org/testing/enblend/enblend-3.1_win32_pre3.zip

== Description ==
Enfuse merges overlapping images using the Mertens-Kautz-Van Reeth exposure fusion algorithm. This is a quick way to produce blend differently exposed images into a nice output image, without producing intermediate HDR images that are then tonemapped to a viewable image. This simplified process often works much better than the currently known tonemapping algorithms.

Enfuse can also be used to build extended DOF images, by blending a focus stack.

The basic idea is that pixels in the input images are weighted according to qualities such as proper exposure, good contrast, and high saturation. These weights determine how much a given pixel will contribute to the final image. A Burt & Adelson multiresolution spline blender is used to combine the images according to the weights. The multiresolution blending ensures that transitions between regions where different images contribute more heavily are difficult to see.

Enfuse uses three different criteria to judge the quality of a pixel: Exposure, saturation, and contrast. The exposure criteria favors pixels with luminance close to the middle of the range. These pixels are considered better-exposed than those with high or low luminance levels. The saturation criteria favors highly-saturated pixels. The contrast criteria favors high-contrast pixels. The local gray or color value standard deviation is used as a contrast measure. The Mertens-Kautz-Van Reeth paper suggest using a laplacian filter, but the standard deviation produces much better results for differently focussed images.

You can adjust how much importance is given to each criteria by setting the weight parameters on the command line. For example, if you set --wExposure=1.0 and --wSaturation=0.5, Enfuse will favor well-exposed pixels over highly-saturated pixels when blending the source images. The impact of these parameters on the final result will not always be clear. The quality of the result is subject to your artistic interpretation. Playing with the weights may or may not give you a more pleasing result. I encourage you to experiment (perhaps using downsized images for speed).

Enfuse expects each input image to have an alpha channel. By setting the alpha values of pixels to zero, users can manually remove those pixels from consideration when blending. If an input image lacks an alpha channel, Enfuse will print a warning and continue assuming all pixels should contribute to the final output. Any alpha value other than zero is interpreted as "this pixel should contribute to the final image".

== Usage ==
The usage below refers to the CVS version of the 21 Dec 2007.

=== Common options ===

-h
Print information on the available options.
-l num
Use exactly this many levels for pyramid blending. This trades off quality of results for faster execution time and lower memory usage. The default is to use as many levels as possible given the size of the overlap region. Enfuse may still use a smaller number of levels if the geometry of the images demands it.
-o output-file
Required. Specify the name of the output file.
-v
Verbose output.
-w
Blend around the -180/+180 boundary. Useful for full-360 panoramas. Enfuse currently does not blend the zenith or the nadir, so you may still see some seams in these areas.
--compression=COMP
Write a compressed output file. Valid values are LZW and DEFLATE for TIFF files, and numbers from 0-100 for JPEG files.

=== Extended options ===

-b kilobytes
Set the block size for Enfuse's image cache. This is the amount of data that Enfuse will move to and from the disk in one go. The default is 2 MiB which should be good for most systems.
-c
Use the CIECAM02 color appearance model for blending colors. Your input TIFF files should have embedded ICC profiles. If no ICC profile is present, Enfuse will assume that image uses the sRGB color space. The difference between using this option and Enfuse's default color blending algorithm is very slight, and will be most noticeable when you need to blend areas of different primary colors together.
-g
Gimp (ver. < 2) and Cinepaint exhibit unusual behaviors when loading images with unassociated alpha channels. Use the -g flag to work around this. With this flag Enfuse will create the output image with the associated alpha tag set, even though the image is really unassociated alpha.
-f WIDTHxHEIGHT
Set the size of the output image manually. This is useful when the input images are cropped TIFF files, such as those produced by Nona.
-m megabytes
Set the size of Enblend's image cache. This is the amount of memory Enblend will use for storing image data before swapping to disk. The default is 1 GiB.

=== Fusion options ===

--wExposure
Sets the relative weight of the well-exposedness criteria. Increasing this weight relative to the others will make well-exposed pixels contribute more to the final output.
--wSaturation
Sets the relative weight of high-saturation pixels. Increasing this weight makes pixels with high saturation contribute more to the final output.
--wContrast
Sets the relative weight of high-contrast pixels.

=== Expert options ===

--ContrastWindowSize
Window size for local contrast analysis. Values larger than 5 might result in a blurry composite and increased computation times. Values in the range of 3 to 5 have given good results on focus stacks.

--HardMask
Force hard blend masks on the finest scale. This avoids averaging of fine details (only), at the expense of increasing the noise. This improves the sharpness of focus stacks considerably.

== See also ==
* [http://www.nabble.com/A-christmas-present-td14438390.html Announcement on Panotools-NG]

Align image stack

2007-12-21T15:55:45Z

Seb Przd:

align_image_stack is a command-line tool available in the development version of [[hugin]] to align overlapping images to facilitate HDR creation.

This article is a stub.

== Usage ==
align_image_stack [options] input files
=== Options: modes of operation ===
-p file
Output .pto file (useful for debugging, or further refinement)"
-a prefix
Align images, output as prefix_xxxx.tif
-o output
Merge images to HDR, generate output.hdr
=== Options: modifiers ===
-v
Verbose, print progress messages
-t num
Remove all control points with an error higher than num pixels (default: 3)
-f HFOV
Approximate horizontal field of view of input images, use if EXIF info not complete
-m
Optimize field of view for all images, execpt for first. Useful for aligning focus stacks with slightly different magnification
-c num
Number of control points to create between adjectant images (default: 200)
-h
Display help.

Align image stack

2007-12-21T15:54:56Z

Seb Przd: Usage

align_image_stack is a command-line tool available in the development version of [[hugin]] to align overlapping himages to facilitate HDR creation.

This article is a stub.

== Usage ==
align_image_stack [options] input files
=== Options: modes of operation ===
-p file
Output .pto file (useful for debugging, or further refinement)"
-a prefix
align images, output as prefix_xxxx.tif
-o output
merge images to HDR, generate output.hdr
=== Options: modifiers ===
-v
Verbose, print progress messages
-t num
Remove all control points with an error higher than num pixels (default: 3)
-f HFOV
approximate horizontal field of view of input images, use if EXIF info not complete
-m
Optimize field of view for all images, execpt for first. Useful for aligning focus stacks with slightly different magnification
-c num
number of control points to create between adjectant images (default: 200)
-h
Display help.

Align image stack

2007-12-21T15:44:28Z

Seb Przd: New page: align_image_stack is a tool available in hugin. This article is a stub.

align_image_stack is a tool available in [[hugin]].

This article is a stub.

Enfuse

2007-12-21T15:40:52Z

Seb Przd:

[[Image:2125768589_b.jpg|thumb|[[:Image:2125768589_b.jpg|Four exposure panorama blended with enfuse]]]]
Enfuse is a command-line program used to merge different exposures of the same scene to produce an image that looks very much like a tonemapped image (without the halos) but requires no creation of an HDR image. Therefore it is much simpler to use and allows the creation of very large multiple exposure panoramas.

Enfuse is based on a paper by Tom Mertens, Jan Kautz and Frank Van Reeth. The implementation was done by Andrew Mihal (developer of [[Enblend]]) - http://research.edm.uhasselt.be/~tmertens/exposure_fusion/

Enfuse is currently in beta and available with the development version of [[Enblend]].

== Description ==
Enfuse merges overlapping images using the Mertens-Kautz-Van Reeth exposure fusion algorithm. This is a quick way to produce blend differently exposed images into a nice output image, without producing intermediate HDR images that are then tonemapped to a viewable image. This simplified process often works much better than the currently known tonemapping algorithms.

Enfuse can also be used to build extended DOF images, by blending a focus stack.

The basic idea is that pixels in the input images are weighted according to qualities such as proper exposure, good contrast, and high saturation. These weights determine how much a given pixel will contribute to the final image. A Burt & Adelson multiresolution spline blender is used to combine the images according to the weights. The multiresolution blending ensures that transitions between regions where different images contribute more heavily are difficult to see.

Enfuse uses three different criteria to judge the quality of a pixel: Exposure, saturation, and contrast. The exposure criteria favors pixels with luminance close to the middle of the range. These pixels are considered better-exposed than those with high or low luminance levels. The saturation criteria favors highly-saturated pixels. The contrast criteria favors high-contrast pixels. The local gray or color value standard deviation is used as a contrast measure. The Mertens-Kautz-Van Reeth paper suggest using a laplacian filter, but the standard deviation produces much better results for differently focussed images.

You can adjust how much importance is given to each criteria by setting the weight parameters on the command line. For example, if you set --wExposure=1.0 and --wSaturation=0.5, Enfuse will favor well-exposed pixels over highly-saturated pixels when blending the source images. The impact of these parameters on the final result will not always be clear. The quality of the result is subject to your artistic interpretation. Playing with the weights may or may not give you a more pleasing result. I encourage you to experiment (perhaps using downsized images for speed).

Enfuse expects each input image to have an alpha channel. By setting the alpha values of pixels to zero, users can manually remove those pixels from consideration when blending. If an input image lacks an alpha channel, Enfuse will print a warning and continue assuming all pixels should contribute to the final output. Any alpha value other than zero is interpreted as "this pixel should contribute to the final image".

== Usage ==
The usage below refers to the CVS version of the 21 Dec 2007.

=== Common options ===

-h
Print information on the available options.
-l num
Use exactly this many levels for pyramid blending. This trades off quality of results for faster execution time and lower memory usage. The default is to use as many levels as possible given the size of the overlap region. Enfuse may still use a smaller number of levels if the geometry of the images demands it.
-o output-file
Required. Specify the name of the output file.
-v
Verbose output.
-w
Blend around the -180/+180 boundary. Useful for full-360 panoramas. Enfuse currently does not blend the zenith or the nadir, so you may still see some seams in these areas.
--compression=COMP
Write a compressed output file. Valid values are LZW and DEFLATE for TIFF files, and numbers from 0-100 for JPEG files.

=== Extended options ===

-b kilobytes
Set the block size for Enfuse's image cache. This is the amount of data that Enfuse will move to and from the disk in one go. The default is 2 MiB which should be good for most systems.
-c
Use the CIECAM02 color appearance model for blending colors. Your input TIFF files should have embedded ICC profiles. If no ICC profile is present, Enfuse will assume that image uses the sRGB color space. The difference between using this option and Enfuse's default color blending algorithm is very slight, and will be most noticeable when you need to blend areas of different primary colors together.
-g
Gimp (ver. < 2) and Cinepaint exhibit unusual behaviors when loading images with unassociated alpha channels. Use the -g flag to work around this. With this flag Enfuse will create the output image with the associated alpha tag set, even though the image is really unassociated alpha.
-f WIDTHxHEIGHT
Set the size of the output image manually. This is useful when the input images are cropped TIFF files, such as those produced by Nona.
-m megabytes
Set the size of Enblend's image cache. This is the amount of memory Enblend will use for storing image data before swapping to disk. The default is 1 GiB.

=== Fusion options ===

--wExposure
Sets the relative weight of the well-exposedness criteria. Increasing this weight relative to the others will make well-exposed pixels contribute more to the final output.
--wSaturation
Sets the relative weight of high-saturation pixels. Increasing this weight makes pixels with high saturation contribute more to the final output.
--wContrast
Sets the relative weight of high-contrast pixels.

=== Expert options ===

--ContrastWindowSize
Window size for local contrast analysis. Values larger than 5 might result in a blurry composite and increased computation times. Values in the range of 3 to 5 have given good results on focus stacks.

--HardMask
Force hard blend masks on the finest scale. This avoids averaging of fine details (only), at the expense of increasing the noise. This improves the sharpness of focus stacks considerably.

== See also ==
* [http://www.nabble.com/A-christmas-present-td14438390.html Announcement on Panotools-NG]

Enfuse

2007-12-21T15:40:10Z

Seb Przd: capitalizing Enfuse

[[Image:2125768589_b.jpg|thumb|[[:Image:2125768589_b.jpg|Four exposure panorama blended with enfuse]]]]
Enfuse is a command-line program used to merge different exposures of the same scene to produce an image that looks very much like a tonemapped image (without the halos) but requires no creation of an HDR image. Therefore it is much simpler to use and allows the creation of very large multiple exposure panoramas.

Enfuse is based on a paper by Tom Mertens, Jan Kautz and Frank Van Reeth. The implementation was done by Andrew Mihal (developer of enblend) - http://research.edm.uhasselt.be/~tmertens/exposure_fusion/

Enfuse is currently in beta and available with the development version of [[Enblend]].

== Description ==
Enfuse merges overlapping images using the Mertens-Kautz-Van Reeth exposure fusion algorithm. This is a quick way to produce blend differently exposed images into a nice output image, without producing intermediate HDR images that are then tonemapped to a viewable image. This simplified process often works much better than the currently known tonemapping algorithms.

Enfuse can also be used to build extended DOF images, by blending a focus stack.

The basic idea is that pixels in the input images are weighted according to qualities such as proper exposure, good contrast, and high saturation. These weights determine how much a given pixel will contribute to the final image. A Burt & Adelson multiresolution spline blender is used to combine the images according to the weights. The multiresolution blending ensures that transitions between regions where different images contribute more heavily are difficult to see.

Enfuse uses three different criteria to judge the quality of a pixel: Exposure, saturation, and contrast. The exposure criteria favors pixels with luminance close to the middle of the range. These pixels are considered better-exposed than those with high or low luminance levels. The saturation criteria favors highly-saturated pixels. The contrast criteria favors high-contrast pixels. The local gray or color value standard deviation is used as a contrast measure. The Mertens-Kautz-Van Reeth paper suggest using a laplacian filter, but the standard deviation produces much better results for differently focussed images.

You can adjust how much importance is given to each criteria by setting the weight parameters on the command line. For example, if you set --wExposure=1.0 and --wSaturation=0.5, Enfuse will favor well-exposed pixels over highly-saturated pixels when blending the source images. The impact of these parameters on the final result will not always be clear. The quality of the result is subject to your artistic interpretation. Playing with the weights may or may not give you a more pleasing result. I encourage you to experiment (perhaps using downsized images for speed).

Enfuse expects each input image to have an alpha channel. By setting the alpha values of pixels to zero, users can manually remove those pixels from consideration when blending. If an input image lacks an alpha channel, Enfuse will print a warning and continue assuming all pixels should contribute to the final output. Any alpha value other than zero is interpreted as "this pixel should contribute to the final image".

== Usage ==
The usage below refers to the CVS version of the 21 Dec 2007.

=== Common options ===

-h
Print information on the available options.
-l num
Use exactly this many levels for pyramid blending. This trades off quality of results for faster execution time and lower memory usage. The default is to use as many levels as possible given the size of the overlap region. Enfuse may still use a smaller number of levels if the geometry of the images demands it.
-o output-file
Required. Specify the name of the output file.
-v
Verbose output.
-w
Blend around the -180/+180 boundary. Useful for full-360 panoramas. Enfuse currently does not blend the zenith or the nadir, so you may still see some seams in these areas.
--compression=COMP
Write a compressed output file. Valid values are LZW and DEFLATE for TIFF files, and numbers from 0-100 for JPEG files.

=== Extended options ===

-b kilobytes
Set the block size for Enfuse's image cache. This is the amount of data that Enfuse will move to and from the disk in one go. The default is 2 MiB which should be good for most systems.
-c
Use the CIECAM02 color appearance model for blending colors. Your input TIFF files should have embedded ICC profiles. If no ICC profile is present, Enfuse will assume that image uses the sRGB color space. The difference between using this option and Enfuse's default color blending algorithm is very slight, and will be most noticeable when you need to blend areas of different primary colors together.
-g
Gimp (ver. < 2) and Cinepaint exhibit unusual behaviors when loading images with unassociated alpha channels. Use the -g flag to work around this. With this flag Enfuse will create the output image with the associated alpha tag set, even though the image is really unassociated alpha.
-f WIDTHxHEIGHT
Set the size of the output image manually. This is useful when the input images are cropped TIFF files, such as those produced by Nona.
-m megabytes
Set the size of Enblend's image cache. This is the amount of memory Enblend will use for storing image data before swapping to disk. The default is 1 GiB.

=== Fusion options ===

--wExposure
Sets the relative weight of the well-exposedness criteria. Increasing this weight relative to the others will make well-exposed pixels contribute more to the final output.
--wSaturation
Sets the relative weight of high-saturation pixels. Increasing this weight makes pixels with high saturation contribute more to the final output.
--wContrast
Sets the relative weight of high-contrast pixels.

=== Expert options ===

--ContrastWindowSize
Window size for local contrast analysis. Values larger than 5 might result in a blurry composite and increased computation times. Values in the range of 3 to 5 have given good results on focus stacks.

--HardMask
Force hard blend masks on the finest scale. This avoids averaging of fine details (only), at the expense of increasing the noise. This improves the sharpness of focus stacks considerably.

== See also ==
* [http://www.nabble.com/A-christmas-present-td14438390.html Announcement on Panotools-NG]

Enfuse

2007-12-21T15:39:33Z

Seb Przd: Info on thumbnail image

[[Image:2125768589_b.jpg|thumb|[[:Image:2125768589_b.jpg|Four exposure panorama blended with enfuse]]]]
enfuse is a command-line program used to merge different exposures of the same scene to produce an image that looks very much like a tonemapped image (without the halos) but requires no creation of an HDR image. Therefore it is much simpler to use and allows the creation of very large multiple exposure panoramas.

enfuse is based on a paper by Tom Mertens, Jan Kautz and Frank Van Reeth. The implementation was done by Andrew Mihal (developer of enblend) - http://research.edm.uhasselt.be/~tmertens/exposure_fusion/

enfuse is currently in beta and available with the development version of [[enblend]].

== Description ==
Enfuse merges overlapping images using the Mertens-Kautz-Van Reeth exposure fusion algorithm. This is a quick way to produce blend differently exposed images into a nice output image, without producing intermediate HDR images that are then tonemapped to a viewable image. This simplified process often works much better than the currently known tonemapping algorithms.

Enfuse can also be used to build extended DOF images, by blending a focus stack.

The basic idea is that pixels in the input images are weighted according to qualities such as proper exposure, good contrast, and high saturation. These weights determine how much a given pixel will contribute to the final image. A Burt & Adelson multiresolution spline blender is used to combine the images according to the weights. The multiresolution blending ensures that transitions between regions where different images contribute more heavily are difficult to see.

Enfuse uses three different criteria to judge the quality of a pixel: Exposure, saturation, and contrast. The exposure criteria favors pixels with luminance close to the middle of the range. These pixels are considered better-exposed than those with high or low luminance levels. The saturation criteria favors highly-saturated pixels. The contrast criteria favors high-contrast pixels. The local gray or color value standard deviation is used as a contrast measure. The Mertens-Kautz-Van Reeth paper suggest using a laplacian filter, but the standard deviation produces much better results for differently focussed images.

You can adjust how much importance is given to each criteria by setting the weight parameters on the command line. For example, if you set --wExposure=1.0 and --wSaturation=0.5, Enfuse will favor well-exposed pixels over highly-saturated pixels when blending the source images. The impact of these parameters on the final result will not always be clear. The quality of the result is subject to your artistic interpretation. Playing with the weights may or may not give you a more pleasing result. I encourage you to experiment (perhaps using downsized images for speed).

Enfuse expects each input image to have an alpha channel. By setting the alpha values of pixels to zero, users can manually remove those pixels from consideration when blending. If an input image lacks an alpha channel, Enfuse will print a warning and continue assuming all pixels should contribute to the final output. Any alpha value other than zero is interpreted as "this pixel should contribute to the final image".

== Usage ==
The usage below refers to the CVS version of the 21 Dec 2007.

=== Common options ===

-h
Print information on the available options.
-l num
Use exactly this many levels for pyramid blending. This trades off quality of results for faster execution time and lower memory usage. The default is to use as many levels as possible given the size of the overlap region. Enfuse may still use a smaller number of levels if the geometry of the images demands it.
-o output-file
Required. Specify the name of the output file.
-v
Verbose output.
-w
Blend around the -180/+180 boundary. Useful for full-360 panoramas. Enfuse currently does not blend the zenith or the nadir, so you may still see some seams in these areas.
--compression=COMP
Write a compressed output file. Valid values are LZW and DEFLATE for TIFF files, and numbers from 0-100 for JPEG files.

=== Extended options ===

-b kilobytes
Set the block size for Enfuse's image cache. This is the amount of data that Enfuse will move to and from the disk in one go. The default is 2 MiB which should be good for most systems.
-c
Use the CIECAM02 color appearance model for blending colors. Your input TIFF files should have embedded ICC profiles. If no ICC profile is present, Enfuse will assume that image uses the sRGB color space. The difference between using this option and Enfuse's default color blending algorithm is very slight, and will be most noticeable when you need to blend areas of different primary colors together.
-g
Gimp (ver. < 2) and Cinepaint exhibit unusual behaviors when loading images with unassociated alpha channels. Use the -g flag to work around this. With this flag Enfuse will create the output image with the associated alpha tag set, even though the image is really unassociated alpha.
-f WIDTHxHEIGHT
Set the size of the output image manually. This is useful when the input images are cropped TIFF files, such as those produced by Nona.
-m megabytes
Set the size of Enblend's image cache. This is the amount of memory Enblend will use for storing image data before swapping to disk. The default is 1 GiB.

=== Fusion options ===

--wExposure
Sets the relative weight of the well-exposedness criteria. Increasing this weight relative to the others will make well-exposed pixels contribute more to the final output.
--wSaturation
Sets the relative weight of high-saturation pixels. Increasing this weight makes pixels with high saturation contribute more to the final output.
--wContrast
Sets the relative weight of high-contrast pixels.

=== Expert options ===

--ContrastWindowSize
Window size for local contrast analysis. Values larger than 5 might result in a blurry composite and increased computation times. Values in the range of 3 to 5 have given good results on focus stacks.

--HardMask
Force hard blend masks on the finest scale. This avoids averaging of fine details (only), at the expense of increasing the noise. This improves the sharpness of focus stacks considerably.

== See also ==
* [http://www.nabble.com/A-christmas-present-td14438390.html Announcement on Panotools-NG]

Enfuse

2007-12-21T09:54:50Z

Seb Przd: /* Expert options */

[[Image:2125768589_b.jpg|thumb|[[:Image:2125768589_b.jpg|Panorama created with enfuse]]]]
enfuse is a command-line program used to merge different exposures of the same scene to produce an image that looks very much like a tonemapped image (without the halos) but requires no creation of an HDR image. Therefore it is much simpler to use and allows the creation of very large multiple exposure panoramas.

enfuse is based on a paper by Tom Mertens, Jan Kautz and Frank Van Reeth. The implementationwas done by Andrew Mihal (developer of enblend) - http://research.edm.uhasselt.be/~tmertens/exposure_fusion/

enfuse is currently in beta and available with the development version of [[enblend]].

== Description ==
Enfuse merges overlapping images using the Mertens-Kautz-Van Reeth exposure fusion algorithm. This is a quick way to produce blend differently exposed images into a nice output image, without producing intermediate HDR images that are then tonemapped to a viewable image. This simplified process often works much better than the currently known tonemapping algorithms.

Enfuse can also be used to build extended DOF images, by blending a focus stack.

The basic idea is that pixels in the input images are weighted according to qualities such as proper exposure, good contrast, and high saturation. These weights determine how much a given pixel will contribute to the final image. A Burt & Adelson multiresolution spline blender is used to combine the images according to the weights. The multiresolution blending ensures that transitions between regions where different images contribute more heavily are difficult to see.

Enfuse uses three different criteria to judge the quality of a pixel: Exposure, saturation, and contrast. The exposure criteria favors pixels with luminance close to the middle of the range. These pixels are considered better-exposed than those with high or low luminance levels. The saturation criteria favors highly-saturated pixels. The contrast criteria favors high-contrast pixels. The local gray or color value standart deviation is used as a contrast measure. The Mertens-Kautz-Van Reeth paper suggest using a laplacian filter, but the standard deviation produces much better results for differently focussed images.

You can adjust how much importance is given to each criteria by setting the weight parameters on the command line. For example, if you set --wExposure=1.0 and --wSaturation=0.5, Enfuse will favor well-exposed pixels over highly-saturated pixels when blending the source images. The impact of these parameters on the final result will not always be clear. The quality of the result is subject to your artistic interpretation. Playing with the weights may or may not give you a more pleasing result. I encourage you to experiment (perhaps using downsized images for speed).

Enfuse expects each input image to have an alpha channel. By setting the alpha values of pixels to zero, users can manually remove those pixels from consideration when blending. If an input image lacks an alpha channel, Enfuse will print a warning and continue assuming all pixels should contribute to the final output. Any alpha value other than zero is interpreted as "this pixel should contribute to the final image".

== Usage ==
The usage below refers to the CVS version of the 21 Dec 2007.

=== Common options ===

-h
Print information on the available options.
-l num
Use exactly this many levels for pyramid blending. This trades off quality of results for faster execution time and lower memory usage. The default is to use as many levels as possible given the size of the overlap region. Enfuse may still use a smaller number of levels if the geometry of the images demands it.
-o output-file
Required. Specify the name of the output file.
-v
Verbose output.
-w
Blend around the -180/+180 boundary. Useful for full-360 panoramas. Enfuse currently does not blend the zenith or the nadir, so you may still see some seams in these areas.
--compression=COMP
Write a compressed output file. Valid values are LZW and DEFLATE for TIFF files, and numbers from 0-100 for JPEG files.

=== Extended options ===

-b kilobytes
Set the block size for Enfuse's image cache. This is the amount of data that Enfuse will move to and from the disk in one go. The default is 2 MiB which should be good for most systems.
-c
Use the CIECAM02 color appearance model for blending colors. Your input TIFF files should have embedded ICC profiles. If no ICC profile is present, Enfuse will assume that image uses the sRGB color space. The difference between using this option and Enfuse's default color blending algorithm is very slight, and will be most noticeable when you need to blend areas of different primary colors together.
-g
Gimp (ver. < 2) and Cinepaint exhibit unusual behaviors when loading images with unassociated alpha channels. Use the -g flag to work around this. With this flag Enfuse will create the output image with the associated alpha tag set, even though the image is really unassociated alpha.
-f WIDTHxHEIGHT
Set the size of the output image manually. This is useful when the input images are cropped TIFF files, such as those produced by Nona.
-m megabytes
Set the size of Enblend's image cache. This is the amount of memory Enblend will use for storing image data before swapping to disk. The default is 1 GiB.

=== Fusion options ===

--wExposure
Sets the relative weight of the well-exposedness criteria. Increasing this weight relative to the others will make well-exposed pixels contribute more to the final output.
--wSaturation
Sets the relative weight of high-saturation pixels. Increasing this weight makes pixels with high saturation contribute more to the final output.
--wContrast
Sets the relative weight of high-contrast pixels.

=== Expert options ===

--ContrastWindowSize
Window size for local contrast analysis. Values larger than 5 might result in a blurry composite and increased computation times. Values in the range of 3 to 5 have given good results on focus stacks.

--HardMask
Force hard blend masks on the finest scale. This avoids averaging of fine details (only), at the expense of increasing the noise. This improves the sharpness of focus stacks considerably.

== See also ==
* [http://www.nabble.com/A-christmas-present-td14438390.html Announcement on Panotools-NG]

Enfuse

2007-12-21T09:54:22Z

Seb Przd: /* Fusion options */

Enfuse

2007-12-21T09:54:05Z

Seb Przd: /* Extended options */

Enfuse

2007-12-21T09:53:38Z

Seb Przd: /* Usage */

Enfuse

2007-12-21T09:53:02Z

Seb Przd: Added help page

Enfuse

2007-12-21T08:19:57Z

Seb Przd:

File:2125768589 b.jpg

2007-12-21T08:19:45Z

Seb Przd:

Example of a panorama created with [[enfuse]]. Church in Saint-Didier-sur-Rochefort, Loire, France. Shot and stitched by me, Seb Przd. See original image: http://www.flickr.com/photos/sbprzd/2125768589/

Enfuse

2007-12-21T08:11:39Z

Seb Przd:

[[Image:2125768589_b.jpg|thumb|[[:Image:2125768589_b.jpg|Panorama created with enfuse]]]]
enfuse is a program used to merge different exposures of the same scene to produce an image that looks very much like a tonemapped image (without the halos) but requires no creation of an HDR image. Therefore it is much simpler to use and allows the creation of very large multiple exposure panoramas.

enfuse is based on a paper by Tom Mertens, Jan Kautz and Frank Van Reeth. http://research.edm.uhasselt.be/~tmertens/exposure_fusion/

enfuse is currently in beta and available with the development version of [[enblend]].

Announcement on Panotools-NG: http://www.nabble.com/A-christmas-present-td14438390.html

File:2125768589 b.jpg

2007-12-21T08:07:03Z

Seb Przd: Example of a panorama created with enfuse

Example of a panorama created with [[enfuse]]

Enfuse

2007-12-21T08:01:40Z

Seb Przd:

enfuse is a program used to merge different exposures of the same scene to produce an image that looks very much like a tonemapped image (without the halos) but requires no creation of an HDR image. Therefore it is much simpler to use and allows the creation of very large multiple exposure panoramas.

enfuse is based on a paper by Tom Mertens, Jan Kautz and Frank Van Reeth. http://research.edm.uhasselt.be/~tmertens/exposure_fusion/

enfuse is currently in beta and available with the development version of [[enblend]].

Announcement on Panotools-NG: http://www.nabble.com/A-christmas-present-td14438390.html

Enfuse

2007-12-21T07:47:05Z

Seb Przd: New page: enfuse is a program used to merge different exposures of the same scene to produce an image that looks very much like a tonemapped image (without the halos) but requires no creation of a H...

Hugin

2007-12-11T08:05:37Z

Seb Przd: /* Supported Platforms */

'''Hugin''' {{Glossary|is an opensource graphical user interface (GUI) for [[Panorama tools]]|1}}.

Like other [[GUI front-ends]], '''hugin''' provides an easy-to-use unified point-and-click interface to a whole range of other command-line tools including:

* [[autopano-sift]], [[autopano-sift-C]] or [[autopano]] for automatic creation of [[control points]].
* [[nona]] or [[PTmender]] for remapping input images and rendering output images.
* [[enblend]] for seamless blending of output images.

The Hugin project's mission is not only to provide a powerful GUI, but also to provide opensource replacements for the small number of closed source components of [[Panorama tools]], especially [[PTStitcher]].
A [[PTStitcher]] replacement, called [[nona]] has been developed, supporting its most important features.

Among the many flexible Hugin workflow options, it is possible to use increased tonal range data in a [[16bit workflow with hugin]] or work entirely with high [[dynamic range]] images such as floating-point [[TIFF]] from start to finish in a [[HDR workflow with hugin]].

== Hugin components ==

The following tools are part of the hugin suite:

* [[hugin]] the gui front end.
* [[nona]] a command-line replacement for [[PTStitcher]].
* [[fulla]] correction of [[barrel distortion]], [[chromatic aberration]] and [[vignetting]].
* [[nona_gui]] a version of [[nona]] with simple gui progress dialogs, similar to the windows version of [[PTStitcher]].
* [[autooptimiser]] an experimental tool with the same interface as [[PTOptimizer]] except using pairwize optimization which doesn't require any manual pre-placement.
* [[align_image_stack]] a tool to automate the process to [[align a stack of photos]].
* [[vig_optimize]] command line tool to estimate photometric parameters.
* [[panoglview]] OpenGL panorama viewer stored in sourceforge CVS alongside [[hugin]] which must be built separately.
* [[hugin_hdrmerge]] merges multiple exposures to [[HDR]] using Khan anti-ghosting algorithm
* [[hugin_stitch_project]] batch stitches a hugin project, performing any [[HDR]] merging or blending as necessary.

More information, documentation and tutorials are available on the project website.

== User interface ==

* [[Hugin Main window]]
* [[Hugin Assistant tab]]
* [[Hugin Images tab]]
* [[Hugin Camera and Lens tab]]
* [[Hugin Crop tab]]
* [[Hugin Control Points tab]]
* [[Hugin Optimizer tab]]
* [[Hugin Exposure tab]]
* [[Hugin Stitcher tab]]
* [[Hugin Preferences]]
* [[Hugin Preview window]]
* [[Hugin Control Points table]]
* [[Hugin Keyboard shortcuts]]

== Development ==

Hugin is Open Source, and as such very much dependent on voluntary contributions of resources. If you have coding skills, you are welcome to look at the source code and contribute to it. Even if you don't have coding skills, you most likely have some skills that the project could use and you are more than welcome to contribute your time. The tasks requiring attention change frequently and so do the required skillset and resources. Join the hugin-ptx mailing list to find out what is going on at the moment and how you can help.

At the time of writing (29-October-2007) there is a major effort going on to document and automate the building process of hugin so that the project can release binaries more frequently. See Test Builds below.

== Test Builds ==

=== Goal ===

an infrastructure for on-demand build and distribution of usable test-binaries for the most popular platforms. These builds are meant to enable users to test the newest features and report bugs. Ideally, on Pablo's demand all those who have a build chain will run it against the newest source code to produce the builds.

=== Process ===

# Experienced users will build the most current hugin and helpers (libpano, enblend, autopano, etc.) for the target platform of their choice, with support from coders.
# The build process will be documented for each of the supported platform.
# Users willing to spend some time learning how to build will reproduce the documented process.
# Power users will script and automate the building process.
# Users with packaging skills will package the builds for distribution (installers).
# The produced binaries/installers will be made available on the web.

=== Specific revisions ===

When building from the repository, some revisions have bugs. This process is meant to build the latest revision so that if the latest revision has bugs these can be identified and corrected. However sometimes these bugs can be more critical than other times. If you need a more or less working version of hugin, try applying the process to one of the following revisions.

{| style="margin: 1em auto 1em auto;background:#FFFFDD;text-align:left;border-top: thin dotted #333333;"
|-valign="top"
! width="100" |
Revision
! width="500" |
Comments
|-valign="top"
! style="border-top: thin dotted #333333;" |
2539
| style="border-top: thin dotted #333333;" |
[http://groups.google.com/group/hugin-ptx/browse_thread/thread/e67e1d5a6215b951]
|-valign="top"
|}

=== Supported Platforms ===

* If you don't find your preferred platform listed below '''and''' you are willing to contribute your time and skills to build hugin on it, feel free to add it to the table. We will accommodate any well supported platform in the regular release process.
* The '''Build-Chain Responsibles''' listed below have access to a build chain on the selected platform and have agreed to run the build chain within 2 days of a request from Pablo. They will forward the resulting binary package to the Release Manager who will in turn put them up for download by the general public.
* '''Redundancy is good'''. If you have access to one of the listed platforms, please try to run the documented process below and report success to hugin-ptx. If you think you could do this on a more regular basis, enter yourself in the Backup Build-Chain field.

{| style="margin: 1em auto 1em auto;background:#FFFFDD;text-align:left;border-top: thin dotted #333333;"
|-valign="top"
! width="100" |
Platform
! width="100" |
Status
! width="100" |
Process
! width="200" |
Build-Chain Responsible
! width="200" |
Credits
! width="200" |
Backup Build-Chains
|-valign="top"
! style="border-top: thin dotted #333333;" |
ubuntu 32bit
| style="border-top: thin dotted #333333;" |
tbd
| style="border-top: thin dotted #333333;" |
[[Hugin Compiling Ubuntu | draft]]
| style="border-top: thin dotted #333333;" |
tbd
| style="border-top: thin dotted #333333;" rowspan="2" |
* Sébastien Perez-Duarte
* Yuval Levy
| style="border-top: thin dotted #333333;" |
|-valign="top"
! style="border-top: thin dotted #333333;" |
ubuntu 64bit
| style="border-top: thin dotted #333333;" |
tbd
| style="border-top: thin dotted #333333;" |
[[Hugin Compiling Ubuntu | draft]]
| style="border-top: thin dotted #333333;" |
tbd

| style="border-top: thin dotted #333333;" |
|-valign="top"
! style="border-top: thin dotted #333333;" |
Fedora 32bit
| style="border-top: thin dotted #333333;" |
tbd
| style="border-top: thin dotted #333333;" |
[[Hugin Compiling Fedora | tbd]]
| style="border-top: thin dotted #333333;" |
tbd
| style="border-top: thin dotted #333333;" rowspan="2" |
* Bruno Postle
| style="border-top: thin dotted #333333;" |
|-valign="top"
! style="border-top: thin dotted #333333;" |
Fedora 64bit
| style="border-top: thin dotted #333333;" |
tbd
| style="border-top: thin dotted #333333;" |
[[Hugin Compiling Fedora | tbd]]
| style="border-top: thin dotted #333333;" |
tbd

| style="border-top: thin dotted #333333;" |
|-valign="top"
! style="border-top: thin dotted #333333;" |
OSX IntelMac
| style="border-top: thin dotted #333333;" |
tbd
| style="border-top: thin dotted #333333;" |
[[Hugin Compiling OSX | draft]]
| style="border-top: thin dotted #333333;" |
Peter A. Crowley
| style="border-top: thin dotted #333333;" rowspan="2" |
* Ippei Ukai
* JD Smith
* Daniel M. German
* Peter A. Crowley
| style="border-top: thin dotted #333333;" |
|-valign="top"
! style="border-top: thin dotted #333333;" |
OSX PPC
| style="border-top: thin dotted #333333;" |
tbd
| style="border-top: thin dotted #333333;" |
[[Hugin Compiling OSX | draft]]
| style="border-top: thin dotted #333333;" |
Peter A. Crowley

| style="border-top: thin dotted #333333;" |
|-valign="top"
! style="border-top: thin dotted #333333;" |
Windows 32bit
| style="border-top: thin dotted #333333;" |
tbd
| style="border-top: thin dotted #333333;" |
[[Hugin Compiling Windows | draft]]
| style="border-top: thin dotted #333333;" |
Tom Sharpless
| style="border-top: thin dotted #333333;" |
* Tom Sharpless
* John Navas
* Jean-Marc Paratte
| style="border-top: thin dotted #333333;" |
|-valign="top"
! style="border-top: thin dotted #333333;" |
OpenSuse 32bit
| style="border-top: thin dotted #333333;" |
tbd
| style="border-top: thin dotted #333333;" |
[[Hugin Compiling OpenSuse | tbd]]
| style="border-top: thin dotted #333333;" |
tbd
| style="border-top: thin dotted #333333;" rowspan="2" |
* Kornel Benko (10.3)
* Peter Suetterlin (10.2)
* Stephan Hegel (10.3 x86_64)
| style="border-top: thin dotted #333333;" |
|-valign="top"
! style="border-top: thin dotted #333333;" |
OpenSuse 64bit
| style="border-top: thin dotted #333333;" |
tbd
| style="border-top: thin dotted #333333;" |
[[Hugin Compiling OpenSuse | tbd]]
| style="border-top: thin dotted #333333;" |
tbd

| style="border-top: thin dotted #333333;" |
|-valign="top"
! style="border-top: thin dotted #333333;" |
all platforms
! style="border-top: thin dotted #333333;" colspan="5" |
a big thank you to '''Pablo d'Angelo''' for supporting all of those building efforts.
|-valign="top"
|}

=== Stati ===

'''Build Chain'''
* tbd: looking for responsible
* OK: mostly automated build process ready on request
* unavailable: temporarily unavailable (e.g. responsible on holiday)
* HW-broken: the hardware is temporarily unavailable
* SW-broken: temporarily dysfunctional, working on a fix
* broken: nobody is working on a fix
* unsupported: has been dropped for lack of support

'''Process'''
* tbd: status unknown
* auto: work as documented and has been automated to a reasonable extent
* OK: works as documented, could use automation / scripting
* draft: documented, needs validation / testing / cleaning
* incomplete: parts are missing (e.g. enblend, libpano)
* outdated: worked in the past but needs an update
* obsolete: nobody has the time to update

=== Publication ===
* Release Manager: tbd
* Download / Webspace: thank you Thomas Rauscher / panotools.org, links will be published soon

== See also ==
* [[hugin FAQ]] Frequently asked questions about hugin

== External links ==
* [http://hugin.sourceforge.net hugin homepage] for Screenshots, Tutorials, Documentation and Links.
* [http://sourceforge.net/projects/hugin hugin sourceforge project] for Downloads, Bug database and Feature requests.
* [http://hugin.svn.sourceforge.net/viewvc/hugin/ sourceforge SVN] to browse the hugin sourcecode.
* [http://groups.google.com/group/hugin-ptx hugin-ptx GoogleGroup] to contribute to development and peer support.

== Supported operating systems ==
* [[windows software|Windows]]
* [[Unix software|Linux and Unix]]
* [[Mac software|Mac OS X]]

[[Category:Software:Platform:Windows]]
[[Category:Software:Platform:Linux]]
[[Category:Software:Platform:Mac OS X]]
[[Category:Software:Hugin]]

Hugin Compiling Ubuntu

2007-11-17T19:33:03Z

Seb Przd: /* Building Enblend */

Hugin Compiling Ubuntu

2007-11-17T15:36:22Z

Seb Przd: /* Building Enblend */

Hugin Compiling Ubuntu

2007-11-17T15:18:12Z

Seb Przd: /* Building Enblend */

Hugin Compiling Ubuntu

2007-11-17T11:17:54Z

Seb Przd: /* Building Enblend */

Hugin Compiling Ubuntu

2007-11-17T09:57:26Z

Seb Przd: /* Building Enblend */

Hugin Compiling Ubuntu

2007-11-16T16:16:52Z

Seb Przd: /* Building environment */

Hugin Compiling Ubuntu

2007-11-16T16:15:15Z

Seb Przd: /* Building environment */

Hugin Compiling Ubuntu

2007-11-16T16:08:30Z

Seb Przd: /* Building hugin */

User:Seb Przd

2007-11-08T16:37:53Z

Seb Przd: New page: [http://flickr.com/sbprzd]

[http://flickr.com/sbprzd]

Hugin

2007-11-08T10:33:08Z

Seb Przd: /* Supported Platforms */

'''Hugin''' is an opensource graphical user interface (GUI) for [[Panorama tools]].

Like other [[GUI front-ends]], '''hugin''' provides an easy-to-use unified point-and-click interface to a whole range of other command-line tools including:

* [[autopano-sift]], [[autopano-sift-C]] or [[autopano]] for automatic creation of [[control points]].
* [[nona]] or [[PTmender]] for remapping input images and rendering output images.
* [[enblend]] for seamless blending of output images.

The Hugin project's mission is not only to provide a powerful GUI, but also to provide opensource replacements for the small number of closed source components of [[Panorama tools]], especially [[PTStitcher]].
A [[PTStitcher]] replacement, called [[nona]] has been developed, supporting its most important features.

Among the many flexible Hugin workflow options, it is possible to use increased tonal range data in a [[16bit workflow with hugin]] or work entirely with high [[dynamic range]] images such as floating-point [[TIFF]] from start to finish in a [[HDR workflow with hugin]].

== Hugin components ==

The following tools are part of the hugin suite:

* [[hugin]] the gui front end.
* [[nona]] a command-line replacement for [[PTStitcher]].
* [[fulla]] correction of [[barrel distortion]], [[chromatic aberration]] and [[vignetting]].
* [[nona_gui]] a version of [[nona]] with simple gui progress dialogs, similar to the windows version of [[PTStitcher]].
* [[autooptimiser]] an experimental tool with the same interface as [[PTOptimizer]] except using pairwize optimization which doesn't require any manual pre-placement.
* [[align_image_stack]] a tool to automate the process to [[align a stack of photos]].
* [[vig_optimize]] command line tool to estimate photometric parameters.
* [[zhang_undistort]] a tool for correcting [[barrel distortion]].
* [[color_correct_tiff]] an experimental tool for correcting colour and brightness differences between overlapping images.
* [[panoglview]] OpenGL panorama viewer stored in sourceforge CVS alongside [[hugin]] which must be built separately.

More information, documentation and tutorials are available on the project website.

== User interface ==

* [[Hugin Main window]]
* [[Hugin Assistant tab]]
* [[Hugin Images tab]]
* [[Hugin Camera and Lens tab]]
* [[Hugin Crop tab]]
* [[Hugin Control Points tab]]
* [[Hugin Optimizer tab]]
* [[Hugin Exposure tab]]
* [[Hugin Stitcher tab]]
* [[Hugin Preferences]]
* [[Hugin Preview window]]
* [[Hugin Control Points table]]
* [[Hugin Keyboard shortcuts]]

== Development ==

Hugin is Open Source, and as such very much dependent on voluntary contributions of resources. If you have coding skills, you are welcome to look at the source code and contribute to it. Even if you don't have coding skills, you most likely have some skills that the project could use and you are more than welcome to contribute your time. The tasks requiring attention change frequently and so do the required skillset and resources. Join the hugin-ptx mailing list to find out what is going on at the moment and how you can help.

At the time of writing (29-October-2007) there is a major effort going on to document and automate the building process of hugin so that the project can release binaries more frequently. See Test Builds below.

== Test Builds ==

=== Goal ===

an infrastructure for on-demand build and distribution of usable test-binaries for the most popular platforms. These builds are meant to enable users to test the newest features and report bugs. Ideally, on Pablo's demand all those who have a build chain will run it against the newest source code to produce the builds.

=== Process ===

# Experienced users will build the most current hugin and helpers (libpano, enblend, autopano, etc.) for the target platform of their choice, with support from coders.
# The build process will be documented for each of the supported platform.
# Users willing to spend some time learning how to build will reproduce the documented process.
# Power users will script and automate the building process.
# Users with packaging skills will package the builds for distribution (installers).
# The produced binaries/installers will be made available on the web.

=== Supported Platforms ===

* If you don't find your preferred platform listed below '''and''' you are willing to contribute your time and skills to build hugin on it, feel free to add it to the table. We will accommodate any well supported platform in the regular release process.
* The '''Build-Chain Responsibles''' listed below have access to a build chain on the selected platform and have agreed to run the build chain within 2 days of a request from Pablo. They will forward the resulting binary package to the Release Manager who will in turn put them up for download by the general public.
* '''Redundancy is good'''. If you have access to one of the listed platforms, please try to run the documented process below and report success to hugin-ptx. If you think you could do this on a more regular basis, enter yourself in the Backup Build-Chain field.

{| style="margin: 1em auto 1em auto;background:#FFFFDD;text-align:left;border-top: thin dotted #333333;"
|-valign="top"
! width="100" |
Platform
! width="100" |
Status
! width="100" |
Process
! width="200" |
Build-Chain Responsible
! width="200" |
Credits
! width="200" |
Backup Build-Chains
|-valign="top"
! style="border-top: thin dotted #333333;" |
ubuntu 32bit
| style="border-top: thin dotted #333333;" |
tbd
| style="border-top: thin dotted #333333;" |
[[Hugin Compiling Ubuntu | tbd]]
| style="border-top: thin dotted #333333;" |
tbd
| style="border-top: thin dotted #333333;" rowspan="2" |
* Sébastien Perez-Duarte
| style="border-top: thin dotted #333333;" |
|-valign="top"
! style="border-top: thin dotted #333333;" |
ubuntu 64bit
| style="border-top: thin dotted #333333;" |
tbd
| style="border-top: thin dotted #333333;" |
[[Hugin Compiling Ubuntu | tbd]]
| style="border-top: thin dotted #333333;" |
tbd

| style="border-top: thin dotted #333333;" |
|-valign="top"
! style="border-top: thin dotted #333333;" |
Fedora 32bit
| style="border-top: thin dotted #333333;" |
tbd
| style="border-top: thin dotted #333333;" |
[[Hugin Compiling Fedora | tbd]]
| style="border-top: thin dotted #333333;" |
tbd
| style="border-top: thin dotted #333333;" rowspan="2" |
* Bruno Postle
| style="border-top: thin dotted #333333;" |
|-valign="top"
! style="border-top: thin dotted #333333;" |
Fedora 64bit
| style="border-top: thin dotted #333333;" |
tbd
| style="border-top: thin dotted #333333;" |
[[Hugin Compiling Fedora | tbd]]
| style="border-top: thin dotted #333333;" |
tbd

| style="border-top: thin dotted #333333;" |
|-valign="top"
! style="border-top: thin dotted #333333;" |
OSX IntelMac
| style="border-top: thin dotted #333333;" |
tbd
| style="border-top: thin dotted #333333;" |
[[Hugin Compiling OSX | draft]]
| style="border-top: thin dotted #333333;" |
Peter A. Crowley
| style="border-top: thin dotted #333333;" rowspan="2" |
* Ippei Ukai
* JD Smith
* Daniel M. German
* Peter A. Crowley
| style="border-top: thin dotted #333333;" |
|-valign="top"
! style="border-top: thin dotted #333333;" |
OSX PPC
| style="border-top: thin dotted #333333;" |
tbd
| style="border-top: thin dotted #333333;" |
[[Hugin Compiling OSX | draft]]
| style="border-top: thin dotted #333333;" |
Peter A. Crowley

| style="border-top: thin dotted #333333;" |
|-valign="top"
! style="border-top: thin dotted #333333;" |
Windows 32bit
| style="border-top: thin dotted #333333;" |
tbd
| style="border-top: thin dotted #333333;" |
[[Hugin Compiling Windows | draft]]
| style="border-top: thin dotted #333333;" |
Tom Sharpless
| style="border-top: thin dotted #333333;" |
* Tom Sharpless
* John Navas
* Jean-Marc Paratte
| style="border-top: thin dotted #333333;" |
|-valign="top"
! style="border-top: thin dotted #333333;" |
all platforms
! style="border-top: thin dotted #333333;" colspan="5" |
a big thank you to '''Pablo d'Angelo''' for supporting all of those building efforts.
|-valign="top"
|}

=== Stati ===

'''Build Chain'''
* tbd: looking for responsible
* OK: mostly automated build process ready on request
* unavailable: temporarily unavailable (e.g. responsible on holiday)
* HW-broken: the hardware is temporarily unavailable
* SW-broken: temporarily dysfunctional, working on a fix
* broken: nobody is working on a fix
* unsupported: has been dropped for lack of support

'''Process'''
* tbd: status unknown
* auto: work as documented and has been automated to a reasonable extent
* OK: works as documented, could use automation / scripting
* draft: documented, needs validation / testing / cleaning
* incomplete: parts are missing (e.g. enblend, libpano)
* outdated: worked in the past but needs an update
* obsolete: nobody has the time to update

=== Publication ===
* Release Manager: tbd
* Download / Webspace: thank you Thomas Rauscher / panotools.org, links will be published soon

== See also ==
* [[hugin FAQ]] Frequently asked questions about hugin

== External links ==
* [http://hugin.sourceforge.net hugin homepage] for Screenshots, Tutorials, Documentation and Links.
* [http://sourceforge.net/projects/hugin hugin sourceforge project] for Downloads, Bug database and Feature requests.
* [http://hugin.svn.sourceforge.net/viewvc/hugin/ sourceforge SVN] to browse the hugin sourcecode.
* [http://groups.google.com/group/hugin-ptx hugin-ptx GoogleGroup] to contribute to development and peer support.

== Supported operating systems ==
* [[windows software|Windows]]
* [[Unix software|Linux and Unix]]
* [[Mac software|Mac OS X]]

[[Category:Software:Platform:Windows]]
[[Category:Software:Platform:Linux]]
[[Category:Software:Platform:Mac OS X]]
[[Category:Software:Hugin]]

Hugin Compiling ubuntu

2007-11-08T10:29:57Z

Seb Przd: Hugin Compiling ubuntu moved to Hugin Compiling Ubuntu: Ubuntu should be capitalized, as for the other compilations pages.

#REDIRECT [[Hugin Compiling Ubuntu]]

Hugin Compiling Ubuntu

2007-11-08T10:29:57Z

Seb Przd: Hugin Compiling ubuntu moved to Hugin Compiling Ubuntu: Ubuntu should be capitalized, as for the other compilations pages.

These instructions were tested on a blank installation of Kubuntu 6.06 (Edgy Eft) on a AMD64 computer. Apart from the odd change in package name, nothing should be substantially different (and if does not work, please leave a comment [http://theseblog.free.fr/2007/10/building-hugin-in-ubuntu-feisty-fawn.php here].

== Building environment ==
Since we are going to build hugin (and libpano13) we need to download and install all the development packages. This is very easy with apt-get.
In a terminal window (K menu/System/Konsole)

<pre>sudo apt-get install build-essential autoconf automake1.9 libtool flex bison gdb libc6-dev-amd64 lib64gcc1
sudo apt-get install subversion
</pre>

== Building libpano13 ==
libpano13 is the new version of the PanoTools libraries. This is a necessary component for hugin, and we need to build it first.
To build libpano13 we need some libraries and particularly their <code>dev</code> package:
<pre>sudo apt-get install lib64z1 lib64z1-dev libpng12-dev libjpeg62-dev libtiff4-dev</pre>

We then need to download the source code from SVN:
<pre>svn co https://panotools.svn.sourceforge.net/svnroot/panotools/trunk/libpano libpano13
cd libpano13
./bootstrap</pre>

If any libraries are missing, the script will complain (or at least, let you know that some library hasn't been found). In that case you probably need to install the library. To find in what package is that library, a general rule is to run the command <code>apt-cache search ''missingfile''</code>, find the relevant library and install both the library and the related <code>-dev</code> package.
Run the <code>./configure</code> script and repeat this process until you have met all the dependencies.
Then we are ready to launch the make process with
<pre>make</pre>

If the library successfully compiles, you have to install it with
<pre>sudo make install
sudo ldconfig</pre>
The last part is for the OS to be aware of the new library (that has been installed in <code>/usr/local/lib</code>).
We can now go back up one folder level and get ready for hugin.
<pre>cd ..</pre>

== Building hugin ==

Some additional libraries are needed. We need first to activate the <code>universe</code> repository (in adept package manager, or by editing the /etc/apt/sources.lst file for example).
<pre>sudo apt-get install cmake libopenexr-dev libboost-dev
boost-build</pre>

We download the source from SVN, as before
<pre>svn co https://hugin.svn.sourceforge.net/svnroot/hugin/hugin/trunk/ hugin
cd hugin</pre>
hugin has to be built using cmake (which we installed before).
<pre>cmake -DCMAKE_INSTALL_PREFIX=/usr/local .</pre>

Reference: [http://theseblog.free.fr/2007/10/building-hugin-in-ubuntu-feisty-fawn.php]

[[Category:Software:Hugin]]
[[Category:Software:Platform:Linux]]

Hugin Compiling Ubuntu

2007-11-03T19:26:08Z

Seb Przd: /* Building hugin */

Hugin Compiling Ubuntu

2007-11-03T15:38:12Z

Seb Przd: /* Building hugin */

These instructions were tested on a blank installation of Kubuntu 6.06 (Edgy Eft) on a AMD64 computer. Apart from the odd change in package name, nothing should be substantially different (and if does not work, please leave a comment [http://theseblog.free.fr/2007/10/building-hugin-in-ubuntu-feisty-fawn.php here].

== Building environment ==
Since we are going to build hugin (and libpano13) we need to download and install all the development packages. This is very easy with apt-get.
In a terminal window (K menu/System/Konsole)

<pre>sudo apt-get install build-essential autoconf automake1.9 libtool flex bison gdb libc6-dev-amd64 lib64gcc1
sudo apt-get install subversion
</pre>

== Building libpano13 ==
libpano13 is the new version of the PanoTools libraries. This is a necessary component for hugin, and we need to build it first.
To build libpano13 we need some libraries and particularly their <code>dev</code> package:
<pre>sudo apt-get install lib64z1 lib64z1-dev libpng12-dev libjpeg62-dev libtiff4-dev</pre>

We then need to download the source code from SVN:
<pre>svn co https://panotools.svn.sourceforge.net/svnroot/panotools/trunk/libpano libpano13
cd libpano13
./bootstrap</pre>

If any libraries are missing, the script will complain (or at least, let you know that some library hasn't been found). In that case you probably need to install the library. To find in what package is that library, a general rule is to run the command <code>apt-cache search ''missingfile''</code>, find the relevant library and install both the library and the related <code>-dev</code> package.
Run the <code>./configure</code> script and repeat this process until you have met all the dependencies.
Then we are ready to launch the make process with
<pre>make</pre>

If the library successfully compiles, you have to install it with
<pre>sudo make install
sudo ldconfig</pre>
The last part is for the OS to be aware of the new library (that has been installed in <code>/usr/local/lib</code>).
We can now go back up one folder level and get ready for hugin.
<pre>cd ..</pre>

== Building hugin ==

Some additional libraries are needed. We need first to activate the <code>universe</code> repository (in adept package manager, or by editing the /etc/apt/sources.lst file for example).
<pre>sudo apt-get install cmake</pre>

We download the source from SVN, as before
<pre>svn co https://hugin.svn.sourceforge.net/svnroot/hugin/hugin/trunk/ hugin
cd hugin</pre>
hugin has to be built using cmake (which we installed before).
<pre>cmake -DCMAKE_INSTALL_PREFIX=/usr/local .</pre>

Reference: [http://theseblog.free.fr/2007/10/building-hugin-in-ubuntu-feisty-fawn.php]

Hugin Compiling Ubuntu

2007-11-03T15:03:36Z

Seb Przd: /* Building libpano13 */

These instructions were tested on a blank installation of Kubuntu 6.06 (Edgy Eft) on a AMD64 computer. Apart from the odd change in package name, nothing should be substantially different (and if does not work, please leave a comment [http://theseblog.free.fr/2007/10/building-hugin-in-ubuntu-feisty-fawn.php here].

== Building environment ==
Since we are going to build hugin (and libpano13) we need to download and install all the development packages. This is very easy with apt-get.
In a terminal window (K menu/System/Konsole)

<pre>sudo apt-get install build-essential autoconf automake1.9 libtool flex bison gdb libc6-dev-amd64 lib64gcc1
sudo apt-get install subversion
</pre>

== Building libpano13 ==
libpano13 is the new version of the PanoTools libraries. This is a necessary component for hugin, and we need to build it first.
To build libpano13 we need some libraries and particularly their <code>dev</code> package:
<pre>sudo apt-get install lib64z1 lib64z1-dev libpng12-dev libjpeg62-dev libtiff4-dev</pre>

We then need to download the source code from SVN:
<pre>svn co https://panotools.svn.sourceforge.net/svnroot/panotools/trunk/libpano libpano13
cd libpano13
./bootstrap</pre>

If any libraries are missing, the script will complain (or at least, let you know that some library hasn't been found). In that case you probably need to install the library. To find in what package is that library, a general rule is to run the command <code>apt-cache search ''missingfile''</code>, find the relevant library and install both the library and the related <code>-dev</code> package.
Run the <code>./configure</code> script and repeat this process until you have met all the dependencies.
Then we are ready to launch the make process with
<pre>make</pre>

If the library successfully compiles, you have to install it with
<pre>sudo make install
sudo ldconfig</pre>
The last part is for the OS to be aware of the new library (that has been installed in <code>/usr/local/lib</code>).
We can now go back up one folder level and get ready for hugin.
<pre>cd ..</pre>

== Building hugin ==

Some additional libraries are needed.

We download the source from SVN, as before
<pre>svn co https://hugin.svn.sourceforge.net/svnroot/hugin/hugin/trunk/ hugin
cd hugin</pre>
hugin has to be built using cmake (which we installed before).
<pre>cmake -DCMAKE_INSTALL_PREFIX=/usr/local .</pre>

Reference: [http://theseblog.free.fr/2007/10/building-hugin-in-ubuntu-feisty-fawn.php]

Hugin Compiling Ubuntu

2007-11-03T15:03:05Z

Seb Przd: /* Building hugin */

These instructions were tested on a blank installation of Kubuntu 6.06 (Edgy Eft) on a AMD64 computer. Apart from the odd change in package name, nothing should be substantially different (and if does not work, please leave a comment [http://theseblog.free.fr/2007/10/building-hugin-in-ubuntu-feisty-fawn.php here].

== Building environment ==
Since we are going to build hugin (and libpano13) we need to download and install all the development packages. This is very easy with apt-get.
In a terminal window (K menu/System/Konsole)

<pre>sudo apt-get install build-essential autoconf automake1.9 libtool flex bison gdb libc6-dev-amd64 lib64gcc1
sudo apt-get install subversion
</pre>

== Building libpano13 ==
libpano13 is the new version of the PanoTools libraries. This is a necessary component for hugin, and we need to build it first.
To build libpano13 we need some libraries and particularly their <code>dev</code> package:
<pre>sudo apt-get install lib64z1 lib64z1-dev libpng12-dev libjpeg62-dev libtiff4-dev</pre>

We then need to download the source code from SVN:
<pre>svn co https://panotools.svn.sourceforge.net/svnroot/panotools/trunk/libpano libpano13
cd libpano13
./bootstrap</pre>

If any libraries are missing, the script will complain (or at least, let you know that some library hasn't been found). In that case you probably need to install the library. To find in what package is that library, a general rule is to run the command <code>apt-cache search ''missingfile''</code>, find the relevant library and install both the library and the related <code>-dev</code> package.
Run the <code>./configure</code> script and repeat this process until you have met all the dependencies.
Then we are ready to launch the make process with
<pre>make</pre>

If the library successfully compiles, you have to install it with
<pre>sudo make install
sudo ldconfig</pre>
The last part is for the OS to be aware of the new library (that has been installed in <code>/usr/local/lib</code>).

== Building hugin ==

Some additional libraries are needed.

We download the source from SVN, as before
<pre>svn co https://hugin.svn.sourceforge.net/svnroot/hugin/hugin/trunk/ hugin
cd hugin</pre>
hugin has to be built using cmake (which we installed before).
<pre>cmake -DCMAKE_INSTALL_PREFIX=/usr/local .</pre>

Reference: [http://theseblog.free.fr/2007/10/building-hugin-in-ubuntu-feisty-fawn.php]

Hugin Compiling Ubuntu

2007-11-03T14:48:55Z

Seb Przd: /* Building libpano13 */

These instructions were tested on a blank installation of Kubuntu 6.06 (Edgy Eft) on a AMD64 computer. Apart from the odd change in package name, nothing should be substantially different (and if does not work, please leave a comment [http://theseblog.free.fr/2007/10/building-hugin-in-ubuntu-feisty-fawn.php here].

== Building environment ==
Since we are going to build hugin (and libpano13) we need to download and install all the development packages. This is very easy with apt-get.
In a terminal window (K menu/System/Konsole)

<pre>sudo apt-get install build-essential autoconf automake1.9 libtool flex bison gdb libc6-dev-amd64 lib64gcc1
sudo apt-get install subversion
</pre>

== Building libpano13 ==
libpano13 is the new version of the PanoTools libraries. This is a necessary component for hugin, and we need to build it first.
To build libpano13 we need some libraries and particularly their <code>dev</code> package:
<pre>sudo apt-get install lib64z1 lib64z1-dev libpng12-dev libjpeg62-dev libtiff4-dev</pre>

We then need to download the source code from SVN:
<pre>svn co https://panotools.svn.sourceforge.net/svnroot/panotools/trunk/libpano libpano13
cd libpano13
./bootstrap</pre>

If any libraries are missing, the script will complain (or at least, let you know that some library hasn't been found). In that case you probably need to install the library. To find in what package is that library, a general rule is to run the command <code>apt-cache search ''missingfile''</code>, find the relevant library and install both the library and the related <code>-dev</code> package.
Run the <code>./configure</code> script and repeat this process until you have met all the dependencies.
Then we are ready to launch the make process with
<pre>make</pre>

If the library successfully compiles, you have to install it with
<pre>sudo make install
sudo ldconfig</pre>
The last part is for the OS to be aware of the new library (that has been installed in <code>/usr/local/lib</code>).

== Building hugin ==

Reference: [http://theseblog.free.fr/2007/10/building-hugin-in-ubuntu-feisty-fawn.php]