Thursday, February 5, 2015

The Yukon Quest on GPS or Google Earth

Last year, we provided some Iditarod track files for quite a large number of software applications. This year, for the Quest, I've prepared copies of the most popular file types:

  • a KMZ file for use with Google Earth
  • a GPX file for use with compatible GPS units, such as Garmin's

KMZ file loaded into Google Earth

The files contain the same information: checkpoint (and dog drop etc) locations as well as the race trail for odd years. I condensed this data from a variety of sources and hand-cleaned it, but obviously it will only be approximate, and the trail will vary from year to year. Also, because the trail is made up of points that are about half a mile distant, the total distance is being underestimated (it comes out to 911 miles according to this track). So please take this (ENTIRELY UNOFFICIAL) file with a good pinch of salt! If it is helpful or useful, I'd be glad. 

Tuesday, February 3, 2015

The predictive value of split differences

It seems that the format of the Knik 200 trail was not that much fun for teams, so we had a few mushers who didn't need qualifiers checking out early (that is to say, scratching).  But, the format also gave us an opportunity to look at some data that haven't been available in the past for distance racing.

The Knik had mushers running from Deshka Landing up to Yentna and back, twice.  That is to say, they passed over the same piece of trail 4 times.  This gave us an opportunity to look at whether or not the consistency of the speed with which they covered the trail had any predictive value, in terms of final placement.  If someone had pretty much the same times on each race leg, did they tend to finish higher or lower in the standings?

So, I created a spreadsheet sheet in which I took the differences between the two up times, the differences between the two back times, and the sum of the absolute values of the differences.  This gave me a handle on just how much variability there was in a team's runtimes.  I then ran correlations on the total differences, the run to Yentna differences, and the run back differences,  I found a fairly strong correlation between the summed runtime differences and final placement, but with also a fairly large standard error given the size of the field.  That is to say:
a team whose times remained consistent from split to split tended to finish better than a team whose times varied more from split to split
This should not be particularly surprising, since the source of speed variation tends to be slowing down due to tiredness, etc.  Another source of consistency, other than conditioning and fitness, could be the musher's expertise in managing their team's resources.  Steady speeds probably don't cause a good finish, but they can tell us something about the team's "quality" (for lack of a better word).

In the correlations I ran, the difference in splits was the independent variable, and finishing position the dependent variable.  Here's the table, with the first correlation being between the summed differences and the finish, the second being the summed differences on the run to Yentna, and the third beingn the summed differences on the run from Yentna back to Deshka:

correlation coefficient:0.7031
standard error:5.4138
correlation coefficient out splits:0.5768
standard error:6.2195
correlation coefficient in splits:0.5781
standard error:6.2121