Hello, Am Dienstag, 16. September 2014 02:47:31 UTC+2 schrieb TB: > > I don't know how cpfind works in details but I always got CPoints with > correlation below 0.5 (generally in some "blurry" areas, in the middle of a > bigger pattern). I believe that this might be because cpfind works on > bigger areas to find similarities while fine-tune option of hugin works on > smaller search area. >
The correlation is not the only measure for the "quality" of a cp. Cpfind is using a different "quality" criterion (and also on other scales). So this is not per se better or more worse than the correlation. So I would not use the correlation as the only measure for the quality of a cp. > In brief my idea was to: > A- load the pictures composing a panorama > B- create Control-Points (cpfind) > C- Fine-tune them and drop CPoints that had correlation < 0.6 > D- optimise alignment (autooptimiser and pano_modify) > E- drop CPoints that were statistically "too far" (cpclean) > F- create "final draft image" (nona and enblend) > > D and E are in the wrong order. Without the correlation criterion, where I don't agree, this can already done by PTBatcherGUI (queue assistant projects, then automatically stitch). -- 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/4ffc803d-fa21-4c44-867c-837570690c4f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
