Event Management & Forum System (Q's, Comments & Suggestions)
RacingRulesOfSailing.org Now Has Fleet Scoring!
Despite confidently asserting that RRoS would never implement scoring, I am proud to say we have done it anyway. After years of avoiding the regatta management feature most noticeably missing from the platform, fleet scoring is now built into RRoS.
Here is what we have built:
Multiple scoring systems. Each fleet can be scored under low point, bonus point, time-on-time, or time-on-distance. Handicap fleets use elapsed time and a boat rating to compute corrected results.
Flexible fleet structures. A regatta can have as many fleets as needed, each configured independently as a fleet, division, or scoring group. Entries can be filtered by boat class, division, handicap, or club so the right competitors appear in the right fleet automatically.
Full finish code support. All standard RRS penalty and scoring codes are supported: DNF, DNS, OCS, BFD, DSQ, DNE, RET, DNC, NSC, RAF, UFD, ZFP, SCP, and AVG. Codes are scored according to the rules — DNC scores N+2, BFD and DNE are non-excludable, ZFP and SCP apply percentage penalties, and AVG is computed from the boat's other finishes per RRS A9.
Throwouts. Configurable per fleet — a fixed number of discards, or one throwout earned automatically every N races sailed.
Corrections. Race results can be amended after the fact through a structured correction workflow. Corrections record the reason (protest penalty, redress, RC error, inquiry, or manual adjustment) and update the standings immediately.
Live standings. The standings page updates automatically as finishes and corrections are entered. Results are also available as a printable PDF or CSV export.
You will find the Help Page here.
As this is a new feature, we recommend you start with a test event or a smaller event in order to understand how the system works. If you have questions or feature requests, please respond to me at the email above.
Here is what we have built:
Multiple scoring systems. Each fleet can be scored under low point, bonus point, time-on-time, or time-on-distance. Handicap fleets use elapsed time and a boat rating to compute corrected results.
Flexible fleet structures. A regatta can have as many fleets as needed, each configured independently as a fleet, division, or scoring group. Entries can be filtered by boat class, division, handicap, or club so the right competitors appear in the right fleet automatically.
Full finish code support. All standard RRS penalty and scoring codes are supported: DNF, DNS, OCS, BFD, DSQ, DNE, RET, DNC, NSC, RAF, UFD, ZFP, SCP, and AVG. Codes are scored according to the rules — DNC scores N+2, BFD and DNE are non-excludable, ZFP and SCP apply percentage penalties, and AVG is computed from the boat's other finishes per RRS A9.
Throwouts. Configurable per fleet — a fixed number of discards, or one throwout earned automatically every N races sailed.
Corrections. Race results can be amended after the fact through a structured correction workflow. Corrections record the reason (protest penalty, redress, RC error, inquiry, or manual adjustment) and update the standings immediately.
Live standings. The standings page updates automatically as finishes and corrections are entered. Results are also available as a printable PDF or CSV export.
You will find the Help Page here.
As this is a new feature, we recommend you start with a test event or a smaller event in order to understand how the system works. If you have questions or feature requests, please respond to me at the email above.
Created: Today 03:44
Comments
Format:
You must be signed in to add a comment.
The trouble with such developments is you will start to get 100's of "what about this" scenarios. For example what happens if A5.3 is activated in the RRS.
I suspect you will get requests for some form of "import" of places/elapsed time. In my experience the challenge with all these things is how you match boats.
I'm also not sure you've mastered the handicap process. What you've described will work for some scenarios but it's clear from posts on here that the UK and AUS (at least) will use average lap handicap racing which means you also need a number of laps in the time entry.
Having scored many a handicap race, use of hh:mm:ss entry makes entirely logical sense from a developer pe spective but is a pain for data entry. For several reasons. HH is relatively rarely entered in dinghy handicap races, and even a race going over 60 minutes might have a time recorded as 65minutes etc depending on how the finish boat watch works. But, also the use of : on a keyboard requires two hands. Use of a decimal can be done from the number pad. So some scoring systems allow the entry to be[H[H]].MM.SS format and the MM can be >60
Good luck with your developments. It does seem entirely logical that a single platform handles it all.