{ } Raw JSON

bundles / scipy latest / scipy / optimize / _linprog / linprog

function

scipy.optimize._linprog:linprog

source: /scipy/optimize/_linprog.py :178

Signature

def   linprog ( c A_ub = None b_ub = None A_eq = None b_eq = None bounds = (0, None) method = highs callback = None options = None x0 = None integrality = None )

Summary

Linear programming: minimize a linear objective function subject to linear equality and inequality constraints.

Extended Summary

Linear programming solves problems of the following form:

\min_x \ & c^T x \\ \mbox{such that} \ & A_{ub} x \leq b_{ub},\\ & A_{eq} x = b_{eq},\\ & l \leq x \leq u ,

where is a vector of decision variables; , , , , and are vectors; and and are matrices.

Alternatively, that's:

  • minimize

    c @ x
  • such that

    A_ub @ x <= b_ub
    A_eq @ x == b_eq
    lb <= x <= ub

Note that by default lb = 0 and ub = None. Other bounds can be specified with bounds.

Parameters

c : 1-D array

The coefficients of the linear objective function to be minimized.

A_ub : 2-D array, optional

The inequality constraint matrix. Each row of A_ub specifies the coefficients of a linear inequality constraint on x.

b_ub : 1-D array, optional

The inequality constraint vector. Each element represents an upper bound on the corresponding value of A_ub @ x.

A_eq : 2-D array, optional

The equality constraint matrix. Each row of A_eq specifies the coefficients of a linear equality constraint on x.

b_eq : 1-D array, optional

The equality constraint vector. Each element of A_eq @ x must equal the corresponding element of b_eq.

bounds : sequence, optional

A sequence of (min, max) pairs for each element in x, defining the minimum and maximum values of that decision variable. If a single tuple (min, max) is provided, then min and max will serve as bounds for all decision variables. Use None to indicate that there is no bound. For instance, the default bound (0, None) means that all decision variables are non-negative, and the pair (None, None) means no bounds at all, i.e. all variables are allowed to be any real.

method : str, optional

The algorithm used to solve the standard form problem. The following are supported.

  • 'highs' <optimize.linprog-highs> (default)

  • 'highs-ds' <optimize.linprog-highs-ds>

  • 'highs-ipm' <optimize.linprog-highs-ipm>

  • 'interior-point' <optimize.linprog-interior-point> (legacy)

  • 'revised simplex' <optimize.linprog-revised_simplex> (legacy)

  • 'simplex' <optimize.linprog-simplex> (legacy)

The legacy methods are deprecated and will be removed in SciPy 1.11.0.

callback : callable, optional

If a callback function is provided, it will be called at least once per iteration of the algorithm. The callback function must accept a single scipy.optimize.OptimizeResult consisting of the following fields:

x

x

fun

fun

success

success

slack

slack

con

con

phase

phase

status

status

nit

nit

message

message

Callback functions are not currently supported by the HiGHS methods.

options : dict, optional

A dictionary of solver options. All methods accept the following options:

maxiter

maxiter

disp

disp

presolve

presolve

All methods except the HiGHS solvers also accept:

tol

tol

autoscale

autoscale

rr

rr

rr_method

rr_method

For method-specific options, see show_options('linprog').

x0 : 1-D array, optional

Guess values of the decision variables, which will be refined by the optimization algorithm. This argument is currently used only by the 'revised simplex' <optimize.linprog-revised_simplex> method, and can only be used if x0 represents a basic feasible solution.

integrality : 1-D array or int, optional

Indicates the type of integrality constraint on each decision variable.

0Continuous variable; no integrality constraint.

1Integer variable; decision variable must be an integer within bounds.

2Semi-continuous variable; decision variable must be within bounds or take value 0.

3Semi-integer variable; decision variable must be an integer within bounds or take value 0.

By default, all variables are continuous.

For mixed integrality constraints, supply an array of shape c.shape. To infer a constraint on each decision variable from shorter inputs, the argument will be broadcast to c.shape using numpy.broadcast_to.

This argument is currently used only by the 'highs' <optimize.linprog-highs> method and is ignored otherwise.

Returns

res : OptimizeResult

A scipy.optimize.OptimizeResult consisting of the fields below. Note that the return types of the fields may depend on whether the optimization was successful, therefore it is recommended to check OptimizeResult.status before relying on the other fields:

x

x

fun

fun

slack

slack

con

con

success

success

status

status

nit

nit

message

message

Notes

This section describes the available solvers that can be selected by the 'method' parameter.

'highs-ds' <optimize.linprog-highs-ds>, and 'highs-ipm' <optimize.linprog-highs-ipm> are interfaces to the HiGHS simplex and interior-point method solvers [13], respectively. 'highs' <optimize.linprog-highs> (default) chooses between the two automatically. These are the fastest linear programming solvers in SciPy, especially for large, sparse problems; which of these two is faster is problem-dependent. The other solvers are legacy methods and will be removed when callback is supported by the HiGHS methods.

Method 'highs-ds' <optimize.linprog-highs-ds>, is a wrapper of the C++ high performance dual revised simplex implementation (HSOL) [13], [14]. Method 'highs-ipm' <optimize.linprog-highs-ipm> is a wrapper of a C++ implementation of an iterior-\ point method [13]; it features a crossover routine, so it is as accurate as a simplex solver. Method 'highs' <optimize.linprog-highs> chooses between the two automatically. For new code involving linprog, we recommend explicitly choosing one of these three method values.

