Greetings from a more-or-less newbie - can someone please point me to a webpage that explains how to interpret event info when viewing on Livelox? I am particularly curious at the moment what the crossed off times for all places after 2nd mean. I thought it meant disqualified, but after seeing it so much, I am doubting that interpretation. For example, I am looking at the recent Billygoat event (5/14/23, NEOC). Thank you!!
It looks like at least one of the people whose time is not crossed off did not skip a control, as was allowed. All of the others skipped one, Livelox presumably notices a missing control and marks that runner as DNF.
@Cristina is correct (as usual...), Livelox gets hot & bothered by people not punching all the controls. The easiest solution is to define multiple courses per class, one for each legal combination that someone ran.
Untested, but it should work!
From what I'm seeing, those two people did each skip a control (#2, #3), just not the most common #19. But other people who skipped the same controls that they did haven't uploaded tracks to Livelox.
Ahhh - so I was maybe kind of on the right track, but it just isn't applicable in this instance, as skipping a control was explicitly allowed for that course. OK, thank you!!
https://www.livelox.com/Viewer/Billygoat-2023/Bill... shows the split table for the Billygoat class. if you click on the "?" help button in the upper RH corner, it will help with interpretation. You'll note that if competitors are shown with a calculator icon to the left of their name, it indicates that split times are based on the GPS proximity "punch" generated by Livelox. If organizers upload the IOF 3.0 XML file of results, the times in the split table should be identical to the Si-generated splits. Depending on the event admin software being used and whether the skipped controls are accounted for in the calculated results, it's possible that Livelox might accept the "OK" status for runners who followed the rules and show times that are not crossed out.
Thanks for the pointer - I will have to try that help button (?) on other views as well!