by Tisztul_A_Visztula » Tue May 28, 2019 3:10 am
I am also pleased with the level of welcome by MTB's community.
My evolution in ST3 was that for years I had been making my logbook more and more complicated using lots of plugins, but my last year was about simplification to make my logging as fast as it can be. Certainly I wanted to keep some data to which I an still interested in, but eg. I don't give a damn to weather data any more. And not so easily, but I said goodbye to running power data, too, because it gave me too much job (I always questioned the accuracy of the data of Power Runner compared to those of GPS2Powertrack, never knew which was I should have kept)
The crucial point for me is whether there will be a facility within MTB which is similar to Calculated Fields (CF) plugin of ST3.
In CF I defined three types of formulae.
a) I defined some to get the custom data fields of peak power, HR and VAM data over different time spans. I deleted some time spans to make the calculation faster, but I still have 15s, 30s, 1m, 2m, 3m, 4m, 5m, 20m and 60m watt, 1m, 5m and 20m HR and VAM.
b) I defined some pretty simple formulate to get some extra custom data fields, which are also missing from ST3, namely moving time, moving speed and 'how many' (it is whether I made my activties alone, the data is 1, together with someone, it is 2, or with of a group of at least 2 people, then it is 9) and a formula which seems to complicate, but it is not to estimate my fat calories.
Just for fun: (Math.Max(Math.Min((175-{AVGHR})/175*2.827,0.21),0)+Math.Max(Math.Min((162-{AVGHR})/162*2.991,0.24),0)+Math.Max(Math.Min((149-{AVGHR})/149*2.063,0.18),0)+Math.Max(Math.Min((136-{AVGHR})/136*0.209,0.02),0)+Math.Max(Math.Min((123-{AVGHR})/123*0.568,0.3),0))*{CALORIES}
c) and finally I ave formula to save the values of standard data fields like avg spd, avg pace, avg HR, distance, elapsed time etc, because I have a simplified version of my loogbok, from which I delete all the data tracks from time to time, and I realized that the saved average and maximum values of those data tracks go crazy sometimes after deletion.
So it has been my story within ST3.
In MTB I am now testing which I can find where and how. And in a time or so I will start to raise questions about the custom fields which are either in groupb a) or b) hoping that I won't need the custom fields being in group c), because digesting data within my logbook will be fast enough and I can avoid the deletion of the data tracks.
Cheers,
Zoltan