|Jan25-13, 05:11 PM||#1|
Why does DataStudio compute velocity from x(t) the way it does?
A motion sensor gives the position of an object at times separated by Δt. DataStudio then calculates velocity by this method:
v(t) = (x(t + 3Δt/2) - x(t - 3Δt/2)) / 3Δt
I wonder why it doesn't do it like this: v(t) = (x(t + Δt/2) - x(t - Δt/2)) / Δt
I know it gives the same v if acceleration is constant since in both cases it corresponds to average speed in the middle of the interval, but if acceleration is not constant (e.g. mass-spring) it must give a value for v that is not as accurate.
physics news on PhysOrg.com
>> Promising doped zirconia
>> New X-ray method shows how frog embryos could help thwart disease
>> Bringing life into focus
|Jan25-13, 08:17 PM||#2|
Maybe the velocity is averaged over multiple timesteps as a smoothing (filtering) feature. An average velocity computed using every single sample might have too much high frequency jitter due to noise.
|Similar Threads for: Why does DataStudio compute velocity from x(t) the way it does?|
|Compute the velocity of a free-falling parachutist using Euler's method||Introductory Physics Homework||3|
|How To Compute Y Velocity For A Projectile - Emulating an online Disney game||Introductory Physics Homework||0|
|Using a time gradient to compute velocity||Calculus||0|
|Question about the program "Datastudio"||Introductory Physics Homework||7|
|Compute sup,inf, and more...||Introductory Physics Homework||2|