Download pdf-ov
Transcript
EGOPSv52 SUM-OV A.1.3 Run-Time Errors in IDL Modules In case a run-time error occurs within an IDL module of EGOPS, the response is - independent of the precise type of error – as follows: the open EGOPS User I/F windows get immediately closed (stalled if EGOPS was started from within IDL), then the User is returned to the shell prompt in the console window, from where EGOPS was started and finally, the console window reports the error information as delivered from the IDL run-time error function (e.g., "Error in module TMANPL, line xx, due to array subscripts out of range..."; the source-code version reports errors more informative than the runtime version). EGOPS can immediately be started again after such error (proceeding as noted in the section on "Starting EGOPS") and it will come up as usual. Recommended actions by the User after an IDL run-time error: - - - Check the error message in the console window and try to understand it. If run without console window, re-run from within such a window to be able to see and check the error message. (Advanced Users: In case of having IDL expertise you could try to explore the state of suspicious variables by interactive inspections at the IDL prompt.) Carefully check whether a relation of the error to some obvious misuse could exist (assignment of ill-formatted/deliberately manipulated files, deliberate modifications of EGOPS program files, file structure, or default data files as set up during EGOPS installation, etc.). Try to eliminate potential error sources. Re-start EGOPS and try to repeat the run-time error condition. If it no longer occurs, the (probably User-produced) problem is fixed. If the error repeats identically and repeated fixing efforts fail, evaluate whether the error can be avoided at first aid by an alternative approach to the simulation problem of interest. Bring, as appropriate and needed, the error to the attention of the EGOPS development team at IGAM/UG. WegCIGAMUG/ESA-EGOPSv52/SUM-OV, Issue 2 61