Data fields: Configurable Speed / Pace

Looks like this could be a useful app, thanks, it's been a while FR205/305 (?) since we've been able to choose some "averaging" on the instant pace ;-)

I find it confusing that you are mixing the terms "apps" and "data fields". Actually, I was not clear what it is as long as I tried it myself.

The above is a configurable data field, which differentiates itself from an app in that way as it is only active during an activity program. An app is permanently active in foreground as being separately started - not as activity, but as standalone program, running exclusively on the watch.

best
VS

Thanks. I changed the text. I hope it's more clear now.

Hello TeunMo,

I'm using your data field as "all I need on my FR235". Bravo!

One question: is the Pace calculated continously (always on the latest period of defined seconds), or does it restart calculating from 0 the Pace each time the defined seconds are finished?
This is a must-to-know, becaus if it's continous then the calculated pace is going to be very very precise all along the run (differently from what Garmin Lap Pace does).

The problem on Lap Pace calculated by Garmin default data field is exactly generated by the fact that after each lap (for example 1 Km) the pace is re-calculated as you were re-starting again the lap, losing the reached precision of the average pace calculated along the lap.

Here is my request, if you can: the possibility to set a distance trigger instead then a time trigger.
Can you?

Thanks in advance and happy new year!!
- enrico

One question: is the Pace calculated continously (always on the latest period of defined seconds), or does it restart calculating from 0 the Pace each time the defined seconds are finished?

The pace is recalculated every second.
If N is the value you set in the configuration:
When you start the data field and less then N seconds have past, it will take the average since the start of the data field. After the initial N seconds, it will always show the average over the last N seconds.

Here is my request, if you can: the possibility to set a distance trigger instead then a time trigger.
Can you?

Yes, this is possible, but I don't really see the added value and I do see some technical complications. Can you maybe explain what would be the added value for you?

The pace is recalculated every second.
If N is the value you set in the configuration:
When you start the data field and less then N seconds have past, it will take the average since the start of the data field. After the initial N seconds, it will always show the average over the last N seconds.
Yes, this is possible, but I don't really see the added value and I do see some technical complications. Can you maybe explain what would be the added value for you?

Thanks a lot for your quick answer.

I just went out for a 9 Km post-ethilic run and used your data field: nothing to say; it's perfect!
It changes the value of my FR235. Thanks again.

The time-based average is what I need for my training; maybe (...not sure) people performing training on short distances could appreciate a different average calculation.

Anyway I consider your app the most interesting of IQ Showcase.
Again: bravo!

Thanks for providing this as it is a good idea...

...but it is unusable for me at the moment. The pace will look comparable to the Garmin smoothed pace and then inexplicably jump +/- 4:00 mi/mile, i.e. I'm running 9:00 mi/mile pace and it jumps to 5:00 or 13:00 mi/mile pace for a few seconds. This was on 2 different treadmills using a footpod and outside with GPS and a footpod. I have not yet tried it without the foopod on (although it shouldn't be seeing the footpod if GPS is active). I have tried 5 sec and 3 sec averages, at 5 sec it is slower to update to a velocity change than the Garmin instant pace.

This is on a 630 w/ HRM4run.

This data field uses the speed it's provided by the device. If this value jumps the way you describe, then that's a discrepancy of the device. If you use the build in speed it will show the same jumps. I think a possible reason for this might be that the device can't calibrate the footpod yet, beause you haven't used it without one yet.

This data field uses the speed it's provided by the device. If this value jumps the way you describe, then that's a discrepancy of the device. If you use the build in speed it will show the same jumps. I think a possible reason for this might be that the device can't calibrate the footpod yet, beause you haven't used it without one yet.

I had it side by side with the Garmin instant pace, which is why I was able to tell how responsive it was comparatively. The Garmin pace reading was stable and the only real issue I have with it is the rounding to 5 sec. Running outside the watch is using GPS for speed, not the footpod. You just stated that your data field is using the same data as the watch so it should read the same (other than the rounding issue). The Garmin pace never bounced more than 5 or 10 sec.

There is something wrong here and I'm just trying to help you sort it out. FYI the footpod is calibrated manually in this case.

Update:

I removed this data field (Configurable Speed / Pace) and installed a different 'xx run data field' which has configurable pace averaging and it worked as expected. No big spikes or dropouts.

I reinstalled your data field and left the default values as installed to remove the possibility of corruption of the settings file. It performed the same as before with huge spikes/dropouts in pace randomly for a few seconds at a time.

I would rather use your (Configurable Speed / Pace) data field as I can choose my layout, the other one has multiple fields in it and no layout choice. This is on a 630 and I have it on a 4 data field screen. I suppose I may try it on it own screen to see if that has any effect on it.