Chapter 8: MM5

 

 

8.1 Purpose

 

 

8.2 Basic Equations of MM5

 

In terms of terrain following coordinates (x, y, σ ), these are the equations for the nonhydrostatic model's basic variables excluding moisture.

 

Pressure

 

       

(8.1)

 

 

 

Momentum (x-component)

 

       

(8.2)

 

 

Momentum (y-component)

 

       

(8.3)

 

 

Momentum (z-component)

 

       

(8.4)

 

 

Thermodynamics

 

       

(8.5)

 

 

Advection terms can be expanded as

 

       

(8.6)

 

where

 

       

(8.7)

 

 

Divergence term can be expanded as

 

       

(8.8)

 

Notes about the equations:

  • Appendix A shows derivations of Equations 8.1, 8.4, 8.5 and 8.7, and shows the coordinate transformation from z to sigma coordinates. 
  • In the model, Equation 8.1 does not include the last term with parentheses on the right. This is neglected and it represents a pressure increase due to heating which forces the air to expand. 
  • Equations 8.2-8.4 include terms (eu and ew) representing the usually neglected component of the Coriolis force, where
  • , λ is latitude, φ is longitude, and φc is central longitude. 
  • The
  • and rearth terms represent curvature effects, and m is map-scale factor.
  • Equations 8.2, 8.3 and 8.8 include terms to account for the sloped sigma surfaces when calculating horizontal gradients. 
  • Prognostic equations also exist for water vapor and microphysical variables such as cloud and precipitation (if used). These include the advection and various source/sink terms. 

Spatial finite differencing -

The above equations are finite differenced on the B grid mentioned in Chapter 1. Second-order centered finite differences represent the gradients except for the precipitation fall term which uses a first-order upstream scheme for positive definiteness. Often horizontal averaging is required to determine the gradient in the correct position. Vertical interpolations allow for the variable vertical grid size. More details are in Grell et al. (1994), NCAR Tech. Note 398.

 

Temporal finite differencing -

A second-order leapfrog time-step scheme is used for these equations, but some terms are handled using a time-splitting scheme. Note that Equations 8.1-8.4 contain extra terms on the left of the equals sign. This designates so-called fast terms that are responsible for sound waves that have to be calculated on a shorter time step. In the leapfrog scheme, the tendencies at time n are used to step the variables from time n-1 to n+1. This is used for most of the right-hand terms (advection, coriolis, buoyancy). A forward step is used for diffusion and microphysics where the tendencies are calculated at time n-1 and used to step the variables from n-1 to n+1. Some radiation and cumulus options use a constant tendency over periods of many model timesteps and are only recalculated every 30 minutes or so.

 

However for certain terms the model timestep is too long for stability and these have to be predicted with a shorter step. Examples of this are the sound-wave terms shown in the equations, the precipitation fall term and the PBL tendencies which also may be split in certain situations. When the timestep is split, certain variables and tendencies are updated more frequently. For sound waves u, v, w and p′ all need to be updated each short step using the tendency terms on the left of 8.1-8.4 while the terms on the right are kept fixed. For sound waves there are usually four of these steps between n-1 and n+1, after which u, v, w and p′ are up to date.

 

Certain processes are treated implicitly for numerical stability. An implicit time scheme is one in which the tendencies of variables depend not only on the present and past values, but also the future values. These schemes are often numerically stable for all timesteps, but usually require a matrix inversion to implement them. In MM5 implicit schemes are used only in 1-d column calculations for vertical sound waves and vertical diffusion, so that the matrix is tridiagonal making it straightforward to solve directly.

 

 

 

 

 

 

 

 

 

8.3 Physics Options in MM5

 

8.3.1 Cumulus Parameterizations (ICUPA)
 

1. None -

Use no cumulus parametrization at grid sizes < 5-10 km.

 

 
2. Anthes-Kuo -

Based on moisture convergence, mostly applicable to larger grid sizes > 30 km. Tends to produce much convective rainfall, less resolved-scale precip, specified heating profile, moistening dependent upon relative humidity.

 
3. Grell -

Based on rate of destabilization or quasi-equilibrium, simple single-cloud scheme with updraft and downdraft fluxes and compensating motion determining heating/moistening profile. Useful for smaller grid sizes 10-30 km, tends to allow a balance between resolved scale rainfall and convective rainfall. Shear effects on precipitation efficiency are considered. See Grell et al. (1994).

 
4. Arakawa-Schubert -

Multi-cloud scheme that is otherwise likeGrell scheme. Based on a cloud population, allowing for entrainment into updrafts and allows for downdrafts. Suitable for larger scales, > 30 km grid sizes, possibly expensive compared to other schemes. Shear effects on precipitation efficiency are considered. Also see Grell et al. (1994).

 
5. Fritsch-Chappell -

Based on relaxation to a profile due to updraft, downdraft and subsidence region properties. The convective mass flux removes 50% of available buoyant energy in the relaxation time. Fixed entrainment rate. Suitable for 20-30 km scales due to single-cloud assumption and local subsidence. See Fritsch and Chappell (1980) for details. This scheme predicts both updraft and downdraft properties and also detrains cloud and precipitation. Shear effects on precipitation efficiency are also considered.

 
6. Kain-Fritsch -

Similar to Fritsch-Chappell, but using a sophisticated cloud-mixing scheme to determine entrainment/detrainment, and removing all available buoyant energy in the relaxation time. See Kain and Fritsch (1993) for details. This scheme predicts both updraft and downdraft properties and also detrains cloud and precipitation. Shear effects on precipitation efficiency are also considered.

 
7. Betts-Miller -

Based on relaxation adjustment to a reference post-convective thermodynamic profile over a given period. This scheme is suitable for > 30 km, but no explicit downdraft, so may not be suitable for severe convection. See Betts (1986), Betts and Miller (1986), Betts and Miller (1993) and Janjic (1994) for details.

 
8. Kain-Fritsch 2 -

A new version of Kain-Fritsch that includes shallow convection. This is similar to one that is being run in test mode in the Eta model (Kain 2002).

 

