On 27 Dez., 12:20, RueiKe <[email protected]> wrote: > > The project did use a pano head, so all stacks will be aligned with > the exception of the nadir, which may have some slight movement, so I > add control points to align the Nadir and specify a different lens > after the intial alignment. I am still using autopano-sift-c. Yes, I > use a lot of control points then delete many during the processes of > successive optimizations. I can usually acheive about 0.3 pixel mean > error for a 16k wide pano.
You may loose more than you gain by throwing out a great number of CPs. Often the 'best' CPs are clustered in unproblematic areas, particularly if you are using a fisheye and/or the lens isn't perfectly calibrated. If you just throw out everything above a threshold, you may end up with insufficient area coverage. Don't be too keen on minimizing the mean error, it's not a measure for the quality of your final panorama, just an indicator about the CPs. In my experience it is useful to throw out only CPs which are obviously way off or wrong (like, the worst 10%, or everything above 10). The optimizer is a very clever thing and can well cope with outliers. Kay -- You received this message because you are subscribed to the Google Groups "Hugin and other free panoramic software" group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/hugin-ptx
