Category Archives: running

running

Runbritain rankings and how they work

I love the Runbritain rankings, other than that the site is not very reliable, because it gives you an indication of your running performance taking into account the conditions. If you run on a muddy course for example you will probably not get a good time, but the same is true for others. The Runbritain rankings take this into account so you can still get credit for your effort, in terms of a reduced handicap. I also like that only your five best performances are taken into account, so you can run slowly with a friend and not worry about harming your handicap (if indeed you ever worry about such things).

How does it work? I found it quite confusing. There is a video explainer by Tim Grose, one of the two leads for the team at Athletics Data that developed the rankings, but even this is not super clear in my opinion. The problem I think is that the normal view in the Runbritain ranking table for an athlete gives you, aside from the race name and time, two figures, SSS and vSSS. The SSS is the “Standard Scratch Score” and measure the state of the course, where zero is pretty much perfect and anything above 4 is fairly bad. 10 is the maximum and apparently it could be slightly negative though I have never seen that.

On a 5K such as a parkrun, each point is worth about half a minute so a score of 4 would mean most people are two minutes slower than they would be on a perfect course.

Second, the vSSS or virtual Standard Scratch Score shows how well you performed; this can be negative. More on this later.

These two figures though do not show you how the handicap is calculated. Handicaps run from maybe -10 (the lowest currently is -7) up to 54, based on golf handicaps, where lower is better. Imagine that you run a 5K parkrun in 25 minutes. This performance represents a basic handicap of 19.3 before adjustment, a figure calculated from senior age gradings but without looking at your age. Runbritain handicaps do not take account of age; they are purely about how fast you are in absolute terms. The exact table is not given though you could easily work it out.

This handicap is then adjusted based on two things, the SSS and the time penalty. The time penalty starts at -1.5 and gradually increases. To give an idea, an event one year ago has a time penalty of 2.5. So if you ran a 5K parkrun in 25 minutes today, and the SSS was 2.0, that would give you a handicap of:

19.3 -2.0 -1.5 = 15.8

If that event were a year ago it would come out at:

19.3 -2.0 + 2.5 = 19.8

Your final handicap is the average of your best 5 handicaps after adjustment.

Since the vSSS is not part of this calculation, why is it shown? Well, it is kind-of part of the calculation because of the way SSS is calculated. Runbritain rankings does not go round inspecting each course and judging its condition. Rather, its algorithm looks at the results and at how each athlete did versus their best time (best handicap). This figure is called MySSS. So if you equalled your best time it would be zero, if you improved on it (PB or Personal Best) it would be negative, and if you ran slower than your PB it would be positive.

The algorithm looks at the MySSS for all the athletes and the middle one (median) becomes the SSS. Then your vSSS is your MySSS less the SSS.

There may be some slight inaccuracies in the above description but I believe the gist of it is correct. Grose refers to things like “mildly progressive” that suggest some small further adjustments.

Any flaws in this approach? I can think of a few. One is that athletes tend to perform worse as they age, so their performance versus their best time will likely widen as the date of that “best time” recedes into the past. I am not sure that Runbritain rankings takes that into account and if it does, Grose does not mention it.

Another is that there are many reasons for slower performance that are not to do with course conditions, such as illness, parkrunning with a pram, tailwalking (going last to sweep up any runners who have difficulties), and more. This presumably is why Runbritain rankings uses the median MySSS and not the mean, to calculate the SSS, but it will never be perfect.

A third issue is that parkrun is not a race – well, some treat it as a race and try for their best time, others more as a social event with dogs, prams, and chatting to a friend as they run. Nothing wrong with either approach, but that will impact the SSS and implies that someone who tries their hardest in a parkrun may have too low a handicap.

Despite imperfections though the system does work and I find it reassuring, after getting a slow time in bad conditions, that the Runbritain rankings view may show it in a more positive light.

running

A year of running

2 Comments

I am not sure exactly when I became a runner, nor for how long I will be one. But I am sure that when I think back over 2023 from a personal point of view, running is the first thing I think about.

Pic courtesy of Microsoft Paint Cocreator AI

Most of us discover the need for exercise at some point in our lives and for years I have been in the habit of doing a short daily workout, hardly even a workout, but based on the old 5BX plan which takes all of 11 minutes. 5BX includes running on the spot which is effective but quite boring. I replaced it with going out for an actual short run and omitting the jumping jacks.

