Changes between Version 18 and Version 19 of doc/app/examples/turbinf

Timestamp:

Jun 17, 2019 8:18:01 AM (6 years ago)

Author:

Giersch

Comment:

--

doc/app/examples/turbinf

@@ -7 +7 @@
 In order to avoid a continous growth of the turbulent layer with time, the height up to which turbulence is recycled is limited by parameter [../../inipar#inflow_damping_height inflow_damping_height]. By default, this height is equal to the the height of the boundary layer z_i calculated by the precursor run. In the case of a strictly neutral flow you have to set the parameter [../../inipar#inflow_damping_height inflow_damping_height] because the value of z_i calculated by the precursor run is zero.   
 
-'''So far, a turbulent inflow is realized from the left (west) side only (2016/04/05)! '''
+'''So far, a turbulent inflow is realized from the left (west) side only (2019/06/17)! '''
 
 The following tries to give a short recipe about how to create a proper setup for using the turbulence recycling method:
@@ -19 +19 @@
     The main run requires the mean profiles from the precursor run to be used at the inflow. For this, the horizontally and temporally averaged mean profiles as provided with the standard PALM output are used. The user has to set parameters [../../d3par#dt_dopr dt_dopr], [../../d3par#averaging_interval averaging_interval], etc. for the precursor run appropriately, so that an output is done '''at the end''' of the precursor run. The profile information is then contained in the restart (binary) file created at the end of the precursor run and can be used by the main run. '''It is very important that the mean profiles at the end of the precursor run are in a stationary or quasi-stationary state''', because otherwise it may not be justified to use them as constant profiles at the inflow. '''Also, turbulence at the end of the precursor run should be fully developed.''' Otherwise, the main run would need an additional spinup-time at the beginning to get the turbulence to its final stage.
 
-  * The restart data of the precursor run must be made available for the main run. The user has to copy/link/rename the restart data of the precursor run manually as they would be restart data of the main run, so that Palm can find the restart data during the main run. Usually, this is done by creating a directory next to your output directory named ''RESTART/<name_of_main_run>_d3d'' and rename/copy/link the directory, where the restart data of the precursor run are saved (this directory is named via [../../jobcontrol#fast_io_catalog tmp_data_catalog] in .palm.config.<configuration identifier>), to ''<name_of_main_run>_d3d''
+  * The restart data of the precursor run must be made available for the main run. The user has to copy/link/rename the restart data of the precursor run manually as they would be restart data of the main run, so that PALM can find the restart data during the main run. Usually, this is done by creating your restart input directory [../../iofiles#BININ BININ] (named ''<name_of_main_run>_d3d/RESTART'') and copy/link the directory, where the restart data of the precursor run are saved (this directory is named via [wiki:doc/app/palm_config#fa_io fast_io_catalog] in .palm.config.<configuration identifier>), to ''<name_of_precursor_run>_d3d/RESTART''
 
   * Set options for turbulent inflow in the parameter file of the main run