[ptx] suggestion: limiting parameters

[Philippe Gac]

hi Pablo,

one limit could indeed be easy to implement and useful: optionally limiting pitch to [-90, 90] by converting yaw and
roll modulo 180 accordingly after optimisation.

right, the viewer now compute the image width correctly (thanks!) by these strange values are nevertheless annoying for
most users (I have been told they are in some cases required)

regards

philippe


> -----Message d'origine-----
> De : ptx-bounces at email-lists.org [mailto:ptx-bounces at email-lists.org]De
> la part de Pablo d'Angelo
> Envoyé : 16 June 2005 22:42
> À : Didier Hérisson
> Cc : ptx at email-lists.org
> Objet : Re: [ptx] suggestion: limiting parameters
>
>
> Didier Hérisson schrieb:
> > Le Jeudi 16 Juin 2005 14:36, J. Schneider a écrit :
> >
> >>Hello,
> >>
> >>i would like to make a suggestion concerning optimization strategies. No
> >>clue if this is easy or even possible to implement since I have only a
> >>faint idea of programming.
> >>It often happens to me that I have images of which I know, that they are
> >>taken fairly exact but of course not mathematically exact.
> >>So for example I would like to let hugin optimize for pitch and roll
> >>values within certain limits, e.g. 1°. (The tripod column may have been
> >>slightly out of the vertical). Or I have scanned framed slides of which
> >>I know that they must have some  shift (d, e), but not more than 50px
> >>and that the crop is slightly different, so I have to optimize v - but
> >>the focal length can't differ more than 1mm.
> >>You can imagine more scenarios like that.
> >>Is it possible to make hugin stop iterating at a certain limit for a
> >>given parameter?
> >
> >
> > I totally agree that it would be nice to be able to set ranges for
> > parameters... I guess the pb is: can these ranges be send to PToptimizer?
>
> No. this would require changes to pano12.dll and PTOptimizer. And I'm
> not sure how this could be implemented nicely. Ideally we would have to
> replace the current levenberg marquardt minimizer inside pano12.dll with
> one that can handle bounds.
>
> ciao
>    Pablo
>
>