Standalone and combined scoreboards

A contest scoreboard covers one contest. For a standing that spans several — a season table, a multi-round series, a league — there are two other kinds of board, and they solve the problem differently.

A standalone scoreboard is built from columns you define one at a time, which can be nested and can mix contest results with member profile data. It has its own address and can be published outside the console. A combined scoreboard adds several whole contests together automatically, keyed by space member, and needs no column definitions at all.

Standalone scoreboards are limited by the plan's scoreboards quota; when it is used up, creating another is refused. See Why a section is missing.

Standalone scoreboards

Contests → Scoreboards lists them by name and format. Creating, editing, rebuilding and deleting them needs the scoreboard write permission.

A scoreboard is created with a name, a key — which becomes part of its address — and a format, IOI or ICPC, which decides how scores and penalties are computed and displayed and cannot be changed afterwards. View opens the public page for it, at the space's site under /s/<key>. Copy duplicates a board with its columns, giving the copy a fresh key; Delete removes the board and its standings.

Columns

The columns are the board. Each has a key, a name, a short name used as the header on the results table, a position, and a type:

Columns nest: a column with a parent is drawn under it, which is how a season board groups a round's problems beneath the round, and the rounds beneath a grand total. The list shows the hierarchy by indentation.

The type and the thing a column refers to — the contest, the problem, the attribute key — are fixed when the column is created. Everything else, including the parent, can be changed later. Three toggles are editable straight from the list: Visible, whether the column appears at all; Sortable, whether readers may sort by it; and Filterable, for Attribute columns, whether readers may filter by it. Set as default sort, on Total and Contest columns, makes that column the one the board is ordered and ranked by, descending.

Freezing a standalone board

Freezing here is scheduled rather than expressed as an offset from a contest's end. On the board's Schedule, each entry is a time and either Freeze, from which moment the board stops showing new results, or Unfreeze, from which it shows them again.

Freezing needs a board that retains what it showed at earlier moments, and not every board does. Set the schedule well before you need it and check that the board actually freezes; if it does not, get in touch rather than waiting for the moment itself.

For freezing a single contest's board, see Freeze the scoreboard.

Results

The Results tab is the standing: a rank column followed by every visible column, drawn in hierarchy order with nested children before the parent that totals them. Name cells show the participant name; Attribute cells show the value, with countries and regions rendered with their flag; Total and Contest cells show the score with the penalty underneath it in ICPC format; Problem cells are the same score cell as on a contest board. Ties share a rank range, shown as 3–5.

The mode switch offers Latest, the current standing and the default in the console, Frozen, the last standing recorded before the freezing moment, and Upsolve.

Rebuild recomputes every row from the underlying contest results, with confirmation. It runs in the background and is a repair rather than a refresh, so it takes real time on a large board.

Combined scoreboards

A combined scoreboard adds several contests together into one standing keyed by space member rather than by contest participant, so the same person appearing in five contests is one row rather than five.

It is reached at /contests/combined-scoreboards in the console and is not linked from the navigation, so you need the address. Working with them needs permission to write contests.

Each board has a name and a slug — lowercase letters, digits, hyphens and underscores, starting with a letter, unique within the space — which identifies it in addresses and in the API, and is accepted anywhere the board's id is.

Best of counts only that many best contests per member towards the total; zero counts all of them. A contest left out by the rule still shows its score on the row, in muted type, and simply does not add to the total.

What it aggregates

The Contests tab lists the contests the board counts, each with its status, problem count and position. Adding a contest walks that contest's participants and brings its members onto the board, so the work is proportional to the size of the contest. Removing one stops its scores counting, and a member who was on the board only through that contest leaves with it.

The Attributes tab adds member profile fields as extra columns — school, city, grade. Each entry is the attribute key, its type, and the column header to use; the header is set here rather than taken from the profile field, whose own label is usually too long for a column. Adding a key the board already shows updates its position and header instead of creating a second column.

Reading a combined board

Columns run: rank, name, total score, then one column per configured attribute, then for each contest its own total column followed by one column per problem in it. Problem headers are numbered by the contest's position and the problem's letter — 1A, 1B, 2A — so the same letter in two contests stays distinguishable.

Problem cells are the same score cells as on a contest board, first-to-solve outline and stale marker included. As on a contest board, ties share a rank range, and the official rank covers only officially ranked members while a second rank counts everyone.

The mode switch offers Main, contest time only; Frozen, in which a contest that is currently frozen contributes its results as of its own freezing time while the others contribute the same values as Main; and Upsolve.

There is one filter per configured attribute, typed from the profile field: numeric fields compare with the usual numeric operators, text fields with equality, contains and starts-with.

Rebuild recomputes every row from the contest scoreboards, with confirmation. Rows are maintained as contests are judged, so this too is a repair rather than a refresh; it runs in the background, a member at a time, and the board stays readable throughout.