7    VisuAlgo.net / /matching Login  A Matching in a graph G = (V, E) is a subset M of E edges in G such that no two of which meet at a common vertex.

Maximum Cardinality Matching (MCM) problem is a Graph Matching problem where we seek a matching M that contains the largest possible number of edges. A possible variant is Perfect Matching where all V vertices are matched, i.e. the cardinality of M is V/2.

A Bipartite Graph is a graph whose vertices can be partitioned into two disjoint sets X and Y such that every edge can only connect a vertex in X to a vertex in Y.

Maximum Cardinality Bipartite Matching (MCBM) problem is the MCM problem in a Bipartite Graph, which is a lot easier than MCM problem in a General Graph.

Remarks: By default, we show e-Lecture Mode for first time (or non logged-in) visitor.
Please login if you are a repeated visitor or register for an (optional) free account first.

X Esc

This visualization is currently limited to unweighted graphs only. Thus, we currently do not support Graph Matching problem variants involving weighted graphs...

Pro-tip: Since you are not logged-in, you may be a first time visitor who are not aware of the following keyboard shortcuts to navigate this e-Lecture mode: [PageDown] to advance to the next slide, [PageUp] to go back to the previous slide, [Esc] to toggle between this e-Lecture mode and exploration mode.

X Esc

To switch between the unweighted MCBM (default, as it is much more popular) and unweighted MCM mode, click the respective header.

Here is an example of MCM mode. In MCM mode, one can draw a General, not necessarily Bipartite graphs. However, the graphs are unweighted (all edges have uniform weight 1).

The available algorithms are different in the two modes.

Another pro-tip: We designed this visualization and this e-Lecture mode to look good on 1366x768 resolution or larger (typical modern laptop resolution in 2017). We recommend using Google Chrome to access VisuAlgo. Go to full screen mode (F11) to enjoy this setup. However, you can use zoom-in (Ctrl +) or zoom-out (Ctrl -) to calibrate this.

X Esc

You can view the visualisation here!

For Bipartite Graph visualization, we will re-layout the vertices of the graph so that the two disjoint sets are clearly visible as Left and Right sets. For General Graph, we do not relayout the vertices.

Initially, edges have grey color. Matched edges will have black color. Free/Matched edges along an augmenting path will have Orange/Light Blue colors, respectively.

X Esc

There are three different sources for specifying an input graph:

1. Draw Graph: You can draw any undirected unweighted graph as the input graph (note that in MCBM mode, the drawn input graph will be relayout into a nice Bipartite graph layout during algorithm animation),
2. Modeling: A lot of graph problems can be reduced into an MCBM problem. In this visualization, we have the modeling examples for the famous Rook Attack problem (currently disabled) and standard MCBM problem (also valid in MCM mode).
3. Examples: You can select from the list of our example graphs to get you started. The list of examples are slightly different in the two MCBM vs MCM modes.
X Esc

There are several Max Cardinality Bipartite Matching (MCBM) algorithms in this visualization, plus one more in Max Flow visualization:

1. O(VE) Augmenting Path Algorithm (without greedy pre-processing),
2. O(√(V)E) Dinic's Max Flow Algorithm, see Max Flow visualization, select Modeling → Bipartite Matching → All 1, then use Dinic's algorithm.
3. O(√(V)E) Hopcroft Karp's Algorithm,
4. O(kE) Augmenting Path Algorithm++ (with randomized greedy pre-processing),

PS: Although possible, we will likely not use O(V3) Edmonds's Matching Algorithm if the input is guaranteed to be a Bipartite Graph.

X Esc

Augmenting Path is a path that starts from a free (unmatched) vertex u in graph G, alternates through unmatched, match, ..., unmatched edges in G, until it ends at another free vertex v. If we flip the edge status along that augmenting path, we will increase the number of edges in the matching set M by 1 and eliminates this augmenting path.

In 1957, Claude Berge proposes the following lemma: A matching M in graph G is maximum iff there is no more augmenting path in G.

