﻿ e04uc Method
e04uc is designed to minimize an arbitrary smooth 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. It is not intended for large sparse problems.
e04uc may also be used for unconstrained, bound-constrained and linearly constrained optimization.
e04uc uses forward communication for evaluating the objective function, the nonlinear constraint functions, and any of their derivatives.

Syntax

C#
```public static void e04uc(
int n,
int nclin,
int ncnln,
double[,] a,
double[] bl,
double[] bu,
E04..::.E04UC_CONFUN confun,
E04..::.E04UC_OBJFUN objfun,
out int iter,
int[] istate,
double[] c,
double[,] cjac,
double[] clamda,
out double objf,
double[] objgrd,
double[,] r,
double[] x,
E04..::.e04ucOptions options,
out int ifail
)```
Visual Basic (Declaration)
```Public Shared Sub e04uc ( _
n As Integer, _
nclin As Integer, _
ncnln As Integer, _
a As Double(,), _
bl As Double(), _
bu As Double(), _
confun As E04..::.E04UC_CONFUN, _
objfun As E04..::.E04UC_OBJFUN, _
<OutAttribute> ByRef iter As Integer, _
istate As Integer(), _
c As Double(), _
cjac As Double(,), _
clamda As Double(), _
<OutAttribute> ByRef objf As Double, _
objgrd As Double(), _
r As Double(,), _
x As Double(), _
options As E04..::.e04ucOptions, _
<OutAttribute> ByRef ifail As Integer _
)```
Visual C++
```public:
static void e04uc(
int n,
int nclin,
int ncnln,
array<double,2>^ a,
array<double>^ bl,
array<double>^ bu,
E04..::.E04UC_CONFUN^ confun,
E04..::.E04UC_OBJFUN^ objfun,
[OutAttribute] int% iter,
array<int>^ istate,
array<double>^ c,
array<double,2>^ cjac,
array<double>^ clamda,
[OutAttribute] double% objf,
array<double>^ objgrd,
array<double,2>^ r,
array<double>^ x,
E04..::.e04ucOptions^ options,
[OutAttribute] int% ifail
)```
F#
```static member e04uc :
n:int *
nclin:int *
ncnln:int *
a:float[,] *
bl:float[] *
bu:float[] *
confun:E04..::.E04UC_CONFUN *
objfun:E04..::.E04UC_OBJFUN *
iter:int byref *
istate:int[] *
c:float[] *
cjac:float[,] *
clamda:float[] *
objf:float byref *
objgrd:float[] *
r:float[,] *
x:float[] *
options:E04..::.e04ucOptions *
ifail:int byref -> unit
```

Parameters

n
Type: System..::.Int32
On entry: n, the number of variables.
Constraint: n>0.
nclin
Type: System..::.Int32
On entry: nL, the number of general linear constraints.
Constraint: nclin0.
ncnln
Type: System..::.Int32
On entry: nN, the number of nonlinear constraints.
Constraint: ncnln0.
a
Type: array< System..::.Double ,2>[,](,)[,]
An array of size [lda, dim2]
Note: lda must satisfy the constraint: ldamax1,nclin
Note: the second dimension of the array a must be at least n if nclin>0, and at least 1 otherwise.
On entry: the ith row of a contains the ith row of the matrix AL of general linear constraints in (1). That is, the ith row contains the coefficients of the ith general linear constraint, for i=1,2,,nclin.
If nclin=0, the array a is not referenced.
bl
Type: array< System..::.Double >[]()[]
An array of size [n+nclin+ncnln]
On entry: bl must contain the lower bounds and bu the upper bounds for all the constraints in the following order. The first n elements of each array must contain the bounds on the variables, the next nL elements the bounds for the general linear constraints (if any) and the next nN elements the bounds for the general nonlinear constraints (if any). To specify a nonexistent lower bound (i.e., lj=-), set bl[j-1]-bigbnd, and to specify a nonexistent upper bound (i.e., uj=+), set bu[j-1]bigbnd; the default value of bigbnd is 1020, but this may be changed by the optional parameter Infinite Bound Size. To specify the jth constraint as an equality, set bl[j-1]=bu[j-1]=β, say, where β<bigbnd.
Constraints:
• bl[j]bu[j], for j=0,1,,n+nclin+ncnln-1;
• if bl[j]=bu[j]=β, β<bigbnd.
bu
Type: array< System..::.Double >[]()[]
An array of size [n+nclin+ncnln]
On entry: bl must contain the lower bounds and bu the upper bounds for all the constraints in the following order. The first n elements of each array must contain the bounds on the variables, the next nL elements the bounds for the general linear constraints (if any) and the next nN elements the bounds for the general nonlinear constraints (if any). To specify a nonexistent lower bound (i.e., lj=-), set bl[j-1]-bigbnd, and to specify a nonexistent upper bound (i.e., uj=+), set bu[j-1]bigbnd; the default value of bigbnd is 1020, but this may be changed by the optional parameter Infinite Bound Size. To specify the jth constraint as an equality, set bl[j-1]=bu[j-1]=β, say, where β<bigbnd.
Constraints:
• bl[j]bu[j], for j=0,1,,n+nclin+ncnln-1;
• if bl[j]=bu[j]=β, β<bigbnd.
confun
Type: NagLibrary..::.E04..::.E04UC_CONFUN
confun must calculate the vector cx of nonlinear constraint functions and (optionally) its Jacobian (= c x ) for a specified n element vector x. If there are no nonlinear constraints (i.e., ncnln=0), confun will never be called by e04uc 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 E04UC_CONFUN.

confun should be tested separately before being used in conjunction with e04uc. See also the description of the optional parameter Verify.
objfun
Type: NagLibrary..::.E04..::.E04UC_OBJFUN
objfun must calculate the objective function Fx and (optionally) its gradient gx = F x  for a specified n-vector x.

A delegate of type E04UC_OBJFUN.

objfun should be tested separately before being used in conjunction with e04uc. See also the description of the optional parameter Verify.
iter
Type: System..::.Int32 %
On exit: the number of major iterations performed.
istate
Type: array< System..::.Int32 >[]()[]
An array of size [n+nclin+ncnln]
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 n elements of istate refer to the upper and lower bounds on the variables, the next nL elements refer to the upper and lower bounds on ALx, and the next nN elements refer to the upper and lower bounds on cx. Possible values for istate[j-1] are as follows:
 istate[j-1] 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 bl[j-1]=bu[j-1].
The values -2, -1 and 4 are also acceptable but will be modified by the method. If e04uc has been called previously with the same values of n, nclin and ncnln, istate already contains satisfactory information. The method also adjusts (if necessary) the values supplied in x to be consistent with istate.
Constraint: -2istate[j]4, for j=0,1,,n+nclin+ncnln-1.
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 istate[j-1] is as follows:
 istate[j-1] Meaning -2 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. -1 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. -0 The constraint is satisfied to within the feasibility tolerance, but is not in the QP working set. -1 This inequality constraint is included in the QP working set at its lower bound. -2 This inequality constraint is included in the QP working set at its upper bound. -3 This constraint is included in the QP working set as an equality. This value of istate can occur only when bl[j-1]=bu[j-1].
