MIP Gap and Solver Termination Criteria
Introduces the absolute and relative MIP gap that branch-and-bound solvers track during the search, and the criteria — gap tolerance, time limit, node limit, etc. — under which they terminate and report a status.
Tutorial
Incumbent, Best Bound, and the MIP Gap
Branch-and-bound rarely runs all the way to a provably optimal solution. The cost of closing the very last fraction of a percent of optimality can be enormous, so solvers stop as soon as the current solution is provably within a small margin of optimal. To make this precise, we track two quantities throughout the search.
At any point in the search, a solver maintains:
- The incumbent : the objective value of the best integer-feasible solution found so far.
- The best bound : the best LP-relaxation objective across all open (unpruned, unexplored) nodes.
For a minimization MIP, every integer-feasible objective is at least and the current incumbent is no worse than , so the optimal value is sandwiched as
The absolute MIP gap is the width of this interval:
The relative MIP gap scales the absolute gap by the size of the incumbent:
This is what Gurobi and CPLEX report as "MIPGap".
Illustration: if and then
The incumbent is guaranteed to be within of the true optimum.