Re: E96 Series Computation
- From: nospam <nospam@xxxxxxxxxxxxxx>
- Date: Thu, 14 Apr 2005 04:18:23 +0100
Fred Bloggs <nospam@xxxxxxxxxx> wrote:
>So I suppose the simplest way to handle these
>discrepancies, 920 in E192, and only a few values in E24 and below is to
>first compute the infinite precision value within the infinite precision
>triangle, and then use a CASE type program structure to catch the
>historical assignments, using the ROUND function elsewhere.
The simplest way to handle the whole problem is to use a table.
A table containing E3 to E192 ranges occupies 900 bytes.
A function which given a range and value returns the closest value (and the
next >= and =< values to allow simple iteration of a range in either
direction) occupies 540 bytes of 32bit Intel code.
It was never coded particularly for speed. On my 2GHz Athlon XP system it
finds around 2.6 million E96 values per second.
.
- Follow-Ups:
- Re: E96 Series Computation
- From: Fred Bloggs
- Re: E96 Series Computation
- References:
- Re: E96 Series Computation
- From: The Phantom
- Re: E96 Series Computation
- From: Fred Bloggs
- Re: E96 Series Computation
- From: The Phantom
- Re: E96 Series Computation
- From: Fred Bloggs
- Re: E96 Series Computation
- Prev by Date: Re: Radar Jamming
- Next by Date: was Re: Embedded System in Noisy Environment
- Previous by thread: Re: E96 Series Computation
- Next by thread: Re: E96 Series Computation
- Index(es):