FAQ - 2004 Rocky Mountain Regional ACM

The following are changes compared to previous contests

These make our conventions more similar to the world finals.

  • We have dropped the Program P by team T ... End of program P by team T convention in the output files.
  • Instead of probN root names (for example prob3.java,prob3.dat and prob3.out), we will:
    1. Use a more descriptive root name, like count.
    2. Use .in instead of .dat for input files. For example: count.cpp, count.in and count.out
  • For Java programs, instead of Main, the main() method must be declared in a public class of the same name as the source file, so
      public class count {
        public static void main(String[] args)
          throws Exception 
          // read count.in and write count.out...

Q. How many teams can be from one institution?

Q. How many people can be on a team?

Q. What languages & platforms will be used for the contest?

Q. What can we bring?

Q. What do you provide?

Q. What problems should we do first?

Q. What do we submit?

Q. How do we edit/compile/run our code?

Q. How do we test our code?

Q. How do we debug our code?

Q. How do we submit a problem?

Q. When we submit a problem, what should we expect back?

If the submission compile, the judges will first attempt to run the submitted program on the sample input data provided in the problem statements, then on additional input data. Along with any error verdict consequent to running the program, the judges will indicate whether the verdict is based on a run using sample input data or additional input data. In the latter case, it can be assumed that the run on sample input data was successful.

Q. How do we clarify a problem?

Q. How are teams ranked?

Enjoy the contest!