| 139 | | If your simulation crashes : |
| 140 | | - guidelines to understand the logs produced by libIGCM [https://forge.ipsl.jussieu.fr/igcmg_doc/wiki/Doc/CheckDebug] |
| 141 | | - if debugging is required, look at the [wiki:Documentation/UserGuide#Debuggingandprofiling Debugging section] on the [https://forge.ipsl.jussieu.fr/orchidee/wiki/Documentation/UserGuide HowTo], starting with the [wiki:Documentation/UserGuide/flags introductory page on debug flags]. |
| 142 | | - the [https://forge.ipsl.jussieu.fr/igcmg_doc/wiki/Doc/Setup#config.card TEST and DEVT options in config.card] can be useful as they keep more log files accessible |
| | 139 | If your simulation crashes you will first need to decide whether the crash was caused by libIGCM or by ORCHIDEE itself. One easy (rather solid) way is to check your configuration folder (config/ORCHIDEE_OL/MYTEST). If a Debug folder was added it was ORCHIDEE that crashed. To be 100% sure open the Script-file in your configuration folder and search for ERROR. If the error refers to orchidee_ol.ksh it was ORCHIDEE that crashed. |
| | 140 | - If it was libIGCM that crashed, carefully read the error log in the Script file. Most often it will be a trivial problem such as a typo in a file name or a path. Guidelines to understand the logs produced by libIGCM can be found [https://forge.ipsl.jussieu.fr/igcmg_doc/wiki/Doc/CheckDebug here] |
| | 141 | - If it was ORCHIDEE that crashed and you were using a single processor simply rerun the model after compiling it in debug mode. The model will of crash again (but not necessarily in the same place because PROD will not crash on divide by zero where DEBUG will crash) and will get an error-stack. This stack will tell you in which line the model crashed. The line number refers to some processed files that can be found in modeles/ORCHIDEE/build/ppcr/... but as a rule of thumb you need to subtract 9 lines from the error stack to get the correct line number in modeles/ORCHIDEE/scr_*/*.f90. |
| | 142 | - You can also make use of [https://forge.ipsl.jussieu.fr/orchidee/wiki/Documentation/TrunkFunctionality4#Consistencychecksr6614 the internal consistency checks] (starting r6616) to get an idea where the model crashes. |
| | 143 | - If the above options does not reveal the problem some serious debugging will be required. Look at the [wiki:Documentation/UserGuide#Debuggingandprofiling Debugging section] on the [https://forge.ipsl.jussieu.fr/orchidee/wiki/Documentation/UserGuide HowTo], starting with the [wiki:Documentation/UserGuide/flags introductory page on debug flags]. |
| | 144 | - The [https://forge.ipsl.jussieu.fr/igcmg_doc/wiki/Doc/Setup#config.card TEST and DEVT options in config.card] can be useful as they keep more log files accessible |
