THE INTERNATIONAL COLLEGIATE PROGRAMMING CONTEST (ICPC)

THE ICPC LATIN-AMERICAN REGIONAL CONTESTS - CARIBBEAN FINALS

Judges’ tips

Please, beware of reading carefully those Judges’ tips:

• • Unless otherwise stated, the following conditions hold for all problems:

    • • Program name:

        • 1. Your solution must be called codename.c, codename.cpp, codename.cc, codename.java, codename.py or codename.kt, where codename is the capital letter which identifies the problem.

      • Input:

        • 1. The input must be read from standard input.

          2. The input consists of a single test case, which is described using a number of lines that depends on the problem. No extra data appear in the input.

          3. When a line of data contains several values, they are separated by single spaces. No other spaces appear in the input. There are no empty lines.

          4. The English alphabet is used. There are no letters with tildes, accents, diaereses or other diacritical marks (~n, ~A, e, I, ^o, U, c, etc.).

          5. Every line, including the last one, has the usual end-of-line mark.

      • Output:

        • 1. The output must be written to standard output.

          2. The result of the test case must appear in the output using a number of lines that depends on the problem. No extra data should appear in the output.

          3. When a line of results contains several values, they must be separated by single spaces. No other spaces should appear in the output. There should be no empty lines.

          4. The English alphabet must be used. There should be no letters with tildes, accents, diaereses or other diacritical marks (~n, ~A, e, I, ^o, U, c, etc.).

          5. Every line, including the last one, must have the usual end-of-line mark.

          6. To output real numbers, round them to the closest rational with the required number of digits after the decimal point. Test case is such that there are no ties when rounding as specified.

  • 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 the 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.