Changes between Version 131 and Version 132 of doc/app/errmsg

Timestamp:

Oct 19, 2012 8:29:21 AM (12 years ago)

Author:

maronga

Comment:

--

doc/app/errmsg

@@ -25 +25 @@
 ||='''Message identifier '''  =||='''Error message'''  =||='''Explanation'''  =||
 ||[=#PA0001 PA0001]   ||"host" is not set. Please check that environment variable "localhost" is set before running PALM  ||  ||
-||[=#PA0002 PA0002]   ||illegal coupling mode: ...   ||  ||
+||[=#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. ||
 ||[=#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). ||
 ||[=#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. ||