Welcome to the senior division of the Bloor C.I. Programming Contest!
The problem setters areand .
Thanks toand for helping organize the contest.
Thanks to, , , , and for testing and feedback on the problems.
This contest will be rated for all participants.
Here are the parameters of the contest:
- Contest duration: 3 hours
- Number of problems: 6, full feedback (you will see the results of your submissions instantly).
- Expected problem difficulty: slightly easier than a typical DMOPC from the past year.
- Problems will be ordered approximately in increasing difficulty. Reading all statements is still recommended.
- Some problems may offer partial marks, often in the form of subtasks.
- Ties will be broken by the maximum submission time that increased score with no penalties.
- 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.
- 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
\ncharacter, with no trailing whitespace.
- Interactors: unless otherwise specified, assume that all interactors are not adaptive.
- It is guaranteed that all problems will be solvable in C++.
Furthermore, users are forbidden from using multiple accounts or collaborating with others during the entire duration of the contest. 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.
You will have 3 hours to complete the contest. After the contest window begins (June 18th, 00: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 3 hours from when you started, or until the hard deadline (June 22nd, 00:00 EDT), whichever comes first.
After joining the contest, you can proceed to the Problems tab to begin.
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.
|BPC 1 S1 - Homework Questions||5||16.6%||128||Editorial|
|BPC 1 S2 - Train Commute||12p||6.5%||38||Editorial|
|BPC 1 S3 - Bus Stops||17p||13.2%||23||Editorial|
|BPC 1 S4 - Binary Matrices||25p||8.7%||8||Editorial|
|BPC 1 S5 - Temple||25p||7.3%||10||Editorial|
|BPC 1 S6 - Painters||30p||9.2%||6||Editorial|