Shallow Cumulus - (ISHALLO=1)

Handles non-precipitating clouds. Assumed to have strong entrainment and small radius, no downdrafts, and uniform clouds. Based on Grell and Arakawa-Schubert schemes. Equilibrium assumption between cloud strength and sub-grid (PBL) forcing.

 

 

8.3.2 PBL Schemes (IBLTYP) and Diffusion
 
0. None -

No surface layer, unrealistic in real-data simulations.

 
1. Bulk PBL -

Suitable for coarse vertical resolution in boundary layer, e.g. > 250 m vertical grid sizes. Two stability regimes.

 
2. High-resolution Blackadar PBL -

Suitable for high resolution PBL, e.g. 5 layers in lowest km, surface layer < 100 m thick. Four stability regimes, including free convective mixed layer. Uses split time steps for stability.

 
3. Burk-Thompson PBL -

Suitable for coarse and high-resolution PBL. Predicts turbulent kinetic energy for use in vertical mixing, based on Mellor-Yamada formulas. See Burk and Thompson (1989) for details. This is the only PBL option that does not call the SLAB scheme, as it has its own force-restore ground temperature prediction

 
4. Eta PBL -

This is the Mellor-Yamada scheme as used in the Eta model, Janjic (1990, MWR) and Janjic (1994, MWR). It predicts TKE and has local vertical mixing. The scheme calls the SLAB routine or the LSM for surface temperature and has to use ISOIL=1 or 2 (not 0) because of its long time step. Its cost is between the MRFPBL and HIRPBL schemes. Before SLAB or the LSM the scheme calculates exchange coefficients using similarity theory, and after SLAB/LSM it calculates vertical fluxes with an implicit diffusion scheme.

 

 

 
5. MRF PBL -

or Hong-Pan PBL, suitable for high-resolution in PBL (as for Blackadar scheme). Efficient scheme based on Troen-Mahrt representation of countergradient term and K profile in the well mixed PBL, as implemented in the NCEP MRF model. See Hong and Pan (1996) for details. This scheme either calls the SLAB routine or the LSM and should have ISOIL=1 or 2. Vertical diffusion uses an implicit scheme to allow longer time steps.

 
6. Gayno-Seaman PBL -

This is also based on Mellor-Yamada TKE prediction. It is distinguished from others by the use of liquid-water potential temperature as a conserved variable, allowing the PBL to operate more accurately in saturated conditions (Ballard et al., 1991; Shafran et al. 2000). Its cost is comparable with the Blackadar scheme's because it uses split time steps.

 
7. Pleim-Chang PBL -

This scheme only works with ISOIL=3 (see later). The PBL scheme is a derivative of the Blackadar PBL scheme called the Asymmetric Convective Model (Pleim and Chang, 1992, Atm. Env.), using a variation on Blackadar's non-local vertical mixing.

 
Moist vertical diffusion - (IMVDIF=1)

IBLTYP = 2, 5 and 7 have this option. It allows diffusion in cloudy air to mix toward a moist adiabat by basing its mixing on moist stability instead of the dry stability. From Version 3.5 it can mix cloudy air upwards into clear air in addition to just internally in cloudy layers.

 
Thermal roughness length - (IZ0TOPT=0,1,2)

IBLTYP =2 and 5 have the option of using a different roughness length for heat/moisture than that used for momentum. This is the thermal roughness length. IZ0TOPT=0 is the default (old) scheme, IZ0TOPT=1 is the Garratt formulation, and IZ0TOPT=2 is the Zilitinkevich formulation (used by the Eta model). Changing the thermal roughness length affects the partitioning of sensible and latent heat fluxes, and affects the total flux over water.

 
Horizontal diffusion - (ITPDIF=0,1,2)

ITPDIF=0,1 are two methods of doing horizontal temperature diffusion. ITPDIF=1 (default) is to only horizontally diffuse the perturbation from the base-state temperature. This partially offsets the effect of the coordinate slope over topography which is needed due to the fact that the diffusion is along model levels. ITPDIF=0 diffuses the full temperature (like all other fields) instead. In Version 3.7, a new option is ITPDIF=2. This applies to temperature, moisture and cloud water, and is a purely horizontal diffusion accounting more accurately for coordinate slope and valley walls (Zangl, 2002 MWR).

 
8.3.3 Explicit Moisture Schemes (IMPHYS)
 
1. Dry -

No moisture prediction. Zero water vapor.

 
2. Stable Precip -

Nonconvective precipitation. Large scale saturation removed and rained out immediately. No rain evaporation or explicit cloud prediction.

 
3. Warm Rain -

Cloud and rain water fields predicted explicitly with microphysical processes. No ice phase processes.

 
4. Simple Ice (Dudhia) -

Adds ice phase processes to above without adding memory. No supercooled water and immediate melting of snow below freezing level. This also can be run with a look-up table (MPHYSTBL=1) version for efficiency.

 
5. Mixed-Phase (Reisner 1) -

Adds supercooled water to above and allows for slow melting of snow. Memory added for cloud ice and snow. No graupel or riming processes. See Reisner et al. (1998) for details. Since version 3.7 an optimized version of this code is also available (MPHYSTBL=2). This also can be run with a look-up table (MPHYSTBL=1) version for efficiency.

 
6. Goddard microphysics -

Includes additional equation for prediction of graupel. Suitable for cloud-resolving models. See Lin et al. (JCAM, 1983), Tao et al. (1989, 1993) for details. Scheme was updated for Version 3.5 to include graupel or hail properties.

 
7. Reisner graupel (Reisner 2) -

Based on mixed-phase scheme but adding graupel and ice number concentration prediction equations. Also suitable for cloud-resolving models. Scheme was updated significantly between Version 3.4 and 3.5, and again between 3.5 and 3.6. 3.6 also has a capability for calling the scheme less frequently than every time-step, but this is not standard and requires code editing to implement (Web pages will show the procedure).

 
8. Schultz microphysics -

A highly efficient and simplified scheme (based on Schultz 1995 with some further changes),

designed for running fast and being easy to tune for real-time forecast systems. It contains ice and graupel/hail processes.

 

 

 
8.3.4 Radiation Schemes (IFRAD)
 
0. None -

No mean tendency applied to atmospheric temperature, unrealistic in long-term simulations.

 
1. Simple cooling -

Atmospheric cooling rate depends just on temperature. No cloud interaction or diurnal cycle.

 
0 or 1. Surface radiation -

This is used with the above two options. It provides diurnally varying shortwave and longwave flux at the surface for use in the ground energy budget. These fluxes are calculated based on atmospheric column-integrated water vapor and low/middle/high cloud fraction estimated from relative humidity.

 
2. Cloud-radiation scheme -

Sophisticated enough to account for longwave and shortwave interactions with explicit cloud and clear-air. As well as atmospheric temperature tendencies, this provides surface radiation fluxes. May be expensive but little memory requirement. In Version 3.7 namelist switches LEVSLP and OROSHAW can be used with this option. LEVSLP enables slope effects on solar radiation, and OROSHAW allows shadowing effects on nearby grid-cells.

 
3. CCM2 radiation scheme -

Multiple spectral bands in shortwave and longwave, but cloud treated based on either resolved clouds (ICLOUD=1) or RH-derived cloud fraction (ICLOUD=2). Suitable for larger grid scales, and probably more accurate for long time integrations. Also provides radiative fluxes at surface. See Hack et al. (1993) for details. As with other radiation schemes ICLOUD=0 can be used to remove cloud effects on the radiation. Up until Version 3.5, this scheme was only able to interact with RH-derived clouds.

 

4. RRTM longwave scheme - 

This is combined with the cloud-radiation shortwave scheme when IFRAD=4 is chosen. This longwave scheme is a new highly accurate and efficient method provided by AER Inc. (Mlawer et al. 1997). It is the Rapid Radiative Transfer Model and uses a correlated-k model to represent the effects of the detailed absorption spectrum taking into account water vapor, carbon dioxide and ozone. It is implemented in MM5 to also interact with the model cloud and precipitation fields in a similar way to IFRAD=2.

 

 

 

 

 

8.3.5 Surface Schemes (ISOIL)
 
None - (ITGFLG=3)

No ground temperature prediction. Fixed surface temperature, not realistic.

 
0. Force/restore (Blackadar) scheme -

Single slab and fixed-temperature substrate. Slab temperature based on energy budget and depth assumed to represent depth of diurnal temperature variation (~ 10-20 cm).

 
1. Five-Layer Soil model -

Temperature predicted in 1,2,4,8,16 cm layers (approx.) with fixed substrate below using vertical diffusion equation. Thermal inertia same as force/restore scheme, but vertically resolves diurnal temperature variation allowing for more rapid response of surface temperature. See Dudhia (1996 MM5 workshop abstracts) for details. Cannot be used with Burk-Thompson PBL (IBLTYP=3).

 
2. Noah Land-Surface Model -

[Note: this was the OSU LSM until MM5 Version 3.5, and from 3.6 it is updated and renamed as the Noah LSM, a unified model between NCAR, NCEP and AFWA].

The land-surface model is capable of predicting soil moisture and temperature in four layers (10, 30, 60 and 100 cm thick), as well as canopy moisture and water-equivalent snow depth. It also outputs surface and underground run-off accumulations. The LSM makes use of vegetation and soil type in handling evapotranspiration, and has effects such as soil conductivity and gravitational flux of moisture. In MM5 it may be called instead of the SLAB model in the MRF and Eta PBL schemes, taking surface-layer exchange coefficients as input along with radiative forcing, and precipitation rate, and outputting the surface fluxes for the PBL scheme. This scheme uses a diagnostic equation to obtain a skin temperature, and the exchange coefficients have to allow for this by use of a suitable molecular diffusivity layer to act as a resistance to heat transfer. See Chen and Dudhia (2001). It also handles sea-ice surfaces. All the aforementioned processes were in the OSU LSM. The Noah LSM has some modifications, and additional processes to better handle snow cover, predict physical snow depth, and frozen soil effects. In addition to soil moisture, soil water is a separate 4-layer variable, and soil moisture is taken to be the total of soil water and soil ice. Physical snow height is also diagnosed and output. The Noah LSM can also optionally use satellite-derived climatological albedo, supplied by REGRID, instead of relating albedo to land-use type. See Appendix D for practical guidance on setting up the modeling system to use the LSM.

 
3. Pleim-Xiu Land-Surface Model

This is coupled to the Pleim-Xiu PBL (IBLTYP=7). It is a combined land-surface and PBL model. It represents soil moisture and temperature in two layers (surface layer at 1 cm, and root zone at 1 m) as well as canopy moisture. It handles soil surface, canopy and evapotranspiration moisture fluxes. It also makes use of percentage land-use and soil data from Terrain to aggregatesoil and vegetation properties, rather than using a single dominant type. Soil moisture can be initialized from land-use moisture availability, a soil moisture input grid (as with the Noah LSM), or via nudging using model minus observed surface temperature error to correct soil moisture. The model also has optional plant-growth and leaf-out algorithms making it suitable for long-term simulations. See Xiu and Pleim (2000).

 

 

 

 
Bucket Soil Moisture Model - (IMOIAV=1,2)

This can be run with ISOIL=0 or 1. It keeps a budget of soil moisture allowing moisture availability to vary with time, particularly in response to rainfall and evaporation rates. The soil moisture can be initialized from land-use type and season (LANDUSE.TBL) as before (IMOIAV=1), or a 10-cm soil moisture input as with the Noah LSM (IMOIAV=2).

 
Snow Cover Model - (IFSNOW=0,1,2)

