Changes between Version 59 and Version 60 of Doc/CheckDebug


Ignore:
Timestamp:
01/15/21 14:02:45 (3 years ago)
Author:
acosce
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Doc/CheckDebug

    v59 v60  
    158158 
    159159}}} 
     160In this case you need to explore the [wiki:Doc/CheckDebug#Debug Debug directory]. [[BR]] 
    160161If the following message is displayed : 
    161162{{{ 
     
    192193### The Debug directory ### 
    193194 
    194 If the simulation failed due to abnormal exit from the executable, a `Debug` directory is created in the working directory. It contains output text files of all model components for your configuration. You should read them to look for errors. For example : 
     195If the simulation failed due to abnormal exit from the executable, a `Debug` directory is created in the working directory. It contains output text files of all model components for your configuration. You should read them to look for errors.  
    195196 
    196197 * `xxx_out_gcm.e.err` and `xxx_out_gcm.e.out`(or `xxx_out_lmdz.e.err` and `xxx_out_lmdz.e.out`) --> lmdz  text output  
     
    198199 * `xxx_ocean.output` --> nemo text output 
    199200 * `xxx_inca.out` --> inca text output 
     201 * `xxx_out_xios.e.err` and `xxx_out_xios.e.out` --> xios log and error message  
    200202 * `xxx_run.def` --> lmdz parameter files 
    201203 * `xxx_gcm.def` --> lmdz  parameter files 
     
    203205 * `xxx_physiq.def` --> lmdz  parameter files 
    204206 * `xxx_orchidee.def` --> orchidee parameter files 
     207 * `xxx_****.xml` --> all xml files use for this simulation  
     208 
     209In models logs files (out_lmdz.x.err, out_lmdz.x.out, out_orchidee, ...) you will find output for each process of the simulation. You can look at the end of the first process to find main error message.  
    205210 
    206211[[NoteBox(tip, Your best friend is : {{{ grep -i error * ; grep -i 'e r r o r' *ocean.output }}} , 600px)]]