As promised we hosted another g10k running event and barbecue this weekend. Thanks to all who signed up, came along and joined in. The British so-called-summer did its best to throw us off course, sending lots of people scurrying under a smallish tent at one point. Spirits were undampened (I was already wet from this year’s upgraded water fight) and the bouncy castle got an outing later on.
Nine runners this year, with a speed range of 1.
Twelve intrepid runners completed this year’s g10k race, completing two hot laps of the “lollipop course”. Proceedings were expertly marshalled by the two race officials and race mascot (thanks Sarah, Lauren and Otis). Meanwhile, nobody was taking it easy. Meerkat-style crèche watching kept a handful of heroic grown-up helpers fully occupied while we runners were making our way round the race.
Having more runners than last time made it even more fun.
How do you (reasonably fairly) handicap a race without information about the competitors' abilities?
The idea of handicaps is a pretty simple one: it’s used in golf, chess, tennis and horse racing. It relies on participants' performance data being available, and being trusted: if I’m expected to go round the course in three shots fewer than you, I’ll start with a three shot penalty, and then we’re equally likely to win.