Willehond Posted December 18, 2009 Share Has anyone upgraded to WKO+ 3.0 and is it worth it? I don't see what upgrades could be worth 64 dollars! Man, I hate it when I have to upgrade just to be current... Link to comment Share on other sites More sharing options...
Christie Posted December 18, 2009 Share I also got an email from them - could get it for 1/2 price on day 1. It does not look like it has significant upgrades. The quadrant analysis looks like something new - don't know if it is something useful, however. Link to comment Share on other sites More sharing options...
Windbreaker Posted December 18, 2009 Share Willehond, don't do it yet. Try the GoldenCheetah stuff when they release a new version in the next few weeks. It won't cost you a thing. I see that WKO is now starting to incorporate some of the GC functionality now as well. Nothing wrong with WKO, just that GC is going to leave it behind shortly - it has a ton of support now. Link to comment Share on other sites More sharing options...
Windbreaker Posted December 18, 2009 Share and it sounds like the NP calcs have developed a bug See extracts below from the wattage forums2009/12/18 Chris Cleeland <chris....@gmail.com>:> On Thu, Dec 17, 2009 at 5:00 PM, Nate <n.......@gmail.com> wrote:>> So what is the best way to handle data from a PT to use your NP>> algorithm.>> it's not data from the PT that's the problem--it's data from a PT when> the sampling rate is anything other than 1.26s (or whatever the most> frequent sampling rate is).Except, Nate's file is 1.26seconds, and should be producing thecorrect value, and it certainly looks to me like WKO 3.0 does get the calculation wrong. I suspect this due to new code which attempts to deal with irregular sampling rates, and is fooled by the non multiple of 1 second nature of the PowerTap into thinking some of the samples cover more than 1 second. ie: WKO 3.0 thinks there are these whole seconds:1,2,3,4,6,7,8,9,11 and for the 6th second it considers that a sample for the 5th and 6th seconds, and the same with the 11th for the 10th and 11th seconds.Doing this for a range of the file and calculating myself, I get an NPvalue the same as WKO 3.0's. I would say this is a WKO 3.0 bug, and if you have a PowerTaprecording at 1.26seconds, stick with 2.2. Jim.and ...My PT is recording at 1.26seconds - a 2hr:49min ride yesterday gives NP of 249 in 2.2 and 255 in 3.0. A 20 min interval within the ride is 297 in 2.2 and 300 in 3.0. and ... I have NP discrepancies with my SRM (set as 0.5 second sampling rate)as well. These are smaller in magnitude but cause concern none theless. ie 60 min period 2.2 - 261W 3.0 - 267W data handling or calculations do appear to be different betweenprogramsand Coggan explains ... On Dec 18, 8:43 am, Andy Coggan <acog...@earthlink.net> wrote:> As Hunter described when announcing release of the new version, there> are differences in how it handles gaps in the data. I suspect that is> what you are seeing, i.e., minor differences are to be expected if> your file isn't "perfect".How "should" gaps be handled? What if, as an off-hand example, the gap was long enough to eat aburrito and drink a beer? and then acknowledgement ...On Dec 18, 2:52 am, Jim Ley <jim....@gmail.com> wrote: > Except, Nate's file is 1.26seconds, and should be producing the> correct value, and it certainly looks to me like WKO 3.0 does get the> calculation wrong. I suspect this due to new code which attempts to> deal with irregular sampling rates, and is fooled by the non multiple> of 1 second nature of the PowerTap into thinking some of the samples> cover more than 1 second.>> ie: WKO 3.0 thinks there are these whole seconds:> 1,2,3,4,6,7,8,9,11> and for the 6th second it considers that a sample for the 5th and 6th> seconds, and the same with the 11th for the 10th and 11th seconds.> Doing this for a range of the file and calculating myself, I get an NP> value the same as WKO 3.0's.>> I would say this is a WKO 3.0 bug, and if you have a PowerTap> recording at 1.26seconds, stick with 2.2.After digging into things a bit more, there does indeed appear to be aproblem with the way that WKO+ 3.0 calculates normalized power fromdata recorded using a legacy (i.e., non-ANT/ANT+) PowerTap. This bugdoes *not* affect the calculation of normalized power from datacollected using any other device. A fix has already been developed anda new build will be released as soon as it can be adequately tested. Andy CogganWindbreaker2009-12-18 15:04:15 Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now