Stunts Forum

ZakStunts - the Competition => Competition and Website => Topic started by: dreadnaut on May 17, 2017, 10:57:46 PM

Title: Refreshing the leading time calculations
Post by: dreadnaut on May 17, 2017, 10:57:46 PM
The leading time code is complex, and now and then makes a few mistakes. I've looked at it before (http://forum.stunts.hu/index.php?topic=3319.msg71836), but now I'm carefully cleaning it up, aiming at something solid enough to assign points automatically at the end of the race —at Zak's press of a button!

At the moment I have a test version on a separate page (http://zak.stunts.hu/index.php?page=leading&track=ZCT189), which kind-of narrates the leading time race so that one can tell if it makes major mistakes.

Three things:
Title: Re: Refreshing the leading time calculations
Post by: Duplode on May 18, 2017, 01:19:50 AM
Quote from: dreadnaut on May 17, 2017, 10:57:46 PM
if you have a moment, could you have a look at a race using that page, and see if the numbers are correct?

Two differences I noted in the new Z171 chart (http://zak.stunts.hu/index.php?page=leading&track=ZCT170) (here is the current page (http://zak.stunts.hu/tracks/ZCT170)):

Quote from: dreadnaut on May 17, 2017, 10:57:46 PM
any suggestions about different visualisations? maybe pipsqueaks ranked by leading time, or just the top three, or some kind of table or graph, etc.

A top four ranking would be useful (I say top four because three-way battles for LTB +1 aren't unheard of). One idea for a tweak -- a possibly silly one, that I haven't thought through -- would be making the time axis in the current chart non-linear, to magnify differences around the current leading time.

Quote from: dreadnaut on May 17, 2017, 10:57:46 PM
mid-year seems like a good moment to discuss possible rule changes regarding LTB; for example, Akoss' suggestion (http://forum.stunts.hu/index.php?topic=3139.msg66726#msg66726) about carrying leading time to the next race, or maybe just having then pile up continuosly, with bonus points being assigned as soon as a pipsqueak reaches X hours?

Akoss' suggestion is still fine, though I don't think it matters as much now that the cutoff for LTB eligibility is 24 rather than 48 hours. The season-long leading time suggestion would completely change how we deal with LTB, and it could be implemented in a number of different ways... I don't know what to think of it just yet.