Baseball Elimination - Princeton Part II Programming Assignment 3


http://coursera.cs.princeton.edu/algs4/assignments/baseball.html
The baseball elimination problem.   In the baseball elimination problem, there is a division consisting of N teams. At some point during the season, team i has w[i] wins, l[i] losses, r[i] remaining games, and g[i][j]games left to play against team j. A team is mathematically eliminated if it cannot possibly finish the season in (or tied for) first place. The goal is to determine exactly which teams are mathematically eliminated. For simplicity, we assume that no games end in a tie (as is the case in Major League Baseball) and that there are no rainouts (i.e., every scheduled game is played).
The problem is not as easy as many sports writers would have you believe, in part because the answer depends not only on the number of games won and left to play, but also on the schedule of remaining games. To see the complication, consider the following scenario:

 
                w[i] l[i] r[i]        g[i][j]
i  team         wins loss left   Atl Phi NY  Mon
------------------------------------------------
0  Atlanta       83   71    8     -   1   6   1
1  Philadelphia  80   79    3     1   -   0   2
2  New York      78   78    6     6   0   -   0
3  Montreal      77   82    3     1   2   0   -
Montreal is mathematically eliminated since it can finish with at most 80 wins and Atlanta already has 83 wins. This is the simplest reason for elimination. However, there can be more complicated reasons. For example, Philadelphia is also mathematically eliminated. It can finish the season with as many as 83 wins, which appears to be enough to tie Atlanta. But this would require Atlanta to lose all of its remaining games, including the 6 against New York, in which case New York would finish with 84 wins. We note that New York is not yet mathematically eliminated despite the fact that it has fewer wins than Philadelphia.
It is sometimes not so easy for a sports writer to explain why a particular team is mathematically eliminated. Consider the following scenario from the American League East on August 30, 1996:

                w[i] l[i] r[i]          g[i][j]
i  team         wins loss left   NY Bal Bos Tor Det
---------------------------------------------------
0  New York      75   59   28     -   3   8   7   3
1  Baltimore     71   63   28     3   -   2   7   7
2  Boston        69   66   27     8   2   -   0   3
3  Toronto       63   72   27     7   7   0   -   3
4  Detroit       49   86   27     3   7   3   3   -
It might appear that Detroit has a remote chance of catching New York and winning the division because Detroit can finish with as many as 76 wins if they go on a 27-game winning steak, which is one more than New York would have if they go on a 28-game losing streak. Try to convince yourself that Detroit is already mathematically eliminated. Here's one ad hoc explanation; we will present a simpler explanation below.
A maxflow formulation.   We now solve the baseball elimination problem by reducing it to the maxflow problem. To check whether team x is eliminated, we consider two cases.

  • Trivial elimination. If the maximum number of games team x can win is less than the number of wins of some other team i, then team x is trivially eliminated (as is Montreal in the example above). That is, if w[x] +r[x] < w[i], then team x is mathematically eliminated.
  • Nontrivial elimination. Otherwise, we create a flow network and solve a maxflow problem in it. In the network, feasible integral flows correspond to outcomes of the remaining schedule. There are vertices corresponding to teams (other than team x) and to remaining divisional games (not involving team x). Intuitively, each unit of flow in the network corresponds to a remaining game. As it flows through the network from s to t, it passes from a game vertex, say between teams i and j, then through one of the team vertices i or j, classifying this game as being won by that team.More precisely, the flow network includes the following edges and capacities.

    • We connect an artificial source vertex s to each game vertex i-j and set its capacity to g[i][j]. If a flow uses all g[i][j] units of capacity on this edge, then we interpret this as playing all of these games, with the wins distributed between the team vertices i and j.
    • We connect each game vertex i-j with the two opposing team vertices to ensure that one of the two teams earns a win. We do not need to restrict the amount of flow on such edges.
    • Finally, we connect each team vertex to an artificial sink vertex t. We want to know if there is some way of completing all the games so that team x ends up winning at least as many games as team i. Since teamx can win as many as w[x] + r[x] games, we prevent team i from winning more than that many games in total, by including an edge from team vertex i to the sink vertex with capacity w[x] + r[x] - w[i].
    If all edges in the maxflow that are pointing from s are full, then this corresponds to assigning winners to all of the remaining games in such a way that no team wins more games than x. If some edges pointing from sare not full, then there is no scenario in which team x can win the division. In the flow network below Detroit is team x = 4.
    What the min cut tells us.   By solving a maxflow problem, we can determine whether a given team is mathematically eliminated. We would also like to explain the reason for the team's elimination to a friend in nontechnical terms (using only grade-school arithmetic). Here's such an explanation for Detroit's elimination in the American League East example above. With the best possible luck, Detroit finishes the season with 49 + 27 = 76 wins. Consider the subset of teams R = { New York, Baltimore, Boston, Toronto }. Collectively, they already have 75 + 71 + 69 + 63 = 278 wins; there are also 3 + 8 + 7 + 2 + 7 = 27 remaining games among them, so these four teams must win at least an additional 27 games. Thus, on average, the teams in R win at least 305 / 4 = 76.25 games. Regardless of the outcome, one team in R will win at least 77 games, thereby eliminating Detroit.
