I'm picking up an idea from another thread: 2009/2/28 Bruno Postle <[email protected]>: > Yes optimising X,Y,Z position parameters for each photo in hugin > would be a good SoC project. > > It wouldn't be necessary to output the full polygon mesh initially, > there are plenty of other simpler uses for the X,Y,Z camera info: > > - distinuishing between parallax and 'real' control point errors > - matchmoving > - linear panoramas and 'nadir mode'
According to the sample script in the wiki PTOptimizer have arguments for receiving XYZ camera positions for the images and also optimizing using these in the scripts. However with a warning that these are intended for PTStereo only. Would there be any problem of actually using PTOptimizer to optimize these parameters by manually adding these to a Hugin generated project, or is this "dead code" in PT Optimizer? I am guessing on the workflow, (maybe it is presented somwhere?) but after optimizing I guess you need to stitch and re-project the image. And the issue would be that these programs, i.e. PTMender/PTSticher does not handle these paramters, right? -- /O --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
