Black lightweight screentap diamond gloves update#

And we hope to have a release update later this season to support these kinds of things (multi-week planning, import from excel, ical integration). We constantly look to improve user experience. We have a lot of data and algorithm building blocks to put in place. Yes - this needs to be much better and smoother workflow. What is missing (I think I hear you?) - incorporating training load estimates into long term training plan building (a season) and show estimated effort over the entire plan WHILE you are building it, dynamically updating the charts. So all these pieces and calculations are there - no question. That effort is used in future Training Load. You can enter your goals and it will calculate estimated effort. SportTracks.mobi definitely supports planned workouts which you can add in the calendar just by clicking a day. While TSB is familiar and comfortable to a lot because of the ST3 Training Load Plugin, we want to stay at the forefront of science. Side note: We chose to go with the Banister model instead of TSB because it's more modern and has the most actual real world data validation. If you lay out a training plan with base building and your Performance isn't increasing - you have a problem. If you're going into a race and your Fatigue (ATL) is close or matching your Fitness (CTL) - you have a problem. If your performance (TSB) crashes - you have a problem. The numbers won't match at all, but it's approximately similar. What you know as CTL is shown in the Fitness chart. What you know as TSB is shown in the Performance chart. 'Negative TSB' doesn't typically happen unless you stress your body really hard from an untrained state.īut the principles are the same. I can see how you'd be uncomfortable switching. If you're used to the ST3 Training Load plugin which uses a different physiological model it will definitely take some getting used to the new data. I'm sorry to hear you're disappointed Henrik. I'll save you a click, it's: 1) Heartrate, 2) Power, 3) Grade adjusted speed, 4) Speed, 5) Intensity. You may also be interested in the calculation details which talk about the order we rank data that is available: This is how it should work, and this is how it does work.įor this to work, it's essential you do two things to make sure your data is categorized correctly:ġ) Pick the right top-level category (run/bike)Ģ) Set up your POWER, HEARTRATE, SPEED zones on the training page for the particular category (under 'My Account') Your example with 30 seconds of high intensity should score higher during those phases, and lower during cruise phases. So, for a single workout, we -ABSOLUTELY- take into consideration time in zones. There isn't really any magic here, it's actually the same approach we use. TSS is just a trademarked acronym that incorporates TRIMP for different data sources (HEARTRATE,SPEED,POWER).

In the end, you still need to listen to your body (and your coach).Īny questions or comments on training load? Post below. Duration of peak (the 'width' of the curve peak).Maximal predicted performance (the 'height' of the top of the curve).Timing (the day the top of the curve peaks).If you look closely at the last two tapers you'll see variation in: As with any model it is not 100% accurate so your peak taper timing may vary by a few days. Keep in mind the training load feature is a model which predicts performance. Compare the two tapers final predicted performance with the fitness and fatigue values. Using what you've learned, notice the difference of these charts in the last week versus the examples above. In the second example, we've chosen to simply take a week off before the race: In the first example, the last 3 workouts rapidly diminish in intensity going into the weekend: The final example shows two one-week tapers and their effect on your predicted performance.