Changes between Version 134 and Version 135 of doc/app/initialization_parameters


Ignore:
Timestamp:
Dec 3, 2010 12:38:13 PM (14 years ago)
Author:
raasch
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • doc/app/initialization_parameters

    v134 v135  
    633633In case of the leapfrog scheme a quite restrictive value of '''cfl_factor''' = ''0.1'' is used because for larger values the velocity divergence significantly effects the accuracy of the model results. Possibly larger values may be used with the leapfrog scheme but these are to be determined by appropriate test runs.\\\\
    634634The default value for the Euler scheme is '''cfl_factor''' = ''0.8.''
     635}}}
     636|----------------
     637{{{#!td style="vertical-align:top;width: 150px"
     638[=#collective_wait '''collective_wait''']
     639}}}
     640{{{#!td style="vertical-align:top;width: 50px"
     641L
     642}}}
     643{{{#!td style="vertical-align:top;width: 75px"
     644see right
     645}}}
     646{{{#!td
     647Set barriers in front of collective MPI operations.\\\\
     648Depending on the communication network in use, setting of barriers (MPI_BARRIER) in front of collective MPI operations (MPI_ALLTOALL, MPI_ALLREDUCE) may significantly speedup the code (about 10% on SGI-ICE-systems with Infiniband fat tree). Therefore, {{{collective_wait}}} is {{{.TRUE.}}} by default on SGI-systems (if hostname(3:5) = "{{{sgi}}}", given with '''mrun'''-option {{{-h}}}), but {{{.FALSE.}}} on all other systems.
    635649}}}
    636650|----------------