hugin-bug-hunters team mailing list archive
-
hugin-bug-hunters team
-
Mailing list archive
-
Message #00130
[Bug 679481] Re: No validity check for fov/control point distance
** Changed in: hugin
Status: New => Invalid
--
No validity check for fov/control point distance
https://bugs.launchpad.net/bugs/679481
You received this bug notification because you are a member of Hugin Bug
Hunters, which is subscribed to Hugin.
Status in Hugin - Panorama Tools GUI: Invalid
Bug description:
When the fov for images is set to inf (vinf in i lines in pto, as can be caused by an autopano-sift-c bug, see patch #2996756) hugin/cpclean/autooptimiser create a control point distance that is nan.
This causes an endless loop in the libpano optimizer. For the command line tools this can only be interrupted by killing the process. For hugin cancel usually does the job, only for "Positions (incremental, from anchor)" you have to kill hugin as there is no progress window with cancel button in the first step.
How to reproduce:
Take any pto and replace "vXX" in the i line(s) with vinf.
Solution:
Probably check for validity of the fov either when parsing the pto or when passing to the optimizer.
Alternatively it might be possible to include more sophisticated checks to the libpano optimizer for the case that there is no progress.