Index: palm/trunk/DOC/app/chapter_4.0.html =================================================================== --- palm/trunk/DOC/app/chapter_4.0.html (revision 54) +++ palm/trunk/DOC/app/chapter_4.0.html (revision 62) @@ -1,22 +1,15 @@ - -
- -Before carrying out a model run, the user +
+Before carrying out a model
+run, the user
has to /determine/ a data set - the model parameters - e.g. how
many grid points are to be used, how large the horizontal and
@@ -26,8 +19,10 @@
should be, at which times and points plot output are supposed to be
made, etc.
-
These data are assigned with the help of -so-called ?NAMELIST-driven input? (FORTRAN - NAMELIST -input). The ?gewählten? values of the model parameters are written +
These data are
+assigned with the help of
+so-called ?“NAMELIST-driven input”? (FORTRAN -
+NAMELIST –
+input). The ?gewählten? values of the model parameters are
+written
into an ASCII file with fixed format, which is expected by the model as
an input
@@ -39,28 +34,29 @@
PARIN:
&inipar nx +
&inipar
+nx
= 79, ny = 79, nz = 40,
- dx = 50.0, dy = 50.0, dz =
+
+dx = 50.0, dy = 50.0, dz =
50.0,
- initializing_actions =
+
+initializing_actions =
"set_1d-model_profiles",
- prandtl_layer = .TRUE.,/
&d3par -end_time = 9000.0, section_xy = 1, 10, 20,/
-&packagename -var1 = .TRUE. /
-&userpar + +prandtl_layer = .TRUE.,/
&d3par +end_time = 9000.0, section_xy = 1, 10, 20,/
&packagename +var1 = .TRUE. /
&userpar
abcd = 1234,0,/
The parameters are separated into four +
The parameters
+are separated into four
different groups which all start with the so-called NAMELIST group
names.
-These are &inipar, &d3par and &packagename as well as &userpar. In each case a
+These are &inipar,
+&d3par
+and &packagename
+as well as &userpar.
+In each case a
group is terminated with one backslash ("/"). Between the beginning of
the line and the group name at least one blank has to be typed. Between
@@ -71,7 +67,7 @@
concerning the NAMELIST syntax, refer to
appropriate FORTRAN manuals.
-
Parameters belonging to the group inipar are first read by PALM. +
Parameters +belonging to the group inipar +are first read by PALM. These are the initialization parameters. Second, the so-called run parameters belonging to the group d3par @@ -82,19 +78,18 @@ group name of the respective package) as well as user-defined parameters -(group userpar). The four -groups must be given in this order, the last groups, packagename and userpar, may +(group userpar). +The four +groups must be given in this order, the last groups, packagename and +userpar, +may be omitted. If several software packages are selected (see chapter 3.7), -further NAMELIST groups may be inserted before the group userpar. -
-The initialization, run and +further NAMELIST groups may be inserted before the group userpar. +
The +initialization, run and package parameters differ as follows:
-The initialization -parameters are steering the basic settings of the model run. They +
The initialization
+parameters are steering the basic settings of the model run.
+They
define e.g. the number of the grid points, the numerical schemes to be
used, initial and boundary conditions to be applied, how the
@@ -104,16 +99,11 @@
run and thus can not be changed with restart runs! If one tries to
change these values within the NAMELIST input file of a restart run,
-then these changes are ignored (sole exception is the parameter initializing_actions, which must be given the
-value read_restart_data for restart runs).
-
The run
-parameters are generally steering actions to be carried out during
+then these changes are ignored (sole exception is the parameter initializing_actions, which
+must be given the
+value read_restart_data for restart
+runs).
+
The run
+parameters are generally steering actions to be carried out
+during
a model run. One can select for example, at which times plot output
should happen and which variables are to be written. Additionally one
@@ -123,22 +113,20 @@
usually keep their values, provided that the NAMELIST input file was
not changed by the user in the meantime).
-
Package parameters behave like - run parameters. Package parameters determine the behavior of -the additional (not user-defined) software packages .
-The user-defined parameters are assigned -by the user within the NAMELIST group name &userpar (see chapter -3.5.2). They steer actions programmed by the user. By default, +
Package parameters +behave like run parameters. Package parameters +determine the behavior of +the additional (not user-defined) software packages .
The user-defined
+parameters are assigned
+by the user within the NAMELIST group name &userpar
+(see chapter
+3.5.2). They steer actions programmed by the user. By
+default,
this group has only one parameter (region).
If the
user don't want to assign any values to the user-defined
-parameters, the group userpar
-may be omitted. The group name &userpar
+parameters, the group
+userpar
+may be omitted. The group name &userpar
can be changed by the user in the user-defined code. In
addition to this, further NAMELIST groups may also be declared (all
@@ -146,5 +134,6 @@
in file user_interface.f90).
Chapter
-4.4 shows a simple but complete example of the input file PARIN.
+4.4 shows a simple but complete example of the input file
+PARIN.
This example file can be used together with the configuration file
(described in chapter
@@ -156,18 +145,8 @@
explanation are described in the lists of the following subsections.
+
- Last change: 15/04/05
-(SR)
-