I'm a bit confused about how to use vnl_levenberg_marquardt properly. =
Although it wraps an f2c-ized lmder and lmdif, it appears to behave =
differently than the Fortran. When I ran the Rosenbrock example, =
although it got the right answer, it exceeded the maximum number of =
iterations (300). This seems to be different behavior than that of the =
Fortran version in lmder_test.f, which terminates successfully in 21 =
function evaluations. How does the usage of set_x_tolerance(), =
set_f_tolerance(), and set_g_tolerance() differ from xtol, ftol, and =
gtol parameters in an lmder or lmdif call?
From: Daniel J. Jacobsen <dj@im...> - 2004-09-13 08:27:54
is anyone out there working on a build of VXL for Dev-C++? I suppose we
are talking about the MinGW compiler in this case.
I have tried using the libraries built for MSVC 7.0, but - not
surprisingly - that does not work.
It would be really nice if this were done, since many people use this
compiler, not wanting to use MSVC. In many cases, this
is no problem (e.g. OpenGL), but if one wants to use VXL, one is in