Skip to content

Document team boxes #3176

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.

Sign up for GitHub

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

Open
wants to merge 13 commits into
base: main
Choose a base branch
from
Open

Document team boxes #3176

Changes from 1 commit
Commits
Show all changes
13 commits
Select commit Hold shift + click to select a range
a5b3e35
Create link for problem set page
vmcj Oct 28, 2025
42b0aa1
Add this commit to discuss if we like this more
vmcj Oct 28, 2025
80db2f3
According to some native speakers a jury is not a collection of judges
vmcj Oct 28, 2025
9f86c2c
Provide a simple summary of the problems page
vmcj Oct 28, 2025
d4ad2de
Provide a longer explanation of the problems overview page
vmcj Oct 28, 2025
5a0c720
Use K&R style
vmcj Oct 28, 2025
2460137
Save some space in the team manual
vmcj Oct 28, 2025
a43578d
Move python3 as it fits on the available space
vmcj Oct 28, 2025
47e7e53
Prevent splitting of the code example
vmcj Oct 28, 2025
bb2e711
Remove pascal as it takes space
vmcj Oct 28, 2025
e53673e
The actual screenshot of the page
vmcj Oct 28, 2025
945114c
Update doc/manual/team.rst
vmcj Oct 28, 2025
c2e39c1
Update doc/manual/team.rst
vmcj Nov 12, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions doc/manual/team.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -140,6 +140,15 @@ an error message otherwise.

Web interface
`````````````
The problems can be found at |problemseturlteam|.
Copy link
Member

@meisterT meisterT Nov 13, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This line can be removed.

The setup of every contest is different so the judges may provide the problemset in hardcopy
Copy link
Member

@meisterT meisterT Nov 13, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suggest the following phrasing:

Judges may distribute the digital versions of the problems either individually per or as full problemset through DOMjudge.
If the judges issue a clarification for a problem, it will be sent out and displayed in the corresponding problem card.
The judges may provide additional files for a problem, such as extra inputs, testing tools, or other relevant attachments.
You can use the problemset page to help decide which problem to solve next. DOMjudge shows the live contest progress, including the number of successful and failed submissions for each problem.
Use the info from the problemset page and the scoreboard to gauge problem difficulty. A good rule of thumb is: Problems solved often and early in the contest are likely easier. Problems solved infrequently or only later in the contest are typically more difficult.

or provide the single problem PDFs here and an optional online full problem set.
Sometimes a clarification about a problem is send, you can view those coupled with the statement with the problem.
The judges may provide additional attachments like extra input files, testing/helpful tools or anything relevant to the problem.
You can use this page to pick the next problem to solve, DOMjudge shows the progress of the contest with the amount of
successful and failed submissions, you can use those to find the next problem to solve with as rule of thumb that problems
which are solved often in the beginning are most likely simpler and problems which are solved later in the contest are
deemed harder to grasp.

Solutions can be submitted from the web interface at |baseurlteam|.
Click the green *Submit* button at the menu bar on every page.
Expand Down