# Floyd–Warshall algorithm

{{#invoke:Hatnote|hatnote}}Template:Main other Template:Infobox Algorithm

Template:Tree search algorithm
In computer science, the **Floyd–Warshall algorithm** (also known as **Floyd's algorithm**, **Roy–Warshall algorithm**, **Roy–Floyd algorithm**, or the **WFI algorithm**) is a graph analysis algorithm for finding shortest paths in a weighted graph with positive or negative edge weights (but with no negative cycles, see below) and also for finding transitive closure of a relation . A single execution of the algorithm will find the lengths (summed weights) of the shortest paths between *all* pairs of vertices, though it does not return details of the paths themselves.

The Floyd–Warshall algorithm was published in its currently recognized form by Robert Floyd in 1962. However, it is essentially the same as algorithms previously published by Bernard Roy in 1959 and also by Stephen Warshall in 1962 for finding the transitive closure of a graph.^{[1]} The modern formulation of Warshall's algorithm as three nested for-loops was first described by Peter Ingerman, also in 1962.

The algorithm is an example of dynamic programming.

## Algorithm

The Floyd–Warshall algorithm compares all possible paths through the graph between each pair of vertices. It is able to do this with Θ(|*V* |^{3}) comparisons in a graph. This is remarkable considering that there may be up to Ω(|*V* |^{2}) edges in the graph, and every combination of edges is tested. It does so by incrementally improving an estimate on the shortest path between two vertices, until the estimate is optimal.

Consider a graph *G* with vertices *V* numbered 1 through *N*. Further consider a function shortestPath(*i*, *j*, *k*) that returns the shortest possible path from *i* to *j* using vertices only from the set {1,2,...,*k*} as intermediate points along the way. Now, given this function, our goal is to find the shortest path from each *i* to each *j* using only vertices 1 to *k* + 1.

For each of these pairs of vertices, the true shortest path could be either (1) a path that only uses vertices in the set {1, ..., *k*} or (2) a path that goes from *i* to *k* + 1 and then from *k* + 1 to *j*. We know that the best path from *i* to *j* that only uses vertices 1 through *k* is defined by shortestPath(*i*, *j*, *k*), and it is clear that if there were a better path from *i* to *k* + 1 to *j*, then the length of this path would be the concatenation of the shortest path from *i* to *k* + 1 (using vertices in {1, ..., *k*}) and the shortest path from *k* + 1 to *j* (also using vertices in {1, ..., *k*}).

If is the weight of the edge between vertices *i* and *j*, we can define shortestPath(*i*, *j*, *k* + 1) in terms of the following recursive formula: the base case is

and the recursive case is

This formula is the heart of the Floyd–Warshall algorithm. The algorithm works by first computing shortestPath(*i*, *j*, *k*) for all (*i*, *j*) pairs for *k* = 1, then *k* = 2, etc. This process continues until *k* = *n*, and we have found the shortest path for all (*i*, *j*) pairs using any intermediate vertices. Pseudocode for this basic version follows:

1letdist be a |V| × |V| array of minimum distances initialized to ∞ (infinity) 2for eachvertexv3 dist[v][v] ← 0 4for eachedge (u,v) 5 dist[u][v] ← w(u,v)// the weight of the edge (u,v)6forkfrom1to|V| 7forifrom1to|V| 8forjfrom1to|V| 9ifdist[i][j] > dist[i][k] + dist[k][j] 10 dist[i][j] ← dist[i][k] + dist[k][j] 11end if

## Example

The algorithm above is executed on the graph on the left below:

Prior to the first iteration of the outer loop, labeled *k*=0 above, the only known paths correspond to the single edges in the graph. At k=1, paths that go through the vertex 1 are found: in particular, the path 2→1→3 is found, replacing the path 2→3 which has fewer edges but is longer. At k=2, paths going through the vertices {1,2} are found. The red and blue boxes show how the path 4→2→1→3 is assembled from the two known paths 4→2 and 2→1→3 encountered in previous iterations, with 2 in the intersection. The path 4→2→3 is not considered, because 2→1→3 is the shortest path encountered so far from 2 to 3. At k=3, paths going through the vertices {1,2,3} are found. Finally, at k=4, all shortest paths are found.

## Behavior with negative cycles

A negative cycle is a cycle whose edges sum to a negative value. There is no shortest path between any pair of vertices i, j which form part of a negative cycle, because path-lengths from i to j can be arbitrarily small (negative). For numerically meaningful output, the Floyd–Warshall algorithm assumes that there are no negative cycles. Nevertheless, if there are negative cycles, the Floyd–Warshall algorithm can be used to detect them. The intuition is as follows:

- The Floyd–Warshall algorithm iteratively revises path lengths between all pairs of vertices (
*i*,*j*), including where*i*=*j*; - Initially, the length of the path (
*i*,*i*) is zero; - A path {(
*i*,*k*), (*k*,*i*)} can only improve upon this if it has length less than zero, i.e. denotes a negative cycle; - Thus, after the algorithm, (
*i*,*i*) will be negative if there exists a negative-length path from*i*back to*i*.

Hence, to detect negative cycles using the Floyd–Warshall algorithm, one can inspect the diagonal of the path matrix, and the presence of a negative number indicates that the graph contains at least one negative cycle.^{[2]} To avoid numerical problems one should check for negative numbers on the diagonal of the path matrix within the inner for loop of the algorithm.^{[3]} Obviously, in an undirected graph a negative edge creates a negative cycle (i.e., a closed walk) involving its incident vertices. Considering all edges of the above example graph as undirected, e.g. the vertice sequence 4 - 2 - 4 is a cycle with weight sum -2.

## Path reconstruction

The Floyd–Warshall algorithm typically only provides the lengths of the paths between all pairs of vertices. With simple modifications, it is possible to create a method to reconstruct the actual path between any two endpoint vertices. While one may be inclined to store the actual path from each vertex to each other vertex, this is not necessary, and in fact, is very costly in terms of memory. Instead, the Shortest-path tree can be calculated for each node in Θ(|*E*|) time using Θ(|*V*|) memory to store each tree which allows us to efficiently reconstruct a path from any two connected vertices.

letdist be a |V| × |V| array of minimum distances initialized to ∞ (infinity)letnext be a |V| × |V| array of vertex indices initialized tonullprocedureFloydWarshallWithPathReconstruction()for eachedge (u,v) dist[u][v] ← w(u,v)// the weight of the edge (u,v)next[u][v] ← vforkfrom1to|V|// standard Floyd-Warshall implementationforifrom1to|V|forjfrom1to|V|ifdist[i][k] + dist[k][j] < dist[i][j]thendist[i][j] ← dist[i][k] + dist[k][j] next[i][j] ← next[i][k]procedurePath(u, v)ifnext[u][v] = nullthenreturn[] path = [u]while u ≠ vu ← next[u][v] path.append(u)returnpath

## Analysis

Let *n* be |V|, the number of vertices. To find all *n*^{2} of shortestPath(*i*,*j*,*k*) (for all *i* and *j*) from those of shortestPath(*i*,*j*,*k*−1) requires 2*n*^{2} operations. Since we begin with shortestPath(*i*,*j*,0) = edgeCost(*i*,*j*) and compute the sequence of *n* matrices shortestPath(*i*,*j*,1), shortestPath(*i*,*j*,2), …, shortestPath(*i*,*j*,*n*), the total number of operations used is *n* · 2*n*^{2} = 2*n*^{3}. Therefore, the complexity of the algorithm is Θ(*n*^{3}).

## Applications and generalizations

The Floyd–Warshall algorithm can be used to solve the following problems, among others:

- Shortest paths in directed graphs (Floyd's algorithm).
- Transitive closure of directed graphs (Warshall's algorithm). In Warshall's original formulation of the algorithm, the graph is unweighted and represented by a Boolean adjacency matrix. Then the addition operation is replaced by logical conjunction (AND) and the minimum operation by logical disjunction (OR).
- Finding a regular expression denoting the regular language accepted by a finite automaton (Kleene's algorithm, a closely related generalization of the Floyd–Warshall algorithm)
^{[4]} - Inversion of real matrices (Gauss–Jordan algorithm)
^{[5]} - Optimal routing. In this application one is interested in finding the path with the maximum flow between two vertices. This means that, rather than taking minima as in the pseudocode above, one instead takes maxima. The edge weights represent fixed constraints on flow. Path weights represent bottlenecks; so the addition operation above is replaced by the minimum operation.
- Fast computation of Pathfinder networks.
- Widest paths/Maximum bandwidth paths
- Computing canonical form of difference bound matrices (DBMs)

## Implementations

Implementations are available for many programming languages.

- For C++, in the boost::graph library
- For C#, at QuickGraph
- For Java, in the Apache Commons Graph library
- For MATLAB, in the Matlab_bgl package
- For Perl, in the Graph module
- For Python, in the NetworkX library
- For R, in package e1071

## See also

- Dijkstra's algorithm, an algorithm for finding single-source shortest paths in a more restrictive class of inputs, graphs in which all edge weights are non-negative
- Johnson's algorithm, an algorithm for solving the same problem as the Floyd–Warshall algorithm, all pairs shortest paths in graphs with some edge weights negative. Compared to the Floyd–Warshall algorithm, Johnson's algorithm is more efficient for sparse graphs.

## References

- ↑ Template:Cite web
- ↑ Template:Cite web
- ↑ {{#invoke:Citation/CS1|citation |CitationClass=journal }}
- ↑ {{#invoke:citation/CS1|citation |CitationClass=citation }}.
- ↑ Template:Cite web

- Template:Introduction to Algorithms
- Section 26.2, "The Floyd–Warshall algorithm", pp. 558–565;
- Section 26.4, "A general framework for solving path problems in directed graphs", pp. 570–576.

- {{#invoke:Citation/CS1|citation

|CitationClass=journal }}

- {{#invoke:Citation/CS1|citation

|CitationClass=journal }}

- {{#invoke:citation/CS1|citation

|CitationClass=book }}

- {{#invoke:Citation/CS1|citation

|CitationClass=journal }}

- {{#invoke:citation/CS1|citation

|CitationClass=book }}

- {{#invoke:Citation/CS1|citation

|CitationClass=journal }}