Race Day Scoring

[Shawn McAfee]

I saw that recently a new option was implemented to post start lists directly from Run Sign Up. This works seamlessly and is such a great addition. 

I wanted to follow that up and find out if there is a way to utilize Race Day Scoring as a bridge to post live results back to RSU. For a DIY timing kit like mine (ZEBRA fx9600 reader + antennas) I've been told that Race Day Scoring requires a Middleware such as Agee Race Timing or Webscorer that can interact directly with the reader. 

Is there a folder where reads are collected and updated to on a PC? 

[Vesa Suomalainen]

We will be adding a feature to the app in the next app update that will collect all the raw reads by the reader - which is the data format Race Day Scoring (RDS) expects to see.  This data will be exportable in file format during / after the race both from the app to a local CSV file as well as from the posted results page in XLS format.

The way RDS works is that the raw chip data is analyzed by RDS by applying filters you specify via RDS race setup for race start times, duplicate detections, lap timeouts etc.  In other words, the same type of setup & logic that the Webscorer app performs in real time when it gets chip detections from the reader.

So results are only as live as you can feed the raw chip data stream to RDS.  What advantage would RDS provide over Webscorer LIVE results?

Another method for getting live results is to use the Master / Helper timing mode in Webscorer PRO which will copy results from the Master timing device to a Helper device in real time over Bluetooth.  We’re making several enhancements to this feature to make it easier to use as “Announcer View”.  We had the local MFG Cyclocross series use this feature by their race announcers at their last race (see photo) and I will visit their event this coming Sunday for more desting.  Main timing device is an iPad (connected to an Impinj R420 reader) and the announcers used another iPad for viewing the live results.  

Regards,

Vesa Suomalainen

Webscorer Inc

--
You received this message because you are subscribed to the Google Groups "Webscorer Users Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to webscorer-users-...@webscorer.com.
To view this discussion visit https://groups.google.com/a/webscorer.com/d/msgid/webscorer-users-group/5e5cea28-4631-4606-b670-ad52db61d7e3n%40webscorer.com.

[Shawn McAfee]

Thanks Vesa, as always your product is fantastic and you are very helpful. 

The advantage that I see with RDS is specific to scenarios where we provide contract timing services for outside organizations that run their registration through RunSignUp. As a racer the expectation is that results, both live and post-race, will be available at the same website that they registered through. 

We currently send an email to all participants with a link to the Webscorer Live results, but we frequently have confused participants who are expecting that the results page of their registration site will have those listed. If the raw reads file was made available to the RaceDayScoring service that should update their results on the RSU website as close to real time as the current live link does and would reduce the number of questions we get at the timing tent. 

[Vesa Suomalainen]

Once the race is over, you can download the Webscorer results as XLS and post the results to RunSignup via file upload.  There is an API to access live results data on Webscorer so it is possible to write a program that uses the JSON API on Webscorer to get the data and use the RSU API to post the data to RunSignup.  The results format between the two platforms is too different for a generic tool to cover all types of races and race options.