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

Timestamp:

Sep 16, 2010 1:04:23 PM (15 years ago)

Author:

witha

Comment:

--

doc/app/par

@@ -19 +19 @@
 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:
+The '''initialization''', '''run''' and '''package''' parameters differ as follows:
 
-    *
-
-      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 three-dimensional fields are initialized at the beginning of a model run (constant  value profiles or 1D-model-pre-run, the initial temperature profile etc.). These parameters apply to the total model 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 '''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 three-dimensional fields are initialized at the beginning of a model run (constant  value profiles or 1D-model-pre-run, the initial temperature profile etc.). These parameters apply to the total model 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 [../inipar#initializing_actions initializing_action], 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 can (and must) specify the time to be simulated. Run parameters only apply to the actual run (job) and with each restart run other values may be declared (if runs are restarted automatically, parameters will usually keep their values, provided that the NAMELIST input file was not changed by the user in the meantime).
+  * 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 can (and must) specify the time to be simulated. Run parameters only apply to the actual run (job) and with each restart run other values may be declared (if runs are restarted automatically, parameters will 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 .
+  * 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 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 user_parin in file user_interface.f90). Chapter 4.4.1 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 3.2) for the execution of a model test run.