On Fri, 2010-04-16 at 10:35 -0700, Hesham wrote: > After optimizing a window, "Optimisation result" opens and reports the > average control point distance. I wanted to see how this is computed, > though I see how the mean is computed for all the control points in > calcCtrlPntsErrorStats(), I couldn't decipher the code and find how > the error is computed for each control point. Many wrappers and > duplicates make reading the code a but difficult :-) any help is > appreciated.
The EvaluateControlPointErrorAndComponents function in libpano13's adjust.c seems find individual control point errors: http://panotools.svn.sourceforge.net/viewvc/panotools/trunk/libpano/adjust.c?revision=1267&view=markup#l_1945 However, it looks the the distances are adjusted after optimising here: http://panotools.svn.sourceforge.net/viewvc/panotools/trunk/libpano/adjust.c?revision=1267&view=markup#l_2157 Though, as you say, there are too many wrappers. So there might be more to it. -James -- 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