In fact, when a team is mathematically eliminated there always exists such a convincing certificate of elimination, where R is some subset of the other teams in the division. Moreover, you can always find such a subset Rby choosing the team vertices on the source side of a min s-t cut in the baseball elimination network. Note that although we solved a maxflow/mincut problem to find the subset R, once we have it, the argument for a team's elimination involves only grade-school algebra.
Your assignment.   Write an immutable data type BaseballElimination that represents a sports division and determines which teams are mathematically eliminated by implementing the following API:
public BaseballElimination(String filename)                    // create a baseball division from given filename in format specified below
public              int numberOfTeams()                        // number of teams
public Iterable<String> teams()                                // all teams
public              int wins(String team)                      // number of wins for given team
public              int losses(String team)                    // number of losses for given team
public              int remaining(String team)                 // number of remaining games for given team
public              int against(String team1, String team2)    // number of remaining games between team1 and team2
public          boolean isEliminated(String team)              // is given team eliminated?
public Iterable<String> certificateOfElimination(String team)  // subset R of teams that eliminates given team; null if not eliminated
https://github.com/zhichaoh/Coursera-Algorithms/blob/master/src/BaseballElimination.java
public class BaseballElimination {

private int[] w;

private int[] l;

private int[] r;

private int[][] g;

private Map<String, Integer> teamNames;

private String[] nameList;

private int numTeams;

public BaseballElimination(String filename) throws Exception {
// create a baseball division from given filename in format specified
// below
Scanner input = new Scanner(new File(filename));
numTeams = input.nextInt();
this.w = new int[numTeams];
this.l = new int[numTeams];
this.r = new int[numTeams];
this.g = new int[numTeams][numTeams];
this.nameList = new String[numTeams];
this.teamNames = new HashMap<String, Integer>();
for (int n = 0; n < numTeams; n++) {
String name = input.next();
teamNames.put(name, n);
w[n] = input.nextInt();
l[n] = input.nextInt();
r[n] = input.nextInt();
for (int m = 0; m < numTeams; m++)
g[n][m] = input.nextInt();
nameList[n] = name;
}
input.close();
}

public int numberOfTeams() {
return this.numTeams;
}

public Iterable<String> teams() {
// all teams
return teamNames.keySet();
}

public int wins(String team) {
// number of wins for given team
if (!teamNames.containsKey(team))
throw new java.lang.IllegalArgumentException();
return w[teamNames.get(team)];
}

public int losses(String team) {
// number of losses for given team
if (!teamNames.containsKey(team))
throw new java.lang.IllegalArgumentException();
return l[teamNames.get(team)];
}

public int remaining(String team) {
// number of remaining games for given team
if (!teamNames.containsKey(team))
throw new java.lang.IllegalArgumentException();
return r[teamNames.get(team)];
}

public int against(String team1, String team2) {
// number of remaining games between team1 and team2
if (!teamNames.containsKey(team1) || !teamNames.containsKey(team2))
throw new java.lang.IllegalArgumentException();
int a = teamNames.get(team1);
int b = teamNames.get(team2);
return g[a][b];
}

public boolean isEliminated(String team) {
// is given team eliminated?
if (!teamNames.containsKey(team))
throw new java.lang.IllegalArgumentException();
int x = teamNames.get(team);

for (int i = 0; i < this.numTeams; i++) {
if (w[x] + r[x] - w[i] < 0)
return true;
}

int numMatches = this.numTeams * (this.numTeams - 1) / 2;
int nodeID = 0;

FlowNetwork fn = new FlowNetwork(numMatches + numTeams + 2);
int s = numMatches + numTeams;
int t = s + 1;

for (int i = 0; i < numTeams; i++) {
for (int j = i + 1; j < numTeams; j++) {
if (i == j)
continue;
fn.addEdge(new FlowEdge(s, nodeID, g[i][j])); // source to match
// nodes
fn.addEdge(new FlowEdge(nodeID, numMatches + i,
Integer.MAX_VALUE)); // match to team nodes
fn.addEdge(new FlowEdge(nodeID, numMatches + j,
Integer.MAX_VALUE)); // match to team nodes
nodeID += 1;
}
fn.addEdge(new FlowEdge(numMatches + i, t, Math.max(0, w[x] + r[x]
- w[i]))); // game nodes to target
}

new FordFulkerson(fn, s, t);

for (FlowEdge e : fn.adj(s)) {
if (e.flow() != e.capacity())
return true;
}
return false;
}

public Iterable<String> certificateOfElimination(String team) {
// subset R of teams that eliminates given team; null if not eliminated
if (!teamNames.containsKey(team))
throw new java.lang.IllegalArgumentException();
int x = teamNames.get(team);
int numMatches = this.numTeams * (this.numTeams - 1) / 2;
int nodeID = 0;

List<String> nList = new ArrayList<String>();
for (int i = 0; i < this.numTeams; i++) {
if (w[x] + r[x] - w[i] < 0)
nList.add(nameList[i]);
}
if (nList.size() > 0)
return nList;

FlowNetwork fn = new FlowNetwork(numMatches + numTeams + 2);
int s = numMatches + numTeams;
int t = s + 1;

for (int i = 0; i < numTeams; i++) {
for (int j = i + 1; j < numTeams; j++) {
if (i == j)
continue;
fn.addEdge(new FlowEdge(s, nodeID, g[i][j])); // source to match
// nodes
fn.addEdge(new FlowEdge(nodeID, numMatches + i,
Integer.MAX_VALUE)); // match to team nodes
fn.addEdge(new FlowEdge(nodeID, numMatches + j,
Integer.MAX_VALUE)); // match to team nodes
nodeID += 1;
}
fn.addEdge(new FlowEdge(numMatches + i, t, Math.max(0, w[x] + r[x]
- w[i]))); // game nodes to target
}

FordFulkerson FF = new FordFulkerson(fn, s, t);

boolean flag = false;
for (FlowEdge e : fn.adj(s)) {
if (e.flow() != e.capacity()) {
flag = true;
break;
}
}
if (!flag)
return null;
else {
List<Integer> nodeList = this.BFSRes(fn, s);
List<String> nl = new ArrayList<String>();
for (Integer v : nodeList) {
if (FF.inCut(v) && v >= numMatches) {
nl.add(this.nameList[v - numMatches]);
}
}
return nl;
}
}

private List<Integer> BFSRes(FlowNetwork graph, int node) {
Queue<Integer> Q = new Queue<Integer>();
boolean[] visited = new boolean[graph.V()];
Q.enqueue(node);
visited[node] = true;
List<Integer> nodeList = new ArrayList<Integer>();
while (!Q.isEmpty()) {
int cn = Q.dequeue();
for (FlowEdge e : graph.adj(cn)) {
int t = -1;
if (e.from() == cn)
t = e.to();
else
t = e.from();
if (e.residualCapacityTo(t) > 0) {
if (!visited[t]) {
Q.enqueue(t);
visited[t] = true;
nodeList.add(t);
}
}
}
}
return nodeList;
}

public static void main(String[] args) throws Exception {
BaseballElimination division = new BaseballElimination(args[0]);
for (String team : division.teams()) {
if (division.isEliminated(team)) {
StdOut.print(team + " is eliminated by the subset R = { ");
for (String t : division.certificateOfElimination(team))
StdOut.print(t + " ");
StdOut.println("}");
} else {
StdOut.println(team + " is not eliminated");
}
}
}
}
https://segmentfault.com/a/1190000005345079
本次作业在细节上有一些非常简单的小技巧可以帮助简化实现(简洁性也是checklist提示的,参考代码不到200行,我的版本为150行左右),但可能不是第一次思考时就能想到:
  • 在读取文件数据时就可额外计算(保存)一些后期需要的数据:目前榜首队伍与获胜场数(用于简单淘汰),和以双方队伍为单位的比赛场次(用于建立FlowNetwork的顶点数);
  • "Do not worry about over-optimizing your program because the data sets that arise in real applications are tiny." 对我的思路,这意味着无需考虑FlowNetwork的复用问题——一个早期造成很多痛苦的优化尝试;
  • FordFulkerson类的使用实际上使问题仅剩下了建模部分,且在说明中已解释得非常详细,故实现十分直接。



