Datafield: Average Pace Over Period

Average Pace Over Period

Average Pace Over Period v0.7

This data field continuously calculates the average pace over a given period of time. Pace is shown in min/km or min/miles, depending on user settings. This version is limited to the average over a two minute period. When user-specified properties are made available, I will release an updated version where the user can specify the period.

To smoothen the pace the data field is only using data from when timer is running. This is to prevent stopping at red lights and so on from interfering with the average pace. I'm considering adding a filter to remove sudden, large jumps in pace to further improve the smoothing.

Due to several requests in the Fenix 3 forum, two other versions are available for sideloading (for Fenix 3 and 920XT only):
Update April 28, 2015: The 30s version now resets the calculation if you stand still for more than 15 seconds.

1 min Average Pace - Fenix 3
30 sec Average Pace - Fenix 3

1 min Average Pace - 920XT
30 sec Average Pace - 920XT

(Download .PRG file, connect watch with USB, place .PRG file in GARMIN/APPS/ folder)

Updates:

Version 0.7 - March 26, 2015:

Tweaked the pace averaging filter.

Version 0.6 - March 23, 2015:

Removed leading zero from minute field.
Fixed leading zero bug in seconds field.
Added experimental filter to only use data from when timer is running.

Version 0.5 - March 16, 2015:

Initial version.

SergeyVDNKH over 9 years ago

everytime I 'sideload' (move a .prg into /APPS ) on the f3, it removes all ConnectIQ apps from my watch after rebooting. Anyone else seeing this? I'd like to try the 30s pace!

In my experience, before loading prg-file, Average Pace Over Period official app should be removed from the watch by GE, after that disconnect the watch, there should be no ConnectIQ field on the watch. Than copy prg-file and disconnect the watch. I had no problems after this little dance. In my opinion, partly the problem is that all versions have the same name, so if you copy all at once, kind of a name-collision happens.

And also, you may have ConnectIQ system messed up on the watch, I had it on my 920xt after trying all the apps at first. Resetted the watch.

torsteinvh over 9 years ago

To avoid naming conflicts, I have compiled new 30 sec and 1 minute version with unique names. I have also provided versions for the 920XT. All files are linked in the first post in this thread.

-Torstein

SergeyVDNKH over 9 years ago

Just run 10K with 30s_pace on 920xt. Generally works great, for me it is the best compromise of stability-responsiveness.
Noticed some wrong behavior:
1) I walked to start line with GPS on, stayed on start for few minutes, but field showed 12km/min all the time.
2) For a minute or so, as I started running, it showed much slower pace, than a native Average pace field.

torsteinvh over 9 years ago

Thanks for the feedback on the 30s version :)

1) 0 speed is not included in the calculations, so when you stand still the watch keep showing the last calculated value. This works fine when you have a short stop, but maybe not so well in situations like the one you describe. Maybe a better idea is to show a 0 or reset the calcualtion after a set period stationary.

2) Related to 1), I guess. The speed values from the slow walk to the starting line will keep affecting the calculation for a while. Again, resetting the calculation to 0 after a period of standstill will solve this.

I'll post an updated version over the weekend :)

Garmik over 9 years ago

This morning I tried installing both Fenix 3 versions to my watch (together or separately) without any success. Every time, the watch deleted all Connect IQ apps in the GARMIN/APPS directory. I'm able to install my own custom watch face using this method without any problem.

Any ideas? I was really looking forward to trying this out.

torsteinvh over 9 years ago

Are you using a Mac by any chance? This thread describes the same problem: https://forums.garmin.com/showthread.php?227127-Watchface-crashes-on-Fenix3-and-wipes-out-all-ConnectIQ-apps

I have loaded both versions on my own Fenix 3 without any problems.

-Torstein

Garmik over 9 years ago

Are you using a Mac by any chance? This thread describes the same problem: https://forums.garmin.com/showthread.php?227127-Watchface-crashes-on-Fenix3-and-wipes-out-all-ConnectIQ-apps

I have loaded both versions on my own Fenix 3 without any problems.

-Torstein

Ah, perfect - that was exactly it. Thanks! The reason my own clock face worked but your fields didn't was because Safari adds extended attributes to all downloads for quarantine purposes; my own clock face file never had those attributes since it was generated locally.

I'll try out the fields on my ride today, though I expect they'll be more useful when running.

Edit: just noticed that the Bike profile doesn't even allow you to add the built-in pace fields, so I can't do a direct comparison unless I choose Run instead. What a silly limitation! It'll probably be several days before my next run to try this out properly (minor knee issue... needs REST). Oh well, thanks for making these!

torsteinvh over 9 years ago

Under 'Settings/System/Format/Pace-Speed Preference' you can choose Pace for cycling, I would think that would allow pace fields (haven't tried myself).

-Torstein

SergeyVDNKH over 9 years ago

Thanks for the feedback on the 30s version :)

1) 0 speed is not included in the calculations, so when you stand still the watch keep showing the last calculated value. This works fine when you have a short stop, but maybe not so well in situations like the one you describe. Maybe a better idea is to show a 0 or reset the calcualtion after a set period stationary.

2) Related to 1), I guess. The speed values from the slow walk to the starting line will keep affecting the calculation for a while. Again, resetting the calculation to 0 after a period of standstill will solve this.

I'll post an updated version over the weekend :)

Long time no update. @TORSTEINVH, how are you doing?

torsteinvh over 9 years ago

Oops, sorry...
I had sort of hoped that Garmin would come up with user configurable setting by now, so I wouldn't have to update all three versions, so I have pushed an update in front of me... Will have a look at it during the next couple of days!

-Torstein