c
Type: array< System..::.Double >[]()[]
An array of size [max1,ncnln]
On exit: if ncnln>0, c[i-1] contains the value of the ith nonlinear constraint function ci at the final iterate, for i=1,2,,ncnln.
If ncnln=0, the array c is not referenced.
cjac
Type: array< System..::.Double ,2>[,](,)[,]
An array of size [ldcj, dim2]
Note: ldcj must satisfy the constraint: ldcjmax1,ncnln
Note: the second dimension of the array cjac must be at least n if ncnln>0, and at least 1 otherwise.
On entry: in general, cjac need not be initialized before the call to e04uc. However, if Derivative Level=2 or 3, 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 ncnln>0, cjac contains the Jacobian matrix of the nonlinear constraint functions at the final iterate, i.e., cjac[i-1,j-1] contains the partial derivative of the ith constraint function with respect to the jth variable, for i=1,2,,ncnln and j=1,2,,n. (See the discussion of parameter cjac under confun.)
If ncnln=0, the array cjac is not referenced.
clamda
Type: array< System..::.Double >[]()[]
An array of size [n+nclin+ncnln]
On entry: need not be set if the (default) optional parameter Cold Start is used.
If the optional parameter Warm Start has been chosen, clamda[j-1] 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 j=n+nclin+1,n+nclin+2,, n+nclin+ncnln. The remaining elements need not be set. Note that if the jth constraint is defined as ‘inactive’ by the initial value of istate array (i.e., istate[j-1]=0), clamda[j-1] should be zero; if the jth constraint is an inequality active at its lower bound (i.e., istate[j-1]=1), clamda[j-1] should be non-negative; if the jth constraint is an inequality active at its upper bound (i.e., istate[j-1]=2), clamda[j-1] 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. clamda[j-1] should be non-negative if istate[j-1]=1 and non-positive if istate[j-1]=2.
objf
Type: System..::.Double %
On exit: the value of the objective function at the final iterate.
objgrd
Type: array< System..::.Double >[]()[]
An array of size [n]
On exit: the gradient of the objective function at the final iterate (or its finite difference approximation).
r
Type: array< System..::.Double ,2>[,](,)[,]
An array of size [ldr, n]
Note: ldr must satisfy the constraint: ldrn
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 R 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 Hessian=No, r contains the upper triangular Cholesky factor R of QTH~Q, an estimate of the transformed and reordered Hessian of the Lagrangian at x (see (6) in [Overview]). If Hessian=Yes, r contains the upper triangular Cholesky factor R of H, 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..::.e04ucOptions
An object of type E04.e04ucOptions. Used to configure optional parameters to this method.
ifail
Type: System..::.Int32 %
On exit: ifail=0 unless the method detects an error (see [Error Indicators and Warnings]).
e04uc returns with ifail=0 if the iterates have converged to a point x that satisfies the first-order Kuhn–Tucker (see [Overview]) conditions to the accuracy requested by the optional parameter Optimality Tolerance (default value=εR0.8, where εr is the value of the optional parameter Function Precision (default value=ε0.9, where ε is the machine precision)), i.e., the projected gradient and active constraint residuals are negligible at x.
You should check whether the following four conditions are satisfied:
 (i) the final value of Norm Gz (see [Description of the Printed Output]) is significantly less than that at the starting point; (ii) during the final major iterations, the values of Step and Mnr (see [Description of the Printed Output]) are both one; (iii) the last few values of both Norm Gz and Violtn (see [Description of the Printed Output]) become small at a fast linear rate; and (iv) Cond Hz (see [Description of the Printed Output]) is small.
If all these conditions hold, x is almost certainly a local minimum of (1).

Description

e04uc is designed to solve the nonlinear programming problem – the minimization of a smooth nonlinear function subject to a set of constraints on the variables. The problem is assumed to be stated in the following form: where Fx (the objective function) is a nonlinear function, AL is an nL by n constant matrix, and cx is an nN element vector of nonlinear constraint functions. (The matrix AL and the vector cx 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 e04uc will usually solve (1) if there are only isolated discontinuities away from the solution.)
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 li=ui. If certain bounds are not present, the associated elements of l or u can be set to special values that will be treated as - or +. (See the description of the optional parameter Infinite Bound Size.)
If there are no nonlinear constraints in (1) and F is linear or quadratic, then it will generally be more efficient to use one of e04mf or e04nc, or e04nk if the problem is large and sparse. If the problem is large and sparse and does have nonlinear constraints, then e04ug should be used, since e04uc treats all matrices as dense.
You must supply an initial estimate of the solution to (1), together with methods that define Fx, cx and as many first partial derivatives as possible; unspecified derivatives are approximated by finite differences.
The objective function is defined by objfun, and the nonlinear constraints are defined by confun. On every call, these methods must return appropriate values of the objective and nonlinear constraints. You should also provide the available partial derivatives. Any unspecified derivatives are approximated by finite differences; see [Description of the Optional Parameters] 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.
The method used by e04uc is described in detail in [Algorithmic Details].
e04uf is an alternative method which uses exactly the same method, but uses reverse communication for evaluating the objective and constraint functions.

