# Flow network

In graph theory, a **flow network** (also known as a **transportation network**) is a directed graph where each edge has a **capacity** and each edge receives a flow. The amount of flow on an edge cannot exceed the capacity of the edge. Often in Operations Research, a directed graph is called a **network**. The vertices are called **nodes** and the edges are called **arcs**. A flow must satisfy the restriction that the amount of flow into a node equals the amount of flow out of it, unless it is a **source**, which has only outgoing flow, or **sink**, which has only incoming flow. A network can be used to model traffic in a road system, circulation with demands, fluids in pipes, currents in an electrical circuit, or anything similar in which something travels through a network of nodes.

## Contents

## Definition

Let be a finite directed graph in which every edge has a non-negative, real-valued capacity . If , we assume that . We distinguish two vertices: a source and a sink . A flow in a flow network is a real function with the following three properties for all nodes and :

**Capacity constraints**:. The flow along an edge cannot exceed its capacity. **Skew symmetry**:. The net flow from to must be the opposite of the net flow from to (see example). **Flow conservation**:, unless or . The net flow to a node is zero, except for the source, which "produces" flow, and the sink, which "consumes" flow.

i.e. ** Flow conservation** implies: , for each vertex

Notice that is the *net* flow from to . If the graph represents a physical network, and if there is a real flow of, for example, 4 units from to , and a real flow of 3 units from to , we have and .

Basically we can say that flow for a physical network is flow leaving at s =

The **residual capacity** of an edge is . This defines a **residual network** denoted , giving the amount of *available* capacity. See that there can be a path from to in the residual network, even though there is no path from to in the original network. Since flows in opposite directions cancel out, *decreasing* the flow from to is the same as *increasing* the flow from to . An **augmenting path** is a path in the residual network, where , , and . A network is at maximum flow if and only if there is no augmenting path in the residual network .

So is constructed using graph G as follows:

1. Vertices of =

2. Edges of = defined as-

For each edge

(i). If make Forward edge withcapacity. (ii). If make Backward edge withcapacity.

This concept is used in Ford–Fulkerson algorithm which computes the maximum flow in a flow network.

Sometimes one needs to model a network with more than one source, a **supersource** is introduced to the graph.^{[1]} This consists of a vertex connected to each of the sources with edges of infinite capacity, so as to act as a global source. A similar construct for sinks is called a **supersink**.^{[2]}

## Example

To the right you see a flow network with source labeled , sink , and four additional nodes. The flow and capacity is denoted . Notice how the network upholds skew symmetry, capacity constraints and flow conservation. The total amount of flow from to is 5, which can be easily seen from the fact that the total outgoing flow from is 5, which is also the incoming flow to . We know that no flow appears or disappears in any of the other nodes.

Below you see the residual network for the given flow. Notice how there is positive residual capacity on some edges where the original capacity is zero, for example for the edge . This flow is not a maximum flow. There is available capacity along the paths , and , which are then the augmenting paths. The residual capacity of the first path is . Notice that as long as there exists some path with a positive residual capacity, the flow will not be maximum. The residual capacity for some path is the minimum residual capacity of all edges in that path.

## Applications

{{#invoke:see also|seealso}}

Picture a series of water pipes, fitting into a network. Each pipe is of a certain diameter, so it can only maintain a flow of a certain amount of water. Anywhere that pipes meet, the total amount of water coming into that junction must be equal to the amount going out, otherwise we would quickly run out of water, or we would have a buildup of water. We have a water inlet, which is the source, and an outlet, the sink. A flow would then be one possible way for water to get from source to sink so that the total amount of water coming out of the outlet is consistent. Intuitively, the total flow of a network is the rate at which water comes out of the outlet.

Flows can pertain to people or material over transportation networks, or to electricity over electrical distribution systems. For any such physical network, the flow coming into any intermediate node needs to equal the flow going out of that node. This conservation constraint was formalized as Kirchhoff's current law.

Flow networks also find applications in ecology: flow networks arise naturally when considering the flow of nutrients and energy between different organizations in a food web. The mathematical problems associated with such networks are quite different from those that arise in networks of fluid or traffic flow. The field of ecosystem network analysis, developed by Robert Ulanowicz and others, involves using concepts from information theory and thermodynamics to study the evolution of these networks over time.

The simplest and most common problem using flow networks is to find what is called the maximum flow, which provides the largest possible total flow from the source to the sink in a given graph. There are many other problems which can be solved using max flow algorithms, if they are appropriately modeled as flow networks, such as bipartite matching, the assignment problem and the transportation problem. Maximum flow problems can be solved efficiently with the Relabel-to-front algorithm. The max-flow min-cut theorem states that finding a maximal network flow is equivalent to finding a cut of minimum capacity that separates the source and the sink.

In a multi-commodity flow problem, you have multiple sources and sinks, and various "commodities" which are to flow from a given source to a given sink. This could be for example various goods that are produced at various factories, and are to be delivered to various given customers through the *same* transportation network.

In a minimum cost flow problem, each edge has a given cost , and the cost of sending the flow across the edge is . The objective is to send a given amount of flow from the source to the sink, at the lowest possible price.

In a circulation problem, you have a lower bound on the edges, in addition to the upper bound . Each edge also has a cost. Often, flow conservation holds for *all* nodes in a circulation problem, and there is a connection from the sink back to the source. In this way, you can dictate the total flow with and . The flow *circulates* through the network, hence the name of the problem.

In a **network with gains** or **generalized network** each edge has a **gain**, a real number (not zero) such that, if the edge has gain *g*, and an amount *x* flows into the edge at its tail, then an amount *gx* flows out at the head.

In a **source localization problem**, an algorithm tries to identify the most likely source node of information diffusion through a partially observed network. This can be done in linear time for trees and cubic time for arbitrary networks and has applications ranging from tracking mobile phone users to identifying the originating village of disease outbreaks.^{[3]}

## See also

- Centrality
- Constructal theory
- Ford–Fulkerson algorithm
- Dinic's algorithm
- Flow (computer networking)
- Flow graph
- Max-flow min-cut theorem
- Oriented matroid
- Shortest path problem

## References

- ↑ Paul E. Black, Supersource at the NIST Dictionary of Algorithms and Data Structures.
- ↑ Paul E. Black, Supersink at the NIST Dictionary of Algorithms and Data Structures.
- ↑ http://www.pedropinto.org.s3.amazonaws.com/publications/locating_source_diffusion_networks.pdf

## Further reading

- {{#invoke:citation/CS1|citation

|CitationClass=book }}

- {{#invoke:citation/CS1|citation

|CitationClass=book }}

- {{#invoke:citation/CS1|citation

|CitationClass=book }}

- {{#invoke:citation/CS1|citation

|CitationClass=book }}

- {{#invoke:citation/CS1|citation

|CitationClass=book }}

- {{#invoke:citation/CS1|citation

|CitationClass=book }}

- {{#invoke:citation/CS1|citation

|CitationClass=book }}

## External links

- Maximum Flow Problem
- Maximum Flow
- Real graph instances
- Template:Dead link Software, papers, test graphs, etc.
- Template:Dead link[Software and papers for network flow problems
- Lemon C++ library with several maximum flow and minimum cost circulation algorithms
- QuickGraph, graph data structures and algorithms for .Net