LMDIF_(3)

πŸ’– LMDIF_(3) πŸ’–

okay bestie, this is the lmdif_ page from the Library Functions Manual, and it's literally the whole nonlinear-least-squares squad in one place 🫢 grab a snack, we're doing this together.


✨ NAME ✨

lmdif_, lmdif1_ β€” minimize the sum of squares of m nonlinear functions


πŸ¦‹ SYNOPSIS πŸ¦‹

include <minpack.h>

void lmdif1_ ( void (*fcn)(int *m, int *n, double *x, double *fvec, int
               *iflag),
  int *m, int * n, double *x, double *fvec,
  double *tol, int *info, int *iwa, double *wa, int *lwa);

void lmdif_ ( void (*fcn)(int *m, int *n, double *x, double *fvec, int
              *iflag),
  int *m, int *n, double *x, double *fvec,
  double *ftol, double *xtol, double *gtol, int *maxfev, double *epsfcn,
  double *diag, int *mode, double *factor, int *nprint, int *info, int
  *nfev, double *fjac,
  int *ldfjac, int *ipvt, double *qtf,
  double *wa1, double *wa2, double *wa3, double *wa4 );

🌸 DESCRIPTION 🌸

ok so lmdif_'s whole thing is minimizing the sum of the squares of m nonlinear functions in n variables, by a modification of the Levenberg-Marquardt algorithm. You, the user, have to hand it a subroutine that actually computes the functions. Then the Jacobian gets calculated by a forward-difference approximation. no cap.

lmdif1_ is giving the exact same purpose, just with a simplified calling sequence β€” the low-effort, high-reward bestie of the two πŸ’…

πŸ’… Language notes πŸ’…

these functions are written in FORTRAN. if you're calling from C, keep these points in mind, fr fr:

πŸŽ€ Name mangling

with gfortran, all the function names end in an underscore.

πŸ”₯ Compile with gfortran

even if your program is 100% C code, you should link with gfortran so it'll pull in the FORTRAN libraries automatically. honestly it's easiest to just use gfortran to do all the compiling β€” it handles C just fine, it's giving versatile πŸ‘‘

🫢 Call by reference

all function parameters must be pointers. every single one. periodt.

🌈 Column-major arrays

suppose a function returns an array with 5 rows and 3 columns in an array z, and in the call you've declared a leading dimension of 7. the FORTRAN and equivalent C references are:

z(1,1)         z[0]
z(2,1)         z[1]
z(5,1)         z[4]
z(1,2)         z[7]
z(1,3)         z[14]
z(i,j)         z[(i-1) + (j-1)*7]

fcn is the name of the user-supplied subroutine which calculates the functions. in FORTRAN, fcn must be declared in an external statement in the user calling program, and should be written as follows:

subroutine fcn(m,n,x,fvec,iflag)
integer m,n,iflag
double precision x(n),fvec(m)
----------
calculate the functions at x and
return this vector in fvec.
----------
return
end

in C, fcn should be written as follows:

void fcn(int *m, int *n, double *x, double *fvec, int *iflag)
{
       /* calculate the functions at x and return
          the values in fvec[0] through fvec[m-1] */
}

the value of iflag should not be changed by fcn unless the user wants to terminate execution of lmdif_ (or lmdif1_). in that case, set iflag to a negative integer. that's the abort button, bestie πŸ›‘

⭐ Parameters for both lmdif_ and lmdif1_ ⭐

  • m β€” a positive integer input variable set to the number of functions.
  • n β€” a positive integer input variable set to the number of variables. n must not exceed m. (the math said no to anything else πŸ™ˆ)
  • x β€” an array of length n. on input, x must contain an initial estimate of the solution vector. on output, x contains the final estimate of the solution vector. glow-up arc ✨
  • fvec β€” an output array of length m which contains the functions evaluated at the output x.

πŸ“ Parameters for lmdif1_ πŸ“

  • tol β€” a nonnegative input variable. termination occurs when the algorithm estimates either that the relative error in the sum of squares is at most tol or that the relative error between x and the solution is at most tol.
  • info β€” an integer output variable. if the user has terminated execution, info is set to the (negative) value of iflag. see description of fcn. otherwise, info is set as follows:
    • info = 0 β€” improper input parameters. πŸ’€
    • info = 1 β€” algorithm estimates that the relative error in the sum of squares is at most tol.
    • info = 2 β€” algorithm estimates that the relative error between x and the solution is at most tol.
    • info = 3 β€” conditions for info = 1 and info = 2 both hold. double slay.
    • info = 4 β€” fvec is orthogonal to the columns of the Jacobian to machine precision.
    • info = 5 β€” number of calls to fcn has reached or exceeded 200*(n+1).
    • info = 6 β€” tol is too small. no further reduction in the sum of squares is possible.
    • info = 7 β€” tol is too small. no further improvement in the approximate solution x is possible.
  • iwa β€” an integer work array of length n.
  • wa β€” a work array of length lwa.
  • lwa β€” an integer input variable not less than m*n + 5*n + m.

