Changes between Version 153 and Version 154 of doc/app/errmsg


Ignore:
Timestamp:
Mar 18, 2014 10:36:09 AM (11 years ago)
Author:
raasch
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • doc/app/errmsg

    v153 v154  
    2424}}}
    2525||='''Message identifier '''  =||='''Error message'''  =||='''Explanation'''  =||
    26 ||[=#PA0001 PA0001]   ||"host" is not set. Please check that environment variable "localhost" is set before running PALM  || ||
    27 ||[=#PA0002 PA0002]   ||illegal coupling mode: ...   || A atmosphere-ocean coupling is implemented in palm. The internal variable {{{coupling_mode}}} gives information about the current model setup. It is internally set to "{{{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 suggests that the initialization of the coupling did fail. Possible reasons might be trying a coupling between two atmospere runs (or two ocean runs), or problems with the {{{mrun}}} script. ||
    28 ||[=#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 explicitely set in case of runs with [../../app/examples/coupled coupled models] (e.g. atmosphere - ocean). ||
    29 ||[=#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 explicitely set and equal in both models. ||
     26||[=#PA0001 PA0001]   ||"host" is not set. Please check that environment variable "localhost" is set before running PALM  || By default, PALM gets the "host" value from reading the NAMELIST {{{envpar}}}, which is automatically provided in a local file named {{{ENVPAR}}}, if PALM is run with scripts {{{mrun}}} or {{{palm_simple_run}}}. You may check the contents of file ENVPAR (e.g. by running {{{mrun}}} with option {{{-B}}} (preventing that the temporary working directory containing this file is automatically deleted when {{{mrun}}} is finished), or submit a [/newticket trouble ticket]. ||
     27||[=#PA0002 PA0002]   ||illegal coupling mode: ...   || This message is related to the atmosphere-ocean coupling 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 {{{mrun}}} script. ||
     28||[=#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). ||
     29||[=#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. ||
    3030||[=#PA0005 PA0005]   ||coupling mode "...": dt_coupling <= 0.0 is not allowed and is reset to MAX(dt_max(A,O)) = ...   || This error occurs if an invalid value for [../d3par#dt_coupling dt_coupling] is used in the parameter file. [../d3par#dt_coupling dt_coupling] must be > 0.0 and equal in both models. ||
    3131||[=#PA0006 PA0006]   ||coupling mode "...": restart_time = ... is not equal to restart_time_remote = ...         || [../d3par#restart_time restart_time] has not been set properly (equal) in the atmosphere and ocean parameter file. See also [../examples/coupled coupled runs]. ||
     
    3333||[=#PA0008 PA0008]   ||coupling mode "...": simulation_time_since_reference = ... is not equal to simulation_time_since_reference_remote = ...   || The simulated time is stored internally in the variable {{{simulation_time_since_reference}}}. In coupled mode both times must be equal. This error might occur when precursor runs are used with different startup times and the coupling is initiated inappropiately. See [../examples/coupled coupled runs] for a detailed description of the setup for precursor runs. ||
    3434||[=#PA0009 PA0009]   ||dx in atmosphere is not larger or equal than dx in ocean||Coupled runs allow to use different grid resolutions in atmosphere and ocean. It is, however, not possible to use a finer grid resolution in the atmosphere than in the ocean. ||
    35 ||[=#PA0010 PA0010]   ||Domain size in x-direction is not equal in ocean and atmosphere|| Coupled runs are only possible, if the horizontal model domain size is equal in both, atmosphere and ocean. Have a look at the settings for [../inipar#dx dx], [../inipar#dy dy], [../inipar#nx nx] and .[./inipar#ny ny] to avoid this error. ||
    36 ||[=#PA0011 PA0011]   ||dy in atmosphere is not larger or equal than dy in ocean||Coupled runs allow to use different grid resolutions in atmosphere and ocean. It is, however, not possible to use a finer grid resolution in the atmosphere than in the ocean.||
     35||[=#PA0010 PA0010]   ||Domain size in x-direction is not equal in ocean and atmosphere|| Coupled runs are only possible, if the horizontal model domain size is equal in both, atmosphere and ocean. Check the settings for [../inipar#dx dx], [../inipar#dy dy], [../inipar#nx nx] and [../inipar#ny ny] to avoid this error. ||
     36||[=#PA0011 PA0011]   ||dy in atmosphere is not larger or equal than dy in ocean||Coupled runs allow to use different grid resolutions in atmosphere and ocean. However, it is not allowed to use a finer grid resolution in the atmosphere than in the ocean.||
    3737||[=#PA0012 PA0012]   ||Domain size in y-direction is not equal in ocean and atmosphere ||Coupled runs are only possible, if the horizontal model domain size is equal in both, atmosphere and ocean. Have a look at the settings for [../inipar#dx dx], [../inipar#dy dy], [../inipar#nx nx] and .[./inipar#ny ny] to avoid this error. ||
    38 ||[=#PA0013 PA0013]   ||illegal value given for loop_optimization: "..."   ||  ||
    39 ||[=#PA0014 PA0014]   ||a non-flat topography does not allow ...   ||  ||
    40 ||[=#PA0015 PA0015]   ||ocean = .T. does not allow ...   ||  ||
    41 ||[=#PA0016 PA0016]   ||unknown solver for perturbation pressure: psolver = "..."   || Siggi ||
     38||[=#PA0013 PA0013]   ||illegal value given for loop_optimization: "..."   ||See [../inipar#loop_optimization loop_optimization] for allowed values, and check your parameter file. ||
     39||[=#PA0014 PA0014]   ||a non-flat topography does not allow ...   ||There are several features which do not work together with a non-flat topography. See parameter [../inipar#topography topography] for possible restrictions and appropriately modify your parameter file. ||
     40||[=#PA0015 PA0015]   ||ocean = .T. does not allow ...   ||There are several features which do not work within PALM's ocean mode. See parameter [../inipar#ocean ocean] for possible restrictions and appropriately modify your parameter file.  ||
     41||[=#PA0016 PA0016]   ||unknown solver for perturbation pressure: psolver = "..."   || ||
    4242||[=#PA0017 PA0017]   ||Vertical grid stretching is not allowed together with particle advection.  || With the currently implemented spatial interpolation of flow quantities on the respective particle positions, a constant vertical grid spacing must be used. ||
    4343||[=#PA0018 PA0018]   ||ros_count > 5 in Rosenbrock method  || The Rosenbrock method is used when curvature and solution effects are included in the calculation of cloud droplet growth due to condensation (see [../inipar#curvature_solution_effects curvature_solution effects]). This algorithm may lead to unreasonable results if the external conditions, especially the supersaturation, significantly changes between two PALM time steps. In that case the algorithm will be carried out again with an smaller internal time step. The limits which decide weather a result is reasonable or not are only tested for a certain range of relative humidities and for cloud droplet sizes. If this error appears the result after 5 recalculations of the Rosenbrock algorithm is still regarded as unreasonable. Thus the limiting values may not be suitable for the current conditions and need further adjustments. ||