Error Indicators and Warnings

Note: e04uc may return useful information for one or more of the following detected errors or warnings.
Errors or warnings detected by the method:
ifail<0
A negative value of ifail indicates an exit from e04uc because you set mode<0 in objfun or confun. The value of ifail will be the same as your setting of mode.
ifail=1
The final iterate x satisfies the first-order Kuhn–Tucker conditions (see [Overview]) to the accuracy requested, but the sequence of iterates has not yet converged. e04uc 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 (default value=ε0.9, 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 ifail=0 are satisfied, x is likely to be a solution of (1) even if ifail=1.
ifail=2
e04uc 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 (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 (default value=max50,3n+nL+nN). 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 AL are of order unity and are accurate to only three decimal places, Linear Feasibility Tolerance should be at least 10-3.
ifail=3
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, e04uc should be restarted at a different starting point.
ifail=4
The limiting number of iterations (as determined by the optional parameter Major Iteration Limit (default value=max50,3n+nL+10nN)) 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 e04uc or, alternatively, rerun e04uc 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 ifail=6.
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 R 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.
ifail=5
Not used by this method.
ifail=6
x does not satisfy the first-order Kuhn–Tucker conditions (see [Overview]) 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 (default value=εR0.8, where εr is the value of the optional parameter Function Precision (default value=ε0.9, where ε is the machine precision)) is too small. In this case you should apply the four tests outlined in the description of the parameter ifail 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 e04uc 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 ifail=7 and check the gradients using the optional parameter Verify (default value=0). 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 the Printed Output]) is extremely large, it may be worthwhile rerunning e04uc from the final point with the optional parameter Warm Start. In this situation, istate and clamda should be left unaltered and R 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 e04uc with a relaxed value of the Feasibility Tolerance (default value=ε, where ε is the machine precision). (Constraint dependencies are often indicated by wide variations in size in the diagonal elements of the matrix T, whose diagonals will be printed if Major Print Level30).
ifail=7
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 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 x=0 or x=1 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 objective function involves subsidiary data communicated in storage. Although the first evaluation of the function 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 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.
ifail=8
Not used by this method.
ifail=9
An input parameter is invalid.
Overflow
If the printed output before the overflow error contains a warning about serious ill-conditioning in the working set when adding the jth constraint, it may be possible to avoid the difficulty by increasing the magnitude of the optional parameter Linear Feasibility Tolerance and/or the optional parameter Nonlinear Feasibility Tolerance and rerunning the program. If the message recurs even after this change then the offending linearly dependent constraint (with index ‘j’) must be removed from the problem. If overflow occurs in one of the user-supplied delegates (e.g., if the nonlinear functions involve exponentials or singularities), it may help to specify tighter bounds for some of the variables (i.e., reduce the gap between the appropriate lj and uj).
ifail=-4000
ifail=-8000
ifail=-6000

Accuracy

If ifail=0 on exit, then the vector returned in the array x is an estimate of the solution to an accuracy of approximately Optimality Tolerance (default value=ε0.8, where ε is the machine precision).

Description of the Printed Output

