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

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

What should a person do if he/she gets a failed system test on a CF Round. I want to know the constructive response.

So, yesterday i noticed some high-rated coders getting FST in easy problems like A and D. So how do you work on that.

I believe there are two possible scenario.

  1. Huh! a FST ? Well, i'm high rated af so i can't be wrong. Its the contest maker, i am always right, i am doing everything right, not my fault
  2. Oh shoot a FST ! I dont think i deserve to be high rated anymore, if i can't solve A then i think i deserve to be thrown at bottom of ranklist. I am good for nothing, RIP

what should be the ideal (constructive) response for this?

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

»
4 года назад, # |
Rev. 3   Проголосовать: нравится +2 Проголосовать: не нравится
  1. Oops, I will pay more attention to problem A next time.
  • »
    »
    4 года назад, # ^ |
      Проголосовать: нравится +16 Проголосовать: не нравится

    yesterday's A was too much, the solutions failed on a trivial test-case which should be definitely included in pretest

»
4 года назад, # |
  Проголосовать: нравится +17 Проголосовать: не нравится

I don't think the two scenarios you listed are the only ones. Usually I try to treat FST as if I failed pretests and just happened to find out at a rather inconvenient time. My solution is still wrong and I treat it as such.

Honestly I'm not sure I really change my strategy or targets that much (except for the one time I rage quit Topcoder), so if you just take it in stride and keep doing what you're doing you should be fine.

Now, if this starts becoming a pattern (like an FST every 4-6 contests), then you should probably revise your submission strategy to test your code a bit more yourself before submitting. And anyways the type of submission strategy that gets that rate of FST is rare because of the penalties you get from rejected solutions.

»
4 года назад, # |
  Проголосовать: нравится 0 Проголосовать: не нравится

Neither of these are the appropriate or general response of people to failed systests. Most people see the mistakes they made and think about how to avoid these issues from occurring again. Projecting the blame on yourself or the problem writer is not effective.

»
6 месяцев назад, # |
  Проголосовать: нравится 0 Проголосовать: не нравится

What is FST?

  • »
    »
    6 месяцев назад, # ^ |
      Проголосовать: нравится 0 Проголосовать: не нравится

    Failed System Testing. (When your solution passes the pretest but fails later during system testing)

»
6 месяцев назад, # |
  Проголосовать: нравится +3 Проголосовать: не нравится

FST means that you didn't noticed some corner cases. I think people FST should be more careful. And don't be frustrated!

»
6 месяцев назад, # |
Rev. 2   Проголосовать: нравится 0 Проголосовать: не нравится

As you can see,when I drop 100+ ratings,I only solve A.

Because I think B is "+",C is "+",so it's not valuable to solve C before B.

As you can see,the result is not good.

So I think 2 is not good.


And I got rank 127 of div.2 half years ago,but I FST.

From then on,I haven't FST any more.

So I think you should pay attention to you code habit. My English is poor.