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

Timestamp:

Jun 17, 2019 8:38:39 AM (6 years ago)

Author:

Giersch

Comment:

--

doc/app/examples/turbinf

@@ -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 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''
+  * 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'', see also [../../iofiles#BINOUT BINOUT])''.
 
   * Set options for turbulent inflow in the parameter file of the main run
@@ -37 +37 @@
     A damping layer for the turbulence signal can be set at top of the domain via [../../inipar#inflow_damping_height inflow_damping_height] and [../../inipar#inflow_damping_width inflow_damping_width]. Inside the damping layer the turbulence signal is linearly damped to 0%. For [../../inipar#inflow_damping_height inflow_damping_height] the boundary layer height from the precursor run should be used.
 
-    The recycled turbulence, which is mapped from the recycling plane to the inflow boundary, can be shifted in y direction. This y-shift reduces persistent streaks that may occur within the recycling domain. To use the y-shift [../../inipar#recycling_yshift recycling_yshift] = .T. needs to be set. The distance of the y-shift is INT([../../d3par#npey npey] / 2), which is in most cases the best distance for effectively reducing streaks in the recycling domain.
+    The recycled turbulence, which is mapped from the recycling plane to the inflow boundary, can be shifted in y direction. This y-shift reduces persistent streaks that may occur within the recycling domain. To use the y-shift [../../inipar#recycling_yshift recycling_yshift] = .T. needs to be set. The distance of the y-shift is INT([../../d3par#npey npey] / 2), which is in most cases the best distance for effectively reducing streaks in the recycling domain. It might be also a good idea to reduce persistent streaks directly in the precursor run by using the parameter [../../inipar#y_shift y_shift]. 
 
   * When starting the main run, [wiki:doc/app/palmrun palmrun] must be told to provide the binary data of the restart run which is done by adding 'rec' to the activation-string list of the palmrun command (option {{{-a}}}, see job control with [wiki:doc/app/palmrun palmrun]).