Mail Archives: djgpp-workers/2004/02/16/15:51:17
--part1_140.222e4448.2d628726_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
In a message dated 2/16/2004 3:44:29 PM Eastern Standard Time,
rudd AT cyberoptics DOT com writes:
> When I run my 2-D FFT routines, the
> most obvious indication that I have a stray NaN in the array is an
> agonizingly-slow execution, since the NaN rapidly infests the entire array.
>
As you know, NaNs often crop up at the least expected times. It could well
be worth the effort to test for a NaN result after each computation or series
of computations.
KB Williams
--part1_140.222e4448.2d628726_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
<HTML><FONT FACE=3Darial,helvetica><HTML><FONT SIZE=3D3 PTSIZE=3D12 FAMILY=
=3D"SERIF" FACE=3D"Georgia" LANG=3D"0">In a message dated 2/16/2004 3:44:29=20=
PM Eastern Standard Time, rudd AT cyberoptics DOT com writes:<BR>
<BR>
<BLOCKQUOTE TYPE=3DCITE style=3D"BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT=
: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px"></FONT><FONT COLOR=3D"#000000"=
BACK=3D"#ffffff" style=3D"BACKGROUND-COLOR: #ffffff" SIZE=3D2 PTSIZE=3D10 F=
AMILY=3D"SANSSERIF" FACE=3D"Arial" LANG=3D"0">When I run my 2-D FFT routines=
, the <BR>
most obvious indication that I have a stray NaN in the array is an <BR>
agonizingly-slow execution, since the NaN rapidly infests the entire array.<=
BR>
</BLOCKQUOTE><BR>
</FONT><FONT COLOR=3D"#000000" BACK=3D"#ffffff" style=3D"BACKGROUND-COLOR:=20=
#ffffff" SIZE=3D3 PTSIZE=3D12 FAMILY=3D"SERIF" FACE=3D"Georgia" LANG=3D"0"><=
BR>
As you know, NaNs often crop up at the least expected times. It could=20=
well be worth the effort to test for a NaN result after each computation or=20=
series of computations.<BR>
<BR>
<BR>
KB Williams</FONT></HTML>
--part1_140.222e4448.2d628726_boundary--
- Raw text -