You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The load_kernel function (https://py.api.tudat.space/en/latest/spice.html#tudatpy.interface.spice.load_kernel) that exposes the furnsh_c routine from SPICE does not allow the user to do any error handling. When sued in a try-except block in a python script, any exceptions occurring in the CSPICE routine is not being caught. Instead, the program crashes with the following message:
The attempt to load "S19TIGE2006_075_2006_079.CKF" by the routine FURNSH
failed. It could not be located.
A traceback follows. The name of the highest level module is first.
furnsh_c --> FURNSH --> ZZLDKER
Oh, by the way: The SPICELIB error handling actions are USER-TAILORABLE. You
can choose whether the Toolkit aborts or continues when errors occur, which
error messages to output, and where to send the output. Please read the ERROR
"Required Reading" file, or see the routines ERRACT, ERRDEV, and ERRPRT.
I do not know what exactly needs to be done to enable the error to be caught in a try-except block, but if it is easily attainable, it may be a good feature to have.
The text was updated successfully, but these errors were encountered:
The load_kernel function (https://py.api.tudat.space/en/latest/spice.html#tudatpy.interface.spice.load_kernel) that exposes the furnsh_c routine from SPICE does not allow the user to do any error handling. When sued in a try-except block in a python script, any exceptions occurring in the CSPICE routine is not being caught. Instead, the program crashes with the following message:
================================================================================
Toolkit version: N0067
SPICE(NOSUCHFILE) --
The attempt to load "S19TIGE2006_075_2006_079.CKF" by the routine FURNSH
failed. It could not be located.
A traceback follows. The name of the highest level module is first.
furnsh_c --> FURNSH --> ZZLDKER
Oh, by the way: The SPICELIB error handling actions are USER-TAILORABLE. You
can choose whether the Toolkit aborts or continues when errors occur, which
error messages to output, and where to send the output. Please read the ERROR
"Required Reading" file, or see the routines ERRACT, ERRDEV, and ERRPRT.
================================================================================
I do not know what exactly needs to be done to enable the error to be caught in a try-except block, but if it is easily attainable, it may be a good feature to have.
The text was updated successfully, but these errors were encountered: