CMP EMBEDDED.COM

Login | Register     Welcome Guest  
HOME DESIGN PRODUCTS COLUMNS E-LEARNING CONFERENCES CODE FORUMS/BLOGS NEWSLETTERS CONTACT FEATURES RSS RSS

Why all the math?



Embedded.com

Suppose, for example, that I'll always be applying the algorithm on the last five measurements; sort of a souped-up moving average. Then the x-values will always be (again, shifting and scaling as needed):

(22)

The values of the sums are:

(23)

The determinant is:

(24)

and the inverse is:

(25)

or:

(26)

Of course, it's a constant matrix, so we can encode it as such, using whatever scaling we find to be appropriate.

Now let's look at the terms in U. These, you'll recall, do involve the measured values of the y's, so we can hardly compute them in advance. On the other hand, u1 depends only on the y's, not the x's. We can compute this one recursively, using the equivalent of a moving average (or, more properly, sum). Just add the one new data point and drop the oldest one.

Let me make this last point crystal clear. Suppose the last measurement I've processed was yk. After I've processed that data, the value of u1 will be:

(27)

1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10

Rate this article: Low High
Current rating
  • .
Embedded.com Career Center
Looking for a new job?
SEARCH JOBS

Browse all jobs

SPONSOR
RECENT JOB POSTINGS



TECH PAPER
WEBINAR
WEBINAR
WEBINAR




 :