Problem Format
-
Every effort is made to guarantee that problems avoid dependence
on detailed knowledge of a particular application area or particular programming language.
-
Each problem will require reading input from a specific text file,
and printing its output to the standard console.
Hint to coaches: Make sure at least one team member can read data from text files.
-
Since judging is a semi-automatic process,
it is mandatory for the program output to match the output format specified in the problem description.
-
The judges' secret input file will test the program on multiple cases (or datasets.)
The format of the input file will be designed so that multiple datasets can be included in a single text file.
-
Each problem in an ACPC contest is specified in the following four sections:
-
Description:
This section specifies the problem contestants are supposed to solve.
-
Input format:
Here you'll find detailed description on how the input file will be formatted.
-
Output format:
This section specifies the format of the output of your program.
Your program's output must conform to the format specified.
-
Sample Input/Output:
Here you'll find a sample Input/Output that has successfully passed the judges' program.
Note that your program will be tested on a different (and more complex) dataset.
Just because your program passed the sample Input/Output, doesn't mean it is correct.
-
In addition, the problem statement will specify the name you should use for your program,
and the name of the input file.
Since compilation and testing is an automated process,
it is important that you follow the naming convention exactly.
For example, if the problem statement states that the files should be named easy
then the program file must be named named
easy.c for a C program,
easy.cpp for a C++ program,
or easy.java for a JAVA program.
The input file will be named easy.in
