THICC '17

Felt like you've done nothing this summer? Want to exercise your mind for the upcoming school year? Scared for upcoming technical interviews or preparing for CCC? Want to feel smarter than your friends? Do you want Amazon Gift Cards? Want to write a contest named after a meme?

The Toronto Hackers Informatics Computing Competition is an online three hour contest, consisting of six problems of a large range of difficulty. It can be written anytime from 11 AM to Midnight. It'll be similar format to Google Code Jam or the CCC.

THICC

The problem writers this time will be kipply, leonchen0613, and Kirito.

The pretest/systest format will not be used. This means that submissions will be judged on the full set of data during the contest. However, partial output will be disabled.

This contest will not be rated.


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

This contest will consist of 6 problems, the difficulty of which may range anywhere from CCC Junior to CCO level.

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 3 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 3 hours from when you started, or until the hard deadline (midnight EST of Aug. 5th), 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.
  • 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 stdin / stdout to perform input / output, respectively.
  • It is guaranteed that all the problems will be solvable with 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 DMOJ staff is final.



Comments

There are no comments at the moment.