- At request of Jon Krupa, sort meets by date when selecting a TFRRS meet. Also,
allow selection of “All meets” or “Future meets.”
- Both Sid Steinweg and Brian Sparacino reported that they couldn’t send a
TFRRS-XC report to the editor. Turns out that neither had obtained a login/password yet from
DirectAthletics. However, you should be able to produce the report without having a signon.
Fixed.
- We are encouraging users to update to this version since improvements have been made to the RunSignUp
integration with RunScore Results as well as other fixes and improvements.
- Download of registrations from imATHLETE is now officially supported. An earlier beta version
only allowed a download blocksize of 50. Due to a change at imATHLETE, that is now 1000. We would like some feedback from RunScore/imATHLETE users.
- Have included the TFRRSRace in the update download. The NCAA is working with
DirectAthletics and have developed this required format for all college cross-county meets
starting this fall. It will probably also be used for many high school race. We are looking for testers.
- Active Works no longer requires a timer to contact their Active representative for an app
token. The new procedure is: “For a Timer to view an Event’s data, an Event Organizer must ‘invite’ them. When individuals accept an invitation to be a Timer in the system, ActiveWorks Endurance now automatically checks if they have an API token. If not, the system will automatically email the token to them. Additionally, Event Owners and Timers can email themselves an API token by clicking Get Timing API Token on the event dashboard.”
- Uploading RunScore Results to RunSignUp uses the reg_id.txt file in the race folder to store the registration_id
values. A registration_id field is not needed. If it IS used, the results were getting the registration_id from the reg_id.txt file which could cause a problem if the id is in the field and not the file. Made a change so that RunScore now checks for the registration_id in both locations.
- Mark Toretsky and Steven Keith reported that a race simulation caused the
first person in the race to be a non-runner, that is, someone without a bib number. The problem was introduced in 2014 when the simulation was changed so to not include the unregistered runner number. Fixed.
- Bill Teschek reported that the upload of changed records to ChronoTrack Live uploaded the same
records each time. Fixed. Note: if fields such as the age-division field, often called DIV, changes, that does not result in that record uploading. The record is only flagged as changed if the field changed is one of those fields that are to be uploaded. To find out which fields they are, look in the CTLive_fields_mapping.ini file in the RunScore folder. The same is true when uploading changed records to RunSignUp.
- At request of Doug Liverside, extend the number of parameters from 20 to 36 (1 -10, ‘a’ – ‘z’).
Had been implemented only as far as ‘j’.
- Added two features to Announce for use with lap races, requested by Andrés Alañón Vázquez: “lap
distance field” for keeping the lap distance in a field. This is for races where everyone is not running the same distance. Likewise, added “laps left field” to specify the number of laps and to tell Announce to display the number of laps left when everyone is not running the same number of laps.