When the LSM is not used this switch determines how snow cover is handled. IFSNOW=0 means snow cover is ignored. IFSNOW=1 uses the input snow-cover (0/1) flag to determine the land-surface properties such as albedo and soil moisture. These stay fixed in the simulation. Since Version 3.5 there is an option (IFSNOW=2) to predict snow cover using an input water-equivalent snow depth. It updates water-equivalent snow depth according to a heat and moisture budget in the SLAB routine, and accumulates snow from the microphysical schemes (currently IMPHYS=4,5, or 7). In Version 3.7 this can be used with IMOIAV=1 or 2, the bucket soil moisture.

 

Polar Mods - (IPOLAR=1)

The so-called Polar Mods were developed by the Byrd Polar Research Center at Ohio State Univerisity to better handle Antarctic conditions for forecasting purposes. IPOLAR=1 is a compile-time option, therefore it is in the configure.user file. The use of the Polar Mods has several effects, and should be applied only with ISOIL=1. The main changes are (i) to increase the number of prognostic soil layers from 5 to 7, and (ii) to allow for sea-ice fraction effects on the heat and moisture fluxes and mean ground temperature. Sea-ice fraction can either be diagnosed from sea-surface temperature (IEXSI=1), or read in from a dataset (IEXSI=2). It is also recommended that the Eta PBL is used with this option, as that has been modified to account for ice-surface fluxes. The soil model is modified to account for snow and ice properties for heat conduction. The Polar Mods also slightly modify the Simple Ice and Reisner 1 microphysics schemes to use the Meyers formula for ice number concentration. In release 3.7 the MRF PBL also has modifications to work with this option.

 

8.4 Interactions of Parameterizations

 

 

 

8.5 Boundary conditions

 

8.5.1 Lateral boundary conditions (IBOUDY)
 
0. Fixed -

This will not allow time variation at lateral boundaries. Not recommended for real-data applications.

 
2. Time-dependent/Nest -

Outer two rows and columns have specified values of all predicted fields. Recommended for nests where time-dependent values are supplied by the parent domain. Not recommended for coarse mesh where only one outer row and column would be specified.

 
3. Relaxation/inflow-outflow -

Outer row and column is specified by time-dependent value, next four points are relaxed towards the boundary values with a relaxation constant that decreases linearly away from the boundary.

Recommended for coarse mesh where boundary values are supplied by the BDYOUT_DOMAIN1 file. Fields without boundary values (such as some moisture variables) are specified zero on inflow and zero-gradient on outflow boundaries.

 

8.5.2 Lower boundary conditions

 

The LOWBDY_DOMAINx file provides sea-surface temperature, substrate temperature, and optionally snow cover and sea-ice. The switch ISSTVAR allows multiple times in this file (created by INTERPF) to be read in as the model runs, which is the method of updating these fields in long-term simulations.

 

8.5.3 Upper boundary condition (IFUPR)
 
0. No upper boundary condition -

Rigid lid with no vertical motion at the model top. This may be preferable for very coarse mesh simulations (50 km or more grids).

 
1. Upper radiative condition -

Top vertical motion calculated to reduce reflection of energy from the model top preventing some spurious noise or energy build-up over topography. This is recommended for grid-lengths below 50 km. It works better for hydrostatic gravity wave scales, rather than inertial or nonhydrostatic

scales.

 

 

8.6 Nesting

 

8.6.1 One-way nesting

 

When a single-domain or multiple-domain run completes, its domain output can be put into NESTDOWN to create an input file with higher resolution (any integer ratio in dx) and new lateral and lower boundary files. See NESTDOWN chapter. NESTDOWN allows the addition of higher resolution elevation and land-use data. This is known as a one-way nest because it is forced purely by the coarse mesh boundaries, and obviously has no feedback on the coarse-mesh run.

 

When INTERPB becomes available, it will be possible to put model output on pressure levels and reanalyze with observations as well as choosing different vertical levels for the nest by using INTERPF and NESTDOWN.

 

8.6.2 Two-way nesting

 

Multiple domains can be run in MM5 at the same time. Up to nine domains on four levels of nest are allowed with each nest level one third of its parent domain's grid-length. Each domain takes information from its parent domain every timestep, and runs three timesteps for each parent step before feeding back information to the parent domain on the coincident interior points. Figure 1.3 illustrates the staggering with the 3:1 ratio. The feedback distinguishes two-way nesting from one-way nesting, and allows nests to affect the coarse mesh solution, usually leading to better behavior at outflow boundaries. However there is significant overhead cost associated with the boundary interpolation and feedback at every timestep, particularly with distributed-memory machines.

 

8.6.3 Two-way nest initialization options (IOVERW)

 

IOVERW is the overwrite switch that determines whether a nested input file is used to replace coarse mesh information or whether the coarse domain is just interpolated to start the nest.

 
0. Interpolation -

No nested input file is required. All the information including topography is interpolated from the coarse mesh to start the nest. This is suitable for nests that start later than the coarse mesh or for

moving and overlapping nests. This could be used in situations where improved topography is not essential such as over water or smooth terrain.

 
1. Nest input file -

This requires an MMINPUT file to be read in for the nest. The input file contains all the meteorological and terrain fields at a higher resolution, and so may provide a more accurate initial analysis. This should only be applied when the coarse mesh and nest both start at the same time, because an analysis at a later time is unlikely to match the coarse-mesh boundary conditions.

 
2. Terrain input file -

This only requires the TERRAIN file for the nest. The meteorological fields are interpolated from the coarse mesh, but the terrain and land-use are replaced with the higher resolution fields from

TERRAIN. A vertical adjustment is carried out to put the interpolated fields on terrain-following levels consistent with the new nest terrain. This has the benefit of allowing fine-topography nests to start later than the coarse mesh.

 

8.6.4 Two-way nesting feedback options (IFEED)

 

These options determine how a nest feeds back its interior information to its parent domain.

 
0. No feedback -

Feedback is turned off, similar to one-way nests except boundary conditions are updated by parent domain every timestep. Not recommended except for tests.

 
1. 9-point weighted average -

Feedback uses a weighted average of nest points onto coarse mesh point, not just coincident value. Not the primary recommended choice because terrain elevation is not consistent with this

feedback.

 
2. 1-point feedback with no smoothing -

