14. Optimal Transport¶
14.1. Overview¶
The transportation or optimal transport problem is interesting both because of its many applications and because of its important role in the history of economic theory.
In this lecture, we describe the problem, tell how linear programming is a key tool for solving it, and then provide some examples.
We will provide other applications in followup lectures.
The optimal transport problem was studied in early work about linear programming, as summarized for example by [DSS58]. A modern reference about applications in economics is [Gal16].
Below, we show how to solve the optimal transport problem using several implementations of linear programming, including, in order,
the linprog solver from SciPy,
the linprog_simplex solver from QuantEcon and
the simplex-based solvers included in the Python Optimal Transport package.
!pip install --upgrade quantecon
!pip install --upgrade POT
Requirement already satisfied: quantecon in /usr/share/miniconda3/envs/quantecon/lib/python3.8/site-packages (0.5.0)
Collecting quantecon
Downloading quantecon-0.5.2-py3-none-any.whl (269 kB)
?25l
|█▏ | 10 kB 30.6 MB/s eta 0:00:01
|██▍ | 20 kB 22.4 MB/s eta 0:00:01
|███▋ | 30 kB 16.3 MB/s eta 0:00:01
|████▉ | 40 kB 6.5 MB/s eta 0:00:01
|██████ | 51 kB 6.7 MB/s eta 0:00:01
|███████▎ | 61 kB 8.0 MB/s eta 0:00:01
|████████▌ | 71 kB 8.4 MB/s eta 0:00:01
|█████████▊ | 81 kB 9.0 MB/s eta 0:00:01
|███████████ | 92 kB 10.0 MB/s eta 0:00:01
|████████████▏ | 102 kB 7.8 MB/s eta 0:00:01
|█████████████▍ | 112 kB 7.8 MB/s eta 0:00:01
|██████████████▋ | 122 kB 7.8 MB/s eta 0:00:01
|███████████████▉ | 133 kB 7.8 MB/s eta 0:00:01
|█████████████████ | 143 kB 7.8 MB/s eta 0:00:01
|██████████████████▎ | 153 kB 7.8 MB/s eta 0:00:01
|███████████████████▌ | 163 kB 7.8 MB/s eta 0:00:01
|████████████████████▊ | 174 kB 7.8 MB/s eta 0:00:01
|██████████████████████ | 184 kB 7.8 MB/s eta 0:00:01
|███████████████████████▏ | 194 kB 7.8 MB/s eta 0:00:01
|████████████████████████▍ | 204 kB 7.8 MB/s eta 0:00:01
|█████████████████████████▋ | 215 kB 7.8 MB/s eta 0:00:01
|██████████████████████████▉ | 225 kB 7.8 MB/s eta 0:00:01
|████████████████████████████ | 235 kB 7.8 MB/s eta 0:00:01
|█████████████████████████████▏ | 245 kB 7.8 MB/s eta 0:00:01
|██████████████████████████████▍ | 256 kB 7.8 MB/s eta 0:00:01
|███████████████████████████████▋| 266 kB 7.8 MB/s eta 0:00:01
|████████████████████████████████| 269 kB 7.8 MB/s
?25hRequirement already satisfied: requests in /usr/share/miniconda3/envs/quantecon/lib/python3.8/site-packages (from quantecon) (2.26.0)
Requirement already satisfied: numpy in /usr/share/miniconda3/envs/quantecon/lib/python3.8/site-packages (from quantecon) (1.20.3)
Requirement already satisfied: numba>=0.38 in /usr/share/miniconda3/envs/quantecon/lib/python3.8/site-packages (from quantecon) (0.54.1)
Requirement already satisfied: scipy>=1.0.0 in /usr/share/miniconda3/envs/quantecon/lib/python3.8/site-packages (from quantecon) (1.7.1)
Requirement already satisfied: sympy in /usr/share/miniconda3/envs/quantecon/lib/python3.8/site-packages (from quantecon) (1.9)
Requirement already satisfied: llvmlite<0.38,>=0.37.0rc1 in /usr/share/miniconda3/envs/quantecon/lib/python3.8/site-packages (from numba>=0.38->quantecon) (0.37.0)
Requirement already satisfied: setuptools in /usr/share/miniconda3/envs/quantecon/lib/python3.8/site-packages (from numba>=0.38->quantecon) (58.0.4)
Requirement already satisfied: charset-normalizer~=2.0.0 in /usr/share/miniconda3/envs/quantecon/lib/python3.8/site-packages (from requests->quantecon) (2.0.4)
Requirement already satisfied: urllib3<1.27,>=1.21.1 in /usr/share/miniconda3/envs/quantecon/lib/python3.8/site-packages (from requests->quantecon) (1.26.7)
Requirement already satisfied: certifi>=2017.4.17 in /usr/share/miniconda3/envs/quantecon/lib/python3.8/site-packages (from requests->quantecon) (2021.10.8)
Requirement already satisfied: idna<4,>=2.5 in /usr/share/miniconda3/envs/quantecon/lib/python3.8/site-packages (from requests->quantecon) (3.2)
Requirement already satisfied: mpmath>=0.19 in /usr/share/miniconda3/envs/quantecon/lib/python3.8/site-packages (from sympy->quantecon) (1.2.1)
Installing collected packages: quantecon
Attempting uninstall: quantecon
Found existing installation: quantecon 0.5.0
Uninstalling quantecon-0.5.0:
Successfully uninstalled quantecon-0.5.0
Successfully installed quantecon-0.5.2
Collecting POT
Downloading POT-0.8.1.0-cp38-cp38-manylinux_2_12_x86_64.manylinux2010_x86_64.whl (673 kB)
?25l
|▌ | 10 kB 25.9 MB/s eta 0:00:01
|█ | 20 kB 32.1 MB/s eta 0:00:01
|█▌ | 30 kB 25.3 MB/s eta 0:00:01
|██ | 40 kB 7.7 MB/s eta 0:00:01
|██▍ | 51 kB 8.8 MB/s eta 0:00:01
|███ | 61 kB 7.8 MB/s eta 0:00:01
|███▍ | 71 kB 8.4 MB/s eta 0:00:01
|████ | 81 kB 9.5 MB/s eta 0:00:01
|████▍ | 92 kB 10.6 MB/s eta 0:00:01
|████▉ | 102 kB 8.3 MB/s eta 0:00:01
|█████▍ | 112 kB 8.3 MB/s eta 0:00:01
|█████▉ | 122 kB 8.3 MB/s eta 0:00:01
|██████▎ | 133 kB 8.3 MB/s eta 0:00:01
|██████▉ | 143 kB 8.3 MB/s eta 0:00:01
|███████▎ | 153 kB 8.3 MB/s eta 0:00:01
|███████▉ | 163 kB 8.3 MB/s eta 0:00:01
|████████▎ | 174 kB 8.3 MB/s eta 0:00:01
|████████▊ | 184 kB 8.3 MB/s eta 0:00:01
|█████████▎ | 194 kB 8.3 MB/s eta 0:00:01
|█████████▊ | 204 kB 8.3 MB/s eta 0:00:01
|██████████▏ | 215 kB 8.3 MB/s eta 0:00:01
|██████████▊ | 225 kB 8.3 MB/s eta 0:00:01
|███████████▏ | 235 kB 8.3 MB/s eta 0:00:01
|███████████▊ | 245 kB 8.3 MB/s eta 0:00:01
|████████████▏ | 256 kB 8.3 MB/s eta 0:00:01
|████████████▋ | 266 kB 8.3 MB/s eta 0:00:01
|█████████████▏ | 276 kB 8.3 MB/s eta 0:00:01
|█████████████▋ | 286 kB 8.3 MB/s eta 0:00:01
|██████████████▏ | 296 kB 8.3 MB/s eta 0:00:01
|██████████████▋ | 307 kB 8.3 MB/s eta 0:00:01
|███████████████ | 317 kB 8.3 MB/s eta 0:00:01
|███████████████▋ | 327 kB 8.3 MB/s eta 0:00:01
|████████████████ | 337 kB 8.3 MB/s eta 0:00:01
|████████████████▌ | 348 kB 8.3 MB/s eta 0:00:01
|█████████████████ | 358 kB 8.3 MB/s eta 0:00:01
|█████████████████▌ | 368 kB 8.3 MB/s eta 0:00:01
|██████████████████ | 378 kB 8.3 MB/s eta 0:00:01
|██████████████████▌ | 389 kB 8.3 MB/s eta 0:00:01
|███████████████████ | 399 kB 8.3 MB/s eta 0:00:01
|███████████████████▌ | 409 kB 8.3 MB/s eta 0:00:01
|████████████████████ | 419 kB 8.3 MB/s eta 0:00:01
|████████████████████▍ | 430 kB 8.3 MB/s eta 0:00:01
|█████████████████████ | 440 kB 8.3 MB/s eta 0:00:01
|█████████████████████▍ | 450 kB 8.3 MB/s eta 0:00:01
|██████████████████████ | 460 kB 8.3 MB/s eta 0:00:01
|██████████████████████▍ | 471 kB 8.3 MB/s eta 0:00:01
|██████████████████████▉ | 481 kB 8.3 MB/s eta 0:00:01
|███████████████████████▍ | 491 kB 8.3 MB/s eta 0:00:01
|███████████████████████▉ | 501 kB 8.3 MB/s eta 0:00:01
|████████████████████████▍ | 512 kB 8.3 MB/s eta 0:00:01
|████████████████████████▉ | 522 kB 8.3 MB/s eta 0:00:01
|█████████████████████████▎ | 532 kB 8.3 MB/s eta 0:00:01
|█████████████████████████▉ | 542 kB 8.3 MB/s eta 0:00:01
|██████████████████████████▎ | 552 kB 8.3 MB/s eta 0:00:01
|██████████████████████████▊ | 563 kB 8.3 MB/s eta 0:00:01
|███████████████████████████▎ | 573 kB 8.3 MB/s eta 0:00:01
|███████████████████████████▊ | 583 kB 8.3 MB/s eta 0:00:01
|████████████████████████████▎ | 593 kB 8.3 MB/s eta 0:00:01
|████████████████████████████▊ | 604 kB 8.3 MB/s eta 0:00:01
|█████████████████████████████▏ | 614 kB 8.3 MB/s eta 0:00:01
|█████████████████████████████▊ | 624 kB 8.3 MB/s eta 0:00:01
|██████████████████████████████▏ | 634 kB 8.3 MB/s eta 0:00:01
|██████████████████████████████▋ | 645 kB 8.3 MB/s eta 0:00:01
|███████████████████████████████▏| 655 kB 8.3 MB/s eta 0:00:01
|███████████████████████████████▋| 665 kB 8.3 MB/s eta 0:00:01
|████████████████████████████████| 673 kB 8.3 MB/s
?25hRequirement already satisfied: scipy>=1.0 in /usr/share/miniconda3/envs/quantecon/lib/python3.8/site-packages (from POT) (1.7.1)
Requirement already satisfied: numpy>=1.20 in /usr/share/miniconda3/envs/quantecon/lib/python3.8/site-packages (from POT) (1.20.3)
Installing collected packages: POT
Successfully installed POT-0.8.1.0
Let’s start with some imports.
import numpy as np
import matplotlib.pyplot as plt
from scipy.optimize import linprog
from quantecon.optimize import linprog_simplex
import ot
from scipy.stats import binom, betabinom
import networkx as nx
14.2. The Optimal Transport Problem¶
Suppose that \(m\) factories produce goods that must be sent to \(n\) locations.
Let
\(x_{ij}\) denote the quantity shipped from factory \(i\) to location \(j\)
\(c_{ij}\) denote the cost of shipping one unit from factory \(i\) to location \(j\)
\(p_i\) denote the capacity of factory \(i\) and \(q_j\) denote the amount required at location \(j\).
\(i = 1, 2, \dots, m\) and \(j = 1, 2, \dots, n\).
A planner wants to minimize total transportation costs subject to the following constraints:
The amount shipped from each factory must equal its capacity.
The amount shipped to each location must equal the quantity required there.
The figure below shows one visualization of this idea, when factories and target locations are distributed in the plane.
The size of the vertices in the figure are proportional to
capacity, for the factories, and
demand (amount required) for the target locations.
The arrows show one possible transport plan, which respects the constraints stated above.
The planner’s problem can be expressed as the following constrained minimization problem:
This is an optimal transport problem with
\(mn\) decision variables, namely, the entries \(x_{ij}\) and
\(m+n\) constraints.
Summing the \(q_j\)’s across all \(j\)’s and the \(p_i\)’s across all \(i\)’s indicates that the total capacity of all the factories equals total requirements at all locations:
The presence of the restrictions in (14.2) will be the source of one redundancy in the complete set of restrictions that we describe below.
More about this later.
14.3. The Linear Programming Approach¶
In this section we discuss using using standard linear programming solvers to tackle the optimal transport problem.
14.3.1. Vectorizing a Matrix of Decision Variables¶
A matrix of decision variables \(x_{ij}\) appears in problem (14.1).
The SciPy function linprog expects to see a vector of decision variables.
This situation impels us to rewrite our problem in terms of a vector of decision variables.
Let
\(X, C\) be \(m \times n\) matrices with entries \(x_{ij}, c_{ij}\),
\(p\) be \(m\)-dimensional vector with entries \(p_i\),
\(q\) be \(n\)-dimensional vector with entries \(q_j\).
With \(\mathbf{1}_n\) denoting the \(n\)-dimensional column vector \((1, 1, \dots, 1)'\), our problem can now be expressed compactly as:
We can convert the matrix \(X\) into a vector by stacking all of its columns into a column vector.
Doing this is called vectorization, an operation that we denote \(\operatorname{vec}(X)\).
Similarly, we convert the matrix \(C\) into an \(mn\)-dimensional vector \(\operatorname{vec}(C)\).
The objective function can be expressed as the inner product between \(\operatorname{vec}(C)\) and \(\operatorname{vec}(X)\):
To express the constraints in terms of \(\operatorname{vec}(X)\), we use a Kronecker product denoted by \(\otimes\) and defined as follows.
Suppose \(A\) is an \(m \times s\) matrix with entries \((a_{ij})\) and that \(B\) is an \(n \times t\) matrix.
The Kronecker product of \(A\) and \(B\) is defined, in block matrix form, by
\(A \otimes B\) is an \(mn \times st\) matrix.
It has the property that for any \(m \times n\) matrix \(X\)
We can now express our constraints in terms of \(\operatorname{vec}(X)\).
Let \(A = \mathbf{I}_m', B = \mathbf{1}_n\).
By equation (14.3)
where \(\mathbf{I}_m\) denotes the \(m \times m\) identity matrix.
Constraint \(X \ \mathbf{1}_n = p\) can now be written as:
Similarly, the constraint \(X' \ \mathbf{1}_m = q\) can be rewriten as:
With \(z := \operatorname{vec}(X)\), our problem can now be expressed in terms of an \(mn\)-dimensional vector of decision variables:
where
14.3.2. An Application¶
We now provide an example that takes the form (14.4) that we’ll
solve by deploying the function linprog.
The table below provides numbers for the requirements vector \(q\), the capacity vector \(p\), and entries \(c_{ij}\) of the cost-of-shipping matrix \(C\).
| Requirement | ||||
|---|---|---|---|---|
| Location | 1 | 2 | 3 | |
| 1 | 10 | 20 | 30 | 25 |
| 2 | 15 | 40 | 35 | 115 |
| 3 | 20 | 15 | 40 | 60 |
| 4 | 20 | 30 | 55 | 30 |
| 5 | 40 | 30 | 25 | 70 |
| Capacity | 50 | 100 | 150 | 300 |
The numbers in the above table tell us to set \(m = 3\), \(n = 5\), and construct the following objects:
Let’s write Python code that sets up the problem and solves it.
# Define parameters
m = 3
n = 5
p = np.array([50, 100, 150])
q = np.array([25, 115, 60, 30, 70])
C = np.array([[10, 15, 20, 20, 40],
[20, 40, 15, 30, 30],
[30, 35, 40, 55, 25]])
# Vectorize matrix C
C_vec = C.reshape((m*n, 1), order='F')
# Construct matrix A by Kronecker product
A1 = np.kron(np.ones((1, n)), np.identity(m))
A2 = np.kron(np.identity(n), np.ones((1, m)))
A = np.vstack([A1, A2])
# Construct vector b
b = np.hstack([p, q])
# Solve the primal problem
res = linprog(C_vec, A_eq=A, b_eq=b, method='Revised simplex')
# Print results
print("message:", res.message)
print("nit:", res.nit)
print("fun:", res.fun)
print("z:", res.x)
print("X:", res.x.reshape((m,n), order='F'))
message: Optimization terminated successfully.
nit: 12
fun: 7225.0
z: [15. 10. 0. 35. 0. 80. 0. 60. 0. 0. 30. 0. 0. 0. 70.]
X: [[15. 35. 0. 0. 0.]
[10. 0. 60. 30. 0.]
[ 0. 80. 0. 0. 70.]]
/tmp/ipykernel_40789/1014317504.py:24: OptimizeWarning: A_eq does not appear to be of full row rank. To improve performance, check the problem formulation for redundant equality constraints.
res = linprog(C_vec, A_eq=A, b_eq=b, method='Revised simplex')
Interpreting the warning:
The above warning message from SciPy points out that A is not full rank.
This indicates that the linear program has been set up to include one or more redundant constraints.
Here, the source of the redundancy is the structure of restrictions (14.2).
Let’s explore this further by printing out \(A\) and staring at it.
A
array([[1., 0., 0., 1., 0., 0., 1., 0., 0., 1., 0., 0., 1., 0., 0.],
[0., 1., 0., 0., 1., 0., 0., 1., 0., 0., 1., 0., 0., 1., 0.],
[0., 0., 1., 0., 0., 1., 0., 0., 1., 0., 0., 1., 0., 0., 1.],
[1., 1., 1., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0.],
[0., 0., 0., 1., 1., 1., 0., 0., 0., 0., 0., 0., 0., 0., 0.],
[0., 0., 0., 0., 0., 0., 1., 1., 1., 0., 0., 0., 0., 0., 0.],
[0., 0., 0., 0., 0., 0., 0., 0., 0., 1., 1., 1., 0., 0., 0.],
[0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 1., 1., 1.]])
The singularity of \(A\) reflects that the first three constraints and the last five constraints both require that “total requirements equal total capacities” expressed in (14.2).
One equality constraint here is redundant.
Below we drop one of the equality constraints, and use only 7 of them.
After doing this, we attain the same minimized cost.
However, we find a different transportation plan.
Though it is a different plan, it attains the same cost!
linprog(C_vec, A_eq=A[:-1], b_eq=b[:-1], method='Revised simplex')
con: array([0., 0., 0., 0., 0., 0., 0.])
fun: 7225.0
message: 'Optimization terminated successfully.'
nit: 13
slack: array([], dtype=float64)
status: 0
success: True
x: array([ 0., 25., 0., 35., 0., 80., 0., 60., 0., 15., 15., 0., 0.,
0., 70.])
%time linprog(C_vec, A_eq=A[:-1], b_eq=b[:-1], method='Revised simplex')
CPU times: user 3.82 ms, sys: 0 ns, total: 3.82 ms
Wall time: 3.52 ms
con: array([0., 0., 0., 0., 0., 0., 0.])
fun: 7225.0
message: 'Optimization terminated successfully.'
nit: 13
slack: array([], dtype=float64)
status: 0
success: True
x: array([ 0., 25., 0., 35., 0., 80., 0., 60., 0., 15., 15., 0., 0.,
0., 70.])
%time linprog(C_vec, A_eq=A, b_eq=b, method='Revised simplex')
CPU times: user 4.26 ms, sys: 270 µs, total: 4.53 ms
Wall time: 4.52 ms
<timed eval>:1: OptimizeWarning: A_eq does not appear to be of full row rank. To improve performance, check the problem formulation for redundant equality constraints.
con: array([0., 0., 0., 0., 0., 0., 0., 0.])
fun: 7225.0
message: 'Optimization terminated successfully.'
nit: 12
slack: array([], dtype=float64)
status: 0
success: True
x: array([15., 10., 0., 35., 0., 80., 0., 60., 0., 0., 30., 0., 0.,
0., 70.])
Evidently, it is slightly quicker to work with the system that removed a redundant constraint.
Let’s drill down and do some more calculations to help us understand whether or not our finding two different optimal transport plans reflects our having dropped a redundant equality constraint.
Hint
It will turn out that dropping a redundant equality isn’t really what mattered.
To verify our hint, we shall simply use all of the original equality constraints (including a redundant one), but we’ll just shuffle the order of the constraints.
arr = np.arange(m+n)
sol_found = []
cost = []
# simulate 1000 times
for i in range(1000):
np.random.shuffle(arr)
res_shuffle = linprog(C_vec, A_eq=A[arr], b_eq=b[arr], method='Revised simplex')
# if find a new solution
sol = tuple(res_shuffle.x)
if sol not in sol_found:
sol_found.append(sol)
cost.append(res_shuffle.fun)
/tmp/ipykernel_40789/2305330369.py:8: OptimizeWarning: A_eq does not appear to be of full row rank. To improve performance, check the problem formulation for redundant equality constraints.
res_shuffle = linprog(C_vec, A_eq=A[arr], b_eq=b[arr], method='Revised simplex')
for i in range(len(sol_found)):
print(f"transportation plan {i}: ", sol_found[i])
print(f" minimized cost {i}: ", cost[i])
transportation plan 0: (0.0, 25.0, 0.0, 35.0, 0.0, 80.0, 0.0, 60.0, 0.0, 15.0, 15.0, 0.0, 0.0, 0.0, 70.0)
minimized cost 0: 7225.0
transportation plan 1: (15.0, 10.0, 0.0, 35.0, 0.0, 80.0, 0.0, 60.0, 0.0, 0.0, 30.0, 0.0, 0.0, 0.0, 70.0)
minimized cost 1: 7225.0
Ah hah! As you can see, putting constraints in different orders in this case uncovers two optimal transportation plans that achieve the same minimized cost.
These are the same two plans computed earlier.
Next, we show that leaving out the first constraint “accidentally” leads to the initial plan that we computed.
linprog(C_vec, A_eq=A[1:], b_eq=b[1:], method='Revised simplex')
con: array([0., 0., 0., 0., 0., 0., 0.])
fun: 7225.0
message: 'Optimization terminated successfully.'
nit: 12
slack: array([], dtype=float64)
status: 0
success: True
x: array([15., 10., 0., 35., 0., 80., 0., 60., 0., 0., 30., 0., 0.,
0., 70.])
Let’s compare this transport plan with
res.x
array([15., 10., 0., 35., 0., 80., 0., 60., 0., 0., 30., 0., 0.,
0., 70.])
Here the matrix \(X\) contains entries \(x_{ij}\) that tell amounts shipped from factor \(i = 1, 2, 3\) to location \(j=1,2, \ldots, 5\).
The vector \(z\) evidently equals \(\operatorname{vec}(X)\).
The minimized cost from the optimal transport plan is given by the \(fun\) variable.
14.3.3. Using a Just-in-Time Compiler¶
We can also solve optimal transportation problems using a powerful tool from
QuantEcon, namely,quantecon.optimize.linprog_simplex.
While this routine uses the same simplex algorithm as
scipy.optimize.linprog, the code is accelerated by using a just-in-time
compiler shipped in the numba library.
As you will see very soon, by using scipy.optimize.linprog the time required to solve an optimal transportation problem can be reduced significantly.
# construct matrices/vectors for linprog_simplex
c = C.flatten()
# Equality constraints
A_eq = np.zeros((m+n, m*n))
for i in range(m):
for j in range(n):
A_eq[i, i*n+j] = 1
A_eq[m+j, i*n+j] = 1
b_eq = np.hstack([p, q])
Since quantecon.optimize.linprog_simplex does maximization instead of
minimization, we need to put a negative sign before vector c.
res_qe = linprog_simplex(-c, A_eq=A_eq, b_eq=b_eq)
Since the two LP solvers use the same simplex algorithm, we expect to get exactly the same solutions
res_qe.x.reshape((m, n), order='C')
array([[15., 35., 0., 0., 0.],
[10., 0., 60., 30., 0.],
[ 0., 80., 0., 0., 70.]])
res.x.reshape((m, n), order='F')
array([[15., 35., 0., 0., 0.],
[10., 0., 60., 30., 0.],
[ 0., 80., 0., 0., 70.]])
Let’s do a speed comparison between scipy.optimize.linprog and quantecon.optimize.linprog_simplex.
# scipy.optimize.linprog
%time res = linprog(C_vec, A_eq=A[:-1, :], b_eq=b[:-1], method='Revised simplex')
CPU times: user 4.48 ms, sys: 15 µs, total: 4.49 ms
Wall time: 4.08 ms
# quantecon.optimize.linprog_simplex
%time out = linprog_simplex(-c, A_eq=A_eq, b_eq=b_eq)
CPU times: user 109 µs, sys: 3 µs, total: 112 µs
Wall time: 116 µs
As you can see, the quantecon.optimize.linprog_simplex is much faster.
(Note however, that the SciPy version is probably more stable than the QuantEcon version, having been tested more extensively over a longer period of time.)
14.4. The Dual Problem¶
Let \(u, v\) denotes vectors of dual decision variables with entries \((u_i), (v_j)\).
The dual to minimization problem (14.1) is the maximization problem:
The dual problem is also a linear programming problem.
It has \(m+n\) dual variables and \(mn\) constraints.
Vectors \(u\) and \(v\) of values are attached to the first and the second sets of primal constraits, respectively.
Thus, \(u\) is attached to the constraints
\((\mathbf{1}_n' \otimes \mathbf{I}_m) \operatorname{vec}(X) = p\)
and \(v\) is attached to constraints
\((\mathbf{I}_n \otimes \mathbf{1}_m') \operatorname{vec}(X) = q.\)
Components of the vectors \(u\) and \(v\) of per unit values are shadow prices of the quantities appearing on the right sides of those constraints.
We can write the dual problem as
For the same numerical example described above, let’s solve the dual problem.
# Solve the dual problem
res_dual = linprog(-b, A_ub=A.T, b_ub=C_vec,
bounds=[(None, None)]*(m+n), method='Revised simplex')
#Print results
print("message:", res_dual.message)
print("nit:", res_dual.nit)
print("fun:", res_dual.fun)
print("u:", res_dual.x[:m])
print("v:", res_dual.x[-n:])
message: Optimization terminated successfully.
nit: 7
fun: -7225.0
u: [ 5. 15. 25.]
v: [ 5. 10. 0. 15. 0.]
We can also solve the dual problem using quantecon.optimize.linprog_simplex.
res_dual_qe = linprog_simplex(b_eq, A_ub=A_eq.T, b_ub=c)
And the shadow prices computed by the two programs are identical.
res_dual_qe.x
array([ 5., 15., 25., 5., 10., 0., 15., 0.])
res_dual.x
array([ 5., 15., 25., 5., 10., 0., 15., 0.])
We can compare computational times from using our two tools.
%time linprog(-b, A_ub=A.T, b_ub=C_vec, bounds=[(None, None)]*(m+n), method='Revised simplex')
CPU times: user 4.57 ms, sys: 16 µs, total: 4.59 ms
Wall time: 4.82 ms
con: array([], dtype=float64)
fun: -7225.0
message: 'Optimization terminated successfully.'
nit: 7
slack: array([ 0., 0., 0., 0., 15., 0., 15., 0., 15., 0., 0., 15., 35.,
15., 0.])
status: 0
success: True
x: array([ 5., 15., 25., 5., 10., 0., 15., 0.])
%time linprog_simplex(b_eq, A_ub=A_eq.T, b_ub=c)
CPU times: user 395 µs, sys: 11 µs, total: 406 µs
Wall time: 412 µs
SimplexResult(x=array([ 5., 15., 25., 5., 10., 0., 15., 0.]), lambd=array([ 0., 35., 0., 15., 0., 25., 0., 60., 15., 0., 0., 80., 0.,
0., 70.]), fun=7225.0, success=True, status=0, num_iter=24)
quantecon.optimize.linprog_simplex solves the dual problem 10 times faster.
Just for completeness, let’s solve the dual problems with nonsingular \(A\) matrices that we create by dropping a redundant equality constraint.
Try first leaving out the first constraint:
linprog(-b[1:], A_ub=A[1:].T, b_ub=C_vec,
bounds=[(None, None)]*(m+n-1), method='Revised simplex')
con: array([], dtype=float64)
fun: -7225.0
message: 'Optimization terminated successfully.'
nit: 7
slack: array([ 0., 0., 0., 0., 15., 0., 15., 0., 15., 0., 0., 15., 35.,
15., 0.])
status: 0
success: True
x: array([10., 20., 10., 15., 5., 20., 5.])
Not let’s instead leave out the last constraint:
linprog(-b[:-1], A_ub=A[:-1].T, b_ub=C_vec,
bounds=[(None, None)]*(m+n-1), method='Revised simplex')
con: array([], dtype=float64)
fun: -7225.0
message: 'Optimization terminated successfully.'
nit: 11
slack: array([ 0., 0., 0., 0., 15., 0., 15., 0., 15., 0., 0., 15., 35.,
15., 0.])
status: 0
success: True
x: array([ 5., 15., 25., 5., 10., 0., 15.])
14.4.1. Interpretation of dual problem¶
By strong duality (please see this lecture Linear Programming), we know that:
One unit more capacity in factory \(i\), i.e. \(p_i\), results in \(u_i\) more transportation costs.
Thus, \(u_i\) describes the cost of shipping one unit from factory \(i\).
Call this the ship-out cost of one unit shipped from factory \(i\).
Similarly, \(v_j\) is the cost of shipping one unit to location \(j\).
Call this the ship-in cost of one unit to location \(j\).
Strong duality implies that total transprotation costs equals total ship-out costs plus total ship-in costs.
It is reasonable that, for one unit of a product, ship-out cost \(u_i\) plus ship-in cost \(v_j\) should equal transportation cost \(c_{ij}\).
This equality is assured by complementary slackness conditions that state that whenever \(x_{ij} > 0\), meaning that there are positive shipments from factory \(i\) to location \(j\), it must be true that \(u_i + v_j = c_{ij}\).
14.5. The Python Optimal Transport Package¶
There is an excellent Python package for optimal transport that simplifies some of the steps we took above.
In particular, the package takes care of the vectorization steps before passing the data out to a linear programming routine.
(That said, the discussion provided above on vectorization remains important, since we want to understand what happens under the hood.)
14.5.1. Replicating Previous Results¶
The following line of code solves the example application discussed above using linear programming.
X = ot.emd(p, q, C)
X
array([[15, 35, 0, 0, 0],
[10, 0, 60, 30, 0],
[ 0, 80, 0, 0, 70]])
Sure enough, we have the same solution and the same cost
total_cost = np.sum(X * C)
total_cost
7225
14.5.2. A Larger Application¶
Now let’s try using the same package on a slightly larger application.
The application has the same interpretation as above but we will also give each node (i.e., vertex) a location in the plane.
This will allow us to plot the resulting transport plan as edges in a graph.
The following class defines a node by
its location \((x, y) \in \mathbb R^2\),
its group (factory or location, denoted by
porq) andits mass (e.g., \(p_i\) or \(q_j\)).
class Node:
def __init__(self, x, y, mass, group, name):
self.x, self.y = x, y
self.mass, self.group = mass, group
self.name = name
Next we write a function that repeatedly calls the class above to build instances.
It allocates to the nodes it creates their location, mass, and group.
Locations are assigned randomly.
def build_nodes_of_one_type(group='p', n=100, seed=123):
nodes = []
np.random.seed(seed)
for i in range(n):
if group == 'p':
m = 1/n
x = np.random.uniform(-2, 2)
y = np.random.uniform(-2, 2)
else:
m = betabinom.pmf(i, n-1, 2, 2)
x = 0.6 * np.random.uniform(-1.5, 1.5)
y = 0.6 * np.random.uniform(-1.5, 1.5)
name = group + str(i)
nodes.append(Node(x, y, m, group, name))
return nodes
Now we build two lists of nodes, each one containing one type (factories or locations)
n_p = 32
n_q = 32
p_list = build_nodes_of_one_type(group='p', n=n_p)
q_list = build_nodes_of_one_type(group='q', n=n_q)
p_probs = [p.mass for p in p_list]
q_probs = [q.mass for q in q_list]
For the cost matrix \(C\), we use the Euclidean distance between each factory and location.
c = np.empty((n_p, n_q))
for i in range(n_p):
for j in range(n_q):
x0, y0 = p_list[i].x, p_list[i].y
x1, y1 = q_list[j].x, q_list[j].y
c[i, j] = np.sqrt((x0-x1)**2 + (y0-y1)**2)
Now we are ready to apply the solver
%time pi = ot.emd(p_probs, q_probs, c)
CPU times: user 591 µs, sys: 18 µs, total: 609 µs
Wall time: 479 µs
Finally, let’s plot the results using networkx.
In the plot below,
node size is proportional to probability mass
an edge (arrow) from \(i\) to \(j\) is drawn when a positive transfer is made from \(i\) to \(j\) under the optimal transport plan.
g = nx.DiGraph()
g.add_nodes_from([p.name for p in p_list])
g.add_nodes_from([q.name for q in q_list])
for i in range(n_p):
for j in range(n_q):
if pi[i, j] > 0:
g.add_edge(p_list[i].name, q_list[j].name, weight=pi[i, j])
node_pos_dict={}
for p in p_list:
node_pos_dict[p.name] = (p.x, p.y)
for q in q_list:
node_pos_dict[q.name] = (q.x, q.y)
node_color_list = []
node_size_list = []
scale = 8_000
for p in p_list:
node_color_list.append('blue')
node_size_list.append(p.mass * scale)
for q in q_list:
node_color_list.append('red')
node_size_list.append(q.mass * scale)
fig, ax = plt.subplots(figsize=(7, 10))
plt.axis('off')
nx.draw_networkx_nodes(g,
node_pos_dict,
node_color=node_color_list,
node_size=node_size_list,
edgecolors='grey',
linewidths=1,
alpha=0.5,
ax=ax)
nx.draw_networkx_edges(g,
node_pos_dict,
arrows=True,
connectionstyle='arc3,rad=0.1',
alpha=0.6)
plt.show()
