comp.lang.idl-pvwave archive: archive » avoiding "floating illegal operand" errors with /nan keyword in mean

Home » Public Forums » archive » avoiding "floating illegal operand" errors with /nan keyword in mean

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Re: avoiding "floating illegal operand" errors with /nan keyword in mean [message #85631 is a reply to message #85605]

Thu, 22 August 2013 12:16

Paul Levine
Messages: 29
Registered: February 2008

Junior Member

On 2013-08-21 12:58:38 +0000, wlandsman said:

> On Tuesday, August 20, 2013 10:17:41 PM UTC-4, Paul Levine wrote:
>> On 2013-08-21 00:26:02 +0000, wlandsman said:
>>
>>
>>> Does setting !except=0 work for you? --Wayne
>>
>> Thank you for the suggestion. It does work insofar as the error>
>> message does not appear, though when I check_math I get 128, so isn't>
>> that more or less the equivalent of simply ignoring the errors?
>>
>
> Yes, setting !EXCEPT suppresses the annoying messages
>
> Why don't you want to ignore the errors (really just warnings)? It
> doesn't hurt the computer to compute floating illegal operands.
> You did say you were interested in efficiency and I'm fairly certain
> that ignoring the warning messages would be the fastest method.
> Just be sure to reset !EXCEPT afterwards so that you catch
> errors/warnings in the rest of your code. If you want to be extra
> careful then make sure the CHECK_MATH output is 128 (floating illegal
> operand) and no other math error occurred durning the mean()
> calculation.
>
> I know this doesn't answer the question you posted, which is an
> interesting problem in its own right. But sometimes the best way to
> untie a knot is to cut it with a knife. --Wayne

Thank you for the reply. The reason I was trying to avoid simply
ignoring those errors was because I was afraid that doing so would mean
missing other errors that were potentially less innocuous. I didn't
think to reset !EXCEPT afterwards; that simple solution seems to
clearly be the best one for me at this point, as I won't have to worry
about missing other errors. The suggestion is much appreciated, as I
now see how I can cut the knot with a knife but still be able to tie it
back up again afterwards :)

Report message to a moderator

[Message index]

		avoiding "floating illegal operand" errors with /nan keyword in mean By: Paul Levine on Tue, 20 August 2013 16:37
		Re: avoiding "floating illegal operand" errors with /nan keyword in mean By: wlandsman on Tue, 20 August 2013 17:26
		Re: avoiding "floating illegal operand" errors with /nan keyword in mean By: Paul Levine on Tue, 20 August 2013 19:17
		Re: avoiding "floating illegal operand" errors with /nan keyword in mean By: wlandsman on Wed, 21 August 2013 05:58
		Re: avoiding "floating illegal operand" errors with /nan keyword in mean By: Paul Levine on Thu, 22 August 2013 12:16
		Re: avoiding "floating illegal operand" errors with /nan keyword in mean By: Fabzi on Wed, 21 August 2013 14:11
		Re: avoiding "floating illegal operand" errors with /nan keyword in mean By: Paul Levine on Thu, 22 August 2013 12:26

Previous Topic:	Call object cleanup method when IDL exits
Next Topic:	IDL Grib Routines

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Fri Oct 10 03:43:30 PDT 2025

Total time taken to generate the page: 1.04010 seconds