Changes between Version 14 and Version 15 of doc/app/par

Timestamp:

Sep 16, 2010 4:27:48 PM (15 years ago)

Author:

witha

Comment:

--

doc/app/par

@@ -26 +26 @@
   * The '''[../d3par 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''' (see [../parpar particle parameters], [../sppar spectra Parameters] and [../dvrpar dvr parameters]) behave like '''run parameters'''. Package parameters determine the behavior of the additional (not user-defined) software packages.
+  * '''Package parameters''' (see [../sppar spectra Parameters] and [../dvrpar dvr parameters]) behave like '''run parameters'''. Package parameters determine the behavior of the additional (not user-defined) software packages.
 
+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}}} ([../userint/userpar see "Definition of user-defined parameters"]). 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]). [../examples/cbl Section "A minimum parameter set for the CBL"] shows a simple but complete example of the input file PARIN. This example file can be used together with the configuration file (described in [../configexample section "Example of a minimum 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.