SCUSA Regional Programming Contest Local Doc Server

This documentation will be available to teams during contst.

Please use this documentation as you see fit. A best effort has been made to provide this info accurately.

Errata

Here are some general clarifications for the contest, not specific to any particular problem:

Input is from stdin and output goes to stdout; there are no files involved. Filenames should never be used.
When you click the Test button in PC^2 and the file section dialog box appears, do not select your source code; select your sample data. You have already selected source.
You may only submit a single source file. No input data, no multiple-file programs.
The judgments we will use are:
- Yes
- No - Compilation Error
- No - Run Time Error
- No - Time Limit Exceeded; the time limit is 60 seconds.
- No - Wrong Answer
Extra whitespace (within reason) will not count against your problem (although we would appreciate if you didn't have any).
Lack of necessary whitespace WILL count against your problem, and will be judged as No - Wrong Answer. Read the problem carefully.
Incorrect spelling WILL count against your problem, and will be judged as No - Wrong Answer. Read the problem carefully.
Despite the appearance on the website, there are no extra blank lines between either input lines or output lines.
Any output to stderr by your program WILL count against your problem, and will be judged as No - Run Time Error. Do not leave debug output on when you submit your problem.
Any non-zero exit code WILL be judged as No - Run Time Error.

Here are various language-specific concerns:

Java
- Any unhandled exceptions thrown in Java will cause your problem to be judged as No - Run Time Error. Do not throw exceptions out of the program.
- Java main classes must be named the same as the source file, per the Java standard.
C/C++
- Ensure that you are including the appropriate headers for any uses of Standard C Library functions, such as atoi() and floor(). The judging machines are using a strict compiler that will give compilation errors if these headers are not included. The easiest way to determine the right header to use is to type man 3 funcname at a terminal, where funcname is the name of the function. Near the top, in the SYNOPSIS section, the proper header will be listed.
- Similarly, make sure you use the proper Standard Template Libraries for C++. For example, fill() is in the <algorithm> header. Check the Standard Template Library documentation, available on localdoc, for details.
- The proper definition for main() in both C and C++ is:
```
         int main(int argc, char* argv[])
```
  A close but incorrect and invalid definition is:
```
         int main(int argc, char argv[])
```
  Make sure you use the correct one.

Here are the per-problem errata:

Rank and File
- If both check and checkmate are detected, print "CHECKMATE".
The Extent of the Problem
- In the Input section, X and Y are the first and last blocks of the second extent.
- The numbering of blocks starts at 1 and ends with S.
- Both the RADfs.doc example at the top and the fourth line of the sample input should have 57-58 as the first extent instead of 37-38. Specifically, the sample input should read, in whole:
```
2
152
1
radfsdoc M 3 57-58 102-114 23-47
1
100
4
swapfile I 3 5-10 80-95 25-50
smallfile M 2 1-4 11-14
bigfile M 2 15-24 51-60
tinyfile M 1 61-64
2
```
Wandering Aimlessly
- In NPC scripts, no value is lower than 1 or higher than 40.

Any printouts without a banner will be recycled. In Eclipse, you must choose to print this header in the printer dialog box. Only the "Standard" header should be used.