[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

*Subject*: Re: Breaking on Math Warnings?*From*: Scott Norton <norton(at)optics.rochester.edu>*Date*: Thu, 07 Jan 1999 16:09:20 -0800*Newsgroups*: comp.lang.idl-pvwave*Organization*: PSINet*References*: <369549A0.E20CF10B@optics.rochester.edu>*Xref*: news.doit.wisc.edu comp.lang.idl-pvwave:13281

I just found the answer to my own question. Sorry for taking up bandwidth. The key command to use is CHECK_MATH(). Although I now need to see if it works for finding convergence errors as when using the Guass2DFit routine (convergence errors are not listed in the table of returned math errors shown in the HELP menu on CHECK_MATH() ). -Scott Scott Norton wrote: > Can anyone tell me how to have a program "break" on math warnings in > IDL? > For instance, if Gauss2Dfit doesn't converge, how can I "respond" to > that warning? > Or, > If I get a "% Program caused arithmetic error: Floating underflow", how > do I "check" > for this? > The CATCH procedure explicitely says that it does not "catch" these > types of errors... > "Calling CATCH establishes an error handler for the current procedure > that intercepts all errors that can be handled by IDL, excluding > non-fatal warnings such as math errors." > > Thanks! > -Scott > Scott_Norton@surromed.com

**Follow-Ups**:**Re: Breaking on Math Warnings?***From:*Scott Lett

**References**:**Breaking on Math Warnings?***From:*Scott Norton

- Prev by Date:
**Breaking on Math Warnings?** - Next by Date:
**power style labels** - Prev by thread:
**Breaking on Math Warnings?** - Next by thread:
**Re: Breaking on Math Warnings?** - Index(es):