Very cool! But I especially like the example of how to connect to runningahead using the api. Thanks!

Now I need to get my own key and then think up something cool to do with it. I would probably use flask.

Well I am glad it is working for some people, although I am still not sure what was happening before. And sdizazzo, I do agree that the API opens up all sorts of potentially cool opportunities -- it's pretty slick.

Even when I throw out the known outliers, Doug's tool gives me around 1.09.

Like I said, either I'm a pansy marathon runner or else I'm just not cut out for it.

Way cool - and like joescott it confirms that I am too damn noncommitted to the training needed to run a quality marathon, or there is some physical limitation that moves me further up the scale. My coefficient is 1.119. Wonder what it is if I throw out the crash and burn in August?

For fun, and since I have been playing around with the RunningAhead API, I built a quick online tool that allows you to analyze your race performance and calculate the coefficient using races stored in your log from 2010 to now.

Hmmm, the traceback shows that it is dying when trying to parse data I get from RA. I modified it to print out the JSON object it is trying to parse if parsing it fails. So If you run it again now it will likely print out something like:

If you post that here, or pm it to me, I can try to figure out what is going on (if there is personal information or whatever, you can remove that bit, I suspect that random non-printable characters are being sent, perhaps in the Notes section). Thanks for reporting it.

Doug

Yep I'm pretty wordy in my notes. With a cursory look, I see a couple of #s, but no gibberish. PMing you the whole thing. Thanks, I'm anxious to see my chart.

Interesting, if I take my last two 5k, half, and full marathons I get 1.0505. Not a surprise, because my 5k times suck.

Just for grins I took my best trail races beyond marathon pace: 30, 50K, 50 mile and I get 1.110. Probably not all that meaningful because the formula is probably not intended to predict 50 mile time. OTOH, it is still below the 1.15 coefficient.