The Linear Relaxation and Its Bound
Drop the integrality restriction and an integer program becomes a linear program that can actually be solved. Its optimal value is a bound on the integer optimum, never worse, in a direction fixed by whether you are minimising or maximising, and that bound is the foundation of every serious integer method. What the relaxation does not give you is the answer: rounding its solution is not generally valid, and often not even feasible.
Definition
The linear relaxation of an integer program is the same program with every integrality restriction dropped. A binary restriction
Write
The bound. Every feasible point of the integer program is feasible for the relaxation, since the relaxation has strictly fewer restrictions. Optimising over a larger set can only do better or equally well, so for a minimisation
and for a maximisation the inequality reverses. The relaxation is optimistic: it promises at least as much as the integer program can deliver.
The gap. The difference
Three inferences the bound licenses.
- If the relaxation is infeasible, the integer program is infeasible, its feasible set is a subset.
- If the relaxation's optimal solution happens to be integral, it solves the integer program: it is feasible there and attains a value the integer program cannot beat.
- The bound rules out claimed integer solutions better than
, which makes it a check as well as a guide.
What it does not license. Rounding. A rounded relaxation solution may be infeasible, and when feasible it may be far from optimal. Neither failure is rare.
Formal statement
For
Assumptions and scope
The bound's direction follows from the objective sense. For a minimisation the relaxation is a lower bound; for a maximisation an upper bound. Applying the minimisation statement to a maximisation inverts the conclusion.
An infeasible relaxation proves the integer program infeasible. The converse fails: a feasible relaxation says nothing, since the polyhedron may contain no integer point at all.
An integral relaxation solution solves the integer program. This is a fortunate case rather than a method, and it cannot be arranged.
Rounding a relaxation solution is not a valid solution method. The rounded point may be infeasible, and where feasible it may be far from the integer optimum.
A loose bound in a linking constraint weakens the relaxation and makes the gap larger. How a model is written affects how useful its relaxation is, which is why tight formulations matter.
Forms this is expressed in
The same content in several forms. Each makes something visible that the others leave implicit, so moving between them is part of understanding the topic rather than a presentation choice.
geometric
The relaxation drawn against the integer points it is meant to bound. The shaded polygon is the feasible set once integrality is dropped; the marked lattice points are the only plans the integer program may actually choose.
The relaxation's optimum sits at a corner of the polygon, and that corner is generally not a lattice point. The distance between its value and the best lattice value is the gap, and it is why the bound is optimistic rather than attainable.
The picture also shows why rounding is not a method: the nearest lattice point to a fractional corner may lie outside the polygon altogether, and the true integer optimum can sit in a different direction entirely.
Worked material
Example
A bound, a gap, and an inference
Take
The relaxation. Drop integrality. The binding constraints meet where
The bound. This is a maximisation, so
The integer optimum. Checking feasible whole-number points near the region's boundary:
The gap.
What rounding would have given.
Non-example
What the bound does not establish
Not established: that the bound is attainable.
Not established: feasibility of the integer program. A relaxation with a perfectly good optimum tells you nothing about whether any integer point exists. The polyhedron
Not valid: rounding as a method. In the worked example above, rounding
Not the same as a small gap: a good model. A tight relaxation often reflects how the model was written. Two formulations of the same situation can have identical integer optima and wildly different gaps, and the one with loose linking bounds will be far harder to solve.
Not a valid inference in reverse. Relaxation infeasible proves integer infeasible. Relaxation feasible proves nothing. The implication runs one way only, and asserting the converse is the commonest logical slip here.
Not a bound at all, in the wrong direction. For a maximisation the relaxation is an upper bound. Applying the minimisation statement unchanged concludes that no integer plan does worse, which is both true and useless, and it will be used as though it were the other thing.
Contrast
A bound is not an answer
The relaxation produces a number and a point. The number is useful; the point usually is not, and keeping them apart is what this unit is for.
The temptation, stated fairly. The relaxation has been solved. Its answer is
Why it fails, case one: infeasibility.
Why it fails, case two: suboptimality.
The structural reason. The continuous and integer optima answer different questions. Which constraints bind at one need not be the ones binding at the other. There is therefore no reason for the integer optimum to be adjacent to the fractional one, and in larger problems they can be far apart in both coordinates and value.
What the bound is actually for. Three things. It limits how good any plan could be, which lets you stop searching with a guarantee. It refutes claimed solutions that beat it. And it guides methods that search properly, branch and bound splits on a fractional variable precisely because the relaxation identified it, then uses the bound to discard whole regions without examining them.
The sentence to carry. The relaxation tells you what you could hope for. It does not tell you what to do.
Common errors
Common misconception
The integer optimum is found by solving the linear relaxation and rounding its solution to the nearest whole numbers, so the relaxation effectively solves the problem.
Related units
Requires
Connected
- Verifying a Reported Solution (used by)
Learn this topic
Used in
Sources
- Integer Programming (2020)