I was looking at some CPS files from a PT and noticed that the highest average Watts for an interval did not always have the highest torque even when multiplied by the Cadence.
Examples from three seperate days during a 20 minute FTP interval. The High torque was from an Uphill TT and the other two are on a trainer. 130 pound athelete:
[font=Comic Sans MS]Watts lb/in RPMs[/font] [font=Comic Sans MS]219 87 X 104 =9,048. [/font] [left][font=Comic Sans MS]221 167 X 68 =11,356.[/font][/left] [left][font=Comic Sans MS]232 89 X 96 =8,544[/font][/left] [left][font=Comic Sans MS][/font] [/left] [left][font=Comic Sans MS]Am I missing a key variable or non-linear part of the equation?[/font][/left] [left][font=Comic Sans MS][/font] [/left] [left][font=Comic Sans MS][/font] [/left]
Now, just as an aside for others: in general, I recommend exporting data in the same format as used by the device that created it (assuming that format is readable by the program you want to use to manipulate it, e.g., Excel). IOW, if you imported data from a PowerTap, export it as .csv, if you imported data from an SRM, export is as .txt, etc. The reason I say this is that CyclingPeaks interpolates the data to the corresponding time base when exporting the file (e.g., 1.26 s for .csv), and on rare occassions this can introduce artifacts. Always exporting to the "native" time base should help prevent this from happening.
