Hello!↵
↵
[TOKI Open 2018](http://mirror.codeforces.com/blog/entry/59182) has ended. Thank you to everyone who participated the contest.↵
↵
We decided to not consider any participants from the second window whose username is registered on the first window. We also decide to not consider any participants from the second window whose code is very similar to other user's code on the first window. After that, we consider a TOKI Open 2018 participant to be those who made at least one submission on either day. ↵
↵
There were a total of 104 participants, which three of them get a fullscore. Congratulation to [user:1021839,2018-05-28], [user:Alex_2oo8,2018-05-28], and [user:zscoder,2018-05-28]. The full result of TOKI Open 2018 is available [here](https://docs.google.com/spreadsheets/d/1wH8FZGwYaDrMDsDaqTvvjMVUF5jmfriRligZgI16yL4/edit?usp=sharing).↵
↵
The skeletons, solutions, problem descriptions, and testcase generators for TOKI Open 2018 are available [here](https://github.com/jonathanirvings/toki-open-2018). The problems are available for upsolving [here](https://training.ia-toki.org/problemsets/113/problems). Alternatively, the PDFs version of the problems are available here ([English](https://drive.google.com/file/d/1gZF2jqlnI0kmmD-v6XFc_MXE4LG7hx49/view?usp=sharing), [Bahasa](https://drive.google.com/file/d/1aPNPnLYDhEQ3A9CEe_F8hRAzBqHgEONZ/view?usp=sharing)).↵
↵
The problems discussion (a.k.a. editorial) for TOKI Open 2018 is currently being written and should be done within two weeks time. I will update this blog post once it is ready. Stay tuned! :)↵
↵
We also have prepared a feedback form for TOKI Open 2018. You can access the feedback form [here](https://docs.google.com/forms/d/e/1FAIpQLScR2ZJ7bgfa9nE5BACnXMiuZj-7601c6QZDOiBkyQhquwLytQ/viewform?usp=sf_link). Please do fill them to help us conduct TOKI Open better in the future. It shouldn't take more than 5 minutes of your time :)↵
↵
We thank everyone who are involved in TOKI Open 2018:↵
↵
- [user:jonathanirvings,2018-05-28], [user:schezo,2018-05-28], [user:afaji321,2018-05-28], [user:FeIi,2018-05-28], and [user:Prabowo,2018-05-28] as Scientific Committee↵
- [user:chaotic_iak,2018-05-28], [Derianto Kusuma](http://stats.ioinformatics.org/people/611), [user:jonathanirvings,2018-05-28], [user:schezo,2018-05-28], [user:FeIi,2018-05-28], and [user:Klungs,2018-05-28] as problem setters (the detailed distribution of the problem setters can be seen on the problems discussion later)↵
- [user:sergiovieri,2018-05-28], [user:malfple,2018-05-28], [user:sokokaleb,2018-05-28], and [user:ayaze,2018-05-28] as problem testers↵
- [user:fushar,2018-05-28] and [Jordan Fernando](http://stats.ioinformatics.org/people/5267) as TLX developer and Technical Committee.↵
↵
We hope to conduct TOKI Open again next year, with broader audience. If you have any inquiries, please contact scientific@toki.or.id. See you next year! :)↵
↵
*UPD1:* The problem discussion (a.k.a. editorial) for TOKI Open 2018 is available [here](https://drive.google.com/file/d/1P_kl08hbckEcVF7y6VhkWhR5aNy7ONDS/view?usp=sharing)
↵
[TOKI Open 2018](http://mirror.codeforces.com/blog/entry/59182) has ended. Thank you to everyone who participated the contest.↵
↵
We decided to not consider any participants from the second window whose username is registered on the first window. We also decide to not consider any participants from the second window whose code is very similar to other user's code on the first window. After that, we consider a TOKI Open 2018 participant to be those who made at least one submission on either day. ↵
↵
There were a total of 104 participants, which three of them get a fullscore. Congratulation to [user:1021839,2018-05-28], [user:Alex_2oo8,2018-05-28], and [user:zscoder,2018-05-28]. The full result of TOKI Open 2018 is available [here](https://docs.google.com/spreadsheets/d/1wH8FZGwYaDrMDsDaqTvvjMVUF5jmfriRligZgI16yL4/edit?usp=sharing).↵
↵
The skeletons, solutions, problem descriptions, and testcase generators for TOKI Open 2018 are available [here](https://github.com/jonathanirvings/toki-open-2018). The problems are available for upsolving [here](https://training.ia-toki.org/problemsets/113/problems). Alternatively, the PDFs version of the problems are available here ([English](https://drive.google.com/file/d/1gZF2jqlnI0kmmD-v6XFc_MXE4LG7hx49/view?usp=sharing), [Bahasa](https://drive.google.com/file/d/1aPNPnLYDhEQ3A9CEe_F8hRAzBqHgEONZ/view?usp=sharing)).↵
↵
The problems discussion (a.k.a. editorial) for TOKI Open 2018 is currently being written and should be done within two weeks time. I will update this blog post once it is ready. Stay tuned! :)↵
↵
We also have prepared a feedback form for TOKI Open 2018. You can access the feedback form [here](https://docs.google.com/forms/d/e/1FAIpQLScR2ZJ7bgfa9nE5BACnXMiuZj-7601c6QZDOiBkyQhquwLytQ/viewform?usp=sf_link). Please do fill them to help us conduct TOKI Open better in the future. It shouldn't take more than 5 minutes of your time :)↵
↵
We thank everyone who are involved in TOKI Open 2018:↵
↵
- [user:jonathanirvings,2018-05-28], [user:schezo,2018-05-28], [user:afaji321,2018-05-28], [user:FeIi,2018-05-28], and [user:Prabowo,2018-05-28] as Scientific Committee↵
- [user:chaotic_iak,2018-05-28], [Derianto Kusuma](http://stats.ioinformatics.org/people/611), [user:jonathanirvings,2018-05-28], [user:schezo,2018-05-28], [user:FeIi,2018-05-28], and [user:Klungs,2018-05-28] as problem setters (the detailed distribution of the problem setters can be seen on the problems discussion later)↵
- [user:sergiovieri,2018-05-28], [user:malfple,2018-05-28], [user:sokokaleb,2018-05-28], and [user:ayaze,2018-05-28] as problem testers↵
- [user:fushar,2018-05-28] and [Jordan Fernando](http://stats.ioinformatics.org/people/5267) as TLX developer and Technical Committee.↵
↵
We hope to conduct TOKI Open again next year, with broader audience. If you have any inquiries, please contact scientific@toki.or.id. See you next year! :)↵
↵
*UPD1:* The problem discussion (a.k.a. editorial) for TOKI Open 2018 is available [here](https://drive.google.com/file/d/1P_kl08hbckEcVF7y6VhkWhR5aNy7ONDS/view?usp=sharing)
