## TLE '16 February Contest (Mock CCC) Junior Division

Welcome to the sixth Trudeau Logic Evaluation of the 2016-17 school year!

The problem writers/testers of this round are ChaSiu, jlsajfj, leonchen0613, and splacorn.

The TLE will be a 3-hour virtual contest, which will allow contestants to participate in any 3-hour window between 9:00 AM EST and 11:59 PM EST on February 20, 2017. Of course, it is forbidden to use two accounts to participate, and it is also forbidden to discuss the problems and/or their solutions with other people during the entire contest period.

This contest will differ from the other TLEs in format. In preparation for the Canadian Computing Competition (CCC), for this month, the TLE will follow the CCC format. This means that there will be two divisions, 5 distinct problems per division, 15 points per problem, and no system testing.

This contest will be unrated.

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

The contest consists of 5 questions with a wide range of difficulties, and you can get 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 problem difficulty is intended to reflect the difficulty of the CCC Junior. 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 (February 20, 11:59 PM EST), 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 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 our staff is final.