Changes between Version 11 and Version 12 of doc/app/examples/turbinf


Ignore:
Timestamp:
Apr 5, 2016 10:09:23 AM (9 years ago)
Author:
gronemeier
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • doc/app/examples/turbinf

    v11 v12  
    11= Setup for turbulent inflow =
    22
    3 Starting from version 3.5 PALM includes a so-called turbulence recycling method which allows a turbulent inflow with non-cyclic horizontal boundary conditions. The method follows the one described by Lund et al. (1998, J. Comp. Phys., '''140''', 233-258), modified by Kataoka and Mizuno (2002, Wind and Structures, '''5''', 379-392). The method is switched on by setting the initial parameter [../../inipar#turbulent_inflow turbulent_inflow] = ''.TRUE.''.\\\\
    4 The turbulent signal A'(y,z) to be imposed at the left inflow boundary is taken from the same simulation at a fixed distance x,,r,, from the inflow (given by parameter [../../inipar#recycling_width recycling_width]): A'(y,z) = A(x,,r,,,y,z) - '''A(z)''', where '''A(z)''' is the line average along y at x = x,,r,,. The turbulent quantity A'(y,z) is then added to a mean inflow profile a(z) which is the horizontal (and temporal) average as calculated from a precursor run. This is done after each timestep.\\\\
    5 '''So far (09/16/08), a turbulent signal is imposed to all prognostic variables except humidity (passive scalar) and salinity! '''\\\\
    6 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 calculated and taken from the precursor run.\\\\
     3Starting from version 3.5 PALM includes a so-called turbulence recycling method which allows a turbulent inflow with non-cyclic horizontal boundary conditions. The method follows the one described by Lund et al. (1998), modified by Kataoka and Mizuno (2002). The method is switched on by setting the initial parameter [../../inipar#turbulent_inflow turbulent_inflow] = ''.TRUE.''.
     4
     5The turbulent signal A'(y,z) to be imposed at the left inflow boundary is taken from the same simulation at a fixed distance x,,r,, from the inflow (given by parameter [../../inipar#recycling_width recycling_width]): A'(y,z) = A(x,,r,,,y,z) - '''A(x,,r,,,z)''', where '''A(x,,r,,,z)''' is the line average along y. The turbulent quantity A'(y,z) is then added to a mean inflow profile a(z) which is the horizontal (and temporal) average as calculated from a precursor run. This is done after each timestep.
     6
     7In 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 calculated and taken from the precursor run.
     8
     9'''So far, a turbulent inflow is realized from the left (west) side only (05/04/16)! '''
     10
    711The following tries to give a short recipe about how to create a proper setup for using the turbulence recycling method:
    812
    913  * A precursor run with cyclic horizontal boundary conditions has to be carried out in order to create a (quasi-) stationary state. Since the horizontal average from this precursor run is used as the mean inflow profile for the main run, '''the wall-normal velocity component must point into the domain at every grid point and its magnitude should be large enough in order to guarantee an inflow even if a turbulence signal is added.'''
    1014
    11   * The main run requires from the precursor run the mean profiles 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.
     15  * 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.
    1216
    1317  * In order to read the binary data from the precursor run, parameter [../../inipar#initializing_actions initializing_actions] = '' 'cyclic_fill' '' has to be set in the main run.
     
    1721  * Because of the Dirichlet condition at the inflow, the flow does not require any further driving force in general. An external pressure gradient or a geostrophic wind can be used, but should have the same value as for the precursor run. Otherwise, the horizontally diverging wind field will induce vertically descending or ascending motions. An application of volume flow conservation ([../../inipar#conserve_volume_flow conserve_volume_flow] = ''.TRUE.'') should be done with care, because it may have the same effects.
    1822
    19   * The main run allows to use a larger domain along x and y than in the precursor run.
     23  * The main run allows to use a larger domain along x and y than in the precursor run. Along z, however, both runs must be exactly the same.
    2024
    2125  * The distance between the inflow and the recycling plane should be large enough to allow for a sufficient advancement of the turbulent eddies (should be somehow correlated with the eddy turnover time). Otherwise, almost the same eddies will be recycled again and again, which will distort the turbulence statistics. Typically, the recycling width will be similar or equal to the domain size of the precursor run.
     26
     27The 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.
     28
     29=== References ===
     30
     31* '''Lund, T. S., X. Wu and K. D. Squires, 1998:''' Generation of turbulent inflow data for spatially-developing boundary layer simulations. ''J. Comput. Phys.'', '''140''', 233-258.
     32
     33* '''Kataoka, H. and M. Mizuno, 2002:''' Numerical flow computation around aeroelastic 3D square cylinder using inflow turbulence. ''Wind Struct.'', '''5''', 379-392.