In the last post in this series we saw some simple examples of linear programs, derived the concept of a dual linear program, and saw the duality theorem and the complementary slackness conditions which give a rough sketch of the stopping criterion for an algorithm. This time we’ll go ahead and *write *this algorithm for solving linear programs, and next time we’ll apply the algorithm to an industry-strength version of the nutrition problem we saw last time. The algorithm we’ll implement is called the *simplex algorithm*. It was the first algorithm for solving linear programs, invented in the 1940’s by George Dantzig, and it’s still the leading practical algorithm, and it was a key part of a Nobel Prize. It’s by far one of the most important algorithms ever devised.

As usual, we’ll post all of the code written in the making of this post on this blog’s Github page.

## Slack variables and equality constraints

The simplex algorithm can solve any kind of linear program, but it only accepts a special form of the program as input. So first we have to do some manipulations. Recall that the primal form of a linear program was the following minimization problem.

where the brackets mean “dot product.” And its dual is

The linear program can actually have more complicated constraints than just the ones above. In general, one might want to have “greater than” and “less than” constraints in the same problem. It turns out that this isn’t any harder, and moreover the simplex algorithm only uses *equality* constraints, and with some finicky algebra we can turn any set of inequality or equality constraints into a set of equality constraints.

We’ll call our goal the “standard form,” which is as follows:

It seems impossible to get the usual minimization/maximization problem into standard form until you realize there’s nothing stopping you from adding more variables to the problem. That is, say we’re given a constraint like:

we can add a new variable , called a *slack variable*, so that we get an equality:

And now we can just impose that . The idea is that represents how much “slack” there is in the inequality, and you can always choose it to make the condition an equality. So if the equality holds and the variables are nonnegative, then the will still satisfy their original inequality. For “greater than” constraints, we can do the same thing but subtract a nonnegative variable. Finally, if we have a minimization problem “” we can convert it to .

So, to combine all of this together, if we have the following linear program with each kind of constraint,

We can add new variables , and write it as

By defining the vector variable and and to have as appropriately for the new variables, we see that the system is written in standard form.

This is the kind of tedious transformation we can automate with a program. Assuming there are variables, the input consists of the vector of length , and three matrix-vector pairs representing the three kinds of constraints. It’s a bit annoying to describe, but the essential idea is that we compute a rectangular “identity” matrix whose diagonal entries are , and then join this with the original constraint matrix row-wise. The reader can see the full implementation in the Github repository for this post, though we won’t use this particular functionality in the algorithm that follows.

There are some other additional things we could do: for example there might be some variables that are completely unrestricted. What you do in this case is take an unrestricted variable and replace it by the difference of *two* unrestricted variables . For simplicity we’ll ignore this, but it would be a fruitful exercise for the reader to augment the function to account for these.

## What happened to the slackness conditions?

The “standard form” of our linear program raises an obvious question: how can the complementary slackness conditions make sense if everything is an equality? It turns out that one can redo all the work one did for linear programs of the form we gave last time (minimize w.r.t. greater-than constraints) for programs in the new “standard form” above. We even get the same complementary slackness conditions! If you want to, you can do this entire routine quite a bit faster if you invoke the power of Lagrangians. We won’t do that here, but the tool shows up as a way to work with primal-dual conversions in many other parts of mathematics, so it’s a good buzzword to keep in mind.

In our case, the only difference with the complementary slackness conditions is that one of the two is trivial: . This is because if our candidate solution is feasible, then it will have to satisfy already. The other one, that , is the only one we need to worry about.

Again, the complementary slackness conditions give us inspiration here. Recall that, informally, they say that when a variable is used at all, it is used as much as it can be to fulfill its constraint (the corresponding dual constraint is tight). So a solution will correspond to a choice of some variables which are either used or not, and a choice of nonzero variables will correspond to a solution. We even saw this happen in the last post when we observed that broccoli trumps oranges. If we can get a good handle on how to navigate the set of these solutions, then we’ll have a nifty algorithm.

Let’s make this official and lay out our assumptions.

## Extreme points and basic solutions

Remember that the graphical way to solve a linear program is to look at the line (or hyperplane) given by and keep increasing (or decreasing it, if you are minimizing) until the very last moment when this line touches the region of feasible solutions. Also recall that the “feasible region” is just the set of all solutions to , that is the solutions that satisfy the constraints. We imagined this picture:

