Quote:
Originally Posted by vamfun
Although it is accurate, my algorithm creates a control dead zone with a width of + or -1 precision unit centered on the last event. That is a big price to pay for the improved rate noise from an oscillating edge.
|
How can you call it accurate and then describe how it is inaccurate?
See post 58.
Quote:
Originally Posted by vamfun
So Joe has reached a compromise position by providing a GetDistance() that is control friendly but sensitive to oscillating edges and a GetRate() that is insensitive to oscillating edges.
|
What did I compromise? It simply doesn't report invalid measurements.
-Joe