Changes between Version 503 and Version 504 of doc/app/errmsg


Ignore:
Timestamp:
May 22, 2018 8:38:52 AM (7 years ago)
Author:
Giersch
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • doc/app/errmsg

    v503 v504  
    2525||='''Message identifier '''  =||='''Error message'''  =||='''Explanation'''  =||
    2626||[=#PA0001 PA0001]   ||manual restart settings requires file activation string "restart" || Values for parameters {{{dt_restart}}} or/and {{{restart_time}}} have been given in the {{{&runtime_parameters}}}-NAMELIST. This also requires to give the file activation string {{{"restart"}}} with palmbuild-option {{{-a}}}, because otherwise the restart files wouldn't be generated at the end of the PALM run. \\\\Repeat the run with {{{-a ".... restart"}}} or remove parameters {{{dt_restart}}} or/and {{{restart_time}}} from your NAMELIST-file. ||
    27 ||[=#PA0002 PA0002]   ||illegal coupling mode: ...   || This message is related to the atmosphere-ocean coupling or pure vertical nesting implemented in PALM. Internally, the variable {{{coupling_mode}}} defines the coupling setup used for the current respective model run. It may have one of the values "{{{atmosphere_to_ocean}}}" (atmospheric part of a coupled run), "{{{ocean_to_atmosphere}}} (ocean part of a coupled run), "{{{precursor_atmos}}}" (a precursor atmosphere run), "{{{precursor_ocean}}}" (a precursor ocean run),  or "{{{uncoupled}}}" (atmosphere or ocean run without any intended coupling). This error message means that the initialization of the coupling did fail because {{{coupling_mode}}} has a value different from the ones mentioned before. Possible reasons might be trying a coupling between two atmosphere runs (or two ocean runs), or problems with the {{{palmrun}}} script. ||
     27||[=#PA0002 PA0002]   ||illegal coupling mode: ...   || This message is related to the atmosphere-ocean coupling or pure vertical nesting implemented in PALM. Internally, the variable {{{coupling_mode}}} defines the coupling setup used for the current respective model run. It may have one of the values "{{{atmosphere_to_ocean}}}" (atmospheric part of a coupled run), "{{{ocean_to_atmosphere}}}" (ocean part of a coupled run), "{{{precursor_atmos}}}" (a precursor atmosphere run), "{{{precursor_ocean}}}" (a precursor ocean run), "{{{vnested_crse}}}", (the coarse simulation of a vertical nesting run) "{{{vnested_fine}}}" (the fine simulation of a vertical nesting run)  or "{{{uncoupled}}}" (atmosphere or ocean run without any intended coupling). This error message means that the initialization of the coupling did fail because {{{coupling_mode}}} has a value different from the ones mentioned before. Possible reasons might be trying a coupling between two atmosphere runs (or two ocean runs), or problems with the {{{palmrun}}} script. ||
    2828||[=#PA0003 PA0003]   ||dt_coupling is not set but required for coupling mode "..."   || This error appears if the temporal interval for the data exchange [../d3par#dt_coupling dt_coupling] is not explicitly set in case of runs with [../../app/examples/coupled coupled models] (e.g. atmosphere - ocean). ||
    2929||[=#PA0004 PA0004]   ||coupling mode "...": dt_coupling = ... is not equal to dt_coupling_remote = ...   || For coupled runs the temporal interval for the data exchange [../d3par#dt_coupling dt_coupling] must be explicitly set and must have the same value in both models ([../d3par#dt_coupling dt_coupling] has to be set in [../iofiles#PARIN PARIN] and [../iofiles#PARIN_O PARIN_O]). See also [../examples/coupled coupled runs]. ||