NAG Library Routine Document
E04UGF/E04UGA
Note: this routine uses optional parameters to define choices in the problem specification and in the details of the algorithm. If you wish to use default
settings for all of the optional parameters, you need only read Sections 1 to 9 of this document. If, however, you wish to reset some or all of the settings please refer to Section 10 for a detailed description of the algorithm, to Section 11 for a detailed description of the specification of the optional parameters and to Section 12 for a detailed description of the monitoring information produced by the routine.
1 Purpose
E04UGF/E04UGA solves sparse nonlinear programming problems.
E04UGA is a version of E04UGF that has additional parameters in order to make it safe for use in multithreaded applications (see
Section 5). The initialization routine
E04WBF must have been called before calling E04UGA.
2 Specification
2.1 Specification for E04UGF
SUBROUTINE E04UGF ( |
CONFUN, OBJFUN, N, M, NCNLN, NONLN, NJNLN, IOBJ, NNZ, A, HA, KA, BL, BU, START, NNAME, NAMES, NS, XS, ISTATE, CLAMDA, MINIZ, MINZ, NINF, SINF, OBJ, IZ, LENIZ, Z, LENZ, IUSER, RUSER, IFAIL) |
INTEGER |
N, M, NCNLN, NONLN, NJNLN, IOBJ, NNZ, HA(NNZ), KA(N+1), NNAME, NS, ISTATE(N+M), MINIZ, MINZ, NINF, IZ(LENIZ), LENIZ, LENZ, IUSER(*), IFAIL |
REAL (KIND=nag_wp) |
A(NNZ), BL(N+M), BU(N+M), XS(N+M), CLAMDA(N+M), SINF, OBJ, Z(LENZ), RUSER(*) |
CHARACTER(1) |
START |
CHARACTER(8) |
NAMES(NNAME) |
EXTERNAL |
CONFUN, OBJFUN |
|
2.2 Specification for E04UGA
SUBROUTINE E04UGA ( |
CONFUN, OBJFUN, N, M, NCNLN, NONLN, NJNLN, IOBJ, NNZ, A, HA, KA, BL, BU, START, NNAME, NAMES, NS, XS, ISTATE, CLAMDA, MINIZ, MINZ, NINF, SINF, OBJ, IZ, LENIZ, Z, LENZ, IUSER, RUSER, LWSAV, IWSAV, RWSAV, IFAIL) |
INTEGER |
N, M, NCNLN, NONLN, NJNLN, IOBJ, NNZ, HA(NNZ), KA(N+1), NNAME, NS, ISTATE(N+M), MINIZ, MINZ, NINF, IZ(LENIZ), LENIZ, LENZ, IUSER(*), IWSAV(550), IFAIL |
REAL (KIND=nag_wp) |
A(NNZ), BL(N+M), BU(N+M), XS(N+M), CLAMDA(N+M), SINF, OBJ, Z(LENZ), RUSER(*), RWSAV(550) |
LOGICAL |
LWSAV(20) |
CHARACTER(1) |
START |
CHARACTER(8) |
NAMES(NNAME) |
EXTERNAL |
CONFUN, OBJFUN |
|
Before calling E04UGA, or
either of the option setting routines
E04UHA or
E04UJA,
E04WBF must be called. The specification for
E04WBF is:
INTEGER |
LCWSAV, LLWSAV, IWSAV(LIWSAV), LIWSAV, LRWSAV, IFAIL |
REAL (KIND=nag_wp) |
RWSAV(LRWSAV) |
LOGICAL |
LWSAV(LLWSAV) |
CHARACTER(*) |
RNAME |
CHARACTER(80) |
CWSAV(LCWSAV) |
|
E04WBF should be called with
.
LCWSAV,
LLWSAV,
LIWSAV and
LRWSAV, the declared lengths of
CWSAV,
LWSAV,
IWSAV and
RWSAV respectively, must satisfy:
The contents of the
arrays
CWSAV,
LWSAV,
IWSAV and
RWSAVmust not be altered between calling routines
E04UGA,
E04UHA,
E04UJA and
E04WBF.
3 Description
E04UGF/E04UGA is designed to solve a class of nonlinear programming problems that are assumed to be stated in the following general form:
where
is a set of variables,
is a smooth scalar objective function,
and
are constant lower and upper bounds,
is a vector of smooth nonlinear constraint functions
and
is a
sparse matrix.
The constraints involving
and
are called the
general constraints. Note that upper and lower bounds are specified for all variables and constraints. This form allows full generality in specifying various types of constraint. In particular, the
th constraint can be defined as an
equality 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.)
E04UGF/E04UGA converts the upper and lower bounds on the
elements of
and
to equalities by introducing a set of
slack variables
, where
. For example, the linear constraint
is replaced by
, together with the bounded slack
. The problem defined by
(1) can therefore be re-written in the following equivalent form:
Since the slack variables
are subject to the same upper and lower bounds as the elements of
and
, the bounds on
and
can simply be thought of as bounds on the combined vector
. The elements of
and
are partitioned into
basic,
nonbasic and
superbasic variables defined as follows:
– |
a basic variable ( say) is the th variable associated with the th column of the basis matrix ; |
– |
a nonbasic variable is a variable that is temporarily fixed at its current value (usually its upper or lower bound); |
– |
a superbasic variable is a nonbasic variable which is not at one of its bounds that is free to move in any desired direction (namely one that will improve the value of the objective function or reduce the sum of infeasibilities). |
For example, in the simplex method (see
Gill et al. (1981)) the elements of
can be partitioned at each vertex into a set of
basic variables (all non-negative) and a set of
nonbasic variables (all zero). This is equivalent to partitioning the columns of the constraint matrix as
, where
contains the
columns that correspond to the basic variables and
contains the
columns that correspond to the nonbasic variables. Note that
is square and nonsingular.
The optional parameter
Maximize may be used to specify an alternative problem in which
is maximized. If the objective function is nonlinear and all the constraints are linear,
is absent and the problem is said to be
linearly constrained. In general, the objective and constraint functions are
structured in the sense that they are formed from sums of linear and nonlinear functions. This structure can be exploited by the routine during the solution process as follows.
Consider the following nonlinear optimization problem with four variables (
):
subject to the constraints
and to the bounds
This problem has several characteristics that can be exploited by the routine:
– |
the objective function is nonlinear. It is the sum of a nonlinear function of the variables () and a linear function of the variables (); |
– |
the first two constraints are nonlinear. The third is linear; |
– |
each nonlinear constraint function is the sum of a nonlinear function of the variables () and a linear function of the variables (). |
The nonlinear terms are defined by
OBJFUN and
CONFUN (see
Section 5), which involve only the appropriate subset of variables.
For the objective, we define the function
to include only the nonlinear part of the objective. The three variables (
) associated with this function are known as the
nonlinear objective variables. The number of them is given by
NONLN (see
Section 5) and they are the only variables needed in
OBJFUN. The linear part
of the objective is stored in row
IOBJ (see
Section 5) of the (constraint) Jacobian matrix
(see below).
Thus, if
and
denote the nonlinear and linear objective variables, respectively, the objective may be re-written in the form
where
is the nonlinear part of the objective and
and
are constant vectors that form a row of
. In this example,
and
.
Similarly for the constraints, we define a vector function
to include just the nonlinear terms. In this example,
and
, where the two variables (
) are known as the
nonlinear Jacobian variables. The number of them is given by
NJNLN (see
Section 5) and they are the only variables needed in
CONFUN. Thus, if
and
denote the nonlinear and linear Jacobian variables, respectively, the constraint functions and the linear part of the objective have the form
where
and
in this example. This ensures that the Jacobian is of the form
where
. Note that
always appears in the
top left-hand corner of
.
The inequalities
and
implied by the constraint functions in
(3) are known as the
nonlinear and
linear constraints, respectively. The nonlinear constraint vector
in
(3) and (optionally) its partial derivative matrix
are set in
CONFUN. The matrices
,
and
contain any (constant) linear terms. Along with the sparsity pattern of
they are stored in the arrays
A,
HA and
KA (see
Section 5).
In general, the vectors and have different dimensions, but they always overlap, in the sense that the shorter vector is always the beginning of the other. In the above example, the nonlinear Jacobian variables are an ordered subset of the nonlinear objective variables . In other cases it could be the other way round (whichever is the most convenient), but the first way keeps as small as possible.
Note that the nonlinear objective function
may involve either a subset or superset of the variables appearing in the nonlinear constraint functions
. Thus,
(or vice-versa). Sometimes the objective and constraints really involve
disjoint sets of nonlinear variables. In such cases the variables should be ordered so that
and
, where the objective is nonlinear in just the last vector
. The first
NJNLN elements of the gradient array
OBJGRD should also be set to zero in
OBJFUN. This is illustrated in
Section 9.
If all elements of the constraint Jacobian are known (i.e., the optional parameter
or
), any constant elements may be assigned their correct values in
A,
HA and
KA. The corresponding elements of the constraint Jacobian array
FJAC need not be reset in
CONFUN. This includes values that are identically zero as constraint Jacobian elements are assumed to be zero unless specified otherwise. It must be emphasized that, if
or
, unassigned elements of
FJAC are
not treated as constant; they are estimated by finite differences, at nontrivial expense.
If there are no nonlinear constraints in
(1) and
is linear or quadratic, then it may be more efficient to use
E04NQF to solve the resulting linear or quadratic programming problem, or one of
E04MFF/E04MFA,
E04NCF/E04NCA or
E04NFF/E04NFA if
is a
dense matrix. If the problem is dense and does have nonlinear constraints then one of
E04UFF/E04UFA,
E04USF/E04USA or
E04WDF (as appropriate) should be used instead.
You must supply an initial estimate of the solution to
(1), together with versions of
OBJFUN and
CONFUN that define
and
, respectively, and as many first partial derivatives as possible. Note that if there are any nonlinear constraints, then the
first call to
CONFUN will precede the
first call to
OBJFUN.
E04UGF/E04UGA is based on the SNOPT package described in
Gill et al. (2002), which in turn utilizes routines from the MINOS package (see
Murtagh and Saunders (1995)). It incorporates a sequential quadratic programming (SQP) method that obtains search directions from a sequence of quadratic programming (QP) subproblems. Each QP subproblem minimizes a quadratic model of a certain Lagrangian function subject to a linearization of the constraints. An augmented Lagrangian merit function is reduced along each search direction to ensure convergence from any starting point. Further details can be found in
Section 10.
Throughout this document the symbol
is used to represent the
machine precision (see
X02AJF).
4 References
Conn A R (1973) Constrained optimization using a nondifferentiable penalty function SIAM J. Numer. Anal. 10 760–779
Eldersveld S K (1991) Large-scale sequential quadratic programming algorithms PhD Thesis Department of Operations Research, Stanford University, Stanford
Fletcher R (1984) An penalty method for nonlinear constraints Numerical Optimization 1984 (eds P T Boggs, R H Byrd and R B Schnabel) 26–40 SIAM Philadelphia
Fourer R (1982) Solving staircase linear programs by the simplex method Math. Programming 23 274–313
Gill P E, Murray W and Saunders M A (2002) SNOPT: An SQP Algorithm for Large-scale Constrained Optimization 12 979–1006 SIAM J. Optim.
Gill P E, Murray W, Saunders M A and Wright M H (1986) Users' guide for NPSOL (Version 4.0): a Fortran package for nonlinear programming Report SOL 86-2 Department of Operations Research, Stanford University
Gill P E, Murray W, Saunders M A and Wright M H (1989) A practical anti-cycling procedure for linearly constrained optimization Math. Programming 45 437–474
Gill P E, Murray W, Saunders M A and Wright M H (1992) Some theoretical properties of an augmented Lagrangian merit function Advances in Optimization and Parallel Computing (ed P M Pardalos) 101–128 North Holland
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
Murtagh B A and Saunders M A (1995) MINOS 5.4 users' guide Report SOL 83-20R Department of Operations Research, Stanford University
Ortega J M and Rheinboldt W C (1970) Iterative Solution of Nonlinear Equations in Several Variables Academic Press
Powell M J D (1974) Introduction to constrained optimization Numerical Methods for Constrained Optimization (eds P E Gill and W Murray) 1–28 Academic Press
5 Parameters
- 1: CONFUN – 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 E04UGF/E04UGA and
CONFUN may be the dummy routine E04UGM. (E04UGM 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:
INTEGER |
MODE, NCNLN, NJNLN, NNZJAC, NSTATE, IUSER(*) |
REAL (KIND=nag_wp) |
X(NJNLN), F(NCNLN), FJAC(NNZJAC), RUSER(*) |
|
- 1: MODE – INTEGERInput/Output
On entry: indicates which values must be assigned during each call of
CONFUN. Only the following values need be assigned:
- F.
- All available elements of FJAC.
- F and all available elements of FJAC.
On exit: you may set to a negative value as follows:
- The solution to the current problem is terminated and in this case E04UGF/E04UGA will terminate with IFAIL set to MODE.
- The nonlinear constraint functions cannot be calculated at the current . E04UGF/E04UGA will then terminate with unless this occurs during the linesearch; in this case, the linesearch will shorten the step and try again.
- 2: NCNLN – INTEGERInput
On entry:
, the number of nonlinear constraints. These must be the first
NCNLN constraints in the problem.
- 3: NJNLN – INTEGERInput
On entry:
, the number of nonlinear variables. These must be the first
NJNLN variables in the problem.
- 4: NNZJAC – INTEGERInput
On entry: the number of nonzero elements in the constraint Jacobian. Note that
NNZJAC will usually be less than
.
- 5: X(NJNLN) – REAL (KIND=nag_wp) arrayInput
On entry: , the vector of nonlinear Jacobian variables at which the nonlinear constraint functions and/or the available elements of the constraint Jacobian are to be evaluated.
- 6: F(NCNLN) – REAL (KIND=nag_wp) arrayOutput
On exit: if or , must contain the value of the th nonlinear constraint function at .
- 7: FJAC(NNZJAC) – REAL (KIND=nag_wp) arrayInput/Output
On entry: the elements of
FJAC are set to special values which enable E04UGF/E04UGA to detect whether they are changed by
CONFUN.
On exit: if
or
,
FJAC must return the available elements of the constraint Jacobian evaluated at
. These elements must be stored in exactly the same positions as implied by the definitions of the arrays
A,
HA and
KA. If optional parameter
or
, the value of any constant Jacobian element not defined by
CONFUN will be obtained directly from
A. Note that the routine does not perform any internal checks for consistency (except indirectly via the optional parameter
Verify Level), so great care is essential.
- 8: NSTATE – INTEGERInput
On entry: if
, then E04UGF/E04UGA is calling
CONFUN for the first time. This parameter setting allows you to save computation time if certain data must be read or calculated only once.
If
, then E04UGF/E04UGA is calling
CONFUN for the last time. This parameter setting allows you to perform some additional computation on the final solution. In general, the last call to
CONFUN is made with
(see
Section 6).
Otherwise, .
- 9: IUSER() – INTEGER arrayUser Workspace
- 10: RUSER() – REAL (KIND=nag_wp) arrayUser Workspace
-
CONFUN is called with the parameters
IUSER and
RUSER as supplied to E04UGF/E04UGA. 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 E04UGF/E04UGA is called. Parameters denoted as
Input must
not be changed by this procedure.
- 2: OBJFUN – SUBROUTINE, supplied by the NAG Library or the user.External Procedure
OBJFUN must calculate the nonlinear part of the objective function
and (optionally) its gradient
for a specified
(
) element vector
. If there are no nonlinear objective variables (i.e.,
),
OBJFUN will never be called by E04UGF/E04UGA and
OBJFUN may be the dummy routine E04UGN. (E04UGN is included in the NAG Library.)
The specification of
OBJFUN is:
INTEGER |
MODE, NONLN, NSTATE, IUSER(*) |
REAL (KIND=nag_wp) |
X(NONLN), OBJF, OBJGRD(NONLN), RUSER(*) |
|
- 1: MODE – INTEGERInput/Output
On entry: indicates which values must be assigned during each call of
OBJFUN. Only the following values need be assigned:
- OBJF.
- All available elements of OBJGRD.
- OBJF and all available elements of OBJGRD.
On exit: you may set to a negative value as follows:
- The solution to the current problem is terminated and in this case E04UGF/E04UGA will terminate with IFAIL set to MODE.
- The nonlinear part of the objective function cannot be calculated at the current . E04UGF/E04UGA will then terminate with unless this occurs during the linesearch; in this case, the linesearch will shorten the step and try again.
- 2: NONLN – INTEGERInput
On entry:
, the number of nonlinear objective variables. These must be the first
NONLN variables in the problem.
- 3: X(NONLN) – REAL (KIND=nag_wp) arrayInput
On entry: , the vector of nonlinear variables at which the nonlinear part of the objective function and/or all available elements of its gradient are to be evaluated.
- 4: OBJF – REAL (KIND=nag_wp)Output
On exit: if
or
,
OBJF must be set to the value of the objective function at
.
- 5: OBJGRD(NONLN) – REAL (KIND=nag_wp) arrayInput/Output
On entry: the elements of
OBJGRD are set to special values which enable E04UGF/E04UGA to detect whether they are changed by
OBJFUN.
On exit: if
or
,
OBJGRD must return the available elements of the gradient evaluated at
.
- 6: NSTATE – INTEGERInput
On entry: if
, E04UGF/E04UGA is calling
OBJFUN for the first time. This parameter setting allows you to save computation time if certain data must be read or calculated only once.
If
, E04UGF/E04UGA is calling
OBJFUN for the last time. This parameter setting allows you to perform some additional computation on the final solution. In general, the last call to
OBJFUN is made with
(see
Section 6).
Otherwise, .
- 7: IUSER() – INTEGER arrayUser Workspace
- 8: RUSER() – REAL (KIND=nag_wp) arrayUser Workspace
-
OBJFUN is called with the parameters
IUSER and
RUSER as supplied to E04UGF/E04UGA. 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 E04UGF/E04UGA is called. Parameters denoted as
Input must
not be changed by this procedure.
- 3: N – INTEGERInput
On entry: , the number of variables (excluding slacks). This is the number of columns in the full Jacobian matrix .
Constraint:
.
- 4: M – INTEGERInput
On entry:
, the number of general constraints (or slacks). This is the number of rows in
, including the free row (if any; see
IOBJ). Note that
must contain at least one row. If your problem has no constraints, or only upper and lower bounds on the variables, then you must include a dummy ‘free’ row consisting of a single (zero) element subject to ‘infinite’ upper and lower bounds. Further details can be found under the descriptions for
IOBJ,
NNZ,
A,
HA,
KA,
BL and
BU.
Constraint:
.
- 5: NCNLN – INTEGERInput
On entry: , the number of nonlinear constraints.
Constraint:
.
- 6: NONLN – INTEGERInput
On entry:
, the number of nonlinear objective variables. If the objective function is nonlinear, the leading
columns of
belong to the nonlinear objective variables. (See also the description for
NJNLN.)
Constraint:
.
- 7: NJNLN – INTEGERInput
On entry: , the number of nonlinear Jacobian variables. If there are any nonlinear constraints, the leading columns of belong to the nonlinear Jacobian variables. If and , the nonlinear objective and Jacobian variables overlap. The total number of nonlinear variables is given by .
Constraints:
- if , ;
- if , .
- 8: IOBJ – INTEGERInput
On entry: if
, row
IOBJ of
is a free row containing the nonzero elements of the linear part of the objective function.
- There is no free row.
- There is a dummy ‘free’ row.
Constraints:
- if , ;
- otherwise .
- 9: NNZ – INTEGERInput
On entry: the number of nonzero elements in (including the Jacobian for any nonlinear constraints). If , set .
Constraint:
.
- 10: A(NNZ) – REAL (KIND=nag_wp) arrayInput/Output
On entry: the nonzero elements of the Jacobian matrix
, ordered by increasing column index. Since the constraint Jacobian matrix
must always appear in the top left-hand corner of
, those elements in a column associated with any nonlinear constraints must come before any elements belonging to the linear constraint matrix
and the free row (if any; see
IOBJ).
In general,
A is partitioned into a nonlinear part and a linear part corresponding to the nonlinear variables and linear variables in the problem. Elements in the nonlinear part may be set to any value (e.g., zero) because they are initialized at the first point that satisfies the linear constraints and the upper and lower bounds.
If
or
, the nonlinear part may also be used to store any constant Jacobian elements. Note that if
CONFUN does not define the constant Jacobian element
then the missing value will be obtained directly from
for some
.
If
or
, unassigned elements of
FJAC are
not treated as constant; they are estimated by finite differences, at nontrivial expense.
The linear part must contain the nonzero elements of
and the free row (if any). If
, set
. Elements with the same row and column indices are not allowed. (See also the descriptions for
HA and
KA.)
On exit: elements in the nonlinear part corresponding to nonlinear Jacobian variables are overwritten.
- 11: HA(NNZ) – INTEGER arrayInput
On entry:
must contain the row index of the nonzero element stored in
, for
. The row indices for a column may be supplied in any order subject to the condition that those elements in a column associated with any nonlinear constraints must appear before those elements associated with any linear constraints (including the free row, if any). Note that
CONFUN must define the Jacobian elements in the same order. If
, set
.
Constraint:
, for .
- 12: KA() – INTEGER arrayInput
On entry:
must contain the index in
A of the start of the
th column, for
. To specify the
th column as empty, set
. Note that the first and last elements of
KA must be such that
and
. If
, set
, for
.
Constraints:
- ;
- , for ;
- ;
- , for .
- 13: BL() – REAL (KIND=nag_wp) arrayInput
On entry:
, the lower bounds for all the variables and general constraints, in the following order. The first
N elements of
BL must contain the bounds on the variables
, the next
NCNLN elements the bounds for the nonlinear constraints
(if any) and the next (
) elements the bounds for the linear constraints
and the free row (if any). To specify a nonexistent lower bound (i.e.,
), set
. To specify the
th constraint as an
equality, set
, say, where
. If
, set
.
Constraint:
if
or
,
(See also the description for
BU.)
- 14: BU() – REAL (KIND=nag_wp) arrayInput
On entry:
, the upper bounds for all the variables and general constraints, in the following order. The first
N elements of
BU must contain the bounds on the variables
, the next
NCNLN elements the bounds for the nonlinear constraints
(if any) and the next (
) elements the bounds for the linear constraints
and the free row (if any). To specify a nonexistent upper bound (i.e.,
), set
. To specify the
th constraint as an
equality, set
, say, where
. If
, set
.
Constraints:
- if or , ;
- , for ;
- if , .
- 15: START – CHARACTER(1)Input
On entry: indicates how a starting basis is to be obtained.
- An internal Crash procedure will be used to choose an initial basis.
- A basis is already defined in ISTATE and NS (probably from a previous call).
Constraint:
or .
- 16: NNAME – INTEGERInput
On entry: the number of column (i.e., variable) and row (i.e., constraint) names supplied in
NAMES.
- There are no names. Default names will be used in the printed output.
- All names must be supplied.
Constraint:
or .
- 17: NAMES(NNAME) – CHARACTER(8) arrayInput
On entry: specifies the column and row names to be used in the printed output.
If
,
NAMES is not referenced and the printed output will use default names for the columns and rows.
If
, the first
N elements must contain the names for the columns, the next
NCNLN elements must contain the names for the nonlinear rows (if any) and the next
elements must contain the names for the linear rows (if any) to be used in the printed output. Note that the name for the free row or dummy ‘free’ row must be stored in
.
- 18: NS – INTEGERInput/Output
On entry: , the number of superbasics. It need not be specified if , but must retain its value from a previous call when .
On exit: the final number of superbasics.
- 19: XS() – REAL (KIND=nag_wp) arrayInput/Output
On entry: the initial values of the variables and slacks
. (See the description for
ISTATE.)
On exit: the final values of the variables and slacks .
- 20: ISTATE() – INTEGER arrayInput/Output
On entry: if
, the first
N elements of
ISTATE and
XS must specify the initial states and values, respectively, of the variables
. (The slacks
need not be initialized.) An internal Crash procedure is then used to select an initial basis matrix
. The initial basis matrix will be triangular (neglecting certain small elements in each column). It is chosen from various rows and columns of
. Possible values for
are as follows:
| State of during Crash procedure |
or | Eligible for the basis |
| Ignored |
| Eligible for the basis (given preference over or ) |
or | Ignored |
If nothing special is known about the problem, or there is no wish to provide special information, you may set
and , for . All variables will then be eligible for the initial basis. Less trivially, to say that the th variable will probably be equal to one of its bounds, set and or and as appropriate.
Following the Crash procedure, variables for which are made superbasic. Other variables not selected for the basis are then made nonbasic at the value if , or at the value or closest to .
If
,
ISTATE and
XS must specify the initial states and values, respectively, of the variables and slacks
. If the routine has been called previously with the same values of
N and
M,
ISTATE already contains satisfactory information.
Constraints:
- if , , for ;
- if , , for .
On exit: the final states of the variables and slacks
. The significance of each possible value of
is as follows:
| State of variable | Normal value of |
| Nonbasic | |
| Nonbasic | |
| Superbasic | Between and |
| Basic | Between and |
If
, basic and superbasic variables may be outside their bounds by as much as the value of the optional parameter
Minor Feasibility Tolerance. Note that if scaling is specified, the optional parameter
Minor Feasibility Tolerance applies to the variables of the
scaled problem. In this case, the variables of the original problem may be as much as
outside their bounds, but this is unlikely unless the problem is very badly scaled.
Very occasionally some nonbasic variables may be outside their bounds by as much as the optional parameter
Minor Feasibility Tolerance and there may be some nonbasic variables for which
lies strictly between its bounds.
If
, some basic and superbasic variables may be outside their bounds by an arbitrary amount (bounded by
SINF if scaling was not used).
- 21: CLAMDA() – REAL (KIND=nag_wp) arrayInput/Output
On entry: if ,
must contain a Lagrange multiplier estimate for the th nonlinear constraint , for . If nothing special is known about the problem, or there is no wish to provide special information, you may set . The remaining elements need not be set.
On exit: a set of Lagrange multipliers for the bounds on the variables (
reduced costs) and the general constraints (
shadow costs). More precisely, the first
N elements contain the multipliers for the bounds on the variables, the next
NCNLN elements contain the multipliers for the nonlinear constraints
(if any) and the next (
) elements contain the multipliers for the linear constraints
and the free row (if any).
- 22: MINIZ – INTEGEROutput
On exit: the minimum value of
LENIZ required to start solving the problem. If
, E04UGF/E04UGA may be called again with
LENIZ suitably larger than
MINIZ. (The bigger the better, since it is not certain how much workspace the basis factors need.)
- 23: MINZ – INTEGEROutput
On exit: the minimum value of
LENZ required to start solving the problem. If
, E04UGF/E04UGA may be called again with
LENZ suitably larger than
MINZ. (The bigger the better, since it is not certain how much workspace the basis factors need.)
- 24: NINF – INTEGEROutput
On exit: the number of constraints that lie outside their bounds by more than the value of the optional parameter
Minor Feasibility Tolerance.
If the
linear constraints are infeasible, the sum of the infeasibilities of the linear constraints is minimized subject to the upper and lower bounds being satisfied. In this case,
NINF contains the number of elements of
that lie outside their upper or lower bounds. Note that the nonlinear constraints are not evaluated.
Otherwise, the sum of the infeasibilities of the
nonlinear constraints is minimized subject to the linear constraints and the upper and lower bounds being satisfied. In this case,
NINF contains the number of elements of
that lie outside their upper or lower bounds.
- 25: SINF – REAL (KIND=nag_wp)Output
On exit: the sum of the infeasibilities of constraints that lie outside their bounds by more than the value of the optional parameter
Minor Feasibility Tolerance.
- 26: OBJ – REAL (KIND=nag_wp)Output
On exit: the value of the objective function.
- 27: IZ(LENIZ) – INTEGER arrayWorkspace
- 28: LENIZ – INTEGERInput
On entry: the dimension of the array
IZ as declared in the (sub)program from which E04UGF/E04UGA is called.
Constraint:
.
- 29: Z(LENZ) – REAL (KIND=nag_wp) arrayWorkspace
- 30: LENZ – INTEGERInput
On entry: the dimension of the array
Z as declared in the (sub)program from which E04UGF/E04UGA is called.
Constraint:
.
The amounts of workspace provided (i.e.,
LENIZ and
LENZ) and required (i.e.,
MINIZ and
MINZ) are (by default) output on the current advisory message unit (as defined by
X04ABF). Since the minimum values of
LENIZ and
LENZ required to start solving the problem are returned in
MINIZ and
MINZ respectively, you may prefer to obtain appropriate values from the output of a preliminary run with
LENIZ set to
and/or
LENZ set to
. (E04UGF/E04UGA will then terminate with
or
.)
- 31: IUSER() – INTEGER arrayUser Workspace
- 32: RUSER() – REAL (KIND=nag_wp) arrayUser Workspace
-
IUSER and
RUSER are not used by E04UGF/E04UGA, but are passed directly to
CONFUN and
OBJFUN and may be used to pass information to these routines as an alternative to using COMMON global variables.
- 33: IFAIL – INTEGERInput/Output
-
Note: for E04UGA, IFAIL does not occur in this position in the parameter list. See the additional parameters described below.
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).
E04UGF/E04UGA returns with
if the iterates have converged to a point
that satisfies the first-order Kuhn–Karesh–Tucker conditions (see
Section 8.1) to the accuracy requested by the optional parameters
Major Feasibility Tolerance (
) and
Major Optimality Tolerance (
).
- Note: the following are additional parameters for specific use with E04UGA. Users of E04UGF therefore need not read the remainder of this description.
- 33: LWSAV() – LOGICAL arrayCommunication Array
- 34: IWSAV() – INTEGER arrayCommunication Array
- 35: RWSAV() – REAL (KIND=nag_wp) arrayCommunication Array
The arrays
LWSAV,
IWSAV and
RWSAV must not be altered between calls to any of the routines E04UGA,
E04UHA or
E04UJA.
- 36: IFAIL – INTEGERInput/Output
Note: see the parameter description for
IFAIL above.
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: E04UGF/E04UGA may return useful information for one or more of the following detected errors or warnings.
Errors or warnings detected by the routine:
A negative value of
IFAIL indicates an exit from E04UGF/E04UGA because you set
in
OBJFUN or
CONFUN. The value of
IFAIL will be the same as your setting of
MODE.
The problem is infeasible. The general constraints cannot all be satisfied simultaneously to within the values of the optional parameters
Major Feasibility Tolerance (
) and
Minor Feasibility Tolerance (
).
The problem is unbounded (or badly scaled). The objective function is not bounded below (or above in the case of maximization) in the feasible region because a nonbasic variable can apparently be increased or decreased by an arbitrary amount without causing a basic variable to violate a bound. Add an upper or lower bound to the variable (whose index is printed by default by E04UGF) and rerun E04UGF/E04UGA.
The problem may be unbounded. Check that the values of the optional parameters
Unbounded Objective (
) and
Unbounded Step Size (
) are not too small. This exit also implies that the objective function is not bounded below (or above in the case of maximization) in the feasible region defined by expanding the bounds by the value of the optional parameter
Violation Limit (
).
Too many iterations. The values of the optional parameters
Major Iteration Limit (
) and/or
Iteration Limit (
) are too small.
Feasible solution found, but requested accuracy could not be achieved. Check that the value of the optional parameter
Major Optimality Tolerance (
) is not too small (say,
).
The value of the optional parameter
Superbasics Limit (
) is too small.
-
An input parameter is invalid.
The user-supplied derivatives of the objective function computed by
OBJFUN appear to be incorrect. Check that
OBJFUN has been coded correctly and that all relevant elements of the objective gradient have been assigned their correct values.
The user-supplied derivatives of the nonlinear constraint functions computed by
CONFUN appear to be incorrect. Check that
CONFUN has been coded correctly and that all relevant elements of the nonlinear constraint Jacobian have been assigned their correct values.
The current point cannot be improved upon. Check that
OBJFUN and
CONFUN have been coded correctly and that they are consistent with the value of the optional parameter
Derivative Level (
).
Numerical error in trying to satisfy the linear constraints (or the linearized nonlinear constraints). The basis is very ill-conditioned.
Not enough integer workspace for the basis factors. Increase
LENIZ and rerun E04UGF/E04UGA.
Not enough real workspace for the basis factors. Increase
LENZ and rerun E04UGF/E04UGA.
The basis is singular after
attempts to factorize it (and adding slacks where necessary). Either the problem is badly scaled or the value of the optional parameter
LU Factor Tolerance (
or
) is too large.
Not enough integer workspace to start solving the problem. Increase
LENIZ to at least
MINIZ and rerun E04UGF/E04UGA.
Not enough real workspace to start solving the problem. Increase
LENZ to at least
MINZ and rerun E04UGF/E04UGA.
An unexpected error has occurred. Please contact
NAG.
7 Accuracy
If the value of the optional parameter
Major Optimality Tolerance is set to
(
) and
on exit, then the final value of
should have approximately
correct significant digits.
This section contains a description of the printed output.
8.1 Major Iteration Printout
This section describes the intermediate printout and final printout produced by the major iterations of E04UGF/E04UGA. The intermediate printout is a subset of the monitoring information produced by the routine at every iteration (see
Section 12). 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 E04UGF, by default no output is produced by E04UGA).
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 Section 10).
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 (6) at the current iterate. This function will decrease at each iteration unless it was necessary to increase the penalty parameters
(see Section 8.1).
As the solution is approached, Merit Function will converge to the value of the objective function at the solution.
In elastic mode (see Section 10.2) then the merit function is a composite function involving the constraint violations weighted by the value of the optional parameter Elastic Weight. If there are no nonlinear constraints present then this entry contains Objective, the value of the objective function . In this case, will decrease monotonically to its optimal value.
|
Feasibl |
is the value of rowerr, the largest element of the scaled nonlinear constraint residual vector defined in the description of the optional parameter Major Feasibility Tolerance. The solution is regarded as ‘feasible’ if Feasibl is less than (or equal to) the optional parameter Major Feasibility Tolerance. Feasibl will be approximately zero in the neighbourhood of a solution. If there are no nonlinear constraints present, all iterates are feasible and this entry is not printed.
|
Optimal |
is the value of maxgap, the largest element of the maximum complementarity gap vector defined in the description of the optional parameter Major Optimality Tolerance. The Lagrange multipliers are regarded as ‘optimal’ if Optimal is less than (or equal to) the optional parameter Major Optimality Tolerance. Optimal will be approximately zero in the neighbourhood of a solution.
|
Cond Hz |
is an estimate of the condition number of the reduced Hessian of the Lagrangian (not printed if NCNLN and NONLN are both zero). It is the square of the ratio between the largest and smallest diagonal elements of the upper triangular matrix . This constitutes a lower bound on the condition number of the matrix that approximates the reduced Hessian. The larger this number, the more difficult the problem.
|
PD |
is a two-letter indication of the status of the convergence tests involving the feasibility and optimality of the iterates defined in the descriptions of the optional parameters Major Feasibility Tolerance and Major Optimality Tolerance. Each letter is T if the test is satisfied and F otherwise. The tests indicate whether the values of Feasibl and Optimal are sufficiently small. For example, TF or TT is printed if there are no nonlinear constraints present (since all iterates are feasible). If either indicator is F when E04UGF/E04UGA terminates with , you should check the solution carefully.
|
M |
is printed if an extra evaluation of user-supplied subroutines OBJFUN and CONFUN was needed in order to define an acceptable positive definite quasi-Newton update to the Hessian of the Lagrangian. This modification is only performed when there are nonlinear constraints present.
|
m |
is printed if, in addition, it was also necessary to modify the update to include an augmented Lagrangian term.
|
s |
is printed if a self-scaled BFGS (Broyden–Fletcher–Goldfarb–Shanno) update was performed. This update is always used when the Hessian approximation is diagonal and hence always follows a Hessian reset.
|
S |
is printed if, in addition, it was also necessary to modify the self-scaled update in order to maintain positive-definiteness.
|
n |
is printed if no positive definite BFGS update could be found, in which case the approximate Hessian is unchanged from the previous iteration.
|
r |
is printed if the approximate Hessian was reset after consecutive major iterations in which no BFGS update could be made. The diagonal elements of the approximate Hessian are retained if at least one update has been performed since the last reset. Otherwise, the approximate Hessian is reset to the identity matrix.
|
R |
is printed if the approximate Hessian has been reset by discarding all but its diagonal elements. This reset will be forced periodically by the values of the optional parameters Hessian Frequency and Hessian Updates. However, it may also be necessary to reset an ill-conditioned Hessian from time to time.
|
l |
is printed if the change in the norm of the variables was greater than the value defined by the optional parameter Major Step Limit. If this output occurs frequently during later iterations, it may be worthwhile increasing the value of Major Step Limit.
|
c |
is printed if central differences have been used to compute the unknown elements of the objective and constraint gradients. A switch to central differences is made if either the linesearch gives a small step, or is close to being optimal. In some cases, it may be necessary to re-solve the QP subproblem with the central difference gradient and Jacobian.
|
u |
is printed if the QP subproblem was unbounded.
|
t |
is printed if the minor iterations were terminated after the number of iterations specified by the value of the optional parameter Minor Iteration Limit was reached.
|
i |
is printed if the QP subproblem was infeasible when the routine was not in elastic mode. This event triggers the start of nonlinear elastic mode, which remains in effect for all subsequent iterations. Once in elastic mode, the QP subproblems are associated with the elastic problem (8) (see Section 10.2). It is also printed if the minimizer of the elastic subproblem does not satisfy the linearized constraints when the routine is already in elastic mode. (In this case, a feasible point for the usual QP subproblem may or may not exist.)
|
w |
is printed if a weak solution of the QP subproblem was found.
|
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.
Variable |
gives the name of the variable. If , a default name is assigned to the th variable, for . If , the name supplied in is assigned to the th variable.
|
State |
gives the state of the variable (LL if nonbasic on its lower bound, UL if nonbasic on its upper bound, EQ if nonbasic and fixed, FR if nonbasic and strictly between its bounds, BS if basic and SBS if superbasic).
A key is sometimes printed before State.
Note that unless the optional parameter is specified, the tests for assigning a key are applied to the variables of the scaled problem.
A |
Alternative optimum possible. The variable is nonbasic, but its reduced gradient is essentially zero. This means that if the variable were allowed to start moving away from its current value, there would be no change in the value of the objective function. The values of the basic and superbasic variables might change, giving a genuine alternative solution. The values of the Lagrange multipliers might also change.
|
D |
Degenerate. The variable is basic, but it is equal to (or very close to) one of its bounds.
|
I |
Infeasible. The variable is basic and is currently violating one of its bounds by more than the value of the optional parameter Minor Feasibility Tolerance.
|
N |
Not precisely optimal. The variable is nonbasic. Its reduced gradient is larger than the value of the optional parameter Major 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 .
|
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. If is optimal, the multiplier should be non-negative if State is LL, non-positive if State is UL and zero if State is BS or SBS.
|
Residual |
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 general constraints is the same as that given above for variables, with ‘variable’ replaced by ‘constraint’,
replaced by
,
replaced by
,
and
are replaced by
and
respectively. The heading is changed as follows:
Constrnt |
gives the name of the general constraint.
|
Numerical values are output with a fixed number of digits; they are not guaranteed to be accurate to this precision.
8.2 Minor Iteration Printout
This section describes the printout produced by the minor iterations of E04UGF/E04UGA, which involve solving a QP subproblem at every major iteration. (Further details can be found in
Section 8.1.) The printout is a subset of the monitoring information produced by the routine at every iteration (see
Section 12). You can control the level of printed output (see the description of the optional parameter
Minor Print Level). Note that the printout is produced only if
(
, which produces no output).
The following line of summary output (
characters) is produced at every minor iteration. In all cases, the values of the quantities printed are those in effect
on completion of the given iteration of the QP subproblem.
Itn |
is the iteration count.
|
Step |
is the step taken along the computed search direction.
|
Ninf |
is the number of infeasibilities. This will not increase unless the iterations are in elastic mode. Ninf will be zero during the optimality phase.
|
Sinf |
is the value of the sum of infeasibilities if Ninf is nonzero. This will be zero during the optimality phase.
|
Objective |
is the value of the current QP objective function when Ninf is zero and the iterations are not in elastic mode. The switch to elastic mode is indicated by a change in the heading to Composite Obj.
|
Composite Obj |
is the value of the composite objective function (9) when the iterations are in elastic mode. This function will decrease monotonically at each iteration.
|
Norm rg |
is the Euclidean norm of the reduced gradient of the QP objective function. During the optimality phase, this norm will be approximately zero after a unit step.
|
Numerical values are output with a fixed number of digits; they are not guaranteed to be accurate to this precision.
9 Example
This is a reformulation of Problem 74 in
Hock and Schittkowski (1981) and involves the minimization of the nonlinear function
subject to the bounds
to the nonlinear constraints
and to the linear constraints
The initial point, which is infeasible, is
and
.
The optimal solution (to five figures) is
and
. All the nonlinear constraints are active at the solution.
The document for
E04UHF/E04UHA includes an example program to solve Problem 45 from
Hock and Schittkowski (1981) using some of the optional parameters described in
Section 11.
9.1 Program Text
Note: the following programs illustrate the use of E04UGF and E04UGA.
Program Text (e04ugfe.f90)
Program Text (e04ugae.f90)
9.2 Program Data
Program Data (e04ugfe.d)
Program Data (e04ugae.d)
9.3 Program Results
Program Results (e04ugfe.r)
Program Results (e04ugae.r)
Note: the remainder of this document is intended for more advanced users. Section 10 contains a detailed description of the algorithm which may be needed in order to understand Sections 11 and 12. Section 11 describes the optional parameters which may be set by calls to E04UHF/E04UHA and/or E04UJF/E04UJA. Section 12 describes the quantities which can be requested to monitor the course of the computation.
10 Algorithmic Details
This section contains a detailed description of the method used by E04UGF/E04UGA.
10.1 Overview
Here we briefly summarise the main features of the method and introduce some terminology. Where possible, explicit reference is made to the names of variables that are parameters of the routine or appear in the printed output. Further details can be found in
Gill et al. (2002).
At a solution of
(1), some of the constraints will be
active, i.e., satisfied exactly. Let
and
denote the set of indices of
corresponding to active constraints at an arbitrary point
. Let
denote the usual
derivative of
, which is the row vector of first partial derivatives of
(see
Ortega and Rheinboldt (1970)). The vector
comprises the
th row of
so that
where
is the Jacobian of
.
A point
is a
first-order Kuhn–Karesh–Tucker (KKT) point for
(1) (see
Powell (1974)) if the following conditions hold:
(a) |
is feasible; |
(b) |
there exists a vector (the Lagrange multiplier vector for the bound and general constraints) such that
where is the gradient of evaluated at ; |
(c) |
the Lagrange multiplier associated with the th constraint satisfies if ; if ; if ; and can have any value if . |
An equivalent statement of the condition
(4) is
where
is a matrix defined as follows. Consider the set
of vectors orthogonal to the gradients of the active constraints, i.e.,
The columns of
may then be taken as any basis for the vector space
. The vector
is termed the
reduced gradient of
at
. Certain additional conditions must be satisfied in order for a first-order KKT point to be a solution of
(1) (see
Powell (1974)).
The basic structure of E04UGF/E04UGA involves
major and
minor iterations. The major iterations generate a sequence of iterates
that satisfy the linear constraints and converge to a point
that satisfies the first-order KKT optimality conditions. At each iterate a QP subproblem is used to generate a search direction towards the next iterate (
). The constraints of the subproblem are formed from the linear constraints
and the nonlinear constraint linearization
where
denotes the
Jacobian matrix, whose rows are the first partial derivatives of
evaluated at the point
. The QP constraints therefore comprise the
linear constraints
where
and
are bounded above and below by
and
as before. If the
by
matrix
and
element vector
are defined as
then the QP subproblem can be written as
where
is a quadratic approximation to a modified Lagrangian function (see
Gill et al. (2002)).
The linear constraint matrix
is stored in the arrays
A,
HA and
KA (see
Section 5). This allows you to specify the sparsity pattern of nonzero elements in
and
and to identify any nonzero elements that remain constant throughout the minimization.
Solving the QP subproblem is itself an iterative procedure, with the
minor iterations of an SQP method being the iterations of the QP method. At each minor iteration, the constraints
are (conceptually) partitioned into the form
where the
basis matrix
is square and nonsingular. The elements of
,
and
are called the
basic,
superbasic and
nonbasic variables respectively; they are a permutation of the elements of
and
. At a QP solution, the basic and superbasic variables will lie somewhere between their bounds, while the nonbasic variables will be equal to one of their upper or lower bounds. At each minor iteration,
is regarded as a set of independent variables that are free to move in any desired direction, namely one that will improve the value of the QP objective function
or sum of infeasibilities (as appropriate). The basic variables are then adjusted in order to ensure that (
) continues to satisfy
. The number of superbasic variables (
say) therefore indicates the number of degrees of freedom remaining after the constraints have been satisfied. In broad terms,
is a measure of
how nonlinear the problem is. In particular,
will always be zero if there are no nonlinear constraints in
(1) and
is linear.
If it appears that no improvement can be made with the current definition of , and , a nonbasic variable is selected to be added to and the process is repeated with the value of increased by one. At all stages, if a basic or superbasic variable encounters one of its bounds, the variable is made nonbasic and the value of decreased by one.
Associated with each of the
equality constraints
is a
dual variable
. Similarly, each variable in
has an associated
reduced gradient
(also known as a
reduced cost). The reduced gradients for the variables
are the quantities
, where
is the gradient of the QP objective function
; the reduced gradients for the slack variables
are the dual variables
. The QP subproblem
(5) is optimal if
for all nonbasic variables at their lower bounds,
for all nonbasic variables at their upper bounds and
for other variables (including superbasics). In practice, an
approximate QP solution is found by slightly relaxing these conditions on
(see the description of the optional parameter
Minor Optimality Tolerance).
After a QP subproblem has been solved, new estimates of the solution to
(1) are computed using a linesearch on the augmented Lagrangian merit function
where
is a diagonal matrix of penalty parameters. If (
) denotes the current estimate of the solution and (
) denotes the optimal QP solution, the linesearch determines a step
(where
) such that the new point
produces a
sufficient decrease in the merit function
(6). When necessary, the penalties in
are increased by the minimum-norm perturbation that ensures descent for
(see
Gill et al. (1992)). As in
E04WDF,
is adjusted to minimize the merit function as a function of
before the solution of the QP subproblem. Further details can be found in
Eldersveld (1991) and
Gill et al. (1986).
10.2 Treatment of Constraint Infeasibilities
E04UGF/E04UGA makes explicit allowance for infeasible constraints. Infeasible linear constraints are detected first by solving a problem of the form
where
. This is equivalent to minimizing the sum of the general linear constraint violations subject to the simple bounds. (In the linear programming literature, the approach is often called
elastic programming.)
If the linear constraints are infeasible (i.e., or ), the routine terminates without computing the nonlinear functions.
If the linear constraints are feasible, all subsequent iterates will satisfy the linear constraints. (Such a strategy allows linear constraints to be used to define a region in which
and
can be safely evaluated.) The routine then proceeds to solve
(1) as given, using search directions obtained from a sequence of QP subproblems
(5). Each QP subproblem minimizes a quadratic model of a certain Lagrangian function subject to linearized constraints. An augmented Lagrangian merit function
(6) is reduced along each search direction to ensure convergence from any starting point.
The routine enters ‘elastic’ mode if the QP subproblem proves to be infeasible or unbounded (or if the dual variables
for the nonlinear constraints become ‘large’) by solving a problem of the form
where
is called a
composite objective and
is a non-negative parameter (the
elastic weight). If
is sufficiently large, this is equivalent to minimizing the sum of the nonlinear constraint violations subject to the linear constraints and bounds. A similar
formulation of
(1) is fundamental to the
QP algorithm of
Fletcher (1984). See also
Conn (1973).
11 Optional Parameters
Several optional parameters in E04UGF/E04UGA define choices in the problem specification or the algorithm logic. In order to reduce the number of formal parameters of E04UGF/E04UGA 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.
The remainder of this section can be skipped if you wish to use the default values for all optional parameters.
The following is a list of the optional parameters available. A full description of each optional parameter is provided in
Section 11.1.
Optional parameters may be specified by calling
one, or both, of the routines
E04UHF/E04UHA and
E04UJF/E04UJA before a call to E04UGF/E04UGA.
E04UHF/E04UHA reads options from an external options file, with
Begin and
End as the first and last lines respectively and each intermediate line defining a single optional parameter. For example,
Begin
Print Level = 5
End
The call
CALL E04UHF (IOPTNS, INFORM)
can then be used to read the file on unit
IOPTNS.
INFORM will be zero on successful exit.
E04UHF/E04UHA should be consulted for a full description of this method of supplying optional parameters.
E04UJF/E04UJA can be called to supply options directly, one call being necessary for each optional parameter. For example,
CALL E04UJF ('Print Level = 5')
E04UJF/E04UJA should be consulted for a full description of this method of supplying optional parameters.
All optional parameters not specified by you are set to their default values. Optional parameters specified by you are unaltered by E04UGF/E04UGA (unless they define invalid values) and so remain in effect for subsequent calls to E04UGF/E04UGA from the calling program (unless altered by you).
11.1 Description of the Optional Parameters
For each option, we give a summary line, a description of the optional parameter and details of constraints.
The summary line contains:
- the keywords, where the minimum abbreviation of each keyword is underlined (if no characters of an optional qualifier are underlined, the qualifier may be omitted);
- a parameter value,
where the letters , denote options that take character, integer and real values respectively;
- the default value is used whenever the condition is satisfied and where the symbol is a generic notation for machine precision (see X02AJF).
Keywords and character values are case and white space insensitive.
Central Difference Interval | | Default |
Note that this option does not apply when .
The value of
is used near an optimal solution in order to obtain more accurate (but more expensive) estimates of gradients. This requires twice as many function evaluations as compared to using forward differences (see optional parameter
Forward Difference Interval). The interval used for the
th variable is
. The resulting gradient estimates should be accurate to
, unless the functions are badly scaled. The switch to central differences is indicated by
c at the end of each line of intermediate printout produced by the major iterations (see
Section 8.1). See
Gill et al. (1981) for a discussion of the accuracy in finite difference approximations.
If , the default value is used.
Check Frequency | | Default |
Every th minor iteration after the most recent basis factorization, a numerical test is made to see if the current solution satisfies the general linear constraints (including any linearized nonlinear constraints). The constraints are of the form , where is the set of slack variables. If the largest element of the residual vector is judged to be too large, the current basis is refactorized and the basic variables recomputed to satisfy the general constraints more accurately.
If , the default value is used. If , the value is used and effectively no checks are made.
Crash Option | | Default |
The default value of
is
if there are any nonlinear constraints and
otherwise. Note that this option does not apply when
(see
Section 5).
If
, an internal Crash procedure is used to select an initial basis from various rows and columns of the constraint matrix
. The value of
determines which rows and columns of
are initially eligible for the basis and how many times the Crash procedure is called. Columns of
are used to pad the basis where necessary. The possible choices for
are the following.
|
Meaning |
0 |
The initial basis contains only slack variables: . |
1 |
The Crash procedure is called once (looking for a triangular basis in all rows and columns of ). |
2 |
The Crash procedure is called twice (if there are any nonlinear constraints). The first call looks for a triangular basis in linear rows and the iteration proceeds with simplex iterations until the linear constraints are satisfied. The Jacobian is then evaluated for the first major iteration and the Crash procedure is called again to find a triangular basis in the nonlinear rows (whilst retaining the current basis for linear rows). |
3 |
The Crash procedure is called up to three times (if there are any nonlinear constraints). The first two calls treat linear equality constraints and linear inequality constraints separately. The Jacobian is then evaluated for the first major iteration and the Crash procedure is called again to find a triangular basis in the nonlinear rows (whilst retaining the current basis for linear rows). |
If or , the default value is used.
If , certain slacks on inequality rows are selected for the basis first. (If , numerical values are used to exclude slacks that are close to a bound.) The Crash procedure then makes several passes through the columns of , searching for a basis matrix that is essentially triangular. A column is assigned to ‘pivot’ on a particular row if the column contains a suitably large element in a row that has not yet been assigned. (The pivot elements ultimately form the diagonals of the triangular basis.) For remaining unassigned rows, slack variables are inserted to complete the basis.
Crash Tolerance | | Default |
The value () allows the Crash procedure to ignore certain ‘small’ nonzero elements in the columns of while searching for a triangular basis. If is the largest element in the th column, other nonzeros in the column are ignored if .
When , the basis obtained by the Crash procedure may not be strictly triangular, but it is likely to be nonsingular and almost triangular. The intention is to obtain a starting basis containing more columns of and fewer (arbitrary) slacks. A feasible solution may be reached earlier on some problems.
If or , the default value is used.
This special keyword may be used to reset all optional parameters to their default values.
Derivative Level | | Default |
This parameter indicates which nonlinear function gradients are provided in user-supplied subroutines
OBJFUN and
CONFUN. The possible choices for
are the following.
|
Meaning |
3 |
All elements of the objective gradient and the constraint Jacobian are provided. |
2 |
All elements of the constraint Jacobian are provided, but some (or all) elements of the objective gradient are not specified. |
1 |
All elements of the objective gradient are provided, but some (or all) elements of the constraint Jacobian are not specified. |
0 |
Some (or all) elements of both the objective gradient and the constraint Jacobian are not specified. |
The default value should be used whenever possible. It is the most reliable and will usually be the most efficient.
If
, E04UGF/E04UGA will
estimate the unspecified elements of the objective gradient, using finite differences. This may simplify the coding of
OBJFUN. However, the computation of finite difference approximations usually increases the total run-time substantially (since a call to
OBJFUN is required for each unspecified element) and there is less assurance that an acceptable solution will be found.
If
, E04UGF/E04UGA will approximate unspecified elements of the constraint Jacobian. For each column of the Jacobian, one call to
CONFUN is needed to estimate all unspecified elements in that column (if any). For example, if the sparsity pattern of the Jacobian has the form
where ‘
’ indicates an element provided and ‘?’ indicates an unspecified element, E04UGF/E04UGA will call
CONFUN twice: once to estimate the missing element in column
and again to estimate the two missing elements in column
. (Since columns
and
are known, they require no calls to
CONFUN.)
At times, central differences are used rather than forward differences, in which case twice as many calls to
OBJFUN and
CONFUN are needed. (The switch to central differences is not under your control.)
If or , the default value is used.
Derivative Linesearch | | Default |
At each major iteration, a linesearch is used to improve the value of the Lagrangian merit function
(6). The default linesearch uses safeguarded cubic interpolation and requires both function and gradient values in order to compute estimates of the step
. If some analytic derivatives are not provided or optional parameter
Nonderivative Linesearch is specified, a linesearch based upon safeguarded quadratic interpolation (which does not require the evaluation or approximation of any gradients) is used instead.
A nonderivative linesearch can be slightly less robust on difficult problems and it is recommended that the default be used if the functions and their derivatives can be computed at approximately the same cost. If the gradients are very expensive to compute relative to the functions however, a nonderivative linesearch may result in a significant decrease in the total run-time.
If optional parameter
Nonderivative Linesearch is selected, E04UGF/E04UGA signals the evaluation of the linesearch by calling
OBJFUN and
CONFUN with
. Once the linesearch is complete, the nonlinear functions are re-evaluated with
. If the potential savings offered by a nonderivative linesearch are to be fully realised, it is essential that
OBJFUN and
CONFUN be coded so that no derivatives are computed when
.
Elastic Weight | | Default or |
The default value of is if there are any nonlinear constraints and otherwise.
This option defines the initial weight
associated with problem
(8).
At any given major iteration , elastic mode is entered if the QP subproblem is infeasible or the QP dual variables (Lagrange multipliers) are larger in magnitude than , where is the objective gradient. In either case, the QP subproblem is resolved in elastic mode with .
Thereafter,
is increased (subject to a maximum allowable value) at any point that is optimal for problem
(8), but not feasible for problem
(1). After the
th increase,
, where
is the iterate at which
was first needed.
If , the default value is used.
Expand Frequency | | Default |
This option is part of the EXPAND anti-cycling procedure due to
Gill et al. (1989), which is designed to make progress even on highly degenerate problems.
For linear models, the strategy is to force a positive step at every iteration, at the expense of violating the constraints by a small amount. Suppose that the value of optional parameter
Minor Feasibility Tolerance is
. Over a period of
iterations, the feasibility tolerance actually used by E04UGF/E04UGA (i.e., the
working feasibility tolerance) increases from
to
(in steps of
).
For nonlinear models, the same procedure is used for iterations in which there is only one superbasic variable. (Cycling can only occur when the current solution is at a vertex of the feasible region.) Thus, zero steps are allowed if there is more than one superbasic variable, but otherwise positive steps are enforced.
Increasing the value of
helps reduce the number of slightly infeasible nonbasic basic variables (most of which are eliminated during the resetting procedure). However, it also diminishes the freedom to choose a large pivot element (see optional parameter
Pivot Tolerance).
If , the default value is used. If , the value is used and effectively no anti-cycling procedure is invoked.
Factorization Frequency | | Default |
The default value of is if there are any nonlinear constraints and otherwise.
If , at most basis changes will occur between factorizations of the basis matrix.
For linear problems, the basis factors are usually updated at every iteration. The default value is reasonable for typical problems, particularly those that are extremely sparse and well-scaled.
When the objective function is nonlinear, fewer basis updates will occur as the solution is approached. The number of iterations between basis factorizations will therefore increase. During these iterations a test is made regularly according to the value of optional parameter
Check Frequency to ensure that the general constraints are satisfied. If necessary, the basis will be refactorized before the limit of
updates is reached.
If , the default value is used.
Note that this option is ignored if the value of optional parameter
Major Iteration Limit is exceeded, or the linear constraints are infeasible.
If termination is about to occur at a point that does not satisfy the nonlinear constraints and optional parameter
Feasible Exit is selected, this option requests that additional iterations be performed in order to find a feasible point (if any) for the nonlinear constraints. This involves solving a feasible point problem in which the objective function is omitted.
Otherwise, this option requests no additional iterations be performed.
If optional parameter
Feasible Point is selected, this option attempts to find a feasible point (if any) for the nonlinear constraints by omitting the objective function. It can also be used to check whether the nonlinear constraints are feasible.
Otherwise, this option specifies the required direction of the optimization. It applies to both linear and nonlinear terms (if any) in the objective function. Note that if two problems are the same except that one minimizes and the other maximizes , their solutions will be the same but the signs of the dual variables and the reduced gradients will be reversed.
Forward Difference Interval | | Default |
This option defines an interval used to estimate derivatives by forward differences in the following circumstances:
(a) |
For verifying the objective and/or constraint gradients (see the description of the optional parameter Verify Level). |
(b) |
For estimating unspecified elements of the objective gradient and/or the constraint Jacobian. |
A derivative with respect to
is estimated by perturbing that element of
to the value
and then evaluating
and/or
(as appropriate) at the perturbed point. The resulting gradient estimates should be accurate to
, unless the functions are badly scaled. Judicious alteration of
may sometimes lead to greater accuracy. See
Gill et al. (1981) for a discussion of the accuracy in finite difference approximations.
If , the default value is used.
Function Precision | | Default |
This parameter defines the relative function precision , which is intended to be a measure of the relative accuracy with which the nonlinear functions can be computed. For example, if (or ) is computed as for some relevant and the first significant digits are known to be correct then the appropriate value for would be .
Ideally the functions or should have magnitude of order . If all functions are substantially less than in magnitude, should be the absolute precision. For example, if (or ) is computed as for some relevant and the first significant digits are known to be correct then the appropriate value for would be .
The choice of
can be quite complicated for badly scaled problems; see Chapter 8 of
Gill et al. (1981) for a discussion of scaling techniques. The default value is appropriate for most simple functions that are computed with full accuracy.
In some cases the function values will be the result of extensive computation, possibly involving an iterative procedure that can provide few digits of precision at reasonable cost. Specifying an appropriate value of may therefore lead to savings, by allowing the linesearch procedure to terminate when the difference between function values along the search direction becomes as small as the absolute error in the values.
If or , the default value is used.
Hessian Frequency | | Default |
This option forces the approximate Hessian formed from
BFGS updates to be reset to the identity matrix upon completion of a major iteration. It is intended to be used in conjunction with optional parameter
Hessian Full Memory.
If , the default value is used and effectively no resets occur.
Hessian Full Memory | | Default when |
Hessian Limited Memory | | Default when |
These options specify the method for storing and updating the quasi-Newton approximation to the Hessian of the Lagrangian function.
If
Hessian Full Memory is specified, the approximate Hessian is treated as a dense matrix and BFGS quasi-Newton updates are applied explicitly. This is most efficient when the total number of nonlinear variables is not too large (say,
). In this case, the storage requirement is fixed and you can expect
-step Q-superlinear convergence to the solution.
Hessian Limited Memory should only be specified when
is very large. In this case a limited memory procedure is used to update a diagonal Hessian approximation
a limited number of times. (Updates are accumulated as a list of vector pairs. They are discarded at regular intervals after
has been reset to their diagonal.)
Note that if
is used in conjunction with
Hessian Full Memory, the effect will be similar to using
Hessian Limited Memory in conjunction with
, except that the latter will retain the current diagonal during resets.
Hessian Updates | | Default |
The default value of
is
when
Hessian Limited Memory is in effect and
when
Hessian Full Memory is in effect, in which case no updates are performed.
If
Hessian Limited Memory is in effect, this option defines the maximum number of pairs of Hessian update vectors that are to be used to define the quasi-Newton approximate Hessian. Once the limit of
updates is reached, all but the diagonal elements of the accumulated updates are discarded and the process starts again. Broadly speaking, the more updates that are stored, the better the quality of the approximate Hessian. On the other hand, the more vectors that are stored, the greater the cost of each QP iteration.
The default value of is likely to give a robust algorithm without significant expense, but faster convergence may be obtained with far fewer updates (e.g., ).
If , the default value is used.
Infinite Bound Size | | Default |
If , defines the ‘infinite’ bound in the definition of the problem constraints. Any upper bound greater than or equal to will be regarded as (and similarly any lower bound less than or equal to will be regarded as ).
If , the default value is used.
Iteration Limit | | Default |
The value of
specifies the maximum number of minor iterations allowed (i.e., iterations of the simplex method or the QP algorithm), summed over all major iterations. (See also the description of the optional parameters
Major Iteration Limit and
Minor Iteration Limit.)
If , the default value is used.
Linesearch Tolerance | | Default |
This option controls the accuracy with which a step length will be located along the direction of search at each iteration. At the start of each linesearch a target directional derivative for the Lagrangian merit function is identified. The value of therefore determines the accuracy to which this target value is approximated.
The default value requests an inaccurate search and is appropriate for most problems, particularly those with any nonlinear constraints.
If the nonlinear functions are cheap to evaluate, a more accurate search may be appropriate; try . The number of major iterations required to solve the problem might decrease.
If the nonlinear functions are expensive to evaluate, a less accurate search may be appropriate. If , try . (The number of major iterations required to solve the problem might increase, but the total number of function evaluations may decrease enough to compensate.)
If , a moderately accurate search may be appropriate; try . Each search will (typically) require only function values, but many function calls will then be needed to estimate the missing gradients for the next iteration.
If or , the default value is used.
List | | Default for |
Nolist | | Default for |
Normally each optional parameter specification is printed as it is supplied. Optional parameter
Nolist may be used to suppress the printing and optional parameter
List may be used to restore printing.
LU Density Tolerance | | Default |
LU Singularity Tolerance | | Default |
If , defines the density tolerance used during the factorization of the basis matrix. Columns of and rows of are formed one at a time and the remaining rows and columns of the basis are altered appropriately. At any stage, if the density of the remaining matrix exceeds , the Markowitz strategy for choosing pivots is terminated. The remaining matrix is then factorized using a dense procedure. Increasing the value of towards unity may give slightly sparser factors, with a slight increase in factorization time. If , the default value is used.
If
,
defines the singularity tolerance used to guard against ill-conditioned basis matrices. Whenever the basis is refactorized, the diagonal elements of
are tested as follows. If
or
, the
th column of the basis is replaced by the corresponding slack variable. This is most likely to occur when
(see
Section 5), or at the start of a major iteration. If
, the default value is used.
In some cases, the Jacobian matrix may converge to values that make the basis exactly singular (e.g., a whole row of the Jacobian matrix could be zero at an optimal solution). Before exact singularity occurs, the basis could become very ill-conditioned and the optimization could progress very slowly (if at all). Setting (say) may therefore help cause a judicious change of basis in such situations.
LU Factor Tolerance | | Default or |
LU Update Tolerance | | Default or |
The default value of is if there are any nonlinear constraints and otherwise. The default value of is if there are any nonlinear constraints and otherwise.
If
and
, the values of
and
affect the stability and sparsity of the basis factorization
, during refactorization and updating, respectively. The lower triangular matrix
is a product of matrices of the form
where the multipliers
satisfy
. Smaller values of
favour stability, while larger values favour sparsity. The default values of
and
usually strike a good compromise. For large and relatively dense problems, setting
(say) may give a marked improvement in sparsity without impairing stability to a serious degree. Note that for problems involving band matrices, it may be necessary to reduce
and/or
in order to achieve stability.
If or , the appropriate default value is used.
Major Feasibility Tolerance | | Default |
This option specifies how accurately the nonlinear constraints should be satisfied. The default value is appropriate when the linear and nonlinear constraints contain data to approximately that accuracy. A larger value may be appropriate if some of the problem functions are known to be of low accuracy.
Let
rowerr be defined as the maximum nonlinear constraint violation normalized by the size of the solution. It is required to satisfy
where
is the violation of the
th nonlinear constraint.
If , the default value is used.
Major Iteration Limit | | Default |
The value of specifies the maximum number of major iterations allowed before termination. It is intended to guard against an excessive number of linearizations of the nonlinear constraints. Setting and means that the objective and constraint gradients will be checked if and the workspace needed to start solving the problem will be computed and printed, but no iterations will be performed.
If , the default value is used.
Major Optimality Tolerance | | Default |
This option specifies the final accuracy of the dual variables. If E04UGF/E04UGA terminates with
, a primal and dual solution (
) will have been computed such that
where
is an estimate of the complementarity gap for the
th variable and
is a measure of the size of the QP dual variables (or Lagrange multipliers) given by
It is included to make the tests independent of a scale factor on the objective function. Specifically,
is computed from the final QP solution using the reduced gradients
, where
is the
th element of the objective gradient and
is the associated column of the constraint matrix
:
If , the default value is used.
Major Print Level | | Default for E04UGF
Default for E04UGA
|
The value of
controls the amount of printout produced by the major iterations of E04UGF/E04UGA, as indicated below. A detailed description of the printed output is given in
Section 8.1 (summary output at each major iteration and the final solution) and
Section 12 (monitoring information at each major iteration). (See also the description of
Minor Print Level.)
The following printout is sent to the current advisory message unit (as defined by
X04ABF):
|
Output |
|
No output. |
|
The final solution only. |
|
One line of summary output ( characters; see Section 8.1) for each major iteration (no printout of the final solution). |
|
The final solution and one line of summary output for each major iteration. |
The following printout is sent to the logical unit number defined by the optional parameter
Monitoring File:
|
Output |
|
No output. |
|
The final solution only. |
|
One long line of output ( characters; see Section 12) for each major iteration (no printout of the final solution). |
|
The final solution and one long line of output for each major iteration. |
|
The final solution, one long line of output for each major iteration, matrix statistics (initial status of rows and columns, number of elements, density, biggest and smallest elements, etc.), details of the scale factors resulting from the scaling procedure (if or ), basis factorization statistics and details of the initial basis resulting from the Crash procedure (if ; see Section 5). |
If
and the unit number defined by the optional parameter
Monitoring File is the same as that defined by
X04ABF then the summary output for each major iteration is suppressed.
Major Step Limit | | Default |
If limits the change in during a linesearch. It applies to all nonlinear problems once a ‘feasible solution’ or ‘feasible subproblem’ has been found.
A linesearch determines a step in the interval , where if there are any nonlinear constraints, or the step to the nearest upper or lower bound on if all the constraints are linear. Normally, the first step attempted is .
In some cases, such as
or
, even a moderate change in the elements of
can lead to floating point overflow. The parameter
is therefore used to define a step limit
given by
where
is the search direction and the first evaluation of
is made at the (potentially) smaller step length
.
Wherever possible, upper and lower bounds on should be used to prevent evaluation of nonlinear functions at meaningless points. The default value should not affect progress on well-behaved functions, but values such as may be helpful when rapidly varying functions are present. If a small value of is selected, a ‘good’ starting point may be required. An important application is to the class of nonlinear least squares problems.
If , the default value is used.
Minor Feasibility Tolerance | | Default |
This option attempts to ensure that all variables eventually satisfy their upper and lower bounds to within the tolerance
. Since this includes slack variables, general linear constraints should also be satisfied to within
. Note that feasibility with respect to nonlinear constraints is judged by the value of optional parameter
Major Feasibility Tolerance and not by
.
If the bounds and linear constraints cannot be satisfied to within , the problem is declared infeasible. Let Sinf be the corresponding sum of infeasibilities. If Sinf is quite small, it may be appropriate to raise by a factor of or . Otherwise, some error in the data should be suspected.
If , feasibility is defined in terms of the scaled problem (since it is more likely to be meaningful).
Nonlinear functions will only be evaluated at points that satisfy the bounds and linear constraints. If there are regions where a function is undefined, every effort should be made to eliminate these regions from the problem. For example, if , it is essential to place lower bounds on both and . If the value is used, the bounds and might be appropriate. (The log singularity is more serious; in general, you should attempt to keep as far away from singularities as possible.)
In reality,
is used as a feasibility tolerance for satisfying the bounds on
and
in each QP subproblem. If the sum of infeasibilities cannot be reduced to zero, the QP subproblem is declared infeasible and the routine is then in
elastic mode thereafter (with only the linearized nonlinear constraints defined to be elastic). (See also the description of
Elastic Weight.)
If , the default value is used.
Minor Iteration Limit | | Default |
The value of
specifies the maximum number of iterations allowed between successive linearizations of the nonlinear constraints. A value in the range
prevents excessive effort being expended on early major iterations, but allows later QP subproblems to be solved to completion. Note that an extra
minor iterations are allowed if the first QP subproblem to be solved starts with the all-slack basis
. (See the description of the optional parameter
Crash Option.)
In general, it is unsafe to specify values as small as (because even when an optimal solution has been reached, a few minor iterations may be needed for the corresponding QP subproblem to be recognized as optimal).
If , the default value is used.
Minor Optimality Tolerance | | Default |
This option is used to judge optimality for each QP subproblem. Let the QP reduced gradients be , where is the th element of the QP gradient, is the associated column of the QP constraint matrix and is the set of QP dual variables.
By construction, the reduced gradients for basic variables are always zero. The QP subproblem will be declared optimal if the reduced gradients for nonbasic variables at their upper or lower bounds satisfy
respectively, and if
for superbasic variables.
Note that
is a measure of the size of the dual variables. It is included to make the tests independent of a scale factor on the objective function. (The value of
actually used is defined in the description for optional parameter
Major Optimality Tolerance.)
If the objective is scaled down to be very small, the optimality test reduces to comparing against .
If , the default value is used.
Minor Print Level | | Default |
The value of
controls the amount of printout produced by the minor iterations of E04UGF/E04UGA (i.e., the iterations of the quadratic programming algorithm), as indicated below. A detailed description of the printed output is given in
Section 8.2 (summary output at each minor iteration) and
Section 12 (monitoring information at each minor iteration). (See also the description of the optional parameter
Major Print Level.)
The following printout is sent to the current advisory message unit (as defined by
X04ABF):
|
Output |
|
No output. |
|
One line of summary output ( characters; see Section 8.2) for each minor iteration. |
The following printout is sent to the logical unit number defined by the optional parameter
Monitoring File:
|
Output |
|
No output. |
|
One long line of output ( characters; see Section 12) for each minor iteration. |
If
and the unit number defined by the optional parameter
Monitoring File is the same as that defined by
X04ABF then the summary output for each minor iteration is suppressed.
Monitoring File | | Default |
If and or and then monitoring information is produced by E04UGF/E04UGA at every iteration is sent to a file with logical unit number . If and/or and then no monitoring information is produced.
Partial Price | | Default |
The default value of is if there are any nonlinear constraints and otherwise.
This option is recommended for large problems that have significantly more variables than constraints (i.e.,
). It reduces the work required for each ‘pricing’ operation (i.e., when a nonbasic variable is selected to become superbasic). The possible choices for
are the following.
|
Meaning |
|
All columns of the constraint matrix are searched. |
|
Both and are partitioned to give roughly equal segments , for (modulo ). If the previous pricing search was successful on , the next search begins on the segments . If a reduced gradient is found that is larger than some dynamic tolerance, the variable with the largest such reduced gradient (of appropriate sign) is selected to enter the basis. If nothing is found, the search continues on the next segments and so on. |
If , the default value is used.
Pivot Tolerance | | Default |
If , is used during the solution of QP subproblems to prevent columns entering the basis if they would cause the basis to become almost singular.
When changes to for some specified search direction , a ‘ratio test’ is used to determine which element of reaches an upper or lower bound first. The corresponding element of is called the pivot element. Elements of are ignored (and therefore cannot be pivot elements) if they are smaller than .
It is common in practice for two (or more) variables to reach a bound at essentially the same time. In such cases, the
Minor Feasibility Tolerance provides some freedom to maximize the pivot element and thereby improve numerical stability. Excessively
small values of
Minor Feasibility Tolerance should therefore not be specified. To a lesser extent, the
Expand Frequency also provides some freedom to maximize the pivot element. Excessively
large values of
Expand Frequency should therefore not be specified.
If , the default value is used.
Scale Option | | Default |
The default value of is if there are any nonlinear constraints and otherwise.
This option enables you to scale the variables and constraints using an iterative procedure due to
Fourer (1982), which attempts to compute row scales
and column scales
such that the scaled matrix coefficients
are as close as possible to unity. (The lower and upper bounds on the variables and slacks for the scaled problem are redefined as
and
respectively, where
if
.) The possible choices for
are the following.
|
Meaning |
0 |
No scaling is performed. This is recommended if it is known that the elements of and the constraint matrix (along with its Jacobian) never become large (say, ). |
1 |
All linear constraints and variables are scaled. This may improve the overall efficiency of the routine on some problems. |
2 |
All constraints and variables are scaled. Also, an additional scaling is performed that takes into account columns of that are fixed or have positive lower bounds or negative upper bounds. |
If there are any nonlinear constraints present, the scale factors depend on the Jacobian at the first point that satisfies the linear constraints and the upper and lower bounds. The setting should therefore be used only if a ‘good’ starting point is available and the problem is not highly nonlinear.
If or , the default value is used.
Scale Tolerance | | Default |
Note that this option does not apply when .
The value () is used to control the number of scaling passes to be made through the constraint matrix . At least (and at most ) passes will be made. More precisely, let denote the largest column ratio (i.e., in some sense) after the th scaling pass through . The scaling procedure is terminated if for some . Thus, increasing the value of from to (say) will probably increase the number of passes through .
If or , the default value is used.
Start Objective Check At Column | | Default |
Stop Objective Check At Column | | Default |
Start Constraint Check At Column | | Default |
Stop Constraint Check At Column | | Default |
These keywords take effect only if
. They may be used to control the verification of gradient elements computed by
OBJFUN and/or Jacobian elements computed by
CONFUN. For example, if the first
elements of the objective gradient appeared to be correct in an earlier run, so that only element
remains questionable then it is reasonable to specify
. Similarly for columns of the Jacobian. If the first
variables occur nonlinearly in the constraints but the remaining variables are nonlinear only in the objective, then
OBJFUN must set the first
elements of the array
OBJGRD to zero, but these hardly need to be verified. Again it is reasonable to specify
.
If or , the default value is used.
If or , the default value is used.
If or , the default value is used.
If or , the default value is used.
Superbasics Limit | | Default |
Note that this option does not apply to linear problems.
It places a limit on the storage allocated for superbasic variables. Ideally, the value of should be set slightly larger than the ‘number of degrees of freedom’ expected at the solution.
For nonlinear problems, the number of degrees of freedom is often called the ‘number of independent variables’. Normally, the value of need not be greater than , but for many problems it may be considerably smaller. (This will save storage if is very large.)
If , the default value is used.
Unbounded Objective | | Default |
Unbounded Step Size | | Default |
These options are intended to detect unboundedness in nonlinear problems. During the linesearch, the objective function is evaluated at points of the form , where and are fixed and varies. If exceeds or exceeds , the iterations are terminated and the routine returns with .
If singularities are present, unboundedness in may manifest itself by a floating point overflow during the evaluation of , before the test against can be made.
Unboundedness in is best avoided by placing finite upper and lower bounds on the variables.
If or , the appropriate default value is used.
This option refers to finite difference checks on the gradient elements computed by
OBJFUN and
CONFUN. Gradients are verified at the first point that satisfies the linear constraints and the upper and lower bounds. Unspecified gradient elements are not checked and hence they result in no overhead. The possible choices for
are the following.
|
Meaning |
|
No checks are performed. |
|
Only a ‘cheap’ test will be performed, requiring three calls to OBJFUN and two calls to CONFUN. Note that no checks are carried out if every column of the constraint gradients (Jacobian) contains a missing element. |
|
Individual objective gradient elements will be checked using a reliable (but more expensive) test. If , a key of the form OK or BAD? indicates whether or not each element appears to be correct. |
|
Individual columns of the constraint gradients (Jacobian) will be checked using a reliable (but more expensive) test. If , a key of the form OK or BAD? indicates whether or not each element appears to be correct. |
|
Check both constraint and objective gradients (in that order) as described above for and respectively. |
The value
should be used whenever a new function routine is being developed. The
Start Objective Check At Column and
Stop Objective Check At Column keywords may be used to limit the number of nonlinear variables to be checked.
If or , the default value is used.
Violation Limit | | Default |
This option defines an absolute limit on the magnitude of the maximum constraint violation after the linesearch. Upon completion of the linesearch, the new iterate
satisfies the condition
where
is the point at which the nonlinear constraints are first evaluated and
is the
th nonlinear constraint violation
.
The effect of the violation limit is to restrict the iterates to lie in an expanded feasible region whose size depends on the magnitude of . This makes it possible to keep the iterates within a region where the objective function is expected to be well-defined and bounded below (or above in the case of maximization). If the objective function is bounded below (or above in the case of maximization) for all values of the variables, then may be any large positive value.
If , the default value is used.
12 Description of Monitoring Information
This section describes the intermediate printout and final printout which constitutes the monitoring information produced by E04UGF/E04UGA. (See also the description of the optional parameters
Monitoring File,
Major Print Level and
Minor Print Level.) You can control the level of printed output.
When
and
, the following line of intermediate printout (
characters) is produced at every major iteration on the unit number specified by optional parameter
Monitoring File. Unless stated otherwise, the values of the quantities printed are those in effect
on completion of the given iteration.
Major |
is the major iteration count.
|
Minor |
is the number of minor iterations required by the feasibility and optimality phases of the QP subproblem. Generally, Minor will be in the later iterations, since theoretical analysis predicts that the correct active set will be identified near the solution (see Section 10).
|
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.
|
nObj |
is the number of times OBJFUN has been called to evaluate the nonlinear part of the objective function. Evaluations needed for the estimation of the gradients by finite differences are not included. nObj is printed as a guide to the amount of work required for the linesearch.
|
nCon |
is the number of times CONFUN has been called to evaluate the nonlinear constraint functions (not printed if NCNLN is zero).
|
Merit |
is the value of the augmented Lagrangian merit function (6) at the current iterate. This function will decrease at each iteration unless it was necessary to increase the penalty parameters (see Section 8.1). As the solution is approached, Merit will converge to the value of the objective function at the solution.In elastic mode (see Section 10.2), the merit function is a composite function involving the constraint violations weighted by the value of the optional parameter Elastic Weight. If there are no nonlinear constraints present, this entry contains Objective, the value of the objective function . In this case, will decrease monotonically to its optimal value.
|
Feasibl |
is the value of rowerr, the largest element of the scaled nonlinear constraint residual vector defined in the description of the optional parameter Major Feasibility Tolerance. The solution is regarded as ‘feasible’ if Feasibl is less than (or equal to) the optional parameter Major Feasibility Tolerance. Feasibl will be approximately zero in the neighbourhood of a solution. If there are no nonlinear constraints present, all iterates are feasible and this entry is not printed.
|
Optimal |
is the value of maxgap, the largest element of the maximum complementarity gap vector defined in the description of the optional parameter Major Optimality Tolerance. The Lagrange multipliers are regarded as ‘optimal’ if Optimal is less than (or equal to) the optional parameter Major Optimality Tolerance. Optimal will be approximately zero in the neighbourhood of a solution.
|
nS |
is the current number of superbasic variables.
|
Penalty |
is the Euclidean norm of the vector of penalty parameters used in the augmented Lagrangian merit function (not printed if NCNLN is zero).
|
LU |
is the number of nonzeros representing the basis factors and on completion of the QP subproblem. If there are nonlinear constraints present, the basis factorization is computed at the start of the first minor iteration. At this stage, , where lenL is the number of subdiagonal elements in the columns of a lower triangular matrix and lenU is the number of diagonal and superdiagonal elements in the rows of an upper triangular matrix. As columns of are replaced during the minor iterations, the value of LU may fluctuate up or down (but in general will tend to increase). As the solution is approached and the number of minor iterations required to solve each QP subproblem decreases towards zero, LU will reflect the number of nonzeros in the factors at the start of each QP subproblem. If there are no nonlinear constraints present, refactorization is subject only to the value of the optional parameter Factorization Frequency and hence LU will tend to increase between factorizations.
|
Swp |
is the number of columns of the basis matrix that were swapped with columns of in order to improve the condition number of (not printed if NCNLN is zero). The swaps are determined by an factorization of the rectangular matrix , with stability being favoured more than sparsity.
|
Cond Hz |
is an estimate of the condition number of the reduced Hessian of the Lagrangian (not printed if NCNLN and NONLN are both zero). It is the square of the ratio between the largest and smallest diagonal elements of the upper triangular matrix . This constitutes a lower bound on the condition number of the matrix that approximates the reduced Hessian. The larger this number, the more difficult the problem.
|
PD |
is a two-letter indication of the status of the convergence tests involving the feasibility and optimality of the iterates defined in the descriptions of the optional parameters Major Feasibility Tolerance and Major Optimality Tolerance. Each letter is T if the test is satisfied and F otherwise. The tests indicate whether the values of Feasibl and Optimal are sufficiently small. For example, TF or TT is printed if there are no nonlinear constraints present (since all iterates are feasible). If either indicator is F when E04UGF/E04UGA terminates with , you should check the solution carefully.
|
M |
is printed if an extra evaluation of user-supplied subroutines OBJFUN and CONFUN was needed in order to define an acceptable positive definite quasi-Newton update to the Hessian of the Lagrangian. This modification is only performed when there are nonlinear constraints present.
|
m |
is printed if, in addition, it was also necessary to modify the update to include an augmented Lagrangian term.
|
s |
is printed if a self-scaled BFGS (Broyden–Fletcher–Goldfarb–Shanno) update was performed. This update is always used when the Hessian approximation is diagonal and hence always follows a Hessian reset.
|
S |
is printed if, in addition, it was also necessary to modify the self-scaled update in order to maintain positive-definiteness.
|
n |
is printed if no positive definite BFGS update could be found, in which case the approximate Hessian is unchanged from the previous iteration.
|
r |
is printed if the approximate Hessian was reset after consecutive major iterations in which no BFGS update could be made. The diagonal elements of the approximate Hessian are retained if at least one update has been performed since the last reset. Otherwise, the approximate Hessian is reset to the identity matrix.
|
R |
is printed if the approximate Hessian has been reset by discarding all but its diagonal elements. This reset will be forced periodically by the values of the optional parameters Hessian Frequency and Hessian Updates. However, it may also be necessary to reset an ill-conditioned Hessian from time to time.
|
l |
is printed if the change in the norm of the variables was greater than the value defined by the optional parameter Major Step Limit. If this output occurs frequently during later iterations, it may be worthwhile increasing the value of Major Step Limit.
|
c |
is printed if central differences have been used to compute the unknown elements of the objective and constraint gradients. A switch to central differences is made if either the linesearch gives a small step, or is close to being optimal. In some cases, it may be necessary to re-solve the QP subproblem with the central difference gradient and Jacobian.
|
u |
is printed if the QP subproblem was unbounded.
|
t |
is printed if the minor iterations were terminated after the number of iterations specified by the value of the optional parameter Minor Iteration Limit was reached.
|
i |
is printed if the QP subproblem was infeasible when the routine was not in elastic mode. This event triggers the start of nonlinear elastic mode, which remains in effect for all subsequent iterations. Once in elastic mode, the QP subproblems are associated with the elastic problem (8) (see Section 10.2). It is also printed if the minimizer of the elastic subproblem does not satisfy the linearized constraints when the routine is already in elastic mode. (In this case, a feasible point for the usual QP subproblem may or may not exist.)
|
w |
is printed if a weak solution of the QP subproblem was found.
|
When
and
, the following line of intermediate printout (
characters) is produced at every minor iteration on the unit number specified by optional parameter
Monitoring File. Unless stated otherwise, the values of the quantities printed are those in effect
on completion of the given iteration.
In the description below, a ‘pricing’ operation is defined to be the process by which a nonbasic variable is selected to become superbasic (in addition to those already in the superbasic set). If the problem is purely linear, the variable selected will usually become basic immediately (unless it happens to reach its opposite bound and return to the nonbasic set).
Itn |
is the iteration count.
|
pp |
is the partial price indicator. The variable selected by the last pricing operation came from the ppth partition of and . Note that pp is reset to zero whenever the basis is refactorized.
|
dj |
is the value of the reduced gradient (or reduced cost) for the variable selected by the pricing operation at the start of the current iteration.
|
+SBS |
is the variable selected by the pricing operation to be added to the superbasic set.
|
-SBS |
is the variable chosen to leave the superbasic set. It has become basic if the entry under -B is nonzero; otherwise it has become nonbasic.
|
-BS |
is the variable removed from the basis (if any) to become nonbasic.
|
-B |
is the variable removed from the basis (if any) to swap with a slack variable made superbasic by the latest pricing operation. The swap is done to ensure that there are no superbasic slacks.
|
Step |
is the value of the step length taken along the current search direction . The variables have just been changed to . If a variable is made superbasic during the current iteration (i.e., +SBS is positive), Step will be the step to the nearest bound. During the optimality phase, the step can be greater than unity only if the reduced Hessian is not positive definite.
|
Pivot |
is the th element of a vector satisfying whenever (the th column of the constraint matrix ) replaces the th column of the basis matrix . Wherever possible, Step is chosen so as to avoid extremely small values of Pivot (since they may cause the basis to be nearly singular). In extreme cases, it may be necessary to increase the value of the optional parameter Pivot Tolerance to exclude very small elements of from consideration during the computation of Step.
|
Ninf |
is the number of infeasibilities. This will not increase unless the iterations are in elastic mode. Ninf will be zero during the optimality phase.
|
Sinf/Objective |
is the value of the current objective function. If is infeasible, Sinf gives the value of the sum of infeasibilities at the start of the current iteration. It will usually decrease at each nonzero value of Step, but may occasionally increase if the value of Ninf decreases by a factor of or more. However, in elastic mode this entry gives the value of the composite objective function (9), which will decrease monotonically at each iteration. If is feasible, Objective is the value of the current QP objective function.
|
L |
is the number of nonzeros in the basis factor . Immediately after a basis factorization , this entry contains lenL. Further nonzeros are added to L when various columns of are later replaced. (Thus, L increases monotonically.)
|
U |
is the number of nonzeros in the basis factor . Immediately after a basis factorization , this entry contains lenU. As columns of are replaced, the matrix is maintained explicitly (in sparse form). The value of U may fluctuate up or down; in general, it will tend to increase.
|
Ncp |
is the number of compressions required to recover workspace in the data structure for . This includes the number of compressions needed during the previous basis factorization. Normally, Ncp should increase very slowly. If it does not, increase LENIZ and LENZ by at least and rerun E04UGF/E04UGA (possibly using ; see Section 5).
|
The following items are printed only if the problem is nonlinear or the superbasic set is non-empty (i.e., if the current solution is nonbasic).
Norm rg |
is the Euclidean norm of the reduced gradient of the QP objective function. During the optimality phase, this norm will be approximately zero after a unit step.
|
nS |
is the current number of superbasic variables.
|
Cond Hz |
is an estimate of the condition number of the reduced Hessian of the Lagrangian (not printed if NCNLN and NONLN are both zero). It is the square of the ratio between the largest and smallest diagonal elements of the upper triangular matrix . This constitutes a lower bound on the condition number of the matrix that approximates the reduced Hessian. The larger this number, the more difficult the problem.
|
When
and
, the following lines of intermediate printout (
characters) are produced on the unit number specified by optional parameter
Monitoring File whenever the matrix
or
is factorized before solving the next QP subproblem. Gaussian elimination is used to compute a sparse
factorization of
or
, where
is a lower triangular matrix and
is an upper triangular matrix for some permutation matrices
and
. The factorization is stabilized in the manner described under the optional parameter
LU Factor Tolerance (
or
).
Note that
may be factorized at the beginning of just some of the major iterations. It is immediately followed by a factorization of
itself.
Factorize |
is the factorization count.
|
Iteration |
is the iteration count.
|
Nonlinear |
is the number of nonlinear variables in the current basis (not printed if is factorized).
|
Linear |
is the number of linear variables in (not printed if is factorized).
|
Slacks |
is the number of slack variables in (not printed if is factorized).
|
Elems |
is the number of nonzeros in (not printed if is factorized).
|
Density |
is the percentage nonzero density of (not printed if is factorized). More precisely, .
|
Compressns |
is the number of times the data structure holding the partially factorized matrix needed to be compressed, in order to recover unused workspace. Ideally, it should be zero. If it is more than or , increase LENIZ and LENZ and rerun E04UGF/E04UGA (possibly using ; see Section 5).
|
Merit |
is the average Markowitz merit count for the elements chosen to be the diagonals of . Each merit count is defined to be , where and are the number of nonzeros in the column and row containing the element at the time it is selected to be the next diagonal. Merit is the average of m such quantities. It gives an indication of how much work was required to preserve sparsity during the factorization.
|
lenL |
is the number of nonzeros in .
|
lenU |
is the number of nonzeros in .
|
Increase |
is the percentage increase in the number of nonzeros in and relative to the number of nonzeros in . More precisely, .
|
m |
is the number of rows in the problem. Note that .
|
Ut |
is the number of triangular rows of at the top of .
|
d1 |
is the number of columns remaining when the density of the basis matrix being factorized reached .
|
Lmax |
is the maximum subdiagonal element in the columns of . This will not exceed the value of the optional parameter LU Factor Tolerance.
|
Bmax |
is the maximum nonzero element in (not printed if is factorized).
|
BSmax |
is the maximum nonzero element in (not printed if is factorized).
|
Umax |
is the maximum nonzero element in , excluding elements of that remain in unchanged. (For example, if a slack variable is in the basis, the corresponding row of will become a row of without modification. Elements in such rows will not contribute to Umax. If the basis is strictly triangular then none of the elements of will contribute and Umax will be zero.)Ideally, Umax should not be significantly larger than Bmax. If it is several orders of magnitude larger, it may be advisable to reset the optional parameter LU Factor Tolerance to some value nearer unity. Umax is not printed if is factorized.
|
Umin |
is the magnitude of the smallest diagonal element of .
|
Growth |
is the value of the ratio Umax/Bmax, which should not be too large. Providing Lmax is not large (say, ), the ratio is an estimate of the condition number of . If this number is extremely large, the basis is nearly singular and some numerical difficulties might occur. (However, an effort is made to avoid near-singularity by using slacks to replace columns of that would have made Umin extremely small and the modified basis is refactorized.)
|
Lt |
is the number of triangular columns of at the left of .
|
bp |
is the size of the ‘bump’ or block to be factorized nontrivially after the triangular rows and columns of have been removed.
|
d2 |
is the number of columns remaining when the density of the basis matrix being factorized has reached .
|
When
,
and
(
), the following lines of intermediate printout (
characters) are produced on the unit number specified by optional parameter
Monitoring File whenever
(see
Section 5). They refer to the number of columns selected by the Crash procedure during each of several passes through
while searching for a triangular basis matrix.
Slacks |
is the number of slacks selected initially.
|
Free cols |
is the number of free columns in the basis, including those whose bounds are rather far apart.
|
Preferred |
is the number of ‘preferred’ columns in the basis (i.e., for some ). It will be a subset of the columns for which was specified.
|
Unit |
is the number of unit columns in the basis.
|
Double |
is the number of columns in the basis containing two nonzeros.
|
Triangle |
is the number of triangular columns in the basis with three (or more) nonzeros.
|
Pad |
is the number of slacks used to pad the basis (to make it a nonsingular triangle).
|
When
or
and
, the following lines of final printout (
characters) are produced on the unit number specified by optional parameter
Monitoring File.
Let denote the th ‘column variable’, for . We assume that a typical variable has bounds .
The following describes the printout for each column (or variable). A full stop (.) is printed for any numerical value that is zero.
Number |
is the column number . (This is used internally to refer to in the intermediate output.)
|
Column |
gives the name of .
|
State |
gives the state of relative to the bounds and .
The various possible states are as follows:
LL |
is nonbasic at its lower limit, .
|
UL |
is nonbasic at its upper limit, .
|
EQ |
is nonbasic and fixed at the value .
|
FR |
is nonbasic at some value strictly between its bounds: .
|
BS |
is basic. Usually .
|
A key is sometimes printed before State.
Note that unless the optional parameter is specified, the tests for assigning a key are applied to the variables of the scaled problem.
A |
Alternative optimum possible. The variable is nonbasic, but its reduced gradient is essentially zero. This means that if the variable were allowed to start moving away from its current value, there would be no change in the value of the objective function. The values of the basic and superbasic variables might change, giving a genuine alternative solution. The values of the Lagrange multipliers might also change.
|
D |
Degenerate. The variable is basic, but it is equal to (or very close to) one of its bounds.
|
I |
Infeasible. The variable is basic and is currently violating one of its bounds by more than the value of the optional parameter Minor Feasibility Tolerance.
|
N |
Not precisely optimal. The variable is nonbasic. Its reduced gradient is larger than the value of the optional parameter Major Feasibility Tolerance.
|
|
Activity |
is the value of at the final iterate.
|
Obj Gradient |
is the value of at the final iterate. (If any is infeasible, is the gradient of the sum of infeasibilities.)
|
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 .
|
Reduced Gradnt |
is the value of at the final iterate.
|
m + j |
is the value of .
|
General linear constraints take the form . The th constraint is therefore of the form and the value of is called the row activity. Internally, the linear constraints take the form , where the slack variables should satisfy the bounds . For the th ‘row’, it is the slack variable that is directly available and it is sometimes convenient to refer to its state. Slacks may be basic or nonbasic (but not superbasic).
Nonlinear constraints are treated similarly, except that the row activity and degree of infeasibility are computed directly from rather than from .
The following describes the printout for each row (or constraint). A full stop (.) is printed for any numerical value that is zero.
Number |
is the value of . (This is used internally to refer to in the intermediate output.)
|
Row |
gives the name of the th row.
|
State |
gives the state of the th row relative to the bounds and .
The various possible states are as follows:
LL |
The row is at its lower limit, .
|
UL |
The row is at its upper limit, .
|
EQ |
The limits are the same .
|
BS |
The constraint is not binding. is basic.
|
A key is sometimes printed before State.
Note that unless the optional parameter is specified, the tests for assigning a key are applied to the variables of the scaled problem.
A |
Alternative optimum possible. The variable is nonbasic, but its reduced gradient is essentially zero. This means that if the variable were allowed to start moving away from its current value, there would be no change in the value of the objective function. The values of the basic and superbasic variables might change, giving a genuine alternative solution. The values of the Lagrange multipliers might also change.
|
D |
Degenerate. The variable is basic, but it is equal to (or very close to) one of its bounds.
|
I |
Infeasible. The variable is basic and is currently violating one of its bounds by more than the value of the optional parameter Minor Feasibility Tolerance.
|
N |
Not precisely optimal. The variable is nonbasic. Its reduced gradient is larger than the value of the optional parameter Major Feasibility Tolerance.
|
|
Activity |
is the value of (or for nonlinear rows) at the final iterate.
|
Slack Activity |
is the value by which the row differs from its nearest bound. (For the free row (if any), it is set to Activity.)
|
Lower Bound |
is , the lower bound specified for the th row. None indicates that .
|
Upper Bound |
is , the upper bound specified for the th row. None indicates that .
|
Dual Activity |
is the value of the dual variable .
|
i |
gives the index of the th row.
|
Numerical values are output with a fixed number of digits; they are not guaranteed to be accurate to this precision.