This section describes the intermediate printout and final printout produced by e04uc. 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 Major Print Level10 (the default for e04uc, by default no output is produced by e04uc).
The following line of summary output (<80 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 1 in the later iterations, since theoretical analysis predicts that the correct active set will be identified near the solution (see [Algorithmic Details]). 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 αk taken along the computed search direction. On reasonably well-behaved problems, the unit step (i.e., αk=1) will be taken as the solution is approached. Merit Function is the value of the augmented Lagrangian merit function (12) at the current iterate. This function will decrease at each iteration unless it was necessary to increase the penalty parameters (see [The Merit Function]). 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 e04uc terminates with ifail=3 (no feasible point could be found for the nonlinear constraints). If there are no nonlinear constraints present (i.e., ncnln=0) then this entry contains Objective, the value of the objective function Fx. The objective function will decrease monotonically to its optimal value when there are no nonlinear constraints. Norm Gz is ZTgFR, the Euclidean norm of the projected gradient (see [Solution of the Quadratic Programming Subproblem]). 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 HZ  ( HZ = ZT HFR Z = RZT RZ ; see (6)). 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 [The Quasi-Newton Update]). 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 x is close to a Kuhn–Tucker point (see [Section Overview] in e04uf). L is printed if the linesearch has produced a relative change in x 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 R indicates that the approximate Hessian is badly conditioned then the approximate Hessian is refactorized using column interchanges. If necessary, R 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 j, for j=1,2,,n, 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. (The latter situation can occur only when there is no feasible point for the bounds and linear constraints.)
A key is sometimes printed before State.
 A Alternative optimum possible. The variable is active at one of its bounds, but its Lagrange multiplier is essentially zero. This means that if the variable were allowed to start moving away from its bound then there would be no change to the objective function. The values of the other free variables might change, giving a genuine alternative solution. However, if there are any degenerate variables (labelled D), the actual change might prove to be zero, since one of them could encounter a bound immediately. In either case the values of the Lagrange multipliers might also change. D Degenerate. The variable is free, but it is equal to (or very close to) one of its bounds. I Infeasible. The variable is currently violating one of its bounds by more than the Feasibility Tolerance.
Value is the value of the variable at the final iteration.
Lower Bound is the lower bound specified for the variable. None indicates that bl[j-1]-bigbnd.
Upper Bound is the upper bound specified for the variable. None indicates that bu[j-1]bigbnd.
Lagr Mult is the Lagrange multiplier for the associated bound. This will be zero if State is FR unless bl[j-1]-bigbnd and bu[j-1]bigbnd, in which case the entry will be blank. If x 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 bl[j-1] and bu[j-1]. A blank entry indicates that the associated variable is not bounded (i.e., bl[j-1]-bigbnd and bu[j-1]bigbnd).
The meaning of the printout for linear and nonlinear constraints is the same as that given above for variables, with ‘variable’ replaced by ‘constraint’, bl[j-1] and bu[j-1] are replaced by bl[n+j-1] and bu[n+j-1] respectively, and with the following changes in the heading:
 L Con gives the name (L) and index j, for j=1,2,…,nL, of the linear constraint. N Con gives the name (N) and index (j-nL), for j=nL+1,nL+2,…,nL+nN, 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 is based on Problem 71 in Hock and Schittkowski (1981) and involves the minimization of the nonlinear function
 Fx=x1x4x1+x2+x3+x3
subject to the bounds
 1≤x1≤ 5 1≤x2≤ 5 1≤x3≤ 5 1≤x4≤ 5
to the general linear constraint
 x1+x2+x3+x4≤20,
and to the nonlinear constraints
 x12+x22+x32+x42≤ 40, x1x2x3x4≥ 25.
The initial point, which is infeasible, is
 x0=1,5,5,1T,
and Fx0=16.
The optimal solution (to five figures) is
 x*=1.0,4.7430,3.8211,1.3794T,
and Fx*=17.014. One bound constraint and both nonlinear constraints are active at the solution.
The document for (e04ud not in this release) includes an example program to solve the same problem using some of the optional parameters described in [Optional Parameters].

