Difference between revisions of "Hugin executor"

From PanoTools.org Wiki
Jump to navigation Jump to search
m (fix spelling)
Line 7: Line 7:
 
To stitch a project file from the command line use
 
To stitch a project file from the command line use
  
     hugin_exectuor --stitching --prefix=prefix project.pto
+
     hugin_executor --stitching --prefix=prefix project.pto
  
 
It will use the settings in the project file and also in [[Hugin_Preferences|Hugins preferences dialog]] (e.g. exiftool settings).
 
It will use the settings in the project file and also in [[Hugin_Preferences|Hugins preferences dialog]] (e.g. exiftool settings).

Revision as of 17:18, 14 November 2015

hugin_executor is a tool for command line stitching or for running the assistant from the command line.

It will be available in Hugin 2015.0 and later. (Hugin versions up to 2014.0 use pto2mk for command line stitching.)

Command line stitching

To stitch a project file from the command line use

   hugin_executor --stitching --prefix=prefix project.pto

It will use the settings in the project file and also in Hugins preferences dialog (e.g. exiftool settings).

When no prefix is specified it will use the output prefix found in Hugins preferences dialog. The default value for the output prefix is the filename (inclusive path) of the project file.

Command line assistant

The assistant can run on the command line with

   hugin_executor --assistant project.pto

This will run different other command line tools (like cpfind, linefind, autooptimiser) on the project. The project file will be overwritten with the extended project file (e. g. with control point and optimized). The settings of the assistant can be changed in Hugins preferences dialog.

Advanced options

  • --threads=NUM: Many of the individual tools are using as much threads as possible, e.g. on a 4 core processor it will use 4 threads. This behavior can be changed by setting the environment variable OMP_NUM_THREADS or set the switch --threads to reduce the CPU load.
  • --dry-run: By default hugin_executor executes all commands in sequence. For special scripting purposes you may need the individual commands. For this use case call hugin_executor with --dry-run switch. This will print all commands to the console, from where you can use them in your own scripts.