Data Field: Race Pacer

Thanks for the DF, just installed it and tried it at home. Nice idea to offer a "split" feature if you're going to be using a specfic strategy or want to account manually for hills. The next step would be to offer more than two splits but of course that's going to become complex to set up ;-)

I don't intend to use the altitude as I don't think it would be very reliable on my sensorless FR235, should I zero out the gradient penalty/bonus values so there is no impact or would putting a 0 altitude difference be enough?

I'm interested in what you mean by more than 2 splits? Currently it's a "linear line" fit split pace, so if you select -15sec/mile for an 8min/mile average pace, so -15sec at finish compared to middle, the pacer pace over say a 6 mile race would look something like:
0 : 8:15
1 : 8:10
2 : 8:05
3 : 8:00
4 : 7:55
5 : 7:50
6 : 7:45

Yes, you are correct setting the up/down hill GAP settings to 0 will disable the GAP adjustment.
I have a fr235, and must admit sides of large buildings and tree cover can make things "jump" around a bit, but it does average out once you get in the clear. I find GAP most useful for those really hilly races, say 400ft+ climbs, really makes a difference with pacing then. Must admit wish I had a fr920xt for it barometric altitude!

Thanks for the feedback.

Hi

I have upgrade to firmware 3.50 on my vivoctive and now there is a way too choose between 1/2/3 data fields layout in run application.
I have choose 2 data fields but seems that with this selections i can see in both fields the estimated time (central field layout in your screenshot example) but not the virtual pace (top fiedl on your screenshot).
Could you eventually test this situation or give me the right instructions to have the right visualisation?

Thanks a lot

Hi

I have upgrade to firmware 3.50 on my vivoctive and now there is a way too choose between 1/2/3 data fields layout in run application.
I have choose 2 data fields but seems that with this selections i can see in both fields the estimated time (central field layout in your screenshot example) but not the virtual pace (top fiedl on your screenshot).
Could you eventually test this situation or give me the right instructions to have the right visualisation?

Thanks a lot

Hi just seen your post, i will take a look and correct the issue,
Thanks for highlighting it

Detailed Race Pacer description

A "gradient adjusted" and "race split" race pacing Data Field.
The Race Pacer creates a "pacer" that allows you to (via IQ App User Configuration Settings):

- Specify a race distance, target time and elevation change from Start to Finish of your race course

- Optionally specify start elevation, or use current GPS value (Specify "-"). Useful if using GPS elevation and starting under trees or next to large building!

- Paces using "gradient adjusted pace" (allows for hills!), so the pacer will go up hills slower!

- Specify a "race split" you would like the pacer to run, eg.finish 15sec/mile quicker than in the middle of the race. (Specify split = -15, so pacer starts at say 8:15, in middle is 8:00, at finish 7:45)

- Gives you a finish time estimate that is based on your performance over the last 5km. Using a linear regression fit of your gradient adjusted performance over the last 5km, it extrapolates using a Riegel type formula to estimate your finish time. For example, if you start out quick and then fade, the estimate may show you missing your target...! This estimate is displayed from after the initial 600m of running.

- In multi-field screens the "race pacer" displays different values depending where on that screen it is placed. This enables you for example on a 3 row screen to add "Race Pacer" twice and have your chosen favourite 3rd field (eg.heart rate...). It displays these values in these positions:

- Fullscreen field : All values
- Top or Bottom full width field on a 3 row screen: "Pacer" + "Req. Pace"
- Middle row of a 3 row screen or bottom of a 2 row screen: "Dist Rem." + "Grade" + "Est."
- Small Quarter or half width field : just "Pacer"

(See 5th screen shot for an example on a fr235, where I use a 3 row layout, use "Race Pacer" data field twice in rows 1 & 2, and "Heart Rate" in 3rd row)

Support & discussion at: https://forums.garmin.com/showthread.php?341894-Data-Field-Race-Pacer

Usage:

1) Using GCM or GE set the Race Pacer App Settings for your desired race distance, elevation change, start elevation ("-" for current value), target time, "race split" and optionally GAP adjustments.
Example: I want to run 10k(6.21miles) in 48min:30secs with a -ve split of -15sec/mile at finish compared to middle average. My start altitude is known to be 50 feet, and finish is 100 feet higher than start.
In GCM/GE enter:
Distance = 6.21
Target time = 48.5
Start elevation = 50 (use "-" if you don't know and use GPS current elevation, but can be less accurate)
Start->Finish elevation change = 100
Race split = -15
(the rest defaults)
For device set to statute units are miles/feet, for metric device units are km/metres.

2) Start Activity... field displays:

A: "current altitude" D: "Start-Finish elevation difference"
or S: "specified start altitude" D: "Start-Finish elevation difference"
"race distance" in "target minutes"
P: "pacer start pace"-"pacer finish pace"

when "GPS Ready", check your elevation is about right (if not specified) for better GAP before you hit "Start"...

Values Displayed:

- Pacer : Your time +/- relative to the "pacer". Green=Ahead, Red=Behind.
- Req. : Your required "pace" from your current position to the finish to achieve your target.
- DstR. : Remaining distance.
- Grade : Elevation difference of the Finish relative to your current position.
- Est. : Estimate for your finish time (displayed from 600m point onwards). Green=Ahead, Red=Behind target time.
- Act. : Actual finish time on completion of race distance.
- 60s pace : Your smoothed average pace over the last 60 seconds.

Notes: The "gradient adjusted pacing" obviously uses altitude, GPS elevation data is quite noisy, I smooth the data, and the end result is quite good. However, if you have barometric altitude support on your device, I advise you to use that.

Notes: The Race Pacer data field displays different data for different field positions in multi-field screens, see screen images below for examples...

Hi

I have upgrade to firmware 3.50 on my vivoctive and now there is a way too choose between 1/2/3 data fields layout in run application.
I have choose 2 data fields but seems that with this selections i can see in both fields the estimated time (central field layout in your screenshot example) but not the virtual pace (top fiedl on your screenshot).
Could you eventually test this situation or give me the right instructions to have the right visualisation?

Thanks a lot

I've fixed this the best I can, so that it shows the relative to pacer and required pace in the 2 data fields. Unfortunately the dimensions and metadata of the top and bottom fields of the 2 field display are identical, hence I can't choose differently for bot compared to top... but at least it will show the most useful view now.
Thanks

I've fixed this the best I can, so that it shows the relative to pacer and required pace in the 2 data fields. Unfortunately the dimensions and metadata of the top and bottom fields of the 2 field display are identical, hence I can't choose differently for bot compared to top... but at least it will show the most useful view now.
Thanks

It works fine thank you, for me it's very good because in two row i can see better
Thank you very much

Download race pacer on vivoactive hr

Karl nashy, got a email message via Garmin from you, however garmin don't give me a way to respond! Doh!
Please try checking Garmin Expresss apps list on PC or Garmin connect mobile device-connect iq apps-data fields to see if Race Pacer present. If it isnt then it didnt download properly, retry... if it is then try resync with vivoactive hr then check activity settings - datascreens- field-iq apps and see if race pacer available?
Cheers
Al636

Can't set Race Pacer twice?

Hi! Today I found that my fr235 can't set Race Pacer twice(which I could b4) when I chose to use 3-row screen, just like what you did with ur fr235 in the sample pic. The firmware of my watch is 4.20, language Traditional Chinese. Pls help. Thank you very much ^^

Hi! Today I found that my fr235 can't set Race Pacer twice(which I could b4) when I chose to use 3-row screen, just like what you did with ur fr235 in the sample pic. The firmware of my watch is 4.20, language Traditional Chinese. Pls help. Thank you very much ^^

Hi there, i will have a look, and fix... Thanks

Hi! Today I found that my fr235 can't set Race Pacer twice(which I could b4) when I chose to use 3-row screen, just like what you did with ur fr235 in the sample pic. The firmware of my watch is 4.20, language Traditional Chinese. Pls help. Thank you very much ^^

Hi Anna, it seems to work fine on my UK fr235, with firmware v4.60. can you describe what happens please? Error or bad screen format or..?
It seems the Chinese watches are somewhat behind on firmware, wondering if that is causing the problem? Is 4.20 the latest available?