Example program (C#): e04uce.cs

Example program data: e04uce.d

Example program results: e04uce.r

Overview

e04uc is essentially identical to the method NPSOL described in Gill et al. (1986b).
At a solution of (1), some of the constraints will be active, i.e., satisfied exactly. An active simple bound constraint implies that the corresponding variable is fixed at its bound, and hence the variables are partitioned into fixed and free variables. Let c denote the m by n matrix of gradients of the active general linear and nonlinear constraints. The number of fixed variables will be denoted by nFX, with nFR nFR=n-nFX the number of free variables. The subscripts ‘FX’ and ‘FR’ on a vector or matrix will denote the vector or matrix composed of the elements corresponding to fixed or free variables.
A point x is a first-order Kuhn–Tucker point for (1) (see Powell (1974)) if the following conditions hold:
(i) x is feasible;
(ii) there exist vectors ξ and λ (the Lagrange multiplier vectors for the bound and general constraints) such that where g is the gradient of F evaluated at x, and ξj=0 if the jth variable is free.
(iii) The Lagrange multiplier corresponding to an inequality constraint active at its lower bound must be non-negative, and non-positive for an inequality constraint active at its upper bound.
Let Z denote a matrix whose columns form a basis for the set of vectors orthogonal to the rows of CFR; i.e., CFRZ=0. An equivalent statement of the condition (2) in terms of Z is
 ZTgFR=0.
The vector ZTgFR is termed the projected gradient of F at x. Certain additional conditions must be satisfied in order for a first-order Kuhn–Tucker point to be a solution of (1) (see Powell (1974)).
e04uc implements a sequential quadratic programming (SQP) method. For an overview of SQP methods, see, for example, Fletcher (1987), Gill et al. (1981) and Powell (1983).
The search direction p in (3) is the solution of a quadratic programming subproblem of the form where g is the gradient of F at x, the matrix H is a positive-definite quasi-Newton approximation to the Hessian of the Lagrangian function (see [The Quasi-Newton Update]), and AN is the Jacobian matrix of c evaluated at x. (Finite difference estimates may be used for g and AN; see the optional parameter Derivative Level.) Let l in (1) be partitioned into three sections: lB, lL and lN, corresponding to the bound, linear and nonlinear constraints. The vector l- in (4) is similarly partitioned, and is defined as
 l-B=lB-x,  l-L=lL-ALx,   and  l-N=lN-c,
where c is the vector of nonlinear constraints evaluated at x. The vector u- is defined in an analogous fashion.
The estimated Lagrange multipliers at each major iteration are the Lagrange multipliers from the subproblem (4) (and similarly for the predicted active set). (The numbers of bounds, general linear and nonlinear constraints in the QP active set are the quantities Bnd, Lin and Nln in the monitoring file output of e04uc; see [Description of Monitoring Information].) In e04uc, (4) is solved using e04nc. Since solving a quadratic program is itself an iterative procedure, the minor iterations of e04uc are the iterations of e04nc. (More details about solving the subproblem are given in [Solution of the Quadratic Programming Subproblem].)
A theoretical characteristic of SQP methods is that the predicted active set from the QP subproblem (4) is identical to the correct active set in a neighbourhood of x*. In e04uc, this feature is exploited by using the QP active set from the previous iteration as a prediction of the active set for the next QP subproblem, which leads in practice to optimality of the subproblems in only one iteration as the solution is approached. Separate treatment of bound and linear constraints in e04uc also saves computation in factorizing CFR and HQ.
Once p has been computed, the major iteration proceeds by determining a step length α that produces a ‘sufficient decrease’ in an augmented Lagrangian merit function (see [The Merit Function]). Finally, the approximation to the transformed Hessian matrix HQ is updated using a modified BFGS quasi-Newton update (see [The Quasi-Newton Update]) to incorporate new curvature information obtained in the move from x to x-.
On entry to e04uc, an iterative procedure from e04nc is executed, starting with the user-supplied initial point, to find a point that is feasible with respect to the bounds and linear constraints (using the tolerance specified by optional parameter Linear Feasibility Tolerance). If no feasible point exists for the bound and linear constraints, (1) has no solution and e04uc terminates. Otherwise, the problem functions will thereafter be evaluated only at points that are feasible with respect to the bounds and linear constraints. The only exception involves variables whose bounds differ by an amount comparable to the finite difference interval (see the discussion of optional parameter Difference Interval). In contrast to the bounds and linear constraints, it must be emphasised that the nonlinear constraints will not generally be satisfied until an optimal point is reached.
Facilities are provided to check whether the user-supplied gradients appear to be correct (see the description of the optional parameter Verify). In general, the check is provided at the first point that is feasible with respect to the linear constraints and bounds. However, you may request that the check be performed at the initial point.
In summary, the method of e04uc first determines a point that satisfies the bound and linear constraints. Thereafter, each iteration includes:
 (a) the solution of a quadratic programming subproblem; (b) a linesearch with an augmented Lagrangian merit function; and (c) a quasi-Newton update of the approximate Hessian of the Lagrangian function.
These three procedures are described in more detail in [Solution of the Quadratic Programming Subproblem] to [The Quasi-Newton Update].

Solution of the Quadratic Programming Subproblem

The search direction p is obtained by solving (4) using e04nc (see Gill et al. (1986)), which was specifically designed to be used within an SQP algorithm for nonlinear programming.
e04nc is based on a two-phase (primal) quadratic programming method. The two phases of the method are: finding an initial feasible point by minimizing the sum of infeasibilities (the feasibility phase), and minimizing the quadratic objective function within the feasible region (the optimality phase). The computations in both phases are performed by the same methods. The two-phase nature of the algorithm is reflected by changing the function being minimized from the sum of infeasibilities to the quadratic objective function.
In general, a quadratic program must be solved by iteration. Let p denote the current estimate of the solution of (4); the new iterate p- is defined by where, as in (3), σ is a non-negative step length and d is a search direction.
At the beginning of each iteration of e04nc, a working set is defined of constraints (general and bound) that are satisfied exactly. The vector d is then constructed so that the values of constraints in the working set remain unaltered for any move along d. For a bound constraint in the working set, this property is achieved by setting the corresponding element of d to zero, i.e., by fixing the variable at its bound. As before, the subscripts ‘FX’ and ‘FR’ denote selection of the elements associated with the fixed and free variables.
Let c denote the sub-matrix of rows of
 AL AN
corresponding to general constraints in the working set. The general constraints in the working set will remain unaltered if which is equivalent to defining dFR as for some vector dZ, where Z is the matrix associated with the TQ factorization (5) of CFR.

The Merit Function

The merit function (12) and its global convergence properties are described in Gill et al. (1986a).

Description of Monitoring Information

This section describes the long line of output (>80 characters) which forms part of the monitoring information produced by e04uc. (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 Major Print Level5 and Monitoring File0, the following line of output is produced at every major iteration of e04uc on the unit number specified by 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 1 in the later iterations, since theoretical analysis predicts that the correct active set will be identified near the solution (see [Algorithmic Details]).
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 αk taken along the computed search direction. On reasonably well-behaved problems, the unit step (i.e., αk=1) 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 (12) at the current iterate. This function will decrease at each iteration unless it was necessary to increase the penalty parameters (see [The Merit Function]). 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 e04uc terminates with ifail=3 (no feasible point could be found for the nonlinear constraints).
If there are no nonlinear constraints present (i.e., ncnln=0) then this entry contains Objective, the value of the objective function Fx. The objective function will decrease monotonically to its optimal value when there are no nonlinear constraints.
Norm Gz is ZTgFR, the Euclidean norm of the projected gradient (see [Solution of the Quadratic Programming Subproblem]). 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 Z (see [Solution of the Quadratic Programming Subproblem]). The value of Nz is the number of variables minus the number of constraints in the predicted active set; i.e., Nz=n-Bnd+Lin+Nln.
Bnd is the number of simple bound constraints in the predicted active set.
Lin is the number of general linear constraints in the predicted 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 H.
Cond Hz is a lower bound on the condition number of the projected Hessian approximation HZ  ( HZ = ZT HFR Z = RZT RZ ; see (6)). 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 (16)–(18) 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:
 (i) the sequence of iterates has converged; (ii) the projected gradient (Norm Gz) is sufficiently small; and (iii) the norm of the residuals of constraints in the predicted active set (Violtn) is small enough.
If any of these indicators is F when e04uc terminates with ifail=0, 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 [The Quasi-Newton Update]).
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 x is close to a Kuhn–Tucker point (see [Section Overview] in e04uf).
L is printed if the linesearch has produced a relative change in x 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 R indicates that the approximate Hessian is badly conditioned then the approximate Hessian is refactorized using column interchanges. If necessary, R is modified so that its diagonal condition estimator is bounded.