Why is my PMC whacky?

gina

I have recently upgraded to WKO 3.0.

Can't figure out why the TSB scale and TSS/day scale are so high. TSB tops out @ ;630 and TSS @ ;756. I don't see anywhere in chart customization to change this to a more reasonable scale.

Also, getting very bizzare TSS totals for the week like 5000!!

Tom Glynn

I've got no problems in WKO 3.0. Is there a particular ride throwing it off? Any rides have the wrong TSS or are there duplicate records?

ht001

I probably can't help with the techie stuff, but I noticed once on mine that some how my Garmin had included a drive between two different locations as distance that I had run so my TSS skyrocketed. Again, not terribly helpful, but I guess I'm just saying that it could be an issue with what's been recorded. ???

gina

Thanks!! I went back and looked. For some reason a run was given a TSS of 4959 !! (obviously, hasn't seen me run). I was able to override that number and now things look normal.

Now, can you tell me why WKO is calculating my interval NP too low??? Overall data ia appropriate. Interval NP is ~ 50 watts lower than real time and what PA shows.

Linda Patch

Keith here--

Do you need to set your threshold power and pace zones in 3.0, because they did not transfer over correctly? For example, if your threshold power is at whatever the default Joe Athlete puts out, your NP will be quite low, as Joe Athlete's FTP is probably closer to Halligan's! That's all I can think of for now.

gina

Hey Keith- You were my next source. Yes, I have TP set appropriately. I am going to PM you on FB. Thanks!

Tom Glynn

A long shot possibility, but are your intervals really short, say 5 minutes or so? The NP math algorithm doesn't start calculating NP for a few minutes. Can't remember, but it could be 3 or 5 minutes. It may be possible that the PA software and the WKO software are calculating the NP slightly differently and then right at the 3 or 5 minute mark they both start calculating and recording the value. I would think if they went for another 30 seconds to a minute, they would come very close again.

You can test my wild theory by manually selecting a range that includes your possibly short range and adding another minute to it. Does the NP plunge back to a reasonable number?

I'm just guessing, but if your NP is correct for the whole ride, and not for an interval, it must be some fluke just around the beginning of the calculation start.

tom

TH3 FRB

Posted By Linda Patch on 16 May 2010 12:55 PM

Keith here--

Do you need to set your threshold power and pace zones in 3.0, because they did not transfer over correctly? For example, if your threshold power is at whatever the default Joe Athlete puts out, your NP will be quite low, as Joe Athlete's FTP is probably closer to Halligan's! That's all I can think of for now.

FTP  has no bearing on NP.  NP is just just a rolling average (more or less) of your actual power output.  I wasn't aware the PA calculated NP...thought that was only licensed to TrainingPeaks, Ergomo, and Saris (Joule).

Tom Glynn

Posted By Joel on 18 May 2010 10:15 PM 

  I wasn't aware the PA calculated NP...thought that was only licensed to TrainingPeaks, Ergomo, and Saris (Joule).

 

Joel,

The formulas for NP, IF, TSS etc. were created by Coggan.  He has made them "open architecture" and will allow anyone to use them.  He doesn't verify that other party calculations are correct.  Per a post in Google Wattage, he wants to keep standardization in this fairly small market.

 

Tom

TH3 FRB

Has PA always done NP?

Tom Glynn

Not sure. I only use PA to download data and then export it to WKO. I've never looked at the graphs or analysis. I just looks rally clunky compared to WKO.