VO2 Max Estimator (Running)

VO2 Max estimator using the formula developed by James D. George in "VO2max estimation from a submaximal 1-mile track jog for fit college-age individuals." The equation was developed by having subjects run easy miles, which for the research was restricted to a minimum mile time of 8 minutes for males, and 9 minutes for females. The VO2 max estimate is calculated from a sustainable pace, and the associated heart rate. The calculated VO2 will be valid once your heart rate has stabilized at the pace you are running. This calculation will not be accurate during workouts such as tempo runs or intervals where effort is high or pace frequently changes. This data field is valid for RUNNING ONLY. **ACCURACY NOTE** First, this is a submaximal effort estimation, meaning that it is designed for an easy run. Second, the equation provided from the paper uses the heart rate of the subject at the completion of a mile. I have found, however, that the equation provides a relatively steady value across most paces, but not so much during sharp speed changes. Lastly, for those claiming that this estimation is way off, are you comparing this estimate to a true measured test? Or to another estimate? That's what I thought... Also, I recently received the following in an email "i don't see a way of updating my review, but i wanted you to know. today i went and had my vo2 tested in a lab. body mass, lactic threshold, and a few others... my VO2 max was 56 = top99 percent for my age group. i was stunned, i thought for sure i'd be closer to my other garmin's vo2 51 reading (or less) - what i'm trying to say is your v02 max is/was dead on." - Thanks for the feedback! The data field may take 30-60 seconds for the value to stabalize, and may display 0's for the first ~20 seconds. This is expected and a side effect of the stability fixes. NOTE: This data field uses both gender and weight from the User Profile, the user profile must be accurate to receive valid results. The calculation also uses current speed and heart rate, so a heart rate monitor is required. V 1.5.3 Truly just reverting to version 1.5.1 (removing VO2 Max Average recording) but you have to increase the version number with every update. Something was not working correct with recording the average VO2 max, and I received some comments that since the VO2 max average had been added some tools could no longer read the .fit files correctly. V 1.5.2 Added a VO2 Max Average calculated from all values in activity. (Can't seem to find where this is reported though...) V 1.5.1 Stability fix, I think I found what was causing the datafield to crash. Also added .fit field recording. May have to uninstall and reinstall data field for recording to work (I had to). V 1.4 Added new watches, rebuilt with SDK 1.2.5. V 1.3.4: Rebuilt app using version 1.1.4 of the connect IQ SDK V 1.3.3: Redesigned code in hopes it will fix the data field not always displaying and people getting just an IQ logo sometimes. V 1.3.2: Rebuilt data field with 1.1.3 SDK release. V 1.3.1: Rebuilt app with latest SDK as there were issues with the data field against the latest Garmin release. V 1.3: The gender values were used backward in the VO2 equation, giving a VO2 max estimate that was 8.444 too high for females, and 8.444 too low for males. This has been corrected in the new version. V 1.2: Updated so that the speed used in the calculation is now a 30 to 60 second average. This should keep the VO2 max estimate a more stable value, and hopefully provide more accuracy as to your actual VO2 max. V 1.1: Updated app so that if heart rate data is not present the VO2 Max estimate returns 0 V 1.0: Original Release

FIT file recording! And a bug fix that will hopefully clean up all the crashes.