Just wanted to list some ideas for next year: 1) Work out something with low participation in Distributed Round. You were planning for something slightly below 500, in the end there were around 200 people actively participating (both in Practice and real round). This actually means that cut off point could be extended to probably 1,000, but it was very difficult to predict beforehand. I am not sure what can be done, but there can be official "check-in" for the competition, like you have a week to respond and check-in into Distributed Round, if you didn't - bunch of e-mails get sent out to those 501st -> up. Not perfect solution, but it was very sad for many people to see that there are 300 people who don't want to participate in something they are eager to participate.
2) Please don't mark testing problem as problem A. Let it be problem Z. I am still confused when somebody says "Problem B", as I remember very well that "almost_sorted" was the first problem and "mutexes" was second. 3) For interim practice and testing - did you consider slowed down single PC which emulates running 100 nodes, though with lower input boundaries? -- You received this message because you are subscribed to the Google Groups "Google Code Jam" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-code/3b45dcd3-8e05-4e1f-a1fb-787c70f6348c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
