Bug in Thompson Scheme (Posted 11/21/05) (Corrected
in 2.1.2)
Problem: The Thompson scheme has an important fix for an error in the rain/snow accretion rates for version 2.1.1. The new module will also fix a minor error in version 2.1.
Solution: To correct the problem, you can download a new version of the routine, module_mp_thompson.F_fix, and replace the one in phys/ directory. Recompile.
Missing cumulus ice and snow tendencies (Posted 11/16/05) (Corrected
in 2.1.2)
Problem: Cumulus ice and snow
tendency terms have been missing since 2.1. This affects all cumulus
schemes that output ice and/or snow tendencies (i.e. all except
BMJ).
Solution: There is a one addition
to dyn_em/solve_em.F to correct the problem. You can download
the routine, solve_em.F.fix_211,
and replace the one in dyn_em/ directory. Recompile. The correction
will produce significant more high cloud in convective regions.
Long Compile Time on SGI Altix: (Posted 11/8/05)
Problem: The Intel ifort compiler
spends a long time compiling the following files:
module_ra_gfdleta.f
module_advect_em.f
mediation_force_domain.f
solve_em.f
wrf_inputout.f
module_configure.f
ndown_em.f
module_big_step_utilities_em.f
module_diffusion_em.f
Partial Solution: You can reduce
the compile time by adding the following compiler option:
-mP3OPT_ecg_lra_switch=T
This does impact the performance of the module/routines
that have this optimization removed - they slow down. If "speed
of compile" is more important that total run time (such as
for development work), this is not a bad option to include for
all files. If "total runtime" is important, then the
user should accept the slow compiles. A reasonable compromise
isto only modify the above files with the new compiler option.
The Intel group plans to have a fix for the
ifort compiler soon. (Thanks to Gerardo Cisneros of SGI.)
Using RSL for Nesting on Linux (posted on 11/8/05):
Problem: The Linux systems
with the PGI compiler, when using RSL for a nested run, incorrectly
interpolate fields within the SINT subroutine for some variables,
for some decomposition configurations (for example, using 10 processors
to run). The most identifiable symptom is that the topography
field of the nest at the initial time shows characteristic lines
along the decomposition boundaries.
Solution: Use RSL_LITE as the
communication layer instead of RSL.
As long as there is not a need for periodic
boundaries in the y-direction, the use of RSL_LITE is transparent
to the user (with the added benefits of 1) allowing larger domains,
2) decomposition of more processors, and 3) running faster).
Use of SST Update Option (posted on 11/8/05)
(Corrected in 2.1.2)
Problem: The SST lower boundary
file does not get updated correctly when doing a restart. After
a restart, the first time period of the lower boundary file is
always used as input.
Solution: Run real.exe again,
and start from the restart time.
Problem: If one uses SST update
option for a nested run, the SST data in the nest won't interpolated
from the coarse domain.
Solution: Run SI for the nest
for all time periods the cover the simulation time, and then run
real.exe for the nest domain to produce nest input file for SST.
(Some modification to the SI source code is needed to process
all nest times.)
RSL_LITE:
Problem: Does not yet work
for periodic boundary condition in y-direction.
