It seems everyone is in the know that Codeforces Beta Round#3 didn’t take place in the appointed time. Seemingly, it happened because of the increased popularity of the site, on the one hand, and some of our bugs, on the other. For sure, it’s a pity that things went in such a way. On the other part, if everything had failed during the contest, it would have been worse. The contest is rescheduled for Sunday, 15:00 (Moscow time). Please be sure to check here for the start time in your time zone: http://www.timeanddate.com/worldclock/fixedtime.html?&day=07&month=03&year=2010&hour=07&min=00&sec=0&p1=179
I’d like to remind you that the project is in Beta yet, and we’ll work on the problem and try to fix it.
Thanks for your understanding,
According to The November Revolution of Colors and Titles, the text below is not an actual and just a historical document.
Not so long ago a new rating system was introduced at Codeforces. To complete the picture I’ll tell you about our Table of Ranks.
From this moment on all the participants will be given ranks that reflect their skills and abilities at such a hard field as computer science and problem solving. Judging by the results of previous rounds you will gain (or lose, I hope it’s not your case) points. If you score big success, you are promoted to a higher rank. You can see the dependence between rating and ranks in the table below. Moreover each rank has its color, which is reflected in the table.
As some users have already noticed - contest rating has been added to Codeforces. For now it is in beta too, but it looks very adequate. Here's how it is calculated.
Each person is characterized by their rating, the number R. If person A's rating is RA, and person B's is equal to RB, then the formula
Before updating your rating after the end of the round, for each participant his seed is calculated, that is the place that the participant is expected to take in this competition. Thus, two things are known for each participant - his seed (the expected place) and rank (the actual place). Depending on the difference between these two values, your rating increases or decreases. If the difference is higher, your rating changes more.
There are a few technical points:
As at TopCoder all users are divided into two divisions: the first (rating over
1500 1650) and the second (rating_ not more than 1500 1650). Not rated users fall into the second division automatically.
Wish you high rating,
Thank you all for participating in Codeforces Beta Round # 2. I hope you enjoyed it. You may discuss the problems and system in comments. Please express your opinion, especially if you notice any inappropriate behavior. And as always, I will read with interest the suggestions for improvement.
See you at Codeforces Beta Round # 3.
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.
Later you'll be introduced to the rules of the Codeforces contests, which differ from those of ACM-ICPC, TopCoder, GCJ, and I hope they'll bring some difference to the world of programming competitions. Most of the official competitions will be carried out according to these rules, though there will be more traditional contests. For example, Codeforces Beta Round #1 will be carried out according to the familiar ACM-ICPC rules. For some time testing will be based on Windows, but things might change in future, fortunately, the system supports testing on different platforms, even within one contest.
At the present time the system is configured to support the following programming languages (the compilation and/or the launching line is shown for each language):
It is not guaranteed that all the problems will have solutions in all the given languages (it's especially about the scripting ones). Probably, I'll later introduce equalizing coefficients for the working time for some languages. A "plus" next to the version name means that the testing system can use older versions. If you have suggestions about the possible ways to change the compilation or the launching line, write about them in your commentaries.
It should be mentioned that apart from standard verdicts, you can get "Denial of judgement", which usually means that your solution can't be launched, or it has unexpectedly failed. For example, is the Delphi array is too big, the compiler compiles the code, but the result will be the incorrect win32 exe-file. Solutions with the verdicts like "Compilation failed", "Denial of judgement", "Judgement failed" will be ignored while summing the results.
Moreover, pay attention, please, that the problems will be given in English as well as in Russian.
That's it, see you at Codeforces Beta Round#1.
UPD: GCC compiler has been added.
UPD 2: Added Haskell and F#.
UPD 3.2: Actual compiler versions are
I will briefly enumerate the changes at Codeforces:
The results are announced - thanks to Ivan Romanov for being so quick. Thanks to everyone who supported us and followed the contest events. My apologies the system break-down, but if everything was stable in Codeforces, I wouldn't have called it beta. Unfortunately, I had no Internet during the day.
The third day was marked by rises and falls of Harbin in our eyes. Everything started with the opening ceremony - it was badly organized, protracted and boring. Right before the opening ceremony the audience went to the assembly hall of the Harbin Engineering University, but the participants were less privileged and had to suffer. We were all gathered in a long basement room, we had to form a line according to predetermined numbers, and wait. As you know, 103 teams take part in the finals, so, about 450 people (coaches and volunteers included) packed into that basement. It was stuffy and crowded there. The Russian teams demonstrated their inherent quick-wittedness, they decided not to stand in the crowd, and moved closer to the entrance, it was cooler and there was more room there.
Finally, to solemn music (be careful, phonogram!) the teams one by one climbed the stage, took pictures and went down to join the audience. As after that according to the program some outdoor activities were planned, many participants had prepared sensibly beforehand, they had put on the presented warm trousers, sweaters, etc. With such a "formal" look they got to the opening ceremony and the shoot. My standing ovation.
The second day we spent sightseeing - we went to the excursions organized by the host country, some places we visited on our own.
In the morning we had some free time, and we went to the local Arbat (or Kirov Avenue, as you wish). Actually, when we walked not far away from the hotel, we found out that we vaguely knew how to get back. But still we didn't want to go back, that's why we went on moving away, guided by little information we had. It was really cold - but we were well-prepared. I put on a down-filled coat, that we'd got on the first day, over my proper one, foe example. Vova put on the presented trousers over his own jeans, and seemed happy. The parts that got cold were our faces.
On our way to that avenue we asked for the directions many times. The problem was that we didn't remember its name. 80% of passers-by said they didn't speak English, 20% said they did, but it was the only thing they could say in English. Finally, using the international language of gestures, we got the direction and found the avenue. Personally I was disappointed, there was nothing to look at there. Of course, it was interesting to walk past old buildings, but we had no desire to "Russian goods" shops. They sold home-made vodka, chocolate called "Russian fir (pets)" (they meant "pelts"), and other goods of doubtful quality.
Everyone got a set of warm clothes. The hats in the photo looked more like scarves at closer inspection. Moreover, we got a set of mustard plasters, which are recommended to be worn under your clothes to keep the body warm.
The Indian team got very excited, when I asked them how popular the TV series The Big Bang Theory is in India.
We flew 7 hours to Beijing, and 2 more hours from Beijing to Harbin. At Sheremetyevo Airport we met several other Russian teams. The teams from Samara, Izhevsk, and, it seems, Ural were on the same plane. And some other teams. Moreover, we flew with Andrey Styskin, who works for Yandex, and will take part in the conference in the context of the contest. Separate teams could be clearly distinguished on the plane: 3 young people, each with a laptop, or a netbook. However there were exceptions.