## Another Contest 5

Hello, welcome to a DMOJ contest! We're glad to invite you to another contest! Here are the parameters of the contest:

• Contest duration: 2 hours.
• Number of problems: 5, full feedback. Each subtask on each problem is worth one point. As per AtCoder format, every submission before your earliest highest scoring submission for a given problem will incur a five minute penalty. However, submissions on problems you do not score on do not penalize you.
• There will be an interactive problem.
• Rated for all users who open the contest and have rating less than 2200.
• Scoreboard will be hidden.
• Contest will run on AtCoder format. This means that ties will be broken first by the number of points you have, and second by the time of your latest earliest highest scoring submission on a problem, plus five minutes per submission on a problem prior to scoring on it.
• Number of submissions allowed per problem: 50.
• Checkers for problems: Unless otherwise specified, identical. The contest will follow the standard convention of having all lines terminate in a \n character.
• Testers for this contest: arknave, Cthulhu, kobortor, and neal.

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, Messenger, or 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 performance being disqualified and pushed to the bottom of the scoreboard. Such behavior includes, but is not limited to:

• Registering for the contest with at least two accounts.
• During the contest window, talking about the contest in more detail than answering a yes/no question about whether one participated in the contest.
• Attempting to exploit bugs in the platform to subvert the constraints of the contest.

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

The contest consists of 5 questions with a range of difficulty. It is highly recommended to read all of the problems. You will have 2 hours to complete the contest. After the contest window begins, you may begin at any time. Your personal timer will start counting down, and you will be able to submit until 2 hours from when you started, or until the hard deadline, 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:

• Start from the beginning. Ties will be broken as specified at the top of the contest description.
• Remove all extra debugging code and/or input prompts from your code before submitting. The judge is strict — your output must match the judge output 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++. All problems have a time limit of at least 3x the reference solution, which is written in C++.

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

## Problems

Problem Points AC Rate Users
Another Contest 5 Problem 1 - Goat Fence 3p 25.9% 186 Editorial
Another Contest 5 Problem 2 - Great Graffiti 3p 19.8% 115 Editorial
Another Contest 5 Problem 3 - Cutting Cheese Costs 5p 23.4% 132 Editorial
Another Contest 5 Problem 4 - Tudor Interacts With Poop 15p 15.7% 22
Another Contest 5 Problem 5 - Another Cheese Problem 12 16.4% 40 Editorial
Another Contest 5 Problem 6 - Tudor Interacts With Poop (Sample) 1p 8.4% 11

• crimsonred  commented on July 23, 2019, 5:48 a.m.

For testing my code on problem 4 in the contest, I had submitted it on the sample problem and it had given WA on the sample test case. After the contest I submitted the exact same code on problem 4 and it gave AC. In the contest I didn't submit on problem 4 because I was getting WA on the sample problem which shouldn't have happened. Please look into this.

Also, it looks like this problem has been copied from here: https://www.codechef.com/FEB19B/problems/MANRECT.

• xiaowuc1  commented on July 24, 2019, 12:14 p.m. edit 3

There was an inconsistency between the sample variant of the problem and the real variant, and submissions that should have received a samples passed verdict did not. This issue was flagged early in the contest but was not addressed during the contest window so that all contestants would have the same experience with the problem, as several contestants had already solved the problem properly in spite of the inconsistencies.

We are rectifying this issue as follows:

1) All submissions to the sample problem will be judged on the real data. Penalty will be charged on that problem as per normal, except that submissions which failed on samples will not count for penalty. This fairly closely emulates the behavior cycle of officially submitting every submission that passed samples, which is a reasonable strategy that contestants would have followed in a real contest scenario.

2) If a contestant earns a positive score on both problems, we will take the earliest time of AC and manually disqualify the latter submission to avoid double-scoring. We will not attempt to collate submissions across both problems.

If you were adversely affected by this issue, you may request to be unrated. To be eligible for unrating for this reason, you must have scored a positive amount of points on either version of this problem.

• Plasmatic  commented on July 25, 2019, 12:14 a.m. edit 2

This negatively affects anyone who thought that you could submit to F without penalty.

As in, anyone who read the rules.

EDIT: Issue Resolved