πŸ’œ Parameters for lmdif_ πŸ’œ

  • ftol β€” a nonnegative input variable. termination occurs when both the actual and predicted relative reductions in the sum of squares are at most ftol. therefore, ftol measures the relative error desired in the sum of squares.
  • xtol β€” a nonnegative input variable. termination occurs when the relative error between two consecutive iterates is at most xtol. therefore, xtol measures the relative error desired in the approximate solution.
  • gtol β€” a nonnegative input variable. termination occurs when the cosine of the angle between fvec and any column of the Jacobian is at most gtol in absolute value. therefore, gtol measures the orthogonality desired between the function vector and the columns of the Jacobian.
  • maxfev β€” a positive integer input variable. termination occurs when the number of calls to fcn is at least maxfev by the end of an iteration.
  • epsfcn β€” an input variable used in determining a suitable step length for the forward-difference approximation. this approximation assumes that the relative errors in the functions are of the order of epsfcn. if epsfcn is less than the machine precision, it is assumed that the relative errors in the functions are of the order of the machine precision.
  • diag β€” an array of length n. if mode = 1 (see below), diag is internally set. if mode = 2, diag must contain positive entries that serve as multiplicative scale factors for the variables.
  • mode β€” an integer input variable. if mode = 1, the variables will be scaled internally. if mode = 2, the scaling is specified by the input diag. other values of mode are equivalent to mode = 1.
  • factor β€” a positive input variable used in determining the initial step bound. this bound is set to the product of factor and the euclidean norm of diag*x if the latter is nonzero, or else to factor itself. in most cases factor should lie in the interval (.1,100.). 100. is a generally recommended value.
  • nprint β€” an integer input variable that enables controlled printing of iterates if it is positive. in this case, fcn is called with iflag = 0 at the beginning of the first iteration and every nprint iterations thereafter and immediately prior to return, with x and fvec available for printing. if nprint is not positive, no special calls of fcn with iflag = 0 are made.
  • info β€” an integer output variable. if the user has terminated execution, info is set to the (negative) value of iflag. see description of fcn. otherwise, info is set as follows:
    • info = 0 β€” improper input parameters. πŸ’€
    • info = 1 β€” both actual and predicted relative reductions in the sum of squares are at most ftol.
    • info = 2 β€” relative error between two consecutive iterates is at most xtol.
    • info = 3 β€” conditions for info = 1 and info = 2 both hold. iconic.
    • info = 4 β€” the cosine of the angle between fvec and any column of the Jacobian is at most gtol in absolute value.
    • info = 5 β€” number of calls to fcn has reached or exceeded maxfev.
    • info = 6 β€” ftol is too small. no further reduction in the sum of squares is possible.
    • info = 7 β€” xtol is too small. no further improvement in the approximate solution x is possible.
    • info = 8 β€” gtol is too small. fvec is orthogonal to the columns of the Jacobian to machine precision.
  • nfev β€” an integer output variable set to the number of calls to fcn.
  • fjac β€” an output m by n array. the upper n by n submatrix of fjac contains an upper triangular matrix r with diagonal elements of nonincreasing magnitude such that
     t     t           t
    p *(jac *jac)*p = r *r,

where p is a permutation matrix and jac is the final calculated Jacobian. column j of p is column ipvt(j) (see below) of the identity matrix. the lower trapezoidal part of fjac contains information generated during the computation of r.

  • ldfjac β€” a positive integer input variable not less than m which specifies the leading dimension of the array fjac.
  • ipvt β€” an integer output array of length n. ipvt defines a permutation matrix p such that jac*p = q*r, where jac is the final calculated Jacobian, q is orthogonal (not stored), and r is upper triangular with diagonal elements of nonincreasing magnitude. column j of p is column ipvt(j) of the identity matrix.
  • qtf β€” an output array of length n which contains the first n elements of the vector (q transpose)*fvec.
  • wa1, wa2, and wa3 β€” work arrays of length n.
  • wa4 β€” a work array of length m.

🧚 SEE ALSO 🧚

lmder(3), lmder1(3), lmstr(3), lmstr1(3).


πŸ‘‘ AUTHORS πŸ‘‘

Jorge More', Burt Garbow, and Ken Hillstrom at Argonne National Laboratory. this manual page was written by Jim Van Zandt <jrv@debian.org>, for the Debian GNU/Linux system (but may be used by others). give them their flowers πŸ’


and that's the whole page, bestie β€” no cap. it came from Minpack, dated March 8, 2002, and it's the LMDIF_(3) manual page in all its glory. go forth and least-squares, you absolute main character πŸ¦‹πŸ’–