Problem settings
The settings pane of the problem page – tests, limits, languages, input and output, difficulty, skills and source, sharing, collections, wiki pages and usage.
The right side of a problem’s page holds its settings pane (Problem settings): collapsible cards, with a width you can change by dragging the pane’s edge. In a narrower window the pane sits below the statement.
Settings are saved in two ways:
| Card | When it is saved |
|---|---|
| Judging (limits, languages, input and output) | With the next published version. Until then the values are kept in this browser. |
| Tests, Excel grading | On their own pages; every change goes into the draft at once. |
| Details, Skills and source, Sharing, Collections, Wiki | At once. The card header shows Saving…, Saved or Not saved; a failed save puts the previous value back. |
People who aren’t editors of the problem can’t change the cards: their fields are disabled.
The card counts the sample tests (sample, shown to students) and the hidden ones (hidden, stay on the server). Manage tests (for non-editors, View tests) opens the tests page. When the draft has unpublished test changes, the card says so.
An Excel task has an Excel grading card instead (see Excel tasks).
Judging
Section titled “Judging”| Field | Values |
|---|---|
| Time limit | 0.1–20 s per test. |
| Memory | 16–4096 MB. |
| Languages | All course languages (the default): in each course the problem can be solved in that course’s languages. With specific languages chosen, the problem is solved only in those, in every course. The editor and the judge support C++, Python and C#. |
| Input/output | Standard or Files. With files, set the Input file and Output file (duom.txt and rez.txt at first). |
These values are saved with the next version: publish to apply them. A single test can have its own time and memory limits (see Tests).
When a problem uses files, the program reads only the input file and writes the output to the output file; standard input is empty, and output printed to the screen is not checked. Letter case matters in file names.
Details
Section titled “Details”- Difficulty: Not set or 0–10, listed by band: Easy (0–2), Medium (3–4), Hard (5–10). The archive shows the band with the number.
Difficulty belongs to the problem, not to a version, so it applies at once, without publishing.
Skills and source
Section titled “Skills and source”What the problem practises (skills from the shared list, as Area › Skill) and where it comes from (Own, Exam, Olympiad, Contest, Textbook, Other, with an optional detail and year). Students don’t see them. See Skills, difficulty and source.
Sharing
Section titled “Sharing”Choose who can find and reuse the problem:
- Public – every teacher on the platform;
- Organisation – staff of the problem’s organisation (only when the problem belongs to one);
- Private – the owner, collection grantees and organisation admins.
Below are the Owner (or Shared archive (no owner)) and the Organisation. The organisation can’t be changed here. System administrators see Change owner… next to the owner: it gives the problem to another teacher or admin, who can then edit it; nothing else about the problem changes (see Problem owner). More in Problem archive.
Collections
Section titled “Collections”The collections the problem is in (a lock marks those you can’t change). Add to a collection… or Change collections… opens the tree: tick the collections and click Save. See Collections.
Related wiki pages, which students see under the statement together with the pages the statement links to.
- Add a page – pick a page.
- The row menu: Move up, Move down, Remove from the problem.
When the problem reaches other organisations, the app warns about organisation pages their students can’t open. Archived pages can’t be added. Only the problem’s editors can change this card. More in Links and related pages.
Where it is used
Section titled “Where it is used”- Courses – courses that use the problem: in a topic, a group’s own list, an individual task or a topic’s task pool. Courses you can open as staff are named; the rest are counted (and N other courses).
- Problem sets – how many sets contain it.
- Task pools – in how many topics’ task pools for individual tasks it is (shown only when it is in one).
- Submissions – how many submissions it has.
- Solved – how many of the students who tried solved it, in the courses you teach (for system administrators, in every course).
- Attempts until accepted – a chart of how many attempts students needed (1, 2, …, 6–10, 11+). Counts only, no names.
At the bottom of the card is Delete… (while the problem is unused) or Archive… (once it has history). More in Archive or delete.
Before publishing
Section titled “Before publishing”A checklist of whether the problem is ready:
- programming problem: a title, the Input and Output sections, sample tests, hidden tests (without them, submissions are graded on samples only);
- Excel task: a title, grading rules worth points, a starter file (optional);
- for a converted statement – whether the conversion notes were reviewed.
The same list appears in the publish dialog. See Drafts and publishing.