


Eryx wins the WildCard
The wildcard round proved particularly difficult, even as wildcard rounds go. Though the easy problem was straightforward if you saw the trick to it (and reid scored over 248 points on it), the other two problems were fiendishly difficult. Despite their best efforts, none of the competitors were able to successfully solve either of them, and only one of them even had a solution that made it as far as the system test phase. In the end, it came down to challenges, and Eryx and ardiankp had the most. Congratulations, and good luck to all the finalists! AlmostBipartiteMatchingby soulnetThis one was my gift for theory lovers. Solving this problem was all about thinking and, if you wanted a lot of points, maybe having faith instead of proofs. Since I have no rush for points now, I'll give you a formal proof. As complicated as the problem statement may sound, carefully looking at the shape of the graphs lead to an incredibly short solution (especially for an onsite!). Anyway, let's start from the beginning: We have two simple paths and some edges that connect them. Let's call the total number of nodes of the graph n. Of course, n = nA + nB. The maximum possible matching is then floor(n/2) (having all nodes matched, or all but one if n is odd, is the best we can do). If a simple path has an even number of nodes k, all its members can be perfectly matched (0 with 1, 2 with 3, ... and k2 with k1). If k is odd, this strategy leaves one node alone. Then, if nA or nB is even, we can obtain a maximum matching. If both are even, we have perfect matching, and if one is even and one is odd, we have a matching of all nodes but one, which is as good as it can get. Now, we only need to take care of the case in which nA and nB are odd. If we use the previous strategy in this case, we leave two nodes unmatched  we have a way of obtaining the second best possible match, so we need to check if a perfect match can be achieved. If it can, then we return n/2; otherwise, we return n/21. Let's suppose there is in fact a perfect match. Let's call red nodes to the nodes in A matched to a member of A and to the nodes in B matched to a member of B; and blue nodes to the rest (matched to a member of the other set). Let's call red edges to edges connecting red nodes and blue edges to edges connecting blue nodes. Edges not used in the matching are gray. Both A and B have an odd number of elements, and so they have one more node with even index than nodes with odd index. All red edges have one endpoint with an odd index and one endpoint with an even index (because of the shape of the graph); therefore, half of the red nodes have an odd index and the other half an even index. Since overall there are n/21 nodex with odd index and n/2+1 nodex with even index, the difference of 2 nodes is in the blue set. Finally, since less than half the set of blue nodes has an odd index, there is an edge that has both endpoints with even index. Using an edge with both endpoints with even indices we can easily construct a perfect matching, since the removal of those endpoints partitions each simple path in zero, one or two simple paths of even size (you can check this claim on your own as a homework) and in each of those paths, the strategy described at the beginning can be used to achieve a perfect match. Altogether, checking whether the most perfect match exists is checking if any of nA or nB is even OR if there is an edge with both endpoints in even indices. If that happens, we return n/2, otherwise, we return n/21 (remember that an "almost perfect" match is always possible). Java code follows: int n=nA+nB; if (nA%2==0nB%2==0) return n/2; for(int i=0;i<edgesA.length;++i) if (edgesA[i]%2==0 && edgesB[i]%2==0) return n/2; return n/21; SingleEliminationby lbackstromThe medium problem caused serious headaches for both the competitors and the TC staff. In particular, the problem statement listed claimed that inputs of size 16 were allowed, but the system only allowed the competitors to test inputs up to size 8. In fact, none of the TC solutions were quite fast enough to work with size 16 inputs, pointing to how hard it would be to solve with 16. When the contradiction was discovered, the decision was made that the best thing to do was to allow inputs of size 16, since that was what the problem statement said. It was felt that it wouldn't be fair to a competitor who spent time trying to solve the size 16 version if the limit was set at 8, and the only way to see the bug was to try to test with a size 16 input, which a competitor would likely not do until he thought he had solved the problem. Of course, the whole situation was very unfortunate, as it caused the problem to be all but unsolvable, and it had adverse effects for some of the competitors. In the end, no one, including the testers, had a solution that was quite fast enough, but TC was able to give the reference solution a little extra time so that the challenge phase could go forward and system tests could be run with size 16 inputs. Below is an explanation of the solution to the problem, which works with size 8 inputs: It is not necessary to test all 8! possible orders of teams to find the best solution, because many orders are equivalent. For example, swapping team 1 and team 2, or teams 14 with teams 58 will not affect the outcome. First, note that with 4 teams, there are only three orders worth considering: { 0, 1, 2, 3 }, { 0, 2, 1, 3 }, and { 0, 3, 1, 2 }. All other orders are equivalent to one of these three. To enumerate all interesting orders of 8 teams, we can start by selecting 3 of the remaining 7 teams to join the team we care about in the top half of the order. For each of the 35 (7 choose 3) possibilities, we can compute our team's best probability of winning by considering each of the three orders for these four teams. Call the greatest of these probabilities P_{1}. Next, we consider each of the 3 unique orders for the bottom 4 teams in the order, and compute the probability of each of these teams advancing to the final match. (These probabilities should sum to 1.0, of course.) Given these lists, we can compute our team's probability of winning the final match for each of the three orders. Call the greatest of these probabilities P_{2}. The maximum of P_{1} * P_{2} for each of the 35 possibilities is the solution to this problem for the N=8 case. Regularsby lbackstromA regular expression can be converted into a DFA, and it is easiest to think about this problem in those terms. Once we have a DFA, we just need to write a simple dynamic program the computes the number of accepted strings of a particular length that start in a particular state. Since our DFA will have two outgoing edges from every node, the number of accepted strings of length k is simply the sum of the number of strings from those two successor states, but of length k1. Unfortunately, converting into a DFA is nontrivial. Luckily, we
don't have to actually do an explicit conversion. Instead, we can do
things implicitly by considering that after some sequence of zeros and
ones, we have advanced some part of the way through the regular
expression. Of course, there are different places we could be in the
regular expression, depending on what choices we make, but there is a
welldefined set of locations, which is not hard to compute. For
example, if the current set is S, and I append a '1', it is easy to
compute the set of possible next positions. For each position p in S,
if p corresponds to a "1*" then I can stay at p, or advance. If p
corresponds to a '1' not followed by a '*', I must advance. Of
course, if p corresponds to something like "1*1*" I might advance
all the way to the end, but this is all easy to compute. The trick is to observe that each set of possible states, S, corresponds to a state in the DFA that would represent the expression. Furthermore, because the regular expression language being used is so simple, the number of possible sets of states remains relatively small. This allows us to write a dynamic program that takes a set S and a length as its state space: int[] ch; boolean[] b; int ptr; HashMap<String, Long> hm = new HashMap(); long go(long pos, int left){ long ret = 0; if((pos & (1l<<ptr))>0)ret = 1; if(left == 0){ return ret; } String key = pos+" "+left; if(hm.containsKey(key))return hm.get(key); long zer = 0, one = 0; for(int i = 0; i<ptr; i++){ if(((1l<<i)&pos)>0){ if(ch[i] == 0){ zer = 1l<<(i+1); if(b[i]) zer = 1l<<i; }else { one = 1l<<(i+1); if(b[i]) one = 1l<<i; } } } for(int i = 0; i<ptr; i++){ if(b[i] && ((1l << i) & one)>0){ one = 1l<<(i+1); } if(b[i] && ((1l << i) & zer)>0){ zer = 1l<<(i+1); } } ret += go(one,left1) + go(zer,left1); hm.put(key,ret); return ret; } public long stringCt(String regex, int maxLen){ ch = new int[regex.length()]; b = new boolean[ch.length]; for(int i = 0; i<regex.length(); i++){ if(regex.charAt(i) == '*'){ b[ptr1] = true; }else{ ch[ptr++] = regex.charAt(i)'0'; } } long pos = 1; for(int i = 0; i<ptr; i++){ if(b[i])pos = 1l<<(i+1); else break; } return go(pos,maxLen); } 
