ACM ICPC World Finals 2015
Disclaimer This is an unofficial analysis of some possible ways to solve the problems of the ACM ICPC World Finals 2015. They are not intended to give a complete solution, but rather to outline some approach that can be used to solve the problem. If some of the terminology or algorithms mentioned below are not familiar to you, your favorite search engine should be able to help. If you find an error, please send an e-mail to austrin@kth.se about it.
— Per Austrin and Jakub Onufry Wojtaszczyk
| A | Amalgamated Artichokes |
| B | Asteroids |
| C | Advance Catering Map |
| D | Cutting Cheese |
| E | Parallel Evolution |
| F | Keyboarding |
| G | Pipe Stream |
| H | Qanat |
| I | Ship Traffic |
| J | Tile Cutting |
| K | Tours |
| L | Weather Report |
| M | Window Manager |
The judges felt this year’s problem set was a bit on the easy side (at the same time guessing that this probably meant that it was about the right difficulty since we always underestimate difficulties).
Congratulations to St. Petersburg State University of IT, Mechanics and Optics, the 2015 ICPC World Champions for their awesome performance, the first team ever to solve all problems in a World Finals!
In terms of number of teams that ended up solving each problem, the numbers were:
| Problem | A | B | C | D | E | F | G | H | I | J | K | L | M |
| Solved | 128 | 6 | 77 | 116 | 20 | 93 | 1 | 20 | 92 | 59 | 2 | 68 | 15 |
| Submissions | 140 | 20 | 150 | 185 | 62 | 324 | 16 | 28 | 237 | 110 | 1 | 81 | 108 |
In total there were 697 Accepted submissions, 562 Wrong Answer submissions, 161 Time Limit Exceeded submissions and 52 Run Time Errors. The most popular language was C++ by a wide margin: 1415 submissions compared to 74 for Java. There was a single submission in C (which was accepted!)
A note about solution sizes: below the size of the smallest judge and team solutions for each problem is stated. It should be mentioned that these numbers are just there to give an indication of the order of magnitude. The judge solutions were not written to be minimal and it is trivial to make them shorter by removing spacing, renaming variables, and so on. And of course the same goes for the code written by the teams during the contest!