Changes between Version 15 and Version 16 of Documentation/UserGuide/flags


Ignore:
Timestamp:
2020-04-20T12:45:24+02:00 (4 years ago)
Author:
dgoll
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Documentation/UserGuide/flags

    v15 v16  
    2323 
    2424== Other useful tips for debugging == 
     25*  If the problem is suspected to be related to ORCHIDEE, the [http://forge.ipsl.jussieu.fr/orchidee/wiki/Documentation/UserGuide/Printlev PRINTLEV] flags which controls the amount of diagnostic 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.  
    2526 
    26 * If the problem is ''DSG_review: suspected to be'' related to reading in .nc files, you can change l_dbg = .TRUE. in errioipsl.f90 to get more information. 
     27* If the problem is suspected to be related to ORCHIDEE reading in .nc files, you can change l_dbg = .TRUE. in errioipsl.f90 to get more information. 
    2728 
    28 * If the problem ''DSG_review: suspected to be'' 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. 
     29* If the problem is suspected to be 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. 
    2930{{{ 
    3031  <variable id="info_level"                type="int">100</variable> 
     
    3334 
    3435 
    35 * ''DSG_review: The next point is the most important point here and shouldn't be hidden here; I would rephrase also: If problem is suggest to be due to orchidee_ol, ...'' 
    36 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.  
    37  
    3836* 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].