Hello DMOJ! We are excited to host the new Victor’s Programming Exhibition (VPEX)! The contest will take place during a 2.5-hour window between 3:00 pm EST of Feb. 7th, 2020 to 3:00 pm EST of Feb. 10th, 2020. To help you prepare for the CCC, this contest will feature 6 problems with an approximate difficulty ranging from CCC Junior 1 to CCC Senior 5. The problem setter for this contest is. This contest will not be rated.
- Contest duration: 2.5 hours.
- Number of problems: 5 main problems and 1 beginner problem, with subtasks.
- Not rated.
- Scoreboard will be visible.
- You will be allowed unlimited submissions.
- The contest will be run with the AtCoder format.
- Problem setter:
- Testers: , , ,
Due to rampant issues with cheating on contests that has happened recently, the DMOJ staff reserves the right to punish any suspicious behavior during the contest window. 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.
- Attempting to reverse engineer the test data.
Punishments may include performance being forcibly ranked at the bottom of the scoreboard or being banned from participating in the contest altogether.
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.
This contest will consist of 5 main problems, the difficulty of which may range anywhere from CCC Junior to CCC Senior Level (in preparation for the actual CCC).
This contest will feature a 6-th problem (Problem 0) for students who are just getting started with programming.
Some problems offer partial marks in the form of subtasks. If you cannot solve a problem fully, we encourage you to go for these partial marks.
You will have 2.5 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 2.5 hours from when you started, or until the hard deadline (15:00:00 EST of Feb. 10th, 2020), 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:
- Ties will be broken by the last submission time that increased your score plus penalties. The first submission time of your highest score will be used.
- Each non-AC (excluding Compiler Errors) submission will incur a penalty of 5 minutes.
- 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++.
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 Slack and Discord.
|VPEX P0 - Pizza||3p||37.0%||586||Editorial|
|VPEX P1 - War on Two Fronts||3p||43.3%||269||Editorial|
|VPEX P2 - Darcy Parties||3p||64.6%||258||Editorial|
|VPEX P3 - Coding Club||12p||4.5%||23||Editorial|
|VPEX P4 - Etopika||12p||17.8%||78||Editorial|
|VPEX P5 - Points Redistribution||20p||21.1%||31||Editorial|