View Single Post
Old 15 Aug 2007, 07:35 (Ref:1989329)   #7
tobias_funke
Rookie
 
Join Date: Aug 2007
Posts: 13
tobias_funke should be qualifying in the top 10 on the grid
Essentially moving average filter is a 'smoother' if the trace and is good for damper speed and accelerations which have a very high frequency rate.

Im pretty sure that a moving average filter of 0.1s applies a linear (i think) average to 0.1 seconds of samples for every data point. So if you sample at 10 Hz with 0.3 MAF it will for a data point it will take the average of the actual values for the point you want, the point before and the point after and so on for the next point. If that makes any sense..

The problem with having too high a value for the MAF is you throw the baby out with the bath water. You can miss a heap of information as, with a big enough filter, you end up averaging samples over a long period of time. I'd imagine if you applied a 100s moving average filter to the speed trace of a 100s lap you'd simply get the average speed for the lap.

Also what sampling rate did you log the speed at? If the sample rate is too low it could throw some important data out (aliasing). For looking at normal speed traces 20 Hz is probably enough but to derive it like you have done, you would probably need at least 50 Hz though 100 Hz would be more.

It sounds silly, but its better to log at 200 Hz and filter a trace than it is to log and view at 50 Hz.
tobias_funke is offline  
Quote