Changes between Version 25 and Version 26 of doc/app/par

Timestamp:

Feb 12, 2020 1:13:54 PM (5 years ago)

Author:

scharf

Comment:

--

doc/app/par

@@ -25 +25 @@
 The groups must be given in this order, the last groups, {{{&<module_name>_parameters}}} and {{{&user_parameters}}}, may be omitted. The namelist groups differ as follows:
 
-  * [../inipar initialization parameters] steer 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_actions], which must be given the value '' 'read_restart_data' '' for restart runs).
+  * [../initialization_parameters initialization parameters] steer 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 [../initialization_parameters#initializing_actions initializing_actions], which must be given the value '' 'read_restart_data' '' for restart runs).
        
   * [../d3par runtime parameters] generally steer 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 **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).