Race Surgeon
-
Being a road-runner with some sort of ambition to optimize races I have been missing a race pacer that allows for defining pace segments. The races I have participated in (Gothenburg area, Sweden) are quite often pretty hilly and I have found that I waste energy in the wrong places and therefore needed an app that could provide some guidance; sort of a smart pace band with some extra bells and whistles. The requirements were pretty close to “RaceWarden Pacer” - but I was missing the possibility to define the distance for the various segments of the race. And. With age comes poor eyesight, so I needed BIG (and clear) numbers to control the pace.
The logic/thinking:
You define your pacing strategy based on the elevation profile of the race and potentially other factors - this is all done outside of the app. Example from “Göteborgsvarvet” where I decided to try Jack Daniels’ Running Formula which roughly translates to -8s/km/%-gradient (uphill) and +5s/km/%-gradient (downhill). But that is outside the app, just the background to the pacing strategy.
The pacing strategy is pushed to the app through user defined app settings:
Segment Distances (km or mile): 2.45 1.79 1.36 1.36 6.59 7.8
Segment paces (min/km or min/mile): 5:18 5:03 5:37 4:55 5:12 5:14The number of segments need to match the number of paces, no fallback implemented (yet)
With the user input the total race length is calculated by summation of the Segment Distances (21,35km) - overall race target time (1:51:26), as well as target pace (overall) is calculated based on defined segments/paces.
After some testing I came to the conclusion that the following information would be useful during a race - again trying to eliminate non-essentials and focus on visibility:
- Segment Target Pace: Derived from user input and displayed once a segment is recognized/completed. In essence this is a pretty static value, that only changes when a segment is completed. Consider this the equivalent to a pace band that updates as segments are completed.
- Segment Pace: Calculated. Similar to Lap Pace but utilizes the user defined Segment Distances/Segment paces, so it’s dynamic and updates as you run.
- Total Seconds ahead/behind Race Plan: Defined as the deviation between overall race plan and completed distance/time; naturally dynamic.
- Needed Pace: Based on initial user input finishing time and total race length are calculated. This is the pace needed for the remaining part of the race to reach the target
So - in essence - you have the segment based race strategy on the right side of the display, everything else focuses on the overall race strategy. I removed all descriptive texts by purpose on the display, as I would either way not be able to see/read them.
All inputs and ideas for further improvements are most welcome!
The app is available in the Suunto+ Store since some days ago - but unfortunately there seem to be a problem beyond my control with entering paces/segments (confirmed on Android - not sure about iOS-devices). This might affect also other apps with similar needs. Workarounds (until problem is sorted) would be to use c/p from clipboard and/or set the phone keyboard to floating, allowing room for entering the paces/segments. Please note: this has nothing to do with the Race Surgeon-app itself
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login