Data Field: Peter's (Race) Pacer

This is the support Thread for the Data Field Peter's (Race) Pacer.

Setup Guide with pictures: http://starttorun.info/peters-race-pacer/

Download
https://apps.garmin.com/en-US/apps/23ea0301-30c6-4c33-b4ef-63e2b5394e76

Summary
Peter's (Race) Pacer resolves 2 issues for me when I'm running a race:
  • Before the race starts I want to see the time of the day (How long till the race starts?)
  • I often pace marathons and it used to be doing mental math all the way, now this is no longer necessary as I can fully depend on the average pace/speed, because this data field allows to correct the distance at the kilometer / mile marker by simply pressing the LAP button
While the data field's primary intent is to race races, you can also use it to run laps around the track, just set the lap distance to 400 meters and press the lap button as you cross the line!...

Intro
In it's full glory this data field uses about 24kb which is too much to run on the older devices. To enable using the data field on older connect IQ devices I've stripped some functionality from these older watches in order to let them operate within the 16kb limit that Connect IQ 1.x allows. (Items marked with (*ciQ2) are only available on the high memory watches (high memory watches are FR735xt, fenix chronos & fenix5 variants))

The data field is fully functional as is, yet donations are encouraged on the watch by a small encouragement text.

Usage
Before starting the race an initial data screen is shown (* cIQ2), this screen shows you the following data
  • Time of the day
  • Current heart rate (+ zone indication)
  • Configured Settings Summary (Change these settings in Garmin Express or in the Garmin Connect Android App)
  • Battery Percentage Remaining
  • Gps Signal Strength Indication
After pressing the START button the race timer will start and a new data screen will be shown, this data screen will show you the following information:
  • top middle configurable field: current heart rate / average pace / average speed / perfect pace / perfect speed (*)
  • row 1 left configurable field: average pace / average speed / current heart rate / perfect pace / perfect speed
  • row 1 middle configurable field: speed, smooth speed (5s average), smooth speed (10s average), pace, smooth pace (5s average), smooth pace (10s average)
  • time ahead / behind
  • race timer
  • (adjusted) distance covered (see adjusting distance explanation below)
  • estimated time of arrival
After Activity in Garmin Connect (*cIQ2)
  • When you opt to record the ahead Time to the FIT track an extra graphic is shown in Garmin Connect
Perfect Pace / Perfect Speed
This field recalculates as you run and gives you the pace you need to run to arrive at the finish with 0 seconds behind / ahead (eg if you run a 10k race and want to arrive in 1 hour (avg pace=6:00min/km), currently you're at the 7k point in 41:30, which means you're 30 seconds ahead, the perfect pace will thus show the value 6:10 (min/km) as you can run the next 3k 10 seconds slower to still get in time at the finish line)

Distance Adjustment
When you press the LAP button the on screen distance is adjusted to the nearest LAP SIZE (eg 5.31k will be adjusted to 5k if the lap size is 1000 meters).
When you press the LAP button by mistake you have 30 seconds to undo the last correction (just press the LAP button again)

When you miss a mile/kilometer marker, don't worry DO NOT PRESS THE LAP button and wait for the next kilometer/mile marker and press the LAP button there.

Adjusting the distance has no influence on the recorded distance (In Garmin Connect when you come back home you will see the real recorded GPS distance, yet of course you will be able to determine based on the lap marker postions where the LAP markings really were)...

Recommendations
  • Train with the data field before you race with it so you're used to the layout!
  • Have a backup second datascreen layout, in case the field crashes you can switch to the native data screen layout
  • If you have a Connect IQ 1.x device consider the application option to enjoy all features of Peter's (Race) Pacer: https://apps.garmin.com/en-US/apps/ea97af1f-1e5d-4541-820c-9bd994080d4
