Classic Sample

Current time:	Sunday, February 5, 2023 16:12:58 CST
Start time:	Saturday, March 19, 2022 9:49:25 GMT-0500
Duration:	3:00:00

This is a sample programming contest. Had it been an actual contest you might expect something like the following rules.

Rules

• Your team may only use one computing device.
• Your team may not communicate with other humans.
• If you do something FastCode.Rocks deems unacceptable your team will be disqualified.
• Examples of unacceptable things include, but is not limited to:
  • cheating or appearing to cheat
  • language that offends others
  • attempting to communicate with non-team members
• FastCode.Rocks judges' decisions are not final.

Submissions

Submissions become the property of FastCode.Rocks. For more information see our policies.

All input will be from standard input. All output should be to standard output.

These are the only results that you will get back:

• accepted Your program was judged as correct! Quit working on it. Go on to another problem.
• rejected: compile error The judge was unable to compile your program.
• rejected: run-time error Your program crashed while running on the judge's system.
• rejected: time limit exceeded Your program ran for more than 30 seconds on the judge's system.
• rejected: wrong answer Your program produced output that did not match the judge's expected output.
• rejected: wrong format Your output has a minor formatting issue.
• rejected: other You have done something unexpected.

Clarifications and Corrections

Normally when a team believes the judges are wrong, the team has not consider all possible data sets or has misunderstood the problem.

If you believe a problem statement is in error, or is ambiguous, or a mistake was made judging your submission, you may submit a clarification request. Clarifications will be answered in one of two ways:

• "no comment" response to team, or
• announcement to all teams via contest pages.

In the event judges determine a judging error has occurred, judges will make every effort to fairly rectify the situation. This may include rejudged all submissions to give credit for the earliest correct submission.

Scoring

Scoring is intended to be similar to ICPC. The team with the most problems solved wins. Fewer penalty minutes will be used to resolve ties. Each minute, or fraction of a minute, a problem remains unsolved is considered a penalty minute. Each incorrect submission you make counts as twenty penalty minutes. Penalty points for unsolved problems will NOT be figured into this score.