Reverse-delete algorithm

From Wikipedia, the free encyclopedia

The reverse-delete algorithm is an algorithm in graph theory used to obtain a minimum spanning tree from a given connected, edge-weighed graph. If the graph is disconnected, this algorithm will find a minimum spanning tree for each disconnected part of the graph. The set of these minimum spanning trees is called a minimum spanning forest, which consists of every vertex in the graph.

This algorithm is a greedy algorithm, choosing the best choice given any situation. It is the reverse of Kruskal's algorithm, which is another greedy algorithm to find a minimum spanning tree. Kruskal’s algorithm starts with an empty graph and adds edges while the Reverse-Delete algorithm starts with the original graph and deletes edges from it. The algorithm works as follows:

  • Start with graph G, which contains a list of edges E.
  • Go through E in decreasing order of edge weights.
  • Check if deleting current edge will further disconnect graph.
  • If G is not further disconnected, delete the edge.

Contents

[edit] Proof of correctness

The Reverse-Delete algorithm ensures connectivity in the graph or graph parts before deletion. Since the algorithm only deletes edges when it does not disconnect the graph, any edge removed by the algorithm at the time of deletion was in a cycle. Since the algorithm starts from the heaviest weighted edge and continues in decreasing order, the edge removed from any cycle is the maximum edge in that cycle. Therefore, according to the definition of a minimum spanning tree, the edges removed by the algorithm are not in any minimum spanning tree.

[edit] Pseudocode

 1  function ReverseDelete(edges[] E)
 2    sort E in decreasing order
 3    Define an index i ← 0
 4    while i < size(E)
 5       Define edge tempE[i]
 6      delete E[i]
 7      if temp.v1 is not connected to temp.v2
 8          E[i] ← temp
 9      ii + 1
 10   return edges[] E

In the above the graph is the set of edges E with each edge containing a weight and connected vertices v1 and v2.

[edit] Example

In the following example green edges are those being evaluated by the algorithm and red edges are those which have been deleted.

This is our original graph. The numbers near the edge indicate their edge weight.
The algorithm will start with the maximum weighted edge, which in this case is DE with an edge weight of 15. Since deleting edge DE does not further disconnect the graph it is deleted.
The next largest edge is FG so the algorithm will check if deleting this edge will further disconnect the graph. Since deleting the edge will not further disconnect the graph, the edge is then deleted.
The next largest edge is edge BD so the algorithm will check this edge and delete the edge.
The next edge to check is edge EG, which will not be deleted since it would disconnect node G from the graph. Therefore, the next edge to delete is edge BC.
The next largest edge is edge EF so the algorithm will check this edge and delete the edge.
The algorithm will then search the remaining edges and will not find another edge to delete; therefore this is the final graph returned by the algorithm.

[edit] Running time

The algorithm can be shown to run in O(E log E (log log E)3) time, where E is the number of edges and V is the number of vertices. This bound is achieved as follows:

  • sorting the edges by weight using a comparison sort in O(E log E) time
  • E iterations of loop
  • deleting in O(1) time
  • connectivity checked in O(logV (log log V)3) time (Thorup 2000).

Equally, the running time can be considered O(E log V (log log V)3) because the largest E can be is V2. Remember that logV2 = 2 * logV, so 2 is a multiplicative constant that will be ignored in big-O notation.

[edit] See also

[edit] References