Yet Another Contest 2

Welcome to yet another Yet Another Contest!

The problem setters are Josh and RandomLB.

Thanks to andy_zhu23, cabbagecabbagecabbage, azeng, Snowfall and BucketPotato for testing, feedback, and assistance with the problems!

Special shout-out to Riolku and Nils_Emmenegger for helping us organize the contest!

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

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 April 5th), 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. If batch dependencies are in use, the subtask will specify which previous subtasks need to be passed in order for it to be evaluated. If batch dependencies are not in use, assume you must pass all previous subtasks in order for a subtask to be evaluated.
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, identical. The contest will follow the standard convention of having all lines terminate in a \n character, with no trailing whitespace.
Interactors: unless otherwise specified, assume that all interactors are not adaptive.
It is guaranteed that all problems will be solvable with C++.

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 2 P1 - Betting	5p	22.4%	263	Editorial
Yet Another Contest 2 P2 - Secret Sequence	7p	26.6%	139	Editorial
Yet Another Contest 2 P3 - Maximum Damage	10p	7.8%	62	Editorial
Yet Another Contest 2 P4 - No More Arithmetic	15p	15.1%	51	Editorial
Yet Another Contest 2 P5 - Mirror Maze	17p	28.9%	46	Editorial
Yet Another Contest 2 P6 - Travel Budget	20p	15.0%	39	Editorial

Comments

Lost commented on March 30, 2022, 8:01 p.m.

🦬🦬🦬
🦬🦬🦬🦬🦬🦬🦬🦬🦬🦬🦬🦬🦬🦬
🦬🦬🦬  🦬                   🦬
        🦬                  🦬
      🦬                  🦬
    🦬                  🦬
  🦬                  🦬🦬🦬🦬🦬🦬🦬
🦬                                     🦬

3

marwan58 commented on March 29, 2022, 3:50 p.m.

orz

3

martin226 commented on March 29, 2022, 4:05 a.m.

ORZ

3

henrybaolol9 commented on March 28, 2022, 8:49 p.m.

rating 📉

7

FlowerPollinator commented on March 29, 2022, 12:15 a.m.

-1

FlowerPollinator commented on March 29, 2022, 12:13 a.m. ← edited →

Sorry bro

0

gavin_chen commented on March 28, 2022, 11:19 p.m.

relateable

5

andy_zhu23 commented on March 28, 2022, 5:42 p.m.

Orz Orz Orz Orz Orz Orz Orz Orz Orz Orz Orz Orz Orz Orz Orz Orz Orz Orz

10

dawangk commented on March 28, 2022, 4:14 p.m.

I kinda feel skeptical due to the timing of the contest (03:00 window between April 1, 2022, 0:00 EDT and April 5, 2022, 0:00 EDT)

Still HYPE for the contest!!

7

ayay9 commented on March 28, 2022, 3:06 p.m.

Back to back rated contests :))))