DMOPC '19 March Contest

This round will be rated
on join
, a change from previous contests.

Welcome to the sixth and last DMOJ Monthly Open Programming Competition of the 2019-2020 season!

The problem writers this time are george_chen, KevinWan, Tzak, little_prince, and richardzhang.

Please note that this contest will be full feedback.

This round will be rated for all participants.


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

This contest will consist of 6 main problems, the difficulty of which may range anywhere from CCC Junior to CCO level.

This contest will feature a 7-th problem (Problem 0) for students who are just getting started with programming.

Some problems offer partial marks in the form of subtasks. If you cannot solve a problem fully, we encourage you to go for these partial marks.

You will have 3 hours to complete the contest. After the contest window begins, you may begin at any time. Once you enter the contest, your personal timer will start counting down and you will be able to submit until 3 hours from when you started, or until the hard deadline (23:59:00 EDT of Mar. 29th), 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:

  • Ties will be broken by the last submission time that increased your score plus penalties. The first submission time of your highest score will be used.
  • Each non-AC (excluding Compiler Errors) submission will incur a penalty of 5 minutes.
  • It is not guaranteed that the problems will be in order of increasing difficulty. Reading all of the statements is recommended.
  • Remove all extra debugging code and/or input prompts from your code before submitting. The judge is very strict — most of the time, it requires your output to match exactly.
  • Do not pause program execution at the end. The judging process is automated. You should use stdin / stdout to perform input / output, respectively.
  • It is guaranteed that all the problems will be solvable with C++.

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 and Discord.


Due to rampant issues with cheating on contests that has happened recently, any suspicious behavior during the contest window may result in your rating being impacted negatively. Such behavior includes, but is not limited to:

  • Registering for the contest with at least two accounts.
  • Participating in the contest with an account that is not your primary account.
  • During the contest window, talking about the contest in more detail than answering a yes/no question about whether one participated in the contest. This includes, but is not limited to, posting spoilers about the contest and public speculation of the contest.
  • Attempting to exploit bugs in the platform to subvert the constraints of the contest.

Punishments may include performance being unrated or, for more serious infractions, being forcibly ranked at the bottom of the scoreboard.

At the end of the contest, you may comment below to appeal a judging verdict. In the case of appeals, the decision(s) of DMOJ staff is final.



Comments