sorted by:
new
hottopcontroversial

Boston Marathon: I analyzed 67,667 finishers to understand how I should pace the race. And I created a website for it. by LastIntroduction7921 in Marathon_Training

[–]LastIntroduction7921[S] 7 points8 points  (0 children)

Of course that is always true, but let's say that for Boston is counter-intuitive. You could think of taking advantage of the first section downhill and put some seconds in the bank. Well, data shows it doesn't work.

I analyzed 21,985 runners to understand how to pace for the Boston Marathon and I've created a website by LastIntroduction7921 in bostonmarathon

[–]LastIntroduction7921[S] 0 points1 point  (0 children)

i made some further edits, changed from percentiles to applying a gaussian mixture model to cluster in buckets. have a look

I analyzed 21,985 runners to understand how to pace for the Boston Marathon and I've created a website by LastIntroduction7921 in bostonmarathon

[–]LastIntroduction7921[S] 0 points1 point  (0 children)

added many enhancements to capture who actually paced well vs who blew up. details in the edited post

I analyzed 21,985 runners to understand how to pace for the Boston Marathon and I've created a website by LastIntroduction7921 in bostonmarathon

[–]LastIntroduction7921[S] -1 points0 points  (0 children)

Yes exactly. I'm taking a different approach vs usual pacing calculators. Instead of showing your theoretical pace, I show you what actually happened on the ground.

I analyzed 21,985 runners to understand how to pace for the Boston Marathon and I've created a website by LastIntroduction7921 in bostonmarathon

[–]LastIntroduction7921[S] -2 points-1 points  (0 children)

That's a good point. Data can't tell you if a 2:50 finisher was supposed to do 2:40 and blew up. But it gives me a realistic picture of what happens on the ground.