Method 'interior-point' <optimize.linprog-interior-point> uses the primal-dual path following algorithm as outlined in [4]. This algorithm supports sparse constraint matrices and is typically faster than the simplex methods, especially for large, sparse problems. Note, however, that the solution returned may be slightly less accurate than those of the simplex methods and will not, in general, correspond with a vertex of the polytope defined by the constraints.

Method 'revised simplex' <optimize.linprog-revised_simplex> uses the revised simplex method as described in [9], except that a factorization [11] of the basis matrix, rather than its inverse, is efficiently maintained and used to solve the linear systems at each iteration of the algorithm.

Method 'simplex' <optimize.linprog-simplex> uses a traditional, full-tableau implementation of Dantzig's simplex algorithm [1], [2] (not the Nelder-Mead simplex). This algorithm is included for backwards compatibility and educational purposes.

Before applying 'interior-point' <optimize.linprog-interior-point>, 'revised simplex' <optimize.linprog-revised_simplex>, or 'simplex' <optimize.linprog-simplex>, a presolve procedure based on [8] attempts to identify trivial infeasibilities, trivial unboundedness, and potential problem simplifications. Specifically, it checks for:

  • rows of zeros in A_eq or A_ub, representing trivial constraints;

  • columns of zeros in A_eq and A_ub, representing unconstrained variables;

  • column singletons in A_eq, representing fixed variables; and

  • column singletons in A_ub, representing simple bounds.

If presolve reveals that the problem is unbounded (e.g. an unconstrained and unbounded variable has negative cost) or infeasible (e.g., a row of zeros in A_eq corresponds with a nonzero in b_eq), the solver terminates with the appropriate status code. Note that presolve terminates as soon as any sign of unboundedness is detected; consequently, a problem may be reported as unbounded when in reality the problem is infeasible (but infeasibility has not been detected yet). Therefore, if it is important to know whether the problem is actually infeasible, solve the problem again with option presolve=False.

If neither infeasibility nor unboundedness are detected in a single pass of the presolve, bounds are tightened where possible and fixed variables are removed from the problem. Then, linearly dependent rows of the A_eq matrix are removed, (unless they represent an infeasibility) to avoid numerical difficulties in the primary solve routine. Note that rows that are nearly linearly dependent (within a prescribed tolerance) may also be removed, which can change the optimal solution in rare cases. If this is a concern, eliminate redundancy from your problem formulation and run with option rr=False or presolve=False.

Several potential improvements can be made here: additional presolve checks outlined in [8] should be implemented, the presolve routine should be run multiple times (until no further simplifications can be made), and more of the efficiency improvements from [5] should be implemented in the redundancy removal routines.

After presolve, the problem is transformed to standard form by converting the (tightened) simple bounds to upper bound constraints, introducing non-negative slack variables for inequality constraints, and expressing unbounded variables as the difference between two non-negative variables. Optionally, the problem is automatically scaled via equilibration [12]. The selected algorithm solves the standard form problem, and a postprocessing routine converts the result to a solution to the original problem.

Examples

Consider the following problem: .. math:: \min_{x_0, x_1} \ -x_0 + 4x_1 & \\ \mbox{such that} \ -3x_0 + x_1 & \leq 6,\\ -x_0 - 2x_1 & \geq -4,\\ x_1 & \geq -3. The problem is not presented in the form accepted by `linprog`. This is easily remedied by converting the "greater than" inequality constraint to a "less than" inequality constraint by multiplying both sides by a factor of :math:`-1`. Note also that the last constraint is really the simple bound :math:`-3 \leq x_1 \leq \infty`. Finally, since there are no bounds on :math:`x_0`, we must explicitly specify the bounds :math:`-\infty \leq x_0 \leq \infty`, as the default is for variables to be non-negative. After collecting coeffecients into arrays and tuples, the input for this problem is:
from scipy.optimize import linprog
c = [-1, 4]
A = [[-3, 1], [1, 2]]
b = [6, 4]
x0_bounds = (None, None)
x1_bounds = (-3, None)
res = linprog(c, A_ub=A, b_ub=b, bounds=[x0_bounds, x1_bounds])
res.fun
res.x
res.message
The marginals (AKA dual values / shadow prices / Lagrange multipliers) and residuals (slacks) are also available.
res.ineqlin
For example, because the marginal associated with the second inequality constraint is -1, we expect the optimal value of the objective function to decrease by ``eps`` if we add a small amount ``eps`` to the right hand side of the second inequality constraint:
eps = 0.05
b[1] += eps
linprog(c, A_ub=A, b_ub=b, bounds=[x0_bounds, x1_bounds]).fun
Also, because the residual on the first inequality constraint is 39, we can decrease the right hand side of the first constraint by 39 without affecting the optimal solution.
b = [6, 4]  # reset to original values
b[0] -= 39
linprog(c, A_ub=A, b_ub=b, bounds=[x0_bounds, x1_bounds]).fun

See also

show_options

Additional options accepted by the solvers.

Aliases

  • scipy.optimize.linprog

Referenced by