Hi Codeforces community! :D
We're excited to invite you to TOKI Regular Open Contest (TROC) #6!
Key details:
- Rated
- Contest link: https://tlx.toki.id/contests/troc-6
- Time: 16 June 2019, 19:05 UTC+7
- Style: ICPC-style, 10-minute penalty per wrong submission
- Writers: athin, ayaze
- Duration: 2.5 hours
- Problems: 7
- Allowed languages: C, C++11, Pascal, Java, Python 3
This will be "the last round of TROC" to generate the initial ratings for the contestants.
Everyone can join (combined divisions), and the problemset is expected to be easier than usual.
Please register to the contest, and we hope you will enjoy TROC #6! :D
UPD: Contest is over! Top 5:
We want to congratulate AMnu to be the first red coder in TLX — TOKI Online Judge! XD
We also want to congratulate Bruteforceman to be the only solver of problem G! XD
Additionally, we would like to thanks prabowo, suhendry, and fushar for testing and proofreading! :D
Editorial is available here (in both Bahasa Indonesia and English).
You can upsolve the problems at https://training.ia-toki.org/problemsets/166/problems.
Thanks for participating and see you on the next chance! :D
clash with ABC 130, please change the time if possible, thanks
Our initial schedule was on 15 June, which is acrually clashed with another Atcoder's diverta 2019 Programming Contest 2.
We then rescheduled this to the next day (16 June). So it's rather unfortunate that we may not reschedule this again for the second one.
A friendly bump!
The contest will be started in less than 48 hours! :D
this is my first time to doing TROC, any advice ? or it is just like other contest generally.
If you are familiar with ICPC, then TROC is similar with it (except the scoreboard is not frozen).
Compared to CF, TROC:
The last bump, the contest will be started in around 30 minutes!
Hope to see the first red coder of TLX — TOKI Online Judge! :D
Auto comment: topic has been updated by athin (previous revision, new revision, compare).
You just assumed a person will have same handle on TLX and CF? tasmeemreza is actually Bruteforceman. -_-
Whoops, we are sorry to assume the same handle for now (if we can find it as a valid handle in CF), ><
Post is updated, thanks for the input!