The Linear Programming Solver: The Interior Point Algorithm: Overview :: SAS/OR(R) 9.2 User's Guide: Mathematical Programming

The Linear Programming Solver

The Interior Point Algorithm: Overview

The interior point LP solver (experimental) in PROC OPTMODEL implements an infeasible primal-dual predictor-corrector interior point algorithm. To illustrate the algorithm and the concepts of duality and dual infeasibility, consider the following LP formulation (the primal):

${min} & \mathbf{c}^{\rm t} \mathbf{x} \ {subject to} & \mathbf{a} \mathbf{x} \ge \mathbf{b} \ & \mathbf{x} \ge \mathbf{0}$

The corresponding dual is as follows:

${max} & \mathbf{b}^{\rm t} \mathbf{y} & & & & \ {subject to} & \mathbf{a}^{\rm... ... & & & \mathbf{y} & \ge & \mathbf{0} \ & & & \mathbf{w} & \ge & \mathbf{0}$

where $\mathbf{y} \in \mathbb{r}^m$ refers to the vector of dual variables and $\mathbf{w} \in \mathbb{r}^n$ refers to the vector of dual slack variables.

The dual makes an important contribution to the certificate of optimality for the primal. The primal and dual constraints combined with complementarity conditions define the first-order optimality conditions, also known as KKT (Karush-Kuhn-Tucker) conditions, which can be stated as follows:

$\mathbf{a}\mathbf{x} - \mathbf{s} & = & \mathbf{b} & {\rm (primalfeasibility)} \... ... \mathbf{x},\, \mathbf{y},\, \mathbf{w}, \, \mathbf{s} & \ge &\mathbf{0} & \$

where $\mathbf{e} \equiv (1, ... , 1)^{\rm t}$ of appropriate dimension and $\mathbf{s} \in \mathbb{r}^m$ is the vector of primal slack variables.

Note: Slack variables (the vector) are automatically introduced by the solver when necessary; it is therefore recommended that you not introduce any slack variables explicitly. This enables the solver to handle slack variables much more efficiently.

The letters $\mathbf{x},$ $\mathbf{y},$ $\mathbf{w},$ and $\mathbf{s}$ denote matrices with corresponding and on the main diagonal and zero elsewhere, as in the following example:

$\mathbf{x} \equiv [ x_1 & 0 & ... & 0 \ 0 & x_2 & ... & 0 \ \vdots & \vdots & \ddots & \vdots \ 0 & 0 & ... & x_n ]$

If $(\mathbf{x}^\ast, \mathbf{y}^\ast, \mathbf{w}^\ast, \mathbf{s}^\ast)$ is a solution of the previously defined system of equations representing the KKT conditions, then $\mathbf{x}^\ast$ is also an optimal solution to the original LP model.

At each iteration the interior point algorithm solves a large, sparse system of linear equations as follows:

$[ \mathbf{y}^{-1}\mathbf{s} & \mathbf{a} \ \mathbf{a}^{\rm t} & - \mathbf{x}^{... ... ] [ \delta \mathbf{y} \ \delta \mathbf{x} ] = [ \xi \ \theta \ ]$

where $\delta \mathbf{x}$ and $\delta \mathbf{y}$ denote the vector of search directions in the primal and dual spaces, respectively; $\theta$ and $\xi$ constitute the vector of the right-hand sides.

The preceding system is known as the reduced KKT system. The interior point solver uses a preconditioned quasi-minimum residual algorithm to solve this system of equations efficiently.

An important feature of the interior point solver is that it takes full advantage of the sparsity in the constraint matrix, thereby enabling it to efficiently solve large-scale linear programs.

The interior point algorithm works simultaneously in the primal and dual spaces. It attains optimality when both primal and dual feasibility are achieved and when complementarity conditions hold. Therefore it is of interest to observe the following four measures:

Relative primal infeasibility measure $\alpha$ :
$\alpha = \frac{\vert\mathbf{ax} - \mathbf{b} - \mathbf{s}\vert _2}{\vert\mathbf{b}\vert _2 + 1}$
Relative dual infeasibility measure $\beta$ :
$\beta = \frac{\vert\mathbf{c} - \mathbf{a}^{\rm t} \mathbf{y} - \mathbf{w} \vert _2}{\vert\mathbf{c}\vert _2 + 1}$
Relative duality gap $\delta$ :
$\delta = \frac{|\mathbf{c}^{\rm t}\mathbf{x} - \mathbf{b}^{\rm t}\mathbf{y}|}{|\mathbf{c}^{\rm t}\mathbf{x}| + 1}$
Absolute complementarity $\gamma$ :
$\gamma=\sum_{i=1}^n x_iw_i + \sum_{i=1}^m y_i s_i$

where $\vert v\vert _2$ is the Euclidean norm of the vector

. These measures are displayed in the iteration log.

Top of Page