-
Notifications
You must be signed in to change notification settings - Fork 278
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.
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
base: main
Are you sure you want to change the base?
Document team boxes #3176
Changes from 1 commit
a5b3e35
42b0aa1
80db2f3
9f86c2c
d4ad2de
5a0c720
2460137
a43578d
47e7e53
bb2e711
e53673e
945114c
c2e39c1
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -23,7 +23,7 @@ become of importance when you run into problems. | |||||
| .. admonition:: Summary | ||||||
|
|
||||||
| The web interface of DOMjudge can be found at | ||||||
| |baseurlteam|. See the two figures on the next page for | ||||||
| |baseurlteam|. See the three figures on the next pages for | ||||||
| an impression. | ||||||
|
|
||||||
| Solutions have to read all input from 'standard in' and write all | ||||||
|
|
@@ -54,6 +54,13 @@ become of importance when you run into problems. | |||||
| requests and replies is done through the web interface at | ||||||
| |baseurlteam|. | ||||||
|
|
||||||
| Use the |problemseturlteam| page to get: | ||||||
|
|
||||||
| - all attachments such as 'testing tools' to problems, | ||||||
vmcj marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||||||
| - view the submission and acceptance ratio during the contest as an indicator of the difficulty of a problem, | ||||||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I like the brevity of this explanation, but I'm not sure if we might want to include a hint that more information is available when hovering the indicators.
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Feel free to propose an alternative text.
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. What about something like this? |
||||||
| - get the problem statement and clarifications on those statements | ||||||
|
||||||
| - see the time & memory limits. | ||||||
|
|
||||||
|
|
||||||
| .. raw:: pdf | ||||||
|
|
||||||
|
|
@@ -76,6 +83,11 @@ Overview of the interface | |||||
|
|
||||||
| The scoreboard webpage. | ||||||
|
|
||||||
| .. figure:: team-problemset.png | ||||||
| :width: 80% | ||||||
|
|
||||||
| The problem set webpage. | ||||||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I looked that one up and it seems that 'problem set' is the correct form and 'problemset' is something which is informally accepted. I'm fine with both though.
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The UI uses problemset it seems so that's why I'm suggesting it. |
||||||
|
|
||||||
| .. raw:: pdf | ||||||
|
|
||||||
| PageBreak | ||||||
|
|
||||||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Leave the URL out here (as mentioned on the other commit)