Publishing live results online

Audience: Event organisers and timing operators who want people away from the arena to follow the race, or to find the results afterwards.

Manager can put your event on the internet in two ways, and they do different jobs:

	liveresultat.orientering.se	meshO cloud (events.mesho.live)
When	While the event is live, updated every few seconds	After the event, once you finish it
What	Start times, radio-control splits, finish times and statuses	The whole event, browsable like the spectator site at the arena: results, splits, start lists, analysis
Set up on	Event details → Live results	Settings → Cloud sync, and Event details → Cloud sync for one event
Off unless	You turn it on for the event	You turn it off — it is on to begin with

You can use either, both or neither. Both are sent by the Manager server itself, so the computer running Manager needs an internet connection — the browsers you work in do not.

Publishing to liveresultat

liveresultat.orientering.se is a free live-results service used across the orienteering world. Manager publishes to it directly: there is no export folder to watch and no other program to run.

Setting it up

1. On the event dashboard, open Event details (see Editing event details) and choose the Live results tab.
2. Switch on Publish to Liveresultat.
3. Choose how to get a competition on liveresultat for this event:
   • Create new… makes a new competition there for you. This is the usual way.
   • Link existing… points this event at a competition that already exists — one you made on liveresultat's own site, or one this event used before you unlinked it.
4. Click Save.

This is best done before the day. Nothing is published until you Start event, so you can set it up whenever you like.

When publishing is switched on, a Liveresultat card appears on the event dashboard showing how it's going (see Checking it is working).

Creating a competition

Create new… asks for:

• Competition name and Organiser — up to 50 characters each. They're what spectators see, so keep them short; Manager refuses an over-long one rather than cutting it.
• Organiser email — required. It's your login for liveresultat's own pages, and the only way back into the competition if its password is lost.
• Time zone — liveresultat shows every time in this zone. It starts as this computer's zone; change it if the event is somewhere else.
• Country — optional. It starts as the time zone's country.
• Is public — whether the competition is listed on liveresultat's start page. On to begin with. See Listed or hidden.

The Competition date is the event's own date and can't be changed here. Manager remembers the organiser, email and country in this browser and offers them next time.

Warning: Create competition makes the competition on liveresultat straight away, and Manager can't undo it. Only the organiser, signed in to liveresultat with the email above, can remove a competition. Check the details before you confirm.

liveresultat gives the new competition a Competition ID and a five-digit Upload password, and Manager stores both with the event.

Linking a competition that already exists

Link existing… lists the competitions on liveresultat for the event's date. Pick yours, or type its Competition ID if it isn't listed, then enter its Upload password — the five-digit password liveresultat gave when the competition was created. Manager checks the ID and the password with liveresultat before saving anything, so a typing mistake is caught now rather than on race morning.

Warning: Linking makes this event the source of everything in that competition. The first time Manager publishes, it removes any runners in the competition that this event doesn't have. That's right when you're re-linking your own competition, and wrong for anybody else's — so check the ID before you click Link competition.

The Live results tab once linked

Once the event has a competition, the tab shows its Competition ID, Competition name, Organiser, Competition date, Time zone (and Country, if Manager created it), and:

• Is public — Published or Hidden, with a Publish or Hide button to change it now.
• Upload password — shown in plain text, so you can read it off. See The upload password.
• Links — Organiser page opens liveresultat's own settings page for the competition, already signed in; Spectator opens the page spectators see, in the language you're using Manager in. Share the spectator link with competitors and supporters.
• Refresh — reads the competition back from liveresultat. Use it after changing something on the organiser page (renaming the competition, moving its time zone, making it public), because nothing tells Manager that happened. Refresh only reads; it never sends anything.
• Publish automatically on start — on to begin with. See below.
• Unlink — stops this event publishing to the competition. See Stopping, unlinking and publishing again.

To change what Manager sets only when creating — the name, date or time zone — or the classes and radio controls liveresultat holds, use the Organiser page.

Listed or hidden

Is public decides whether the competition is listed on liveresultat's start page and in its list of the day's competitions. It is not a lock: a hidden competition is still shown to anyone who has its link.

Publish automatically on start makes the competition public at the moment you click Start event, and at no other time — linking a competition or saving the event's settings mid-race never does it. So a common way to work is:

1. Create the competition ahead of time with Is public off.
2. Leave Publish automatically on start on.
3. On the day, Start event: the competition appears on liveresultat's start page as the results start to arrive.

With Is public left on when you create it, the competition is listed straight away, empty until the event starts.

The upload password

Every upload carries the competition's upload password. It also opens liveresultat's organiser page for the competition, where somebody could change its settings or clear its data, so treat it like any other password.

