Hi Pablo, Pablo> D M German wrote: >> FYI, >> >> Adding Tr parameters to the script will restrict the output of the any >> remapped image be at most 180 degrees, even if it can spawn longer (such >> as most of the cylindrical panoramas). >> >> I am not sure why this happens yet.
Pablo> Only images that have nonzero TrXYZ should be affected by this, as they Pablo> are fist projected onto a plane and thus cannot have more than 180 Pablo> degrees in the final panorama. Pablo> The behaviour of images with Tr(XYZ)0 should not change. I agree. The problem is the execution path of libpano. When a parameter is found, its corresponding function is executed as part of the stack, even if the parameters do not alter the image (such as Tr(XYZ)0). I suspect that the translation function becomes undefined (return nans) when the point if beyond 90 degrees on either of the four directions. The result of this is that the output image has the right size, but has no data outside the 90 degrees boundary. I suspect the best approach is to test for the values of the Tr* parameters in the parser, and if they are zero, do not set the im->cp.trans to TRUE. This can be done for several other parameters too, and will remove unnecessary processing. Pablo> ciao Pablo -- -- Daniel M. German http://turingmachine.org/ http://silvernegative.com/ dmg (at) uvic (dot) ca replace (at) with @ and (dot) with . -- 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
