Hello Codeforces Community, TOKI Open Contest is back again! :D
We would like to invite you to participate in this TOKI Open Contest March 2018. TOKI Open Contest is Indonesian (bi-)monthly online programming contest. You may see the January 2018 contest here! :)
Every problem is written in both Bahasa Indonesia and English. The contest will be divided into two divisions: Division 1 and Division 2. It is pretty similar to the divisions in Atcoder (Beginner and Regular). You are free to register in any division (it's extremely OK if you are a Div2 Codeforces user and register to our Division 1 contest)! The expected difficulties of the problems are much the same with Atcoder's contest problems.
TOKI Open Contest March 2018 will be held on Saturday, 24 March 2018, 19.00 — 21.00 Western Indonesian Time (UTC+7). This contest is written by Jonathan Mulyawan Woenardi (jonathanwoenardi); also monitored and supervised by Agus Sentosa Hermawan (aguss787), Ammar Fathin Sabili (athin), Anthony Ng (anthonyhkf), and Muhammad Ayaz Dzulfikar (ayaze).
Several details related to the contest:
The contest will use ACM-ICPC scoring type and usual standard contest ACM-ICPC rule that is very strict about newline and whitespace.
For each division, there will be FOUR (4) problems with various difficulties but the weight for each problem is the same. The contest duration is 2 hours.
The problems are sorted by their expected difficulty from easy to hard. Participants are recommended to read all the problems.
Any non-Accepted submission will get 8 minutes penalty but it will only be counted after the respective problem got Accepted.
The rank will be sorted according to the most number of solves (problems with Accepted verdict). If there are ties, it will be determined by least (sum of solving time + sum of penalties). The rank will be separated for Division 1 and Division 2.
The allowed programming languages are C, C++11, Pascal, Python 3, and Java 8. However, please note that we do not ensure that every language can solve all the problems on the given time limit.
The contest will be held on https://competition.ia-toki.org/contests/262 for division 1 and https://competition.ia-toki.org/contests/263 for division 2. Registration is already opened at the same place. Registering the contest requires a TLX (http://competition.ia-toki.org) account. You may need to register for an account if you don't have one.
Wish you all good luck and have fun! See you at the leaderboard! :D
UPD 1 : The contest will be held in less than 24 hours, make sure you are already registered! :D
UPD 2 : The contest is over, thanks for participating the TOKI Open Contest March 2018! :D
This contest has 18 contestants in Division 1 and 33 contestants in Division 2 with at least one submission.
The following are the winner of the TOKI Open Contest March 2018:
Division 1:
robinyu solved 3 problems with 161 minutes total penalty.
jonathanirvings solved 3 problems with 185 minutes total penalty.
Yehezkiel solved 2 problems with 140 minutes total penalty.
Division 2:
Reiva5 solved 4 problems with 264 minutes total penalty.
halohalo solved 4 problems with 267 minutes total penalty.
coderbodoh solved 3 problems with 141 minutes total penalty.
Congratulation to winners! :D
The problems are available at https://training.ia-toki.org/problemsets/108/problems for upsolving. See you at the next TOKI Open Contest! :D
Are you kidding? It's not 2003 anymore, although Putin is still in power in Russia. Please use normal standard checkers in polygon style, for example.
Agree, statement "very strict about newline and whitespace" now is irrelevant to world finals.
Thanks for the feedback, :D
We'll look into this. As our TLX is not only supporting competition but also trainings and problemsets gate too, there may be some tasks requiring this constraint (e.g. print these star pattern). And also, there are many classic ICPC problems too here which are being imported. Some of them are intended to be exact having the same behaviour as in the real contest itself. That's why the default grading is like this.
But anyway, it'll be discussed more with our developers. Many thanks for the advice, :)