Wow, fail on my part!  1.4 was for something else that I did recently.  =

  I'm looking at the C-to-F code now, and I did indeed use 461/256.

BTW, for similar apps, where the sample/refresh rate is not critical,  =

and I'm averaging many samples, I've just added 'n' samples where 'n'  =

would happen to multiply the result so that the resulting math is some  =

power of two.

Cheers,
-Neil.



Quoting William Couture <bcouture@gmail.com>:

> On Thu, May 13, 2010 at 9:05 AM, PICdude <picdude3@narwani.org> wrote:
>
>> BTW, I've done C to F before, and I did the math for 9/5 at once. =A0I
>> used 717/512 =3D 1.40039 which is 0.03% error.
>
> Hmmm... 9/5 =3D 1.8
>             717/512 =3D 1.40039
>
> That doesn't seem like a 0.03% error.  Am I missing something here?
>
> Personally, I'd use 461 / 256 =3D 1.80078  (0.0434% error).
>
> Bill
>
> --
> Psst...  Hey, you... Buddy...  Want a kitten?  straycatblues.petfinder.org
>
> --
> http://www.piclist.com PIC/SX FAQ & list archive
> View/change your membership options at
> http://mailman.mit.edu/mailman/listinfo/piclist
>




-- =

http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist