[reply]
Thanks for letting me know how the PT works. Except you forgot to say whether the power measurement comes from peak, average or minimal torque during the period and peak, average, or minimal velocity during the period. Do you know? How it works could make a difference in evaluating and possibly explaining these inconsistencies without a need to invoke nefarious intent.
[\reply]
It takes a snapshot in time. If set on the 1.26 second recording mode, it takes the instantaneous value at that time slice. 1.26 seconds later, it takes another instant value. No max, min, average, etc. Just what the data is. Same for the other time recording modes (i.e., 2.52 seconds, ...).
[reply]...but I do not accept that this is evidence that Joaquin deliberately manipulated the file to make himself look better than he is. If I wanted to change a PT file to look better than I am I would simply change the torque and power numbers by a set percentage across the board and leave everything else alone. This would be undetectable using all the methods you folks have used to examine this file.[/reply]
Which is why I originally said nothing about intent, just that the data was bad. It could indeed be a Powertap glitch, though in my 4-5+ years and 2000+ riding hours of owning 3 PT CPUs I've never experienced such a problem.
Thanks for letting me know how the PT works. Except you forgot to say whether the power measurement comes from peak, average or minimal torque during the period and peak, average, or minimal velocity during the period. Do you know? How it works could make a difference in evaluating and possibly explaining these inconsistencies without a need to invoke nefarious intent.
[\reply]
It takes a snapshot in time. If set on the 1.26 second recording mode, it takes the instantaneous value at that time slice. 1.26 seconds later, it takes another instant value. No max, min, average, etc. Just what the data is. Same for the other time recording modes (i.e., 2.52 seconds, ...).
[reply]...but I do not accept that this is evidence that Joaquin deliberately manipulated the file to make himself look better than he is. If I wanted to change a PT file to look better than I am I would simply change the torque and power numbers by a set percentage across the board and leave everything else alone. This would be undetectable using all the methods you folks have used to examine this file.[/reply]
Which is why I originally said nothing about intent, just that the data was bad. It could indeed be a Powertap glitch, though in my 4-5+ years and 2000+ riding hours of owning 3 PT CPUs I've never experienced such a problem.