Coincident point is fed back. Not recommended except for tests.

 

3. 1-point feedback with smoother-desmoother -

Coincident point is fed back, and coarse mesh fields are then filtered using smoother-desmoother to remove two-grid-length noise. Recommended option.

 
4. 1-point feedback with heavy smoothing -

Coincident point is fed back, and coarse mesh fields are then smoothed with a 1-2-1 smoother that

removes two-grid-length noise, and damps other short wavelengths strongly. Could be used if nest region appears excessively noisy when viewing coarse mesh output.

 

 

8.7 Four-Dimensional Data Assimilation (FDDA)

 

8.7.1 Introduction

FDDA is a method of running a full-physics model while incorporating observations. Thus the model equations assure a dynamical consistency while the observations keep the model close to the true conditions and make up for errors and gaps in the initial analysis and deficiencies in model physics. The MM5 model uses the Newtonian-relaxation or nudging technique.

 

8.7.2 FDDA Method

 

There are two distinct nudging methods. The model can use these individually or combined.

 
Analysis or Grid Nudging -

Newtonian relaxation terms are added to the prognostic equations for wind, temperature, and water vapor. These terms relax the model value towards a given analysis. The technique is implemented by obtaining analyses on the model grid over the data assimilation period and these are fed to the model in its standard input format. The model linearly interpolates the analyses in time to determine the value towards which the model relaxes its solution. The user defines the time scale of the relaxation constants for each variable.

 
Station or Observational Nudging -

In situations where analysis-nudging is not practical, such as at high resolution or with asynoptic data, obs-nudging is a useful alternative. This method again uses relaxation terms, but the method is similar to objective analysis techniques where the relaxation term is based on the model error at observational stations. The relaxation is such as to reduce this error. Each observation has a radius of influence, a time window and a relaxation time scale to determine where, when and how much it affects the model solution. Typical model grid points may be within the radius of influence of several observations and their contributions are weighted according to distance. To implement this method an observation input file is required that chronologically lists the 3D positions and values of each observation in a specific format.

 

8.7.3 Uses of FDDA

 

Four-Dimensional Data Assimilation has three basic uses -

 

  • Dynamic Initialization: Data assimilation by the above methods is applied during a pre-forecast time period for which additional observations or analyses exist. Then the nudging terms switch off as the forecast begins. This has two advantages over the standard static initialization, (i) It can make use of asynoptic data during the pre-forecast period and generally contains more observational information at the forecast start time, and (ii) There is a reduced spin-up or shock effect at the forecast start owing to the better balance of the initial model conditions. 
  • Dynamic Analysis: This is the same as dynamic initialization except that the intent is to produce a four-dimensionally consistent analysis taking into account dynamical balances that are provided by the model and observations that are introduced by nudging. This analysis may be used to initialize higher-resolution simulations or for kinematic studies such as chemical and tracer transports. 
  • Boundary Conditions: By using data assimilation on the coarse mesh and nesting with a finer mesh, the fine mesh is provided with superior boundary conditions compared to the standard linear interpolation of analyses, because the boundaries have a much higher time resolution of features passing through them into the fine mesh.  

Note: For scientific case studies and forecasts the model should have no data assimilation terms as these represent non-physical terms in the equations.

 

8.7.4 Data used in FDDA
 
Analysis nudging -

When doing three-dimensional analysis nudging, no additional input data files are required. MM5 can use the same MMINPUT file or a copy of MMINPUT to MMINPUT2 file. If surface FDDA is desired, a user must set F4D = TRUE in the namelist of RAWINS job deck, which enables the job to create (typically) a 3-hourly surface analysis file to be used in MM5. FDDA now works with all the boundary layer options except 0, 1, and 3. It needs information on the boundary-layer top from these schemes.

 
Station nudging -

There is no standard software available to create input data file for observational nudging. The input file is a binary file containing 9 real numbers per record and in order of increasing time. The READ statement in the model is the following:

 

READ (NVOL,END=111) TIMEOB,RIO,RJO,RKO,(VAROBS(IVAR),IVAR=1,5)

 

where NVOL is the input fortran unit number, and

 

TIMEOB: Julian date in dddhh. Example: 16623.5 - Julian day 166 and hour 2330 UTC

RIO: y-location - I dot-point location on coarse mesh (may be a fraction of a grid)

RJO: x-location - J dot-point location on coarse mesh (may be a fraction of a grid)

RKO: z-location - K half-σ level (must be on half σ levels)

IVAR(1): u wind - in m/sec rotated to model grid

IVAR(2): v wind - in m/sec rotated to model grid

IVAR(3): temperature - in Kelvin

IVAR(4): water vapor mixing ratio - in kg/kg

IVAR(5): Pstar - in cb (only used in hydrostatic model)

 

A user may include more information at the end of a record which are not read by the model but can be used to identify the station and data type. The no-data value is 99999.. If running the model in nonhydrostatic mode, 99999. can be used to fill up the Pstar spot.

 

 

8.8 How to run MM5

 

Get the source code. The current MM5 release resides on NCAR's anonymous ftp site, ftp.ucar.edu:mesouser/MM5V3/MM5.TAR.gz. You may download MM5.TAR.gz to your working directory from the web page, ftp://ftp.ucar.edu/mesouser/MM5V3. Or you can copy it from ~mesouser/MM5V3/MM5.TAR.gz on NCAR's SCD machines.

 

There are 2 steps to compiling and running the MM5 system:

 

  • Choosing compilation options and compiling the code.
  • Modifying the run-time options and executing the program.

 

8.8.1 Compiling MM5

 

  • Edit the file "configure.user"
  • Type `make'

 

(see 8.8.3 for running batch job on NCAR's IBM.)

The user chooses those compilation options appropriate to his/her system by editing the "configure.user" file. This file is included in every Makefile used in compiling the model so it contains many rules, but the user need only concern with 3 things:

  • Find the section of compilation options appropriate for your machine. Uncomment the RUNTIME_SYSTEM variable and the compiler options.
  • Make sure that the general utilities required in a UNIX environment for compilation are available and appropriate. For example, there are many versions of the program "make" - if yours has special quirks and/or options, this would be the place to indicate them.
  • Set model options in sections 5 and 6 of configure.user. These are used to set up domain sizes, 4DDA and physics option for (selective) compilation purposes.

 

If you wish to compile and run the model on a distributed-memory machine (such as IBM SP2, Cray T3E, SGI Origin 2000 with MPI, and Linux clusters),

  • obtain additional tar file, MPP.TAR.gz, gunzip and then untar the file in the MM5 top directory;
  • edit the configure.user file, and select and uncomment the appropriate RUNTIME_SYSTEM and compiler flags;
  • type `make mpp' to make an executable.

 

More information is provided for this topic in README.MPP in the MM5 tar file, Appendix D in this document, and on Web page: http://www.mmm.ucar.edu/mm5/mpp.html

 

8.8.2 Running MM5

 

  • create the "mm5.deck" script by typing `make mm5.deck' - need to set RUNTIME_SYSTEM correctly to get the right deck.
  • edit the mm5.deck script to set appropriate namelist values
  • run the "mm5.deck" script by typing `mm5.deck'.
Basic Run:

Need to set at least these namelist variables in mm5.deck:

TIMAX, TISTEP, TAPFRQ, NESTIX, NESTJX, NESTI, NESTJ

 

Restart Run: 

In addition to above namelist variables, set IFREST = .TRUE., and IXTIMR = restart time (can be found at the end of the mm5.print.out file from the previous run).

 

One-Way Run: 

Should treat a one-way run in exact manner as if it is a basic run.

 

8.8.3 Running MM5 Batch Job on NCAR's IBM

 

  • If you want to work in batch mode, whether to compile and/or execute, get a copy of mm5.deck.ibm from mesouser directory: ~mesouser/MM5V3/IBM on NCAR's blackforest/babyblue/bluesky. Or, you may get the deck once you obtain the MM5.TAR.gz file on your local machine. To do so, first unzip and untar the tar file, edit the configure.user file to define RUNTIME_SYSTEM=``sp2"; then type `make mm5.deck'. This deck has the relavent part of configure.user file inside the deck. This deck is designed to be used for both interactive and batch mode.  
  • If you would like to compile interactively on a IBM, you can either use the above deck, or use the IBM interactive deck, by setting the RUNTIME_SYSTEM=``IBM'', and followed by typing `make mm5.deck'. The mm5.deck generated this way has an appearance of other workstations decks. Compiling on IBM is similar to what one does on all other workstations. 
  • When you use the interactive deck to compile, you will still need to use the batch deck to submit a batch job for executing. Before you submit the batch job, remember to tar up your entire directory structure, and save it to some place (whether it is NCAR's MSS, or your local archive). Your batch job needs to access this tar file (default name mm5exe.tar) for executing. 

Note: The mmlif (namelist file) for running MM5 is now generated from both your configure.user file (section 6 of the configure.user) and mm5.deck.

 

Useful make commands

 

make clean

 

This removes all generated files and returns the code to its original state. Use it before doing recompilation.

 

make code

 

This creates *.f files from *.F files and places them in directory pick/. Useful for looking at code in a single directory. All files related to options selected in configure.user file will be created.

 

 

8.9 Input to MM5

 

Files from INTERPF program for a basic run:

 

  • Model initial condition file(s): MMINPUT_DOMAINx (MMINPUT_DOMAIN2, 3.. are optional)
  • Lateral and lower boundary condition files for the coarsest domain: BDYOUT_DOMAIN1, LOWBDY_DOMAINx (LOWBDY_DOMAIN2, 3, ..., are optional. The model will use them if they are present).
  • Nest terrain file(s) from program TERRAIN: TERRAIN_DOMAIN2, 3, etc. if using IOVERW = 2 option.

Files from MM5 program, if it is a restart run: 

  • Model save file(s) from previous run: rename SAVE_DOMAINx to RESTART_DOMAINx

 

Files from RAWINS/LITTLE_R, if running gridded 4DDA option with surface analysis 

  • FDDA surface analysis: SFCFDDA_DOMAINx

 

Files generated by user, if running observational nudging option 

  • FDDA 4D obs file(s): MM5OBS_DOMAINx

 

mmlif: a namelists file containing user-specified options; created when mm5.deck is executed.

 

LANDUSE.TBL: user-modifiable landuse characteristics (in ASCII), provided.

RRTM_DATA: RRTM radiation scheme data file, provided.

BUCKET.TBL: user-modifiable constants used in bucket soil moisture model, provided.

VEGPARM.TBL: user-modifiable constants used in Noah LSM, provided.

SOILPARM.TBL: user-modifiable constants used in Noah LSM, provided.

GENPARM.TBL: user-modifiable constants used in Noah LSM, provided.

 

Note that the workstation mm5.deck expects all input files (named as above) to be present in the Run/ directory. See the mm5.deck for details.

 

 

8.10 Output from MM5

 

A number of files are written out during MM5 integration. These are

  • history files (MMOUT_DOMAINx), if IFTAPE = 1, and the output frequency is set by TAPFRQ (and INCTAP).
  • restart files (SAVE_DOMAINx), if IFSAVE = .TRUE., and the output frequency is set by SAVFRQ.

Output from each domain will be written to different files. For example, domain 1's history file is written to MMOUT_DOMAIN1, and its restart file to SAVE_DOMAIN1. Each output file contains data for all output times for that domain. On NCAR's IBMs, we recommend that one uses BUFFRQ to limit output file sizes not exceeding 6,000 Mb (which is the file size limit for MSS).

 

For each time period the model history output includes:

 

  • A general header record describing the model configuration
  • A subheader describing the field following, and the field. This is repeated for all fields in a output.

 

3D forecast fields dimensioned by (IX, JX, KX or KX+1) for that domain include (note that the variables are NO LONGER coupled in Version 3):

 

1

U: U-wind (m/s)

dot

2

V: V-wind (m/s

dot

3

T: Temperature (K)

cross

4

Q: Water vapor mixing ratio (kg/kg) (if IMPHYS .ge. 2)

cross

5

CLW: Cloud water mixing ratio (kg/kg) (if IMPHYS .ge. 3)

cross

6

RNW: Rain water mixing ratio (kg/kg) (if IMPHYS .ge. 3)

cross

7

ICE: Ice cloud mixing ratio (kg/kg) (if IMPHYS .ge. 5)

cross

8

SNOW: Snow mixing ratio (kg/kg) (if IMPHYS .ge. 5)

cross

9

GRAUPEL: Graupel (kg/kg) (if IMPHYS .ge. 6)

cross

10

NCI: Number concentration of ice (if IMPHYS = 7)

cross

11

TKE: Turbulent k.e. (J/kg) (if IBLTYP = 3,4,6)

cross

12

RAD TEND: Atmospheric radiation tendency (K/day)(if FRAD .ge. 2)

cross

13

W: Vertical velocity (m/s) (on full s -levels)

cross

14

PP: Perturbation pressure (Pa)

cross

 
 
 
 
 
 
 
 
 
 

2D forecast fields dimensioned (IX, JX) include:

1

PSTARCRS: Pstar (mb)

cross

2

GROUND T: Ground temperature (K)

cross

3

RAIN CON: Accum. convective rainfall (cm)

cross

4

RAIN NON: Accum. nonconv. rainfall (cm)

cross

5

PBL HGT: PBL height (m)

cross

6

REGIME: PBL regime (catagory, 1-4)

cross

7

SHFLUX: Surface sensible heat flux (W/m2)

cross

8

LHFLUX: Surface latent heat flux (W/m2)

cross

9

UST: Frictional velocity (m/s)

cross

10

SWDOWN: Surface downward shortwave radiation (W/m2)

cross

11

LWDOWN: Surface downward longwave radiation (W/m2)

cross

12

MAVAIL: Surface moisture availability (if IMOIAV=1,2)

cross

13

SOIL T x: Soil temperature in a few layers (K) (if ISOIL=1,2)

cross

14

SOIL M x: Soil moisture in a few layers (m3/m3) (if ISOIL=2)

cross

15

SOIL W x: Soil water in a few layers (m3/m3) (if ISOIL=2)

cross

16

SFCRNOFF: Surface runoff (mm) (if ISOIL=2)

cross

17

UGDRNOFF: Underground runoff (mm) (if ISOIL=2)

cross

18

SNOWCOVR: Snow cover (variable if ISOIL=2)

cross

19

SNOWH: physical snow height (m) (if ISOIL=2, or IFSNOW=2)

cross

20

WEASD: Water-equivalent snow depth (mm) (if ISOIL=2, or IFSNOW=2)

cross

21

CANOPYM: Canopy moisture (m) (if ISOIL=2)

cross

22

GRNFLX: ground head flux (W/m2) (if ISOIL=2, 3)

cross

23

ALB: albedo (fraction) (if ISOIL=2)

cross

24

ALBSNOMX: maximum snow albedo (%) (if ISOIL=2, and RDMAXALB=T)

cross

25

MONALBnn: monthly albedo (%) (if ISOIL=2, or RDBRDALB=T)

cross

26

ALBEDO: background albedo (%) (if IFSOIL=2, RDBRDALB=T)

cross

27

VEGFRC: Vegetation coverage (if ISOIL = 2)

cross

28

SWOUT: top outgoing shortwave radiation (if FRAD>=2)

cross

29

LWOUT: top outgoing longwave radiation (if FRAD>=2)

cross

30

T2: 2 m temperature (K) (if IBLTYP=2, 4, 5)

cross

31

Q2: 2 m mixing ratio (kg/kg) (if IBLTYP=2, 4, 5)

cross

32

U10: 10 m u component of wind (m/sec) (if IBLTYP=2,4,5)

cross

33

V10: 10 m v component of wind (m/sec) (if IBLTYP=2,4,5)

cross

34

M-O LENG: Monin-Obukov length (m) (if ISOIL=3)

cross

35

NET RAD: surface net radiation (W/m2) (if ISOIL=3)

cross

36

ALBEDO: surface albedo (fraction) (if ISOIL=3)

cross

37

RA: aerodynamic resistance (s/m) (if ISOIL=3)

cross

38

RS: surface resistance (s/m) (if ISOIL=3)

cross

39

LAI: leaf area index (area/area) (if ISOIL=3)

cross

40

VEGFRC: vegetation fraction (fraction) (if ISOIL=3)

cross

41

ZNT: roughness length (m) (if ISOIL=3)

cross

42

ISLTYP: soil texture type (if ISOIL=3)

cross

43

SUMFB: mass flux updraft (if ICUPA=8)

cross

44

SPSRC: source layer updraft (if ICUPA=8)

cross

45

SEAICEFR: seaice fraction (if IPOLAR=1)

cross

46

TGSI: seaice temperature (if IPOLAR=1)

cross

 

2D constant fields dimensioned (IX, JX) include:
 

47

TERRAIN: Terrain elevation (m)

cross

48

MAPFACCR: Map scale factor

cross

49

MAPFACDT: Map scale factor

dot

50

CORIOLIS: Coriolis parameter (/s)

cross

51

RES TEMP: Substrate temperature (K)

cross

52

LATITCRS: Latitude (deg)

cross

53

LONGICRS: Longitude (deg)

cross

54

LANDUSE: Land-use category

cross

55

SNOWCOVR: Snow cover (if ISOIL < 2)

cross

56

TSEASFC: Sea surface temperature (K)

cross

57

SEAICE: Seaice (dimensionless) (if ISOIL=2)

cross

 

Other special output:
 

58

SIGMAH: Model half-sigma levels

 

59

ALBD: Surface albedo from LANDUSE.TBL

 

60

SLMO: Surface moisture availability from LANDUSE.TBL

 

61

SFEM: Surface emissivity from LANDUSE.TBL

 

62

SFZ0: Surface roughness from LANDUSE.TBL

 

63

THERIN: Surface thermal inertia from LANDUSE.TBL

 

64

SFHC: Soil heat capacity from LANDUSE.TBL

 

65

SCFX: Snow cover effect from LANDUSE.TBL

 

 

 

If one sets IFTSOUT = .TRUE., and defines TSLAT and TSLON for the time-series locations, one will obtain time-series output in fort.26 for domain 1, fort.27 for domain 2 and so on for serial runs (for MPI runs, the time series is (unfortunately) scattered in various rsl.out.* files. The time-series output contains the following data:

 

xtime, time-step, its, jts, t-sfc, q-sfc, u-sfc, v-sfc,

pstar, pp-sfc, rainc, rainnc, clw, glw, hfx, qfx, gsw, t-ground

 

where

xtime : model time (unit minutes)

time-step : the nth time series

its, jts : I, J locations in model grid for time-series points

t-sfc : 2-m or lowest σ level temperature (unit K)

q-sfc : 2-m or lowest σ level mixing ratio (unit kg/kg)

u-sfc, v-sfc : the 10-m or lowest-σ level winds (unit m s-1), rotated to earth coordinates

pstar : reference p* (unit cb, or 10*hPa)

pp-sfc : perturbation pressure at the lowest-σ level (unit Pa)

rainc, rainnc : accumulative convective and non-convective surface precipitation (unit cm)

clw : column integrated cloud liquid/ice (unit mm)

glw, gsw : surface downward long-wave and shortwave radiation (unit W m-2)

hfx, qfx : surface sensible and latent heat (* latent heat of vaporization) fluxes (unit W m-2)

t-ground : ground or skin temperature (if ISOIL = 2) temperature (unit K).

 

 

8.11 MM5 Files and Unit Numbers

 

MM5 accesses most files by referring to the file names. Fortan unit numbers associated with the files are assigned as follows:

 

Table 8.1 File names, fortran unit numbers, and their description for MM5.

File name

Unit number

Description


  INPUT
 

mmlif

fort.10

Input, namelist file

LOWBDY_DOMAIN1

fort.21, 22, ...

Lower boundary file, contains substrate temp and SST

BDYOUT_DOMAIN1

 

fort.9

Lateral boundary file created by program INTERPF

LANDUSE.TBL

fort.19

Physical properties for landuse categories

BUCKET.TBL

fort.18

Max, min moisture availability range, evaporation rate

VEGPARM.TBL

fort.19

used if ISOIL = 2

SOILPARM.TBL

fort.19

used if ISOIL = 2

GENPARM.TBL

fort.19

used if ISOIL = 2

RRTM_DATA

fort.20

RRTM radiation scheme data

MMINPUT_DOMAINx

(TERRAIN_DOMAIN2..)

fort.11, 12, ... 19

Initial condition files created by program INTERPF (or NESTDOWN);

or Terrain output files for nests

MMINPUT(2)_DOMAINx

fort.31, 32, ... 39

3D analysis nudging files (same as initial condition files)

SFCFDDA_DOMAINx

fort.71, 72, ... 79 (fort.81, 82, ... 89)

Surface analysis nudging files created by program LITTLE_R/RAWINS

MM5OBS_DOMAINx

fort.61,62, ... 69

Observation nudging files created by user's own program

RESTART_DOMAINx

fort.91, 92 ... 99

Restart files (same as SAVE_DOMAINx files)


  OUTPUT
 

MMOUT_DOMAINx

fort.41,42, ... 49

MM5 model history files

SAVE_DOMAINx

fort.51, 52, ..., 59

restart files

SHUTDO_DOMAINx

fort.61, 62, ..., 69

Shutdown restart files

fort.26, fort.27....

fort.26, 27, ..., 29

time series output (IFTSOUT=T)

 
 

8.12 Configure.user Variables

 

The `configure.user' is the first file one needs to edit (if one is running Cray batch job, one would need to edit the mm5.deck only and these variables appear inside the deck). Except for the first variable, the rest are used for setting up model's memory - these variables are referred to as pre-compilation variables. Sections 1, 4 and make rules will be explained in Chapter 9.

 

