Welcome to the third Generic Computer Contest!

It has long been said there is a certain group of people who excel in solving problems with hard templates, but cannot think their way out of a paper bag. Perhaps this shall prove them wrong?

The GCC will be a 4-hour virtual contest, which will allow contestants to participate in any 4-hour window between Apr 1, 12AM EDT and Apr 6, 12AM EDT.

The contest format will use the AtCoder contest format.

This contest will not be rated.

Before the contest date, you may wish to check out the tips and help pages. The contest consists of 3 questions with partial marks for partial solutions in the form of subtasks. If you cannot solve a problem fully, we encourage you to go for these partial marks. The difficulty of the problems may range anywhere from CCC Junior to IOI level. You will have 4 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 4 hours from when you started, or until the hard deadline (Apr 6, 12AM EDT), whichever comes first.

After joining the contest, you proceed to the Problems tab to begin.

Here are the parameters of the contest:

• Each problem will be worth 100 marks, and may offer partial marks in the form of subtasks.
• Number of problems: 3, full feedback (you will see the results of your submissions instantly).
• Scoreboard will be hidden, until your window is over.
• Ties will be broken by the maximum submission time that increased score with 5 minute penalties for each incorrect submission.
• Checkers: identical.
• 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 C++ over Python 2/3 when submitting.

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 the recent increase in the power of AI, all AI usage is banned. This includes, but is not limited to, ChatGPT and Copilot.