-
Notifications
You must be signed in to change notification settings - Fork 260
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement partial scoring #2518
Comments
From https://cms.readthedocs.io/en/v1.4/Configuring%20a%20contest.html#computation-of-the-score:
|
In each case, how will penalty time be calculated? I think this is probably the most pressing issue for our contest in particular. We're currently simulating the second variant by having multiple problems, but this means that penalty time gets multiplied for each testcase group, which is kind of awkward. I think having a single penalty time for the entire problem calculated as max(all submission times) + X * max(# wrong submissions for each testcase group) would make most sense. In this example, this team gets 63 + 67 + 70 = 200 penalty for problems 5, 5b1, and 5b2 despite submitting the same code 3 times in succession after seeing the verdict for each previous testcase group. I think an ideal situation would be if they would be able to submit one time, use checkboxes to select all testcase groups, and then get a single 63 as their penalty time. |
Related to my comments in #2525 (comment), I'm not a big fan option 2 to let the score for a problem depend in such a complex way depend on the score of each individual submission. I'd rather stay with: the score for a problem is always the maximum over the scores of each team's submissions for that problem. |
Then there are two variants:
If we would implement the first variant, the second variant could be worked around by splitting it up into multiple problems.
The kattis problem format suggests adding a
testdata.yml
per testcase group: https://icpc.io/problem-package-format/spec/problem_package_format#test-data-groupsThe text was updated successfully, but these errors were encountered: