h02bbf solves ‘zero-one’, ‘general’, ‘mixed’ or ‘all’ integer programming problems using a branch and bound method. The routine may also be used to find either the first integer solution or the optimum integer solution. It is not intended for large sparse problems.
The routine may be called by the names h02bbf or nagf_mip_ilp_dense.
h02bbf is capable of solving certain types of integer programming (IP) problems using a branch and bound (B&B) method, see Taha (1987). In order to describe these types of integer programs and to briefly state the B&B method, we define the following Linear Programming (LP) problem:
If, in (1), it is required that (some or) all the variables take integer values, then the integer program is of type (mixed or) all general IP problem. If additionally, the integer variables are restricted to take only – values (i.e., and ) then the integer program is of type (mixed or all) zero-one IP problem.
The B&B method applies directly to these integer programs. The general idea of B&B (for a full description see Dakin (1965) or Mitra (1973)) is to solve the problem without the integral restrictions as an LP problem (first node). If in the optimal solution an integer variable takes a noninteger value , two LP sub-problems are created by branching, imposing and respectively, where denotes the integer part of . This method of branching continues until the first integer solution (bound) is obtained. The hanging nodes are then solved and investigated in order to prove the optimality of the solution. At each node, an LP problem is solved using e04mff/e04mfa.
Dakin R J (1965) A tree search algorithm for mixed integer programming problems Comput. J.8 250–255
Mitra G (1973) Investigation of some branch and bound strategies for the solution of mixed integer linear programs Math. Programming4 155–170
Taha H A (1987) Operations Research: An Introduction Macmillan, New York
1: – IntegerInput/Output
On entry: an upper bound on the number of iterations for each LP problem.
On exit: unchanged if on entry , else .
2: – IntegerInput
On entry: the amount of printout produced by h02bbf, as indicated below (see Section 5.1 for a description of the printed output). All output is written to the current advisory message unit (as defined by x04abf).
The final IP solution only.
One line of output for each node investigated and the final IP solution.
The original LP solution (first node), one line of output for each node investigated and the final IP solution.
3: – IntegerInput
On entry: , the number of variables.
4: – IntegerInput
On entry: , the number of general linear constraints.
5: – Real (Kind=nag_wp) arrayInput
Note: the second dimension of the array a
must be at least
if and at least if .
On entry: the
th row of a must contain the coefficients of the th general constraint, for .
On entry: the first dimension of the array a as declared in the (sub)program from which h02bbf is called.
7: – Real (Kind=nag_wp) arrayInput
8: – Real (Kind=nag_wp) arrayInput
On entry: bl must contain the lower bounds and bu the upper bounds, for all the constraints in the following order. The first elements of each array must contain the bounds on the variables, and the next elements the bounds for the general linear constraints (if any). To specify a nonexistent lower bound (i.e., ), set and to specify a nonexistent upper bound (i.e., ), set . To specify the th constraint as an equality, set , say, where .
, for ;
if , .
9: – Integer arrayInput
On entry: indicates which are the integer variables in the problem. For example, if is an integer variable then must be set to , and otherwise.
or , for ;
for at least one value of .
10: – Real (Kind=nag_wp) arrayInput
On entry: the coefficients of the objective function . The routine attempts to find a minimum of . If a maximum of is desired,
should be set to , for , so that the routine will find a minimum of .
11: – IntegerInput
On entry: the maximum number of nodes that are to be searched in order to find a solution (optimum integer solution). If and , then the B&B tree search is continued until all the nodes have been investigated.
12: – IntegerInput
On entry: specifies whether to terminate the B&B tree search after the first integer solution (if any) is obtained. If then the B&B tree search is terminated at node say, which contains the first integer solution. For this applies only if .
13: – IntegerInput
On entry: the maximum depth of the B&B tree used for branch and bound.
14: – Real (Kind=nag_wp)Input/Output
On entry: the integer feasibility tolerance; i.e., an integer variable is considered to take an integer value if its violation does not exceed toliv. For example, if the integer variable is near unity then is considered to be integer only if .
On exit: unchanged if on entry , else .
15: – Real (Kind=nag_wp)Input/Output
On entry: the maximum acceptable absolute violation in each constraint at a ‘feasible’ point (feasibility tolerance); i.e., a constraint is considered satisfied if its violation does not exceed tolfes.
On exit: unchanged if on entry , else (where is the machine precision).
16: – Real (Kind=nag_wp)Input/Output
On entry: the ‘infinite’ bound size in the definition of the problem constraints. More precisely, any upper bound greater than or equal to bigbnd will be regarded as and any lower bound less than or equal to will be regarded as .
On exit: unchanged if on entry , else .
17: – Real (Kind=nag_wp) arrayInput/Output
On entry: an initial estimate of the original LP solution.
On exit: with , x contains a solution which will be an estimate of either the optimum integer solution or the first integer solution, depending on the value of intfst. If , then x contains a solution which will be an estimate of the best integer solution that was obtained by searching maxnod nodes.
18: – Real (Kind=nag_wp)Output
On exit: with or , objmip contains the value of the objective function for the IP solution.
19: – Integer arrayCommunication Array
20: – IntegerInput
On entry: the dimension of the array iwork as declared in the (sub)program from which h02bbf is called.
21: – Real (Kind=nag_wp) arrayCommunication Array
22: – IntegerInput
On entry: the dimension of the array rwork as declared in the (sub)program from which h02bbf is called.
If , the amounts of workspace provided and required (with ) are printed. As an alternative to computing maxdpt, liwork and lrwork from the formulas given above, you may prefer to obtain appropriate values from the output of a preliminary run with the values of maxdpt, liwork and lrwork set to . If however only liwork and lrwork are set to , then the appropriate values of these arguments for the given value of maxdpt will be computed and printed unless . In both cases h02bbf will then terminate with .
23: – IntegerInput/Output
On entry: ifail must be set to , or to set behaviour on detection of an error; these values have no effect when no error is detected.
A value of causes the printing of an error message and program execution will be halted; otherwise program execution continues. A value of means that an error message is printed while a value of means that it is not.
If halting is not appropriate, the value or is recommended. If message printing is undesirable, then the value is recommended. Otherwise, the value is recommended since useful values can be provided in some output arguments even when on exit. When the value or 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).
5.1Description of Printed Output
The level of printed output from h02bbf is controlled by you (see the description of msglvl in Section 5).
When , the summary printout at the end of execution of h02bbf includes a listing of the status of every variable and constraint. Note that default names are assigned to all variables and constraints. The following describes the printout for each variable.
gives the name (V) and index , for , of the variable.
gives the state of the variable (FR if neither bound is in the working set, EQ if a fixed variable, LL if on its lower bound, UL if on its upper bound, TF if temporarily fixed at its current value). If Value lies outside the upper or lower bounds by more than the Feasibility Tolerance, State will be ++ or -- respectively.
is the value of the variable at the final iterate.
is the lower bound specified for the variable. (None indicates that .) Note that if , then the printed value of Lower Bound for the th variable may not be the same as that originally supplied in .
is the upper bound specified for the variable. (None indicates that .) Note that if , then the printed value of Upper Bound for the th variable may not be the same as that originally supplied in .
is the value of the Lagrange-multiplier for the associated bound constraint. This will be zero if State is FR or TF. If is optimal, the multiplier should be non-negative if State is LL, and non-positive if State is UL.
is the difference between the variable Value and the nearer of its bounds and .
The meaning of the printout for general constraints is the same as that given above for variables, with ‘variable’ replaced by ‘constraint’, and are replaced by and respectively, and with the following change in the heading.
gives the name (L) and index , for , of the constraint.
When , the summary printout at the end of every node during the execution of h02bbf is a listing of the outcome of forcing an integer variable with a noninteger value to take a value within its specified lower and upper bounds.
is the current node number of the B&B tree being investigated.
is the parent node number of the current node.
is the final objective function value. If a node does not have a feasible solution then No Feas Soln is printed instead of the objective function value. If a node whose optimum solution exceeds the best integer solution so far is encountered (i.e., it does not pay to explore the sub-problem any further), then its objective function value is printed together with a CO (Cut Off).
is the index of the integer variable chosen for branching.
is the noninteger value of the integer variable chosen.
is the lower bound value that the integer variable is allowed to take.
is the upper bound value that the integer variable is allowed to take.
is the value of the integer variable after the current optimization.
is the depth of the B&B tree at the current node.
6Error Indicators and Warnings
If on entry or , explanatory error messages are output on the current error message unit (as defined by x04aaf).
Errors or warnings detected by the routine:
Note: in some cases h02bbf may return useful information.
The problem does not have a feasible integer solution.
It was not possible to satisfy all the integer variables to within the integer feasibility tolerance (determined by toliv). Increase toliv and rerun h02bbf.
The solution is unbounded.
This value of ifail implies that a step as large as bigbnd would have to be taken in order to continue the algorithm (see Section 9).
The does not have a feasible solution.
It was not possible to satisfy all the constraints to within the feasibility tolerance (determined by tolfes). If the data for the constraints are accurate only to the absolute precision , you should ensure that the value of the feasibility tolerance is greater than . For example, if all elements of are of order unity and are accurate only to three decimal places, the feasibility tolerance should be at least (see Section 9).
Iteration limit (determined by itmax) reached without finding a solution. (See Section 9.)
On entry, , .
Constraint: or .
On entry, and .
On entry, .
On entry, .
On entry, .
On entry, the dimension of iwork is too small: . iwork must be of dimension (at least) .
On entry, the dimension of rwork is too small: . rwork must be of dimension (at least) .
On entry, there were infinite or inconsistent bounds given in arrays bl and bu. For further advisory details set .
Search of a branch was terminated due to iteration limit.
The IP solution reported is not the optimum IP solution. In other words, the B&B tree search for at least one of the branches had to be terminated since an LP sub-problem in the branch did not have a solution (see Section 9).
The solution returned is the best solution for the number of nodes investigated in the B&B tree.
No feasible solution was found for the number of nodes investigated in the B&B tree.
Not enough workspace to solve problem.
Although the workspace sizes are sufficient to meet the documented restriction, they are not sufficiently large to accommodate an internal partition of the workspace that meets the requirements of the problem. Increase the workspace sizes.
The maximum depth of the B&B tree used for branch and bound (determined by maxdpt) is too small. Increase maxdpt (along with liwork and/or lrwork if appropriate) and rerun h02bbf.
It may be possible to avoid the difficulty by increasing the magnitude of the feasibility tolerance (tolfes) and rerunning the program. If the message recurs even after this change, see Section 9.
An unexpected error has been triggered by this routine. Please
See Section 7 in the Introduction to the NAG Library FL Interface for further information.
Your licence key may have expired or may not have been installed correctly.
See Section 8 in the Introduction to the NAG Library FL Interface for further information.
Dynamic memory allocation failed.
See Section 9 in the Introduction to the NAG Library FL Interface for further information.
h02bbf implements a numerically stable active set strategy and returns solutions that are as accurate as the condition of the problem warrants on the machine.
8Parallelism and Performance
h02bbf is not thread safe and should not be called from a multithreaded user program. Please see Section 1 in FL Interface Multithreading for more information on thread safety.
h02bbf makes calls to BLAS and/or LAPACK routines, which may be threaded within the vendor library used by this implementation. Consult the documentation for the vendor library for further information.
Please consult the X06 Chapter Introduction for information on how to control and interrogate the OpenMP environment used within this routine. Please also consult the Users' Note for your implementation for any additional implementation-specific information.
The original LP problem may not have an optimum solution, i.e., h02bbf terminates with , or or overflow may occur. In this case, you are recommended to relax the integer restrictions of the problem and try to find the optimum LP solution by using e04mff/e04mfa instead.
In the B&B method, it is possible for an LP sub-problem to terminate without finding a solution. This may occur due to the number of iterations exceeding the maximum allowed. Therefore, the B&B tree search for that particular branch cannot be continued. Thus the returned solution may not be optimal. (). For the second and unlikely case, a solution could not be found despite a second attempt at an LP solution.
This example solves the integer programming problem:
subject to the bounds
and to the general constraints
where and are integer variables.
The initial point, which is feasible, is
The optimal solution is
Note that maximizing is equivalent to minimizing .