Changes between Version 298 and Version 299 of doc/app/runtime_parameters


Ignore:
Timestamp:
May 22, 2019 10:12:20 AM (6 years ago)
Author:
kanani
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • doc/app/runtime_parameters

    v298 v299  
    378378}}}
    379379{{{#!td
    380 Flag for debug output to UNIT 9.\\\\
     380Flag for debug output to UNIT 9 during initialization phase and final actions of PALM run.\\\\
    381381By adding the parameter '''debug_output''' = ''.T.'', pre-defined debug_message(s) will be printed to the {{{DEBUG_00*}}} files (UNIT=9) in the temporary directory of a PALM run for each processor core. This can be very helpful to narrow down the location of a model crash simply by setting this parameter instead of having to add WRITE statements and re-compile the code. Once the location is narrowed down, set '''debug_output''' = ''.F.'' and implement your own {{{CALL debug_message (....)}}}. You may search the SOURCE code for the string "debug_message" to find out how it works.\\\\
    382382'''NOTE:''' Adding {{{CALL debug_message (....)}}} in new places might require setting of
     
    385385        ONLY:  debug_output, debug_string
    386386}}}
    387 if not already set.
     387if not already set.\\\\
     388Additionally, the flag [wiki:doc/app/d3par#debug_output_timestep debug_output_timestep] enables debug output during timestepping. Keep in mind that this may create very large DEBUG files.
     389}}}
     390|----------------
     391{{{#!td style="vertical-align:top"
     392[=#debug_output_timestep '''debug_output_timestep''']
     393}}}
     394{{{#!td style="vertical-align:top"
     395L
     396}}}
     397{{{#!td style="vertical-align:top"
     398.F.
     399}}}
     400{{{#!td
     401Flag for debug output to UNIT 9 during timestepping.\\\\
     402For further details, see [wiki:doc/app/d3par#debug_output debug_output].
    388403}}}
    389404|----------------