In Reply To:
No, your analysis is correct. My only problem is the attribution that the only explanation for this "corruption" is the deliberate manipulation of the file by Joaquin to make himself look better than he is. There is actually no evidence the power numbers are suspect (since his reported time and power comports with the analyticcycling estimate for this climb and there was a witness to the effort who states he believes the reported time to be correct), only the speed and HR numbers are truly bizarre as I understand it.
Huh? Frank, the average power number which you say isn't "suspect" is created DIRECTLY from the values in the file which are obviously false. How can the individual data points be "suspect", yet the average of those values NOT be "suspect"? Look at this plot and tell me that it's not obvious that the power data isn't fudged with the blatant "cut and pasting" and repetition of power sequences. In fact, the beginning sequence is EXACTLY repeated at around minute 368 with the huge power spike up to EXACTLY 539 watts:
You also hang your hat on the fact that the overall distance is correct. Well, what happens if we calculate the apparent speed values by simply taking the distance increment recorded every 1.26s and multipy by 3600/1.26 to get km/hr? Here it is:
Look at that. Besides the long periods of EXACTLY constant speeds, the first few minutes of the file show multiple step changes in velocity between EXACTLY 25.71 km/hr and 17.41 km/hr in 1.26s!
BUT, and this is what you want us to believe, that data is no good, but somehow the averages are miraculously correct? Are you serious??
So, let's summarize:
1. The power data is obviously false and "cut and pasted"...yet the average is somehow OK because it's close to what he said it would be?
2. The speed calculated from the distance data requires massive step changes in velocity...yet the average is OK?
3. The speed data recorded in the file doesn't come close to matching the distance data recorded, even though both are calculated from the same internal signal in the PT hub...yet the distance is OK?
4. The data summary from downloading the head unit (as reported by Joaquin on 10/28) doesn't match the summary from this file...yet it's from the same file, right? So the problem is in the hub or the head unit? Really? How does that work?
5. As far as we know, the only person who has had access to this file prior to it's dissemination is Joaquin. That seems to cut down the possible "suspects" pretty quickly.
In Reply To:
So, such a "deliberate manipulation" explanation makes little sense to me, even though i cannot come up with another one.
How about someone trying to come up with a file that gives an average power and distance that they said it should have, yet not being "savvy" enough to realize that the way they are going about it would be VERY easy to be detected? No need to figure out any Machiavellian intent when simple incompetence will suffice.
In Reply To:
The file is corrupted. How it got that way is unknown although some here have speculated nefarious intent, even though they have no proof of same. Anyhow, IMHO, the data should not be used to try to "prove" anything. I think it should be left at that.
Oh, I'm SURE you wish it would just be left alone and discarded. The problem is, it clearly demonstrates unethical actions...in many ways. No proof? See summary above.
BTW, you keep using that word "corrupted" hoping that it will catch on (and since it must make you feel better.) In the words of another Spaniard, Inigo Montoya:
Quote:
You keep using that word...I do not think it means what you think it means.
http://bikeblather.blogspot.com/