Yet Another Contest 7

YAC Banner

Welcome to yet another Yet Another Contest!

The problem setter is Josh.

Thanks to jeroenopdebeek, Snowfall, andy_zhu23, BucketPotato, Zirui, azeng, thomas_li and moonpole for testing, feedback, and assistance with the problems!

Special shout-out to Riolku, RandomLB and Nils_Emmenegger for helping with organizing the contest!

The contest will be rated for all participants with a rating under 3000.

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 EDT of August 18th), 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. These dependencies will not be noted in the problem statements.
  • Number of problems: 6, full feedback (you will see the results of your submissions instantly).
  • Number of submissions allowed per problem: 50.
  • 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.
  • Ties will be broken by the maximum submission time that increased score with no penalties.
  • Problems will be approximately increasing in difficulty, and will all have full feedback. Reading all of the statements is recommended.
  • Rated for opening the contest. Being able to read the problems will cause the contest to be rated.
  • Checkers: unless otherwise specified, standard.
  • Interactors: unless otherwise specified, assume that all interactors are not adaptive.
  • It is guaranteed that all problems will be solvable with C++, Java, and Python.

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, unless otherwise specified.

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
Yet Another Contest 7 P1 - Page Turning 5p 19.6% 286 Editorial
Yet Another Contest 7 P2 - Coprime Grid 10p 22.3% 207 Editorial
Yet Another Contest 7 P3 - No More Math Homework 12p 16.3% 90 Editorial
Yet Another Contest 7 P4 - Paparazzi 17p 8.5% 49 Editorial
Yet Another Contest 7 P5 - Egg Dropping 25p 1.5% 3 Editorial
Yet Another Contest 7 P6 - Arithmetic Sequence Data Structure 25p 7.6% 8 Editorial

Comments


  • 1
    farmersrice  commented on Aug. 18, 2023, 4:35 a.m.

    I am new here. How to upsolve? What does this points table at the bottom of the page mean?


    • 1
      Josh  commented on Aug. 18, 2023, 6:04 a.m.

      Point values are a measure of problem difficulty (although the difficulty of a problem is quite subjective). They contribute towards the number of points that you've earned (check 'Total points' on https://dmoj.ca/user, and see https://dmoj.ca/post/103-point-system-rework for more details).

      The problems have now been made public, so you can submit to them freely.


      • 0
        farmersrice  commented on Aug. 18, 2023, 7:39 a.m.

        Thanks, I have successfully found how to upsolve. I see that other people seem to have upsolved during the contest time, since p5 and p6 have solves from hours/days ago but nobody solved in contest. How can I do that? The problems were not visible after my submission time ended.


        • 3
          spheniscine  commented on Aug. 18, 2023, 8:27 a.m.

          If you participated in the contest, you could upsolve the problems after your contest window but before the contest end by "spectating" the contest.