Changes between Version 11 and Version 12 of Documentation/UserGuide/flags


Ignore:
Timestamp:
2020-02-28T15:44:42+01:00 (4 years ago)
Author:
jgipsl
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • Documentation/UserGuide/flags

    v11 v12  
    1 = How to prepare for debugging = 
     1= How to get started debugging = 
     2Author: M. !McGrath[[BR]] 
     3Last revision: J. Ghattas 2020/02/28[[BR]] 
     4 
    25 
    36You are running ORCHIDEE, just like every other day, when it stops for no apparent reason.  You don't have output files from the simulation, and the run.card lists "Fatal".  What can you do? 
    … …  
    1316   
    1417 
    15 = Other useful tips for debugging = 
     18== Other useful tips for debugging == 
    1619 
    17 * Can change l_dbg = .TRUE. in errioipsl.f90 to get more information printed out about reading in .nc files. 
     20* If the problem is related to reading in .nc files, you can change l_dbg = .TRUE. in errioipsl.f90 to get more information. 
    1821 
    19 * Can also make the following changes to iodef.xml to get more information printed out from XIOS. 
    20  
     22* If the problem is related to XIOS, for example writing of output variables, you can make the following changes to iodef.xml to get more information printed out from XIOS. 
    2123{{{ 
    2224  <variable id="info_level"                type="int">100</variable> 
    … …  
    2527 
    2628 
    27 * The [https://forge.ipsl.jussieu.fr/orchidee/wiki/Documentation/UserGuide/Printlev printlev] flags can be very useful in finding out which routine the code is crashing in.  If you can't get a line number any other way, turn up the printlev as high as possible, check to see the last line printed out, and then check to see the next line which should be printed out.  The crash must be happening somewhere between those two lines.  
     29* The [http://forge.ipsl.jussieu.fr/orchidee/wiki/Documentation/UserGuide/Printlev PRINTLEV] flags which controls the amount of text output from ORCHIDEE can be very useful in finding out which routine the code is crashing in.  If you can't get a line number any other way, turn up the PRINTLEV as high as possible, check to see the last line printed out, and then check to see the next line which should be printed out.  The crash must be happening somewhere between those two lines.  
    2830 
    2931* And if you are up against a bug that seems to change every single time you run the code, even with all the above flags on, you might want to check out [https://forge.ipsl.jussieu.fr/orchidee/wiki/Documentation/UserGuide/valgrind Valgrind].