Another Contest 9

Hello, welcome to another contest! Here are the parameters of the contest:

  • Contest duration: 3 hours.
  • Number of problems: 5, full feedback. There are no subtasks. Problems are presented in roughly increasing order of difficulty.
  • This contest will be rated on open for all previously unrated users and all users with rating of at most 2599.
  • Scoreboard will be hidden.
  • Contest format: AtCoder format, no wrong submission penalty. Ties will be broken first by the number of points you have and second by the time of your latest first AC on a problem.
  • Number of submissions allowed per problem: 50.
  • Checkers for problems: Unless otherwise specified, identical. The contest will follow the standard convention of having all lines terminate in a \n character.
  • Organizers for this contest: maxcruickshanks.
  • Testers for this contest: arknave, d, dawnstar63, and y0105w49.
  • It is guaranteed that all the problems will be solvable with C++, and all time limits will be at least 2x the runtime of the reference solution.

Clarification requests for the contest must be routed through the clarification system provided on DMOJ and not through other channels, including but not limited to Slack or Discord. Furthermore, all clarification requests will be handled the way they normally are in IOI. Note that, in particular, clarification requests must come in the form of yes/no questions.


Before the contest date, you may wish to check out the tips and help pages.

The contest consists of 5 questions with a range of difficulties. It is highly recommended to read all of the problems. You will have 3 hours to complete the contest. After the contest window begins, you may begin at any time. Your personal timer will start counting down, and you can submit until 3 hours from when you started, or until the hard deadline, whichever comes first.

After joining the contest, you proceed to the Problems tab to begin. You can also go to Users if you wish to see the rankings.

We have listed below some advice as well as contest strategies:

  • Start from the beginning.
  • Remove all extra debugging code and/or input prompts from your code before submitting. The judge is strict — your output must match the judge's output exactly.
  • Do not pause program execution at the end. The judging process is automated. You should use stdin / stdout to perform input / output, respectively.


Comments


  • 0
    maxcruickshanks  commented on July 11, 2022, 4:13 a.m.

    Hi, everyone! Unfortunately, the DMOJ site experienced some downtime from around July 10, 8:22 pm to July 10, 8:52 pm EDT. During this time, either the site was inaccessible, or the judges were unavailable. If any contestant affected by this downtime wishes to be unrated from the contest, they may do so by sending an email to contact@dmoj.ca. We apologize for the inconvenience and hope you still enjoyed the contest.