Options Class for e04ug
Syntax
C# |
---|
public class e04ugOptions |
Visual Basic |
---|
Public Class e04ugOptions |
Visual C++ |
---|
public ref class e04ugOptions |
F# |
---|
type e04ugOptions = class end |
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 x02aj).
Keywords and character values are case and white space insensitive.
Central Difference Interval |
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 [Major Iteration Printout]). See Gill et al. (1981) for a discussion of the accuracy in finite difference approximations.
If , the default value is used.
Check Frequency |
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 |
The default value of is if there are any nonlinear constraints and otherwise. Note that this option does not apply when (see [Parameters]).
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 |
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.
Defaults |
This special keyword may be used to reset all optional parameters to their default values.
Derivative Level |
This parameter indicates which nonlinear function gradients are provided in user-supplied delegates 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 , e04ug 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 , e04ug 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, e04ug 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 |
Nonderivative Linesearch |
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, e04ug 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 |
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 |
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 e04ug (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 |
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.
Infeasible Exit |
Feasible Exit |
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.
Minimize |
Maximize |
Feasible Point |
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 |
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 |
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 |
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 |
Hessian Limited Memory |
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 |
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 |
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 |
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 |
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 |
Nolist |
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 |
LU Singularity Tolerance |
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 [Parameters]), 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 |
LU Update Tolerance |
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 |
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 |
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 |
Optimality Tolerance |
This option specifies the final accuracy of the dual variables. If e04ug 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 |
Print Level |
The value of controls the amount of printout produced by the major iterations of e04ug, as indicated below. A detailed description of the printed output is given in [Major Iteration Printout] (summary output at each major iteration and the final solution) and [Description of Monitoring Information] (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 not in this release)):
Output | |
No output. | |
The final solution only. | |
One line of summary output ( characters; see [Major Iteration Printout]) 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 [Description of Monitoring Information]) 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 [Parameters]). |
If and the unit number defined by the optional parameter Monitoring File is the same as that defined by (X04ABF not in this release) then the summary output for each major iteration is suppressed.
Major Step Limit |
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 |
Feasibility Tolerance |
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 method 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 |
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 |
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 |
The value of controls the amount of printout produced by the minor iterations of e04ug (i.e., the iterations of the quadratic programming algorithm), as indicated below. A detailed description of the printed output is given in [Minor Iteration Printout] (summary output at each minor iteration) and [Description of Monitoring Information] (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 not in this release)):
Output | |
No output. | |
One line of summary output ( characters; see [Minor Iteration Printout]) 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 [Description of Monitoring Information]) for each minor iteration. |
If and the unit number defined by the optional parameter Monitoring File is the same as that defined by (X04ABF not in this release) then the summary output for each minor iteration is suppressed.
Monitoring File |
If and or and then monitoring information is produced by e04ug at every iteration is sent to a file with logical unit number . If and/or and then no monitoring information is produced.
Partial Price |
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 |
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 |
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 method 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 |
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 |
Stop Objective Check At Column |
Start Constraint Check At Column |
Stop Constraint Check At Column |
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 |
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 |
Unbounded Step Size |
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 method 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.
Verify Level |
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 method 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 |
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.