h02ce obtains integer solutions to sparse linear programming and quadratic programming problems.
Syntax
C# |
---|
public static void h02ce( int n, int m, int nnz, int iobj, int ncolh, H..::..H02CE_QPHX qphx, double[] a, int[] ha, int[] ka, double[] bl, double[] bu, string start, string[] names, int nname, string[] crname, ref int ns, double[] xs, int[] intvar, int lintvr, int mdepth, int[] istate, out int miniz, out int minz, out double obj, double[] clamda, int strtgy, int[] iz, double[] z, H..::..H02CE_MONIT monit, H..::..h02ceOptions options, out int ifail ) |
Visual Basic |
---|
Public Shared Sub h02ce ( _ n As Integer, _ m As Integer, _ nnz As Integer, _ iobj As Integer, _ ncolh As Integer, _ qphx As H..::..H02CE_QPHX, _ a As Double(), _ ha As Integer(), _ ka As Integer(), _ bl As Double(), _ bu As Double(), _ start As String, _ names As String(), _ nname As Integer, _ crname As String(), _ ByRef ns As Integer, _ xs As Double(), _ intvar As Integer(), _ lintvr As Integer, _ mdepth As Integer, _ istate As Integer(), _ <OutAttribute> ByRef miniz As Integer, _ <OutAttribute> ByRef minz As Integer, _ <OutAttribute> ByRef obj As Double, _ clamda As Double(), _ strtgy As Integer, _ iz As Integer(), _ z As Double(), _ monit As H..::..H02CE_MONIT, _ options As H..::..h02ceOptions, _ <OutAttribute> ByRef ifail As Integer _ ) |
Visual C++ |
---|
public: static void h02ce( int n, int m, int nnz, int iobj, int ncolh, H..::..H02CE_QPHX^ qphx, array<double>^ a, array<int>^ ha, array<int>^ ka, array<double>^ bl, array<double>^ bu, String^ start, array<String^>^ names, int nname, array<String^>^ crname, int% ns, array<double>^ xs, array<int>^ intvar, int lintvr, int mdepth, array<int>^ istate, [OutAttribute] int% miniz, [OutAttribute] int% minz, [OutAttribute] double% obj, array<double>^ clamda, int strtgy, array<int>^ iz, array<double>^ z, H..::..H02CE_MONIT^ monit, H..::..h02ceOptions^ options, [OutAttribute] int% ifail ) |
F# |
---|
static member h02ce : n : int * m : int * nnz : int * iobj : int * ncolh : int * qphx : H..::..H02CE_QPHX * a : float[] * ha : int[] * ka : int[] * bl : float[] * bu : float[] * start : string * names : string[] * nname : int * crname : string[] * ns : int byref * xs : float[] * intvar : int[] * lintvr : int * mdepth : int * istate : int[] * miniz : int byref * minz : int byref * obj : float byref * clamda : float[] * strtgy : int * iz : int[] * z : float[] * monit : H..::..H02CE_MONIT * options : H..::..h02ceOptions * ifail : int byref -> unit |
Parameters
- n
- Type: System..::..Int32On entry: , the number of variables (excluding slacks). This is the number of columns in the linear constraint matrix .Constraint: .
- m
- Type: System..::..Int32On entry: , the number of general linear constraints (or slacks). This is the number of rows in , including the free row (if any; see iobj).Constraint: .
- nnz
- Type: System..::..Int32On entry: the number of nonzero elements in .Constraint: .
- iobj
- Type: System..::..Int32On entry: if , row iobj of is a free row containing the nonzero elements of the vector appearing in the linear objective term .If , there is no free row, i.e., the problem is either an FP problem (in which case iobj must be set to zero), or a QP problem with .Constraint: .
- ncolh
- Type: System..::..Int32On entry: , the number of leading nonzero columns of the Hessian matrix . For FP and LP problems, ncolh must be set to zero.Constraint: .
- qphx
- Type: NagLibrary..::..H..::..H02CE_QPHXFor QP problems, you must supply a version of qphx to compute the matrix product . If has rows and columns consisting entirely of zeros, it is most efficient to order the variables so thatwhere the nonlinear variables appear first as shown. For LP problems, qphx will never be called by h02ce.
A delegate of type H02CE_QPHX.
- a
- Type: array<System..::..Double>[]()[][]An array of size [nnz]On entry: the nonzero elements of , ordered by increasing column index. Note that multiple elements with the same row and column indices are not allowed.On exit: used as internal workspace prior to being restored and hence is unchanged.
- ha
- Type: array<System..::..Int32>[]()[][]An array of size [nnz]On entry: must contain the row index of the nonzero element stored in , for . Note that the row indices for a column may be supplied in any order.Constraint: , for .
- ka
- Type: array<System..::..Int32>[]()[][]An array of size []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 .Constraints:
- ;
- , for ;
- ;
- , for .
- bl
- Type: array<System..::..Double>[]()[][]An array of size []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 , and the next m elements the bounds for the general linear constraints (or slacks ) and the free row (if any). To specify a nonexistent lower bound (i.e., ), set , where is the value of the optional parameter Infinite Bound Size (). To specify the th constraint as an equality, set , say, where . Note that the lower bound corresponding to the free row must be set to and stored in .Constraint: if ,(See also the description for bu.)
- bu
- Type: array<System..::..Double>[]()[][]An array of size []On entry: , the upper 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 , and the next m elements the bounds for the general linear constraints (or slacks ) and the free row (if any). To specify a nonexistent upper bound (i.e., ), set . Note that the upper bound corresponding to the free row must be set to and stored in .On exit: used as internal workspace prior to being restored and hence is unchanged.Constraints:
- if , ;
- , for ;
- if , .
- start
- Type: System..::..StringOn entry: indicates how a starting basis is to be obtained.
- An internal crash procedure will be used to choose an initial basis matrix .
- A basis is already defined in istate (probably from a previous call).
Constraint: or .
- names
- Type: array<System..::..String>[]()[][]An array of size []On entry: a set of names associated with the so-called MPSX form of the problem.
- Must contain the name for the problem (or be blank).
- Must contain the name for the free row (or be blank).
- Must contain the name for the constraint right-hand side (or be blank).
- Must contain the name for the ranges (or be blank).
- Must contain the name for the bounds (or be blank).
- nname
- Type: System..::..Int32On entry: the number of column (i.e., variable) and row names supplied in the array names.
- There are no names. Default names will be used in the printed output.
- All names must be supplied.
Constraint: or .
- crname
- Type: array<System..::..String>[]()[][]An array of size [nname]On entry: the optional column and row names.If , crname is not referenced and the printed output will use default names for the columns and rows.
- ns
- Type: System..::..Int32%On entry: , the number of superbasics. For QP problems, ns need not be specified if , but must retain its value from a previous call when . For FP and LP problems, ns need not be initialized.On exit: the final number of superbasics. This will be zero for FP and LP problems.
- xs
- Type: array<System..::..Double>[]()[][]An array of size []On entry: the initial values of the variables and slacks . (See the description for istate.)On exit: contains the final value of , for .
- intvar
- Type: array<System..::..Int32>[]()[][]An array of size [lintvr]On entry: specifies which components of the solution vector are constrained to be integer. Specifically, if elements of are required to take integer values then , for , where is the integer index such that is integer. If then must be set to to signal the end of the integer variable indices.The order in which the indices of those components of required to be integer is presented determines the order in which the sub-problems are treated and solved. As such it can be a powerful tool to assist the method in achieving a solution efficiently. The general advice is to enter the important integer variables in the model early in intvar; secondary or less important variables should be entered near the end of the list. However some experimentation might be required to find the optimal order.
- lintvr
- Type: System..::..Int32On entry: , the number of components of required to be integer. If , then lintvr must be set to and set to .
- mdepth
- Type: System..::..Int32On entry: specifies the maximum depth the tree of sub-problems may be developed.Suggested value: .Constraint: .
- istate
- Type: array<System..::..Int32>[]()[][]An array of size []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 columns of . Possible values for are as follows: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.
State of during crash procedure 0 or Eligible for the basis 2 Ignored 3 Eligible for the basis (given preference over or ) 4 or Ignored 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 .Constraints:- if , , for ;
- if , , for .
On exit: the final states of the variables and slacks from the solution of the last sub-problem tackled. The significance of each possible value of is as follows:If (see [Description of the Printed Output]), basic and superbasic variables may be outside their bounds by as much as the value of the optional parameter Feasibility Tolerance (, where is the machine precision). Note that unless the optional parameter () is specified, the 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.State of variable Normal value of Nonbasic Nonbasic Superbasic Between and Basic Between and Very occasionally some nonbasic variables may be outside their bounds by as much as the 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 (see [Description of the Printed Output]) if ).
- miniz
- Type: System..::..Int32%
- minz
- Type: System..::..Int32%
- obj
- Type: System..::..Double%
- clamda
- Type: array<System..::..Double>[]()[][]An array of size []On exit: a set of Lagrange-multipliers for the bounds on the variables and the general constraints. More precisely, the first n elements contain the multipliers (reduced costs) for the bounds on the variables, and the next m elements contain the multipliers (shadow prices) for the general linear constraints.
- strtgy
- Type: System..::..Int32On entry: defines the branching strategy adopted by the method.
- Each sub-problem first explored imposes a tighter upper bound on the component of .
- Each sub-problem first explored imposes a tighter lower bound on the component of .
- Each branch explored imposes a tighter upper bound on the component of if its fractional part is less than , otherwise it imposes a tighter lower bound.
- Random choice is made between first exploring a tighter lower bound or a tighter upper bound sub-problem.
Constraint: , , or .
- iz
- Type: array<System..::..Int32>[]()[][]An array of size [leniz]the dimension of the array iz.Constraint: .
- z
- Type: array<System..::..Double>[]()[][]An array of size [lenz]the dimension of the array z.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 not in this release)). 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 and lenz set to . (h02ce will then terminate with .)
- monit
- Type: NagLibrary..::..H..::..H02CE_MONITTo provide feed-back on the progress of the branch and bound process. Additionally monit provides, via its parameter halt, the ability to terminate the process. (You might choose to do this when an integer solution is found, rather than search for a better solution.) If you do not require any intermediate output then monit may be the dummy method (H02CEY not in this release).
A delegate of type H02CE_MONIT.
- options
- Type: NagLibrary..::..H..::..h02ceOptionsAn Object of type H.h02ceOptions. Used to configure optional parameters to this method.
- ifail
- Type: System..::..Int32%On exit: unless the method detects an error or a warning has been flagged (see [Error Indicators and Warnings]).
Description
h02ce is designed to obtain integer solutions to a class of quadratic programming problems addressed by e04nk. Specifically it solves the following problem:
where is a set of variables (some of which may be required to be integer), is an by matrix and the objective function may be specified in a variety of ways depending upon the particular problem to be solved. The optional parameter Maximize may be used to specify an alternative problem in which is maximized. The possible forms for are listed in Table 1, in which the prefixes LP and QP stand for ‘linear programming’ and ‘quadratic programming’ respectively, is an -element vector and is the by second-derivative matrix (the Hessian matrix).
(1) |
Problem type | Objective function | Hessian matrix |
LP | Not applicable | |
QP | Symmetric positive semidefinite |
For LP and QP problems, the unique global minimum value of is found. For QP problems, you must also provide a method that computes for any given vector . ( need not be stored explicitly.)
(It is not expected that the feasibility problem of e04nk would be relevant here.)
The method employs a ‘Branch and Bound’ technique to enforce the integer constraints. In this technique the problem is first solved without the integer constraints. If a variable is found to be non-integral when it is required to have an integer value then two additional problems are constructed. One bounds the variable above by the nearest integer value below the optimal value previously obtained. The second problem is formed by bounding the variable below by the nearest integer value above the optimal value. This process is continued until an integer solution is found. At this point you may elect to stop, or may continue to search for better integer solutions by examining any other sub-problems that remain to be explained.
In practice the method tries to compute an integer solution as quickly as possible using a depth-first approach, since this helps determine a realistic cut-off value. If we have a cut-off value, say the value of the function at this first integer solution, and any sub-problem, say, has a solution value greater than this cut-off value, then subsequent sub-problems of must have solutions greater than the value of the solution at and therefore need not be computed. Thus a knowledge of a good cut-off value can result in fewer sub-problems being solved and thus speed up the operation of the method. (See the description of monit in [Parameters] for details of how you can supply your own cut-off value.)
Each sub-problem is solved using (E04NKA not in this release). You are referred to the method document for e04nk for details of the algorithm used.
References
Gill P E, Hammarling S, Murray W, Saunders M A and Wright M H (1986) Users' guide for LSSOL (Version 1.0) Report SOL 86-1 Department of Operations Research, Stanford University
Gill P E and Murray W (1978) Numerically stable methods for quadratic programming Math. Programming 14 349–372
Gill P E, Murray W, Saunders M A and Wright M H (1986) Some theoretical properties of an augmented Lagrangian merit function Report SOL 86–6R 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 (1991) Inertia-controlling methods for general quadratic programming SIAM Rev. 33 1–36
Hock W and Schittkowski K (1981) Test Examples for Nonlinear Programming Codes. Lecture Notes in Economics and Mathematical Systems 187 Springer–Verlag
Lawson C L, Hanson R J, Kincaid D R and Krogh F T (1979) Basic linear algebra supbrograms for Fortran usage ACM Trans. Math. Software 5 308–325
Murtagh B A and Saunders M A (1983) MINOS 5.0 user's guide Report SOL 83-20 Department of Operations Research, Stanford University
Error Indicators and Warnings
Errors or warnings detected by the method:
- Halted at your request.
- Successful exit.
- Input parameter error immediately detected.
- No integer solution found.
- mdepth is too small.
- The problem is unbounded (or badly scaled). The objective function is not bounded below in the feasible region.
- The problem is infeasible. The general constraints cannot all be satisfied simultaneously to within the value of the optional parameter Feasibility Tolerance (, where is the machine precision).
- Too many iterations. The value of the optional parameter Iteration Limit () is too small.
- The reduced Hessian matrix (see [Definition of the Working Set and Search Direction]) exceeds its assigned dimension. The value of the optional parameter Superbasics Limit () is too small.
- The Hessian matrix appears to be indefinite. Check that qphx has been coded correctly and that all relevant elements of have been assigned their correct values.
- An input parameter is invalid for an internal call to e04nk.
- Numerical error in trying to satisfy the general constraints. The basis is very ill-conditioned.
- The basis is singular after attempts to factorize it (adding slacks where necessary). Either the problem is badly scaled or the value of the optional parameter LU Factor Tolerance () is too large.
- An internal error has occurred. Contact NAG with details of your program.
Accuracy
h02ce implements a numerically stable active-set strategy and returns solutions that are as accurate as the condition of the problem warrants on the machine.
Parallelism and Performance
None.
Further Comments
This section contains a description of the printed output.
Description of the Printed Output
This section describes the (default) intermediate printout and final printout produced by h02ce. The intermediate printout is a subset of the monitoring information produced by the method at every iteration (see [Description of Monitoring Information]). You can control the level of printed output (see the description of the optional parameter Print Level in [Description of the Optional Parameters]). Note that the intermediate printout and final printout are produced only if (the default).
The following line of summary output ( characters) is produced at every iteration. In all cases, the values of the quantities printed are those in effect on
completion of the given iteration.
Itn | is the iteration count. |
Step | is the step taken along the computed search direction. If a constraint is added during the current iteration, Step will be the step to the nearest constraint. When the problem is of type LP, the step can be greater than one during the optimality phase. |
Ninf | is the number of violated constraints (infeasibilities). This will be zero during the optimality phase. |
Sinf/Objective |
is the value of the current objective function. If is not feasible, Sinf gives a weighted sum of the magnitudes of constraint violations. If is feasible, Objective is the value of the objective function. The output line for the final iteration of the feasibility phase (i.e., the first iteration for which Ninf is zero) will give the value of the true objective at the first feasible point. During the optimality phase, the value of the objective function will be nonincreasing. During the feasibility phase, the number of constraint infeasibilities will not increase until either a feasible point is found, or the optimality of the multipliers implies that no feasible point exists. Once optimal multipliers are obtained, the number of infeasibilities can increase, but the sum of infeasibilities will either remain constant or be reduced until the minimum sum of infeasibilities is found.
|
Norm rg | is , the Euclidean norm of the reduced gradient (see [The Main Iteration]). During the optimality phase, this norm will be approximately zero after a unit step. For FP and LP problems, Norm rg is not printed. |
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 to give some additional information about the state of a variable. Note that unless the optional parameter () is specified, the tests for assigning a key are applied to the variables of the scaled problem.
|
||||||||
Value | is the value of the variable at the final iterate. | ||||||||
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 linear 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, and with the following change in the heading.
Constrnt | gives the name of the linear constraint. |
Note that movement off a constraint (as opposed to a variable moving away from its bound) can be interpreted as allowing the entry in the Residual column to become positive.
Numerical values are output with a fixed number of digits; they are not guaranteed to be accurate to this precision.
Example
This example minimizes the quadratic function , where
subject to the bounds
to the linear constraints
and the variables , , , , , , are constrained to be integer.
The initial point, which is infeasible, is
The optimal solution (to five figures) is
One bound constraint and one linear constraint are active at the solution. Note that the Hessian matrix is positive semidefinite.
Example program (C#): h02cee.cs
Algorithmic Details
This section contains a detailed description of the method used by h02ce.
Overview
h02ce employs a Branch and Bound technique (see [Description]) based on an inertia-controlling method to solve the sub-problems that maintains a Cholesky factorization of the reduced Hessian (see below). The method is similar to that of Gill and Murray (1978), and is described in detail by Gill et al. (1991). Here we briefly summarise the main features of the method. Where possible, explicit reference is made to the names of variables that are parameters of the method or appear in the printed output.
The method used has two distinct phases: finding an initial feasible point by minimizing the sum of infeasibilities (the feasibility phase), and minimizing the quadratic objective function within the feasible region (the optimality phase). The computations in both phases are performed by the same methods. The two-phase nature of the algorithm is reflected by changing the function being minimized from the sum of infeasibilities (the printed quantity Sinf; see [Description of Monitoring Information]) to the quadratic objective function (the printed quantity Objective; see [Description of Monitoring Information]).
In general, an iterative process is required to solve a quadratic program. Given an iterate in both the original variables and the slack variables , a new iterate is defined by
where the step length
is a non-negative scalar (the printed quantity Step; see [Description of Monitoring Information]), and is called the search direction. (For simplicity, we shall consider a typical iteration and avoid reference to the index of the iteration.) Once an iterate is feasible (i.e., satisfies the constraints), all subsequent iterates remain feasible.
(2) |
Definition of the Working Set and Search Direction
At each iterate , a working set of constraints is defined to be a linearly independent subset of the constraints that are satisfied ‘exactly’ (to within the value of the optional parameter Feasibility Tolerance; see [Description of the Optional Parameters]). The working set is the current prediction of the constraints that hold with equality at a solution of the LP or QP problem. Let denote the number of constraints in the working set (including bounds), and let denote the associated by working set matrix consisting of the gradients of the working set constraints.
The search direction is defined so that constraints in the working set remain unaltered for any value of the step length. It follows that must satisfy the identity
This characterisation allows to be computed using any by full-rank matrix that spans the null space of . (Thus, and .) The null space matrix is defined from a sparse factorization of part of (see (6) and (7) below). The direction will satisfy (3) if
where is any -vector.
(3) |
(4) |
The working set contains the constraints and a subset of the upper and lower bounds on the variables . Since the gradient of a bound constraint or is a vector of all zeros except for in position , it follows that the working set matrix contains the rows of and the unit rows associated with the upper and lower bounds in the working set.
The working set matrix can be represented in terms of a certain column partition of the matrix . As in [Description] we partition the constraints so that
where is a square nonsingular basis and , and are the basic, superbasic and nonbasic variables respectively. The nonbasic variables are equal to their upper or lower bounds at , and the superbasic variables are independent variables that are chosen to improve the value of the current objective function. The number of superbasic variables is (the printed quantity Ns; see [Description of Monitoring Information]). Given values of and , the basic variables are adjusted so that satisfies (5).
(5) |
If is a permutation matrix such that , then the working set matrix satisfies
where is the identity matrix with the same number of columns as .
(6) |
The null space matrix is defined from a sparse factorization of part of . In particular, is maintained in ‘reduced gradient’ form, using the LUSOL package (see Gill et al. (1986)) to maintain sparse factors of the basis matrix that alters as the working set changes. Given the permutation , the null space basis is given by
This matrix is used only as an operator, i.e., it is never computed explicitly. Products of the form and are obtained by solving with or . This choice of implies that , the number of ‘degrees of freedom’ at , is the same as , the number of superbasic variables.
(7) |
Let and denote the reduced gradient and reduced Hessian of the objective function:
where is the objective gradient at . Roughly speaking, and describe the first and second derivatives of an -dimensional unconstrained problem for the calculation of . (The condition estimator of is the quantity Cond Hz in the monitoring file output; see [Description of Monitoring Information].)
(8) |
At each iteration, an upper triangular factor is available such that . Normally, is computed from at the start of the optimality phase and then updated as the QP working set changes. For efficiency, the dimension of should not be excessive (say, ). This is guaranteed if the number of nonlinear variables is ‘moderate’.
If the QP problem contains linear variables, is positive semidefinite and may be singular with at least one zero diagonal element. However, an inertia-controlling strategy is used to ensure that only the last diagonal element of can be zero. (See Gill et al. (1991) for a discussion of a similar strategy for indefinite quadratic programming.)
If the initial is singular, enough variables are fixed at their current value to give a nonsingular . This is equivalent to including temporary bound constraints in the working set. Thereafter, can become singular only when a constraint is deleted from the working set (in which case no further constraints are deleted until becomes nonsingular).
The Main Iteration
If the reduced gradient is zero, is a constrained stationary point on the working set. During the feasibility phase, the reduced gradient will usually be zero only at a vertex (although it may be zero elsewhere in the presence of constraint dependencies). During the optimality phase, a zero reduced gradient implies that minimizes the quadratic objective function when the constraints in the working set are treated as equalities. At a constrained stationary point, Lagrange-multipliers are defined from the equations
A Lagrange-multiplier corresponding to an inequality constraint in the working set is said to be optimal if when the associated constraint is at its upper bound, or if when the associated constraint is at its lower bound, where depends on the value of the optional parameter Optimality Tolerance (see [Description of the Optional Parameters]). If a multiplier is nonoptimal, the objective function (either the true objective or the sum of infeasibilities) can be reduced by continuing the minimization with the corresponding constraint excluded from the working set. (This step is sometimes referred to as ‘deleting’ a constraint from the working set.) If optimal multipliers occur during the feasibility phase but the sum of infeasibilities is nonzero, there is no feasible point and the method terminates immediately with (see [Error Indicators and Warnings]).
(9) |
The special form (6) of the working set allows the multiplier vector , the solution of (9), to be written in terms of the vector
where satisfies the equations , and denotes the basic elements of . The elements of are the Lagrange-multipliers associated with the equality constraints . The vector of nonbasic elements of consists of the Lagrange-multipliers associated with the upper and lower bound constraints in the working set. The vector of superbasic elements of is the reduced gradient in (8). The vector of basic elements of is zero, by construction. (The Euclidean norm of and the final values of , and are the quantities Norm rg, Reduced Gradnt, Obj Gradient and Dual Activity in the monitoring file output; see [Description of Monitoring Information].)
(10) |
If the reduced gradient is not zero, Lagrange-multipliers need not be computed and the search direction is given by (see (7) and (11)). The step length is chosen to maintain feasibility with respect to the satisfied constraints.
There are two possible choices for , depending on whether or not is singular. If is nonsingular, is nonsingular and in (4) is computed from the equations
where is the reduced gradient at . In this case, is the minimizer of the objective function subject to the working set constraints being treated as equalities. If is feasible, is defined to be unity. In this case, the reduced gradient at will be zero, and Lagrange-multipliers are computed at the next iteration. Otherwise, is set to , the step to the ‘nearest’ constraint along . This constraint is added to the working set at the next iteration.
(11) |
If is singular, then must also be singular, and an inertia-controlling strategy is used to ensure that only the last diagonal element of is zero. (See Gill et al. (1991) for a discussion of a similar strategy for indefinite quadratic programming.) In this case, satisfies
which allows the objective function to be reduced by any step of the form , where . The vector is a direction of unbounded descent for the QP problem in the sense that the QP objective is linear and decreases without bound along . If no finite step of the form (where ) reaches a constraint not in the working set, the QP problem is unbounded and the method terminates immediately with (see [Error Indicators and Warnings]). Otherwise, is defined as the maximum feasible step along and a constraint active at is added to the working set for the next iteration.
(12) |
Miscellaneous
If the basis matrix is not chosen carefully, the condition of the null space matrix in (7) could be arbitrarily high. To guard against this, the method implements a ‘basis repair’ feature in which the LUSOL package (see Gill et al. (1986)) is used to compute the rectangular factorization
returning just the permutation that makes unit lower triangular. The pivot tolerance is set to require
, and the permutation is used to define in (6). It can be shown that is likely to be little more than unity. Hence, should be well-conditioned regardless of the condition of
. This feature is applied at the beginning of the optimality phase if a potential ordering is known.
(13) |
The EXPAND procedure (see Gill et al. (1989)) is used to reduce the possibility of cycling at a point where the active constraints are nearly linearly dependent. Although there is no absolute guarantee that cycling will not occur, the probability of cycling is extremely small (see Gill et al. (1986)). The main feature of EXPAND is that the feasibility tolerance is increased at the start of every iteration. This allows a positive step to be taken at every iteration, perhaps at the expense of violating the bounds on by a small amount.
Suppose that the value of the optional parameter Feasibility Tolerance is . Over a period of iterations (where is the value of the optional parameter Expand Frequency; see [Description of the Optional Parameters]), the feasibility tolerance actually used by h02ce (i.e., the working feasibility tolerance) increases from to (in steps of ).
At certain stages the following ‘resetting procedure’ is used to remove small constraint infeasibilities. First, all nonbasic variables are moved exactly onto their bounds. A count is kept of the number of nontrivial adjustments made. If the count is nonzero, the basic variables are recomputed. Finally, the working feasibility tolerance is reinitialized to .
If a problem requires more than iterations, the resetting procedure is invoked and a new cycle of iterations is started. (The decision to resume the feasibility phase or optimality phase is based on comparing any constraint infeasibilities with .)
The resetting procedure is also invoked when h02ce reaches an apparently optimal, infeasible or unbounded solution, unless this situation has already occurred twice. If any nontrivial adjustments are made, iterations are continued.
The EXPAND procedure not only allows a positive step to be taken at every iteration, but also provides a potential choice of constraints to be added to the working set. All constraints at a distance (where ) along from the current point are then viewed as acceptable candidates for inclusion in the working set. The constraint whose normal makes the largest angle with the search direction is added to the working set. This strategy helps keep the basis matrix well-conditioned.
Description of Monitoring Information
This section describes the intermediate printout and final printout which constitutes the monitoring information produced by h02ce. (See also the description of the optional parameters Monitoring File and Print Level in [Description of the Optional Parameters].) You can control the level of printed output.
When or and , the following line of intermediate printout ( characters) is produced at every iteration on the unit number specified by Monitoring File. Unless stated otherwise, the values of the quantities printed are those in effect on completion of the given iteration.
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. |
+S | is the variable selected by the pricing operation to be added to the superbasic set. |
-S | is the variable chosen to leave the superbasic set. |
-B | is the variable removed from the basis (if any) to become nonbasic. |
-B | is the variable chosen to leave the set of basics (if any) in a special basic superbasic swap. The entry under -S has become basic if this entry is nonzero, and nonbasic otherwise. The swap is done to ensure that there are no superbasic slacks. |
Step | is the value of the step length taken along the computed search direction . The variables have been changed to . If a variable is made superbasic during the current iteration (i.e., +S 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 (, where is the machine precision) to exclude very small elements of from consideration during the computation of Step. |
Ninf | is the number of violated constraints (infeasibilities). This will be zero during the optimality phase. |
Sinf/Objective |
is the value of the current objective function. If is not feasible, Sinf gives a weighted sum of the magnitudes of constraint violations. If is feasible, Objective is the value of the objective function. The output line for the final iteration of the feasibility phase (i.e., the first iteration for which Ninf is zero) will give the value of the true objective at the first feasible point. During the optimality phase, the value of the objective function will be nonincreasing. During the feasibility phase, the number of constraint infeasibilities will not increase until either a feasible point is found, or the optimality of the multipliers implies that no feasible point exists. Once optimal multipliers are obtained, the number of infeasibilities can increase, but the sum of infeasibilities will either remain constant or be reduced until the minimum sum of infeasibilities is found.
|
L | is the number of nonzeros in the basis factor . Immediately after a basis factorization , this is lenL, the number of subdiagonal elements in the columns of a lower triangular matrix. 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 is lenU, the number of diagonal and superdiagonal elements in the rows of an upper triangular matrix. 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 lenz by at least and rerun h02ce (possibly using ; see [Parameters]). |
Norm rg | is , the Euclidean norm of the reduced gradient (see [The Main Iteration]). During the optimality phase, this norm will be approximately zero after a unit step. For FP and LP problems, Norm rg is not printed. |
Ns | is the current number of superbasic variables. For FP and LP problems, Ns is not printed. |
Cond Hz | is a lower bound on the condition number of the reduced Hessian (see [Definition of the Working Set and Search Direction]). The larger this number, the more difficult the problem. For FP and LP problems, Cond Hz is not printed. |
When and , the following lines of intermediate printout ( characters) are produced on the unit number specified by Monitoring File whenever the matrix or is factorized. Gaussian elimination is used to compute an 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 LU Factor Tolerance (; see [Description of the Optional Parameters]).
Factorize | is the factorization count. | ||||||||||||||
Demand |
is a code giving the reason for the present factorization as follows:
|
||||||||||||||
Iteration | is the iteration count. | ||||||||||||||
Nonlinear | is the number of nonlinear variables in (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 h02ce (possibly using ; see [Parameters]). | ||||||||||||||
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 (not printed if is factorized). This will not exceed the value of the 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, 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 LU Factor Tolerance to a value near . Umax is not printed if is factorized.
|
||||||||||||||
Umin | is the magnitude of the smallest diagonal element of (not printed if is factorized). | ||||||||||||||
Growth |
is the value of the ratio , 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 could occur in subsequent computations. (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.) Growth is not printed if is factorized.
|
||||||||||||||
Lt | is the number of triangular columns of at the beginning of . | ||||||||||||||
bp | is the size of the ‘bump’ or block to be factorized nontrivially after the triangular rows and columns have been removed. | ||||||||||||||
d2 | is the number of columns remaining when the density of the basis matrix being factorized reached . |
When and , the following lines of intermediate printout ( characters) are produced on the unit number specified by Monitoring File whenever (see [Parameters]). They refer to the number of columns selected by the crash procedure during each of several passes through , whilst 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. |
Preferred | is the number of ‘preferred’ columns in the basis (i.e., for some ). |
Unit | is the number of unit columns in the basis. |
Double | is the number of double columns in the basis. |
Triangle | is the number of triangular columns in the basis. |
Pad | is the number of slacks used to pad the basis. |
When and , the following lines of intermediate printout ( characters) are produced on the unit number specified by Monitoring File. They refer to the elements of the names array (see [Parameters]).
Name | gives the name for the problem (blank if none). |
Objective | gives the name of the free row for the problem (blank if none). |
RHS | gives the name of the constraint right-hand side for the problem (blank if none). |
Ranges | gives the name of the ranges for the problem (blank if none). |
Bounds | gives the name of the bounds for the problem (blank if none). |
When or and , the following lines of final printout ( characters) are produced on the unit number specified by Monitoring File.
Let denote the th column of , for . 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 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 to give some additional information about the state of . Note that unless the optional parameter () is specified, the tests for assigning a key are applied to the variables of the scaled problem.
|
||||||||
Activity | is the value of at the final iterate. | ||||||||
Obj Gradient | is the value of at the final iterate. For FP problems, is set to zero. | ||||||||
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 (see [The Main Iteration]). For FP problems, is set to zero. | ||||||||
m + j | is the value of . |
Let denote the th row of , for . 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 . | ||||||||
State |
gives the state of the variable (LL if active on its lower bound, UL if active on its upper bound, EQ if active and fixed, BS if inactive when is basic and SBS if inactive when is superbasic).
A key is sometimes printed before State to give some additional information about the state of . Note that unless the optional parameter () is specified, the tests for assigning a key are applied to the variables of the scaled problem.
|
||||||||
Activity | is the value of at the final iterate. | ||||||||
Slack Activity | is the value by which 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 variable. None indicates that . | ||||||||
Upper Bound | is the upper bound specified for the variable. None indicates that . | ||||||||
i | gives the index of . |
Numerical values are output with a fixed number of digits; they are not guaranteed to be accurate to this precision.