With this geometric intuition it’s clear that there will always be an optimal solution on a *vertex* of the feasible region. These points are called *extreme points* of the feasible region. But because we will almost never work in the plane again (even introducing slack variables makes us relatively high dimensional!) we want an algebraic characterization of these extreme points.

If you have a little bit of practice with convex sets the correct definition is very natural. Recall that a set is *convex *if for any two points every point on the line segment between and is also in . An algebraic way to say this (thinking of these points now as vectors) is that every point when . Now an *extreme* point is just a point that isn’t on the inside of any such line, i.e. can’t be written this way for . For example,

Another way to say this is that if is an extreme point then whenever can be written as for some , then actually . Now since our constraints are all linear (and there are a finite number of them) they won’t define a convex set with weird curves like the one above. This means that there are a finite number of extreme points that just correspond to the intersections of some of the constraints. So there are at most possibilities.

Indeed we want a characterization of extreme points that’s specific to linear programs in standard form, “.” And here is one.

**Definition: **Let be an matrix with . A solution to is called *basic* if at most of its entries are nonzero.

The reason we call it “basic” is because, under some mild assumptions we describe below, a basic solution corresponds to a vector space basis of . Which basis? The one given by the columns of used in the basic solution. We don’t need to talk about bases like this, though, so in the event of a headache just think of the basis as a set of size corresponding to the nonzero entries of the basic solution.

Indeed, what we’re doing here is looking at the matrix formed by taking the columns of whose indices are in , and the vector in the same way, and looking at the equation . If all the parts of that we removed were zero then this will hold if and only if . One might worry that is not invertible, so we’ll go ahead and assume it is. In fact, we’ll assume that *every* set of columns of forms a basis and that the rows of are also linearly independent. This isn’t without loss of generality because if some rows or columns are not linearly independent, we can remove the offending constraints and variables without changing the set of solutions (this is why it’s so nice to work with the standard form).

Moreover, we’ll assume that every basic solution has *exactly* nonzero variables. A basic solution which doesn’t satisfy this assumption is called *degenerate*, and they’ll essentially be special corner cases in the simplex algorithm. Finally, we call a basic solution *feasible *if (in addition to satisfying ) it satisfies . Now that we’ve made all these assumptions it’s easy to see that choosing nonzero variables uniquely determines a basic feasible solution. Again calling the sub-matrix for a basis , it’s just . Now to finish our characterization, we just have to show that under the same assumptions basic feasible solutions are exactly the extremal points of the feasible region.

**Proposition: **A vector is a basic feasible solution if and only if it’s an extreme point of the set .

*Proof.* For one direction, suppose you have a basic feasible solution , and say we write it as for some . We want to show that this implies . Since all of these points are in the feasible region, all of their coordinates are nonnegative. So whenever a coordinate it must be that both . Since has exactly zero entries, it must be that both have at least zero entries, and hence are both basic. By our non-degeneracy assumption they both then have exactly nonzero entries. Let be the set of the nonzero indices of . Because , we have . Now has all of its nonzero entries in , and because the columns of are linearly independent, the fact that implies .

In the other direction, suppose that you have some extreme point which is feasible but not basic. In other words, there are more than nonzero entries of , and we’ll call the indices where . The columns of are linearly dependent (since they’re vectors in ), and so let be a nontrivial linear combination of the columns of . Add zeros to make the into a length vector , so that . Now

And if we pick sufficiently small will still be nonnegative, because the only entries we’re changing of are the strictly positive ones. Then for , but this is very embarrassing for who was supposed to be an extreme point.

Now that we know extreme points are the same as basic feasible solutions, we need to show that any linear program that has *some* solution has a basic feasible solution. This is clear geometrically: any time you have an optimum it has to either lie on a line or at a vertex, and if it lies on a line then you can slide it to a vertex without changing its value. Nevertheless, it is a useful exercise to go through the algebra.

**Theorem.** Whenever a linear program is feasible and bounded, it has a basic feasible solution.

*Proof.* Let be an optimal solution to the LP. If has at most nonzero entries then it’s a basic solution and by the non-degeneracy assumption it must have exactly nonzero entries. In this case there’s nothing to do, so suppose that has nonzero entries. It can’t be a basic feasible solution, and hence is not an extreme point of the set of feasible solutions (as proved by the last theorem). So write it as for some feasible and .

The only thing we know about is it’s optimal. Let be the cost vector, and the optimality says that , and . We claim that in fact these are equal, that are both optimal as well. Indeed, say were not optimal, then

Which can be rearranged to show that . Unfortunately for , this implies that it was not optimal all along:

An identical argument works to show is optimal, too. Now we claim we can use to get a new solution that has fewer than nonzero entries. Once we show this we’re done: inductively repeat the argument with the smaller solution until we get down to exactly nonzero variables. As before we know that must have at least as many zeros as . If they have more zeros we’re done. And if they have exactly as many zeros we can do the following trick. Write for a we’ll choose later. Note that no matter the , is optimal. Rewriting , we just have to pick a that ensures one of the nonzero coefficients of is zeroed out while maintaining nonnegativity. Indeed, we can just look at the index which minimizes and use . .

So we have an immediate (and inefficient) combinatorial algorithm: enumerate all subsets of size , compute the corresponding basic feasible solution , and see which gives the biggest objective value. The problem is that, even if we knew the value of , this would take time , and it’s not uncommon for to be in the tens or hundreds (and if we don’t know the trivial search is exponential).

So we have to be smarter, and this is where the simplex tableau comes in.

## The simplex tableau

Now say you have any basis and any feasible solution . For now might not be a basic solution, and even if it is, its basis of nonzero entries might not be the same as . We can decompose the equation into the basis part and the non basis part:

and solving the equation for gives

It may look like we’re making a wicked abuse of notation here, but both and are vectors of length so the dimensions actually do work out. Now our feasible solution has to satisfy , and the entries of are all nonnegative, so it must be that and , and by the equality above as well. Now let’s write the maximization objective by expanding it first in terms of the , and then expanding .

If we want to maximize the objective, we can just maximize this last line. There are two cases. In the first, the vector and . In the above equation, this tells us that making any component of bigger will *decrease* the overall objective. In other words, . Picking (with zeros in the non basis part) meets this bound and hence must be optimal. In other words, no matter what basis we’ve chosen (i.e., no matter the candidate basic feasible solution), if the two conditions hold then we’re done.

Now the crux of the algorithm is the second case: if the conditions *aren’t* met, we can pick a positive index of and increase the corresponding value of to increase the objective value. As we do this, other variables in the solution will change as well (by decreasing), and we have to stop when one of them hits zero. In doing so, this changes the basis by removing one index and adding another. In reality, we’ll figure out how much to increase ahead of time, and the change will correspond to a single elementary row-operation in a matrix.

Indeed, the matrix we’ll use to represent all of this data is called a *tableau* in the literature. The columns of the tableau will correspond to variables, and the rows to constraints. The last row of the tableau will maintain a candidate solution to the dual problem. Here’s a rough picture to keep the different parts clear while we go through the details.

But to make it work we do a slick trick, which is to “left-multiply everything” by . In particular, if we have an LP given by , then for any basis it’s equivalent to the LP given by (just multiply your solution to the new program by to get a solution to the old one). And so the actual tableau will be of this form.

When we say it’s in this form, it’s really only true up to rearranging columns. This is because the chosen basis will always be represented by an identity matrix (as it is to start with), so to find the basis you can find the embedded identity sub-matrix. In fact, the beginning of the simplex algorithm will have the initial basis sitting in the *last* few columns of the tableau.

Let’s look a little bit closer at the last row. The first portion is zero because is the identity. But furthermore with this trick the dual LP involves everywhere there’s a variable. In particular, joining all but the last column of the last row of the tableau, we have the vector , and setting we get a candidate solution for the dual. What makes the trick even slicker is that is already the candidate solution , since is the identity. So we’re implicitly keeping track of two solutions here, one for the primal LP, given by the last column of the tableau, and one for the dual, contained in the last row of the tableau.

I told you the last row was the dual solution, so why all the other crap there? This is the final slick in the trick: the last row further encodes the complementary slackness conditions. Now that we recognize the dual candidate sitting there, the complementary slackness conditions simply ask for the last row to be non-positive (this is just another way of saying what we said at the beginning of this section!). You should check this, but it gives us a stopping criterion: if the last row is non-positive then stop and output the last column.

## The simplex algorithm

Now (finally!) we can describe and implement the simplex algorithm in its full glory. Recall that our informal setup has been:

- Find an initial basic feasible solution, and set up the corresponding tableau.
- Find a positive index of the last row, and increase the corresponding variable (adding it to the basis) just enough to make another variable from the basis zero (removing it from the basis).
- Repeat step 2 until the last row is nonpositive.
- Output the last column.

This is almost correct, except for some details about how increasing the corresponding variables works. What we’ll really do is represent the basis variables as pivots (ones in the tableau) and then the first 1 in each row will be the variable whose value is given by the entry in the last column of that row. So, for example, the last entry in the first row may be the optimal value for , if the fifth column is the first entry in row 1 to have a 1.

As we describe the algorithm, we’ll illustrate it running on a simple example. In doing this we’ll see what all the different parts of the tableau correspond to from the previous section in each step of the algorithm.

Spoiler alert: the optimum is and the value of the max is 8.

So let’s be more programmatically formal about this. The main routine is essentially pseudocode, and the difficulty is in implementing the helper functions

def simplex(c, A, b): tableau = initialTableau(c, A, b) while canImprove(tableau): pivot = findPivotIndex(tableau) pivotAbout(tableau, pivot) return primalSolution(tableau), objectiveValue(tableau)

Let’s start with the initial tableau. We’ll assume the user’s inputs already include the slack variables. In particular, our example data *before* adding slack is

c = [3, 2] A = [[1, 2], [1, -1]] b = [4, 1]

And after adding slack:

c = [3, 2, 0, 0] A = [[1, 2, 1, 0], [1, -1, 0, 1]] b = [4, 1]

Now to set up the initial tableau we need an initial feasible solution in mind. The reader is recommended to work this part out with a pencil, since it’s much easier to write down than it is to explain. Since we introduced slack variables, our initial feasible solution (basis) can just be . And so is just the slack variables, is the zero vector, and is the 2×2 identity matrix. Now , which is just the original two columns of we started with, and . For the last row, is zero so the part under is the zero vector. The part under is just .

Rather than move columns around every time the basis changes, we’ll keep the tableau columns in order of . In other words, for our example the initial tableau should look like this.

[[ 1, 2, 1, 0, 4], [ 1, -1, 0, 1, 1], [ 3, 2, 0, 0, 0]]

So implementing `initialTableau`

is just a matter of putting the data in the right place.

def initialTableau(c, A, b): tableau = [row[:] + [x] for row, x in zip(A, b)] tableau.append(c[:] + [0]) return tableau

As an aside: in the event that we *don’t* start with the trivial basic feasible solution of “trivially use the slack variables,” we’d have to do a lot more work in this function. Next, the `primalSolution()`

and `objectiveValue()`

functions are simple, because they just extract the encoded information out from the tableau (some helper functions are omitted for brevity).

def primalSolution(tableau): # the pivot columns denote which variables are used columns = transpose(tableau) indices = [j for j, col in enumerate(columns[:-1]) if isPivotCol(col)] return list(zip(indices, columns[-1])) def objectiveValue(tableau): return -(tableau[-1][-1])

Similarly, the `canImprove()`

function just checks if there’s a nonnegative entry in the last row

def canImprove(tableau): lastRow = tableau[-1] return any(x > 0 for x in lastRow[:-1])

Let’s run the first loop of our simplex algorithm. The first step is checking to see if anything can be improved (in our example it can). Then we have to find a pivot entry in the tableau. This part includes some edge-case checking, but if the edge cases aren’t a problem then the strategy is simple: find a positive entry corresponding to some entry of , and then pick an appropriate entry in that column to use as the pivot. Pivoting increases the value of (from zero) to whatever is the largest we can make it without making some other variables become negative. As we’ve said before, we’ll stop increasing when some other variable hits zero, and we can compute which will be the first to do so by looking at the current values of (in the last column of the tableau), and seeing how pivoting will affect them. If you stare at it for long enough, it becomes clear that the first variable to hit zero will be the entry of the basis for which is minimal (and has to be positve). This is because, in order to maintain the linear equalities, every entry of will be decreased by that value during a pivot, and we can’t let *any* of the variables become negative.

All of this results in the following function, where we have left out the degeneracy/unboundedness checks.

def findPivotIndex(tableau): # pick first nonzero index of the last row column = [i for i,x in enumerate(tableau[-1][:-1]) if x > 0][0] quotients = [(i, r[-1] / r[column]) for i,r in enumerate(tableau[:-1]) if r[column] > 0] # pick row index minimizing the quotient row = min(quotients, key=lambda x: x[1])[0] return row, column

For our example, the minimizer is the entry (second row, first column). Pivoting is just doing the usual elementary row operations (we covered this in a primer a while back on row-reduction). The pivot function we use here is no different, and in particular mutates the list in place.

def pivotAbout(tableau, pivot): i,j = pivot pivotDenom = tableau[i][j] tableau[i] = [x / pivotDenom for x in tableau[i]] for k,row in enumerate(tableau): if k != i: pivotRowMultiple = [y * tableau[k][j] for y in tableau[i]] tableau[k] = [x - y for x,y in zip(tableau[k], pivotRowMultiple)]

And in our example pivoting around the chosen entry gives the new tableau.

[[ 0., 3., 1., -1., 3.], [ 1., -1., 0., 1., 1.], [ 0., 5., 0., -3., -3.]]

In particular, is now , since our pivot removed the second slack variable from the basis. Currently our solution has . Notice how the identity submatrix is still sitting in there, the columns are just swapped around.

There’s still a positive entry in the bottom row, so let’s continue. The next pivot is (0,1), and pivoting around that entry gives the following tableau:

[[ 0. , 1. , 0.33333333, -0.33333333, 1. ], [ 1. , 0. , 0.33333333, 0.66666667, 2. ], [ 0. , 0. , -1.66666667, -1.33333333, -8. ]]

And because all of the entries in the bottom row are negative, we’re done. We read off the solution as we described, so that the first variable is 2 and the second is 1, and the objective value is the opposite of the bottom right entry, 8.

To see all of the source code, including the edge-case-checking we left out of this post, see the Github repository for this post.

## Obivous questions and sad answers

An obvious question is: what is the runtime of the simplex algorithm? Is it polynomial in the size of the tableau? Is it even guaranteed to stop at some point? The surprising truth is that nobody knows the answer to all of these questions! Originally (in the 1940’s) the simplex algorithm actually had an exponential runtime in the worst case, though this was not known until 1972. And indeed, to this day while some variations are known to terminate, no variation is known to have polynomial runtime in the worst case. Some of the choices we made in our implementation (for example, picking the *first* column with a positive entry in the bottom row) have the potential to cycle, i.e., variables leave and enter the basis without changing the objective at all. Doing something like picking a *random* positive column, or picking the column which will increase the objective value by the largest amount are alternatives. Unfortunately, every single pivot-picking rule is known to give rise to exponential-time simplex algorithms in the worst case (in fact, this was discovered as recently as 2011!). So it remains open whether there is a variant of the simplex method that runs in guaranteed polynomial time.

But then, in a stunning turn of events, Leonid Khachiyan proved in the 70’s that in fact linear programs can always be solved in polynomial time, via a completely different algorithm called the *ellipsoid method*. Following that was a method called the *interior point method*, which is significantly more efficient. Both of these algorithms generalize to problems that are harder than linear programming as well, so we will probably cover them in the distant future of this blog.

Despite the celebratory nature of these two results, people still use the simplex algorithm for industrial applications of linear programming. The reason is that it’s much faster in practice, and much simpler to implement and experiment with.

The next obvious question has to do with the poignant observation that whole numbers are great. That is, you often want the solution to your problem to involve integers, and not real numbers. But adding the constraint that the variables in a linear program need to be integer valued (even just 0-1 valued!) is NP-complete. This problem is called *integer linear programming, *or just *integer programming *(IP). So we can’t hope to solve IP, and rightly so: the reader can verify easily that boolean satisfiability instances can be written as linear programs where each clause corresponds to a constraint.

This brings up a very interesting theoretical issue: if we take an integer program and just remove the integrality constraints, and solve the resulting linear program, how far away are the two solutions? If they’re close, then we can hope to give a good *approximation* to the integer program by solving the linear program and somehow turning the resulting solution back into an integer solution. In fact this is a very popular technique called *LP-rounding*. We’ll also likely cover that on this blog at some point.

Oh there’s so much to do and so little time! Until next time.