Skip to content
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 output only problems #2521

Open
meisterT opened this issue May 1, 2024 · 4 comments
Open

Implement output only problems #2521

meisterT opened this issue May 1, 2024 · 4 comments

Comments

@meisterT
Copy link
Member

meisterT commented May 1, 2024

  • Currently, contestants submit source code that it run and executed.
  • Output-only problems can be used when you don't want to restrict what languages can be used in a contest or don't have the judging capacity.
  • In theory it could be combined with the other scoring types: scoring
@meisterT
Copy link
Member Author

meisterT commented May 1, 2024

Example how this was used during the ICPC challenge in Luxor:

For problem A1, you can find the 25 open tests on your workstation. The exact location of the file will be announced with a broadcast message at the start of the contest. The materials also contain a text summary that mentions the main parameters and the scoring weight of each open test. You should solve the problem A1 locally on your workstation. Then submit a ZIP archive which, in its root, contains the answers named after the respective tests: 01.out, 02.out, ..., 25.out. Your archive may contain only part of the answers: in that case, the missing answers will contribute 0 points. One of the ways to create the archive is to use the following command in the terminal:

zip -FSr submission.zip *.out

@meisterT
Copy link
Member Author

meisterT commented May 1, 2024

Note that you could in theory today create an output-only "language" which does basically just cat. You cannot restrict languages per problem though, only per instance.

@vmcj
Copy link
Member

vmcj commented May 1, 2024

Note that you could in theory today create an output-only "language" which does basically just cat. You cannot restrict languages per problem though, only per instance.

I think that is also the way to implement this (as it requires less code changes), adding some extra overrides to contestproblems with allow judgeable/allowed languages seems not that much extra code change and would already implement this.

@as6325400
Copy link
Contributor

截圖 2024-10-19 上午11 54 45
Is it a better approach to add a language that executes directly by default under the disable option?

meisterT added a commit to meisterT/domjudge that referenced this issue Nov 22, 2024
…contest.

If empty, falls back to the global definition.

This is part of DOMjudge#2521.
meisterT added a commit to meisterT/domjudge that referenced this issue Nov 22, 2024
…contest.

If empty, falls back to the global definition.

This is part of DOMjudge#2521.
meisterT added a commit to meisterT/domjudge that referenced this issue Nov 23, 2024
…contest.

If empty, falls back to the global definition.

This is part of DOMjudge#2521.
meisterT added a commit to meisterT/domjudge that referenced this issue Nov 23, 2024
…contest.

If empty, falls back to the global definition.

This is part of DOMjudge#2521.
meisterT added a commit to meisterT/domjudge that referenced this issue Nov 23, 2024
…contest.

If empty, falls back to the global definition.

This is part of DOMjudge#2521.
meisterT added a commit to meisterT/domjudge that referenced this issue Nov 23, 2024
…contest.

If empty, falls back to the global definition.

This is part of DOMjudge#2521.
meisterT added a commit to meisterT/domjudge that referenced this issue Nov 24, 2024
…contest.

If empty, falls back to the global definition.

This is part of DOMjudge#2521.
github-merge-queue bot pushed a commit that referenced this issue Nov 24, 2024
…contest.

If empty, falls back to the global definition.

This is part of #2521.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants