

Suggestion: Make Div2As easier
source link: http://codeforces.com/blog/entry/106222
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.


Hi everyone! I've noticed that the difficulty of Div2As has slightly increased. In my opinion, this creates a skewed result, as people who intend to join may not be able to solve the first problem. Then, they may end up leaving without submitting anything. As a result, the difficulty rating of Div2As largely depends on the number of fakesolves; i.e. those who fail main tests or end up FSTing.
A harder Div2A also gives a slight disadvantage to those who join and only get A, as the pool of people competing are the ones who are more likely to solve A.
In addition, a hard Div2A scares lower rated coders away from Div2, which shouldn't be the case as the competition is also for them.
Therefore, I humbly suggest problemsetters to make simpler Div2As for more inclusive participation.
3 weeks ago, # | Completely agree! And not only div2, div1 too. Problem A should be as submitbait as possible so people don't leave contest because of not being able to solve A fast enough, thus giving a huge disadvantage those who have been able to solve it. Since now they are last, whereas in reality they would have been in front of those who left. |
-
Or we can just use the Atcoder rated / unrated registration system :)
3 weeks ago, # | Completely agree. This is a mistake I've done when I started out. And I am seeing many of my peers do it because of hard div2A. And I also feel like the balance should be maintained. Or else many people who can solve A but not B are going to face a hard time. |
3 weeks ago, # | In div1s some cannot solve A and leave the contest unrated... and others solve A just before the contest end with a rating decrease. Making div1A easier can improve this situation. |
3 weeks ago, # | Well, if we can expect a trivial A, then people might use pattern "If a cannot solve B I will quit.", and check B before submitting A. Actually I am doing this since months. The problem would be better solved by the Atcoder rated / unrated registration system as stated by others above. |
-
I think there is a negligible amount of people who do that.
-
In cf this will work against you, every minute you hold submission for A you lose points. Not a feasible approach
I have been doing that on leetcode for some time, only submitting when I passed samples for 3 problems out of 4, if I can’t pass a 3rd problem I don’t submit at all
-
3 weeks ago, # | agreed!! |
3 weeks ago, # | Sometime: "I solved A problem late, maybe I should not enter the contest, I should submit it after the contest". |
Full support. There is another point here: solving one problem mentally commits you to the contest. I think such psychological concerns should not be ignored. Several experienced organizers, I remember snark for example, have said that each contest should have a "gift" that almost all contestants can easily solve. Even though it may seem that a problem that everyone solves quickly doesn't change anything, it in practice means a better and more enjoyed contest by everyone. I find it kind of baffling how easily this advice is ignored these days. Also I think many A-s make the mistake of trying to be very clever that are simple once you see something, but that often means the problems aren't so easy. There are certain problems that seem obvious once you know the solution, but that can lead to a bad assessment of its difficulty. |
3 weeks ago, # | Same feeling |
3 weeks ago, # | I completely agree. When atcoder came up with their Rated/Unrated system, I wasn't sure if the system would work. But as the time went, I realized that it was the best thing that happened. I wish that system can be replicated on codeforces as well. |
-
I understand the rated/unrated thing on Atcoder, but why should it be on Codeforces? You will lose points already if you submit late in contest, unlike Atcoder where the points were fixed no matter when you submitted. The late strategy is even worse for cf style educational rounds.
So the late submission thing may only favor you on Codeforces, when you can also solve harder problems.
That being said, I think the only thing that makes sense is reducing the difficulty of the first problem, which may also result in the server slowing down in the first couple of minutes of the contest.
pigmike
-
When you mark beforehand that the contest is rated for you, you won't skip the round because A/B took you too long to solve.
-
Idk, but whatever time leverage given to choose rated/unrated (e.g. 5 minutes used on Atcoder, which may be increased since cf has more users) should be enough time to determine if you won't be able to solve Div2A, or if you should skip.
-
-
-
What if you decide you can't make it to the contest, after having thought previously that you were going to be able to? Then solving no problems would leave you with a rating that doesn't represent your skill
-
You can unregister, at least on Codeforces.
-
3 weeks ago, # | The comment is hidden because of too negative feedback, click here to view it |
-
I expect Div 1 A not to be a 1900 problem so that people can have more time to solve other problems.
-
The comment is hidden because of too negative feedback, click here to view it
-
-
We don’t say all div1 As should be made easier, we say that this accidents shouldn’t happen.
-
It was just 1 problem in the last 4 months, these "accidents" are very rare. Honestly, your Div1A argument is totally pointless.
-
From the things I noticed while testing rounds these accidents are made on purpose, and I think it's wrong. Also even 1600 may be too much
-
1600 is too much? You do realize most/all Div1 rounds have Div2 rounds in parallel, and reducing the difficulty of Div1A/Div2C just makes the first few problems in Div2 too easy, which may result in "speedforces".
-
Last three(with already rated problem) div2-only rounds have C difficulties of 1400, 1100 and 1200.
-
Rounds with C>=1600 rated have balanced solves distribution. In those rounds doesn't happen thing like C has 5000 solves and D has 200. In rounds with too easy C always happens that many CMs or high experts appear to be below pupils and specialists.
Yes, it happens in rounds with >=1600 C, but way less and less frequently.
-
-
-
-
-
-
-
The biggest problem I see is telling people participating in div2 contests to move to div3 contests when a) div3 contests are less frequent, b) people who only solve div2A are still at a disadvantage when more people back out, c) people are still discouraged when they are unable to solve a single problem from a div2 contest (at least people know div1 contests are hard, people come into div2 contests thinking they're just average), and most importantly, d) it's one problem that's already meant to be rated 800, there's literally no consequence to making it an easier 800.
I agree that div 1A is probably fine as is, I do disagree with the 1900 div1A but that's just an exception to what's generally been in the right difficulty range most contests.
3 weeks ago, # | I completely agree. I'm helping fresh students get into competitive programming, and recommended them to come to Codeforces and start with 800-difficulty problems, but then I find that the recent 800-difficulty problems are waaaaaaaaaaaaaay harder than the old 800-difficulty problems. For example, problems like 1712B - Woeful Permutation really should not be rated at 800. I know this is a B problem, but I think the 800 rating only arose because 1712A - Wonderful Permutation induced a lot of quits, which I also don't think should be 800 either. I'm aware that you can sort the problems by number of solves instead, but I feel that newer problems have better quality than older problems (along with later trends like test cases and input sizes that reflect modern performance in the judging environment). Number of solves is biased towards older problems due to their age, and this becomes compounded further when people sort by number of solves to start practicing. |
3 weeks ago, # | Agreed ! Also the last problem in Div2 is solved by generally <50 people who are most likely to end up in Div1. So adding an easy question and popping the last question (not necessary tho) would make the contest more engaging in my opinion. P.S: Just a thought ^_^ |
3 weeks ago, # | Maybe have it so that if you enter the contest page (the page with the problems), and you registered before hand, then the round is rated even if you don't submit. That way if you registered and forgot about the contest or something, you will still be fine. |
3 weeks ago, # | Just make people write div3-4 instead. Or go practice coding somewhere else |
3 weeks ago, # | Another suggestion: div2As should not be about guessing from sample input (as it frequently is nowadays) |
-
I don't agree. I have set round for codeforces, the coordinator requires 2a to be a little difficult and interesting, if the sample is not strong, it is almost impossible. A complete sample is an effective way to reduce the difficulty value. Generally speaking, I am used to designing samples to ensure that almost everyone can slove 2a smoothly.
-
I agree, but not only div 2 A-s. A lot of easy problems try to be "clever" and "simple once you see it", but the consequence is that a lot of these problems are in practice guessed by most participants who don't have any idea why their solution works. At this rate I'm worried that we are teaching beginners that CP is about guessing. After all, there are already plenty of greys who tell other greys that an "observation" means "looking at input/output pairs and noticing an apparent pattern".
3 weeks ago, # | agree |
9 days ago, # | I prefer harder Ds |
80 minutes ago, # | We need harder As, even division 1 As are too trivial. They should be at least 2000 rated. Marinush |
Recommend
About Joyk
Aggregate valuable and interesting links.
Joyk means Joy of geeK