The Augmenting Path Algorithm is a simple O(V*(V+E)) = O(V2 + VE) = O(VE) implementation of that lemma (on Bipartite Graph): Find and then eliminate augmenting paths in Bipartite Graph G. Click Augmenting Path Algorithm Demo to visualize this algorithm on the currently displayed random Bipartite Graph.

X Esc

`vi match, vis; // global variablesint Aug(int L) { // return 1 if ∃ an augmenting path from L  if (vis[L]) return 0; // return 0 otherwise  vis[L] = 1;  for (auto &v : AL[L]) {    int R = v.first;    if (match[R] == -1 || Aug(match[R])) {      match[R] = L;      return 1; // found 1 matching  } }  return 0; // no matching}`
X Esc

`// in int main(), build the bipartite graph// use directed edges from left set (of size VLeft) to right set  int MCBM = 0;  match.assign(V, -1);  for (int L = 0; L < VLeft; L++) {    vis.assign(VLeft, 0);    MCBM += Aug(L); // find augmenting path starting from L  }  printf("Found %d matchings\n", MCBM);`

You can also download ch4_09_mcbm.cpp/java from Competitive Programming 3 companion website.

X Esc

If we are given a Complete Bipartite Graph KN/2,N/2, i.e.
V = N/2+N/2 = N and E = N/2×N/2 = N2/4 ≈ N2, then
the Augmenting Path Algorithm discussed earlier will run in O(VE) = O(N×N2) = O(N3).

This is only OK for V ∈ [400..500].

Try executing the standard Augmenting Path Algorithm on this Extreme Test Case, which is an almost complete K5,5 Bipartite Graph.

X Esc

The MCBM problem can be modeled as a Max Flow problem. Go to Max Flow visualization page and see the flow graph modeling of MCBM problem (select Modeling → Bipartite Matching → all 1).

If we use one of the fastest Max Flow algorithm, i.e. Dinic's algorithm on this flow graph, we can find Max Flow = MCBM in O(√(V)E) time — analysis omitted for now. This allows us to solve MCBM problem with V ∈ [1 000..1 500].

X Esc

The key idea of Hopcroft Karp's (HK) Algorithm (invented in 1973) is identical to Dinic's Max Flow Algorithm discussed earlier, i.e. prioritize shortest augmenting paths (in terms of number of edges used) first. That's it, augmenting paths with 1 edge are processed first before longer augmenting paths with 3 edges, 5 edges, 7 edges, etc (the length always increase by 2 due to the nature of augmenting path in a Bipartite Graph).

Hopcroft Karp's Algorithm has time complexity of O(√(V)E) — analysis omitted for now. This allows us to solve MCBM problem with V ∈ [1 000..1 500].

Try HK Algorithm on the same Extreme Test Case earlier. You will notice that HK Algorithm can find the MCBM in a much faster time than the previous standard O(VE) Augmenting Path Algorithm.

X Esc

However, we can actually make the easy-to-code Augmenting Path Algorithm discussed earlier to avoid its worst case O(VE) behavior by doing O(V+E) randomized (to avoid adversary test case) greedy pre-processing before running the actual algorithm.

This O(V+E) additional pre-processing step is simple: For every vertex on the left set, match it with a randomly chosen unmatched neighbouring vertex on the right set. This way, we eliminates many trivial (one-edge) Augmenting Paths that consist of a free vertex u, an unmatched edge (u, v), and a free vertex v.

Try Augmenting Path Algorithm++ on the same Extreme Test Case earlier. Notice that the pre-processing step already eliminates many trivial 1-edge augmenting paths, making the actual Augmenting Path Algorithm only need to do little amount of additional work.

X Esc

Quite often, on randomly generated Bipartite Graph, the randomized greedy pre-processing step has cleared most of the matchings.

However, we can construct test case like: Examples: Randomized Greedy Processing Killer to make randomization as ineffective as possible. For every group of 4 vertices, there are 2 matchings. Random greedy processing has 50% chance of making mistake per group. Try this Hard Test Case case to see for yourself.

