There were some extra whitespaces at the end of lines in the testdata of Problem C. It has been fixed now, and all submissions will be re-judged at the end of the contest so that no penalty is incurred due to this. We apologize for the error.
Because of this I wasted an hour and a few wrong submission. The whitespaces issue happened only to python users because they take the whitespace as well while taking the input. So a similar thing happened in March Cook-Off but in that contest the ratings were removed. Please make this contest un-rated as well. I donāt have issues because of the whitespace issue as I should have moved on with the other problems but then in that case you should make March Cook-Off rated.
Also, 144 penalty for just one contest? IDK, it seems a bitā¦inflated? Whenever I participate in cook-off, I usually see a rating buff of 20-60 most of the timesā¦so I expect a similar pattern in degradation of rating. (Correct me if I am wrong here)
And this was just one of the issues. There were other issues like-
āThere was an issue with the testdata in Problem F. It has been fixed, and all submissions re-judged. We are very sorry for the mistake.ā
āProblem G has been added. The delay is regrettedā [This problem was added after 1hr 40minā¦i.e. when more than 50% of time was over. Call me biased, but I am STRICTLY AGAINST this. What would you had done had it been a 2hr contest?)
So roughly we can say that there were issues with 3/7 problems in contest, ~42%.
In Lunchtime, Rainbow was 1 of the 5 problems with issue (~20% of the total problems) [I have ignored the issue of trailing spaces in testcases in ROBOTG, ].
I think you have a point with your claims. But I donāt know how codechef would act to this, because making it unrated for everyone would make many unhappy (those who got lots of ratings) and its kind of a ā¦āproblemā when you take back something you gave. Nonetheless, I think they can make it unrated for those most affected/a few people who were badly affected by having a check at submissions.
Your claims have got points, but the problem is the ratings been already updated. Try to think of some middle path where both of you can compromise.
At least in the Contests of Short format , if there is a problem with test data due to which user is getting wrong Answer for Correct Submission ; and that error gets rectified after a very long time ( above 30 minutes? ) , then it is better to make the round un-rated. Even though the solutions will be rejudged to take back the penalty, but what about the time spent by the user correcting the already correct solution. Its just not easy to move to other problem with the weight of WA when you feel that you have got the logic right.
