Thanks, I will have a look at your information. I tried to post it as two tables, but couldn't find any way to do so. The only way I could think of was a screenshot. Here it is as two lists:
*OPTIONS/**Function**/**Explanation/**Group* --------------------- *Modes of operation:* --------------------- *-p* *file* Output .pto file (useful for debugging, or further refinement) ----- - --------------------- *-a* *prefix* Output aligned images as prefix_xxxx.tif ----- Output an image for each input image, using the prefix shown. - 1x --------------------- *-o* *output* Align images and merge them to HDR, generate output.hdr ----- Create one High Dynamic Range output file, named as shown. 1x *---------------------* *Modifiers*: --------------------- *-v* Verbose, print progress messages. Repeat for higher verbosity ----- Does “Repeat…” mean that -v -v would output more details than -v? - --------------------- *-e* Assume input images are full frame fish eye (default: rectilinear) ----- Specifies a special image geometry. 3x --------------------- *-t* *num* Remove all control points with an error higher than num pixels (default: 3) ----- Alter precision, maybe improve alignment but possibly make it impossible to match some images. 5x? --------------------- *--corr=num* Correlation threshold for identifying control points (default: 0.9) ----- Alter precision, maybe improve alignment but possibly make it impossible to match some images. 5x? --------------------- *-f* *HFOV* Approximate horizontal field of view of input images, use if EXIF info not complete ----- No idea. - --------------------- *-m* Optimize field of view for all images, except for first. Useful for aligning focus stacks with slightly different magnification. ----- No idea. 3x? --------------------- *-d* Optimize radial distortion for all images, except for first. ----- No idea. 3x --------------------- *-i* Optimize image center shift for all images, except for first. ----- No idea. 3x --------------------- *-x* Optimize X coordinate of camera position ----- No idea. 3x --------------------- *-y* Optimize Y coordinate of camera position ----- No idea. 3x --------------------- *-z* Optimize Z coordinate of camera position ----- No idea. 3x --------------------- *-S* Assume stereo images - allow horizontal shift of control points. ----- See -A 2x? --------------------- *-A* Align stereo window - assumes -S Does “Assumes -S” mean “assumes you are also using -S”? So -S is mandatory with ----- - A? 2x --------------------- *-P* Align stereo window with pop-out effect - assumes -S ----- See -A. 2x --------------------- *-C* Auto crop the image to the area covered by all images ----- - --------------------- *-c* *num* Number of control points (per grid) to create between adjacent images (default: 8) ----- Can select more or less precision by creating more control points per grid square. 6+ --------------------- *-l* Assume linear input files ----- Parameter-e states “(default: rectilinear)”. So isn’t this parameter redundant? Or does it mean something else? 3x --------------------- *-s* *scale* Scale down image by 2^scale (default: 1 [2x down-sampling+) ----- Reduce output image size in the chosen ratio to the input images. - --------------------- *-g* *gsize* Break image into a rectangular grid (gsize x gsize) and attempt to find num control points in each section (default: 5 [5x5 grid+) ----- Spread control points evenly over image by dividing it into squares and having same number of control points in each. Where does *num* come from, is it -c num? 6+ --------------------- *--distortion* Try to load distortion information from lens database ----- Presumably if data is available, AIS uses it to try to compensate for the distortion. What happens if there is none or it’s invalid? - --------------------- *--use-given-order* Use the image order as given on the command line. (By default images will be sorted by exposure values.) ----- Does not affect 3D processing as images are identified as right and left by their order on the command line? 2x --------------------- *--gpu* Use GPU for remapping ----- What happens if there’s no GPU or it’s unsuitable? - --------------------- *-h* Display help summary. ----- - ====================================================================== *Group/Probable Relationship/Parameters/Function* 1x Mutually exclusive -p or -o Output file(s) --------------------- 2x Mutually exclusive -A or -P -S? --use-given-order Stereo image type *It’s not clear whether -S must be used when -A or -P is, or whether it will be included automatically when -A or -P is.* *What is the difference between -A and -S?* --------------------- 3x Mutually exclusive -d -i -x -y -z Which coordinate to optimise? --------------------- 4x Mutually exclusive -e -l Image geometry *What’s the point of -l if the default is rectilinear?* --------------------- 5+ If -g is used, -c must be used too to supply *num* -c -g Affect precision. --------------------- 6x Mutually exclusive? -t --corr Affect precision What’s the difference between -t and -corr? --------------------- - Unrelated to other parameters -p -v -h -f -C -s --gpu --distortion Tools Various On Tuesday, April 9, 2024 at 5:19:52 PM UTC+1 T. Modes wrote: > Chris schrieb am Dienstag, 9. April 2024 um 00:51:28 UTC+2: > > I am using align_image_stack to align 2 images for processing into a 3D > image. > > There is documentation https://wiki.panotools.org/Align_image_stack but > the page states that ““*This article is incomplete. You can help > Panotools Wiki by expanding it > <https://wiki.panotools.org/index.php?title=Align_image_stack&action=edit>.”* > > The descriptions are brief and I’m not sure I completely understand them > all. It is not clear which options are mutually exclusive. > > I expanded the wiki page. Hopefully this make some more clear. > All (or most) of the switches are not mutually exclusive, they can be used > together. > By posting only PNG images you make it more difficult to answer to some of > your points. > > e.g. -l switch refer to linear color space. This has totally unrelated to > rectilinear images, also fisheye images can be in linear color space. So > this switch is not redundant. > -- A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ --- You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/ae9129f4-e522-4051-a179-b09efd1aad7bn%40googlegroups.com.
