Changes between Version 19 and Version 20 of doc/app/par

Timestamp:

Mar 26, 2018 9:58:56 PM (7 years ago)

Author:

maronga

Comment:

--

doc/app/par

@@ -5 +5 @@
 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,
-              dx = 50.0, dy = 50.0, dz = 50.0,
-              initializing_actions = "set_1d-model_profiles",
-              constant_flux_layer = .TRUE.,/
+      &initialization_parameters nx = 79, ny = 79, nz = 40,
+                                 dx = 50.0, dy = 50.0, dz = 50.0,
+                                 initializing_actions = "set_1d-model_profiles",
+                                 constant_flux_layer = .TRUE.,/
 
-      &d3par  end_time = 9000.0, section_xy = 1, 10, 20,/
+      &runtime_parameters  end_time = 9000.0, section_xy = 1, 10, 20,/
 
-      &packagename var1 = .TRUE. /
+      &packagename_parameters var1 = .TRUE. /
 
-      &userpar abcd = 1234,0,/
+      &user_parameters 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.\\\\
+The parameters are separated into four different groups which all start with the so-called NAMELIST group names. These are {{{&initialization_parameters}}}, {{{&runtime_parameters}}} and {{{&packagename_parameters}}} as well as {{{&user_parameters}}}. 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 [../packages software packages] are selected, further NAMELIST groups may be inserted before the group {{{userpar}}}.
 
@@ -29 +29 @@
 
 Starting from version 3.2, the {{{particles-package}}} is part of the default model, so it does not have to be switched on using '''mrun'''-option {{{-p}}}. However, the respective parameters have still to be set by using the NAMELIST group [../parpar particles_par].\\\\
-The user-defined parameters are assigned by the user within the NAMELIST group name {{{&userpar}}} (see [../userint/userpar here]). They steer actions programmed by the user. By default, this group has only one parameter ([../userpar#region 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}}} can be changed by the user in the user-defined code. In addition to this, further NAMELIST groups may also be declared (all within routine [source:palm/trunk/SOURCE/user_parin.f90 user_parin]). A simple but complete example of the input file PARIN can be found [../examples/cbl here]. This example file can be used together with the [../configexample configuration file] for the execution of a model test run.\\\\
+The user-defined parameters are assigned by the user within the NAMELIST group name {{{&user_parameters}}} (see [../userint/userpar here]). They steer actions programmed by the user. By default, this group has only one parameter ([../userpar#region 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 {{{&user_parameters}}} can be changed by the user in the user-defined code. In addition to this, further NAMELIST groups may also be declared (all within routine [source:palm/trunk/SOURCE/user_parin.f90 user_parin]). A simple but complete example of the input file PARIN can be found [../examples/cbl here]. This example file can be used together with the [../configexample configuration file] for the execution of a model test run.\\\\
 PALM assigns default values to nearly all parameters. They become effective if no other assignments are given in the parameter file. These default values as well as the parameter name, type and its explanation are described in the lists of the following subsections.