Rogue Scholar Posts

language
Published in quantixed

2023 has been a great year in running for me. Previous running round-ups are here (2022, 2021). My two main goals for 2023 were to run 3000 km and also to run 50 HM-or-more distance runs. I managed both with a couple of weeks left. I also bagged new PBs for 5K, 10K and half marathon as well as a handful of segments on Strava. I won no races but I did win two little running competitions at work.

Published in quantixed

2022 was my best year for running to date. In 2021, my goal was to run 2021 km. For 2022, I wanted to see if I could run 2500 km and also to run 50 HM-or-more distance runs. I managed both and ended the year on a total of 2734 km. I also bagged two PBs for half marathon. Of course, if you subscribe to Strava or VeloViewer or whatever, you can get a nice data visualisation of your year in running.

Published in quantixed

There are lots of ways for runners and cyclists to analyse training data. A key question most fitness enthusiasts want to know is “how am I doing?”. “How you are doing” is referred to as form . Unsurprisingly, form can be estimated in many ways. One method is using training stress scores (acute training load and chronic training load) to assess form as training stress balance.

Published in quantixed

By 30th September 2022, I had clocked up a total of over 2000 km of running in 2022. This milestone was a good opportunity to look at how I got to this point. The code is shown below. First, we can make a histogram to look at the distance of runs. From this type of plot it’s clear that my runs this year consist of a lot of 4-5 km runs and then a chunk of 21 km plus.

Published in quantixed

Reading about someone else’s recovery-after-injury story can be a bit dull. At least that was my conclusion after pressing delete on my story a moment ago. Having spared you the details, the summary is: I got injured. It hurt. It took me a year to recover because I didn’t tackle the recovery properly.

Published in quantixed

A short follow-up post. Previously, I looked at how to reproduce a Strava feature that compares performance over similar courses. With a few modifications to the code, I was able to analyse a much larger dataset of cycling performance on similar courses. Two courses with the highest number of tracks are shown below. I cycle these courses all the time. Well, I did until the pandemic struck.

Published in quantixed

One of several features that Strava put behind a paywall was the ability to compare performance on similar courses. I miss this comparison tool and wondered how hard it would be to code my own. I would love to… but I don’t subscribe This post is a walkthrough of how I approached the problem. The code is available here. It uses the trackeR library in R to convert the GPX tracks to a huge dataframe. This is then processed by IgorPro.

Published in quantixed

Joe Friel reposted an article earlier this year on Efficiency Factor in running. Efficiency Factor (EF) can be viewed in Training Peaks software and he describes how it is calculated. This post describes how I went about calculating EF in R using a single gpx file. What is Efficiency Factor (EF)? Essentially, EF is the average distance that you are propelled forward per heart beat. The higher the number, the more efficient you are at running.