I propose to discuss here all that concerns Codeforces Beta Round #3. Of course, during the competition it is forbidden to write anything about the solution of problems and similar things
For the time of this contest, we turned off the chat server. This does not mean that it will not operate in future - I think it is a convenient and efficient way to communicate during the competition and you may expect it in the future.
Also I'd like to announce Codeforces Beta Round #4, which will be held next week. It will be for participants from the second division (non-rated users or those having less than 1500 rating points). We will try not to delay Codeforces Beta Round #5, which will be opened for all.
Wish you high rating,
MikeMirzayanov
Problem A: It said that both the first and second lines would contain t. I had no idea where to report it but I guess everyone was able to get around it.
Problem B: It was not clear at first that the second line of output should be a space separated list, again I had to guess and hope for the best. For that matter, I wish the example required two vehicles in output...
Problem C: Nice trickiness.
Problem D: I wish I didn't lose so much time on implementation of the other three problems because this seems like the only truly interesting one of the set :)
I like that it tells you the number of test it is running.
At one moment I had two tests in queue for the same problem, because I noticed too late that the first one was running 1000 random test cases... I think that instead of having both soltuions in the queue, after submitting the second one, the first should get a "Cancelled" and get penalization. Else you could just submit slow solutions and forbid queue usage from the rest of the teams...
Hello, maybe I missed that while reading other posts regarding the contests. Is there some pseudoconstant defined on the server? It would be a nice thing, in that case the contestants won't have to deal with streams.
For example, right now I use the following trick:
#ifndef USE_ONLINE_JUDGE
freopen("input.txt","rt",stdin);
freopen("output.txt","wt",stdout);
#endif
And before sumbitting I have to add the line manually in the beginning of the source code:
#define ONLINE_JUDGE
I think it will be helpful (for educational purpose) because it's quite difficult to find bugs when the solution fails in tricky case.
Thank you for suggestion. I'm interested in how other people debug during competitions, especially when the solution fails several times. Do you use stress-test?
But I think it would be nice if test data are published because it's not always possible to solve problems by oneself.
Tests are not published mainly in the online archives, which are rating.
By the way, If you want to solve the problem yourself, nobody forces you to watch tests.
It was compiler's problem related to printf. (I'm not complaining, because it's not CodeForces's fault at all.) But I suggest to publish test data and enable us to run solutions on the CodeForces's system to find such bugs as easy as possible.
Can someone help me? 10970260 is my submission ID, which is getting invalid output format. Although it is giving correct output format on my machine.
The link for the tutorial is broken?
I mean the link shown in the contest material part in http://codeforces.me/contest/3/
edit: Dont quite understand the downvotes... Is this actually fixed?