RUNTIME_SYSTEM

computer system to run model on.

FDDAGD

=1, for 4DDA grid analysis nudging; =0, no 4DDA.

FDDAOB

=1, for 4DDA observation nudging; =0, no obs 4DDA.

MAXNES

maximum number of domains in simulation. Note though, there are only 4 default nest levels (i.e. 1 coarse domain and 3 nests)

MIX,MJX,MKX

maximum number of grid points in I, J, and K.

IMPHYS

options for explicit schemes:
=1, dry;
=2, removal of super-saturation;
=3, warm rain (Hsie);
=4, simple ice (Dudhia);
=5, mixed phase (Reisner);
=6, mixed phase with graupel (Goddard);
=7, mixed phase with graupel (Reisner);
=8, mixed phase with graupel (Schultz)

MPHYSTBL

=0, not using look-up table version;
=1, use look-up table version of explicit scheme options 4 and 5;
=2, use new optimized version (with vmass libraries)

ICUPA

options for cumulus parameterization schemes:

=1, none;

=2, Anthes-Kuo;

=3, Grell;

=4, Arakawa-Schubert;

=5, Fritsch-Chappell;

=6, Kain-Fritsch;

=7, Betts-Miller;

=8, Kain-Fritsch 2 (with shallow convection).

IBLTYP

options for planetary boundary layer schemes:
=0, no PBL;
=1, bulk PBL;
=2, Blackadar PBL;
=3, Burk-Thompson PBL;
=4, Eta PBL;
=5, MRF PBL;
=6, Gayno-Seaman PBL;
=7, Pleim-Chang PBL.

FRAD

options for atmospheric radiation schemes:
=0, none;
=1, simple cooling;
=2, cloud (Dudhia) (require IMPHYS 3);
=3, CCM2;
=4, RRTM longwave scheme.

IPOLAR

=0, none;
=1, polar physics (ISOIL .ne. 2).