aboAdnan's blog

Discovering that tests are weak after judging ended!
By aboAdnan, history, 6 years ago, In English

Hi Codeforces!

In D2 problem in today's Div.2 contest, the testcases were not covering all cases.

If no rejudging will be held, this will effect positively on someones (with passed wrong solutions), and negatively on otherones (with ranks worse than what they worth).

For me, I'm satisfied although it may effect negatively on me, because in a previous contest, this case have effected on me positively.

So, if Codeforces will always deal with this case with just apologising, so it will be like: "today it effects on you with -1, tomorrow will effects with +1", but this is not guaranteed for every one and for all times.

So, please, work on solving weaktest cases, even if the solution will be rejudging, or fair will not be held in those contests.

Thanks anyway!

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

Comments Comments (9)
| Write comment?
»
6 years ago, # |
← Rev. 3   Vote: I like it +9 Vote: I do not like it

I think that you can write message to codeforces coordinators and be the tester of upcoming rounds, not only you but everyone else who want to make codeforces better

→ Reply
»
6 years ago, # |
  Vote: I like it +58 Vote: I do not like it

Just to play Devil's advocate here:

The round you are referring to featured something that is not usually in previous rounds, i.e. Having a subtask. This kind of thing is sometimes seen on other platforms like AtCoder, but to my knowledge, is new to CF. Introducing new problem formats is always going to be prone to errors, since the CF team is human. I would argue that these kinds of errors, if small, are okay, because it incentivizes CF to try out new problem formats.

So, if we want to see new types of problems like interactive, problems with subtasks, etc. we will probably have to tolerate at least some level of errors, simply because trying out something new is prone to introduce all kinds of situations that the team had not necessarily thought of.

→ Reply
  • »
    »
    6 years ago, # ^ |
      Vote: I like it +15 Vote: I do not like it

    Thanks for your pointing out, this point is important to take in consederation.

    I realy appreciate what Codeforces is presenting to us as Competitive Programmer.

    I'm just showing the problem, pleasing, if there are solutions for it, to apply one of them.

    → Reply
  • »
    »
    6 years ago, # ^ |
      Vote: I like it +8 Vote: I do not like it

    Well, actually, there were multiple such rounds with subtasks (Take the last Div. 3 round as an example). So it's not a new feature, to be honest :)

    → Reply
    • »
      »
      »
      6 years ago, # ^ |
        Vote: I like it +7 Vote: I do not like it

      Oh, I see. None of the previous rounds I've done in my memory have had them, so I assumed they were new. In any case, the point partially still stands in that an error like this will forever make subtask problems better.

      → Reply
»
6 years ago, # |
  Vote: I like it -29 Vote: I do not like it

Let me try to help you- you should take a deep breath, get over the fact you failed this contest and realize that it's not problem setters' fault that you failed. Nothing's gonna change, get over it man! Please start training more for programming competitions. Here is a great resource which helped me a lot: https://cp-algorithms.com/

It will take a long time to master these topics, but in the end you will find yourself in possession of knowledge that will nourish you for the rest of your life. Good luck!

→ Reply