e04us is designed to minimize an arbitrary smooth sum of squares function subject to constraints (which may include simple bounds on the variables, linear constraints and smooth nonlinear constraints) using a sequential quadratic programming (SQP) method. As many first derivatives as possible should be supplied by you; any unspecified derivatives are approximated by finite differences. See the description of the optional parameter Derivative Level, in [Description of the Optional Parameters]. It is not intended for large sparse problems.
e04us may also be used for unconstrained, bound-constrained and linearly constrained optimization.
Syntax
C# |
---|
public static void e04us( int m, int n, int nclin, int ncnln, double[,] a, double[] bl, double[] bu, double[] y, E04..::..E04US_CONFUN confun, E04..::..E04US_OBJFUN objfun, out int iter, int[] istate, double[] c, double[,] cjac, double[] f, double[,] fjac, double[] clamda, out double objf, double[,] r, double[] x, E04..::..e04usOptions options, out int ifail ) |
Visual Basic |
---|
Public Shared Sub e04us ( _ m As Integer, _ n As Integer, _ nclin As Integer, _ ncnln As Integer, _ a As Double(,), _ bl As Double(), _ bu As Double(), _ y As Double(), _ confun As E04..::..E04US_CONFUN, _ objfun As E04..::..E04US_OBJFUN, _ <OutAttribute> ByRef iter As Integer, _ istate As Integer(), _ c As Double(), _ cjac As Double(,), _ f As Double(), _ fjac As Double(,), _ clamda As Double(), _ <OutAttribute> ByRef objf As Double, _ r As Double(,), _ x As Double(), _ options As E04..::..e04usOptions, _ <OutAttribute> ByRef ifail As Integer _ ) |
Visual C++ |
---|
public: static void e04us( int m, int n, int nclin, int ncnln, array<double,2>^ a, array<double>^ bl, array<double>^ bu, array<double>^ y, E04..::..E04US_CONFUN^ confun, E04..::..E04US_OBJFUN^ objfun, [OutAttribute] int% iter, array<int>^ istate, array<double>^ c, array<double,2>^ cjac, array<double>^ f, array<double,2>^ fjac, array<double>^ clamda, [OutAttribute] double% objf, array<double,2>^ r, array<double>^ x, E04..::..e04usOptions^ options, [OutAttribute] int% ifail ) |
F# |
---|
static member e04us : m : int * n : int * nclin : int * ncnln : int * a : float[,] * bl : float[] * bu : float[] * y : float[] * confun : E04..::..E04US_CONFUN * objfun : E04..::..E04US_OBJFUN * iter : int byref * istate : int[] * c : float[] * cjac : float[,] * f : float[] * fjac : float[,] * clamda : float[] * objf : float byref * r : float[,] * x : float[] * options : E04..::..e04usOptions * ifail : int byref -> unit |
Parameters
- m
- Type: System..::..Int32On entry: , the number of subfunctions associated with .Constraint: .
- n
- Type: System..::..Int32On entry: , the number of variables.Constraint: .
- nclin
- Type: System..::..Int32On entry: , the number of general linear constraints.Constraint: .
- ncnln
- Type: System..::..Int32On entry: , the number of nonlinear constraints.Constraint: .
- a
- Type: array<System..::..Double,2>[,](,)[,][,]An array of size [dim1, dim2]Note: dim1 must satisfy the constraint:Note: the second dimension of the array a must be at least if , and at least otherwise.
- bl
- Type: array<System..::..Double>[]()[][]An array of size []On entry: 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 , .
- bu
- Type: array<System..::..Double>[]()[][]An array of size []On entry: 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 , .
- y
- Type: array<System..::..Double>[]()[][]An array of size [m]On entry: the coefficients of the constant vector of the objective function.
- confun
- Type: NagLibrary..::..E04..::..E04US_CONFUNconfun 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 e04us and confun may be the dummy method 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.
A delegate of type E04US_CONFUN.
- objfun
- Type: NagLibrary..::..E04..::..E04US_OBJFUNobjfun must calculate either the th element of the vector or all elements of and (optionally) its Jacobian () for a specified -element vector .
A delegate of type E04US_OBJFUN.
- iter
- Type: System..::..Int32%On exit: the number of major iterations performed.
- istate
- Type: array<System..::..Int32>[]()[][]An array of size []On entry: need not be set if the (default) optional parameter Cold Start is used.If the optional parameter Warm Start has been chosen, the elements of istate corresponding to the bounds and linear constraints define the initial working set for the procedure that finds a feasible point for the linear constraints and bounds. The active set at the conclusion of this procedure and the elements of istate corresponding to nonlinear constraints then define the initial working set for the first QP subproblem. More precisely, the first elements of istate refer to the upper and lower bounds on the variables, the next elements refer to the upper and lower bounds on , and the next elements refer to the upper and lower bounds on . Possible values for are as follows:
Meaning 0 The corresponding constraint is not in the initial QP working set. 1 This inequality constraint should be in the working set at its lower bound. 2 This inequality constraint should be in the working set at its upper bound. 3 This equality constraint should be in the initial working set. This value must not be specified unless . The values , and are also acceptable but will be modified by the method. If e04us has been called previously with the same values of n, nclin and ncnln, istate already contains satisfactory information. (See also the description of the optional parameter Warm Start.) The method also adjusts (if necessary) the values supplied in x to be consistent with istate.Constraint: , for .On exit: the status of the constraints in the QP working set at the point returned in x. The significance of each possible value of is as follows:Meaning This constraint violates its lower bound by more than the appropriate feasibility tolerance (see the optional parameters Linear Feasibility Tolerance and Nonlinear Feasibility Tolerance). This value can occur only when no feasible point can be found for a QP subproblem. This constraint violates its upper bound by more than the appropriate feasibility tolerance (see the optional parameters Linear Feasibility Tolerance and Nonlinear Feasibility Tolerance). This value can occur only when no feasible point can be found for a QP subproblem. 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 .
- c
- Type: array<System..::..Double>[]()[][]An array of size []On exit: if , contains the value of the th nonlinear constraint function at the final iterate, for .If , the array c is not referenced.
- cjac
- Type: array<System..::..Double,2>[,](,)[,][,]An array of size [dim1, dim2]Note: dim1 must satisfy the constraint:Note: the second dimension of the array cjac must be at least if , and at least otherwise.On entry: in general, cjac need not be initialized before the call to e04us. However, if , you may optionally set the constant elements of cjac (see parameter nstate in the description of confun). Such constant elements need not be re-assigned on subsequent calls to confun.On exit: if , cjac contains the Jacobian matrix of the nonlinear constraint functions at the final iterate, i.e., contains the partial derivative of the th constraint function with respect to the th variable, for and . (See the discussion of parameter cjac under confun.)If , the array cjac is not referenced.
- f
- Type: array<System..::..Double>[]()[][]An array of size [m]On exit: contains the value of the th function at the final iterate, for .
- fjac
- Type: array<System..::..Double,2>[,](,)[,][,]An array of size [dim1, n]Note: dim1 must satisfy the constraint:
- clamda
- Type: array<System..::..Double>[]()[][]An array of size []On entry: need not be set if the (default) optional parameter Cold Start is used.If the optional parameter Warm Start has been chosen, must contain a multiplier estimate for each nonlinear constraint with a sign that matches the status of the constraint specified by the istate array, for . The remaining elements need not be set. Note that if the th constraint is defined as ‘inactive’ by the initial value of the istate array (i.e., ), should be zero; if the th constraint is an inequality active at its lower bound (i.e., ), should be non-negative; if the th constraint is an inequality active at its upper bound (i.e., , should be non-positive. If necessary, the method will modify clamda to match these rules.On exit: the values of the QP multipliers from the last QP subproblem. should be non-negative if and non-positive if .
- objf
- Type: System..::..Double%On exit: the value of the objective function at the final iterate.
- r
- Type: array<System..::..Double,2>[,](,)[,][,]An array of size [dim1, n]Note: dim1 must satisfy the constraint:On entry: need not be initialized if the (default) optional parameter Cold Start is used.If the optional parameter Warm Start has been chosen, r must contain the upper triangular Cholesky factor of the initial approximation of the Hessian of the Lagrangian function, with the variables in the natural order. Elements not in the upper triangular part of r are assumed to be zero and need not be assigned.On exit: if , r contains the upper triangular Cholesky factor of , an estimate of the transformed and reordered Hessian of the Lagrangian at (see (6) in e04uf). If , r contains the upper triangular Cholesky factor of , the approximate (untransformed) Hessian of the Lagrangian, with the variables in the natural order.
- x
- Type: array<System..::..Double>[]()[][]An array of size [n]On entry: an initial estimate of the solution.On exit: the final estimate of the solution.
- options
- Type: NagLibrary..::..E04..::..e04usOptionsAn Object of type E04.e04usOptions. Used to configure optional parameters to this method.
- ifail
- Type: System..::..Int32%On exit: unless the method detects an error or a warning has been flagged (see [Error Indicators and Warnings]).
Description
e04us is designed to solve the nonlinear least squares programming problem – the minimization of a smooth nonlinear sum of squares function subject to a set of constraints on the variables. 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 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. (The method of e04us will usually solve (1) if any isolated discontinuities are away from the solution.)
(1) |
Note that although the bounds on the variables could be included in the definition of the linear constraints, we prefer to distinguish between them for reasons of computational efficiency. For the same reason, the linear constraints should not be included in the definition of the nonlinear constraints. Upper and lower bounds are specified for all the variables and for all the constraints. An equality constraint can be specified by setting . If certain bounds are not present, the associated elements of or can be set to special values that will be treated as or . (See the description of the optional parameter Infinite Bound Size.)
You must supply an initial estimate of the solution to (1), together with methods that define , and as many first partial derivatives as possible; unspecified derivatives are approximated by finite differences.
The subfunctions are defined by the array y and objfun, and the nonlinear constraints are defined by confun. On every call, these methods must return appropriate values of and . You should also provide the available partial derivatives. Any unspecified derivatives are approximated by finite differences for a discussion of the optional parameter Derivative Level. Note that if there are any nonlinear constraints, then the first call to confun will precede the first call to objfun.
For maximum reliability, it is preferable for you to provide all partial derivatives (see Chapter 8 of Gill et al. (1981) for a detailed discussion). If all gradients cannot be provided, it is similarly advisable to provide as many as possible. While developing objfun and confun, the optional parameter Verify should be used to check the calculation of any known gradients.
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
Error Indicators and Warnings
Note: e04us may return useful information for one or more of the following detected errors or warnings.
Errors or warnings detected by the method:
Some error messages may refer to parameters that are dropped from this interface
(LDA, LDCJ, LDFJ, LDR) In these
cases, an error in another parameter has usually caused an incorrect value to be inferred.
- The final iterate satisfies the first-order Kuhn–Tucker conditions (see [] in e04uf) to the accuracy requested, but the sequence of iterates has not yet converged. e04us was terminated because no further improvement could be made in the merit function (see [Description of the Printed Output]).This value of ifail may occur in several circumstances. The most common situation is that you ask for a solution with accuracy that is not attainable with the given precision of the problem (as specified by the optional parameter Function Precision (, where is the machine precision)). This condition will also occur if, by chance, an iterate is an ‘exact’ Kuhn–Tucker point, but the change in the variables was significant at the previous iteration. (This situation often happens when minimizing very simple functions, such as quadratics.)If the four conditions listed in [Parameters] for are satisfied, is likely to be a solution of (1) even if .
- e04us has terminated without finding 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 (, 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 feasible point could be found for the nonlinear constraints. The problem may have no feasible solution. This means that there has been a sequence of QP subproblems for which no feasible point could be found (indicated by I at the end of each line of intermediate printout produced by the major iterations; see [Description of the Printed Output]). 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.) If the infeasible subproblems occur from the very first major iteration, it is highly likely that no feasible point exists. If infeasibilities occur when earlier subproblems have been feasible, small constraint inconsistencies may be present. You should check the validity of constraints with negative values of istate. If you are convinced that a feasible point does exist, e04us should be restarted at a different starting point.
- The limiting number of iterations (as determined by the optional parameter Major Iteration Limit () has been reached.If the algorithm appears to be making satisfactory progress, then Major Iteration Limit may be too small. If so, either increase its value and rerun e04us or, alternatively, rerun e04us using the optional parameter Warm Start. If the algorithm seems to be making little or no progress however, then you should check for incorrect gradients or ill-conditioning as described under .Note that ill-conditioning in the working set is sometimes resolved automatically by the algorithm, in which case performing additional iterations may be helpful. However, ill-conditioning in the Hessian approximation tends to persist once it has begun, so that allowing additional iterations without altering is usually inadvisable. If the quasi-Newton update of the Hessian approximation was reset during the latter major iterations (i.e., an r occurs at the end of each line of intermediate printout; see [Description of the Printed Output]), it may be worthwhile to try a Warm Start at the final point as suggested above.
- Not used by this method.
- does not satisfy the first-order Kuhn–Tucker conditions (see [] in e04uf), and no improved point for the merit function (see [Description of the Printed Output]) could be found during the final linesearch.This sometimes occurs because an overly stringent accuracy has been requested, i.e., the value of the optional parameter Optimality Tolerance (, where is the value of the optional parameter Function Precision (, where is the machine precision)) is too small. In this case you should apply the four tests described under to determine whether or not the final solution is acceptable (see Gill et al. (1981), for a discussion of the attainable accuracy).If many iterations have occurred in which essentially no progress has been made and e04us has failed completely to move from the initial point then user-supplied delegates objfun and/or confun may be incorrect. You should refer to comments under and check the gradients using the optional parameter Verify (). Unfortunately, there may be small errors in the objective and constraint gradients that cannot be detected by the verification process. Finite difference approximations to first derivatives are catastrophically affected by even small inaccuracies. An indication of this situation is a dramatic alteration in the iterates if the finite difference interval is altered. One might also suspect this type of error if a switch is made to central differences even when Norm Gz and Violtn (see [Description of the Printed Output]) are large.Another possibility is that the search direction has become inaccurate because of ill-conditioning in the Hessian approximation or the matrix of constraints in the working set; either form of ill-conditioning tends to be reflected in large values of Mnr (the number of iterations required to solve each QP subproblem; see [Description of the Printed Output]).If the condition estimate of the projected Hessian (Cond Hz; see [Description of Monitoring Information]) is extremely large, it may be worthwhile rerunning e04us from the final point with the optional parameter Warm Start. In this situation, istate and clamda should be left unaltered and should be reset to the identity matrix.If the matrix of constraints in the working set is ill-conditioned (i.e., Cond T is extremely large; see [Description of Monitoring Information]), it may be helpful to run e04us with a relaxed value of the optional parameter Feasibility Tolerance (, where is the machine precision). (Constraint dependencies are often indicated by wide variations in size in the diagonal elements of the matrix , whose diagonals will be printed if ).
- The user-supplied derivatives of the subfunctions and/or nonlinear constraints appear to be incorrect.Large errors were found in the derivatives of the subfunctions and/or nonlinear constraints. This value of ifail will occur if the verification process indicated that at least one Jacobian element had no correct figures. You should refer to 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 subfunction and constraint values is correct – for example, by computing the subfunctions at a point where the correct value of is known. However, care should be taken that the chosen point fully tests the evaluation of the subfunctions. 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.Special care should be used in this test if computation of the subfunctions involves subsidiary data communicated in storage. Although the first evaluation of the subfunctions may be correct, subsequent calculations may be in error because some of the subsidiary data has accidentally been overwritten.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 subfunctions may be quite subtle in that the subfunction values are ‘almost’ correct. For example, a subfunction 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 subfunction 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 subfunction; since some compilers do not convert such constants to double precision, half the correct figures may be lost by such a seemingly trivial error.
- Not used by this method.
- An input parameter is invalid.
- If overflow occurs then either an element of is very large, or the singular values or singular vectors have been incorrectly supplied.
Accuracy
If on exit, then the vector returned in the array x is an estimate of the solution to an accuracy of approximately Optimality Tolerance (, where is the machine precision).
Parallelism and Performance
None.
Further Comments
Description of the Printed Output
This section describes the intermediate printout and final printout produced by e04us. The intermediate printout is a subset of the monitoring information produced by the method at every iteration (see [Description of Monitoring Information]). You can control the level of printed output (see the description of the optional parameter Major Print Level). Note that the intermediate printout and final printout are produced only if (the default for e04us, by default no output is produced by ).
(by default no output is produced by e04us).
The following line of summary output ( characters) is produced at every major iteration. In all cases, the values of the quantities printed are those in effect on completion of the given iteration.
Maj | is the major iteration count. |
Mnr |
is the number of minor iterations required by the feasibility and optimality phases of the QP subproblem. Generally, Mnr will be in the later iterations, since theoretical analysis predicts that the correct active set will be identified near the solution
(see [Algorithmic Details] in e04uf).
Note that Mnr may be greater than the optional parameter Minor Iteration Limit if some iterations are required for the feasibility phase.
|
Step | is the step taken along the computed search direction. On reasonably well-behaved problems, the unit step (i.e., ) will be taken as the solution is approached. |
Merit Function |
is the value of the augmented Lagrangian merit function (see (12) in e04uf) at the current iterate. This function will decrease at each iteration unless it was necessary to increase the penalty parameters
(see [] in e04uf).
As the solution is approached, Merit Function will converge to the value of the objective function at the solution.
If the QP subproblem does not have a feasible point (signified by I at the end of the current output line) then the merit function is a large multiple of the constraint violations, weighted by the penalty parameters. During a sequence of major iterations with infeasible subproblems, the sequence of Merit Function values will decrease monotonically until either a feasible subproblem is obtained or e04us terminates with (no feasible point could be found for the nonlinear constraints).
If there are no nonlinear constraints present (i.e., ) then this entry contains Objective, the value of the objective function . The objective function will decrease monotonically to its optimal value when there are no nonlinear constraints.
|
Norm Gz | is , the Euclidean norm of the projected gradient (see [] in e04uf). Norm Gz will be approximately zero in the neighbourhood of a solution. |
Violtn | is the Euclidean norm of the residuals of constraints that are violated or in the predicted active set (not printed if ncnln is zero). Violtn will be approximately zero in the neighbourhood of a solution. |
Cond Hz | is a lower bound on the condition number of the projected Hessian approximation (; see (6) and (11) in e04uf). The larger this number, the more difficult the problem. |
M | is printed if the quasi-Newton update has been modified to ensure that the Hessian approximation is positive definite (see [] in e04uf). |
I | is printed if the QP subproblem has no feasible point. |
C | is printed if central differences have been used to compute the unspecified objective and constraint gradients. If the value of Step is zero then the switch to central differences was made because no lower point could be found in the linesearch. (In this case, the QP subproblem is resolved with the central difference gradient and Jacobian.) If the value of Step is nonzero then central differences were computed because Norm Gz and Violtn imply that is close to a Kuhn–Tucker point (see [] in e04uf). |
L | is printed if the linesearch has produced a relative change in greater than the value defined by the optional parameter Step Limit. If this output occurs frequently during later iterations of the run, optional parameter Step Limit should be set to a larger value. |
R | is printed if the approximate Hessian has been refactorized. If the diagonal condition estimator of indicates that the approximate Hessian is badly conditioned then the approximate Hessian is refactorized using column interchanges. If necessary, is modified so that its diagonal condition estimator is bounded. |
The final printout includes a listing of the status of every variable and constraint.
The following describes the printout for each variable. A full stop (.) is printed for any numerical value that is zero.
Varbl | gives the name (V) and index , for , of the variable. | ||||||
State |
gives the state of the variable (FR if neither bound is in the working set, EQ if a fixed variable, LL if on its lower bound, UL if on its upper bound, TF if temporarily fixed at its current value). If Value lies outside the upper or lower bounds by more than the Feasibility Tolerance, State will be ++ or -- respectively.
A key is sometimes printed before State.
|
||||||
Value | is the value of the variable at the final iteration. | ||||||
Lower Bound | is the lower bound specified for the variable. None indicates that . | ||||||
Upper Bound | is the upper bound specified for the variable. None indicates that . | ||||||
Lagr Mult | is the Lagrange multiplier for the associated bound. This will be zero if State is FR unless and , in which case the entry will be blank. If is optimal, the multiplier should be non-negative if State is LL and non-positive if State is UL. | ||||||
Slack | is the difference between the variable Value and the nearer of its (finite) bounds and . A blank entry indicates that the associated variable is not bounded (i.e., and ). |
The meaning of the printout for linear and nonlinear constraints is the same as that given above for variables, with ‘variable’ replaced by ‘constraint’, and are replaced by and respectively, and with the following changes in the heading:
L Con | gives the name (L) and index , for , of the linear constraint. |
N Con | gives the name (N) and index (), for , of the nonlinear constraint. |
Note that movement off a constraint (as opposed to a variable moving away from its bound) can be interpreted as allowing the entry in the Slack column to become positive.
Numerical values are output with a fixed number of digits; they are not guaranteed to be accurate to this precision.
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 initial point, which is infeasible, is
and .
The optimal solution (to five figures) is
and . The nonlinear constraint is active at the solution.
Example program (C#): e04use.cs
Algorithmic Details
e04us implements a sequential quadratic programming (SQP) method incorporating an augmented Lagrangian merit function and a BFGS (Broyden–Fletcher–Goldfarb–Shanno) quasi-Newton approximation to the Hessian of the Lagrangian, and is based on e04wd. The documents for e04nc, e04uf and e04wd should be consulted for details of the method.
Description of Monitoring Information
This section describes the long line of output ( characters) which forms part of the monitoring information produced by e04us. (See also the description of the optional parameters Major Print Level, Minor Print Level and Monitoring File.) You can control the level of printed output.
When and , the following line of output is produced at every major iteration of e04us on the unit number specified by optional parameter Monitoring File. In all cases, the values of the quantities printed are those in effect on completion of the given iteration.
Maj | is the major iteration count. | ||||||
Mnr |
is the number of minor iterations required by the feasibility and optimality phases of the QP subproblem. Generally, Mnr will be in the later iterations, since theoretical analysis predicts that the correct active set will be identified near the solution
(see [Algorithmic Details] in e04uf).
Note that Mnr may be greater than the optional parameter Minor Iteration Limit if some iterations are required for the feasibility phase.
|
||||||
Step | is the step taken along the computed search direction. On reasonably well-behaved problems, the unit step (i.e., ) will be taken as the solution is approached. | ||||||
Nfun | is the cumulative number of evaluations of the objective function needed for the linesearch. Evaluations needed for the estimation of the gradients by finite differences are not included. Nfun is printed as a guide to the amount of work required for the linesearch. | ||||||
Merit Function |
is the value of the augmented Lagrangian merit function (see (12) in e04uf) at the current iterate. This function will decrease at each iteration unless it was necessary to increase the penalty parameters
(see [] in e04uf).
As the solution is approached, Merit Function will converge to the value of the objective function at the solution.
If the QP subproblem does not have a feasible point (signified by I at the end of the current output line) then the merit function is a large multiple of the constraint violations, weighted by the penalty parameters. During a sequence of major iterations with infeasible subproblems, the sequence of Merit Function values will decrease monotonically until either a feasible subproblem is obtained or e04us terminates with (no feasible point could be found for the nonlinear constraints).
If there are no nonlinear constraints present (i.e., ) then this entry contains Objective, the value of the objective function . The objective function will decrease monotonically to its optimal value when there are no nonlinear constraints.
|
||||||
Norm Gz | is , the Euclidean norm of the projected gradient (see [] in e04uf). Norm Gz will be approximately zero in the neighbourhood of a solution. | ||||||
Violtn | is the Euclidean norm of the residuals of constraints that are violated or in the predicted active set (not printed if ncnln is zero). Violtn will be approximately zero in the neighbourhood of a solution. | ||||||
Nz | is the number of columns of (see [] in e04uf). The value of Nz is the number of variables minus the number of constraints in the predicted active set; i.e., . | ||||||
Bnd | is the number of simple bound constraints in the current working set. | ||||||
Lin | is the number of general linear constraints in the current working set. | ||||||
Nln | is the number of nonlinear constraints in the predicted active set (not printed if ncnln is zero). | ||||||
Penalty | is the Euclidean norm of the vector of penalty parameters used in the augmented Lagrangian merit function (not printed if ncnln is zero). | ||||||
Cond H | is a lower bound on the condition number of the Hessian approximation . | ||||||
Cond Hz | is a lower bound on the condition number of the projected Hessian approximation (; see (6) and (11) in e04uf). The larger this number, the more difficult the problem. | ||||||
Cond T | is a lower bound on the condition number of the matrix of predicted active constraints. | ||||||
Conv |
is a three-letter indication of the status of the three convergence tests (2)–(4) defined in the description of the optional parameter Optimality Tolerance. Each letter is T if the test is satisfied and F otherwise. The three tests indicate whether:
If any of these indicators is F when e04us terminates with , you should check the solution carefully.
|
||||||
M | is printed if the quasi-Newton update has been modified to ensure that the Hessian approximation is positive definite (see [] in e04uf). | ||||||
I | is printed if the QP subproblem has no feasible point. | ||||||
C | is printed if central differences have been used to compute the unspecified objective and constraint gradients. If the value of Step is zero then the switch to central differences was made because no lower point could be found in the linesearch. (In this case, the QP subproblem is resolved with the central difference gradient and Jacobian.) If the value of Step is nonzero then central differences were computed because Norm Gz and Violtn imply that is close to a Kuhn–Tucker point (see [] in e04uf). | ||||||
L | is printed if the linesearch has produced a relative change in greater than the value defined by the optional parameter Step Limit. If this output occurs frequently during later iterations of the run, optional parameter Step Limit should be set to a larger value. | ||||||
R | is printed if the approximate Hessian has been refactorized. If the diagonal condition estimator of indicates that the approximate Hessian is badly conditioned then the approximate Hessian is refactorized using column interchanges. If necessary, is modified so that its diagonal condition estimator is bounded. |