CLC2016 - Judges' tips

The 2016 ACM-ICPC Caribbean Local Contests.
User avatar
Posts: 1096
Joined: Fri Nov 11, 2011 9:32 am
Location: Havana, Cuba
Gender: Male

CLC2016 - Judges' tips

Postby dovier » Sat Jun 25, 2016 4:05 pm

Judges' tips

Please, beware of reading carefully those Judges’ tips:
  • For clarifications, we strongly recommend to write in English. And make sure to select the proper Subject (Problem title) before sending the clarification. Don't send the same question several times, all clarifications will be answered by the human judges as soon as possible. A "No comments" response will be delivered if the answer to your question is included in the problem statement.
  • Do not use the %I64d specifier to read or write 64-bit integers in C++. It is recommended to use cin, cout, streams or the %lld specifier instead.
  • If the problem statement doesn't specify the number of instances (tests cases) or when to stop reading, this means that you should read until you reach the End Of File (EOF). Also you don't need to process tests cases one by one, although it's possible. You can read all the input first, then process the data, and finally output responses for all instances. Of course, take into account that all this should be done within the limits of time and memory for the problem.
  • Always respect the problems' output format: this is the main reason for Presentation Error (PE). Beware problems in which the use of real numbers is needed in the written solution. The point '.' is the most commonly used decimal separator in almost all problems involving real numbers in their datasets, therefore perhaps you need to change the locale configuration; formatting the output numbers for using '.' instead of ','.
  • Also, remember that your program is tested with more datasets than those that appear in the "Sample Input" and "Sample Output" sections: try to think of extreme cases to test your program before submitting a solution. The fact that your program solves the sample input dataset correctly doesn't mean that it solves all datasets correctly.
  • To submit a code to the judge, select the proper problem and language before sending. Otherwise, you will probably get an unexpected response.
  • If you are submitting a file (instead of pasting the source code in the text area) to the judge, the filename is irrelevant no matter the language used. You must however respect the common extension of the language you selected (.c for C, .cpp for C++, .java for Java, .cs for C#, .py for Python).
  • Please, read the COJ's FAQ for other common questions, like code formats, answers of the judging system, etc.

Return to “2016”

Who is online

Users browsing this forum: No registered users and 1 guest