You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is biased towards the latter, but avoids aggregation rules.
Specification bapc-scoring-0.1
A problem where type contains scoring is called a scoring problem. Each submission receives a non-negative numerical score (such as 85) rather than a verdict (such as AC). The goal of the submission is to maximize the score.
Scores are determined for test cases, test groups, and the submission itself.
The score of a failed test case is 0. By default, the score of an accepted test case is 1; but this can be overriden in testdata.yaml. If a custom output validator produces a score (by writing to score.txt), that value is multiplied with the test case score.
The score of a test group is determined by its subgroups and test cases. The score of an empty test group is 0. Otherwise, the score is either the sum or the minimum of its children. (The default is sum.)
The submission score is score on the topmost test group data.
The scoring behavior is configured by the following flags under scoring in testdata.yaml, which must exist in every testgroup corresponding to a subtask:
scoring?: {
#Thescoreassignedtoeachacceptedtestcaseinthegroup. If a scoring output validator is used, this score is multiplied by the score from the validator.
score?: >=0|*1aggregation?: *"sum"|"min"
}
Example. Here is an example for a IOI-style problem with two subtasks of 20p and 80p, and where sample gives no points:
This issue attempts to specify semantics for problems of
type:scoring
. At the time of writing, it is somewhere between the semantics oflegacy
specification of the problem package format https://github.com/Kattis/problem-package-format/blob/master/spec/legacy.md and the evolving2023-07-draft
https://github.com/Kattis/problem-package-format/blob/master/spec/2023-07-draft.md.It is biased towards the latter, but avoids aggregation rules.
Specification bapc-scoring-0.1
A problem where
type
containsscoring
is called a scoring problem. Each submission receives a non-negative numerical score (such as85
) rather than a verdict (such asAC
). The goal of the submission is to maximize the score.Scores are determined for test cases, test groups, and the submission itself.
The score of a failed test case is
0
. By default, the score of an accepted test case is1
; but this can be overriden intestdata.yaml
. If a custom output validator produces a score (by writing toscore.txt
), that value is multiplied with the test case score.The score of a test group is determined by its subgroups and test cases. The score of an empty test group is
0
. Otherwise, the score is either the sum or the minimum of its children. (The default issum
.)The submission score is score on the topmost test group
data
.The scoring behavior is configured by the following flags under
scoring
intestdata.yaml
, which must exist in every testgroup corresponding to a subtask:Example. Here is an example for a IOI-style problem with two subtasks of 20p and 80p, and where
sample
gives no points:The text was updated successfully, but these errors were encountered: