Changes between Version 78 and Version 79 of doc/app/particle_parameters

Timestamp:

Sep 13, 2010 2:32:51 PM (14 years ago)

Author:

suehring

Comment:

--

doc/app/particle_parameters

@@ -149 +149 @@
 || npt*2  ||  variance of the number of particles with respect to the average number of particles per subdomain  ||                
 }}}
+|----------------
+{{{#!td style="vertical-align:top"
+[=#dt_min_part '''dt_min_part''']
+}}}
+{{{#!td style="vertical-align:top"
+R
+}}}
+{{{#!td style="vertical-align:top"
+0.0002
+}}}
+{{{#!td
+Minimum value for the particle timestep when SGS velocities are used (in s).\\
+For a further explanation see package parameter [../d3par#use_sgs_for_particles use_sgs_for_particles].
+}}}
+|----------------
+{{{#!td style="vertical-align:top"
+[=#dt_sort_particles '''dt_sort_particles''']
+}}}
+{{{#!td style="vertical-align:top"
+R
+}}}
+{{{#!td style="vertical-align:top"
+0.0
+}}}
+{{{#!td
+Temporal interval for sorting particles (in s).\\
+By default, particles are sorted in memory in a way that their order follows the order in which the gridpoint values are stored. This may improve cache coherence in case of larger numbers of particles and gridpoints. However, since the sorting itself is time consuming and since the requirement of sorting depends on the strength of mixing in the flow, performance can be improved if the sorting is applied only after certain time intervals. The proper length of this interval '''dt_sort_particles''' must be determined empirically by carrying out test runs with different intervals. Check file [../iofile#CPU_MEASURES CPU_MEASURES] to find the value of '''dt_sort_particles''' which gives the best performance.\\\
+Note:
+In case of [../inipar#cloud_droplets cloud_droplets] = '' '.T.' '', any given non-zero value of '''dt_sort_particles''' will be reset to zero and a corresponding warning message will appear in the job protocol.
+}}}
+
+
+
+
+
+
+
+
+
+
 
 Table row with nesting:\\