meshO Manager

Appearance

Results quarantine ​

Audience: Event organisers running a competition where some classes — usually the elite classes — start from a quarantine.

When runners wait in quarantine before their start, they must not learn anything about the course from the people who have already run it. Manager helps by holding back those classes' results from every public display until you release them. The start list stays visible the whole time, so a spectator can still find out when an elite runner is due to start.

What is held back, and where ​

While a class is quarantined:

WhereWhat it shows for that class
Spectator site (phones)The start list. Live results show "Results will be shown from 11:34." instead of a result table.
KioskThe same as the spectator site.
TV screens (leaderboard, Live top 10, analysis walls)The same notice where the class's table or graph would be.
Results, analysis and splits pagesThe same notice in place of the class's results, graphs and splits.
liveresultatThe start list: each runner and their start time, shown as not started. No splits and no finish times.
Live export (the IOF XML file written for other software)The class is left out of the file.

What is not affected, so your officials can still do their jobs:

  • Manager itself, on the operator's computer and the entry desk — you always see everything.
  • The commentary screen — the speaker sees every result. Make sure whatever they read out can't be heard from the quarantine.
  • The info screens (start clock, starters, radio feed, pending downloads).
  • Exports you make yourself (results files, Eventor upload). Exporting results during a quarantine is your decision. A cloud push is different — see Cloud copies below.

If you have set an access PIN (Settings → Access protection), the commentary screen and the info screens that show results ask for it while a class is in quarantine — only a device signed in with the PIN is shown a quarantined class's results. Anyone can choose Continue without the PIN; that screen then shows the class's start list, like a public screen. The start clock and the starters screen never ask.

Set a PIN if the quarantine has to hold. Without one, Manager cannot tell your officials' screens from anybody else's on the venue network, and goes by what each screen says it is.

When a class is released, every open public screen updates by itself within a second or two, and liveresultat and the live export catch up on their next publish. Nobody needs to reload a screen.

Setting it up ​

  1. On the event dashboard, click Event details on the event header card, and choose the Quarantine tab.
  2. Pick a class from Add a class. Add each class that is in quarantine — or click Add all to add every class at once.
  3. For each class, choose under Release when its results come out:
    • At last start — the results appear once the last runner in the class is due to start. This follows the start list: if you move a start time, the release moves with it.
    • At a set time — the results appear at the Release time you type in, whatever the start list says. The dialog won't save a class set to this with no time.
  4. Click Save.

Once saved, a class released at its last start shows when that is, worked out from the start list — for example Hidden until 11:34, or Released at 11:34 once that time has passed.

Example. W21E's last starter is at 11:34 and M21E's at 11:56.

  • Set both to At last start, and W21E appears on the public screens at 11:34 and M21E at 11:56.
  • Or set both to At a set time of 11:30, and both appear at 11:30.

You can mix the two: each class has its own setting.

Good to know ​

  • "At last start" uses the allocated start times — the start list, including a class or event mass start. A runner who is marked as not starting (DNS, not participating, cancelled) doesn't count. It never waits for someone who starts late.
  • A runner with no start time doesn't count either. A late entry who hasn't been given a start time yet is left out: the class is released at the last start time on the start list. If you then give them a later start, the class is hidden again until that start.
  • A relay set to At last start is released at its restart, when every runner still waiting is sent out. A relay with no restart stays hidden until you finish the event — its later legs go whenever the runner before them comes in, which nobody can know in advance. Set a time if you want it out sooner.
  • Release times to the second. A last start at 11:34:30 is shown as Results will be shown from 11:34:30, so the notice is never earlier than the release.
  • A class with no start times yet stays hidden. If you choose At last start for a class that has no start times — a punching start, say — Manager can't tell when to release it, so it keeps the results hidden until you finish the event. The Quarantine tab says No start times beside it. Set a time instead, or remove the class when you want its results out.
  • Releasing early. To release a class straight away, remove it from the list (the × beside it) and click Save.
  • Moving a start later puts a class back into quarantine. If you give a runner a start time after the release, the class is hidden again until that new last start.
  • Finishing the event releases everything. So does abandoning it.
  • Replaying an event runs the quarantine again, exactly as it happened on the day.
  • Cloud copies. A copy of the event pushed to a cloud server keeps its quarantined classes hidden until the event is finished (or two days after the event date), and shows Results are not being shown yet rather than a time. A cloud server's clock may be in a different time zone, so it can't safely go by the time of day.
  • Shared courses. If a quarantined class shares a course with a class that isn't quarantined, the other class's course comparisons (such as the mistake analysis) are worked out from everyone on the course, including the quarantined runners. Elite courses are normally their own, so this rarely matters.