If it doesn't, you might try closing then reopening the chart to try to trigger recalculation. should do it automatically (it did for me). Is there a way to get the TSS scores to recalculate once I have set new threshold values with the UI ? Will it use the date ranges defined via the UI ? So if I say from Jan-01-2015 to April-30-2015 my run threshold was 4:10/km, then set it to 4:00/km from May 1st to today, can I get it to recompute rTSS for all 2015 ? *Or almost 1400 athlete-years, assuming people train every day and ignoring leap years.Ībout 100 athlete years was me re-downloading and re-downloading as I finally figured out the accent bug. I have a sense, though, that many people would like that option.anybody want to share their thoughts or opinions on the matter?Īndrew Coggan wrote:BTW, in one of our recent meetings it was shared that more than 500,000 files* were transferred from TP to WKO4 in the 1st 24 h after the program was released.so the sync must be working for somebody. In the end we decided not to, since many people seem to have garbage files or data points that screw up their mean maximal power curve, and hence the model fit (why people let such things persist is another question). The good news is that WKO4 has a far nicer UI for setting FTP (sFTP), so it shouldn't take all that long to do so (and the fact that you have to do it manually should discourage people from micromanaging their sFTP, which is a bad idea).Īs an aside, one thing we debated was whether to let the program enter sFTP for you (based on the model-derived FTP, or mFTP), either by default or by active choice. Unfortunately, due to differences in the way WKO+ 3 and TrainingPeaks handled such historical metadata, it wasn't possible to seamlessly carry over over your FTP settings used to calculate TSS, and hence CTL/ATL/TSB. Marcag wrote:Now if only I recalculate TSS scores :-)