NAG Library Routine Document

e04kzf (bounds_mod_deriv_easy)


e04kzf is an easy-to-use modified Newton algorithm for finding a minimum of a function Fx1,x2,,xn, subject to fixed upper and lower bounds on the independent variables x1,x2,,xn, when first derivatives of F are available. It is intended for functions which are continuous and which have continuous first and second derivatives (although it will usually work even if the derivatives have occasional discontinuities).


Fortran Interface
Subroutine e04kzf ( n, ibound, funct2, bl, bu, x, f, g, iw, liw, w, lw, iuser, ruser, ifail)
Integer, Intent (In):: n, ibound, liw, lw
Integer, Intent (Inout):: iuser(*), ifail
Integer, Intent (Out):: iw(liw)
Real (Kind=nag_wp), Intent (Inout):: bl(n), bu(n), x(n), ruser(*)
Real (Kind=nag_wp), Intent (Out):: f, g(n), w(lw)
External:: funct2
C Header Interface
#include <nagmk26.h>
void  e04kzf_ (const Integer *n, const Integer *ibound,
void (NAG_CALL *funct2)(const Integer *n, const double xc[], double *fc, double gc[], Integer iuser[], double ruser[]),
double bl[], double bu[], double x[], double *f, double g[], Integer iw[], const Integer *liw, double w[], const Integer *lw, Integer iuser[], double ruser[], Integer *ifail)


e04kzf is applicable to problems of the form:
MinimizeFx1,x2,,xn  subject to  ljxjuj,  j=1,2,,n  
when first derivatives are known.
Special provision is made for problems which actually have no bounds on the xj, problems which have only non-negativity bounds, and problems in which l1=l2==ln and u1=u2==un. You must supply a subroutine to calculate the values of Fx and its first derivatives at any point x.
From a starting point you supplied there is generated, on the basis of estimates of the gradient of the curvature of Fx, a sequence of feasible points which is intended to converge to a local minimum of the constrained function.


Gill P E and Murray W (1976) Minimization subject to bounds on the variables NPL Report NAC 72 National Physical Laboratory


1:     n – IntegerInput
On entry: the number n of independent variables.
Constraint: n1.
2:     ibound – IntegerInput
On entry: indicates whether the facility for dealing with bounds of special forms is to be used. It must be set to one of the following values:
If you are supplying all the lj and uj individually.
If there are no bounds on any xj.
If all the bounds are of the form 0xj.
If l1=l2==ln and u1=u2==un.
Constraint: 0ibound3.
3:     funct2 – Subroutine, supplied by the user.External Procedure
You must supply this routine to calculate the values of the function Fx and its first derivatives F xj  at any point x. It should be tested separately before being used in conjunction with e04kzf (see Chapter E04).
The specification of funct2 is:
Fortran Interface
Subroutine funct2 ( n, xc, fc, gc, iuser, ruser)
Integer, Intent (In):: n
Integer, Intent (Inout):: iuser(*)
Real (Kind=nag_wp), Intent (In):: xc(n)
Real (Kind=nag_wp), Intent (Inout):: ruser(*)
Real (Kind=nag_wp), Intent (Out):: fc, gc(n)
C Header Interface
#include <nagmk26.h>
void  funct2 (const Integer *n, const double xc[], double *fc, double gc[], Integer iuser[], double ruser[])
1:     n – IntegerInput
On entry: the number n of variables.
2:     xcn – Real (Kind=nag_wp) arrayInput
On entry: the point x at which the function and derivatives are required.
3:     fc – Real (Kind=nag_wp)Output
On exit: the value of the function F at the current point x,
4:     gcn – Real (Kind=nag_wp) arrayOutput
On exit: gcj must be set to the value of the first derivative F xj  at the point x, for j=1,2,,n.
5:     iuser* – Integer arrayUser Workspace
6:     ruser* – Real (Kind=nag_wp) arrayUser Workspace
funct2 is called with the arguments iuser and ruser as supplied to e04kzf. You should use the arrays iuser and ruser to supply information to funct2.
funct2 must either be a module subprogram USEd by, or declared as EXTERNAL in, the (sub)program from which e04kzf is called. Arguments denoted as Input must not be changed by this procedure.
Note: funct2 should not return floating-point NaN (Not a Number) or infinity values, since these are not handled by e04kzf. If your code inadvertently does return any NaNs or infinities, e04kzf is likely to produce unexpected results.
4:     bln – Real (Kind=nag_wp) arrayInput/Output
On entry: the lower bounds lj.
If ibound is set to 0, you must set blj to lj, for j=1,2,,n. (If a lower bound is not specified for a particular xj, the corresponding blj should be set to -106.)
If ibound is set to 3, you must set bl1 to l1; e04kzf will then set the remaining elements of bl equal to bl1.
On exit: the lower bounds actually used by e04kzf.
5:     bun – Real (Kind=nag_wp) arrayInput/Output
On entry: the upper bounds uj.
If ibound is set to 0, you must set buj to uj, for j=1,2,,n. (If an upper bound is not specified for a particular xj, the corresponding buj should be set to 106.)
If ibound is set to 3, you must set bu1 to u1; e04kzf will then set the remaining elements of bu equal to bu1.
On exit: the upper bounds actually used by e04kzf.
6:     xn – Real (Kind=nag_wp) arrayInput/Output
On entry: xj must be set to a guess at the jth component of the position of the minimum, for j=1,2,,n. The routine checks the gradient at the starting point, and is more likely to detect any error in your programming if the initial xj are nonzero and mutually distinct.
On exit: the lowest point found during the calculations of the position of the minimum.
7:     f – Real (Kind=nag_wp)Output
On exit: the value of Fx corresponding to the final point stored in x.
8:     gn – Real (Kind=nag_wp) arrayOutput
On exit: the value of F xj  corresponding to the final point stored in x, for j=1,2,,n; the value of gj for variables not on a bound should normally be close to zero.
9:     iwliw – Integer arrayWorkspace
10:   liw – IntegerInput
On entry: the dimension of the array iw as declared in the (sub)program from which e04kzf is called.
Constraint: liwn+2.
11:   wlw – Real (Kind=nag_wp) arrayWorkspace
12:   lw – IntegerInput
On entry: the dimension of the array w as declared in the (sub)program from which e04kzf is called.
Constraint: lwmaxn×n+7,10.
13:   iuser* – Integer arrayUser Workspace
14:   ruser* – Real (Kind=nag_wp) arrayUser Workspace
iuser and ruser are not used by e04kzf, but are passed directly to funct2 and may be used to pass information to this routine.
15:   ifail – IntegerInput/Output
On entry: ifail must be set to 0, -1 or 1. If you are unfamiliar with this argument you should refer to Section 3.4 in How to Use the NAG Library and its Documentation for details.
For environments where it might be inappropriate to halt program execution when an error is detected, the value -1 or 1 is recommended. If the output of error messages is undesirable, then the value 1 is recommended. Otherwise, because for this routine the values of the output arguments may be useful even if ifail0 on exit, the recommended value is -1. When the value -1 or 1 is used it is essential to test the value of ifail on exit.
On exit: ifail=0 unless the routine detects an error or a warning has been flagged (see Section 6).

Error Indicators and Warnings

If on entry ifail=0 or -1, explanatory error messages are output on the current error message unit (as defined by x04aaf).
Note: e04kzf may return useful information for one or more of the following detected errors or warnings.
Errors or warnings detected by the routine:
On entry,n<1,
oribound=0 and blj>buj for some j,
oribound=3 and bl1>bu1,
There has been a large number of function evaluations, yet the algorithm does not seem to be converging. The calculations can be restarted from the final point held in x. The error may also indicate that Fx has no minimum.
The conditions for a minimum have not all been met but a lower point could not be found and the algorithm has failed.
Not used. (This value of the argument is included to make the significance of ifail=5 etc. consistent in the easy-to-use routines.)
There is some doubt about whether the point x found by e04kzf is a minimum. The degree of confidence in the result decreases as ifail increases. Thus, when ifail=5 it is probable that the final x gives a good estimate of the position of a minimum, but when ifail=8 it is very unlikely that the routine has found a minimum.
In the search for a minimum, the modulus of one of the variables has become very large 106. This indicates that there is a mistake in funct2, that your problem has no finite solution, or that the problem needs rescaling (see Section 9).
It is very likely that you have made an error in forming the gradient.
An unexpected error has been triggered by this routine. Please contact NAG.
See Section 3.9 in How to Use the NAG Library and its Documentation for further information.
Your licence key may have expired or may not have been installed correctly.
See Section 3.8 in How to Use the NAG Library and its Documentation for further information.
Dynamic memory allocation failed.
See Section 3.7 in How to Use the NAG Library and its Documentation for further information.
If you are dissatisfied with the result (e.g., because ifail=5, 6, 7 or 8), it is worth restarting the calculations from a different starting point (not the point at which the failure occurred) in order to avoid the region which caused the failure. If persistent trouble occurs and it is possible to calculate second derivatives it may be advisable to change to a routine which uses second derivatives (see the E04 Chapter Introduction).


When a successful exit is made then, for a computer with a mantissa of t decimals, one would expect to get about t/2-1 decimals accuracy in x and about t-1 decimals accuracy in F, provided the problem is reasonably well scaled.

Parallelism and Performance

e04kzf makes calls to BLAS and/or LAPACK routines, which may be threaded within the vendor library used by this implementation. Consult the documentation for the vendor library for further information.
Please consult the X06 Chapter Introduction for information on how to control and interrogate the OpenMP environment used within this routine. Please also consult the Users' Note for your implementation for any additional implementation-specific information.

Further Comments

The number of iterations required depends on the number of variables, the behaviour of Fx and the distance of the starting point from the solution. The number of operations performed in an iteration of e04kzf is roughly proportional to n3+On2. In addition, each iteration makes at least m+1 calls of funct2 where m is the number of variables not fixed on bounds. So unless Fx and the gradient vector can be evaluated very quickly, the run time will be dominated by the time spent in funct2.
Ideally the problem should be scaled so that at the solution the value of Fx and the corresponding values of x1,x2,,xn are in the range -1,+1, and so that at points a unit distance away from the solution, F is approximately a unit value greater than at the minimum. It is unlikely that you will be able to follow these recommendations very closely, but it is worth trying (by guesswork), as sensible scaling will reduce the difficulty of the minimization problem, so that e04kzf will take less computer time.


A program to minimize
F= x1+10x2 2+5 x3-x4 2+ x2-2x3 4+10 x1-x4 4  
subject to
1 x1 3 -2 x2 0 1 x4 3  
starting from the initial guess 3,-1,0,1 .
In practice, it is worth trying to make funct2 as efficient as possible. This has not been done in the example program for reasons of clarity.

Program Text

Program Text (e04kzfe.f90)

Program Data


Program Results

Program Results (e04kzfe.r)