The minimum-cost network flow (MCF) problem is a fundamental problem in network analysis that involves sending flow over a network at minimal cost. Let be a directed graph. For each link , associate a cost per unit of flow, designated as . The demand (or supply) at each node is designated as , where denotes a supply node and denotes a demand node. These values must be within . Define decision variables that denote the amount of flow sent between node i and node j. The amount of flow that can be sent across each link is bounded to be within . The problem can be modeled as a linear programming problem as follows:
When for all nodes , the problem is called a pure network flow problem. For these problems, the sum of the supplies and demands must be equal to 0 to ensure that a feasible solution exists.
In PROC OPTNET, you can invoke the minimum-cost network flow solver by using the MINCOSTFLOW statement. The options for this statement are described in the section MINCOSTFLOW Statement.
The minimum-cost network flow solver reports status information in a macro variable called _OROPTNET_MCF_. For more information about this macro variable, see the section Macro Variable _OROPTNET_MCF_.
The algorithm that PROC OPTNET uses to solve the MCF problem is a variant of the primal network simplex algorithm (Ahuja, Magnanti, and Orlin 1993). Sometimes the directed graph is disconnected. In this case, the problem is first decomposed into its weakly connected components, and then each minimum-cost flow problem is solved separately.
The input for the network is the standard graph input, which is described in the section Graph Input Data. The links data set, which is specified in the DATA_LINKS= option in the PROC OPTNET statement, contains the following columns:
weight
, which defines the link cost
lower
, which defines the link lower bound . The default is 0.
upper
, which defines the link upper bound . The default is .
The nodes data set, which is specified in the DATA_NODES= option in the PROC OPTNET statement, can contain the following columns:
weight
, which defines the node supply lower bound . The default is 0.
weight2
, which defines the node supply upper bound . The default is .
To define a pure network in which the node supply must be met exactly, use the weight
variable only. You do not need to specify all the node supply bounds. For any missing node, the solver uses a lower and upper
bound of 0.
To explicitly define an upper bound of , use the special missing value, (
.I). To explicitly define a lower bound of , use the special missing value, (
.M). Related to infinite bounds, the following scenarios are not supported:
The flow on a link must be bounded from below ( is not allowed).
Flow balance constraints cannot be free ( and is not allowed).
The resulting optimal flow through the network is written to the links output data set, which is specified in the OUT_LINKS= option in the PROC OPTNET statement.
This example demonstrates how to use the network simplex algorithm to find a minimum-cost flow in a directed graph. Consider the directed graph in Figure 2.35, which appears in Ahuja, Magnanti, and Orlin (1993).
The directed graph can be represented by the following links data set LinkSetIn
and nodes data set NodeSetIn
:
data LinkSetIn; input from to weight upper; datalines; 1 4 2 15 2 1 1 10 2 3 0 10 2 6 6 10 3 4 1 5 3 5 4 10 4 7 5 10 5 6 2 20 5 7 7 15 6 8 8 10 7 8 9 15 ;
data NodeSetIn; input node weight; datalines; 1 10 2 20 4 -5 7 -15 8 -10 ;
You can use the following call to PROC OPTNET to find a minimum-cost flow:
proc optnet loglevel = moderate graph_direction = directed data_links = LinkSetIn data_nodes = NodeSetIn out_links = LinkSetOut; mincostflow logfreq = 1; run; %put &_OROPTNET_; %put &_OROPTNET_MCF_;
The progress of the procedure is shown in Figure 2.36.
Figure 2.36: PROC OPTNET Log for Minimum-Cost Network Flow
NOTE: ------------------------------------------------------------------------------------------ |
NOTE: ------------------------------------------------------------------------------------------ |
NOTE: Running OPTNET version 13.2. |
NOTE: ------------------------------------------------------------------------------------------ |
NOTE: ------------------------------------------------------------------------------------------ |
NOTE: Reading the nodes data set. |
NOTE: There were 5 observations read from the data set WORK.NODESETIN. |
NOTE: Reading the links data set. |
NOTE: There were 11 observations read from the data set WORK.LINKSETIN. |
NOTE: Data input used 0.01 (cpu: 0.00) seconds. |
NOTE: Building the input graph storage used 0.00 (cpu: 0.00) seconds. |
NOTE: The input graph storage is using 0.0 MBs of memory. |
NOTE: The number of nodes in the input graph is 8. |
NOTE: The number of links in the input graph is 11. |
NOTE: ------------------------------------------------------------------------------------------ |
NOTE: ------------------------------------------------------------------------------------------ |
NOTE: Processing the minimum-cost network flow problem. |
NOTE: The network has 1 connected component. |
Primal Primal Dual |
Iteration Objective Infeasibility Infeasibility Time |
1 0.000000E+00 2.000000E+01 8.900000E+01 0.00 |
2 0.000000E+00 2.000000E+01 8.900000E+01 0.00 |
3 5.000000E+00 1.500000E+01 8.400000E+01 0.00 |
4 5.000000E+00 1.500000E+01 8.300000E+01 0.00 |
5 7.500000E+01 1.500000E+01 8.300000E+01 0.00 |
6 7.500000E+01 1.500000E+01 7.900000E+01 0.00 |
7 1.300000E+02 1.000000E+01 7.600000E+01 0.00 |
8 2.700000E+02 0.000000E+00 0.000000E+00 0.00 |
NOTE: The Network Simplex solve time is 0.00 seconds. |
NOTE: Objective = 270. |
NOTE: Processing the minimum-cost network flow problem used 0.00 (cpu: 0.00) seconds. |
NOTE: ------------------------------------------------------------------------------------------ |
NOTE: Creating links data set output. |
NOTE: Data output used 0.00 (cpu: 0.00) seconds. |
NOTE: ------------------------------------------------------------------------------------------ |
NOTE: ------------------------------------------------------------------------------------------ |
NOTE: The data set WORK.LINKSETOUT has 11 observations and 5 variables. |
STATUS=OK MCF=OPTIMAL |
STATUS=OPTIMAL OBJECTIVE=270 CPU_TIME=0.00 REAL_TIME=0.00 |
The optimal solution is displayed in Figure 2.37.
The optimal solution is represented graphically in Figure 2.38.
Using the same directed graph shown in Figure 2.35, this example demonstrates a network that has a flexible supply and demand. Consider the following adjustments to the node bounds:
Node 1 has an infinite supply, but it still requires at least 10 units to be sent.
Node 4 is a throughput node that can now handle an infinite amount of demand.
Node 8 has a flexible demand. It requires between 6 and 10 units.
You use the special missing values (
.I) to represent infinity and (
.M) to represent minus infinity. The adjusted node bounds can be represented by the following nodes data set:
data NodeSetIn; input node weight weight2; datalines; 1 10 .I 2 20 20 4 .M -5 7 -15 -15 8 -10 -6 ;
You can use the following call to PROC OPTNET to find a minimum-cost flow:
proc optnet loglevel = moderate graph_direction = directed data_links = LinkSetIn data_nodes = NodeSetIn out_links = LinkSetOut; mincostflow logfreq = 1; run; %put &_OROPTNET_; %put &_OROPTNET_MCF_;
The progress of the procedure is shown in Figure 2.39.
Figure 2.39: PROC OPTNET Log for Minimum-Cost Network Flow
NOTE: ------------------------------------------------------------------------------------------ |
NOTE: ------------------------------------------------------------------------------------------ |
NOTE: Running OPTNET version 13.2. |
NOTE: ------------------------------------------------------------------------------------------ |
NOTE: ------------------------------------------------------------------------------------------ |
NOTE: Reading the nodes data set. |
NOTE: There were 5 observations read from the data set WORK.NODESETIN. |
NOTE: Reading the links data set. |
NOTE: There were 11 observations read from the data set WORK.LINKSETIN. |
NOTE: Data input used 0.01 (cpu: 0.02) seconds. |
NOTE: Building the input graph storage used 0.00 (cpu: 0.00) seconds. |
NOTE: The input graph storage is using 0.0 MBs of memory. |
NOTE: The number of nodes in the input graph is 8. |
NOTE: The number of links in the input graph is 11. |
NOTE: ------------------------------------------------------------------------------------------ |
NOTE: ------------------------------------------------------------------------------------------ |
NOTE: Processing the minimum-cost network flow problem. |
NOTE: The network has 1 connected component. |
Primal Primal Dual |
Iteration Objective Infeasibility Infeasibility Time |
1 1.000000E+01 2.000000E+01 1.730000E+02 0.00 |
2 1.000000E+01 2.000000E+01 1.730000E+02 0.00 |
3 4.500000E+01 2.000000E+01 1.740000E+02 0.00 |
4 4.500000E+01 2.000000E+01 1.740000E+02 0.00 |
5 7.500000E+01 1.500000E+01 1.660000E+02 0.00 |
6 7.500000E+01 1.500000E+01 1.660000E+02 0.00 |
7 1.590000E+02 9.000000E+00 8.700000E+01 0.00 |
8 2.150000E+02 5.000000E+00 8.700000E+01 0.00 |
9 2.300000E+02 5.000000E+00 8.600000E+01 0.00 |
10 2.300000E+02 5.000000E+00 1.690000E+02 0.00 |
11 2.300000E+02 5.000000E+00 8.200000E+01 0.00 |
12 2.180000E+02 1.000000E+00 8.200000E+01 0.00 |
13 2.180000E+02 1.000000E+00 8.200000E+01 0.00 |
14 2.280000E+02 0.000000E+00 2.000000E+00 0.00 |
15 2.280000E+02 0.000000E+00 2.000000E+00 0.00 |
16 2.260000E+02 0.000000E+00 0.000000E+00 0.00 |
NOTE: The Network Simplex solve time is 0.00 seconds. |
NOTE: Objective = 226. |
NOTE: Processing the minimum-cost network flow problem used 0.00 (cpu: 0.00) seconds. |
NOTE: ------------------------------------------------------------------------------------------ |
NOTE: Creating links data set output. |
NOTE: Data output used 0.00 (cpu: 0.02) seconds. |
NOTE: ------------------------------------------------------------------------------------------ |
NOTE: ------------------------------------------------------------------------------------------ |
NOTE: The data set WORK.LINKSETOUT has 11 observations and 5 variables. |
STATUS=OK MCF=OPTIMAL |
STATUS=OPTIMAL OBJECTIVE=226 CPU_TIME=0.00 REAL_TIME=0.00 |
The optimal solution is displayed in Figure 2.40.
The optimal solution is represented graphically in Figure 2.41.