DMOPC '22 November Contest

Welcome to the second DMOJ Monthly Open Programming Competition of the 2022-2023 season!

The contest organizers this time are 4fecta, Riolku, and zhouzixiang2004.

UPDATE: Thanks for writing the contest! The problem writers this time were 4fecta, Riolku, Dormi, and yzhao123.

Thanks to kdrkdr, ThingExplainer, Dec0Dedd, azeng, Dormi, yzhao123, Maillew, Marshmellon, Nils_Emmenegger, dxke02, WilliamWu277, and X_Ray for testing and feedback on the problems.

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 problems, the difficulty of which may range anywhere from CCC Junior to CCO level.

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 (00:00:00 EST of November 29th), whichever comes first.

After joining the contest, you proceed to the Problems tab to begin.

Here are the parameters of the contest:

  • Some problems offer partial marks in the form of subtasks. Specifically, for problems with subtasks, batch dependencies will be structured as follows: if the set of cases possible for a subtask B is a superset of the cases for a previous subtask A and any case in A produced a non-accepted verdict, the cases in B will not be executed.
  • Ties will be broken by the maximum submission time that increased score with no penalties.
  • A maximum of 50 submissions will be allowed per problem.
  • Scoreboard will be hidden, until your window is over. Divulging the contents of the scoreboard to participants who have not finished their window is an offense, the punishments of which are listed below.
  • Problems will be approximately increasing in difficulty, and will all have full feedback. Reading all of the statements is recommended.
  • Checkers: unless otherwise specified, standard.
  • Interactors: unless otherwise specified, assume that all interactors are not adaptive.
  • Rated for opening the contest. Being able to read the problems will cause the contest to be rated.
  • 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.

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

  • 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.
  • Python users are recommended to use PyPy 2/3 over Python 2/3 when submitting.

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

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:

  • Divulging the contents of the scoreboard to participants who have not finished their window.
  • 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.
  • Attacking the judge infrastructure, other contestants, or contest personnel within or after your window.

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.

Problems

Problem Points AC Rate Users Editorials
DMOPC '22 Contest 2 P1 - DMOPC Crisis 5p 15.5% 315 Editorial
DMOPC '22 Contest 2 P2 - Line Trace 7p 34.1% 167 Editorial
DMOPC '22 Contest 2 P3 - Good Permutations 12p 20.2% 127 Editorial
DMOPC '22 Contest 2 P4 - Falling Leaves 20p 23.7% 31 Editorial
DMOPC '22 Contest 2 P5 - Beautiful Bins 30 8.0% 12 Editorial
DMOPC '22 Contest 2 P6 - Yogyakarta Elevators 25p 9.3% 35 Editorial

Comments


  • -4
    BLAHAJ  commented on Dec. 4, 2022, 11:26 p.m.

    why do some people have -9999 points


    • -21
      volcano  commented on Dec. 4, 2022, 11:54 p.m. ← edit 2

      This comment is hidden due to too much negative feedback. Show it anyway.


      • 4
        Mystical  commented on Dec. 31, 2022, 3:44 a.m.

        This did not age well...


      • 3
        Mystical  commented on Dec. 5, 2022, 1:18 a.m.

        the irony


  • 6
    sortSlave  commented on Nov. 29, 2022, 1:03 p.m.

    Yzhao123 so cool


  • -11
    _wcipeg  commented on Nov. 24, 2022, 12:31 a.m.

    This comment is hidden due to too much negative feedback. Show it anyway.


    • 61
      dnialh_  commented on Nov. 24, 2022, 1:37 a.m.

      In light of your feedback, we have decided to delay the contest by 11 months. We hope this causes no inconvenience.


      • 4
        badasian  commented on Nov. 25, 2022, 5:55 p.m.

        why??? :(


        • -2
          Dan4Life  commented on Dec. 1, 2022, 1:47 p.m.

          A lesser evil :)