Changes between Version 14 and Version 15 of doc/app/examples/turbinf
- Timestamp:
- Nov 20, 2018 4:51:36 PM (7 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TabularUnified doc/app/examples/turbinf
v14 v15 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. 20 20 21 * 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 (th s directory is named via [../../jobcontrol#tmp_data_catalog tmp_data_catalog] in .mrun.config), to ''<name_of_main_run>_d3d''21 * 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'' 22 22 23 23 * Set options for turbulent inflow in the parameter file of the main run … … 39 39 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. 40 40 41 * When starting the main run, mrun must be told to provide the binary data of the restart run. For this, first the list of input-files in ''.mrun.config'' must be modified. In line41 * When starting the main run, [wiki:doc/app/palmrun palmrun] must be told to provide the binary data of the restart run. For this, first the list of input-files in ''.palm.iofiles'' must be modified. In line 42 42 {{{ 43 43 BININ in:loc:flpe d3f $base_data/$fname/RESTART _d3d … … 47 47 BININ in:loc:flpe d3f:cycfill $base_data/$fname/RESTART _d3d 48 48 }}} 49 This flag has to be added to the run control list of the mrun command (option {{{-r}}}, [../../jobcontrol#r see job control withmrun]) when starting the main run as well.49 This flag has to be added to the run control list of the palmrun command (option {{{-a}}}, see job control with [wiki:doc/app/palmrun palmrun]) when starting the main run as well. 50 50 51 51 === References ===