ChameleonScales schrieb am Freitag, 20. Mai 2022 um 18:00:24 UTC+2:
> > - There seems to be an inconsistency in the formulations of > > > - > - do optimise whole panorama (skip step 1) > and > - do only pairwise optimisation (skip step 2) > Shouldn't the first one say > - only optimise whole panorama (skip step 1) ? > And in any case it's not just the optimization but also the control > point removal that gets skipped, so why even mention it instead of > simply > saying skip step 1 or 2 ? > > Okay, I will change this text. > > - When using the --dont-optimize option on a pto, the terminal outputs > - Skipping optimisation, current image positions will be used. > But the manual says "when optimising the whole panorama", meaning > it only skips the optimisation to step 2. So wouldn't the images move > in > step 1 ? > > No. Cpclean does not change the image positions. Also with --dont-optimize it will do a pairwise optimisation, then calculate mean/sigma and do the cp clean. Afterward the results of the optimization is disregarded - so the images don't "move". As written, only the optimisation of the whole pano is skipped. So this option makes probably only sense in combination with --whole-pano-checking. -- 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/db590781-53f4-4acc-a899-73cf4f2b5726n%40googlegroups.com.
