Subject: bessel.lisp error codes and noisy quad_qagi
From: Edwin Woollett
Date: Fri, 11 Nov 2011 14:47:08 -0800
On Nov. 11, 2011, Raymond Toy wrote:
--------------------------------------
>> ... finally:
>>
>> ***MESSAGE FROM ROUTINE DQAGI IN LIBRARY SLATEC.
>> ***INFORMATIVE MESSAGE, PROG CONTINUES, TRACEBACK REQUESTED
>> * ABNORMAL RETURN
>> * ERROR NUMBER = 5
>> * ***END OF MESSAGE
>>
>> (%o5) [-311.0051190974822,70.**21683385597015,5985,5]
>>
>> Is there a *quieter way* I can use quad_qagi for this
>> calculation?
>>
>
>Right now you get to go and remove the print from bessel-k in
>src/bessel.lisp. :-(
>
>Rather than doing these fixes one at a time, perhaps it's time to
>consider
>what maxima should do with these kinds of errors and fix them all at
>once.
>I certainly don't want the message to be removed; there needs to be some
>way to inform the user about issues. This is what needs to be designed.
>
-------------------------------
I am relying on the error code (fourth element of returned list)
returned by quad_qagi to make a decision about what to do
next inside nint. That's really all the information I need from
quad_qagi. The rest of the zbesk ierr = stuff is not needed,
nor is the final
***MESSAGE FROM ROUTINE DQAGI IN LIBRARY SLATEC.
For my purposes, this is noise.
Other programs which call bessel-k may profit from the micro
error messages produced.
A global flag (which would allow an application which only
needs the macro information provided in the list returned by
quad_qagi to turn off the additional micro info) would
be useful.
Ted