SPatrik's blog

By SPatrik, history, 2 years ago, In English
Tutorial is loading...

C++ code: 58307249

Tutorial is loading...

C++ code: 58307265

Tutorial is loading...

C++ code: 58307281

Tutorial is loading...

C++ code: 58307302

Tutorial is loading...

C++ code: 58307320

$$$O(n^4)$$$ complexity solution for problem E1 by KAN: 58306483

Read more »

  • Vote: I like it
  • +37
  • Vote: I do not like it

By SPatrik, history, 2 years ago, In English

Hello, Codeforces!

I am glad to invite you to take part in Codeforces Round #577 (Div 2), which will be held on Sunday, 4 August at 16:35 UTC.

You will be given 5 problems, one of them will have 2 subtasks and 2 hours to solve them.

The round will be rated for the second division.

Huge thanks to cdkrot and KAN for helping to prepare the round.

I would like to thank to 300iq, isaf27, vintage_Vlad_Makeev, pllk, mohammedehab2002, 74TrAkToR, Rox, _overrated_ for testing the round.

And thanks to MikeMirzayanov for the great codeforces and polygon platforms.

This is my first Codeforces round. Hope you will enjoy it.

Good luck and have fun!

UPD: The scoring distribution is: 500 — 1000 — 1500 — 2000 — (2000 + 1000)

UPD2: Editorial

UPD3: Congratulations to the winners:


1: wwaynetuu

2: jerome_mei

3: satu0king

4: Yazmau

5: Tlatoani, Hasan0540, boba5551

Unofficial Div1:

1: neal

2: uwi

3: scott_wu

4: I_love_Tanya_Romanova

5: ecnerwala

Read more »

  • Vote: I like it
  • +210
  • Vote: I do not like it

By SPatrik, history, 3 years ago, In English

I really got fed up with codeforces pretest and main test system. This system makes every contest a game of luck. Let's say there are two contestants: A and B. They both solve a problem incorrectly. Contestant A submits his code and gets pretests passed, while contestant B gets WA on pretest. Now B moves on and will get 0 points for this problem, while A can easily spot the mistake in the code and correct it. He gets 50 points penalty, and he gets the score for the problem. So what was the difference between A and B? A was lucky because he got WA on pretest and got the score for the problem, B was unlucky to pass the pretests and he got nothing. Of course it is said to check your solution, and it is your responsibility if you get WA on main test, but still it costs lots of time (too much time for 2 hours contests) to check every single solution and even if you spot a mistake, you still get the 50 points penalty for resubmitting your code and the time penalty. This pretest and main test system is ridiculous and shouldn't be continued in such a way. I could think 2 ways to make the system testing fair and removing the factor of luck:

1: Your solution gets tested when you submit your code. If it pass tests it is ACCEPTED and there won't be more tests at the end of the contests. If it doesn't pass tests, you get penalty as usual. This would make slightly easier to solve problems, but this advantage would be good for everyone, so it wouldn't affect the contests results.

2: There are no pretests at all. You can submit your code and you don't get any feedback from your verdict of your solution. You can change your solution till the end of the contest. There are no penalty for resubmitting, but only your last solution will run on tests (after the end of the contest) and you get time penalty also according to the time you submitted your last solution. This system would make much harder to make a good solution, but this would be fair for everyone.

These are my suggestions. If you have any other idea feel free to share.

Read more »

  • Vote: I like it
  • -29
  • Vote: I do not like it