RaceDay Scoring Pre-Alpha Walk-Thru

rdgo_scoring

We will be giving timers an Alpha version of RaceDay Scoring at the RunSignUp Symposium next week. Matt Avery will be doing a tutorial and we will be handing out USB’s with the Mac and Windows native versions. We still have a long way to go, but RD Scoring can be used to score a simple, real race. In addition, all the “guts” are there to score complex races. We are looking to get some testing and feedback at Symposium.

This blog is being written beforehand to provide some written instructions and context for either before or after the tutorial. There will be changes between the time of this blog and the Alpha even…

RDScoring has this architecture:

Screen Shot 2017-07-11 at 12.49.45 PM

The Connectors, Timing Filters and Scoring Engine are what makes up RDScoring, and is what will be installed as a native Windows or Mac app on your PC.

The main Dashboard of RD Scoring takes you thru the process of setting up a race – mostly in the order of the menu at the left. This interface is likely to change a fair amount to make things easier and hide some of the “raw” complexities that are a bit exposed in the Alpha:

Screen Shot 2017-07-11 at 3.00.01 PM.png

The typical steps to scoring a race are:

  1. Setup Race. Today this is done by connecting to RunSignUp and syncing race and participant data.
  2. Timing Devices. This is where the definition of your timing equipment is done.
  3. Timing Locations. This maps your timing devices to specific locations like Start, Finish, 10K Split, Triathlon Bike Transition Exit, etc.
  4. Scored Events. Defining which events get scored and mapping the Timing Locations. For example picking the 5K, Then setting the Start and Finish Locations, and defining the Approximate and Actual Start times.
  5. Segments. Entire Race is the default segment, but you can define any number of segments for things like splits, or triathlon segments like swim, transition, etc.
  6. Age Groups. Define age groups and gender for scoring. This will expand to have many scoring parameters like Athena and Clydesdale.
  7. Participants. This is where you can sync and edit and add participants.
  8. Scoring. This is where you define how you score top finishers (chip or gun time), how many people in each age group, whether there is double dipping, etc.
  9. Reports. This is where you format and define the output (View, HTML, PDF, Sync to RunSignUp or other API, etc.) your results.

Step 1 – Connect to RunSignUp and Sync Race and Participant Data

The gear icon at the top right takes you to a configuration page where you can set up to point to either RunSignUp Production or RunSignUp Test. Connecting will show a list of races that you can import from RunSignUp. In a later version you will be able to create stand alone races right in RD Scoring.

Once you have added a race you will see it appear in the drop-down list from the top of the page. When you connect to the race all Participant information will be automatically and bi-directionally synced on a regular basis (and you can also force syncs).

Step 2 – Set up Timing Devices

Timing Devices are the ways you are collecting the times. We support a variety of manual, file and chip timing devices. Once Devices are set up, they are available for other races. Timers with chip systems can set up all of their systems.

Screen Shot 2017-07-12 at 10.48.35 AM.png

Setting up an individual Timing Device is fairly simple, and depends on the type of device. For example, here is a view of the standard RunSignUp Protocol that we will be documenting and putting in open source:

Screen Shot 2017-07-12 at 10.50.03 AM.png

We support a variety of devices in the Alpha:

Screen Shot 2017-07-12 at 10.51.55 AM.png

Note also that we have a variety of actions that we can take on devices, depending on what the device offers and our level of support.

Step 3 – Timing Locations

Screen Shot 2017-07-12 at 1.06.37 PM.png

Once Timing Devices are setup, you can then assign the devices to one or more Timing Locations. You should typically have a Start and Finish (Lap Races will get added later), as well as Splits. There are also parameters to filter, such as bib ranges and times. You also set the priority of devices for primary and backup.

Screen Shot 2017-07-12 at 1.08.01 PM.png

Step 4 – Scored Events

A Race may have multiple Scored Events, like a 5K and a 10K. This let’s you set up each Scored Event based on the TIming Locations. In the example below, there are a number of events, and the setup is just for the 5K. Note how it aligns the Starting Point and Endpoint with one of the Timing Locations (Start and Finish).

