I've updated the season points standings spreadsheet with results from Points #5.
Actually, they've been there since the week following the event. Why so much delay???
In the same round of spreadsheet updating, I also added all of the results for Points #1 - #5 for the newly data-driven Cone Killer award, which I announced at the club meeting last night.
The Cone Killer award is now scored in the same style as Top Gun and Dishman Cup, except instead of awarding points to the drivers with the run with the fastest PAX time and raw time, points are awarded to drivers with the most cones on any given run. Naturally, this leads to very many ties, with nearly all drivers having at least one run with a cone, and plenty with two or three cones, so I think it's important to explain how it works.
If two drivers have the same max-cone-count run, the tie will be broken by the next-highest cone count run of the driver. Consider the following runs, sorted by cone count:
Code:
Driver A | Driver B
6 cones | 6 cones
3 cones | 2 cones
1 cones | 2 cones
clean | 1 cone
The tie-break will favor Driver A over Driver B, because Driver A hit more cones on the next-highest cone count run.
Time for some Q and A.
Q1: But Driver B hit more cones in total AND at least one on every run. Why doesn't the tie-break in their favor?
A1: This is autocross. You aren't supposed to hit cones. This award is just for fun. Don't take it too seriously. Also, having an award that would seem to encourage drivers to hit every cone on every run would be a logistical nightmare for the course workers, and would likely result in a Hold Start while the course is put back together from scratch. If you make a deliberate effort to hit every cone possible, chances are VERY strong a course worker will call in a DNF.
Q2: I hit eleventy bazillion cones on one of my runs earlier this season, but all my other runs all season have been clean. Why isn't my name in the spreadsheet?
A2: The run was recorded as a DNF. Runs that are recorded as DNFs do not contain cone count data, so for all intents and purposes, officially, you did not hit any cones. This is a technical limitation of AXware, and we will be putting exactly zero effort into working around it.
I built this report from scratch, since AXware doesn't have a way to generate it. I encourage those who are interested to
review my code.