Forum

Post 17.05.2009   # 1
Subject Is 'Timeout' considered as a 'Fail' ?
I didn't even know that we can get that result. Does it mean that the solution is wrong because it's slow ? Is time a constraint?
dime_a is offline Reply
Post 17.05.2009   # 2
dime_a wrote:
I didn't even know that we can get that result. Does it mean that the solution is wrong because it's slow ? Is time a constraint?


Yes, there is a time constraint of 5 seconds. (We are flexible about 2-3 seconds over this limit, just in case).

If the solution is slow, this is considered as a wrong result.
anikov is offline Reply
Post 17.05.2009   # 3
5 sec per test case? Isnt that too much?
vasja is offline Reply
Post 17.05.2009   # 4
vasja wrote:
5 sec per test case? Isnt that too much?


It is
A good solution either runs in miliseconds or it doesn't run for hours.
But, we are giving 5 seconds just in case...
anikov is offline Reply
Post 17.05.2009   # 5
The time limit is not mentioned in the official rules of the competition. Maybe some of the competitors from previous years know that but it is not stated anywhere...

A good solution either runs in miliseconds or it doesn't run for hours.


- For example when ppl wait for results from DNA analysis they usually wait couple of days (I don't know how much is it currently) but it is really important thing sometimes... Sometimes it it important for the solution to be correct.

Plus when you only have 2 hours you make stupid mistakes (like I did using int instead of long in the 500 problem - change it with long and it passes all the cases )

I am pretty new in Java and this competition generally but the testing examples passed in all my problems while I was solving the problems but now I see that most of them are Timeout

When making the test examples choose some of those that require more time

Anyway... the problems were cool, the competition is nicely prepared and keep up the good work

kaskopje is offline Reply
Post 17.05.2009   # 6
kaskopje wrote:
The time limit is not mentioned in the official rules of the competition. Maybe some of the competitors from previous years know that but it is not stated anywhere...


Good point. I will check now the official rules and correct them if necessary.

- For example when ppl wait for results from DNA analysis they usually wait couple of days (I don't know how much is it currently) but it is really important thing sometimes... Sometimes it it important for the solution to be correct.


When looking at some of the solutions, it is clear that they will not finish / produce a result for a lifetime, even on fastest computers.
How could we then check whether they are correct if we don't have enough time to wait for their result?

I am pretty new in Java and this competition generally but the testing examples passed in all my problems while I was solving the problems but now I see that most of them are Timeout

When making the test examples choose some of those that require more time


Part of the problem solution is to predict all the border cases and to calculate the time for the worst case. We always give very strict constraints on the input arguments, so it should be easy to compute the worst case.
But, don't worry, it will come in time, all you need to do is practice, practice, practice.

Anyway... the problems were cool, the competition is nicely prepared and keep up the good work


Thanks, it is always nice to hear that.

[/quote]
anikov is offline Reply
Post 17.05.2009   # 7
I have another question regarding Timeout for the 500 problem:

Since I've kept all my results calculated in advance (because I expected that all test cases will be calculated in one execution), I can't understand why some of the tests are Timeout (6, 4000+, 500000+, etc.), because all of them should run at same execution time.


Thx in advance
cefo is offline Reply
Post 17.05.2009   # 8
cefo wrote:
I have another question regarding Timeout for the 500 problem:

Since I've kept all my results calculated in advance (because I expected that all test cases will be calculated in one execution), I can't understand why some of the tests are Timeout (6, 4000+, 500000+, etc.), because all of them should run at same execution time.


The Java class is loaded and initialized for every test case. For each test case we calculate 5 seconds of timeouts.
The test cases are not even run on the same server. Especially today because of the high rate of submission and the high rate of timeouts we had to run the testing on 7 servers in parallel.

Have in mind that these are only preliminary results. We will check all the results and all the solutions once again tomorrow.
anikov is offline Reply
Post 17.05.2009   # 9
Thx for the fast reply. Since that's the case (every test case is a separate run/loading class), then, as I said, for my "solution", wouldn't matter the value of the input - beacause it calculates all values(whole interval) every test/run . Anyway, I'll wait the official results, before any further comment. (((:
cefo is offline Reply
Post 19.05.2009   # 10
Anyway... the problems were cool, the competition is nicely prepared and keep up the good work


I totally agree with you. I just think that problems 300 and 500 should have been swapped . In my opinion , and also the results show this, 500 was much easier than 300. Unfortunately i didn't solve any of them in time but at least had an idea for 500
vasja is offline Reply
Post 19.05.2009   # 11
vasja wrote:
I just think that problems 300 and 500 should have been swapped . In my opinion , and also the results show this, 500 was much easier than 300.

I think that most of the people underestimated the 300 problem because there was no test case where N is close to 1000000.
We usually have one test case where input parameters have maximum allowed values, but somehow we missed to have such test case for the 300 problem.

bilievsk is offline Reply

Please login to post reply.