Sunday, March 6, 2022
Online Contest
Contest announcement mailing list
Follow @NAPCNews

1. The Contest will be held on March 6, 2022 at Online Contest.
2. Prizes: TBA.
3. The programming languages and compilers used will be: C/C++ (gcc/g++/gnat) 6.1.1.; Java OpenJDK 1.8.0; python 2.7.12 and 3.5.1; Kotlin Debuggers will be: ddd 3.3 and gdb 7.9
4. Registration information: TBA.
5. See the full rules below about registering guests.
6. Teams may bring any printed material they wish, including books, language reference manuals, code printouts, contest problems and their solutions.
7. No electronic devices or media of any kind are permitted, including floppy disks, CDs, DVDs, calculators, pagers, pagers, PDAs, memory sticks, mp3 players, and CD players.

Please read the rules that apply to every region. Please pay special attention to the new rules, which are in red.

In addition to the general rules, there are additional rules specific to the Greater New York Regional contest. In cases where the specific rules disagree with the general rules, the specific rules take precedence.

These rules may be changed at any time and without notice. Changes in the rules does not entitle any team to a refund.

Eligibility

Please see the official rules here: http://icpc.global/regionals/rules

If you have any questions, or would like to ask for an exception, email the Contest Director. Note that all exceptions must be requested by March 2, 2021

Date, Time, and Environment

1. Contestants will have five hours to solve the six or more posed programming problems.
2. Contestants are drawn from the greater New York metropolitan area, including areas of New York, New Jersey, and Connecticut. The portion of New Jersey in this Region is all schools north of I-195. There is no strict definition for the portion of New York or Connecticut included.
3. The site has a capacity of 50 teams.
4. The languages used are: C, C++, Java, python2, python3. See above for version numbers.
5. Each team will be provided with one computer and access to all compilers and editors used in the contest. All teams will have comparable computing equipment.
6. The contest site will provide a printing facility that will be shared among the contestants. Printing will be done through the use of networked printing facilities shared by all teams.

1. TBA

1. The Contest Director is responsible for appointing a Site Director and Head Judge for the contest, and is ultimately responsible for all aspects of the contest.
2. The Site Director is responsible for all local contest arrangements, including the solicitation of on-site volunteers, procurement of rooms and equipment (including backup systems), and so forth. The Site Director will conduct a meeting with the contestants prior to the start of the contest to reiterate the contest procedures and explain any site-specific policies, and will distribute the official contest results to all teams that participate in the contest.
3. The Head Judge is responsible for coordinating all aspects of the judging effort. The Head Judge will explain the judging procedures and work with the other judges to distribute the contest judging and record-keeping responsibilities.

1. At least six problems will be posed.
2. Each team must have a faculty advisor and a coach, who may or may not be the same person. The coach need not be a member of the faculty. The faculty advisor needs to be able to verify the eligibility of the contestants on the team. The coach must accompany the team to the contest.
3. Coaches and guests will have no contact with their teams during the contest. The penalty for contact is immediate disqualification of all teams from that school.
4. Coaches will receive a copy of the problems once the contest has begun. If a coach suspects any ambiguity in the problem statements, he or she must report this to the Contest Director for an immediate ruling.
5. If the Contest Director or Head Judge decides that a clarification is necessary, the Site Director will disseminate this information to all teams.
6. The Contest Director, Site Director(s), the Head Judge, and the pool of team coaches present serve as the final authority for resolving all local contest matters.
7. No penalties will be assessed for obtaining printed listings during the contest. Local procedures for obtaining a listing will be explained by the Site Coordinator during the meeting of the contestants.
8. Everyone who attends the contest gives permission to the Region and any organization it designates to use their likenesses in electronic and physical publications.

1. Submission of problems will be electronic, with PC^2 version 9. Please read the Contestant's Guide.

1. Teams will not be given the test input files that the judges will use to determine program correctness.
2. Solutions to problems submitted for judging are called runs. Each run is judged as correct or incorrect, and the team is notified of the results. Incorrect runs will be marked with one of the following comments. They are listed in decreasing order of severity.
   1. file naming error: The file naming convention was not followed. Either the submission was incorrectly named, or the program did not read from / write to the correctly named file.
   2. compile error: The program did not compile.
   3. run-time error: The program did not run to completion.
   4. wrong answer: This means that the program compiled and ran, but produced incorrect output.
   5. time limit exceeded: The program did not finish executing within the 2 minute time limit.
   6. presentation error: The output was nominally correct, but was not in the correct format.
3. The Contest Judges are solely responsible for determining the correctness of submitted runs. In consultation with the Contest Judges, the Chief Judge is responsible for determining the winners of the contest. They are empowered to adjust for or adjudicate unforeseen events and conditions. Their decisions are final.
4. The final contest results will be announced following the contest by the Contest Director, Site Director, or Head Judge.
5. Although they are unlikely, the Contest Director will resolve ties by examining the quality of submitted solutions and number of incorrect submissions.

Last modified 15 September 2016. Please email with comments, questions, or corrections.