<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
<title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
Pablo d'Angelo wrote:<br>
<blockquote type="cite" cite="mid20040716193126.GB1448@svalbart">
<blockquote type="cite">
<pre wrap="">- Default values for lens parameters (a, b, c) are still 0. hugin does not
optimise these values until they are not edited to 0,01 or so. This was
already reported. I'm not sure, but I think this behavior is not new - it
just comes up due to the new defaults.
</pre>
</blockquote>
<pre wrap=""><!---->
Ups, overlooked that. I'll take a look at it.. Strangely, the same thing
happens if I just use PTOptimizer on the script. If I set the initial b to
some number significantly different from 0 (0.1 or so), it works, but else
it fails on the command line as well. If I set it to a really small number,
like 0.0001, the b estimate goes berzerk and I get a rms error of ~144,
where
I don't remember the old optimizer did stuff like that, I'm using the new,
panotools 2.7a-2 rpm from bruno's site. Maybe its a bug somewhere inside
the improved optimisation?
</pre>
</blockquote>
Could always be a bug. But I just reran one of my standard test cases,
using pano12.dll built from 2.7.0.3 sources, under PTGui, optimizing
fov/a/b/c from starting a/b/c = 0, e-6, e-5, e-4, e-3, e-2, 0.1, 0.2,
0.5, and it converged stably in all those cases. It finally failed to
converge well starting at a/b/c = 1, no great surprise. <br>
<br>
Could also be some subtle interaction with other parameters.<br>
<br>
If this problem persists, send me the PTOptimizer script and I'll try
it in my environment.<br>
<br>
--Rik<br>
</body>
</html>