It's that time of the (school) year again, and to celebrate, we present the Back to School '17 contest! Get back into your tip top programming shape and start the school year with a new rating!
The problem writers of this contest are, , and .
Back to School '17 will consist of 8 problems, with difficulty ranging between CCC Junior to IOI level. The contest questions have a wide range of difficulty, 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.
Contestants can participate in any 4 hour window between the 48 hour period of Saturday, September 9 to Sunday, September 10 EDT. Once you enter the contest, you will be able to submit until 4 hours from when you started, or until the hard deadline (September 11, 12:00 AM EDT), whichever comes first
Of course, it is forbidden to use multiple accounts to participate, and it is also forbidden to discuss the problems and/or their solutions with other people during the entire contest period.
Due to the large contest time window, we will be using a pretest/systest format in order to prevent cheating. On problems 5-8, when you submit, you will receive your result on some of the test data, called preliminary tests (pretests). After the contest, we will rejudge all solutions on the complete set of test data, and that will determine your final score. Note that getting AC on pretests does not ensure that you will pass system testing.
The pretests may be weak, so be sure to check the correctness and complexity of your solutions! You might also want to constant optimize to prevent TLEing by a small margin. In particular, non-AC submissions on the pretests will likely result in a score of 0 on the systests.
This contest will be rated for contestants with at least one submission.
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++ and Java.
Read carefully, and try to attempt all the problems. They may not be as hard as they seem and you may get partial points!
At the end of the contest, you may comment below to appeal a judging verdict. In the case of appeals, the decision(s) of staff is final.
|Back To School '17: 🅱aram🅱e||3p||42.0%||222|
|Back to School '17: Avalon||5p||30.3%||201|
|Back To School '17: Physics||5p||16.5%||121|
|Back To School '17: Wet Mud||10p||10.7%||81|
|Back to School '17: New English||12p||10.9%||27|
|Back to School '17: Sour Candy||15p||34.1%||46|
|Back to School '17: Hot and Cold||20p||20.0%||36|
|Back to School '17: Big Integer||35p||2.8%||96|