Originally posted on June 10, 2016 on Phidippides: A Data-Informed Marathoner’s Toolbox by John Stanton-Geddes
To determine how much slower 2016 was due to the temperature, I found the time in 2016 for the finishing place at each time threshold in the previous years. For example, in 2015, 92 runners finished under 3 hours, and in 2016, the time for the 92nd finisher was 3:11:53. Using this data, I then calculated the percent time difference between the Xth finisher in each year. For the example I just gave, the 92nd finisher in 2016 was 7% slower than the 92nd finisher in 2015.
I grabbed hourly weather data from wunderground for each race day, and using this data I fit a statistical model using the temperature at 10am (2 hours into the race) to predict how much slower the average runner’s pace was in 2016, 81C at 10 am, then if the race had been at cooler temperatures.
This table shows that a 3 hour marathoner was ~5% slower in 2016 than if the race temp had been 60C, and ~7% slower than if the temp had been 50C. This may not seem like much, but for a 3:30 marathoner (8 min/mi pace) they would slow to 8:33 min/mi pace, or a 3:44 marathon. Bummer.
I also noticed that the percent pace slowdown was less for faster runners, which makes sense as they spend less time out in the heat, and their generally higher marathon fitness may have allowed them to perform better given the conditions.
|Time||Temp at 10am||Percent Slower|
Hopefully this provides some consolation to runners out there that yes, they could have gone faster if it had been a cooler day! Better luck next time!
Editor’s Note: John was part of the VCM invited runner’s field in part due to his marathon PR of 2:36:27 (from the 2015 Vermont City Marathon). In the heat this year he ran a 2:42:46 and finished 12th overall.