On 11 Feb., 20:35, Pablo d'Angelo <[email protected]> wrote:
> The FOV normalisation is a nice idea, but I needs a bit more effort than > a simple scaling. As a first, and very simple, step, it should be enough to do these steps: - pixels/degree fov is passed as parameter PPD - image N has fov of FOV degrees across - image N is WIDTH pixels wide - pixels wanted across NPIX = FOV * PPD - scaling factor FSCALE = NPIX / WIDTH of course this does not take into account the variation in resolution from center to edge, which is significant in wide-angle images, but as a rule-of-thumb method to get an idea if this path is promising, it might be worth investigating. If cpfind has a facility to scale individual images with individual factors, it should be cheap to implement - otherwise it'd be more laborious - I fear it's the latter because I know of no CPG with per-image-scaling, but it might be a valuable feature anyway, and would set cpfind further apart from the rest ;-) I hope your 'real' work's grip will lessen eventually, so you can dedicate some time again to cpfind! > Note that a global finetune is not really the best thing, as most of > the control points found by cpfind/panomatic/sift will be in some higher > scale, and the finetune only uses a small window for correlation. I think the finetuning could do with a bit of TLC anyway - or maybe an alternative method to yield better results in some situations when the usual method has difficulties. For finetuning CPs on the overlapping edges of fisheye images, correlation may not be appropriate. Only guessing - haven't looked at the code. 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
