On 6 Jan., 00:11, Bruno Postle <[email protected]> wrote:
> You could use PToptimizer which writes all this statistical > information about control point errors to the project file. Though > you have to clean a Hugin project file to make it acceptable to the > panotools parser in PToptimizer. Bruno, thank you for your advice. I have started out on a new project towards the goal of eventually providing a scripting interface for hugin, prompted by the awkwardness of only interfacing with the pto, when all the infrastructure needed is already there in hugin. You may want to have a look at http://groups.google.com/group/hugin-ptx/browse_thread/thread/6e0da57a1b1aefe9# I've run into another problem with finding the CP errors here - if I call the optimizer on the Panorama object, the errors are filled in, but now I wonder if there isn't a way to just ask for the calculation of the distances without actually optimizing the CPs? After all, if the transformations for the images are known, the distances should be calculable without optimization. cpclean also calls the optimizer, probably because it had the same problem? 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
