Skip to main content

Checks

Checks read the whole match after every change and list what doesn't add up: a score that jumps, a team that didn't rotate, a player who isn't on court. Fix them as you go, and your .dvw opens cleanly everywhere.

Open Checks​

  • Coding layout: the Checks tab on the right is always there.
  • Video layout: press Alt+C (⌥C on a Mac), or click the faults flag above the code log ("2 faults · 5 follow"). Checks open in place of the code log, so the video doesn't move. Click the back arrow to return; typing a code also brings the log back.

Alt+C works in the Coding layout too: it switches the right panel to the Checks tab.

The tab shows how many issues there are of each kind:

MarkSeverityMeaning
Filled octagonErrorSomething is wrong: the file won't add up as it stands.
TriangleWarningProbably wrong. Check it.
Circled "i"InfoA note, often a hint: a long gap that may be a missed rally, a combination from an unusual zone.

Read an issue​

Each issue shows its mark, what's wrong, and where: "code 214 · rotation". The newest issues are at the top.

Click an issue to go to its code in the log: Courtside opens the code's set and rally, scrolls to it and flashes it. To see it in the video, click the code in the log.

The issues use the same names as the rules: score, rotation, back row, substitution, serve/reception, roles and code.

Fix the first fault first​

One slip often causes a string of issues after it. A side-out without its rotation, for example, puts every later rotation in the set out. Courtside lists such a fault once, with the issues that follow from it underneath:

  • The fault shows "4 later issues follow from this". The follow-on issues are listed under it, each with its code number (↳ 231). Click the line to hide or show them.
  • In the code log, a row whose issues all follow from an earlier fault shows ↳ 214 instead of a mark. Click it to go to the fault.

Fix the fault, and its follow-on issues usually go away with it.

For rotation faults there's a shortcut: Fix rotations from here.

When there's nothing to fix​

The tab says "No issues."

Some notes are fine to leave, for example a long gap before a serve that was really a long break. Info notes don't stop anything.