Tested on real FR735XT, all other devices were tested in the simulator.
  • Thanks for the quick fix, HR% is now working and the version number says 3.1.1
  • Eta?

    Hi Peter,
    Tried the app version for the first time today on my F3 HR. Very promising, seems to do everything I want in a race timer! Great work.
    Two questions: how do you calculate the ETA? Is it by using the adjusted remaining distance at the current pace/speed? Or the average pace/speed? Or something else?
    Also, should Autolap be turned off or doesn't matter?
    Donation coming soon.
  • Thanks. Glad you like it. ;)

    The Eta is calculated as the average adjusted speed over the target distance (average adjusted speed=average speed when you did no manual lap presses or the average speed over the covered adjusted distance when you did manual lap presses).

    auto-lap:
    * In the app version there is no auto-lap option, a lap is only being created when you press the LAP button.

    * In the datafield version you can leave auto-lap enabled. If you leave auto-lap enabled then it is important that the auto lap size is the same size as the lap size configuration in Peter's (Race) Pacer. (eg if your auto lap size is 1k then set the lap size in Peter's (Race) Pacer to 1000 meter). (What will happen internally in the datafield is that when the auto-lap is being triggered a correction will be applied, but since the auto lap distance is the same as the configured lap size distance a zero-correction will be applied.)
  • Laps?

    Tried the app on my long run today. I had the distance set for marathon, lap size 1000, target pace 5:40. During the run everything looked good. I did not press any manual laps. I ran 27.4K
    After the run when I look at the stats in Garmin Connect, there are only four laps, the first three are 8.05K, the last one 3.24K. Any ideas on why this happened? I had expected 27 1K laps.
  • In the app version there is no auto-lap option, a lap is only being created when you press the LAP button, so I assume you must have pressed the lap button 3 times if you have 4 laps.

    At the moment the lap size is only used for distance corrections and to find the closest multiplicate of the lap size to the current distance.

    I have considered creating laps or foresee some sort of autolap creation option in the app-version (and it wouldn't be all that difficult to do so really), but what holds me back to implement this is that I can not delete lap-markers when a manual press occurs. (eg if a manual lap press at 3.2k occurs I preferably would like to remove the marker at the 3k point, as the 3.2k marker is in reality the 3k marker... but I can't do so...)
  • Laps

    Thanks for the quick reply. Quite sure I did not press Lap even once. In fact, I went back and had a look at last Sunday's long run in GC. Same thing: laps auto created every 8.05K! No biggie, just wondered if this is intended behaviour, which I gather it isn't. I'll do some more testing to see if I can figure out what's going on.
  • no it's not intended behaviour,... at the moment the app doesn't have that much functionality really, it enables all high memory logic, starts a running recording and for the rest it's basically just a shell around the datafield version really...

    I'll have a look if I can reproduce this strange behaviour in the simulator, on my real device I'm blocked by the strava live segments detection bug (filed a report for that one here: https://forums.garmin.com/showthread.php?370682-Watch-App-detects-Strava-Live-Segments-(shows-dismiss-message-and-exits-app) )

    Edit:
    (non related to the above)
    Released version 3.1.2 of the datafield version today:
    * small bugfix: converting a 0:00 pace to speed resulted in an error
  • 8.05 k

    Really strange! I had the app running while driving home from work today. Regardless of driving speed, every 8.05 kilometer a lap is created! Again, it doesn't seem to affect the app while it is running, so don't worry about it. But let me know if you want some sample files for analysis.
  • also tried my app on the highway and was able to reproduce it, on my fr735xt it autolaps every 1.61k (=1mile), for your device it autolaps every 8.05k (=5mile), I have a filed a bug report here: https://forums.garmin.com/showthread.php?371787-Watch-App-that-creates-a-running-session-autolaps-at-(insert-magic-number-here).
  • @Mickelin01 it's likely a bug that the device team needs to solve, can you post your device in this thread https://forums.garmin.com/showthread.php?371787-Watch-App-that-creates-a-running-session-autolaps-at-(insert-magic-number-here)&p=957655#post957655 so that they can also create a ticket for your device. Thanks. :)