It is well known thatis always angry. To vent out his anger, he decided to create yet another contest with and . This time they also roped in to help create some problems.
With the CCO quickly approaching, this contest will be a great way to practice your problem solving skills.
Here are the parameters of the contest:
- Contest duration: 4 hours.
- Number of problems: 7, full feedback. Each problem will be worth 100 points, with some problems offering partial marks in the form of subtasks.
- Rated for opening the contest. Unlike with other contests which require making a submission for the contest to be rated, opening the contest and being able to read the problems will cause the contest to be rated.
- Scoreboard will be public.
- No submission penalty.
- Ties will be broken by the last submission time that increased your overall score.
- Checkers for problems: Unless otherwise specified,
identical. The contest will follow the standard convention of having all lines terminate in a
\ncharacter, with no trailing whitespace.
Furthermore, users are forbidden from using multiple accounts or collaborating during the entire contest duration. Any suspicious behaviour during the contest window may result in a severe penalty including, but not limited to, being placed at the bottom of the scoreboard. 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.
The problem setters for this contest are, , and .
Special thanks to, , and , for providing feedback and testing the problems.
This contest will consist of problems, the difficulty of which is similar to a typical Wesley's Anger Contest.
You will have 4 hours to complete the contest. After the contest window begins (April 26th, 09:00 EDT), 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 4 hours from when you started, or until the hard deadline (April 28th, 23:59 EDT), whichever comes first.
After joining the contest, you can 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:
- 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
stdoutto perform input / output, respectively.
- It is guaranteed that all the problems will be solvable with C++. All problems have a time limit of at least 2x the reference solution, which is written in C++ and uses this template for I/O. If you're unable to see the template, you must solve this problem. Problems that have been tested in multiple languages may have language specific time limits.
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.