- Please do not discuss strategy, suggestions or tips in the comments during a live contest. Posting questions clarifying the problem statement is ok. If you are unsure, email us at email@example.com
- Discussing CodeChef’s problems or any aspect of problem, on any other platform on web, on identification, could lead to disabling of respective account and banning from the community.. Contest problems will become visible on Friday, 3rd October 2014 at 15:00 hours IST. Check your timezone here.
- You will receive one point for solving a problem (passing all test cases - no partial credit), regardless of the level of difficulty of that problem.
- You can submit solutions as many times as you'd like, there are no penalties for incorrect submissions.
- Each contest will have one min/max tie breaker problem, where the best solution will receive one point and all other solutions will receive a fraction based how close they come to the best solution
- You shall not possess more than one account on CodeChef. If you have, then do let us know, so that we can deactivate the insignificant one. If you do not report it and we come to know about it, we may deactivate both the accounts permanently.
- The score that you will see during the contest will only be partial (obtained on 20% of the test data).
- The submissions will be re-judged at the end of the contest to get full score (obtained on the whole test data).
- The number of submissions that one can make during the contest on the problem will be limited to 500.
- All participants are expected to abide by the CodeChef Code Of Conduct
Note: As a contestant, you are responsible for making sure others don't access the code that you submit. If you're on a network or shared computer, or using an online development environment, make sure that other contestants don't have access to your code. If you use Ideone, make sure to mark your submission "private" (not secret)".
The problem PRPOTION has been updated. Problem statement has been changed. Please re-read the problem statement. Test data and reference solutions of both setter and tester were wrong. Please resubmit the solutions of the problem. We are really sorry for the situation. We regret the inconvenience.