One of the key parameters here is the entry of the Actual Start Time. This will be used for calculating gun time based off of time of day scored reads during scoring.

Step 5 – Segments

There is a default segment called Entire Race that accepts all of the data defined earlier. The only real data to change would be Endpoint occurrence in case a timing location is being passed several times in a race.

Screen Shot 2017-07-12 at 1.17.21 PM.png

You can add segments for splits and other uses like triathlons.

Step 6 – Age Groups

This is a pretty simple form today, that will gain power as we move toward release. Today it is a pretty manual process for entering in gender and age groups.

Screen Shot 2017-07-12 at 1.18.20 PM.png

Step 7 – Participants

If you are syncing with a RunSignUp race, it will also sync the participant information (bidirectionally). It has search and display capability:

Screen Shot 2017-07-12 at 1.19.45 PM.png

And you can Edit and add participants:

Screen Shot 2017-07-12 at 1.21.55 PM.png

Step 8 – Scoring

We are using a concept called a Listing. A Listing is a way of taking computed fields and doing filtering (like looking for Females 21-40) and Sorts (like sorting the fastest in that filtered group) to produce a Listing Output. The quick view of a listing output will be something like this:

Screen Shot 2017-07-12 at 1.27.13 PM.png

A group os listings will look something like this:

Screen Shot 2017-07-12 at 1.29.00 PM.png

We do not have a User Interface yet to allow you to define Listings yet. Only 3 default Listing Templates, which are mechanisms to read the setup data like Age Groups and Gender, and create each individual Listing. We are including 3 default Listing Templates:

Screen Shot 2017-07-12 at 1.22.54 PM.png

Each Template will read the setup information from previous steps (like Age Groups and Gender) and create each Listing automatically.

Techie Note: Templates are actually JSON files that define how to create a Listing (also a JSON file). This makes the RD Scoring platform very open – where anyone with the proper knowledge can create listing files. And since these Templates and Listings have a standard portable format, they can be shared in the RD Scoring community. This means there could be several different people working on the best XC Scoring Template and it will provide the community with many options and flexibility. In the Alpha version, we give you the ability to download the templates (but there is not documentation yet on how you could do your own). Eventually we will have several wizards and screens in the tool to allow you create Listings and Template Listings easily by clicking and dragging.

Screen Shot 2017-07-12 at 1.35.59 PM.png

Step 9 – Reports (Result Publication)

This is another area that will receive a lot more ease of use features before it goes to production. Right now you have to hand build each report.Screen Shot 2017-07-12 at 1.36.38 PM.png

There are several output formats today, with more coming (like API connections to RunSignUp and others). Clicking on View will run the report in RD Scoring. :

Screen Shot 2017-07-12 at 1.38.39 PM.png

This is the report builder today for the above report:

Screen Shot 2017-07-12 at 1.40.05 PM.png

See how Column 1 is multiple fields and we provide a way to concatenate these fields with a space between the First and Last names.

Fields can be static text or they can come from scored read data, participant information or output from the Listings. In this case I am adding a column to show the total number of overall finishers that is being generated by the listing:

Screen Shot 2017-07-12 at 1.47.30 PM.png

Note how I centered the new field and it is added to the Report View:

Screen Shot 2017-07-12 at 1.48.25 PM.png

Summary

As you can see, we have created much of the foundation for the next generation of Scoring. When it is fully released, it should be easier to use than The Race Director, and have the type of customization power that RunScore provides. We are also hoping for a robust community that will share Listings and Report Templates.

We are releasing the Alpha next week to start to get some input and testing. We are hoping to release a Beta in the next couple of months that will introduce more ease of use and configuration, the ability to handle non-RunSignUp races, and much more documentation than this blog.

New Individual Results UX

We have released the new User Experience (UX) for viewing individual results:

unnamed-2.png

If the individual has a profile photo, then it will appear as well:

Screen Shot 2017-07-12 at 10.41.09 AM

(BTW, that photo is of Meredith Klein, our UX Engineer who designed this new page!)

We have some more improvements coming on Results, so stay tuned!

P.S. Just to remind you how horrible it used to look…

unnamed-3.png

Timer Dashboard

We have released the first wave of our new Timer Dashboard. As the name implied, this is for timers to be able to manage all of their races in a single place – whether they are the Partner for a race, the actual race director or have been added as the Timer for a race:

Screen Shot 2017-07-12 at 8.46.07 AM.png

This first version is mostly focused on giving timers direct and easy access to manage RaceDay related things for races. They have quick access to each full Dashboard, or a quick “Actions” menu that will take them directly to where they need to go:

Screen Shot 2017-07-12 at 8.46.25 AM.png

You can add Secondary users, and begin to manage your information.

We will be adding a number of things over the coming months:

  • Add non-RunSignUp races easily
  • Consolidate various timer accounts you may have
  • More information about your business, which will be used to provide better guides for race directors looking for timers
  • The Race Director and RD Scoring license information
  • Direct access to RD ¬†Scoring on the web to manage multiple local RD Scoring systems at multiple races
  • Manage your Race Calendar, similar to Sponsors – keep track of race commitments, invoice customers, collect payments, automate renewal processes, etc.
  • Track resources like equipment and people as they are assigned to races

RaceDay Scoring – Participant Editing

rdgo_scoringWe are happy to release the first step of RaceDay Scoring, our cloud and mobile based scoring solution that will be rolling out this year. Timers and Race Directors are now able to edit participant information without impacting the participant’s RunSignUp Profile or the information in other races.

Here is an explanation of what happens:

  1. Participant Signs up for a race. That information that is entered is their Profile information and belongs to the User.
  2. A copy of that information is now stored with the Race. We call that the Race User information.
  3. The Race Director and Timer can now change that information independent of the Participant’s core Profile – or affecting information in other races.
  4. If the Participant updates their core Profile information, it does not affect the Race User information.

This gives Race Directors and Timers the type of control they need, without impacting the participants private information. We will be adding other conveniences that make things simpler for Timers especially on race morning during the heat of moment – changing Age or Gender or Event (from Full to Half Marathon for example).

Remember, Participants editing their information will NOT change the information in any races that they have already registered for. If they need information updated for races they have already registered for, they will need to contact the race directly.

Custom RaceDay Web Results from The Race Director

racedirector-logoThe Race Director is one of the two leading scoring packages used by timers, along with RunScore. Both offer tight integration with RunSignUp – bi-directionally syncing participant information, posting results, sending TXT notifications of results, etc.

One of the features we built in RaceDay Results (aka RunSignUp Results – the ones that show up as part of a Race website), is the ability to upload a custom result set. This means that The Race Director and RunScore can basically post any report and format they want onto the web easily. We originally built this for RunScore, since there is not a fixed format to the data schema.

Recently, The Race Director added the capability to upload Custom Results Sets. It is set up on this interface in The Race Director:

rd0

The define the page information:

rd2

Overall Finish List ‚Äď right now, this is available only for when you are producing a finish list with no splits.¬† In this local race, quite a few who registered are identified as Gerber employees in an optional data field.¬† When the output is produced all the settings from the report prompt as far as which columns to include come into play just as they do when you produce the report to spreadsheet or HTML.¬† https://runsignup.com/race/results/?raceId=16140

Screen Shot 2016-12-05 at 4.26.41 PM.png

Team Reports ‚Äď I really like how this comes out for detail team results.¬† This may be the blueprint for how we tackle cross country.¬† ¬†https://runsignup.com/race/results/?raceId=13201

Screen Shot 2016-12-05 at 4.27.53 PM.png

Predicted Time and Age Graded Result – https://test.runsignup.com/race/results/?raceId=4388

Screen Shot 2016-12-05 at 4.28.46 PM.png

As timers get a sense of this and want other reports included, let us know and we will try to add them.