Then a couple of things conspired to persuade me to do more running. It was partly a side-effect of lockdown, when my wife who was on furlough did the NHS Couch to 5K programme which was followed by an addiction to Parkrun, free 5K runs which take place every Saturday morning at numerous locations around the UK and some worldwide.

Second, an event called the Winchester Half Marathon passes our house and I found myself thinking that I would like to do it myself.

I decided that I might as well join in with the Parkrun and soon enjoyed the challenge of trying to improve my time week by week. That began in July 2022.

I was enjoying it enough that in April 2023 I booked myself into the Winchester Half for September. That gave me 6 months to train, more than enough. I increased my daily run to a 15 minute hilly run three times round the block near my home. I started doing a long run on Sunday mornings, working up from 8K to 10K to 12K and up to 20K, just short of the half marathon distance.

The Winchester Half is somewhat hilly so I booked for the flatter New Forest Half Marathon earlier in September as a practice. That went OK despite rain and I finished in 2:03:50. Winchester went a bit better and I did 1:58:27. Ambition fulfilled.

I was enjoying it too much to give up though, and since then have joined the local Winchester Running Club and booked for several more events next year. I also did the AWS re:Invent 5k in Las Vegas which was fun if a little odd in the way it was organized!

I have started running relatively late in life and wish I had done it earlier; but it is also fun to do something new. Often I meet people who tell me they also loved to run but had to stop due to injury, sometimes knees, sometimes something else. I do not think running is risk-free but I am convinced that it is more likely to do good than harm. I have just read Daniel Lieberman’s book Exercised; Lieberman is a professor of biological sciences and writes that “the negative effects of too much exercise appear to be ridiculously less than the negative effects of too little.”

Even the risk to knees is not clear-cut. “Physical activities like running that load joints repeatedly and heavily do not cause higher rates of osteoarthritis and may sometimes be protective,” writes Lieberman, referencing a 2008 study in the American Journal of Preventive Medicine.

There are consequences though. I have lost weight. My resting heart rate has slowed. And it is time-consuming, especially if one trains for the longer distances.

I realise though that I may not always be able to run. That for me is all the more reason to run while I can.

running, tech

The AWS re:Invent 5K run 2023

2 Comments
Sunrise over Las Vegas – at the re:Invent 5K run 2023

It happens that, a little later in life than most, I have taken up running, and during the recent AWS re:Invent in Las Vegas I was one of 978 attendees to take part in the official event 5K run.

If there were around 50,000 at the conference that would be nearly 2% of us which is not bad considering the first coaches to the venue left our hotel at 5.15am. The idea was that you could do the run and still make the keynote I guess – which I did.

I would not call myself an experienced runner but I have taken part in a few races and this one seemed to have all the trimmings. The run was up and down Frank Sinatra Drive, which was closed for the event, and the start and finish was at the Michelob ULTRA Arena at Mandalay Bay. Snacks and drinks were available; there was a warm-up; there was a bag drop; there was a guy who kept up an enthusiastic commentary both for the start and the finish. The race was chip timed.

We started in three waves, being fast-ish, medium, and run/walk. I started perhaps optimistically in the fast-ish group and did what for me was a decent time; it was a quick course with the only real impediments being two u-turns at the ends of the loop.

Overall a lot of fun and I am grateful to the organisers for arranging it (it does seem to be a regular re:Invent feature).

Here is where it gets a bit odd though. The event is pushed quite hard; it is a big focus at the community stand outside the registration/swag hall and elsewhere at the other official re:Invent hotels. It is also a charity event, supporting the Fred Hutchinson Cancer Center. All good; but I was surprised never to be officially told my result.

I was curious about it and eventually tracked down the results – I figured that with chip timing they were probably posted somewhere – and yes, here they are. You will notice though that no names are included, only the bib numbers. If you know your bib number you can look up your time. The QR code on the bib also links to the results. This was mine.

It seems that AWS do not really publish the results which would have disappointed me if I had been the first finisher who achieved an excellent time of 16:23 – well done 1116!

I can’t pretend to understand why one would organise a chip-timed race but then not publish the results. Perhaps in the interests of inclusivity one could give people an option to be anonymous but for most runners the time achieved is part of the fun. I think we were meant to be emailed our results but mine never came; but even if I had received an email, I would like to browse through the full table and see how I did overall.