The new EvoLab analysis will build the estimations and predictions on a time-pace model using your best performance in different time duration.
- Only the previous 90 days will be taken into consideration
- To unlock EvoLab data, a user must first record an outdoor run of 25 minutes or longer at 60% of Max Heart Rate or higher
- Any further Run activity recorded longer than 30 seconds will impact your predicated benchmark data, there is no upper limit. The core principle in this new model considers your "Best performance in the last 90 days" to be the best indicator of current fitness
- The data is not based on absolute pace values, but rather is converted into the Effort Pace equivalent, which considers slope and historical heart rate data to make predictions.
- If you do not record a run for 90 days or more, the model will be rebuilt once a new activity is recorded.
X-axis is measured in seconds, Y-axis in m/s
-
Time-pace model construction method adopts three-parameter model
The three key parameters are:
-
Pmax (1s maximum speed)
-
W' (anaerobic work, about 1 min can run the longest distance)
-
CP (lactate threshold)
Through daily running data, the above three parameters will be recorded to build a predictive model.
-
Accuracy of the model compared to lab testing (80% of users can achieve the following accuracy)
Improvements from EvoLab 1.0 to EvoLab 2.0Lactate threshold pace 17.2%5K performance prediction9.2%10K performance prediction10.9%Half marathon result prediction44.3%Overall Running Fitness prediction29.2%
Running Fitness Test
-
To establish Lactate Threshold Pace and Lactate Threshold HR, the Running Fitness Test will encourage users to run in a few different pace zones, but primarily base the measurements on the data gathered when running at a mixed oxygen intensity (both aerobic and anaerobic systems are being used, such as during a marathon pace effort). This will be the most stable pace and heart rate relationship to create the most accurate estimations.
-
Max Heart Rate will be predicted based upon your individual maximum heart rate achieved during the Running Fitness Test. It is expected that anyone completing the Running Fitness Test will reach 90% of their max intensity, and from this reading the algorithm will make a prediction to what the corresponding intensity of 100% max intensity and Max Heart Rate would be.
-
Current accuracy: 87%, margin of error +/-5%
-
Main problems solved with the Evolab Updates
-
Predictions and estimations within the EvoLab system are easier to access (unlock), more stable, and more accurate
-
EvoLab data is unlocked after 25 consecutive minutes of a run at 60% of Heart Rate Reserve or higher are recorded
-
[(Max HR - Resting HR) * 0.7] + Resting HR = Heart Rate Reserve
-
-
Predicted and estimated times can be recorded after completing the Running Fitness Test just one time
-
Using the time-pace model above, we can assess four separate running abilities
-
Base (30km+)
-
Endurance (10km)
-
Speed (3km)
-
Sprint (400m)
-
-
The Running Fitness Test is a quick way to obtain, or reassess, Lactate Threshold Pace, Lactate Threshold Heart Rate and Personal Maximum Heart Rate. Why?
-
New users want easy to access and accurate results.
-
If a user believes their current Running Fitness estimations to be inaccurate, they can quickly complete one Running Fitness Test to calibrate their data
-
After injury or a period of inactivity/low training, it is easier to record one Running Fitness Test to quickly reassess fitness levels
-
A user can record a Running Fitness Test to obtain a quick estimation of their Max Heart Rate
-
-
When evaluating the user under normal training conditions, the evaluation of the ability should not decrease. By identifying that the load fatigue exceeds a certain threshold, it is determined that the training is in accordance with the law, and the ability should not be decreased.
EvoLab 2.0 display updates
Progress Page - Running Fitness
Home
Secondary page
-
Title: Running Fitness
-
Running Fitness Score: Displays the absolute value of a user's running ability score (40-100), to help better understand their strengths and areas for improvement as a runner
-
Running Fitness Score = Mean score of the four separate Running Fitness scores (Base, Endurance, Speed, Sprint)
-
Running Fitness Breakdown: Four abilitiesBase = Aerobic endurance, > 30kmEndurance = Lactate threshold ability, ~ 10kmSpeed = Speed endurance, ~ 3kmSprint = Sprint ability,. ~ 400mUsers can view each ability as and compare their scores to their overall Running Fitness score. This allows users to interpret their individual skills and find training methods to improve a specific ability to meet their goals.
-
Basic metrics: VO2 Max prediction algorithm does not change. Lactate Threshold Pace and Threshold Heart Rate from Evolab 2.0 as discussed above
-
Race Predictor: Based on Evolab 2.0
Race Predictor times are based upon a users recent training (90 days) and how they are able to perform on their best day.
Race Predictor times do not take into consideration heat, humidity, altitude, or training surfaces. For example, if you've been training in cool conditions but your race day is hot, the times may not be accurate.
Personal information page - Pace Zones
-
Pace Zones
Previously, Pace Zones were determined by a users Lactate Threshold Pace in 6 different zones. With the updated EvoLab algorithms, each specific Pace Zone can be estimated based on the time-pace model (Now the model can directly output the lactate threshold pace, aerobic threshold pace and VO2 Max pace. According to these three key parameters (referenced above, W/CP/Pmax) there is a higher degree of personalization to Pace Zones for more accurate training.
- Zone 1 and 2 boundaries are roughly a users aerobic threshold speed
- The dividing line of Zone 2 and 3 is roughly a users Lactate Threshold Pace
- The boundary between Zones 5 and 6 is roughly the VO2 Max pace