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

Timestamp:

Sep 1, 2020 10:14:06 AM (4 years ago)

Author:

eckhard

Comment:

fixed typos

doc/app/nesting_offl_parameters

@@ -2 +2 @@
 [[TracNav(doc/app/partoc|nocollapse)]]
 
-Since revision -r3347 a mesoscale nesting is available, which allows to nest a PALM domain within a mesoscale model. Therefore, time-dependent values for the three velocity components, potential temperature as well as the mixing ratio for the lateral and top boundaries of the PALM model domain are stored in the [../iofiles/pids#dynamic_input dynamic] input file and are read and mapped onto the respective arrays during the simulation. This way, it is possible to account for evolving synoptic conditions during the simulation without adding further tendency terms or to nudge the LES solution. Please note, the mesoscale is designed as an inter-model one-way offline nesting where the mesoscale simulation runs in advance. The mesoscale offline nesting needs to be distinguished from PALM's [../nesting_parameters self-nesting], which is designed as an two-way (one-way possible) model-coupling between PALM simulations during the time-integration.   
+Since revision -r3347 a mesoscale nesting is available, which allows to nest a PALM domain within a mesoscale model. Therefore, time-dependent values for the three velocity components, potential temperature as well as the mixing ratio for the lateral and top boundaries of the PALM model domain are stored in the [../iofiles/pids#dynamic_input dynamic] input file and are read and mapped onto the respective arrays during the simulation. This way, it is possible to account for evolving synoptic conditions during the simulation without adding further tendency terms or to nudge the LES solution. Please note, the mesoscale is designed as an inter-model one-way offline nesting where the mesoscale simulation runs in advance. The mesoscale offline nesting needs to be distinguished from PALM's [../nesting_parameters self-nesting], which is designed as a two-way (one-way possible) model coupling between PALM simulations during the time-integration.   
 
 For a detailed detailed technical description of the mesoscale offline nesting we refer to ''< replace with doi when available >''.
@@ -23 +23 @@
 Flag to enable the mesoscale offline nesting.  
 If set to ''.TRUE.'', lateral and top boundary data for the velocity components, potential temperature and mixing_ratio ([../initialization_parameters#humidity humidity]) are read from the dynamic input file (see [../iofiles#PIDS_DYNAMIC PIDS_DYNAMIC]). 
-Boundary data can be created with the preprocessor [wiki:doc/app/iofiles/inifor INIFOR], which is currently tailored towards the COSOM-model (other models will follow). 
+Boundary data can be created with the preprocessor [wiki:doc/app/iofiles/inifor INIFOR], which is currently tailored towards the COSMO-model (other models will follow). 
 Please note, offline nesting is only possible if a dynamic input file (see [../iofiles#PIDS_DYNAMIC PIDS_DYNAMIC]) is available. 
 
-Note, as the mesoscale model output does not contain turbulence, this need to be imposed at the lateral inflow boundaries by employing the synthetic turbulence generator (see [../stg_par#use_syn_turb_gen here]) to trigger the spatial development of the turbulent flow . 
+Note, as the mesoscale model output does not contain turbulence, it needs to be imposed at the lateral inflow boundaries by employing the synthetic turbulence generator (see [../stg_par#use_syn_turb_gen here]) to trigger the spatial development of the turbulent flow . 
 }}}