• Who can see it. It's shown on the Live results tab, to whoever is using Manager — after the manager PIN, if you've set one (see Settings → Access protection). Spectator screens, the kiosk and the info screens never receive it, and it never appears in the audit trail or the server's logs. The Organiser page link is opened the same protected way, so the password never shows in an address another device could pick up.
• Where it goes with the event. It's stored with the event, so it's in every backup of the event and in the copy you publish to the cloud (the cloud doesn't show it to anyone). That's why publishing keeps working after you move an event to another computer, and why a backup file should be kept private.
• A duplicated event doesn't get it. A copy made with Duplicate is not linked to any competition.
• If you lose it, sign in to liveresultat with the organiser email.

An event linked to a competition before this version of Manager holds an ID but no password, and can't publish. The tab says so: Unlink, then Link existing… again with the ID and the password.

What is published, and when

Publishing runs only while the event is live — from Start event until you finish it. Every ten seconds Manager checks whether anything that affects results has changed, and if it has, sends only what changed: a new finish, a corrected start time, a runner moved to another class. A quiet ten seconds sends nothing at all, so a busy radio network doesn't mean busy uploads. If Manager is restarted mid-event, it reads the competition back from liveresultat and carries on from there rather than sending everything again.

For each competitor liveresultat gets their name, club, class, bib, start time, status and — once they've finished — their time.

• Splits are radio controls only. Each class's split columns are the radio controls it has (see Controls and radio controls), and only times at those controls are sent. A class with no radio controls shows finish times and no split columns, even after cards are downloaded. Mark or unmark a radio mid-event and the column appears or disappears on the next update. A control code above 999 can't be shown as a split.
• Runners still out show no time. A runner who hasn't started and one who is on course both appear without a time, never as a time of zero.
• Statuses. OK, DNS, DNF, MP, DSQ and Overtime are sent as they are. A No timing (NT) runner appears as approved without a time. An Out of competition (OOC) runner appears with their time like anyone else, because liveresultat has no such status, and Not competing (NP) and Cancelled entries appear as DNS. A runner marked OK with no running time is sent as MP, so they can't top the class with a time of 0:00.
• Relays. liveresultat has no teams, so each leg is published as its own class, named after the class and the leg — Men Open-1, Men Open-2 and so on. The team's name appears in the club column and the team's bib as the bib. Each runner's time and splits are their own leg's, measured from their changeover, not the team's running total. A leg whose previous runner hasn't finished yet shows no splits. There's no team total on liveresultat.
• Quarantined classes are published as a start list: each runner with their allocated start time, shown as not started, with no splits and no finish times, until the class is released. See Results quarantine.
• Score and scatter courses can't be published. liveresultat ranks on time and expects every runner to visit the controls in one order. If the event has any score or scatter course, nothing is published for the whole event, and the dashboard card says why.
• Names, clubs and classes longer than 50 characters, and bibs longer than 10, are shortened.

Checking it is working

The Liveresultat card on the event dashboard is the place to look. It shows the competition's ID with the Organiser page and Spectator links, and:

• a headline: Published or Hidden when all is well; Publishing is failing, with the reason and a count of Failed attempts; No recent update if no check has run for two minutes; or No competition created yet;
• Status — Idle (all sent, waiting for the next change — the normal state), Sending, or Not started (the event isn't live);
• Last sent — when changes were last uploaded. On a quiet field this can stand still for a long time, which is fine;
• Last checked — when Manager last looked for changes. This one should keep moving while the event is live;
• Activity — a chart of the last half hour's uploads.

The surest check is to open the Spectator link and look for a runner you've just downloaded.

If publishing fails three times in a row, an alert appears across Manager — Publishing to Liveresultat is failing — so you'll see it on the Download card and Results screens too. A single failure on its own is not reported: a moment's dropout at a venue is normal, and the next attempt catches up. When it recovers, the alert goes and a second one says it is working again. Nothing is lost while it's failing: the next successful upload sends everything that changed in the meantime.

When it fails

What it says	What to do
Liveresultat could not be reached. Check that this computer is online.	Check the internet connection of the computer running Manager. Publishing retries by itself.
Liveresultat reported an error of its own.	A problem on liveresultat's side. Wait; it retries by itself.
Liveresultat is busy and asked meshO to slow down.	Wait; it retries by itself.
Liveresultat did not accept the upload password for this competition.	The password was mistyped, or changed on the organiser page. Unlink, then Link existing… with the current password.
This event's competition no longer exists on Liveresultat.	Check the Competition ID. If the competition was removed, unlink and create or link another.
Liveresultat would not accept what was sent.	The server log has liveresultat's reason. Send it to support with a backup of the event.
Liveresultat cannot show score or scatter courses…	Nothing will publish for this event. See What is published, and when.
No competition has been created on Liveresultat for this event yet.	Publishing is switched on but no competition is linked. Create or link one, or switch publishing off.
This event holds no upload password…	Unlink, then Link existing… with the ID and password.

Stopping, unlinking and publishing again

• Finishing the event stops publishing. What's on liveresultat stays there.
• A correction after finishing is not sent. If it matters, click Restart event (see Restarting an event you've already finished): publishing resumes and sends the difference, then finish again. Restarting counts as starting, so with Publish automatically on start on, a competition you had hidden is listed again.
• Switching off Publish to Liveresultat stops this event publishing; the competition stays linked, so switching it back on carries on where it left off.
• Hide takes the competition off liveresultat's start page but leaves it reachable by its link.
• Unlink detaches the event from the competition and forgets the upload password. Nothing on liveresultat is changed or removed. To link it again you'll need the password, so note it first (or open the Organiser page) if Manager is the only place you have it. Unlinking is also the way out if you've linked the wrong competition: it stops at once, even part-way through an upload.
• Removing a competition can only be done on liveresultat, by the organiser signed in with the organiser email.

Manager publishes an event only while it is live. With two events live at once, each publishes to its own linked competition, and finishing one leaves the other publishing.

Publishing to the meshO cloud

The meshO cloud, at events.mesho.live, is a public copy of meshO Manager where finished events can be browsed online: results, splits, start lists and analysis, the same pages spectators use on their phones at the arena. It's the place to send people who want the results after they've gone home.

How it's set up

It works out of the box. In Settings → Cloud sync (see Settings):

• Publish events to the cloud automatically when they are finished is on to begin with. Finishing an event queues it, and it goes up in the background.
• Cloud URL points at the meshO cloud, and Push token is left blank because Manager carries its own token for it. Test connection checks the address.
• Running your own cloud server instead? Enter its address and its push token. Clearing the Cloud URL turns cloud sync off.

Each event decides for itself

Event details → Cloud sync has Publish automatically when finished, with three choices: Use global setting (shown with whether that is on or off), On for this event and Off for this event. Turn it off for a training run, a private club event, or anything else that shouldn't be public — before you finish the event.

The same tab shows where the event stands on the cloud, with Open spectator page; a Push to cloud button; Delete from the cloud; and the Sync history — every time the event was published, updated or deleted, whether that was Automatic or By hand, and how much was uploaded.

When it goes up

• On finish. Nothing is uploaded while any event is live, so the upload never competes with radio punches or liveresultat for the venue's connection.
• No internet at the venue is fine. The request is kept with the event on disk. Finish, close the laptop and go home: the event goes up the next time the computer is online, after a restart too. An unreachable cloud is tried again by itself, and at once when the computer's network changes.
• By hand, any time, with Push to cloud on the event's card on the Events page or on the Cloud sync tab. A push is a snapshot of the event at that moment; the cloud copy doesn't follow the race as it happens.
• Again after a change. Restart a finished event to correct something and finish it again, and it's published again. Each later push replaces the cloud copy and keeps the same spectator link.

The small grey cloud beside a finished event's status chip on the Events page shows where it stands: a tick once it's on the cloud, a clock while it's waiting, and an exclamation mark in the warning colour for something waiting won't fix — a refused token, or an event larger than the cloud accepts. Hover over it for the reason.

What the cloud copy shows, and what it doesn't

The upload is the whole event, like a backup. What the public sees of it is what spectators see at the arena — names, clubs, classes, start times and results — and less in some respects:

• Birth year and sex are never shown. No public page on the cloud serves them, to anyone. They are carried in the copy only so that meshO Events, which reads pushed events as the record of results, can tell apart two people with the same name in the same club. See Birth year and sex.
• Notes and custom competitor fields are not private. Nothing displays them, but the competitor data behind the public pages carries them. Don't put anything in a note you wouldn't want public.
• Quarantined classes stay hidden until the event is finished, or two days after its date, and say Results are not being shown yet. The cloud doesn't go by the time of day, because its clock may be in a different time zone. An event published on finish has released every class already; this matters for a copy pushed by hand mid-event. See Results quarantine.
• It's a copy, not the event. The cloud receives no radio punches or card downloads, and changes are made on your computer and pushed again.
• Video recordings are never sent.

Taking an event down

Delete from the cloud on Event details → Cloud sync takes the event off the public site. The event on your computer is not touched, and its automatic sync is switched off so that finishing it again doesn't put it back.

To stop an upload that hasn't happened yet, turn automatic sync off — in Settings for every event, or on the event's Cloud sync tab for one. Anything already queued is paused, and resumes if you turn it back on.

A restored or duplicated event is never linked to the original's cloud copy: publishing it creates a separate cloud event (see Moving an event to another computer).

Other ways results leave Manager

• Upload to Eventor — the final results, or the start list, sent straight to the event on Eventor. See Uploading to Eventor.
• Live export — an IOF XML results file rewritten on a schedule, for another results program watching a folder, such as liveresultat's own EmmaClient. It's separate from publishing to liveresultat described above; you don't need both. See Live export.
• Livelox — trackers' GPS positions sent to Livelox during the race. See Tracking.
• The spectator site and kiosk at the arena, on the event's own network. See Reaching the server.

Related

• Results — the Results screen, and where else results appear while the event runs
• Results quarantine — holding back elite classes, on liveresultat and on the cloud
• Settings — Cloud sync
• Creating an event — the other Event details tabs
• Moving an event to another computer — what happens to the liveresultat link and the cloud copy
• Exporting data — results files and Eventor
• End-of-event checklist
• Running two events at once — two live events, each publishing to its own competition