Changes between Version 301 and Version 302 of doc/app/errmsg


Ignore:
Timestamp:
Jun 6, 2017 3:43:51 PM (8 years ago)
Author:
sward
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • doc/app/errmsg

    v301 v302  
    646646||[=#PA0418 PA0418]   ||illegal nesting datatransfer mode: ... ||See parameter [../nestpar#nesting_datatransfer_mode nesting_datatransfer_mode] for allowed values, and check your parameter file. ||
    647647||[=#PA0419 PA0419]   ||mismatch between root model and client settings \\ <parameter name>(root) = ... \\ <parameter name>(client) = ... \\ client value is set to root value ||The displayed parameter has been assigned different values for the root domain and a client domain (the id of the client domain is listed in the first line of the message) but it must have the same value for all domains. PALM automatically adjusts the client domain value to the one given for the root domain. In order to get rid of this warning message, adjust the parameter in the respective NAMELIST-parameter file of the client (or root) domain.||
    648 ||[=#PA0420 PA0420]   ||unknown collision algorithm: collision_algorithm = ... || The only allowed collision algorithms are 'all_or_nothing' and 'average_impact'. Make sure the spelling is correct. ||
     648||[=#PA0420 PA0420]   ||unknown collision algorithm: collision_algorithm = ... || The allowed values of [../parpar#collision_algrithm collision_algorithm]  are 'all_or_nothing' and 'average_impact'. ||
    649649||[=#PA0421 PA0421]   ||recycling_yshift = .T. requires more than one processor in y direction|| The distance of the y-shift is calculated by INT( npey / 2 ). With only one processor in y direction, no y-shift is possible. ||
    650650||[=#PA0422 PA0422]   ||data_output_pr = ... is not available for cloud_scheme = saturation_adjust || If the output is not necessary, delete the variable from the namelist. If it is necessary, use [../inipar#cloud_scheme cloud_scheme] = kessler or  seifert_beheng. ||