Labels

LeetCode (1432) GeeksforGeeks (1122) LeetCode - Review (1067) Review (882) Algorithm (668) to-do (609) Classic Algorithm (270) Google Interview (237) Classic Interview (222) Dynamic Programming (220) DP (186) Bit Algorithms (145) POJ (141) Math (137) Tree (132) LeetCode - Phone (129) EPI (122) Cracking Coding Interview (119) DFS (115) Difficult Algorithm (115) Lintcode (115) Different Solutions (110) Smart Algorithm (104) Binary Search (96) BFS (91) HackerRank (90) Binary Tree (86) Hard (79) Two Pointers (78) Stack (76) Company-Facebook (75) BST (72) Graph Algorithm (72) Time Complexity (69) Greedy Algorithm (68) Interval (63) Company - Google (62) Geometry Algorithm (61) Interview Corner (61) LeetCode - Extended (61) Union-Find (60) Trie (58) Advanced Data Structure (56) List (56) Priority Queue (53) Codility (52) ComProGuide (50) LeetCode Hard (50) Matrix (50) Bisection (48) Segment Tree (48) Sliding Window (48) USACO (46) Space Optimization (45) Company-Airbnb (41) Greedy (41) Mathematical Algorithm (41) Tree - Post-Order (41) ACM-ICPC (40) Algorithm Interview (40) Data Structure Design (40) Graph (40) Backtracking (39) Data Structure (39) Jobdu (39) Random (39) Codeforces (38) Knapsack (38) LeetCode - DP (38) Recursive Algorithm (38) String Algorithm (38) TopCoder (38) Sort (37) Introduction to Algorithms (36) Pre-Sort (36) Beauty of Programming (35) Must Known (34) Binary Search Tree (33) Follow Up (33) prismoskills (33) Palindrome (32) Permutation (31) Array (30) Google Code Jam (30) HDU (30) Array O(N) (29) Logic Thinking (29) Monotonic Stack (29) Puzzles (29) Code - Detail (27) Company-Zenefits (27) Microsoft 100 - July (27) Queue (27) Binary Indexed Trees (26) TreeMap (26) to-do-must (26) 1point3acres (25) GeeksQuiz (25) Merge Sort (25) Reverse Thinking (25) hihocoder (25) Company - LinkedIn (24) Hash (24) High Frequency (24) Summary (24) Divide and Conquer (23) Proof (23) Game Theory (22) Topological Sort (22) Lintcode - Review (21) Tree - Modification (21) Algorithm Game (20) CareerCup (20) Company - Twitter (20) DFS + Review (20) DP - Relation (20) Brain Teaser (19) DP - Tree (19) Left and Right Array (19) O(N) (19) Sweep Line (19) UVA (19) DP - Bit Masking (18) LeetCode - Thinking (18) KMP (17) LeetCode - TODO (17) Probabilities (17) Simulation (17) String Search (17) Codercareer (16) Company-Uber (16) Iterator (16) Number (16) O(1) Space (16) Shortest Path (16) itint5 (16) DFS+Cache (15) Dijkstra (15) Euclidean GCD (15) Heap (15) LeetCode - Hard (15) Majority (15) Number Theory (15) Rolling Hash (15) Tree Traversal (15) Brute Force (14) Bucket Sort (14) DP - Knapsack (14) DP - Probability (14) Difficult (14) Fast Power Algorithm (14) Pattern (14) Prefix Sum (14) TreeSet (14) Algorithm Videos (13) Amazon Interview (13) Basic Algorithm (13) Codechef (13) Combination (13) Computational Geometry (13) DP - Digit (13) LCA (13) LeetCode - DFS (13) Linked List (13) Long Increasing Sequence(LIS) (13) Math-Divisible (13) Reservoir Sampling (13) mitbbs (13) Algorithm - How To (12) Company - Microsoft (12) DP - Interval (12) DP - Multiple Relation (12) DP - Relation Optimization (12) LeetCode - Classic (12) Level Order Traversal (12) Prime (12) Pruning (12) Reconstruct Tree (12) Thinking (12) X Sum (12) AOJ (11) Bit Mask (11) Company-Snapchat (11) DP - Space Optimization (11) Dequeue (11) Graph DFS (11) MinMax (11) Miscs (11) Princeton (11) Quick Sort (11) Stack - Tree (11) 尺取法 (11) 挑战程序设计竞赛 (11) Coin Change (10) DFS+Backtracking (10) Facebook Hacker Cup (10) Fast Slow Pointers (10) HackerRank Easy (10) Interval Tree (10) Limited Range (10) Matrix - Traverse (10) Monotone Queue (10) SPOJ (10) Starting Point (10) States (10) Stock (10) Theory (10) Tutorialhorizon (10) Kadane - Extended (9) Mathblog (9) Max-Min Flow (9) Maze (9) Median (9) O(32N) (9) Quick Select (9) Stack Overflow (9) System Design (9) Tree - Conversion (9) Use XOR (9) Book Notes (8) Company-Amazon (8) DFS+BFS (8) DP - States (8) Expression (8) Longest Common Subsequence(LCS) (8) One Pass (8) Quadtrees (8) Traversal Once (8) Trie - Suffix (8) 穷竭搜索 (8) Algorithm Problem List (7) All Sub (7) Catalan Number (7) Cycle (7) DP - Cases (7) Facebook Interview (7) Fibonacci Numbers (7) Flood fill (7) Game Nim (7) Graph BFS (7) HackerRank Difficult (7) Hackerearth (7) Inversion (7) Kadane’s Algorithm (7) Manacher (7) Morris Traversal (7) Multiple Data Structures (7) Normalized Key (7) O(XN) (7) Radix Sort (7) Recursion (7) Sampling (7) Suffix Array (7) Tech-Queries (7) Tree - Serialization (7) Tree DP (7) Trie - Bit (7) 蓝桥杯 (7) Algorithm - Brain Teaser (6) BFS - Priority Queue (6) BFS - Unusual (6) Classic Data Structure Impl (6) DP - 2D (6) DP - Monotone Queue (6) DP - Unusual (6) DP-Space Optimization (6) Dutch Flag (6) How To (6) Interviewstreet (6) Knapsack - MultiplePack (6) Local MinMax (6) MST (6) Minimum Spanning Tree (6) Number - Reach (6) Parentheses (6) Pre-Sum (6) Probability (6) Programming Pearls (6) Rabin-Karp (6) Reverse (6) Scan from right (6) Schedule (6) Stream (6) Subset Sum (6) TSP (6) Xpost (6) n00tc0d3r (6) reddit (6) AI (5) Abbreviation (5) Anagram (5) Art Of Programming-July (5) Assumption (5) Bellman Ford (5) Big Data (5) Code - Solid (5) Code Kata (5) Codility-lessons (5) Coding (5) Company - WMware (5) Convex Hull (5) Crazyforcode (5) DFS - Multiple (5) DFS+DP (5) DP - Multi-Dimension (5) DP-Multiple Relation (5) Eulerian Cycle (5) Graph - Unusual (5) Graph Cycle (5) Hash Strategy (5) Immutability (5) Java (5) LogN (5) Manhattan Distance (5) Matrix Chain Multiplication (5) N Queens (5) Pre-Sort: Index (5) Quick Partition (5) Quora (5) Randomized Algorithms (5) Resources (5) Robot (5) SPFA(Shortest Path Faster Algorithm) (5) Shuffle (5) Sieve of Eratosthenes (5) Strongly Connected Components (5) Subarray Sum (5) Sudoku (5) Suffix Tree (5) Swap (5) Threaded (5) Tree - Creation (5) Warshall Floyd (5) Word Search (5) jiuzhang (5)

Popular Posts