The worst case time complexity is no longer O(VE) but now O(kE) where k is a small integer, much smaller than V, k can be as small as 0 and is at most V/2. In our experiments, we estimate k to be "about √(V)" too. This version of Augmenting Path Algorithm++ allows us to solve MCBM problem with V ∈ [1 000..1 500] too.

X Esc

There are two Max Cardinality Matching (MCM) algorithms in this visualization:

1. O(V^3) Edmonds's Matching algorithm (without greedy pre-processing),
2. O(V^3) Edmonds's Matching algorithm (with greedy pre-processing),
X Esc

In General Graph, we may have Odd-Length cycle. Augmenting Path is not well defined in such graph, hence we cannot directly implement Claude Berge's lemma like what we did with Bipartite Graph.

Jack Edmonds call a path that starts from a free vertex u, alternates between free, matched, ..., free edges, and returns to the same free vertex u as Blossom. This situation is only possible if we have Odd-Length cycle, i.e. non-Bipartite Graph. Edmonds then proposed Blossom shrinking/contraction and expansion algorithm to solve this issue, details verbally.

This algorithm can be implemented in O(V^3).

X Esc

As with the Augmenting Path Algorithm++ for the MCBM problem, we can also do randomized greedy pre-processing step to eliminate as many 'trivial matchings' as possible upfront. This reduces the amount of work of Edmonds's Matching Algorithm, thus resulting in a faster time complexity — analysis TBA.

X Esc

We have not added visualizations for weighted variant of MCBM and MCM problems (future work).

X Esc

X Esc

e-Lecture: The content of this slide is hidden and only available for legitimate CS lecturer worldwide. Drop an email to visualgo.info at gmail dot com if you want to activate this CS lecturer-only feature and you are really a CS lecturer (show your University staff profile).

X Esc

-／+：减缓／增加速度

X Esc

Return to 'Exploration Mode' to start exploring!

Note that if you notice any bug in this visualization or if you want to request for a new visualization feature, do not hesitate to drop an email to the project leader: Dr Steven Halim via his email address: stevenhalim at gmail dot com.

X Esc

Examples Rook Attack

GO

Generate Random Bipartite Graph

Undirected Max Flow Killer

House of Cards

CS4234 Tutorial 3

F-mod

Randomized Greedy Processing Killer

K5,5

K5,5 (Almost)

Hopcroft Karp

Edmonds Blossom

Edmonds Blossom + Greedy

#### 关于

VisuAlgo在2011年由Steven Halim博士概念化，作为一个工具，帮助他的学生更好地理解数据结构和算法，让他们自己和自己的步伐学习基础。
VisuAlgo包含许多高级算法，这些算法在Steven Halim博士的书（“竞争规划”，与他的兄弟Felix Halim博士合作）和其他书中讨论。今天，一些高级算法的可视化/动画只能在VisuAlgo中找到。

VisuAlgo不是从一开始就设计为在小触摸屏（例如智能手机）上工作良好，因为需要满足许多复杂的算法可视化，需要大量的像素和点击并拖动手势进行交互。一个令人尊敬的用户体验的最低屏幕分辨率为1024x768，并且只有着陆页相对适合移动设备。
VisuAlgo是一个正在进行的项目，更复杂的可视化仍在开发中。

zh, id, kr, vn, th.

#### 团队

Dr Steven Halim, Senior Lecturer, School of Computing (SoC), National University of Singapore (NUS)
Dr Felix Halim, Software Engineer, Google (Mountain View)

Koh Zi Chun, Victor Loh Bo Huai

Phan Thi Quynh Trang, Peter Phandi, Albert Millardo Tjindradinata, Nguyen Hoang Duy

Rose Marie Tan Zhao Yun, Ivan Reinaldo

Jonathan Irvin Gunawan, Nathan Azaria, Ian Leow Tze Wei, Nguyen Viet Dung, Nguyen Khac Tung, Steven Kester Yuwono, Cao Shengze, Mohan Jishnu

Erin Teo Yi Ling, Wang Zi

Truong Ngoc Khanh, John Kevin Tjahjadi, Gabriella Michelle, Muhammad Rais Fathin Mudzakir

List of translators who have contributed ≥100 translations can be found at statistics page.