I propose to discuss here the issues and troubles associated with Codeforces Beta Round #4. On our side, we identified three difficulties:
- Slow judging - apologize for the large queue, to the next round, I assume significantly increase the speed of judging;
- Runtime errors on Python solutions - apparently the decision they want to load some library, which is prohibited by security reasons;
- Sometimes incorrect runtime errors - apparently the result of the antivirus on testing servers, they will be turned off on the next rounds
Also express your impressions about the round.
P.S. And by the way, the round tutorial is waiting for a volunteer. It is desirable that it will be one of the leaders of today's competition. The tutorial should be in Russian and in English. It will be published on the homepage and later will be available via special link from the contest page.
UPD. The ratings have been updated.
UPD 2. Thanks to KudryashovIA for his help in making contest.
- I think it will be good to see code that I sent to judge;
- In my opinion slow judging was more harmful for some contestants (including me) than for the others;
- I would like to know if after beta mode everyone will start again with gray color if not I would be grateful if I could be removed from standings of beta round 4;
-100 is not so bad. The rating system has such organization, that it is OK to loose some rounds, everyone will get his own rating after awhile. Read about rating system on TopCoder, i think this system is something like topcoder's.
That's not true everyone had the same problem. For example contestants 1 and 2 sent solution to problem A at time x. After 20 minutes contestant 1 was informed his solution was incorrect and resubmit it and got acc at time x+20+1. Contestant 1 sent correct solution for problem B at time y whilst contestant 2 send correct solution for this problem at time y+30. It was all that these 2 contestants sent and in final standings contestant 1 has time x+40+1+y, and contestant 2 has time x+y+30 and is higher in standings than contestant 1, whilst in normal situation contestant 1 should have time x+20+1+y and he should be before contestant 2. It was one example, second could be when one contestant has completely no idea how to solve the problem, whilst the other knows the solution, but has a bug and wasn't informed about it during the contest. It is ok with top coder rules, but not with acm icpc rules. I think this round misrepresents the rating.
If I knew about this I wouldn't take part, but I found out after I sent solution to problem A.
I am not upset, because server is in beta now, I just would like to know if rating based on such rounds is beta too, and will be cleaned after beta mode.
This also raises the question as to what other modules are similarly restricted, and makes submitting in Python during an actual contest a risky option.