Skip to content

Basic implementation of partial scoring. #3047

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

Draft
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

meisterT
Copy link
Member

@meisterT meisterT commented Aug 3, 2025

This follows the legacy spec in:
https://icpc.io/problem-package-format/spec/legacy.html#graders

We might decided at a later point whether we want to support this or just the new (currently draft) spec, but basic constructs of the change should be the same.

Not yet implemented:

  • any form of testing
  • anything on the team interface
  • shadowing

Part of #2518

This follows the legacy spec in:
https://icpc.io/problem-package-format/spec/legacy.html#graders

We might decided at a later point whether we want to support this or
just the new (currently draft) spec, but basic constructs of the change
should be the same.

Not yet implemented:
- any form of testing
- anything on the team interface
- shadowing

Part of DOMjudge#2518
@meisterT
Copy link
Member Author

meisterT commented Aug 5, 2025

Some notes:

  • there's a to-do already, but we need to talk about internal precision and precision in presentation
  • we should add to the jury submission page some info that allows following the result calculation with test case groups (should be easy to do with the existing function)
  • the number of tries on a scoring scoreboard should really be the number of total tries (not until the first correct attempt like for pass-fail)
  • it seems we are not handling the accept_if_any_accepted case always correctly, needs more testing
  • while we can ingest results from a primary CCS now, we don't compare the scores yet for shadow differences
  • the layout of the shadow differences table needs to be fixed
  • optimization problems are by their very nature less deterministic as they incentivize teams to do stuff like try this approach for that amount of time, then this other approach for that amount of time and generally the use of RNG is much more prevalent

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant