NAG Library Routine Document
E05USF
1 Purpose
E05USF is designed to find the global minimum of an arbitrary smooth sum of squares function subject to constraints (which may include simple bounds on the variables, linear constraints and smooth nonlinear constraints) by generating a number of different starting points and performing a local search from each using sequential quadratic programming.
2 Specification
SUBROUTINE E05USF ( |
M, N, NCLIN, NCNLN, A, LDA, BL, BU, Y, CONFUN, OBJFUN, NPTS, X, LDX, START, REPEAT1, NB, OBJF, F, FJAC, LDFJAC, SDFJAC, ITER, C, LDC, CJAC, LDCJAC, SDCJAC, CLAMDA, LDCLDA, ISTATE, LISTAT, IOPTS, OPTS, IUSER, RUSER, INFO, IFAIL) |
INTEGER |
M, N, NCLIN, NCNLN, LDA, NPTS, LDX, NB, LDFJAC, SDFJAC, ITER(NB), LDC, LDCJAC, SDCJAC, LDCLDA, ISTATE(LISTAT,*), LISTAT, IOPTS(740), IUSER(*), INFO(NB), IFAIL |
REAL (KIND=nag_wp) |
A(LDA,*), BL(N+NCLIN+NCNLN), BU(N+NCLIN+NCNLN), Y(M), X(LDX,*), OBJF(NB), F(M,*), FJAC(LDFJAC,SDFJAC,*), C(LDC,*), CJAC(LDCJAC,SDCJAC,*), CLAMDA(LDCLDA,*), OPTS(485), RUSER(*) |
LOGICAL |
REPEAT1 |
EXTERNAL |
CONFUN, OBJFUN, START |
|
Before calling E05USF, the optional parameter arrays
IOPTS and
OPTS
must
be initialized for use with E05USF by calling
E05ZKF with
OPTSTR set to
‘
Initialize = e05usf’.
Optional parameters may subsequently be specified by calling
E05ZKF before the call to E05USF.
3 Description
The local minimization method is
E04USA.
The problem is assumed to be stated in the following form:
where
(the
objective function) is a nonlinear function which can be represented as the sum of squares of
subfunctions
, the
are constant,
is an
by
constant linear constraint matrix, and
is an
element vector of nonlinear constraint functions. (The matrix
and the vector
may be empty.) The objective function and the constraint functions are assumed to be smooth, i.e., at least twice-continuously differentiable. (This routine will usually solve
(1) if any isolated discontinuities are away from the solution.)
E05USF solves a user-specified number of local optimization problems with different starting points. You may specify the starting points via the subroutine
START. If a random number generator is used to generate the starting points then the parameter
REPEAT1 allows you to specify whether a repeatable set of points are generated or whether different starting points are generated on different calls. The resulting local minima are ordered and the best
NB results returned in order of ascending values of the resulting objective function values at the minima. Thus the value returned in position
will be the best result obtained. If a sufficiently high number of different points are chosen then this is likely to be the global minimum.
4 References
Gill P E, Murray W and Wright M H (1981) Practical Optimization Academic Press
Hock W and Schittkowski K (1981) Test Examples for Nonlinear Programming Codes. Lecture Notes in Economics and Mathematical Systems 187 Springer–Verlag
5 Parameters
- 1: – INTEGERInput
-
On entry: , the number of subfunctions associated with .
Constraint:
.
- 2: – INTEGERInput
-
On entry: , the number of variables.
Constraint:
.
- 3: – INTEGERInput
-
On entry: , the number of general linear constraints.
Constraint:
.
- 4: – INTEGERInput
-
On entry: , the number of nonlinear constraints.
Constraint:
.
- 5: – REAL (KIND=nag_wp) arrayInput
-
Note: the second dimension of the array
A
must be at least
if
, and at least
otherwise.
On entry: the matrix
of general linear constraints in
(1). That is, the
th row contains the coefficients of the
th general linear constraint, for
.
If
, the array
A is not referenced.
- 6: – INTEGERInput
-
On entry: the first dimension of the array
A as declared in the (sub)program from which E05USF is called.
Constraint:
.
- 7: – REAL (KIND=nag_wp) arrayInput
- 8: – REAL (KIND=nag_wp) arrayInput
-
On entry:
BL must contain the lower bounds and
BU the upper bounds for all the constraints in the following order. The first
elements of each array must contain the bounds on the variables, the next
elements the bounds for the general linear constraints (if any) and the next
elements the bounds for the general nonlinear constraints (if any). To specify a nonexistent lower bound (i.e.,
), set
, and to specify a nonexistent upper bound (i.e.,
), set
; the default value of
is
, but this may be changed by the optional parameter
Infinite Bound Size. To specify the
th constraint as an equality, set
, say, where
.
Constraints:
- , for ;
- if , .
- 9: – REAL (KIND=nag_wp) arrayInput
-
On entry: the coefficients of the constant vector of the objective function.
- 10: – SUBROUTINE, supplied by the NAG Library or the user.External Procedure
-
CONFUN must calculate the vector
of nonlinear constraint functions and (optionally) its Jacobian (
) for a specified
-element vector
.
If there are no nonlinear constraints (i.e.,
),
CONFUN will never be called by E05USF and
CONFUN may be the dummy routine E04UDM.
(E04UDM is included in the NAG Library.)
If there are nonlinear constraints, the first call to
CONFUN will occur before the first call to
OBJFUN.
The specification of
CONFUN is:
SUBROUTINE CONFUN ( |
MODE, NCNLN, N, LDCJSL, NEEDC, X, C, CJSL, NSTATE, IUSER, RUSER) |
INTEGER |
MODE, NCNLN, N, LDCJSL, NEEDC(NCNLN), NSTATE, IUSER(*) |
REAL (KIND=nag_wp) |
X(N), C(NCNLN), CJSL(LDCJSL,*), RUSER(*) |
|
- 1: – INTEGERInput/Output
-
On entry: indicates which values must be assigned during each call of
CONFUN. Only the following values need be assigned, for each value of
such that
:
- , the th nonlinear constraint.
- All available elements in the th row of CJSL.
- and all available elements in the th row of CJSL.
On exit: may be set to a negative value if you wish to abandon the solution to the current local minimization problem. In this case E05USF will move to the next local minimization problem.
- 2: – INTEGERInput
-
On entry: , the number of nonlinear constraints.
- 3: – INTEGERInput
-
On entry: , the number of variables.
- 4: – INTEGERInput
-
On entry:
LDCJSL is the first dimension of the array
CJSL.
- 5: – INTEGER arrayInput
-
On entry: the indices of the elements of
C and/or
CJSL that must be evaluated by
CONFUN. If
,
and/or the available elements of the
th row of
CJSL (see parameter
MODE) must be evaluated at
.
- 6: – REAL (KIND=nag_wp) arrayInput
-
On entry: , the vector of variables at which the constraint functions and/or the available elements of the constraint Jacobian are to be evaluated.
- 7: – REAL (KIND=nag_wp) arrayOutput
-
On exit: if
and
or
,
must contain the value of
. The remaining elements of
C, corresponding to the non-positive elements of
NEEDC, need not be set.
- 8: – REAL (KIND=nag_wp) arrayInput/Output
-
CJSL may be regarded as a two-dimensional ‘slice’
of the three-dimensional
array
CJAC
of E05USF.
On entry: unless
or
, the elements of
CJSL are set to special values which enable E05USF to detect whether they are changed by
CONFUN.
On exit: if
and
or
, the
th row of
CJSL must contain the available elements of the vector
given by
where
is the partial derivative of the
th constraint with respect to the
th variable, evaluated at the point
. See also the parameter
NSTATE. The remaining rows of
CJSL, corresponding to non-positive elements of
NEEDC, need not be set.
If all elements of the constraint Jacobian are known (i.e.,
or
; note the default is
), any constant elements may be assigned to
CJSL one time only at the start of each local optimization. An element of
CJSL that is not subsequently assigned in
CONFUN will retain its initial value throughout the local optimization. Constant elements may be loaded into
CJSL during the first call to
CONFUN for the local optimization (signalled by the value
). The ability to preload constants is useful when many Jacobian elements are identically zero, in which case
CJSL may be initialized to zero and nonzero elements may be reset by
CONFUN.
Note that constant nonzero elements do affect the values of the constraints. Thus, if
is set to a constant value, it need not be reset in subsequent calls to
CONFUN, but the value
must nonetheless be added to
. For example, if
and
then the term
must be included in the definition of
.
It must be emphasized that, if
or
, unassigned elements of
CJSL are not treated as constant; they are estimated by finite differences, at nontrivial expense. If you do not supply a value for the optional parameter
Difference Interval, an interval for each element of
is computed automatically at the start of each local optimization. The automatic procedure can usually identify constant elements of
CJSL, which are then computed once only by finite differences.
- 9: – INTEGERInput
-
On entry: if
then E05USF is calling
CONFUN for the first time on the current local optimization problem. This parameter setting allows you to save computation time if certain data must be read or calculated only once.
- 10: – INTEGER arrayUser Workspace
- 11: – REAL (KIND=nag_wp) arrayUser Workspace
-
CONFUN is called with the parameters
IUSER and
RUSER as supplied to E05USF. You are free to use the arrays
IUSER and
RUSER to supply information to
CONFUN as an alternative to using COMMON global variables.
CONFUN must either be a module subprogram USEd by, or declared as EXTERNAL in, the (sub)program from which E05USF is called. Parameters denoted as
Input must
not be changed by this procedure.
CONFUN should be tested separately before being used in conjunction with E05USF. See also the description of the optional parameter
Verify.
- 11: – SUBROUTINE, supplied by the user.External Procedure
-
OBJFUN must calculate either the
th element of the vector
or all
elements of
and (optionally) its Jacobian (
) for a specified
-element vector
.
The specification of
OBJFUN is:
SUBROUTINE OBJFUN ( |
MODE, M, N, LDFJSL, NEEDFI, X, F, FJSL, NSTATE, IUSER, RUSER) |
INTEGER |
MODE, M, N, LDFJSL, NEEDFI, NSTATE, IUSER(*) |
REAL (KIND=nag_wp) |
X(N), F(M), FJSL(LDFJSL,*), RUSER(*) |
|
- 1: – INTEGERInput/Output
-
On entry: indicates which values must be assigned during each call of
OBJFUN. Only the following values need be assigned:
- and , where
- .
- and
- F.
- and
- All available elements of FJSL.
- and
- F and all available elements of FJSL.
On exit: may be set to a negative value if you wish to abandon the solution to the current local minimization problem. In this case E05USF will move to the next local minimization problem.
- 2: – INTEGERInput
-
On entry: , the number of subfunctions.
- 3: – INTEGERInput
-
On entry: , the number of variables.
- 4: – INTEGERInput
-
On entry:
LDFJSL is the first dimension of the array
FJSL.
- 5: – INTEGERInput
-
On entry: if , only the th element of needs to be evaluated at ; the remaining elements need not be set. This can result in significant computational savings when .
- 6: – REAL (KIND=nag_wp) arrayInput
-
On entry: , the vector of variables at which the objective function and/or all available elements of its gradient are to be evaluated.
- 7: – REAL (KIND=nag_wp) arrayOutput
-
On exit: if
and
,
must contain the value of
at
.
If or and ,
must contain the value of at , for .
- 8: – REAL (KIND=nag_wp) arrayInput/Output
-
FJSL may be regarded as a two-dimensional ‘slice’ of the three-dimensional array
FJAC of E05USF.
On entry: is set to a special value.
On exit: if
or
and
, the
th row of
FJSL must contain the available elements of the vector
given by
evaluated at the point
. See also the parameter
NSTATE.
- 9: – INTEGERInput
-
On entry: if
then E05USF is calling
OBJFUN for the first time on the current local optimization problem. This parameter setting allows you to save computation time if certain data must be read or calculated only once.
- 10: – INTEGER arrayUser Workspace
- 11: – REAL (KIND=nag_wp) arrayUser Workspace
-
OBJFUN is called with the parameters
IUSER and
RUSER as supplied to E05USF. You are free to use the arrays
IUSER and
RUSER to supply information to
OBJFUN as an alternative to using COMMON global variables.
OBJFUN must either be a module subprogram USEd by, or declared as EXTERNAL in, the (sub)program from which E05USF is called. Parameters denoted as
Input must
not be changed by this procedure.
OBJFUN should be tested separately before being used in conjunction with E05USF. See also the description of the optional parameter
Verify.
- 12: – INTEGERInput
-
On entry: the number of different starting points to be generated and used. The more points used, the more likely that the best returned solution will be a global minimum.
Constraint:
.
- 13: – REAL (KIND=nag_wp) arrayOutput
-
Note: the second dimension of the array
X
must be at least
.
On exit: contains the final estimate of the th solution, for .
- 14: – INTEGERInput
-
On entry: the first dimension of the array
X as declared in the (sub)program from which E05USF is called.
Constraint:
.
- 15: – SUBROUTINE, supplied by the NAG Library or the user.External Procedure
-
START must calculate the
NPTS starting points to be used by the local optimizer. If you do not wish to write a routine specific to your problem then E05UCZ may be used as the actual argument. E05UCZ is supplied in the NAG Library and uses the NAG quasi-random number generators to distribute starting points uniformly across the domain. It is affected by the value of
REPEAT1.
The specification of
START is:
INTEGER |
NPTS, N, IUSER(*), MODE |
REAL (KIND=nag_wp) |
QUAS(N,NPTS), BL(N), BU(N), RUSER(*) |
LOGICAL |
REPEAT1 |
|
- 1: – INTEGERInput
-
On entry: indicates the number of starting points.
- 2: – REAL (KIND=nag_wp) arrayInput/Output
-
On entry: all elements of
QUAS will have been set to zero, so only nonzero values need be set subsequently.
On exit: must contain the starting points for the
NPTS local minimizations, i.e.,
must contain the
th component of the
th starting point.
- 3: – INTEGERInput
-
On entry: the number of variables.
- 4: – LOGICALInput
-
On entry: specifies whether a repeatable or non-repeatable sequence of points are to be generated.
- 5: – REAL (KIND=nag_wp) arrayInput
-
On entry: the lower bounds on the variables. These may be used to ensure that the starting points generated in some sense ‘cover’ the region, but there is no requirement that a starting point be feasible.
- 6: – REAL (KIND=nag_wp) arrayInput
-
On entry: the upper bounds on the variables. (See
BL.)
- 7: – INTEGER arrayUser Workspace
- 8: – REAL (KIND=nag_wp) arrayUser Workspace
-
START is called with the parameters
IUSER and
RUSER as supplied to E05USF. You are free to use the arrays
IUSER and
RUSER to supply information to
START as an alternative to using COMMON global variables.
- 9: – INTEGERInput/Output
-
On entry:
MODE will contain
.
On exit: if you set
MODE to a negative value then E05USF will terminate immediately with
.
START must either be a module subprogram USEd by, or declared as EXTERNAL in, the (sub)program from which E05USF is called. Parameters denoted as
Input must
not be changed by this procedure.
- 16: – LOGICALInput
-
On entry: is passed as an argument to
START and may be used to initialize a random number generator to a repeatable, or non-repeatable, sequence. See
Section 9 for more detail.
- 17: – INTEGERInput
-
On entry: the number of solutions to be returned. The routine saves up to
NB local minima ordered by increasing value of the final objective function. If the defining criterion for ‘best solution’ is only that the value of the objective function is as small as possible then
NB should be set to
. However, if you want to look at other solutions that may have desirable properties then setting
will produce
NB local minima, ordered by increasing value of their objective functions at the minima.
Constraint:
.
- 18: – REAL (KIND=nag_wp) arrayOutput
-
On exit: contains the value of the objective function at the final iterate for the th solution.
- 19: – REAL (KIND=nag_wp) arrayOutput
-
Note: the second dimension of the array
F
must be at least
.
On exit: contains the value of the th function at the final iterate, for ,
for the th solution, for .
- 20: – REAL (KIND=nag_wp) arrayOutput
-
Note: the last dimension of the array
FJAC
must be at least
.
On exit: for the
th returned solution, the Jacobian matrix of the functions
at the final iterate, i.e.,
contains the partial derivative of the
th function with respect to the
th variable, for
,
and
. (See also the discussion of parameter
FJSL under
OBJFUN.)
- 21: – INTEGERInput
-
On entry: the first dimension of the array
FJAC as declared in the (sub)program from which E05USF is called.
Constraint:
.
- 22: – INTEGERInput
-
On entry: the second dimension of the array
FJAC as declared in the (sub)program from which E05USF is called.
Constraint:
.
- 23: – INTEGER arrayOutput
-
On exit:
contains the number of major iterations performed to obtain the
th solution. If less than
NB solutions are returned then
contains the number of starting points that have resulted in a converged solution. If this is close to
NPTS then this might be indicative that fewer than
NB local minima exist.
- 24: – REAL (KIND=nag_wp) arrayOutput
-
Note: the second dimension of the array
C
must be at least
.
On exit: if
,
contains the value of the
th nonlinear constraint function
at the final iterate, for the
th solution, for
.
If
, the array
C is not referenced.
- 25: – INTEGERInput
-
On entry: the first dimension of the array
C as declared in the (sub)program from which E05USF is called.
Constraint:
.
- 26: – REAL (KIND=nag_wp) arrayOutput
-
Note: the last dimension of the array
CJAC
must be at least
.
On exit: if
,
CJAC contains the Jacobian matrices of the nonlinear constraint functions at the final iterate for each of the returned solutions, i.e.,
contains the partial derivative of the
th constraint function with respect to the
th variable, for
and
, for the
th solution. (See the discussion of parameter
CJSL under
CONFUN.)
If
, the array
CJAC is not referenced.
- 27: – INTEGERInput
-
On entry: the first dimension of the array
CJAC as declared in the (sub)program from which E05USF is called.
Constraint:
.
- 28: – INTEGERInput
-
On entry: the second dimension of the array
CJAC as declared in the (sub)program from which E05USF is called.
Constraint:
if , .
- 29: – REAL (KIND=nag_wp) arrayOutput
-
Note: the second dimension of the array
CLAMDA
must be at least
.
On exit: the values of the QP multipliers from the last QP subproblem solved for the th solution. should be non-negative if and non-positive if .
- 30: – INTEGERInput
-
On entry: the first dimension of the array
CLAMDA as declared in the (sub)program from which E05USF is called.
Constraint:
.
- 31: – INTEGER arrayOutput
-
Note: the second dimension of the array
ISTATE
must be at least
.
On exit:
contains the status of the constraints in the QP working set for the
th solution. The significance of each possible value of
is as follows:
| Meaning |
| The constraint is satisfied to within the feasibility tolerance, but is not in the QP working set. |
| This inequality constraint is included in the QP working set at its lower bound. |
| This inequality constraint is included in the QP working set at its upper bound. |
| This constraint is included in the QP working set as an equality. This value of ISTATE can occur only when . |
- 32: – INTEGERInput
-
On entry: the first dimension of the array
ISTATE as declared in the (sub)program from which E05USF is called.
Constraint:
.
- 33: – INTEGER arrayCommunication Array
- 34: – REAL (KIND=nag_wp) arrayCommunication Array
-
The arrays
IOPTS and
OPTS must not be altered between calls to any of the routines E05USF and
E05ZKF.
- 35: – INTEGER arrayUser Workspace
- 36: – REAL (KIND=nag_wp) arrayUser Workspace
-
IUSER and
RUSER are not used by E05USF, but are passed directly to
CONFUN,
OBJFUN and
START and may be used to pass information to these routines as an alternative to using COMMON global variables.
With SMP-enabled versions of E05USF the arrays
IUSER and
RUSER provided are classified as OpenMP shared memory. Use of
IUSER and
RUSER has to take account of this in order to preserve thread safety whenever information is written back to either of these arrays.
- 37: – INTEGER arrayOutput
-
On exit: if
,
does not contain an error value returned by
E04USF/E04USA .
If
on exit, then not all
NB solutions have been found, and
contains the number of solutions actually found.
- 38: – INTEGERInput/Output
-
On entry:
IFAIL must be set to
,
. If you are unfamiliar with this parameter you should refer to
Section 3.3 in the Essential Introduction for details.
For environments where it might be inappropriate to halt program execution when an error is detected, the value
is recommended. If the output of error messages is undesirable, then the value
is recommended. Otherwise, because for this routine the values of the output parameters may be useful even if
on exit, the recommended value is
.
When the value is used it is essential to test the value of IFAIL on exit.
On exit:
unless the routine detects an error or a warning has been flagged (see
Section 6).
6 Error Indicators and Warnings
If on entry
or
, explanatory error messages are output on the current error message unit (as defined by
X04AAF).
Note: E05USF may return useful information for one or more of the following detected errors or warnings.
Errors or warnings detected by the routine:
An input value is incorrect. One or more of the following requirements are violated:
-
On entry, : .
Constraint: , for all .
-
On entry, and .
Constraint: .
-
On entry, and .
Constraint: .
-
On entry, and .
Constraint: .
-
On entry, , , and .
Constraint: .
-
On entry, and .
Constraint: .
-
On entry, and .
Constraint: .
-
On entry, , , and .
Constraint: .
-
On entry, .
Constraint: .
-
On entry, .
Constraint: .
-
On entry, and .
Constraint: .
-
On entry, .
Constraint: .
-
On entry, .
Constraint: .
-
On entry, , and .
Constraint: if , .
-
On entry, and .
Constraint: .
-
E05USF has terminated without finding any solutions. The majority of calls to the local optimizer have failed to find a feasible point for the linear constraints and bounds, which means that either no feasible point exists for the given value of the optional parameter Linear Feasibility Tolerance (default value , where is the machine precision), or no feasible point could be found in the number of iterations specified by the optional parameter Minor Iteration Limit. You should check that there are no constraint redundancies. If the data for the constraints are accurate only to an absolute precision , you should ensure that the value of the optional parameter Linear Feasibility Tolerance is greater than . For example, if all elements of are of order unity and are accurate to only three decimal places, Linear Feasibility Tolerance should be at least .
No solution obtained. Linear constraints may be infeasible.
-
E05USF has failed to find any solutions. The majority of local optimizations could not find a feasible point for the nonlinear constraints. The problem may have no feasible solution. This behaviour will occur if there is no feasible point for the nonlinear constraints. (However, there is no general test that can determine whether a feasible point exists for a set of nonlinear constraints.)
No solution obtained. Nonlinear constraints may be infeasible.
-
E05USF has failed to find any solutions. The majority of local optimizations have failed because the limiting number of iterations have been reached.
No solution obtained. Many potential solutions reach iteration limit.
-
The user-supplied derivatives of the objective function and/or nonlinear constraints appear to be incorrect.
Large errors were found in the derivatives of the objective function and/or nonlinear constraints. This value of
IFAIL will occur if the verification process indicated that at least one gradient or Jacobian element had no correct figures. You should refer to or enable the printed output to determine which elements are suspected to be in error.
As a first-step, you should check that the code for the objective and constraint values is correct – for example, by computing the function at a point where the correct value is known. However, care should be taken that the chosen point fully tests the evaluation of the function. It is remarkable how often the values or are used to test function evaluation procedures, and how often the special properties of these numbers make the test meaningless.
Gradient checking will be ineffective if the objective function uses information computed by the constraints, since they are not necessarily computed before each function evaluation.
Errors in programming the function may be quite subtle in that the function value is ‘almost’ correct. For example, the function may not be accurate to full precision because of the inaccurate calculation of a subsidiary quantity, or the limited accuracy of data upon which the function depends. A common error on machines where numerical calculations are usually performed in double precision is to include even one single precision constant in the calculation of the function; since some compilers do not convert such constants to double precision, half the correct figures may be lost by such a seemingly trivial error.
-
Only
solutions obtained.
Not all
NB solutions have been found.
contains the number actually found.
-
User terminated computation from
START procedure:
.
If E05UCZ has been used as an actual argument for START then the message displayed, when or on entry to E05USF, will have the following meaning:
|
failure to allocate space, a smaller value of NPTS should be tried. |
|
an internal error has occurred. Please contact NAG for assistance. |
-
Failed to initialize optional parameter arrays.
An unexpected error has been triggered by this routine. Please
contact
NAG.
See
Section 3.8 in the Essential Introduction for further information.
Your licence key may have expired or may not have been installed correctly.
See
Section 3.7 in the Essential Introduction for further information.
Dynamic memory allocation failed.
See
Section 3.6 in the Essential Introduction for further information.
7 Accuracy
If
on exit and the value of
, then the vector returned in the array
X for solution
is an estimate of the solution to an accuracy of approximately
Optimality Tolerance.
8 Parallelism and Performance
E05USF is threaded by NAG for parallel execution in multithreaded implementations of the NAG Library. In these implementations, this routine may make calls to the user-supplied functions from within an OpenMP parallel region. Thus OpenMP directives within the user functions can only be used if you are compiling the user-supplied function and linking the executable in accordance with the instructions in the
Users' Note for your implementation. The user workspace arrays
IUSER and
RUSER are classified as OpenMP shared memory and use of
IUSER and
RUSER has to take account of this in order to preserve thread safety whenever information is written back to either of these arrays. If at all possible, it is recommended that these arrays are only used to supply read-only data to the user functions when a multithreaded implementation is being used.
E05USF 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.
You should be wary of requesting much intermediate output from the local optimizer, since large volumes may be produced if
NPTS is large.
The auxiliary routine E05UCZ
makes use of the NAG quasi-random Sobol generator (
G05YLF and
G05YMF). If
E05UCZ
is used as the actual argument for
START and
then a randomly chosen value for
ISKIP is used, otherwise
ISKIP is set to
. If
REPEAT1 is set to .FALSE. and the program is executed several times, each time producing the same best answer, then there is increased probability that this answer is a global minimum. However, if it is important that identical results be obtained on successive runs, then
REPEAT1 should be set to .TRUE..
9.1 Description of the Printed Output
See
Section 9.1 in E04USF/E04USA.
10 Example
This example is based on Problem 57 in
Hock and Schittkowski (1981) and involves the minimization of the sum of squares function
where
and
subject to the bounds
to the general linear constraint
and to the nonlinear constraint
The optimal solution (to five figures) is
and
. The nonlinear constraint is active at the solution.
The document for
E04UQF/E04UQA includes an example program to solve the same problem using some of the optional parameters described in
Section 12.
10.1 Program Text
Program Text (e05usfe.f90)
10.2 Program Data
Program Data (e05usfe.d)
10.3 Program Results
Program Results (e05usfe.r)
11 Algorithmic Details
See
Section 11 in E04USF/E04USA.
12 Optional Parameters
Several optional parameters in E05USF define choices in the problem specification or the algorithm logic. In order to reduce the number of formal parameters of E05USF these optional parameters have associated default values that are appropriate for most problems. Therefore you need only specify those optional parameters whose values are to be different from their default values.
Optional parameters may be specified by calling
E05ZKF before a call to E05USF. Before calling E05USF, the optional parameter arrays
IOPTS and
OPTS
must
be initialized for use with E05USF by calling
E05ZKF with
OPTSTR set to ‘
Initialize = e05usf’.
All optional parameters not specified are set to their default values. Optional parameters specified are unaltered by E05USF (unless they define invalid values) and so remain in effect for subsequent calls to E05USF.
See
Section 12 in E04USF/E04USA for full details.
The
Warm Start option of
E04USF/E04USA is not a valid option for use with E05USF.
E05USF supports two options that are distinct from those of
E04USF/E04USA:
This option allows you to send information arising from an appropriate setting of
Out_Level to be sent to
the Fortran unit number defined by
Punch Unit. If you wish this file to be different to the standard output unit (
) where other output is displayed then this file should be attached by calling
X04ACF prior to calling E05USF.
This option defines the amount of extra information to be sent to
the Fortran unit number defined by
Punch Unit. The possible choices for
are the following:
|
Meaning |
0 |
No extra output. |
1 |
Updated solutions only. This is useful during long runs to observe progress. |
2 |
Successful start points only. This is useful to save the starting points that gave rise to the final solution. |
3 |
Both updated solutions and successful start points. |
13 Description of Monitoring Information
See
Section 13 in E04USF/E04USA.