Changes between Version 12 and Version 13 of doc/app/stg_par

Timestamp:

Aug 25, 2020 6:06:17 AM (5 years ago)

Author:

raasch

Comment:

--

doc/app/stg_par

@@ -14 +14 @@
 |----------------
 {{{#!td style="vertical-align:top"
+[=#compute_velocity_seeds_local '''compute_velocity_seeds_local''']
+}}}
+{{{#!td style="vertical-align:top"
+L
+}}}
+{{{#!td style="vertical-align:top"
+.F.
+}}}
+{{{#!td
+Flag to control the computation of velocity seeds that are the basis of the imposed disturbances. 
+If .FALSE., the computation of the seeds at the boundary is 
+distributed to all processes along the respective 1D communicator. Subsequently, seeds are gathered on the respective boundary process.
+This option is especially useful for large length scales where the computational effort can become quite huge (it scales with the turbulent length scales), so that gain by parallelization exceeds the costs by the subsequent communication. 
+
+If .TRUE., velocity seeds are computed only locally and no communication is necessary. This performs better when the turbulent length scales are small and thus the loops are smaller. 
+}}}
+|----------------
+{{{#!td style="vertical-align:top"
 [=#dt_stg_adjust '''dt_stg_adjust''']
 }}}
@@ -20 +38 @@
 }}}
 {{{#!td style="vertical-align:top"
-1800
+1800.0
 }}}
 {{{#!td
@@ -53 +71 @@
 Using turbulence recycling ([../initialization_parameters#turbulent_inflow turbulent_inflow]=.T.) together with the synthetic turbulence generator is not allowed.
 }}}
-|----------------
-{{{#!td style="vertical-align:top"
-[=#compute_velocity_seeds_local '''compute_velocity_seeds_local''']
-}}}
-{{{#!td style="vertical-align:top"
-L
-}}}
-{{{#!td style="vertical-align:top"
-.F.
-}}}
-{{{#!td
-Flag to control the computation of velocity seeds that are the basis of the imposed disturbances. 
-If .FALSE., the computation of the seeds at the boundary is 
-distributed to all processes along the respective 1D communicator. Subsequently, seeds are gathered on the respective boundary process.
-This option is especially useful for large length scales where the computational effort can become quite huge (it scales with the turbulent length scales), so that gain by parallelization exceeds the costs by the subsequent communication. 
-
-If .TRUE., velocity seeds are computed only locally and no communication is necessary. This performs better when the turbulent length scales are small and thus the loops are smaller. 
-}}}