Changeset 116 for palm/trunk/DOC/app/chapter_4.2.html
- Timestamp:
- Oct 11, 2007 2:30:27 AM (17 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
palm/trunk/DOC/app/chapter_4.2.html
r108 r116 1 1 <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> 2 <html> 3 <head> 2 <html><head> 4 3 5 4 … … 12 11 13 12 14 <title>PALM chapter 4.2</title> 15 </head> 16 13 <title>PALM chapter 4.2</title></head> 17 14 18 15 <body> … … 8686 8683 8687 8684 8688 <tr> 8685 <tr><td style="vertical-align: top;"><span style="font-weight: bold;"><a name="dt_sort_particles"></a>dt_sort_particles</span></td><td style="vertical-align: top;">R</td><td style="vertical-align: top;"><span style="font-style: italic;">0.0</span></td><td style="vertical-align: top;">Temporal interval for sorting particles (in s).<br><br>By 8686 default, particles are sorted in memory in a way that their order 8687 follows the order in which the gridpoint values are stored. This may 8688 improve cache coherence in case of larger numbers of particles and 8689 gridpoints. However, since the sorting itself is time consuming and 8690 since the requirement of sorting depends on the strength of mixing in 8691 the flow, performance can be improved if the sorting is applied only 8692 after certain time intervals. The proper length of this interval <span style="font-weight: bold;">dt_sort_particles</span> must be determined empirically by carrying out test runs with different intervals. Check file <a href="chapter_3.4.html#CPU_MEASURES">CPU_MEASURES</a> to find the value of <span style="font-weight: bold;">dt_sort_particles</span> which gives the best performance.<br><br><span style="font-weight: bold;">Note:</span><br>In case of <a href="chapter_4.1.html#cloud_droplets">cloud_droplets</a> = <span style="font-style: italic;">.T.</span>, any given non-zero value of <span style="font-weight: bold;">dt_sort_particles</span> will be reset to zero and a corresponding warning message will appear in the job protocol.</td></tr><tr> 8689 8693 8690 8694 … … 11590 11594 11591 11595 11592 </body> 11593 </html> 11596 </body></html>
Note: See TracChangeset
for help on using the changeset viewer.