Changes between Version 1 and Version 2 of doc/app/par

Timestamp:

Sep 16, 2010 1:00:46 PM (15 years ago)

Author:

witha

Comment:

--

doc/app/par

@@ -2 +2 @@
 
 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 vertical grid spacing should be, which kind of boundary conditions are to be used for the individual variables, which numerical schemes implemented in the model are to be used, how long the simulated time 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 chosen values of the model parameters are written into an ASCII file with fixed format, which is expected by the model as an input file under the local name [../iofiles#PARIN PARIN]. On this file the parameters are represented by their variable names they have in the model. These parameters can be assigned one or more values, depending on the type and size the variable has. The following example shows the format of the file [../iofiles#PARIN PARIN]:
-
+These data are assigned with the help of so-called "''NAMELIST-driven input''" (FORTRAN - NAMELIST – input). The chosen values of the model parameters are written into an ASCII file with fixed format, which is expected by the model as an input file under the local name [../iofiles#PARIN PARIN]. On this file the parameters are represented by their variable names they have in the model. These parameters can be assigned one or more values, depending on the type and size the variable has. The following example shows the format of the file [../iofiles#PARIN PARIN]:\\\\
 {{{
       &inipar nx = 79, ny = 79, nz = 40,
@@ -16 +15 @@
       &userpar abcd = 1234,0,/
 }}}
-
-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 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 the group names and the "/", the values are assigned to the variables. The example shows that in principle all FORTRAN data types are allowed. For more details concerning the NAMELIST syntax, refer to appropriate FORTRAN manuals.
-
-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 are read in, then the parameters for steering the optional software packages (group packagename, the string "packagename" must be replaced by the NAMELIST 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 be omitted. If several software packages are selected (see chapter 3.7), further NAMELIST groups may be inserted before the group userpar.
+\\
+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 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 the group names and the "/", the values are assigned to the variables. The example shows that in principle all FORTRAN data types are allowed. For more details concerning the NAMELIST syntax, refer to appropriate FORTRAN manuals.\\\\
+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}}} are read in, then the parameters for steering the optional software packages (group {{{packagename}}}, the string "{{{packagename}}}" must be replaced by the NAMELIST 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 be omitted. If several software packages are selected ([../packages see "Optional software packages"]), further NAMELIST groups may be inserted before the group {{{userpar}}}.
 
 The initialization, run and package parameters differ as follows: