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


Ignore:
Timestamp:
Apr 30, 2019 9:58:13 AM (6 years ago)
Author:
kanani
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • doc/app/runtime_parameters

    v297 v298  
    369369|----------------
    370370{{{#!td style="vertical-align:top"
     371[=#debug_output '''debug_output''']
     372}}}
     373{{{#!td style="vertical-align:top"
     374L
     375}}}
     376{{{#!td style="vertical-align:top"
     377.F.
     378}}}
     379{{{#!td
     380Flag for debug output to UNIT 9.\\\\
     381By 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.\\\\
     382'''NOTE:''' Adding {{{CALL debug_message (....)}}} in new places might require setting of
     383{{{
     384    USE control_parameters,                                                    &
     385        ONLY:  debug_output, debug_string
     386}}}
     387if not already set.
     388}}}
     389|----------------
     390{{{#!td style="vertical-align:top"
    371391[=#do2d_at_begin '''do2d_at_begin''']
    372392}}}