1. Teams may use 25 pages (or 12.5 double-sided sheets) of their own reference materials in the contest arena.  The team must submit this material in one ISO CD-ROM or as 25 pages hard copy, labeled with your team name and university's.  The CD must contain only one file, a PDF of your Team REFERENCE Document. Print out of this material will be made available for the team during the final contest.
2. Contestants may not bring any machine-readable versions of software or data to the contest arena. Contestants may not bring their own computers, computer terminals or calculators.  It is the intent that contestants enter the Finals area clothed with no carry-ins except personalization items such as hats, stuffed mascots, and such.
3. Upon entering the contest arena, do not touch the work station or other facilities provided in the contest environment. Wait for instructions from the Contest Manager.
4. Each team will have a single workstation.
5. Team will be provided with the following items at the contest arena:
   • Teams’ 25 page reference material.
   • Printout of contest problem set.
   • Work station and Mooshak Login credentials.
   • Rough paper and pen
6. All the queries related to the problem set and Mooshak contest server should be asked of the judges via Mooshak.
7. A contestant may submit a claim of ambiguity or error in a problem statement by submitting a clarification request to a judge. If the judges agree that an ambiguity or error exists, a clarification will be issued to all contestants.
8. Any needs or queries related to contest environment may be asked of the lab volunteers (Interaction with the volunteers must be minimum during the final contest).
9. Keep all discussions within the team.
10. Communication between teams is not permitted during the contest.
11. Only one team will be permitted to go out of the contest arena at any given time.
12. Documentation for STL and Java will be provided.
13. Judges' decisions are final.
14. While the contest is scheduled for five hours, the regional contest director has the authority to alter the length of the contest in the event of unforeseen difficulties. Should the contest duration be altered, every attempt will be made to notify contestants in a timely and uniform manner.
15. A team may be disqualified by the regional contest director for any activity that jeopardizes the contest such as dislodging extension cords, unauthorized modification of contest materials, or distracting behavior.
16. During the contest the contestants can make clarification requests on the problem statements. The clarification request must exactly identify the part of the problem statement that the team considers ambiguous, together with the possible interpretations. The Jury encourages contestants to use the sample input and output for resolving (apparent) ambiguities.
17. When the Jury responds to the clarification request, the team receives its "Clarification Request" with the answer. If the clarification request is incorrect or the answer is clear from the problem description, the Jury answers "No comments". If the Jury agrees that there is an ambiguity or error in the problem statement, a clarification will be issued to all teams.
18. At least six problems will be posed. So far as possible, problems will avoid dependence on detailed knowledge of a particular applications area or particular contest language.
19. During the contest, teams solve the posed problems. A solution is a program (single source file, not executable) on one of the allowed programming languages. Different problems may be solved using different programming languages.
20. Solutions are submitted for judging during the contest using the contest software. Solutions to problems that were submitted for judging are called runs. Immediately after submission of any run, the team may continue to work on other problems. A minimum time of 2 minutes between submission runs will be enforced.
21. Runs are NOT allowed to:
    • access the network;
    • work with any files except those explicitly specified in the problem statement;
    • attack system security;
    • execute other programs and create new processes;
    • change file system permissions;
    • work with sub directories;
    • create or manipulate any GUI items (windows, dialog boxes, etc);
    • work with external devices (sound, printer, etc);
    • do anything else that can stir up the evaluating process and the contest.
22. All submissions are open to scrutiny by anyone – in fact, we may publish all submissions on our website, where anyone may access them.
23. Run Evaluation: Each run is judged as accepted or rejected.
    • The run is evaluated by executing it on a secret set of tests, common for all teams. A run is accepted, only if it gives correct answers to all tests.
    • Evaluation is performed automatically, that is why a program should respect formats of input and output files described in the problem statement. If not explicitly stated otherwise, all input data are considered to be correct and satisfying all restrictions from the problem statement.
24. The time limit is the maximum execution time for the set of test.
25. The memory limit is the maximum amount of memory that a run may utilize.

1. Practice contest aims to make contestant familiar with the contest environment. This is not a contest to check the skill of contestants.
2. Learn about the Contest Server Mooshak.
3. You can submit the solution more than once to learn more about the error status generated by the Contest Server Mooshak.
4. Check all if the software (Editor, debugger etc) the may be used during the contest is available in the contestants machine.
5. Use the feedback form available to report about the changes required or issues faced.

1. The problem is considered solved by the team, if it is accepted by the contest software, not rejected by the Jury.
2. The time consumed for a solved problem is the time elapsed from the beginning of the contest to the submission of the first accepted run for this problem (in minutes) plus 20 minutes for every other run for this problem before the accepted one. For an unsolved problem no time consumed is computed.
3. The total time is the sum of the time consumed for each problem solved.
4. Teams are ranked according to the number of solved problems. Teams that solve the same number of problems are ranked by the least total time and, if need be, by the earliest time of submittal of the last accepted run.
5. Contestants and observers will see preliminary results of all teams during the contest. Contestants may see the results on their computers, observers - on the monitor outside the competition area.
6. According to the traditions of the competition, to encourage interest in the award ceremony, updating of the current information on results will be stopped 45 minutes before the end of the contest.

1. The Jury is solely responsible for determining the correctness of runs. Its decisions are final and may not be appealed.
2. If irregularities or misconduct are observed during the contest, team members or coaches should bring them to the attention of the contest officials so that action may be taken as soon as possible.

g++ -Wno-deprecated -w <filename.cpp>

gcc -w -lm <filename.c>

Compile:         javac -g:none -Xlint -nowarn <filename.java>
Execute:         java -client -Xmx64m <filename>

1. vim                 Version - 7.1
2. gedit              Version - 2.22.3
3. emacs            Version - 21.4.1
4. kate               Version - 2.5.10
5. kdevelop        Version - 3.5.3
6. Net Beans      Version - 6.7
7. Ecllipse           Version - 3.5

1. gdb                 Version - 6.8
2. ddd                 Version - 3.3.0
3. valgrind          Version - 3.3.11

1. Default Man pages in Linux
2. Java Documentation
3. C++ Standard Template Libraries