Data field: Flexirunner

Oh I see, since it was the same label as in the middle center field I assumed it showed the same data. I have now reverted back.

The label should read "Run. Pace" (except on 920xt, where it just says "Run"), whereas the middle field just says "Pace".
You must have run at a very even, steady pace not to have notified any difference!

Actually I just changed it this morning so hadn't run with it yet. By "label" I meant the description in GCM actually but yes on the actual field it says Pace in the middle and Run.pace bottom right.

Very cool data field! Great work! Would you be willing to add a calories burned option to the list of configurable fields? Would be great to see this info and I could also use during brisk walking when I don't wear a hrm.

Thank you

Back from my 10k recovery run so I had ample time to look at the "lap speed" field at the beginning of each 1km autolap. Compared to yesterday I'd changed it from "current lap pace" to "current lap moving (running) pace" and I don't really see a change, which makes sense since it's a continuous run. It takes between 1 and 2 minutes to reach an accurate value (it starts out way too fast), which does seem like a lot. Could there be some rounding going on or some type of "disconnect" between the distance covered and the time since the beginning of the lap ?

Flexirunner IQ Exclamation

I can reproduce the Crash of Flexirunner which JohnChristof reportet yesterday, on a VAHR: Start the app with the datafield and start the run before the OHR-Sensor gets data.
If i wait until HR is ready, its ok, but when i start the run too early, it crashes.
It was easy to reproduce this many times during a walk with my dog :-)

Paul

Very cool data field! Great work! Would you be willing to add a calories burned option to the list of configurable fields? Would be great to see this info and I could also use during brisk walking when I don't wear a hrm.

I can try and see if it will fit, the problem is that adding more choices to the list increases the amount of memory required, and the data field is pretty much at the limit for most devices (the newer CIQ 2.x devices - Fenix Chronos, FR735xt, vivoactive HR - have more memory available). What device are you using?

Back from my 10k recovery run so I had ample time to look at the "lap speed" field at the beginning of each 1km autolap. Compared to yesterday I'd changed it from "current lap pace" to "current lap moving (running) pace" and I don't really see a change, which makes sense since it's a continuous run. It takes between 1 and 2 minutes to reach an accurate value (it starts out way too fast), which does seem like a lot. Could there be some rounding going on or some type of "disconnect" between the distance covered and the time since the beginning of the lap ?

2 minutes does seem like a long time to stabilize, but I would expect at least 20-30 seconds, so 1 minute is not beyond the realms of feasibility.

There is some rounding in that it rounds the time from milliseconds to the nearest second, and the distance from decimetres to the nearest metre. This matters early on in the lap, when the values are small and so the signal-to-noise ratio is high, e.g. if you travel 4.7 metres in 1.4 seconds (approx. 8:00 min/mi), and this is rounded to 5 metres in 1 second, then the pace is wildly different (5:20 min/mi). However, another moment later, continuing at the same, say you've now covered 9.4 m in 2.8 s, that's 8:56 min/mi. Then 14.1 m in 4.2 s is rounded to 7:40 min/mi, you can see it is converging to the true average.

There is also a technical difference to the built-in lap quantities in that in Connect IQ you have to calculate lap quantities yourself, all you know is the point at which a lap occurred. However, you are only told this after the lap is written into the FIT file. This difference from when the lap precisely occurred should really be negligible, it can't take more than a few hundred milliseconds to write, but it is nonetheless a difference compared to what the built-in watch knows about lap points.

On top of this, if you use moving (running) pace metrics, then these subtract time and distance where you are stopped or moving slowly. The calculation is done approximately once per second (rounded to a second), and there is no smoothing, so if the watch says you were moving too slowly for the just last second (which can happen, especially with GPS), Flexirunner will subtract this from the moving values. This is obviously only a rough approximation, and again, early on this is likely to result in high signal-to-noise issues. The real value of the moving (running) averages is in longer times.

I can reproduce the Crash of Flexirunner which JohnChristof reportet yesterday, on a VAHR: Start the app with the datafield and start the run before the OHR-Sensor gets data.
If i wait until HR is ready, its ok, but when i start the run too early, it crashes.
It was easy to reproduce this many times during a walk with my dog :-)

Excellent, thanks for the debugging, that is very helpful!

I will take a look at the code with this in mind. Obviously, the data field needs to be usable without any HRM too!
I think JohnChristof is using a 920XT, so maybe he doesn't have a HRM, or the ANT+ connection is not ready. This is going to be particularly annoying given that the latest update to the FR235 removed the 'Wrist Heart Rate Ready' message that popped up when HR data was available.

I can try and see if it will fit, the problem is that adding more choices to the list increases the amount of memory required, and the data field is pretty much at the limit for most devices (the newer CIQ 2.x devices - Fenix Chronos, FR735xt, vivoactive HR - have more memory available). What device are you using?

OK thanks for seeing if it will fit. Fenix3 non HR version here.

Really like the layout.

BTW which pace field will read my footpod and give me an instant pace or something close to the last 5 to 10 seconds?

Would you have any interest in porting this over and making a walking data field with similar layout? I have some suggestions on fields that would be useful for that activity.

Again great work!

BTW which pace field will read my footpod and give me an instant pace or something close to the last 5 to 10 seconds?

There is no way to choose the pace source in Connect IQ, but if you choose your foot pod as the source in your watch settings (e.g. 'Always use as pace source' or something similar to that), then that is where the pace will come from in Flexirunner (and the built-in 'Pace' field), or also if there is no GPS signal.
The centre field in Flexirunner shows instant pace.

Would you have any interest in porting this over and making a walking data field with similar layout? I have some suggestions on fields that would be useful for that activity.

I'm unlikely to do it myself, but the source code is freely available if anyone wants to adapt it.