Блог пользователя iaNTU

Автор iaNTU, история, 2 года назад, По-английски

I don't get what this guy is talking about.

Is it my fault not receiving a code to claim the T-shirt?

Полный текст и комментарии »

  • Проголосовать: нравится
  • -52
  • Проголосовать: не нравится

Автор iaNTU, история, 4 года назад, По-английски

Hey guys look what I've found today on youtube.. Mass cheating in the ongoing codeforces round #718. Its very shameful to have these people in our community.. Due to these cheaters, hard working people in our community are not getting the results they expect.There are also several telegram groups having a large no of participants.. .It's the link of the video. link The video may be deleted so please look into it asap

Note : almost copy and paste from link link

Полный текст и комментарии »

  • Проголосовать: нравится
  • +82
  • Проголосовать: не нравится

Автор iaNTU, история, 5 лет назад, По-английски

Story

I just participated as an unrated contestant in Educational Codeforces Round 88 (Rated for Div. 2). I was trying hard to solve problem C, yet keep getting WA on test 4. I didn't solve the problem during the contest, and when I was testing my solutions after the contest, something weird happened.

Check this out

Compiler : C++17 AC

Compiler : C++17 (64bit) WA

I know nothing about the compiler.

I am just curious about what causes this difference, and what should I do to avoid these bugs.

Полный текст и комментарии »

  • Проголосовать: нравится
  • +30
  • Проголосовать: не нравится

Автор iaNTU, история, 5 лет назад, По-английски

Hi, I'm a contestant of 2019 Bangkok Regional contest, which have just finished the practice session today.

During the practice session my teammates found some strange behavior of the judging system. Below are the list of issues we found.

  • The order of the problems on the scoreboard was randomized and there's no problem number on it, thus neither the contestant nor the coach could know the real order. For example, the problem order on the scoreboard in the practice session was actually CAB.
  • CE code submissions were judged as RE, which contributed to the penalty. (The judge replies that it might be fixed though.)
  • The sample testcase of problem B in practice session was wrong, and when asked the judge responded "read the problem statement".
  • The input description of problem C said that the string Y would be given in reverse, while it's not.
  • Some team asked about the stack size, and the judge replied that they can't let us know.

This is our first year participating in ICPC contests, so I don't know whether this is common >///<.

Полный текст и комментарии »

  • Проголосовать: нравится
  • +147
  • Проголосовать: не нравится