• Replies 893 replies
  • Subscribers 46 subscribers
  • Views 127436 views
  • Users 0 members are here
Options
Related

Data Field: AppBuilder

flowstate
over 8 years ago
By user request, this app lets you define your own data field, based on a simple math formula like cadence / 2.

If you want to get fancy, there's conditional expressions (like IF in Excel), functions for data analysis (like MIN and AVG), and the data field can also display the text of your choice. The resulting data can be (optionally) written to the activity FIT file.

With AppBuilder, you can implement almost any field that involves math, such as: calculating normalized power and saving the data to the FIT activity file, showing the average pace for even-numbered laps, or recording the amount of time you sprinted.

Full documentation and examples here:
http://ciq-appbuilder.blogspot.com/

AppBuilder 5:
Now with new features! AppBuilder 5 is a completely new app, so please check it out in the store if you are interested in any of the new features.
https://apps.garmin.com/en-US/apps/fd690281-9c22-4fee-a81e-3b7f39aa67c5

- Store up to four formulas per app. Switch between formulas directly on the watch, without using a phone or PC. With four clone apps, you can store up to 16 formulas total
- User variables. Allows for powerful formulas where information can be stored at one point, like the start of a lap, and used later. e.g. Lap elevation change
- Improved timeavg() options. Allows for simpler, more flexible normalized power function
- More functions and variables

4 clones of AppBuilder are available in the store, so you can have 2 formulas in the same activity
  • Former Member
    Former Member over 6 years ago
    Recording Average Power, Display and record Lap Power and display and record power (graph).

    RECORDSUMMARY(AVG(GETV(2)),20) ; RECORDLAP(LAPAVG(GETV(2)),19) +'..'+ RECORD(GETV(2),7)

    Shows lap power..power for example in 3 field screen placed in center field this gives a nice big easy to read power readout.

    Combined formula

    SETV(1, IF(Speed_raw GTE 1, TIMEAVG((Altitude_raw - PREVN(Altitude_raw, 14)) / (Distance_raw - PREVN(Distance_raw, 14)) *100, 3), 0) ) ; SETV(2, (0.0017 * GETV(1)^2 + 0.029 * GETV(1) + 1) * Speed_raw * 81 * 1.022) ; RECORDSUMMARY(AVG(GETV(2)),20) ; RECORDLAP(LAPAVG(GETV(2)),19) +'..'+ RECORD(GETV(2),7)
  • over 6 years ago
    JTH9 thanks! I'm prolly gonna steal these....
  • Former Member
    Former Member over 6 years ago
    A few graphs of the formula in use.community.garmin.com/.../1437085.jpg
  • Former Member
    Former Member over 6 years ago
    FlowState no problem, the reason I posted it here. It may require a bit fine tuning still, so will post it here for others to experiment on.
  • over 6 years ago
    JTH9 btw, FYI your weight is available as a variable in appbuilder: userweight
  • Former Member
    Former Member over 6 years ago
    Oh, totally forgot about that, was actually in my mind to add at one point. So one can change 81 from the formula with UserWeight and don't have to configure anything except the correction factor.

    One might even leave the correction (1,022) totally out. As it's not real power anyway, and then again what is? TBH I don't notice that much difference running with this simple formula vs Stryd. If anything it's actually a bit closer to RPE thanks to the Strava adjustment curve, even when it has a few glitches where its seemingly off, but then again I get that with Stryd too.

    If you just want a number to base your training on, even plain GAP would do as I notice from NGP in Training Peaks the NGP IF is always very close to NP IF. I just converted the numbers since TrainingPeaks doesn't regognize other GAP than their own and I didn't want to change my FTP just for this test.
  • Former Member
    Former Member over 6 years ago
    The recorded power from Stryd is much more refined though, probably their altimeter is also more accurate. But on the go both are off from RPE at times, mostly because of the lag there is to grade calculation. Also when using GPS there is also the speed lag. Still it was surprising that using just GPS as speed source the numbers weren't more off. I had a seemingly good GPS day as the distance was spot on with my calibrated Stryd, and admittedly the GPS is more accurate / stable on F5+ than it was on F5.
  • Former Member
    Former Member over 6 years ago
    Well seems the Stryd altimeter is much more refined. Here's the same formula running on Stryd elevation from offline data. This is the same run data as in the first picture, a lot less spikey actually:

    community.garmin.com/.../1437171.jpg
  • Former Member
    Former Member over 6 years ago
    Here's what simply GAP vs Normal Pace would look like (this one's the most describing actually), I used Stryd data for elevation again to get a cleaner comparison. Too bad the altimeter is so bad on a top of the line watch like the F5+. Just shows how Garmin puts poor quality components in these watches to make big profit.
    community.garmin.com/.../1437417.jpg
  • Former Member
    Former Member over 6 years ago
    My favorite part is the 1 min test downhill, the sudden drop in graph is caused because of a 90deg turn after a snowy hill so I had to slow down to not fall, but otherwise I went as fast as I could, with correction the speed stays nice and level. :)

    Also notice in the previous graph how much Stryd drops in this same downhill section even though I was starting with fresh legs after rest so here I actually think Strava GAP is closer to truth.