TSS Programming Competition 2 - December

Hello, welcome to the second Thornhill Secondary School Programming Competition! You will be able to start any time during the break, and have a 3-hour window.

  • Contestants may not consult the Internet outside of accessing the relevant parts of the contest via the TSSOJ platform or consulting language documentation, and contestants may not use any prewritten code.
  • Contest duration: 3 hours.
  • Number of problems: 5, some with subtasks. As per AtCoder format, every submission before your earliest highest-scoring submission will incur a five-minute penalty. However, submissions on problems you do not score on do not penalize you.
  • This contest will be Rated.
  • No submission limit.
  • Problem setters for this contest: Encodeous, Eric_Zhang, and HARRIBO

Clarification requests for the contest can either be routed through the clarification system provided on TSSOJ or by direct messaging a club exec on Discord. Note that, in particular, clarification requests must come in the form of yes/no questions.

Any suspicious behavior will result in being forcibly ranked at the bottom of the scoreboard.

The contest consists of 5 questions in random order of difficulty. It is highly recommended to read all of the problems. You will have 3 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 3 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 by the sum of times used to solve the problems starting from the beginning of the contest. The last submission time of your highest score will be used.
  • 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++ and Java.

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.


There are no comments at the moment.