andylaurence wrote:So we have a 3kph tolerance and probably a 30 metre window where that speed happened. Is the start or finish off the speed trap at the finish line? If either. Assuming the latter, then the speed achieved is likely around 15 metres before that. Lots of tolerances add up. Add in a 0.001 tolerance at the start of the trap and one at the end, you suddenly have a tolerance of 0.002.
What's key here is that the speed of a car can be measured in many ways and they all have different tolerances, which may vary on circumstance. It's quite possible that the tolerance on the FIA speed trap allied to the tolerances on the location and that of the speed measurement of the data logger on the car has led to a large disparity in figures. It could alternatively be the PR team making a number up.
Sorry i don't understand your first part. if you have an averaging either you have a constant speed or a superior minus inferior speed hence there's no indication as to when the speed was reached (this is why we try to measure speed with as little distance as possible).
As for the tolerance, the 0,001 is for the decoder so the tolerance of the loops are already factored in it seems (and probably some software related tolerance too).
Now from what i read and my experience as an official sprint kart time keeper, the FIA doesn't bring anything, the loops are part of the track infrastructure (and that's precisely one criteria of homologation for having minimum level competitions) so there nothing really added to the decoder tolerance (yes you can always add some probable errors like wear of loops, interference etc.. but that's nothing special). And even if you do 0.002. you just add two km/h in the range (357/362)
Now the way i understand it:
-the 366 km comes from the speed trap which is on site and the averaging leaves an error margin that is composed off: tolerance_error+averaging_window_error. the minimum error would be 2-3 kph with tolerance error alone. From that we would need to know the rate of change of acceleration to know how the speed was averaged over the 30 meters.
-The 378kmh smees to come from onboard sensors and/or GPS (datalinked to the pits) and thus according to tim are very precise. In fact according to (1) the precision of GPS (which is bettered by optical sensors) is 0,001
kph.
The way i interpret it:
Even with the averaging the speed trap measure doesn't lead to completely distorted measurements. The first reason is that the error tolerance over signal is low due to the window chosen. Next the averaging window can't hide too high variation simply because we are dealing with cars at high speed and thus with relatively low acceleration and the time (0,3sec) needed to span the window is relatively small to have lots of changes in rate of change of acceleration.
However, during the window, such change (in acceleration rate) may happen due to slipstream conditions and what is interesting is that if such a change really occurred (and what hidden by the averaging window) then the next few meters to the initial brake point may have seen a rather great acceleration of the car. If three cars were in slipstream this may be the reason.
Of course the most important point is to know where the speed trap loop is centered on.
We do not know much more but at least it seems the averaging is not the reason and hence we can have confidence in the speed traps (hourray!) for what they are: a measure of speed at a location along the track. How the speed will evolve after it is another story.
(1)ieeexplore.ieee.org/xpls/abs_all.jsp?arnumber=425848