On Fri 27-Feb-2009 at 16:28 +0100, Oskar Sander wrote: > >> What about PTStereo? It uses X, Y, & Z to define camera position. I >> have never used PTStereo so I don't know for sure how it works. >> >> # X10 World coordinates of camera position, only used for PTStereo >> # Y200 If the camera is aligned (yaw = pitch = roll = 0.0), >> # Z-13.5 X is coordinate to the right, Y vertically up and >> # -Z is forward viewing direction.
>Is this how you typically use PTStereo, or is it used for steroscopic >panoramas? I don't quite get what you use the triangulation for >based on the wiki. Is it to tell PTStereo what surface in Pic1 that >correspons to what surface in Pic2. Say a "controll surface" is that >right? PTStereo was used for assembling 3d models of scenes from two or more photos, using panotools as a backend. Aside from being closed-source, the main problem was that it did everything at once - Optimising parameters, outputting 3d geometry and cutting up images to map to the meshes. The triangle mode in ptpicker was to connect control-points and indicate surfaces for the 3d geometry, other than that it used the same control-point system as hugin. 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' -- Bruno --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
