January 2005
PSU/NCAR Mesoscale Modeling System Tutorial Class Notes and User’s Guide: MM5 Modeling System Version 3
Mesoscale and Microscale Meteorology Division National Center for Atmospheric Research
NCAR MM5 Tutorial Class Staff:
Jimy Dudhia Dave Gill Kevin Manning Wei Wang Cindy Bruyere Sudie Kelly, Administrative Assistant Katy Lackey, Administrative Assistant
MM5 Tutorial
MM5 Tutorial
CONTENTS
CONTENTS 1
INTRODUCTION 1.1 1.2 1.3 1.4 1.5 1.6 1.7 1.8 1.9 1.10
2
Getting Started 2.1 2.2 2.3 2.4 2.5 2.6 2.7 2.8 2.9 2.10 2.11 2.12 2.13 2.14
3
Purpose 3 Program portability 3 Prerequisite 4 Where to obtain program tar files? 5 What is Contained in a Program tar File? 7 Steps to run MM5 modeling system programs 7 Functions of Job Decks or Scripts 8 What to Modify in a Job Deck/Script? 8 How to Build the Executable and Run the Program? 10 Input Files 11 Output Files 11 Representation of Date in MM5 Modeling System Programs 11 Where to Find Data at NCAR? 12 Other Data Sources 14
MAKE UTILITY 3.1 3.2 3.3 3.4 3.5 3.6 3.7 3.8 3.9 3.10 3.11
MM5 Tutorial
Introduction to MM5 Modeling System 3 The MM5 Model Horizontal and Vertical Grid 6 Nesting 9 Lateral Boundary Conditions 10 Nonhydrostatic Dynamics Versus Hydrostatic Dynamics 11 Reference State in the Nonhydrostatic Model 11 Four-Dimensional Data Assimilation 12 Land-Use Categories 12 Map Projections and Map-Scale Factors 13 Data Required to Run the Modeling System 13
The UNIX make Utility 3 make Functionality 3 The Makefile 4 Sample make Syntax 5 Macros 5 Internal Macros 5 Default Suffixes and Rules 6 Sample Program Dependency Chart 7 Sample Program Components for make Example 8 makefile Examples for the Sample Program 9 Make Command Used in MM5 Preprocessing Programs 10
iii
CONTENTS
3.12 3.13
4
TERRAIN 4.1 4.2 4.3 4.4 4.5 4.6 4.7 4.8 4.9 4.10 4.11 4.12 4.13 4.14
5
Purpose 3 Structure 3 A schematic 4 Input to pregrid 4 Input to regridder 5 Output from regridder 5 Intermediate Data Format 5 Pregrid VTables 8 Pregrid program functioning 9 Handy pregrid utility programs 9 How to run REGRID 10 pregrid.csh 11 The regridder Namelist options 13 REGRID tar File 15 Data 15
Objective Analysis (little_r) 6.1 6.2 6.3 6.4 6.5 6.6 6.7
iv
Purpose 3 Input Data 4 Defining Mesoscale Domains 16 Interpolation 19 Adjustment 22 Fudging function 23 Script Variables 24 Parameter statement 24 Namelist Options 24 How to run TERRAIN 26 TERRAIN Didn’t Work: What Went Wrong? 28 TERRAIN Files and Unit Numbers 29 TERRAIN tar File 30 terrain.deck 31
REGRID 5.1 5.2 5.3 5.4 5.5 5.6 5.7 5.8 5.9 5.10 5.11 5.12 5.13 5.14 5.15
6
An Example of Top-level Makefile 10 An Example of Low-level Makefile 13
Purpose of Objective Analysis 3 RAWINS or LITTLE_R? 4 Source of Observations 4 Objective Analysis techniques in LITTLE_R and RAWINS 4 Quality Control for Observations 6 Additional Observations 7 Surface FDDA option 7
MM5 Tutorial
CONTENTS
6.8 6.9 6.10 6.11 6.12 6.13 6.14
7
INTERPF 7.1 7.2 7.3 7.4 7.5 7.6 7.7 7.8 7.9 7.10 7.11 7.12 7.13 7.14 7.15
8
Purpose 3 INTERPF Procedure 3 Surface Pressure Computation 5 Hydrostatic Vertical Interpolation 6 Integrated Mean Divergence Removal 6 Base State Computation 8 Initialization of Nonhydrostatic Model 9 Substrate Temperature and the LOWBDY_DOMAINn file 9 Shell Variables (for IBM job deck only) 10 Parameter Statements 10 FORTRAN Namelist Input File 11 How to Run INTERPF 12 INTERPF didn’t Work! What Went Wrong? 13 File I/O 14 INTERPF tar File 15
MM5 8.1 8.2 8.3 8.4 8.5 8.6 8.7 8.8 8.9 8.10 8.11 8.12 8.13 8.14 8.15 8.16 8.17 8.18
MM5 Tutorial
Objective Analysis on Model Nests 8 How to Run LITTLE_R 8 Output Files 10 Plot Utilities 11 LITTLE_R Observations Format 12 LITTLE_R Namelist 15 Fetch.deck 22
Purpose 3 Basic Equations of MM5 3 Physics Options in MM5 7 Interactions of Parameterizations 17 Boundary conditions 17 Nesting 18 Four-Dimensional Data Assimilation (FDDA) 20 How to run MM5 22 Input to MM5 24 Output from MM5 24 MM5 Files and Unit Numbers 27 Configure.user Variables 28 Script Variables for IBM Batch Deck: 30 Namelist Variables 30 Some Common Errors Associated with MM5 Failure 36 MM5 tar File 37 Configure.user 39 mm5.deck 54
v
CONTENTS
9
MAKE AND MM5 9.1 9.2 9.3 9.4
10
NESTDOWN 10.1 10.2 10.3 10.4 10.5 10.6 10.7 10.8 10.9 10.10 10.11 10.12
11
Purpose 3 INTERPB Procedure 3 Sea Level Pressure Computation 4 Vertical Interpolation/Extrapolation 6 Parameter Statements 8 FORTRAN Namelist Input File 8 How to Run INTERPB 11 INTERPB didn’t Work! What Went Wrong? 12 File I/O 12 INTERPB tar File 13
GRAPH 12.1 12.2 12.3 12.4 12.5 12.6 12.7 12.8 12.9 12.10
vi
Purpose 3 NESTDOWN Procedure 3 Base State Computation 5 Shell Variables (for IBM job deck only) 5 Parameter Statements 5 FORTRAN Namelist Input File 5 Horizontal Interpolation 7 Vertical Corrections after Horizontal Interpolation 8 How to Run NESTDOWN 10 NESTDOWN didn’t Work! What Went Wrong? 10 File I/O 11 NESTDOWN tar File 12
INTERPB 11.1 11.2 11.3 11.4 11.5 11.6 11.7 11.8 11.9 11.10
12
make and MM5 3 Configure.user File 4 Makefiles 5 CPP 11
Purpose 3 Typical GRAPH Jobs 4 Plotting Table File: g_plots.tbl 5 Default Option Settings File: g_defaults.nml 7 Map Options File: g_map.tbl 8 Plot Color Options File: g_color.tbl 10 How to Run GRAPH 11 Available 2-D Horizontal Fields 14 Available Cross-Section Only Fields 16 Available 3-D Fields (as 2-D Horizontal or Cross-Section) 17
MM5 Tutorial
CONTENTS
12.11 12.12 12.13 12.14 12.15
13
I/O FORMAT 13.1 13.2 13.3 13.4 13.5 13.6 13.7 13.8 13.9 13.10 13.11 13.12 13.13
14
Purpose 3 Utility Programs 3
EXERCISE 15.1 15.2 15.3 15.4 15.5 15.6 15.7 15.8 15.9
MM5 Tutorial
Introduction 3 Version 3 File Format 3 Explanation of Output Field List 7 Big Header Record for TERRAIN Output 7 Big Header Record for REGRID output 8 Big Header Record for little_r/RAWINS Output 9 Big Header Record for little_r Surface FDDA Output 10 Big Header Record for INTERPF Output 11 Big Record Header for LOWBDY Output 12 Big Record Header for BDYOUT Output 13 Big Record Header for MM5 Output 14 Big Record Header for Interpolated, Pressure-level MM5 Output 18 Special Data Format in MM5 Modeling System 20
Utility Programs 14.1 14.2
15
Some Hints for Running GRAPH 19 Sample Graph Plot File 20 Graph tar file 21 Script file to run Graph job 21 An Alternative Plotting Package: RIP 24
Test Case 3 Obtaining Program Tar Files 3 Getting Started 3 Experiment Design 4 Terrain and Land-Use Data 4 Objective Analysis : 4 Interpolation 5 Model Simulation 5 Viewing Model Output 6
vii
CONTENTS
Appendix A
Derivation of Basic MM5 Equations
Appendix B
MM5 Model Code
Appendix C
How to Noah Use Land-Surface Model Option
Appendix D
MPP MM5 - The Distributed-memory (DM) Extension
Appendix E
3DVAR
Appendix F
RAWINS
Appendix G
Alternative Plotting Package - RIP
Appendix H
Running MM5 Jobs on IBM References
viii
MM5 Tutorial
PREFACE
PREFACE The MM5 tutorial class is sponsored by the Mesoscale and Microscale Meteorology Division (MMM) at the National Center for Atmospheric Research. The class of January 2005 is the final official MM5 tutorial offered by the Mesoscale Prediction Group of MMM. The first tutorial class was offered in 1993, and a total of nearly 800 participants were trained at NCAR during the past 12 years. The tutorial notes are available on the MM5 Web page (URL: http://www.mmm.ucar.edu/mm5/ documents/tutorial-v3-notes.html and http://www.mmm.ucar.edu/mm5/documents/ MM5_tut_Web_notes/TutTOC.html). An online tutorial, which takes a new user step by step through how to set up and run the MM5 modeling system programs, is available at http:// www.mmm.ucar.edu/mm5/mm5v3/tutorial/teachyourself.html. General information regarding the MM5 modeling system, model applications, documentation and user support can also be found on the MM5 Web page (http://www.mmm.ucar.edu/mm5/mm5-home.html). This version of the notes is edited for MM5 modeling system Version 3, release 3-7. The major changes in the release 3-7 are improvements to the MM5 code. The pre- and post-processors did not change much between release 3-6 and 3-7. Most of the chapters in these notes have therefore not changed much, except chapter 8: MM5, which reflect all the new code development in release 3-7. The MM5 3DVAR code was officially released in June 2003. An introduction to this code has been added, and is available in Appendix E. More information on the 3DVAR system can be obtained from URL: http://www.mmm.ucar.edu/3dvar).
MM5 Tutorial
i
ii
MM5 Tutorial
PREFACE
MM5 Tutorial
i
1: INTRODUCTION
INTRODUCTION
1
Introduction to MM5 Modeling System 1-3 The MM5 Model Horizontal and Vertical Grid 1-6 Nesting 1-9 Lateral Boundary Conditions 1-10 Nonhydrostatic Dynamics Versus Hydrostatic Dynamics 1-11 Reference State in the Nonhydrostatic Model 1-11 Four-Dimensional Data Assimilation
1-12
Land-Use Categories 1-12 Map Projections and Map-Scale Factors 1-13 Data Required to Run the Modeling System 1-13
MM5 Tutorial
1-1
1: INTRODUCTION
1-2
MM5 tutorial
1: INTRODUCTION
1
INTRODUCTION
1.1 Introduction to MM5 Modeling System The Fifth-Generation NCAR / Penn State Mesoscale Model is the latest in a series that developed from a mesoscale model used by Anthes at Penn State in the early ‘70’s that was later documented by Anthes and Warner (1978). Since that time it has undergone many changes designed to broaden its applications. These include (i) a multiple-nest capability, (ii) nonhydrostatic dynamics, and (iii) a four-dimensional data assimilation (Newtonian nudging) capability, (iv) increased number of physics options, and (v) portability to a wider range of computer platforms, including OpenMP and MPI systems. The purpose of this introduction is to acquaint the user with some concepts as used in the MM5 modeling system. Flow-charts of the complete modeling system are depicted in the schematic diagrams in Fig. 1.1. It is intended to show the order of the programs, flow of the data, and to briefly describe their primary functions. Fig.1.1a shows the a flow-chart when objective analysis (LITTLE_R/RAWINS) is used, while Fig. 1.1b depicts the flow when 3-dimensional variational analysis (3DVAR) is used. Terrestrial and isobaric meteorological data are horizontally interpolated (programs TERRAIN and REGRID) from a latitude-longitude grid to a mesoscale, regtangular domain on either a Mercator, Lambert Conformal, or Polar Stereographic projection. Since the interpolation of the meteorological data does not necessarily provide much mesoscale detail, the interpolated data may be enhanced (program LITTLE_R/RAWINS) with observations from the standard network of surface and rawinsonde stations using a successive-scan Cressman or multiquadric technique. Program INTERPF then performs the vertical interpolation from pressure levels to the σ-coordinate of the MM5 model. Alternatively, program 3DVAR may be used to ingest data on model σ-levels. After a MM5 model integration, program INTERPB can be used to interpolate data from σ-levels back to pressure levels, while program NESTDOWN can be used to interpolate model level data to a finer grid to prepare for a new model integration. Graphic programs (RIP and GRAPH) may be used to view modeling system output data on both pressure and σ-levels.
MM5 Tutorial
1-3
1: INTRODUCTION
Additional Capability
Main Programs
Data Sets TERRESTRIAL
TERRAIN
GRAPH/ RIP
Old, USGS and Old, and USGS SiB Landuse Terrain
Other LSM Data
GLOBAL/REGIONAL ANALYSIS MM5
little_r/ RAWINS
REGRID ETA NNRP NCEP AVN ...... ERA ECMWF TOGA
INTERPF/ INTERPB/ NESTDOWN
little_r/ RAWINS
OBSERVATIONS
Surface
Rawinsonde
INTERPB INTERPF
MM5 NESTDOWN
Fig 1.1a The MM5 modeling system flow chart.
1-4
MM5 Tutorial
1: INTRODUCTION
Additional Capability
Main Programs
Data Sets TERRESTRIAL
TERRAIN
GRAPH/ RIP
Old, USGS and Old, and USGS SiB Landuse Terrain
Other LSM Data
GLOBAL/REGIONAL ANALYSIS MM5
REGRID
INTERPF 3DVAR
ETA NNRP NCEP AVN ...... ERA ECMWF TOGA INTERPF
Observations (Conventional, satellite) 3DVAR
Background error statistics
MM5
Fig 1.1b The MM5 modeling system flow chart, when using 3DVAR
MM5 Tutorial
1-5
1: INTRODUCTION
1.2 The MM5 Model Horizontal and Vertical Grid It is useful to first introduce the model’s grid configuration. The modeling system usually gets and analyzes its data on pressure surfaces, but these have to be interpolated to the model’s vertical coordinate before being input to the model. The vertical coordinate is terrain following (see Fig. 1.2) meaning that the lower grid levels follow the terrain while the upper surface is flat. Intermediate levels progressively flatten as the pressure decreases toward the chosen top pressure. A dimensionless quantity σ is used to define the model levels
σ = ( p0 – pt ) ⁄ ( ps 0 – pt )
(1.1)
where p0 is the reference-state pressure, pt is a specified constant top pressure, and ps0 is the reference-state surface pressure. Section 1.6 provides more discussion on the definition of the reference state. It can be seen from the equation and Fig 1.2 that σ is zero at the model top and one at the model surface, and each model level is defined by a value of σ. The model vertical resolution is defined by a list of values between zero and one that do not necessarily have to be evenly spaced. Commonly the resolution in the boundary layer is much finer than above, and the number of levels may vary from ten to forty, although there is no limit in principle. The horizontal grid has an Arakawa-Lamb B-staggering of the velocity variables with respect to the scalars. This is shown in Fig 1.3 where it can be seen that the scalars (T, q etc.) are defined at the center of the grid square, while the eastward (u) and northward (v) velocity components are collocated at the corners. The center points of the grid squares will be referred to as cross points, and the corner points are dot points. Hence horizontal velocity is defined at dot points, for example, and when data is input to the model the preprocessors do the necessary interpolations to assure consistency with the grid. All the above variables are defined in the middle of each model vertical layer, referred to as halflevels and represented by the dashed lines in Fig 1.2. Vertical velocity is carried at the full levels (solid lines). In defining the σ levels it is the full levels that are listed, including levels at 0 and 1. The number of model layers is therefore always one less than the number of full σ levels. Note also the I, J, and K index directions in the modeling system. The finite differencing in the model is, of course, crucially dependent upon the grid staggering wherever gradients or averaging are required to represent terms in the equations, and more details of this can be found in the model description document (Grell et al., 1994).
1-6
MM5 Tutorial
1: INTRODUCTION
K
σ
1
0.0
· σ
pt,
=0
1 1 --2
2
0.1
1 2 --2
3
0.2
1 3 --2
4
· σ
,w
u,v,T,q,p’ 0.3
1 4 --2
5
0.4
1 5 --2
6 7
0.5 0.6
8
0.7
9
0.78
10
0.84
11
0.89
12
0.93
13
0.96
16
1.00
ps,
· σ
=0
Figure 1.2 Schematic representation of the vertical structure of the model. The example is for 15 vertical layers. Dashed lines denote half-sigma levels, solid lines denote full-sigma levels.
MM5 Tutorial
1-7
1: INTRODUCTION
(IMAX, JMAX)
(IMAX, 1)
T,q,p’,w u,v
I
(1,1)
(1, JMAX)
J
Figure 1.3 Schematic representation showing the horizontal Arakawa B-grid staggering of the dot (l) and cross (x) grid points. The smaller inner box is a representative mesh staggering for a 3:1 coarse-grid distance to fine-grid distance ratio.
1-8
MM5 Tutorial
1: INTRODUCTION
1
2 3 4
Fig 1.4 Example of a nesting configuration. The shading shows three different levels of nesting.
1.3 Nesting MM5 contains a capability of multiple nesting with up to nine domains running at the same time and completely interacting. A possible configuration is shown in Fig 1.4. The nesting ratio is always 3:1 for two-way interaction. “Two-way interaction” means that the nest’s input from the coarse mesh comes via its boundaries, while the feedback to the coarser mesh occurs over the nest interior. It can be seen that multiple nests are allowed on a given level of nesting (e.g. domains 2 and 3 in Fig 1.4), and they are also allowed to overlap. Domain 4 is at the third level, meaning that its grid size and time step are nine times less than for domain 1. Each sub-domain has a “Mother domain” in which it is completely embedded, so that for domains 2 and 3 the mother domain is 1, and for 4 it is 3. Nests may be turned on and off at any time in the simulation, noting that whenever a mother nest is terminated all its descendent nests also are turned off. Moving a domain is also possible during a simulation provided that it is not a mother domain to an active nest and provided that it is not the coarsest mesh. There are three ways of doing two-way nesting (based on a switch called IOVERW). These are • Nest interpolation (IOVERW=0). The nest is initialized by interpolating coarse-mesh fields. Topography, land-use coastlines only retain the coarse-mesh resolution. This option should be used with moving nests. It requires no additional input files. • Nest analysis input (IOVERW=1). This requires a model input file to be prepared for the MM5 Tutorial
1-9
1: INTRODUCTION
nest in addition to the coarse mesh. This allows the inclusion of high-resolution topography and initial analyses in the nest. Usually such a nest would have to start up at the same time as the coarse mesh starts. • Nest terrain input (IOVERW=2). This new option requires just a terrain/land-use input file, and the meteorological fields are interpolated from the coarse mesh and vertically adjusted to the new terrain. Such a nest can be started up at any time in the simulation, but there will be a period over which the model would adjust to the new topography. One-way nesting is also possible in MM5. Here the model is first run to create an output that is interpolated using any ratio (not restricted to 3:1), and a boundary file is also created once a oneway nested domain location is specified. Typically the boundary file may be hourly (dependent upon the output frequency of the coarse domain), and this data is time-interpolated to supply the nest. Therefore one-way nesting differs from two-way nesting in having no feedback and coarser temporal resolution at the boundaries. The one-way nest may also be initialized with enhancedresolution data and terrain. It is important that the terrain is consistent with the coarser mesh in the boundary zone, and the TERRAIN preprocessor needs to be run with both domains to ensure this.
1.4 Lateral Boundary Conditions To run any regional numerical weather prediction model requires lateral boundary conditions. In MM5 all four boundaries have specified horizontal winds, temperature, pressure and moisture fields, and can have specified microphysical fields (such as cloud) if these are available. Therefore, prior to running a simulation, boundary values have to be set in addition to initial values for these fields. The boundary values come from analyses at the future times, or a previous coarser-mesh simulation (1-way nest), or from another model’s forecast (in real-time forecasts). For real-time forecasts the lateral boundaries will ultimately depend on a global-model forecast. In studies of past cases the analyses providing the boundary conditions may be enhanced by observation analysis (little_r or Rawins) in the same way as initial conditions are. Where upper-air analyses are used the boundary values may only be available 12-hourly, while for model-generated boundary conditions it may be a higher frequency like 6-hourly or even 1-hourly. The model uses these discrete-time analyses by linearly interpolating them in time to the model time. The analyses completely specify the behavior of the outer row and column of the model grid. In the next four rows and columns in from the boundary, the model is nudged towards the analyses, and there is also a smoothing term. The strength of this nudging decreases linearly away from the boundaries. To apply this condition, the model uses a boundary file with information for the five points nearest each of the four boundaries at each boundary time. This is a rim of points from the future analyses described above. The interior values from these analyses are not required unless data assimilation by grid-nudging is being performed, so disk-space is saved by having the boundary file just contain the rim values for each field. Two-way nest boundaries are similar but are updated every coarse-mesh timestep and have no relaxation zone. The specified zone is two grid-points wide instead of one.
1-10
MM5 Tutorial
1: INTRODUCTION
1.5 Nonhydrostatic Dynamics Versus Hydrostatic Dynamics Historically the Penn State/NCAR Mesoscale Model has been hydrostatic because typical horizontal grid sizes in mesoscale models are comparable with or greater than the vertical depth of features of interest. Therefore the hydrostatic approximation holds and the pressure is completely determined by the overlying air’s mass. However when the scale of resolved features in the model have aspect ratios nearer unity, or when the horizontal scale becomes shorter than the vertical scale, nonhydrostatic dynamics can not be neglected. MM5 Version 3 only supports the nonhydrostatic solver. The only additional term in nonhydrostatic dynamics is vertical acceleration that contributes to the vertical pressure gradient so that hydrostatic balance is no longer exact. Pressure perturbations from a reference state (described in the next section) together with vertical momentum become extra three-dimensional predicted variables that have to be initialized.
1.6 Reference State in the Nonhydrostatic Model The reference state is an idealized temperature profile in hydrostatic equilibrium. It is specified by the equation
T 0 = T s0 + Alog e ( p 0 ⁄ ( p 00 ) )
(1.2)
T0 (p0) is specified by 3 constants: p00 is sea-level pressure taken to be 105 Pa, Ts0 is the reference temperature at p00, and A is a measure of lapse rate usually taken to be 50 K, representing the temperature difference between p00 and p00/e = 36788 Pa. These constants are chosen in the INTERP program. Usually just Ts0 needs to be selected based on a typical sounding in the domain. The reference profile represents a straight line on a T-log p thermodynamic diagram. The accuracy of the fit is not important, and typically Ts0 is taken to the nearest 10 K (e.g. 270, 280, 290, 300 in polar, midlatitude winter, midlatitude summer, and tropical conditions, respectively). A closer fit however does reduce the pressure gradient force error associated with sloped coordinate surfaces over terrain, so Ts0 should be selected by comparison with the lower tropospheric profile. The surface reference pressure therefore depends entirely upon the terrain height. This can be derived from (1.2) using the hydrostatic relation, 2 RT RA ⎛ p 0 ⎞ s0 ⎛ p 0 ⎞ Z = – ------- ⎜ ln --------⎟ – ------------ ⎜ ln --------⎟ g ⎝ p 00⎠ 2g ⎝ p 00⎠
(1.3)
and this quadratic can be solved for p0 (surface) given Z, the terrain elevation. Once this is done, the heights of the model σ levels are found from
p 0 = p s0 σ + p top
MM5 Tutorial
(1.4)
1-11
1: INTRODUCTION
where
p s0 = p 0 ( surface ) – p top
(1.5)
and then (1.3) is used to find Z from p0. It can be seen that since the reference state is independent of time, the height of a given grid point is constant. Since Version 3.1 the reference state can include an isothermal layer at the top to better approximate the stratosphere. This is defined by a single additional temperature (Tiso) which acts as a lower limit for the base-state temperature. Using this effectively raises the model top height.
1.7 Four-Dimensional Data Assimilation In situations where data over an extended time period is to be input to the model, four-dimensional data assimilation (FDDA) is an option that allows this to be done. Essentially FDDA allows the model to be run with forcing terms that “nudge” it towards the observations or an analysis. The benefit of this is that after a period of nudging the model has been fit to some extent to all the data over that time interval while also remaining close to a dynamical balance. This has advantages over just initializing with an analysis at a single synoptic time because adding data over a period effectively increases the data resolution. Observations at a station are carried downstream by the model and may help fill data voids at later times. The two primary uses for FDDA are dynamical initialization and four-dimensional datasets. Dynamical initialization is where FDDA is used over a pre-forecast period to optimize the initial conditions for a real-time forecast. It has been shown that the added data is beneficial to forecasts compared to a static initialization from an analysis at the initial time. The second application, four-dimensional datasets, is a method of producing dynamically balanced analyses that have a variety of uses from budget to tracer studies. The model maintains realistic continuity in the flow and geostrophic and thermal-wind balances while nudging assimilates data over an extended period. Two methods of data assimilation exist that depend on whether the data is gridded or individual observations. Gridded data, taking the form of analyses on the model grid, are used to nudge the model point-by-point with a given time constant. This is often most useful on larger scales where an analysis can accurately represent the atmosphere between the observations that go into it. For smaller scales, asynoptic data, or special platforms such as profilers or aircraft, where full analyses cannot be made, individual observations may be used to nudge the model. Here each observation is given a time window and a radius of influence over which it affects the model grid. The weight of the observation at a grid point thus depends upon its spatial and temporal distance from the observation, and several observations may influence a point at a given time.
1.8 Land-Use Categories The model has the option of three sets of land-use categorizations (Table 4.2) that are assigned
1-12
MM5 Tutorial
1: INTRODUCTION
along with elevation in the TERRAIN program from archived data. These have 13, 16, or 24 categories (type of vegetation, desert, urban, water, ice, etc.). Each grid cell of the model is assigned one of the categories, and this determines surface properties such as albedo, roughness length, longwave emissivity, heat capacity and moisture availability. Additionally, if a snow cover dataset is available, the surface properties may be modified accordingly. The values in the table are also variable according to summer or winter season (for the northern hemisphere). Note that the values are climatological and may not be optimal for a particular case, especially moisture availability. A simpler land-use option distinguishes only between land and water, and gives the user control over the values of surface properties for these categories.
1.9 Map Projections and Map-Scale Factors The modeling system has a choice of several map projections. Lambert Conformal is suitable for mid-latitudes, Polar Stereographic for high latitudes and Mercator for low latitudes. The x and y directions in the model do not correspond to west-east and north-south except for the Mercator projection, and therefore the observed wind generally has to be rotated to the model grid, and the model u and v components need to be rotated before comparison with observations. These transformations are accounted for in the model pre-processors that provide data on the model grid, and post-processors. The map scale factor, m, is defined by m = (distance on grid) / (actual distance on earth) and its value is usually close to one varying with latitude. The projections in the model preserve the shape of small areas, so that dx=dy everywhere, but the grid length varies across the domain to allow a representation of a spherical surface on a plane surface. Map-scale factors need to be accounted for in the model equations wherever horizontal gradients are used.
1.10 Data Required to Run the Modeling System Since the MM5 modeling system is primarily designed for real-data studies/simulations, it requires the following datasets to run:
• Topography and landuse (in categories); • Gridded atmospheric data that have at least these variables: sea-level pressure, wind, temperature, relative humidity and geopotential height; and at these pressure levels: surface, 1000, 850, 700, 500, 400, 300, 250, 200, 150, 100 mb; • Observation data that contains soundings and surface reports. Mesouser provides a basic set of topography, landuse and vegetation data that have global coverage but variable resolution. The Data Support Section of Scientific Computing Division at NCAR has an extensive archive of atmospheric data from gridded analyses to observations. For information on how to obtain data from NCAR, please visit URL: http://www.scd.ucar.edu/dss/ index.html.
MM5 Tutorial
1-13
1: INTRODUCTION
1-14
MM5 Tutorial
2: GETTING STARTED
Getting Started
2
Purpose 2-3 Program portability 2-3 Prerequisite 2-4 Where to obtain program tar files? 2-5 What is Contained in a Program tar File? 2-7 Steps to run MM5 modeling system programs 2-7 Functions of Job Decks or Scripts 2-8 What to Modify in a Job Deck/Script? 2-8 Shell Variables 2-8 Parameter Statements 2-9 Fortran Namelist 2-9 How to Build the Executable and Run the Program? 2-10 Creating FORTRAN Executable 2-10 Linking files to Fortran units 2-10 Execution 2-10 Input Files 2-11 Output Files 2-11 Representation of Date in MM5 Modeling System Programs 2-11 Where to Find Data at NCAR? 2-12 Other Data Sources 2-14
MM5 Tutorial
2-1
2: GETTING STARTED
2-2
MM5 tutorial
2: GETTING STARTED
2
Getting Started
2.1 Purpose This chapter discusses general aspects of MM5 modeling system programs, including
• what are required on your computer in order to compile and run MM5 programs; • where and how to obtain program tar files and utility programs; • function of a job script (or a job deck); • parameter statement and namelist; • how to set up, compile and run the modeling system programs; • date representation in MM5 modeling system; • where to find data to run MM5. 2.2 Program portability MM5 modeling system programs, TERRAIN, REGRID, LITTLE_R/RAWINS, INTERPF, NESTDOWN, INTERPB, RIP/GRAPH and MM5, can all be run on Unix workstations, PC running Linux, Cray’s and IBM’s. Running MM5 programs on a Linux PC requires either the Portland Group, or INTEL Fortran and C compilers. The primary reasons for these choices are 1) they supports Cray pointers which are used in several programs, including MM5 model; and 2) they have Fortran 90 compilers. MM5 modeling system programs are mostly Fortran programs that require compilation on your local computer. Some (Fortran 77) programs need recompilation each time you change model configuration. Others (Fortran 90) programs need only be compiled once. A user should try to know your computer and compiler. Find out how much usable memory you have on the computer, and what version of compiler you have. This information can come handy when you encounter problems when compiling and running the modeling system programs and report problems to mesouser. If you are thinking about purchasing a computer, get at least 0.5 to 1 Gb memory and a few Gb of disk. As most of the MM5 preprocessor programs are being migrated to Fortran 90, you will need a f90 compiler too to compile the programs. The following table lists the source code type and compiler required to compile them: MM5 Tutorial
2-3
2: GETTING STARTED
Program Name
Source Code
Compiler required
TERRAIN
Fortran 77
f77 (or f90)
REGRID
Fortran 90
f90
LITTLE_R
Fortran 90
f90
RAWINS
Fortran 77
f77 (or f90)
INTERPF
Fortran 90
f90
MM5
Fortran 77
f77 (or f90)
NESTDOWN
Fortran 90
f90
INTERPB
Fortran 90
f90
RIP/GRAPH
Fortran 77
f77 (or f90)
MM5 programs do not require NCAR Graphics to run. It is a matter of convenience to have it, since a few programs use it to help you configure model domains and prepare data. Some of the vitualization software that come with the MM5 system (RIP and GRAPH programs) is based on NCAR Graphics. NCAR Graphics is a licensed software, but part of it has become free and this is the part that MM5 modeling system requires. For more information on NCAR Graphics, please see its Web page: http://ngwww.ucar.edu/.
2.3 Prerequisite There are a few things a user needs to prepare before starting running jobs on your workstation.
• If you have NCAR Graphics on your system, make sure you have the following line in your .cshrc file:
setenv NCARG_ROOT /usr/local or setenv NCARG_ROOT /usr/local/ncarg This enables a user to load NCAR Graphics libraries when compiling programs which use NCAR Graphics (Terrain, Little_r, Rawins, RIP and Graph).
• If you need to remotely copy files between two workstations, make sure you have an .rhosts file on both workstations. A typical .rhosts file looks like this: chipeta.ucar.edu username blackforest.ucar.edu username
• Make sure that you browse through the ~mesouser directories on the NCAR’s computers, or mesouser/ directory on anonymous ftp. All job decks, program tar files, data catalogs, and utility programs reside in the directory.
2-4
MM5 Tutorial
2: GETTING STARTED
2.4 Where to obtain program tar files? MM5 modeling system programs are archived in three locations: NCAR’s anonymous ftp, NCAR IBM-accessible disk, and NCAR’s Mass Storage System (MSS). On the ftp site, the source code tar files are archived under /mesouser/MM5V3: /mesouser/MM5V3/TERRAIN.TAR.gz /mesouser/MM5V3/REGRID.TAR.gz /mesouser/MM5V3/LITTLE_R.TAR.gz /mesouser/MM5V3/RAWINS.TAR.gz /mesouser/MM5V3/INTERPF.TAR.gz /mesouser/MM5V3/MM5.TAR.gz /mesouser/MM5V3/MPP.TAR.gz /mesouser/MM5V3/NESTDOWN.TAR.gz /mesouser/MM5V3/INTERPB.TAR.gz /mesouser/MM5V3/GRAPH.TAR.gz /mesouser/MM5V3/RIP4.TAR.gz /mesouser/MM5V3/RIP.TAR.gz /mesouser/MM5V3/FETCH.TAR.gz /mesouser/mm53dvar/3dvar.tar.gz On NCAR’s IBM, the source code tar files and job decks reside in ~mesouser/MM5V3: ~mesouser/MM5V3/TERRAIN.TAR.gz ~mesouser/MM5V3/REGRID.TAR.gz ~mesouser/MM5V3/INTERPF.TAR.gz ~mesouser/MM5V3/LITTLE_R.TAR.gz ~mesouser/MM5V3/RAWINS.TAR.gz ~mesouser/MM5V3/MM5.TAR.gz ~mesouser/MM5V3/MPP.TAR.gz ~mesouser/MM5V3/NESTDOWN.TAR.gz ~mesouser/MM5V3/INTERPB.TAR.gz ~mesouser/MM5V3/GRAPH.TAR.gz ~mesouser/MM5V3/RIP4.TAR.gz ~mesouser/MM5V3/RIP.TAR.gz ~mesouser/MM5V3/FETCH.TAR.gz ~mesouser/MM5V3/CRAY/*.deck.cray ~mesouser/MM5V3/IBM/*.deck On MSS, the source code tar files are archived in /MESOUSER/MM5V3 /MESOUSER/MM5V3/TERRAIN.TAR.gz /MESOUSER/MM5V3/REGRID.TAR.gz /MESOUSER/MM5V3/INTERPF.TAR.gz /MESOUSER/MM5V3/LITTLE_R.TAR.gz /MESOUSER/MM5V3/RAWINS.TAR.gz /MESOUSER/MM5V3/MM5.TAR.gz /MESOUSER/MM5V3/MPP.TAR.gz /MESOUSER/MM5V3/NESTDOWN.TAR.gz /MESOUSER/MM5V3/INTERPB.TAR.gz MM5 Tutorial
2-5
2: GETTING STARTED
/MESOUSER/MM5V3/GRAPH.TAR.gz /MESOUSER/MM5V3/RIP4.TAR.gz /MESOUSER/MM5V3/RIP.TAR.gz /MESOUSER/MM5V3/FETCH.TAR.gz Previous releases are also available on ftp and MSS. To obtain files from IBM and MSS, you need to have an NCAR SCD computing account. To access program tar files from NCAR’s anonymous ftp site, do the following (taking MM5 tar file as an example): # ftp ftp.ucar.edu Name: anonymous Password: your-email-address ftp> cd mesouser/MM5V3 ftp> binary ftp> get MM5.TAR.gz ftp> quit Once you download these tar files, use Unix gunzip command to decompress the .gz files, gunzip MM5.TAR.gz and untar the file by using the command tar -xvf MM5.TAR After you untar the file, a program directory will be created. In this example, an MM5 directory will be created with all source code files inside it. All utility programs are archived under MM5V3/Util/ directory on ftp and NCAR IBM-accessible disk. The list of the utility programs are:
Program/script Name
Function
cray2ibm.f
convert Cray MM5 binary data to IBM binary data
cray2ibm-intermediate.f
convert Cray intermediate binary data to IBM binary data
ieeev3.csh
convert Cray binary data to standard 32-bit IEEE data
readv3.f
read program for MM5 V3 modeling system output
v22v3.tar.gz
program tar file to convert V2 data to V3
v32v2.tar.gz
program tar file to convert V3 MM5 model data to V2
tovis5d.tar.gz
program tar files to convert MM5 model data to Vis5D data
MM5toGrADS.TAR.gz
program tar files to convert MM5 model data to GrADS data
2-6
MM5 Tutorial
2: GETTING STARTED
2.5 What is Contained in a Program tar File? A program tar file contains all source code (excluding NCAR Graphics), makefile, and instructions (in README file) required to compile and run that particular program. As an example, the files contained in program RAWINS tar file are listed below: CHANGES Diff/ Makefile README Templates/ con.tbl map.tbl src/
Description of changes to the program Will contain difference files between consecutive releases Makefile to create the program executable General information about the program directory Job script directory Table file for plots Table file for plots Program source code directory and low-level makefile
2.6 Steps to run MM5 modeling system programs Typically there are several steps to set up and run the modeling system programs. For detailed instruction on how to compile and run a particular program, read the respective chapter and README file inside the tar file. For FORTRAN 77 programs TERRAIN, and RAWINS: 1) Type make x.deck to create job script to compile and run the program. 2) Edit x.deck to select appropriate shell variables, parameter statements, and namelist. 3) Type x.deck to (compile and) run the program. For FORTRAN 77 program GRAPH: 1) Edit include files if necessary. 2) Type make to create the program executable. 3) Type graph.csh n m mm5-modeling-system-output-file to run. For FORTRAN 90 programs REGRID, LITTLE_R, INTERPF, INTERPB and NESTDOWN: 1) Type make to compile the program. 2) Edit either the job script and/or namelist.input file. 3) Type the executable name to run the program, e.g. regridder
MM5 Tutorial
2-7
2: GETTING STARTED
2.7 Functions of Job Decks or Scripts Most of MM5 modeling system programs have a job deck or script to help you run the program. Some are called x.deck, and some are x.csh. While x.deck can be used either for a batch job (such as on an IBM) or interactive job, x.csh is only for interactive use. They have very similar functions. When using these job decks or scripts, they assume the program source code is local. Most also expect all input files are local too. To obtain an appropriate job script for your computer, type ‘make x.deck’ to create a deck for program x (program name in lower case, e.g. make terrain.deck). The general job deck construct and functions are the following:
• job switches, which usually appear in the first part of a deck; • parameter statements used in Fortran 77 programs to define domain and data dimensions; • FORTRAN namelist used during program execution to select runtime options; • a section that does not normally require user modification, which links input files to Fortran units, create executable based on parameter statement setup, and obtain data from anonymous ftp sites (such as in the case of TERRAIN program)
2.8 What to Modify in a Job Deck/Script? 2.8.1 Shell Variables Since the MM5 modeling system is designed for multiple applications, there are many options on how a job may be run. These options include different sources for inputting terrestrial and meteorological data, ways to do objective analysis, running the model with or without 4DDA option, and whether an MM5 job is an initial or restart run, etc. A user is required to go through the shell variables and make appropriate selections for your application. The following is an example taken from the pregrid.csh, and the selection is with regarding to the type of global analysis to be used to create the first guess fields: # # Select the source of 3-d analyses # # #
set SRC3D = ON84 set SRC3D = NCEP set SRC3D = GRIB
# Many GRIB-format datasets
Other examples of shell variables are listed below and they need to be defined by users for each program of the MM5 modeling system: Program Name TERRAIN REGRID/pregrid RAWINS MM5
Shell Variables ftpdata,Where30sTer SRC3D,SRCSST,SRCSNOW,SRCSOIL,VTxxx INOBS, SFCsw, BOGUSsw,InRaobs,InSfc3h,InSfc6h STARTsw, FDDAsw (in IBM batch deck only)
These shell variables will be discussed in detail in the other chapters of this document. 2-8
MM5 Tutorial
2: GETTING STARTED
2.8.2 Parameter Statements The FORTRAN 77 MM5 modeling system programs require a user to set parameter statements in a deck or script (TERRAIN and RAWINS), or directly in an include file (GRAPH), which are typically used to define the parameterized dimensions for a FORTRAN 77 program before compilation takes place. The unix cat command is used in a deck to create FORTRAN include files containing these parameter statements. These are direct modifications to the source code, implying that strict FORTRAN syntax must be observed. The usage of cat is shown below: cat > src/param.incl src/parame.incl.tmp nml &! X.print.out, or time ./X.exe >& X.print.out Where X is the program name. And Unix command timex or time is used to get a timing of the executable run. Example: # # run MM5 # timex mm5.exe >&! mm5.print.out
2-10
MM5 Tutorial
2: GETTING STARTED
At the end of your mm5.print.out file, you will see something like: real user sys
1028.8 1009.7 2.4
which tells you how long the mm5 job has taken in terms of wallclock time (real).
2.10 Input Files MM5 modeling system programs require several datasets to run. Mesouser provides the terrestrial datasets for program TERRAIN. Programs REGRID, LITTLE_R and RAWINS will require other archived data or data in real-time to run. Since V3.6, maximum snow albedo data at 1 degree resolution can be ingetsted into the model via REGRID using the ALMX_FILE file which is supplied with the REGRID.TAR.gz file. It is suggested that this file be used if one intends to use the Noah LSM option in MM5. Monthly albedo fields at 0.15 degree resolution can also be ingested via REGRID for Noah LSM use. These data are available from /MESOUSER/DATASETS/REGRID/MONTHLY_ALBEDO.TAR.gz, or from ftp://ftp.ucar.edu/mesouser/MM5V3/REGRID_DATA/MONTHLY_ALBEDO.TAR.gz
2.11 Output Files When a job is completed, certain output files are generated, which are named programname_DOMAINx (e.g., REGRID_DOMAIN1, LITTLE_R_DOMAIN1, etc.). It is up to the user to archive the output. If you want to keep the output files, move them to a disk where you can keep them. If you run the same program again, these files will be overwritten.
2.12 Representation of Date in MM5 Modeling System Programs Date is represented in the MM5 modeling system programs by up to 24 characters in the form of yyyy-mm-dd_hh:mm:ss:xxxx, where yyyy represents 4-digit year, mm 2-digit month, dd 2-digit day, hh 2-digit hour, mm (again) 2-digit minutes, ss 2 digit second, and xxxx ten thousandths of a second (optional). This replaces the 8-digit integer date representation, YYMMDDHH, in previous modeling system codes. For example, 1200 UTC 24 January 2005 is represented as 2005-0124_12:00:00 in the model. Note that all model times are referring to Universal Time or Greenwich Mean Time, and not local time.
MM5 Tutorial
2-11
2: GETTING STARTED
2.13 Where to Find Data at NCAR? The Data Support Section of NCAR’s Scientific Computing Division provides catalogs of data MM5 modeling system programs REGRID and LITTLE_R/RAWINS use. These catalogs are available from the Data Support Section of NCAR/SCD: http://dss.ucar.edu/datasets/dsNNN.x/MSS-file-list.html or ftp://ncardata.ucar.edu/datasets/dsNNN.x where NNN.x is a dataset identifier. Most datasets that MM5 uses are listed below: Dataset Identifier
Dataset Name
DS082.0
NCEP GLOBAL TROPO ANALS, DAILY 1976JUL-1997MAR
DS083.0
NCEP GLOBAL TROPO ANALS, DAILY 1997MAY-CON (GRIB)
DS083.2
NCEP Final Analysis (GRIB, 1 degree resolution) 1999SEP15 - CON
DS090.0
NCEP/NCAR Global Reanalysis, 6 hourly, monthly (1948-Current)
DS111.2
ECMWF TOGA GLOBAL SFC & UPPER AIR ANALS, DAILY 1985-CON
DS115
ECMWF Global Reanalysis (1979-1993)
DS118
ECMWF Global Reanalysis (ERA40), 1957SEP-2002AUG
DS609.2
NCEP Eta model output (GRID212) 1995MAY01- CON
DS240.0
U.S. NAVY FNOC N.HEM SEA SFC TEMP ANALS, DAILY 1961NOV1993DEC
DS353.4
NCEP ADP GLOBAL UPPER AIR OBS SUBSETS, DAILY 1973-CON
DS464.0
NCEP ADP GLOBAL SFC OBS, DAILY JUL1976-CON
Information on NCEP/NCAR Reanalysis Project (NNRP) and on European Center Reanalysis can be found at URL http://dss.ucar.edu/pub/reanalyses.html The NCEP Eta model data (the AWIP data, GRID 212), NCEP Final Analysis and ECMWF ERA40 are recent additions to NCAR’s archive. Information about the data can be found at: http://dss.ucar.edu/datasets/ds609.2.html http://dss.ucar.edu/datasets/ds083.2.html http://dss.ucar.edu/datasets/ds118.0.html and http://dss.ucar.edu/datasets/ds118.1.html
2-12
MM5 Tutorial
2: GETTING STARTED
When choosing to run the Noah land-surface model option in MM5, one can use the NNRP, AWIP or Final Analysis datasets at NCAR. These datasets contain additional fields required by LSM to initialize soil temperature and moisture. A recent addition which can also be used as input to the Noah LSM option, is the AGRMET data supplied by AFWA. AGRMET data provides soil temperature, soil moisture, soil water, land-sea mask and soil height data. One can use this dataset in combination with any other 3-dimensional meteorological analyses. This dataset can be obtained from: /MESOUSER/DATASETS/AGRMET/ This data is available since October 2002. Documentation regarding this data is available from: http://www.mmm.ucar.edu/mm5/mm5v3/data/agrmet.html
A sample of the catalog for NCEP dataset DS083.0 is shown below: Y47606 Y48077 Y48277
1998OCT01-1998OCT31, 12524 BLKS, 1998NOV01-1998NOV30, 12120 BLKS, 1998DEC01-1998DEC31, 12524 BLKS,
86.0MB 83.3MB 85.9MB
The MSS filenames correspond to these files are /DSS/Y47606 /DSS/Y48077 /DSS/Y48277 A sample of the catalog for NCEP Global upper air observation dataset DS343.4 looks like Y47652 Y48086 Y48286
1998OCT01-1998OCT31, 9096 BLKS LIST 1998NOV01-1998NOV30, 8688 BLKS LIST 1998DEC01-1998DEC31, 8541 BLKS, SEE NOTES - LIST NOTE:ADPUPA 1998DEC15 MISSING LIST
A98 A98 A98 A98
Similarly, the MSS file name corresponding to the Oct 1998 dataset is /DSS/Y47625 File specifics for all global analysis used as input to REGRID are no longer required. Shell scripts are provided to access the data MASTER file, find the MSS file names, and obtain them based on user selected data source and date. If you run LITTLE_R or RAWINS at your local computer, you will still need to go to the catalog, find the file name on MSS, and access them from NCAR’s computer. Note that you need to use -fBI option with msread to obtain observations to be used on your workstation. A small utility program, fetch.csh, may be used to obtain observational data too. NCAR has a couple of free data sets available from the NCAR/DSS web site. These data sets are updated monthly, and are available for the latest 12 months. The free data sets are:
MM5 Tutorial
2-13
2: GETTING STARTED
DS083.0
NCEP GLOBAL TROPO ANALS, DAILY 1997MAY-CON (GRIB)
DS083.2
NCEP Final Analysis (GRIB, 1 degree resolution) 1999SEP15 - CON
DS090.0
NCEP/NCAR Global Reanalysis, 6 hourly, monthly (1948-Current)
DS353.4
NCEP ADP GLOBAL UPPER AIR OBS SUBSETS, DAILY 1973-CON
DS464.0
NCEP ADP GLOBAL SFC OBS, DAILY JUL1976-CON
For more information on the free data sets, see: http://www.mmm.ucar.edu/mm5/mm5v3/data/free_data.html If you don’t have access to NCAR’s data, you need to consider where you can obtain similar data to run the modeling system.
2.14 Other Data Sources Seaice fractional data is available from the Near Real-TimeSSM/I EASE-Grid Daily Global Ice Concentration and Snow Extent. Boulder, CO, USA: National Snow and Ice Data Center. This data can be obtained from their web site: http://nsidc.org/data/nise1.html Please become a registered user before downloading data (no charge). SST data on a 0.5 degree grid is available from NCEP’s ftp server: ftp://ftpprd.ncep.noaa.gov/ pub/emc/mmab/history/sst Files names has the format: rtg_sst_grib_0.5.YYYYMMDD This data is in GRIB format and is available since Febuaray 2001. If you are interested in running MM5 in real-time, a good source of data can be obtained from NCEP’s ftp server: ftp://ftpprd.ncep.noaa.gov/pub/data/nccf/com. NCEP provides a number of datasets from their global and regional models at this site. For example, NAM/Eta 40 km data: nam/prod/nam.YYYYMMDD/nam.tXXz.grbgrbYY.tm00 (eg. nam/prod/nam.20021223/nam.t18z.grbgrb12.tm00 ) GFS/AVN 1deg data: gfs/prod/gfs.YYYYMMDD/gfs.tXXz.pgrbfYY (eg. gfs/prod/gfs.20021223/gfs.t12z.pgrbf12 )
2-14
MM5 Tutorial
3: MAKE UTILITY
MAKE UTILITY
3
The UNIX make Utility 3-3 make Functionality 3-3 The Makefile 3-4 Sample make Syntax 3-5 Macros 3-5 Internal Macros 3-5 Default Suffixes and Rules 3-6 Sample Program Dependency Chart 3-7 Sample Program Components for make Example 3-8 makefile Examples for the Sample Program 3-9 Make Command Used in MM5 Preprocessing Programs 3-10 An Example of Top-level Makefile 3-10 An Example of Low-level Makefile 3-13
MM5 Tutorial
3-1
3: MAKE UTILITY
3-2
MM5 tutorial
3: MAKE UTILITY
3
MAKE UTILITY
3.1 The UNIX make Utility The following chapter is designed to provide the MM5 user with both an overview of the UNIX make command and an understanding of how make is used within the MM5 system. UNIX supplies the user with a broad range of tools for maintaining and developing programs. Naturally, the user who is unaware of their existence, doesn’t know how to use them, or thinks them unnecessary will probably not benefit from them. In the course of reading this chapter it is hoped that you not only become aware of make but that you will come to understand why you need it. In the same way you use dbx when you want to “debug” a program or sort when you need to sort a file, so you use make when you want to “make” a program. While make is so general that it can be used in a variety of ways, its primary purpose is the generation and maintenance of programs. But why the bother of a separate make utility in the first place? When you wrote your first program it probably consisted of one file which you compiled with a command such as “f77 hello.f”. As long as the number of files is minimal you could easily track the modified files and recompile any programs that depend on those files. If the number of files becomes larger you may have written a script that contains the compiler commands and reduces the amount of repetitive typing. But as the number of files increases further your script becomes complicated. Every time you run the script every file is recompiled even though you have only modified a single file. If you modify an include file it is your responsibility to make sure that the appropriate files are recompiled. Wouldn’t it be nice to have something that would be smart enough to only recompile the files that need to be recompiled? To have something that would automatically recognize that a buried include file have been changed and recompile as necessary? To have something that would optimize the regeneration procedure by executing only the build steps that are required. Well, you do have that something. That something is make. When you begin to work on larger projects, make ceases to be a nicety and becomes a necessity.
3.2 make Functionality
MM5 Tutorial
3-3
3: MAKE UTILITY
The most basic notion underlying make is that of dependencies between files. Consider the following command: f77 -o average mainprog.o readit.o meanit.o printit.o Consider the object file mainprog.o and its associated source code file mainprog.f. Since a change in mainprog.f necessitates recompiling mainprog.o, we say that mainprog.o is dependent upon mainprog.f. Using the same reasoning we see that the final program average is dependent upon mainprog.o. average in this context is the target program (the program we wish to build). In this fashion we can build up a tree of dependencies for the target, with each node having a subtree of its own dependencies (See Figure 3.1). Thus the target average is dependent upon both mainprog.o and mainprog.f, while mainprog.o is dependent only upon mainprog.f. Whenever mainprog.f is newer than mainprog.o, average will be recompiled. make uses the date and time of last modification of a file to determine if the dependent file is newer than the target file. This is the time you see when using the UNIX ls command. By recognizing this time relationship between target and dependent, make can keep track of which files are up-to-date with one another. This is a reasonable approach since compilers produce files sequentially. The creation of the object file necessitates the pre-existence of the source code file. Whenever make finds that the proper time relationship between the files does not hold, make attempts to regenerate the target files by executing a user-specified list of commands, on the assumption that the commands will restore the proper time relationships between the source files and the files dependent upon them. The make command allows the specification of a heirarchical tree of dependency relationships. Such relationships are a natural part of the structure of programs. Consider our program average (See Figure 3.1). This application consists of 6 include files and four source code files. Each of the four source code files must be recompiled to create the four object files, which in turn are used to create the final program average. There is a natural dependency relationship existing between each of the four types of files: include files, FORTRAN sources, object, and executables. make uses this relationship and a specification of the dependency rules between files to determine when a procedure (such a recompilation) is required. make relieves people who are constantly recompiling the same code of the tedium of keeping track of all the complexies of their project, while avoiding inefficiency by minimizing the number of steps required to rebuild the executable.
3.3 The Makefile Even with a small number of files the dependency relationships between files in a programming project can be confusing to follow. In the case of mm5 with hundreds of files, an English description would be unuseable. Since make requires some definition of the dependencies, it requires that you prepare an auxillary file -- the makefile -- that describes the dependencies between files in the project. There are two kinds of information that must be placed in a makefile: dependency relations and generation commands. The dependency relations are utilized to determine when a file must be regenerated from its supporting source files. The generation commands tell make how to build out-of-date files from the supporting source files. The makefile therefore contains two distinct line formats: one called rules, the other commands.
3-4
MM5 Tutorial
3: MAKE UTILITY
3.4 Sample make Syntax targetfile : < tab > < tab >
dependencies command1 command2
myprog.exe: mysource1.f mysource2.f < tab > f77 -o myprog.exe mysource1.f mysource2.f A rule begins in the first position of the line and has the following format: targetfile: dependencies. The name or names to the left of the colon are the names of target files. The names to the right of the colon are the files upon which our target is dependent. That is, if the files to the right are newer than the files to the left, the target file must be rebuilt. A dependency rule may be followed by one or more command lines. A command line must begin with at least one tab character; otherwise, it will not be recognized by make and will probably cause make to fail. This is a common cause of problems for new users. Other than this, make places no restrictions are command lines - when make uses command lines to rebuild a target, it passes them to the shell to be executed. Thus any command acceptable to the shell is acceptable to make.
3.5 Macros make Macro definitions and usage look very similar to UNIX environment variables and serve much the same purpose. If the Macro STRING1 has been defined to have the value STRING2, then each occurrence of $(STRING1) is replaced with STRING2. The () are optional if STRING1 is a single character. MyFlags = -a -b -c -d In this example every usage of $(MyFlags) would be replaced by make with the string “-a -b -c d” before executing any shell command.
3.6 Internal Macros $@
name of the current target
$
MM5 Tutorial
6: OBJECTIVE ANALYSIS
set ExpName set RetPd # # # # # # # # # #
= MM5V3/TEST = 365
# MSS path name for output # MSS retention period in days
The only user inputs to the fetch program are the beginning and ending dates of the observations, and a bounding box for the observation search. These dates are given in YYYYMMDDHH. The ADP data are global, and include the surface observations and upper-air soundings. A restrictive bounding box (where possible) reduces the cost substantially. Note: No observational data are available prior to 1973, and no or limited surface observations are available prior to 1976.
set starting_date = 1993031300 set ending_date = 1993031400 set set set set
lon_e lon_w lat_s lat_n
= 180 = -180 = -90 = 90
######################################################### ######### ######### ######### END OF USER MODIFICATIONS ######### ######### ######### #########################################################
MM5 Tutorial
6-23
6: OBJECTIVE ANALYSIS
6-24
MM5 Tutorial
7: INTERPF
INTERPF
7
Purpose 7-3 INTERPF Procedure 7-3 Surface Pressure Computation 7-5 Hydrostatic Vertical Interpolation 7-6 Integrated Mean Divergence Removal 7-6 Base State Computation 7-8 Initialization of Nonhydrostatic Model 7-9 Substrate Temperature and the LOWBDY_DOMAINn file 7-9 Shell Variables (for IBM job deck only) 7-10 Parameter Statements 7-10 FORTRAN Namelist Input File 7-11 How to Run INTERPF 7-12 INTERPF didn’t Work! What Went Wrong? 7-13 File I/O 7-14 INTERPF tar File 7-15
MM5 Tutorial
7-1
7: INTERPF
7-2
MM5 tutorial
7: INTERPF
7
INTERPF
7.1 Purpose The INTERPF program handles the data transformation required to go from the analysis programs to the mesoscale model. This entails vertical interpolation, diagnostic computation, and data reformatting. INTERPF takes REGRID, RAWINS, LITTLE_R, or INTERPB output data as input to generate a model initial, lateral boundary condition and a lower boundary condition. The INTERPF program runs on the following platforms: HP/Compaq/Alpha, Cray, Fujitsu, HP, IBM, SGI, Sun, PCs running Linux (Fedora with PGI or Intel compilers), and MAC (OSX with xlf). The INTERPF code is written in FORTRAN 90.
7.2 INTERPF Procedure • input LITTLE_R, RAWINS, REGRID, or INTERPB data • pressure level Qv for Psfc • interpolate variables from pressure coordinates to hydrostatic σ • u, v, RH: linear in pressure • theta: linear in ln pressure • remove integrated mean divergence • compute base state • compute w • re-interpolate u, v, t, Qv,(optionally QC, QR, QI, QS, QG) • compute perturbation pressure • save Tsfc and SST for daily mean for lower boundary file • output current data for boundary file • output interpolated data for initial conditions • output data for lower boundary file
MM5 Tutorial
7-3
7: INTERPF
REGRID
LITTLE_R / RAWINS
INTERPF
INTERPB
MM5
NESTDOWN
Fig 7.1 MM5 modeling system flow chart for INTERPF.
7-4
MM5 Tutorial
7: INTERPF
7.3 Surface Pressure Computation Please note that the “X” used in the following computations throughout the entire chapter signifies an arithmetic multiplication, not a cross product. 1. first guess for representative T, p 100 hPa above surface
P slv –TER ⁄ H 850 ⎛ P sfc = P slv ----------⎞ ⎝ 850 ⎠
(7.1)
⎛ P slv ⎞ γ T slv = T 100 – up ⎜ ----------------------⎟ ⎝ P 100 – up⎠
(7.2)
2. extrapolate Tslv
T 850 ln ----------T 700 γ = ---------------- , 850 ln --------700
if 700 ≤ P 100 – up ≤ 850
(7.3)
3. corrected Tsfc
T sfc = T slv – γ s × TER
(7.4)
4a. use mean temperature underground to estimate surface pressure
⎧ -TER × g 1 ⎫ P sfc = P slv exp ⎨ ---------------------- ⁄ --- × ( T sfc + T slv ) ⎬ R 2 ⎩ ⎭
(7.5)
4b. OR use daily mean surface temperature to compute surface pressure
P sfc = P slv
MM5 Tutorial
– g------γ S × TER Rγ S
⎛ 1 + -----------------------⎞ ⎝ Tavg ⎠
(7.6)
7-5
7: INTERPF
7.4 Hydrostatic Vertical Interpolation The process of going from pressure levels to the σ coordinate requires only strictly bounded interpolation. Since the σ coordinate is defined to be contained within the maximum and minimum pressure, no extrapolations are required. A generated surface field is available as a coding option inside INTERPF via the namelist. Vertical interpolation uses linear techniques exclusively, typically linear in pressure or linear in ln pressure. Hydrostatic pressure is defined as *
P ijk = σ k × p ij + P top
(7.7)
where σ is a 1-D vertical coordinate, σ=1 at the ground, σ=0 at the model lid; p* is the arithmetic difference of the 2-D field of surface pressure and a constant (Ptop); and Ptop is the constant pressure at the model lid.
αP ( PB – Pσ ) + αP ( Pσ – PA ) A B α σ = --------------------------------------------------------------------------PB – PA
(7.8)
Pa, αa Pσ, ασ Pb, αb
1
2
3
Fig. 7.2 A vertical profile of a σ surface cutting through several isobaric layers. The heavy dot is the location on the σ surface for which a vertical interpolation is requested. The arrows (labeled 1 through 3) represent consecutive grid points that use three separate surrounding layers along a σ surface.
7.5 Integrated Mean Divergence Removal Removing the integrated mean divergence allows the model to begin with a smaller amount of ini7-6
MM5 Tutorial
7: INTERPF
tial condition noise that the analysis contains. Given the average upper-air station separation, the reasonableness of the high frequency, column-averaged vertical motion is spurious at best. Again, the computations are scalar, and the “X” signifies scalar multiplication. 1. pressure weighted u, v on each σ *
*
PU ijk = p ij × u ijk , PV ijk = p ij × v ijk
(7.9)
2. vertically average p*u, p*v
U integ = ij
∑ PUijk × ∆σk , Vinteg
ij
=
∑ PVijk × ∆σk
(7.10)
k k 3. divergence of vertically-averaged pressure-weighted wind [m is the map scale factor for dot (D) and cross (X)]
∆ ( U integ ⁄ m D ) ∆ ( V integ ⁄ m D ) 2 ij ij - + -------------------------------------DIV ij = m X -------------------------------------∆x ∆y
(7.11)
4. solve for the velocity potential, with assumed boundary conditions
∇2χ ij = DIV ij , χ ij ≡0 boundary
(7.12)
5. mean divergent wind components
m D ∆χ m D ∆χ U DIV = -------- ------- , V DIV = -------- ------* * ij ij p ∆x p ∆y
(7.13)
6. vertical weighting
require:
∑ wk × ∆σk= 1 ,
(7.14)
k
presently: w k =2 ( 1-σk )
MM5 Tutorial
(7.15)
7-7
7: INTERPF
7. corrected wind components
U corrected
ijk
= u ijk – U DIV × w k , V corrected = v ijk – V DIV × w k ij ijk ij
(7.16)
7.6 Base State Computation The base state for the MM5 model is constructed from several constants prescribing a surface level temperature and pressure, a temperature profile which may include an isothermal layer above the tropopause, and analytic expressions for a reference pressure and the height of the nonhydrostatic σ surfaces. Other than the terrain elevation only these constants are required by the modeling system as user input to completely define the base state. 1. constants
• P00: reference sea level pressure (in the INTERPF namelist) • Ts0: reference sea level temperature (in the INTERPF namelist) • A: reference temperature lapse rate (in the INTERPF namelist) • PTOP: reference pressure at model top (in the REGRIDDER and INTERPF namelists) • TISO: (optional) temperature at which the reference temperature becomes constant (possibly for use in modeling the stratosphere) (in the INTERPF namelist)
2. reference p*
P s0 =
1--⎧ ⎫ 2⎪ T s0 2 ⎪ – T s0 TER P 00 exp ⎨ ----------- + ⎛ --------⎞ – 2g ------------- ⎬– P TOP ⎝ A⎠ A×R ⎪ ⎪ A ⎩ ⎭
(7.17)
3. reference pressure 3-D
P 0 = P s0 × σ + P TOP
(7.18)
P0 T 0 = T s0 + Aln --------P 00
(7.19)
4. reference temperature 3-D
5. reference height 2 R×T R × A ⎛ P0 ⎞ s0 P 0 ----------------------------------- ln --------z = – ⎜ ln ⎟ + 2g ⎝ P 00⎠ P 00 g 7-8
(7.20) MM5 Tutorial
7: INTERPF
This provides a fixed (in time) height for each σ surface, since each i,j,k location is a function of the fixed σ values and the terrain elevation. If the user has requested the use of the isothermal temperature option from the namelist, the temperature and height computations are modified. First, the minimum temperature allowable is defined as the isothermal temperature. The pressure at the location for the switch to the isothermal temperature is computed. From this pressure (PISO), the isothermal height is found, and then the adjusted reference height.
⎛ R × A ⎛ ⎛ P ISO⎞ ⎞ 2 R × T s0 ⎛ P ISO⎞ ⎞ -------------------------------------× ⎜ ln ⎜ × ln ⎜ ------------⎟ ⎟ Z ISO = – ⎜ ⎟⎟ + g P 2g ⎝ ⎝ ⎝ 00 ⎠ ⎠ ⎝ P 00 ⎠ ⎠
(7.21)
R × T ISO ⎛ P0 ⎞ --------------------× ln ⎜ ------------⎟ z = Z ISO – g ⎝ P ISO⎠
(7.22)
7.7 Initialization of Nonhydrostatic Model INTERPF first generates a hydrostatic input file on the hydrostatic sigma levels which is based on actual surface pressure, not reference pressure. To initialize the data for the nonhydrostatic model a further small vertical interpolation is needed to move to the nonhydrostatic sigma levels. This involves first calculating the heights of the hydrostatic levels, then doing a linear-in-height interpolation of u, v, T and q to the nonhydrostatic levels. While sea-level pressure, u, v, T and q are known from the input data sets, the nonhydrostatic model requires two more variables to be initialized.
• Vertical velocity (w) is simply calculated from the pressure velocity (ω) obtained by integrating horizontal velocity divergence vertically while still on the hydrostatic sigma levels. Divergence removal has already ensured that this integration will give no vertical motion at the top of the model domain. This ω is then interpolated to the nonhydrostatic levels and converted to w (w=-ω/ρg). In practice, the results are not sensitive to whether w is initialized this way or equal to zero.
• Pressure perturbation (p′) has to be initialized to give a hydrostatic balance. Once virtual
temperature is known on the nonhydrostatic model levels, the model’s vertical velocity equation in finite difference form is used with the acceleration and advection terms set to zero. This leaves a relation between Tv(z) and the vertical gradient of p′. Given the sealevel pressure, p′ at the lowest sigma level can be estimated, and then given the profile of virtual temperature vertical integration gives p′ at the other levels. This balance ensures that the initial vertical acceleration is zero in each model column.
7.8 Substrate Temperature and the LOWBDY_DOMAINn file There are three primary binary output files from the INTERPF program: MMINPUT_DOMAINn,
MM5 Tutorial
7-9
7: INTERPF
BDYOUT_DOMAINn and LOWBDY_DOMAINn. The MMINPUT_DOMAINn file contains the time dependent 3D and 2D fields, such as wind, temperature, moisture and pressure. The BDYOUT_DOMAINn file contains the lateral boundaries of the 3D fields, typically, four rows worth of data. The LOWBDY_DOMAINn file contains either daily means of, or time-varying surface temperature fields (surface air temperature and sea surface temperature), and optionally sea-ice and snow cover fields. The surface air temperature is either the temperature field defined at the surface from the input pressure-level data set (typically), or the lowest σ-level temperature field (if the namelist option was set to not use the input surface data in the vertical interpolation). This field is used as the constant, deep-soil temperature whenever the land surface model is not selected. The variable used as the sea surface temperature in REGRID is not well defined. Based on user selections, the sea surface temperature could be the water temperature, the skin temperature or the 1000 hPa temperature. Users with high resolution land use may find that they have very “hot” lakes during the summer. If the user selected the skin temperature from the PREGRID Vtable, a daily mean of both the surface air temperature and the sea surface temperature are computed and output in the LOWBDY_DOMAINn file. The purpose for the daily mean is to reduce the diurnal variation of the “constant” temperature and provide more realistic inland lake temperatures. This is the reason it is recommended that users always prepare an analysis/forecast that extends for at least a full day. If the user selected the SST from the PREGRID Vtable, then the INTERPF program automatically provides time varying fields of both SST and the surface air temperature. When in doubt, the user should assume that that temperature at the ground is the skin temperature and not suitable for use as a time varying field for SST.
7.9 Shell Variables (for NCAR IBM job deck only) All of the MM5 system job decks for IBM are written as C-shell executables. Strict adherence to C-shell syntax is required in this section. Table 7.1: INTERPF IBM deck shell variables. C-shell Variable Name
Options and Use
ExpName
location of MSS files, keep same as used for deck generating input file for this program
RetPd
time in days to retain data on MSS after last access
input_file
MSS root name for p-level input to INTERPF
7.10 Parameter Statements Ha! There aren’t any.
7-10
MM5 Tutorial
7: INTERPF
7.11 FORTRAN Namelist Input File Most of the available options for the INTERPF code are handled through the namelist input file. Since this file is a FORTRAN namelist (FORTRAN 90 standard), syntax is very specific. There are six namelist records (record0 through record5). In general, all of the namelist records must be filled with the user’s description of the data. Table 7.2: INTERPF namelist values: RECORD0 and RECORD1. Namelist Record
Namelist Variable
RECORD0
INPUT_FILE
input file from REGRID, RAWINS, LITTLE_R, or INTERPB complete with directory structure
RECORD1
START_YEAR
starting time, 4 digit INTEGER of the year
RECORD1
START_MONTH
starting time, 2 digit INTEGER of the month
RECORD1
START_DAY
starting time, 2 digit INTEGER of the day
RECORD1
START_HOUR
starting time, 2 digit INTEGER of the hour
RECORD1
END_YEAR
ending time, 4 digit INTEGER of the year
RECORD1
END_MONTH
ending time, 2 digit INTEGER of the month
RECORD1
END_DAY
ending time, 2 digit INTEGER of the day
RECORD1
END_HOUR
ending time, 2 digit INTEGER of the hour
RECORD1
INTERVAL
time interval in seconds between analysis periods
RECORD1
LESS_THAN_24H
T/F flag of whether to force less than 24 h in the analysis (FALSE by default)
Description
Table 7.3: INTERPF namelist values: RECORD2 and RECORD3. Namelist Record
Namelist Variable
RECORD2
SIGMA_F_BU
input sigma levels, full levels, bottom-up (1.0 through 0.0)
RECORD2
PTOP
pressure of the model lid (Pa)
MM5 Tutorial
Description
7-11
7: INTERPF
Table 7.3: INTERPF namelist values: RECORD2 and RECORD3. Namelist Record
Namelist Variable
RECORD2
ISFC
how many sigma levels to include in the use of the lowest level analysis for the vertical interpolation; 0 = normal interpolation, 1 = use surface level for lowest sigma layer, n>1 use surface level for n sigma layers in interpolation
RECORD3
P0
reference sea level pressure (Pa)
RECORD3
TLP
reference temperature lapse rate (K {ln Pa}-1)
RECORD3
TS0
reference sea level temperature (K)
RECORD3
TISO
isothermal temperature (K), if this is left as 0 there is no effect, this is the temperature that the reference profile assumes when the temperature would otherwise be less than TISO
Description
Table 7.4: INTERPF namelist values: RECORD4 and RECORD5. Namelist Record
Namelist Variable
Description
RECORD4
REMOVEDIV
T/F flag, remove the integrated mean divergence
RECORD4
USESFC
T/F flag, use the input surface data in the vertical interpolation
RECORD4
WRTH2O
T/F flag, saturation is with respect to liquid water
RECORD4
PSFC_METHOD
INTEGER, 0 => (Tslv + Tsfc )/2; 1 => surface pressure from diurnally averaged surface temp
RECORD5
IFDATIM
INTEGER, number of time periods of initial condition output required (only 1 is necessary if not doing analysis nudging), “-1” is the magic value that means output all of the time periods
7.12 How to Run INTERPF 1) Obtain the source code tar file from one of the following places:
7-12
MM5 Tutorial
7: INTERPF
Anonymous ftp: ftp://ftp.ucar.edu/mesouser/MM5V3/INTERPF.TAR.gz On NCAR MSS: /MESOUSER/MM5V3/INTERPF.TAR.gz 2) gunzip the file, untar it. A directory INTERPF will be created. cd to INTERPF. 3) Type ‘make’ to create an executable for your platform. 4) On an NCAR IBM, edit interpf.deck.ibm (located in ~mesouser/MM5V3/IBM) to select script options and to select namelist options. On workstations, edit the namelist.input file for the namelist options. 5) On an NCAR IBM, type interpf.deck.ibm to compile and execute the program. It is usually a good practice to pipe the output to an output file so that if the program fails, you can take a look at the log file. To do so, type: interpf.deck.ibm >& interpf.log, for example. On a workstation, run the executable directly (interpf >& interpf.log). INTERPF requires one of the following input files: REGRID_DOMAINn, RAWINS_DOMAINn, LITTLE_R_DOMAINn, or MMOUTP_DOMAINn (where n is the domain identifier). The location for the input data, including directory structure, is defined in the namelist file. Output files from INTERPF (input files for MM5): MMINPUT_DOMAINn, BDYOUT_DOMAINn, LOWBDY_DOMAINn (where n is the domain identifier). These files are output in the current working directory. The user has no control over this naming convention.
7.13 INTERPF didn’t Work! What Went Wrong? • Most of the errors from INTERPF that do not end with a "segmentation fault", "core dump", or "floating point error" are accompanied with a print statement. Though the message itself may not contain enough substance to correct the problem, it will lead you to the section of the code that failed, which should provide more diagnostic information. The last statement that INTERPF prints during a controlled failed run is the diagnostic error.
• To see if INTERPF completed successfully, first check to see if the "STOP 99999" statement appears. Also check to see that INTERPF processed each of the requested times from the namelist. The initial condition file should be written-to after each analysis time, up to the number of time periods requested by the namelist. The boundary condition file is written-to after each analysis time, beginning with the second time period. The lower boundary file is written to just once.
• When INTERPF tells you that it "Relaxation did not converge in 20000 iterations”, you may doing an idealized run with non-divergent winds. Set the flag (REMOVEDIV = .FALSE. in the namelist) so that you are not doing the mean divergence removal.
• Remember that to generate a single boundary condition file, you must have at least two
time periods, so that a lateral boundary tendency may be computed. Even if you are not
MM5 Tutorial
7-13
7: INTERPF
going to run a long forecast, it is advantageous to provide a full day for the lower boundary condition file, as this file contains the daily mean of the surface air temperature and the daily mean of the SST.
• When INTERPF runs into an interpolation error that it did not expect (i.e. forced to do an
extrapolation when none should be required), INTERPF will stop and print out the offending (I,J,K) and pressure values. If this is not simply a fix by amending the provided σ or pressure surfaces, it is usually a bit more tricky and implies that the analysis data is possibly in error.
7.14 File I/O The interpolation program has input and output files that are ingested and created during an INTERPF run. The binary input files and all of the output files are unformatted FORTRAN write statements (binary, sequential access). One of the input files is a human-readable namelist formatted file of run-time options. The following tables are for the input and output units.
Table 7.5: INTERPF program input file. File Name
Description
namelist.input
namelist file containing run-time options
LITTLE_R_DOMAINn, RAWINS_DOMAINn, REGRID_DOMAINn, MMOUTP_DOMAINn (specified in namelist file)
MM5 system, meteorological data on pressure levels, input to INTERPF
Table 7.6: INTERPF program output files. File Name
Description
MMINPUT_DOMAINn
initial condition for MM5
BDYOUT_DOMAINn
lateral boundary condition for MM5
LOWBDY_DOMAINn
lower boundary condition (reservoir temperature, mean or timevarying SST, sea ice, fractional seaice, snow cover)
7-14
MM5 Tutorial
7: INTERPF
7.15 INTERPF tar File The interpf.tar file contains the following files and directories: CHANGES Doc Makefile README interpf.deck.cray namelist.input src/
MM5 Tutorial
Description of changes to the INTERPF program Contains a couple of README files Makefile to create INTERPF executable General information about the INTERPF directory job deck for usage on one of the NCAR Cray machines input namelist file for run-time options INTERPF source code
7-15
7: INTERPF
7-16
MM5 Tutorial
8: MM5
MM5
8
Purpose 8-3 Basic Equations of MM5 8-3 Physics Options in MM5 8-7 Cumulus Parameterizations (ICUPA) 8-7 PBL Schemes (IBLTYP) 8-8 Explicit Moisture Schemes (IMPHYS) 8-10 Radiation Schemes (IFRAD) and Diffusion 8-13 Surface Schemes (ISOIL) 8-14 Interactions of Parameterizations 8-17 Boundary conditions 8-17 Lateral boundary conditions (IBOUDY) 8-17 Lower boundary conditions 8-18 Upper boundary condition (IFUPR) 8-18 Nesting 8-18 One-way nesting 8-18 Two-way nesting 8-18 Two-way nest initialization options (IOVERW) 8-18 Two-way nesting feedback options (IFEED) 8-19 Four-Dimensional Data Assimilation (FDDA) 8-20 Introduction 8-20 FDDA Method 8-20 Uses of FDDA 8-20 Data used in FDDA 8-21 How to run MM5 8-22 Compiling MM5 8-22 Running MM5 8-22 Running MM5 Batch Job on NCAR’s IBM 8-23 Useful make commands 8-23
MM5 Tutorial
8-1
8: MM5
Input to MM5 8-24 Output from MM5 8-24 MM5 Files and Unit Numbers 8-27 Configure.user Variables 8-28 Script Variables for IBM Batch Deck: 8-30 Namelist Variables 8-30 OPARAM 8-31 LPARAM 8-31 NPARAM 8-34 PPARAM 8-35 FPARAM 8-35 Some Common Errors Associated with MM5 Failure 8-36 MM5 tar File 8-37 Configure.user 8-39 mm5.deck 8-54
8-2
MM5 tutorial
8: MM5
8
MM5
8.1 Purpose • This is the numerical weather prediction part of the modeling system. • MM5 can be used for a broad spectrum of theoretical and real-time studies, including applications of both predictive simulation and four-dimensional data assimilation to monsoons, hurricanes, and cyclones.
• On the smaller meso-beta and meso-gamma scales (2-200 km), MM5 can be used for studies involving mesoscale convective systems, fronts, land-sea breezes, mountain-valley circulations, and urban heat islands.
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 γp ⎛ Q· T 0 ⎞ ∂p′ ------- – ρ 0 gw + γp∇ ⋅ v = – v ⋅ ∇p′ + ----- ⎜ ----- + ----- D θ⎟ ∂t T ⎝ cp θ0 ⎠
MM5 Tutorial
(8.1)
8-3
8: MM5
Momentum (x-component) ∂m ∂m uw ∂-----u m ∂p′ σ ∂p∗ ∂p′ + ---- ⎛ ------- – ------ -------- -------⎞ = – v ⋅ ∇u + v ⎛ f + u ------- – v -------⎞ – ew cos α – ------------- + D u ⎝ ∂y ∂x ⎠ r earth ∂t ρ ⎝ ∂x p∗ ∂x ∂σ ⎠
(8.2)
Momentum (y-component) ∂----v- m ∂p′ σ ∂p∗ ∂p′ ∂m ∂m vw + ---- ⎛⎝ ------- – ------ -------- -------⎞⎠ = – v ⋅ ∇v – u ⎛⎝ f + u ------- – v -------⎞⎠ + ew sin α – ------------- + D v ∂t ρ ∂y p∗ ∂y ∂σ ∂y ∂x r earth
(8.3)
Momentum (z-component) 2 2 p 0 T′ g d p ′ ρ 0 g ∂p′ g p′ ∂-----w ---u + v R – - ------ ------- + --- ---- = – v ⋅ ∇w + g ----- ----- – --------- ---- + e ( u cos α – v sin α ) + ----------------- + D w ∂t ρ p∗ ∂σ γ p p T0 cp p r earth
(8.4)
Thermodynamics · Q ∂----T1 ∂p′ T = – v ⋅ ∇T + -------- ⎛⎝ ------- + v ⋅ ∇p′ – ρ 0 gw⎞⎠ + ----- + -----0 D θ ∂t ρc p ∂t cp θ0
(8.5)
Advection terms can be expanded as A∂A · ∂A v ⋅ ∇A ≡ mu ∂----+ mv ------ + σ -----∂x ∂y ∂σ
(8.6)
ρ0 g mσ ∂p∗ mσ ∂p∗ · - w – -------- -------- u – -------- -------- v σ = – -------p∗ p∗ ∂x p∗ ∂y
(8.7)
where
Divergence term can be expanded as u mσ ∂p∗ ∂u v mσ ∂p∗ ∂v ρ 0 -g∂-----w 2 2 ∇ ⋅ v = m ∂ ⎛ ----⎞ – -------- -------- ------ + m ∂ ⎛ ----⎞ – -------- -------- ------ – -------⎝ ⎠ ⎝ ⎠ ∂x m ∂y m p∗ ∂x ∂σ p∗ ∂y ∂σ p∗ ∂σ
8-4
(8.8)
MM5 Tutorial
8: MM5
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 e = 2Ω cos λ , α = φ – φ c , λ is latitude, φ is longitude, and φc is central longitude. ∂m ∂m • The u ------- , v ------- and rearth terms represent curvature effects, and m is map-scale factor. ∂y ∂x • 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 MM5 Tutorial
8-5
8: MM5
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.
First time step:
∆t
n=1
n=2
∆τ
Time step n: T, qv, qc, etc., advection, physics, boundary, coriolis, diffusion terms
Long (leapfrog) step ∆t
n-1
∆t
n
n+1
∆τ Short (forward) step u, v, w, p’ advanced (pressure gradients, divergence terms) Time step n+1:
∆t
n
n+1
∆t
n+2
∆τ
8-6
MM5 Tutorial
8: MM5
8.3 Physics Options in MM5 8.3.1 Cumulus Parameterizations (ICUPA) 1. None Use no cumulus parametrization at grid sizes < 5-10 km.
Illustration of Cumulus Processes
detrainment updraft compensating subsidence downdraft entrainment boundary layer
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).
MM5 Tutorial
8-7
8: MM5
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 8-8
MM5 Tutorial
8: MM5
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.
Illustration of PBL Processes stable layer/free atmosphere
vertical diffusion entrainment
PBL top
nonlocal mixing PBL layers
local mixing
surface layer
sensible heat flux
latent heat flux
friction
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. MM5 Tutorial
8-9
8: MM5
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 8-10
MM5 Tutorial
8: MM5
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.
MM5 Tutorial
8-11
8: MM5
Illustration of Microphysics Processes Dudhia simple ice Hsie Warm Qv
Qi
Qv
Qs
0C Qv Qc
Qr Qc
Goddard mixed-phase
Reisner mixed-phase Qv
Qi
Qr
Qv
Qs
Qi
Qg Qs
Qc
8-12
Qr
Qc
Qr
MM5 Tutorial
8: MM5
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.
MM5 Tutorial
8-13
8: MM5
Illustration of Free Atmosphere Radiation Processes Shortwave Longwave
Shortwave Longwave reflection
model layer cloud
surface emissivity
clear sky
scattering
absorption LW emission
surface albedo
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,
8-14
MM5 Tutorial
8: MM5
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 landuse 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).
Illustration of Surface Processes LW/SW
LW
SH LH snow
land
SH LH water constant temperature
Ground flux soil layers
soil diffusion
substrate (constant temperature)
MM5 Tutorial
8-15
8: MM5
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 landsurface 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-16
MM5 Tutorial
8: MM5
8.4 Interactions of Parameterizations
Direct Interactions of Parameterizations cloud detrainment
Microphysics
Cumulus
cloud effects cloud fraction
surface fluxes
Radiation
SH, LH
PBL
downward SW, LW
surface T,Qv,wind
surface emission/albedo Surface
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.
MM5 Tutorial
8-17
8: MM5
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)
8-18
MM5 Tutorial
8: MM5
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.
MM5 Tutorial
8-19
8: MM5
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.
8-20
MM5 Tutorial
8: MM5
• 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: RIO: RJO: RKO: IVAR(1): IVAR(2): IVAR(3): IVAR(4): IVAR(5):
Julian date in dddhh. Example: 16623.5 - Julian day 166 and hour 2330 UTC y-location - I dot-point location on coarse mesh (may be a fraction of a grid) x-location - J dot-point location on coarse mesh (may be a fraction of a grid) z-location - K half-σ level (must be on half σ levels) u wind - in m/sec rotated to model grid v wind - in m/sec rotated to model grid temperature - in Kelvin water vapor mixing ratio - in kg/kg 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.
MM5 Tutorial
8-21
8: MM5
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’.
8-22
MM5 Tutorial
8: MM5
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.
8.8.4 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.
MM5 Tutorial
8-23
8: MM5
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:
8-24
MM5 Tutorial
8: MM5
• 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 2 3 4 5 6 7 8 9 10 11 12 13 14
U: U-wind (m/s) V: V-wind (m/s) T: Temperature (K) Q: Water vapor mixing ratio (kg/kg) (if IMPHYS≥2) CLW: Cloud water mixing ratio (kg/kg) (if IMPHYS≥3) RNW: Rain water mixing ratio (kg/kg) (if IMPHYS≥3) ICE: Ice cloud mixing ratio (kg/kg) (if IMPHYS≥5) SNOW: Snow mixing ratio (kg/kg) (if IMPHYS≥5) GRAUPEL: Graupel (kg/kg) (if IMPHYS≥6) NCI: Number concentration of ice (if IMPHYS=7) TKE: Turbulent k.e. (J/kg) (if IBLTYP=3,4,6) RAD TEND: Atmospheric radiation tendency (K/day) (if FRAD≥2) W: Vertical velocity (m/s) (on full σ -levels) PP: Perturbation pressure (Pa)
2D forecast fields dimensioned (IX, JX) include: 1 PSTARCRS: Pstar (cb) 2 GROUND T: Ground temperature (K) 3 RAIN CON: Accum. convective rainfall (cm) 4 RAIN NON: Accum. nonconv. rainfall (cm) 5 PBL HGT: PBL height (m) 6 REGIME: PBL regime (catagory, 1-4) 7 SHFLUX: Surface sensible heat flux (W/m2) 8 LHFLUX: Surface latent heat flux (W/m2) 9 UST: Frictional velocity (m/s) 10 SWDOWN: Surface downward shortwave radiation (W/m2) 11 LWDOWN: Surface downward longwave radiation (W/m2) 12 MAVAIL: Surface moisture availability (if IMOIAV=1,2) 13 SOIL T x: Soil temperature in a few layers (K) (if ISOIL=1,2) 14 SOIL M x: Soil moisture in a few layers (m3/m3) (if ISOIL=2) 15 SOIL W x: Soil water in a few layers (m3/m3) (if ISOIL=2) 16 SFCRNOFF: Surface runoff (mm) (if ISOIL=2) 17 UGDRNOFF: Underground runoff (mm) (if ISOIL=2) 18 SNOWCOVR: Snow cover (variable if ISOIL=2) 19 SNOWH: physical snow height (m)
MM5 Tutorial
dot dot cross cross cross cross cross cross cross cross cross cross cross cross cross cross cross cross cross cross cross cross cross cross cross cross cross cross cross cross cross cross cross
8-25
8: MM5
(if ISOIL=2, or IFSNOW=2) 20 WEASD: Water-equivalent snow depth (mm) (if ISOIL=2, or IFSNOW=2) 21 CANOPYM: Canopy moisture (m) (if ISOIL=2) 22 GRNFLX: ground head flux (W/m2) (if ISOIL=2, 3) 23 ALB: albedo (fraction) (if ISOIL=2) 24 ALBSNOMX: maximum snow albedo (%) (if ISOIL=2, and RDMAXALB=T) 25 MONALBnn: monthly albedo (%) (if ISOIL=2, or RDBRDALB=T) 26 ALBEDO: background albedo (%) (if IFSOIL=2, RDBRDALB=T) 27 VEGFRC: Vegetation coverage (if ISOIL = 2) 28 SWOUT: top outgoing shortwave radiation (if FRAD>=2) 29 LWOUT: top outgoing longwave radiation (if FRAD>=2) 30 T2: 2 m temperature (K) (if IBLTYP=2, 4, 5) 31 Q2: 2 m mixing ratio (kg/kg) (if IBLTYP=2, 4, 5) 32 U10: 10 m u component of wind (m/sec) (if IBLTYP=2,4,5) 33 V10: 10 m v component of wind (m/sec) (if IBLTYP=2,4,5) 34 M-O LENG: Monin-Obukov length (m) (if ISOIL=3) 35 NET RAD: surface net radiation (W/m2) (if ISOIL=3) 36 ALBEDO: surface albedo (fraction) (if ISOIL=3) 37 RA: aerodynamic resistance (s/m) (if ISOIL=3) 38 RS: surface resistance (s/m) (if ISOIL=3) 39 LAI: leaf area index (area/area) (if ISOIL=3) 40 VEGFRC: vegetation fraction (fraction) (if ISOIL=3) 41 ZNT: roughness length (m) (if ISOIL=3) 42 ISLTYP: soil texture type (if ISOIL=3) 43 SUMFB: mass flux updraft (if ICUPA=8) 44 SPSRC: source layer updraft (if ICUPA=8) 45 SEAICEFR: seaice fraction (if IPOLAR=1) 46 TGSI: seaice temperature (if IPOLAR=1) 2D constant fields dimensioned (IX, JX) include: 47 TERRAIN: Terrain elevation (m) 48 MAPFACCR: Map scale factor 49 MAPFACDT: Map scale factor 50 CORIOLIS: Coriolis parameter (/s) 51 RES TEMP: Substrate temperature (K) 52 LATITCRS: Latitude (deg) 53 LONGICRS: Longitude (deg) 54 LANDUSE: Land-use category 55 SNOWCOVR: Snow cover (if ISOIL < 2) 56 TSEASFC: Sea surface temperature (K) 57 SEAICE: Seaice (dimensionless) (if ISOIL=2)
cross cross cross cross cross cross cross cross cross cross cross cross cross cross cross cross cross cross cross cross cross cross cross cross cross cross cross cross cross dot cross cross cross cross cross cross cross 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 8-26
MM5 Tutorial
8: MM5
62 63 64 65
SFZ0: Surface roughness from LANDUSE.TBL THERIN: Surface thermal inertia from LANDUSE.TBL SFHC: Soil heat capacity from LANDUSE.TBL 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 timeseries 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
MM5 Tutorial
8-27
8: MM5
File name
Unit number
Description
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
Rrestart 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 precompilation 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:
8-28
MM5 Tutorial
8: MM5
=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
ICUPA
=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). 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)
ISOIL
MM5 Tutorial
=1, use the multi-layer soil model (require IBLTYP=2, 4, 5, 6); =0, no soil model; =2, Noah LSM model (requires IBLTYP=4, 5); =3, Pleim-Xiu LSM (requires IBLTYP=7).
8-29
8: MM5
ISHALLO
=1, use shallow convective scheme (not well tested); =0, no.
8.13 Script Variables for IBM Batch Deck: ExpName
experiment name used in setting MSS pathname for output.
InName
input MSS pathname.
RetPd
mass store retention period (days).
compile
=yes, compile the mm5 code; =no, expect an existing executable.
execute
=yes, execute the model; =no, compile the code only.
UseMySource
=yes, use your own source code; =no, use mesouser version of the source code.
CaseName
MSS pathname for this run.
STARTsw
= NoReStart: start model run at hour zero (initialize). = ReStart: restart model run.
FDDAsw
= NoFDDA, no FDDA input files, = Anly, gridded FDDA input files, = Obs, obsFDDA input files, = Both, gridded and obs FDDA input files.
InBdy
MSS name of lateral boundary file.
InLow
MSS name for lower boundary condition file.
InMM
MSS name(s) of model input files.
InRst
MSS name(s) of model restart files.
In4DSfc
MSS name of surface analysis used for 4DDA.
In4DObs
MSS name of fdda obs files.
Host
=
[email protected]:/usr/tmp/username, host computer to rcp user’s program tar file.
OutMM
MSS name for output.
8.14 Namelist Variables A namelist file, called mmlif, is created when mm5.deck is executed. In MM5, this file is created 8-30
MM5 Tutorial
8: MM5
partially from the configure.user file, and partially from mm5.deck.
8.14.1 OPARAM TIMAX
= forecast length in minutes.
TISTEP
= time step in seconds for the coarsest domain (recommend 3*dx(km)).
IFREST
=TRUE, for restart, =FALSE, for initial run.
IXTIMR
= integer time in minutes for restart.
IFSAVE
=TRUE, if saving data for restart, = FALSE, for no restart output.
SVLAST
= TRUE, if only saving the last time; = FALSE, save multiple times.
SAVFRQ
= frequency of restart output in minutes.
IFTAPE
= 1, for model output; =0, no model output.
TAPFRQ
= frequency of model history file output in minutes.
BUFFRQ
= how frequency to split model output files in minutes (ignored if < TAPFRQ).
INCTAP
= multipliers of TAPFRQ for outputting.
IFRSFA
= TRUE, if it is a restart run, using FDDA and multiple input files. Use with CDATEST.
IFSKIP
= TRUE, skip input files to start the model - DO NOT use this when restart.
CDATEST
= DATE (yyyy-mm-dd_hh:mm:ss) of the start file, used with IFSKIP/IFRSFA.
IFPRT
= 1, for printed output fields; = 0, for no printed output fields
PRTFRQ
= frequency of printed output fields in minutes
MASCHK
= integer frequency in number of time steps for budget/rainfall prints (coarsest mesh) - may not give correct answer on parallel computers.
IFTSOUT
= TRUE, if output time series; = FALSE, do not output time series
TSLAT
= latitudes of time series output locations
TSLON
= longitudes of time series output locations
8.14.2 LPARAM 1) Defined in mm5.deck: RADFRQ
= frequency in minutes of radiation calculations (surface and atmospheric)
IMVDIF
=1, for moist vertical diffusion in clouds (requires IMPHYS>2, and IBLTYP=2, 5 or 7), = 0, vertical diffusion is dry
IVQADV MM5 Tutorial
= 0, vertical moisture advection uses log interpolation (old method), 8-31
8: MM5
= 1, vertical moisture advection uses linear interpolation (affects all moisture variables) IVTADV
= 0, vertical temperature advection uses log interpolation (old method), = 1, vertical temperature advection uses linear interpolation
ITHADV
= 0, temperature advection and adiabatic term use temperature (old method), = 1, temperature advection and adiabatic term use potential temperature
ITPDIF
= 1, for diffusion using perturbation temperature in NH model; =2, use horizontal diffusion (new in version 3.7); = 0, not using this function (new in V2)
TDKORR
=2, temperature gradient correction fo horizontal diffusion (ITPDIF=2) at ground level uses ground temperature; =1, temperature gradient correction fo horizontal diffusion (ITPDIF=2) at ground level uses one sided difference of air temperature.
ICOR3D
= 1, for full 3D Coriolis force (requires INHYD=1), = 0, for traditional approximation.
IEXSI
= 0, no seaice = 1, seaice fraction diagnosed from sea-surface temperature (requires IPOLAR=1) = 2, seaice fraction read from from LOWBDY file (requires IPOLAR=1)
IFUPR
= 1, for upper radiative boundary condition (NH run only). = 0, rigid upper boundary in nonhydrostatic runs.
LEVSLP
nest level (corresponding to LEVIDN) at which solar radiation starts to account for orography (to switch off, set to a large value). Only available for SWRAD (IFRAD=2,4).
OROSHAW
=1, include the effect of orography shadowing. This only has an effect if LEVSLP is also set. This option is not available for MM5 MPP runs.Only available for SWRAD (IFRAD=2,4). =0, do not include the effect of orography shawdowing.
ITADVM
=1, use instability limiter for temperature advection. =0, do not use instability limiter for temperature advection
IQADVM
=1, use instability limiter for QV/CLW advection. =0, do not use instability limiter for QV/CLW advection
IBOUDY
Boundary condition options: = 0, fixed, and for coarse domain only = 2, time-dependent (used for 2-way nested boundary condition) = 3, relaxation inflow/outflow, for coarse domain only
8-32
MM5 Tutorial
8: MM5
IFDRY
= 1, for fake dry run with no latent heating release (requires IMPHYS>1, and ICUPA=1)
ISSTVAR
= 1, update SST during a simulation (and snow cover and sea ice, if they are available). Must have at least SST field in the input; = 0, do not update SST (and snow cover and sea ice) during a simulation.
IMOIAV
used for bucket moisture scheme. = 0, do not use bucket scheme. = 1, use bucket scheme, and soil moisture is initialized with moisture availability values in LANDUSE.TBL. = 2: use bucket scheme, and soil moisture is initialized with soil moisture fields from MMINPUT files.
IFSNOW
= 1, snow cover effects (requires input SNOWC field from REGRID) = 2, snow-cover prediction (requires input WEASD field from REGRID, and use of IMPHYS = 4,5, and 7)
ISFMTHD
method for calculation of 2m/10m diagnostics = 0, old method = 1, new method for stable conditions (IBLTYP = 2 and 5 only)
IZ0TOPT
Thermal roughness length option for IBLTYP = 2 and 5 only. = 0, default (old) scheme = 1, Garratt formulation = 2, Zilitinkevich formulation
ISFFLX
= 1, compute surface heat and moisture fluxes; =0, no fluxes.
ITGFLG
= 1, ground temperature predicted; = 3, constant ground temperature.
ISFPAR
= 1, use TERRAIN-generated land-use categories; = 0, use only 2 (land/water) categories.
ICLOUD
= 1, consider cloud effects on surface radiation when FRAD=0,1 ; consider clouds in both surface and atmospheric radiation when FRAD=2,3,4; = 0, do not consider cloud effect on radiation; = 2, (IFRAD=3 only) radiation interacts with RH-derived cloud fraction only.
IEVAP
= 1, normal evaporative cooling; = 0, no evaporative effects; = -1, no precip evaporative cooling, (for IMPHYS=3,4, and 5).
ISMRD
Soil moisture initialization method for IBLTYP = 7 (Pleim-Xiu scheme) only. = 0, use moisture availability from LANDUSE.TBL; = 2, use soil moisture input from REGRID.
ISTLYR
bottom of soil layers expected as input for SOIL=2,3
ISMLYR
bottom of soil layers expected as input for SOIL=2,3
RDMAXALB
whether to read in max snow albedo for ISOIL = 2 (Noah LSM) only.
MM5 Tutorial
8-33
8: MM5
= FALSE, do not use max snow albedo; = TRUE, use max snow albedo present in MMINPUT file. RDBRDALB
whether to read in climatological month albedo for ISOIL = 2 (Noah LSM). = FALSE, do not use climatological monthly albedo; = TRUE, use climatological monthly albedo present in MMINPUT file.
2) Defined in configure.user, or internally produced: IFRAD
see ‘Configure.user variables’
ICUPA
see ‘Configure.user variables’
IBLTYP
see ‘Configure.user variables’
ISHALLO
see ‘Configure.user variables’
ISOIL
see ‘Configure.user variables’
IPOLAR
see ‘Configure.user variables’
8.14.3 NPARAM LEVIDN
= level of nest for each domain (0 for domain 1 - default valid values are 0-3)
NUMNC
= id number of parent domain for each domain (1 for domain 1)
NESTIX
= I-dimension of each domain.
NESTJX
= J-dimension of each domain.
NESTI
= south-west corner point I for each domain.
NESTJ
= south-west corner point J for each domain.
XSTNES
= starting time in minutes for each domain.
XENNES
= ending time in minutes for each domain.
IOVERW
= 1, for initializing a nest from the nest input file, usually at model starting time; = 0, for interpolating to a nest from parent mesh, usually during model integration; = 2, for initializing domain with high resolution terrain, usually during model integration.
IACTIV
= 1, if this domain is active when restart; = 0, if this domain is inactive.
IMOVE
= 0, if domain does not move; =1, if domain will move.
IMOVCO
= number of first move (always 1 at beginning, may change for restarts).
IMOVEI
= increment in I (parent domain grids) of this move for this domain.
8-34
MM5 Tutorial
8: MM5
IMOVEJ
= increment in J (parent domain grids) of this move for this domain.
IMOVET
= time in minutes of this move for this domain (relative to beginning of the coarse mesh run).
Note: the default number of moves is 10. IFEED
feedback from nest to coarse mesh in 2-way nests: = 0, no feedback; = 1, 9-point weighted average; = 2, 1-point feedback, with no smoothing; = 3, 1-point feedback, with smoother/desmoother (recommended); = 4, 1-point feedback, with heavy smoothing
8.14.4 PPARAM ZZLND
= roughness length over land (m) (if ISFPAR=0)
ZZWTR
= roughness length over water (m) (if ISFPAR=0)
ALBLND
= albedo over land (if ISFPAR=0)
THILND
= thermal inertia of land (cal-1 cm-2 K-1 s-0.5, if ISFPAR=0)
XMAVA
= moisture availability over land (if ISFPAR=0)
CONF
= non-convective precip saturation criterior (fraction ≤ 1 for IMPHYS=1)
SOILFAC
= a factor to make 5-layer soil model time step more conservative. Higher number makes soil timestep shorter (range typically 1.0 - 2.0). Used in IBLTYP=1, 2, 4 ,5, and 6.
CZO,OZO
= constants in Charnock relation for water roughness length. Used in IBLTYP = 2, 5 and 6.
CKH
= factor to control background diffusion coefficient used in the model. Default value is 1., which gives the same diffusion as versions before 3.5 if one uses 3xDX as the time step.
8.14.5 FPARAM FDASTA
(MAXSES); time (min) for initiation of FDDA.
FDAEND
(MAXSES); time (min) for termination of FDDA.
I4D
(MAXSES, 2); will FDDA analysis nudging be employed, (0=no; 1=yes).
DIFTIM
(MAXNES, 2); time (min) between input analyses for analysis nudging.
IWIND
(MAXSES, 2); will the wind field be nudged from analyses, (0=no; 1=yes).
GV
(MAXSES, 2); analysis-nudging coefficient (s-1) for wind.
ITEMP
(MAXSES, 2); will the temperature be nudged from analyses, (0=no; 1=yes).
MM5 Tutorial
8-35
8: MM5
GT
(MAXSES, 2); analysis-nudging coefficient (s-1) for temperature.
IMOIS
(MAXSES, 2); will the mixing ratio be nudged from analyses, (0=no; 1=yes).
GQ
(MAXSES, 2); analysis-nudging coefficient (s-1) for mixing ratio.
IROT
(MAXSES); will vorticity be nudged from analyses, (0=no; 1=yes).
GR
(MAXSES, 2); analysis-nudging coefficient (m2 s-1) for vorticity.
INONBL
(MAXSES, 4); will PBL fields be nudged from 3-D analyses when not using surface-analysis nudging within PBL. (0=yes; 1=exclude certain variables depending on integer value of second index).
RINBLW
radius of influence (km) for surface-analysis nudging where the horizontal weighting function depends on surface data density.
NPFG
coarse-grid time-step frequency for select diagnostic print of analysis nudging.
I4DI
(MAXSES); will FDDA observation nudging be employed, (0=no; 1=yes).
ISWIND
(MAXSES); will the wind field be nudged from observations, (0=no; 1=yes).
GIV
(MAXSES); observation-nudging coefficient (s-1) for wind.
ISTEMP
(MAXSES); will the temperature be nudged from observations, (0=no; 1=yes).
GIT
(MAXSES); observation-nudging coefficient (s-1) for temperature.
ISMOIS
(MAXSES); will the mixing ratio be nudged from observations, (0=no; 1=yes).
GIQ
(MAXSES); observation-nudging coefficient (s-1) for mixing ratio.
RINXY
default horizontal radius of influence (km) for distance-weighted nudging corrections (for observation nudging).
RINSIG
vertical radius of influence (on sigma) for distance -weighted nudging corrections (for observationnudging).
TWINDO
(time window)/2 (min) over which an observation will be used for nudging.
NPFI
coarse-grid time-step frequency for select diagnostic print of observation nudging.
IONF
observation-nudging frequency in coarse grid time steps for observation-nudging calculations.
IDYNIN
for dynamic initialization using a ramp-down function to gradually turn off the FDDA before the pure forecast (1=yes, 0=no).
DTRAMP
the time period in minutes over which the nudging (obs nudging and analysis nudging) is ramped down from one to zero. Set dtramp negative if FDDA is to be ramped down BEFORE the end-of-data time (DATEND), and positive if the FDDA ramp-down period extends beyond the end-of-data time.g calculations.
8.15 Some Common Errors Associated with MM5 Failure When an MM5 job is completed, always check for at least the following: • The “STOP 99999” print statement indicates that MM5 completed without crashing.
8-36
MM5 Tutorial
8: MM5
• When running a batch job on NCAR’s computer, check to be sure that the mswrite com-
mands were all completed successfully by the shell, and that the files were written to the pathnames you expected. • Check the top of “mm5.print.out” file to see if all domains are correctly initiated if running a multiple-domain job, and if the physics options are correctly specified. If an MM5 job has failed, check for some of the common problems: • If your model stops immediately after it prints out ‘NON-HYDROSTATIC RUN’ with an ‘Segmentation fault’ or sometimes ‘Bus error’, it is a good indication that the model is not getting enough memory to run. On most machine, typing ‘unlimit’ before you run the model will be the solution. • “Read past end-of-file”: This is usually followed by a fortran unit number. Check this unit number with Table 8.1 to find out which file MM5 has problem with. Check all the MSREAD statements in the printout to be sure that files were read properly from the MSS. Also check to make sure that the file sizes are not zero. Double-check experiment names, MSS pathnames. • “Unrecognized namelist variable”: This usually means there are typos in the namelist. • Unmatched physics option: for instance, the following should appear in the print output: STOP SEE ERRORS IN PRINT-OUT If one browses through the output, one may find things like: ERROR: IFRAD=2 REQUIRES IRDDIM=1 AND IMPHYS>3 which tells a user what a user needs to do to correct the problem.
• Uncompiled options: STOP SEE ERRORS IN PRINT-OUT If one browses through the output, one may find things like: ERROR: IFRAD=2, OPTION NOT COMPILED which tells a user the option you choose has not been compiled.
• When restarting a job, do not re-compile. If you do re-compile, do not change anything in the configure.user file. • If the job stopped and there is a long list of “CFL>1...”, it usually means the time step (TISTEP in namelist) is too big. Shorten the TISTEP and re-submit. • If doing a multi-domain run, please check these namelist variables carefully: LEVIDN = 0,1,1,1,1,1,1,1,1,1, ; level of nest for each domain NUMNC = 1,1,1,1,1,1,1,1,1,1, ; ID of mother domain for each nest
8.16 MM5 tar File The mm5.tar file contains the following files and directories: CHANGES Makefile README
MM5 Tutorial
Description of changes to the MM5 program Makefile to create MM5 executable General information about the MM5 directory and
8-37
8: MM5
README.MPP Diff/ Run/ Templates/ Util/ configure.user configure.user.linux domain/ dynamics/ fdda/ include/ memory/ physics/ pick/
how to run MM5 General information on how to compile and run on DM machines Diff files for each new release Where MM5 runs MM5 job decks for different machines Utility programs for cpp Make rules and model configuration Above for PC running Linux OS on single and OMP processors
The file README contains basic instructions on how to compile and run the model. The file README.MPP contains basic information and instructions on how to start compiling and running MPP MM5. The model is executed in the directory Run. The bug fixes and changes to the source code and tar file are described in file CHANGES file and diff.* files in directory Diff/. All FORTRAN files are in lower-case directories separated according to their functions. See the chart at the end of this chapter for a complete list of FORTRAN files. When ‘make code’ command is executed, all .F and .f files selected for compiling are copied into the pick/ directory. A single cat command will enable a user to generate a source listing (see the README file in directory pick/).
8-38
MM5 Tutorial
8: MM5
8.17 Configure.user (This file is included here for reference only. Use the most up-to-date one from MM5.TAR file.) # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
Sections 1. System Variables 3. Fortran options 3a. Cray (YMP, J90) Note: set RUNTIME_SYSTEM="CRAY_IA" for Cray interactive job 3a2. Cray X1 Single Node OpenMP version 3b. IRIX.6.X (SGI_Origin,SGI_R10000,SGI_R8000 which support OpenMP) 3b2. IRIX.6.X (SGI_Origin,SGI_R10000,SGI_R8000) 3c. IRIX.5.2/5.3, IRIX.6.X (SGI_R4000/SGI_R4400/SGI_R5000) Note: set RUNTIME_SYSTEM="SGI_R4000" for SGI_R4400/SGI_R5000 3d. SUN Fortran (solaris,SPARC20/SPARC64) 3e. DEC_ALPHA (OSF/1) 3e2. DEC_ALPHA (4100/8400; use OpenMP parallel directives) 3f. IBM (AIX) 3f2. IBM, OpenMP (AIX) 3g. HP (UX) 3h. HP (SPP-UX) for HP Exemplar S/X-Class Systems 3i1. PC_PGF (LINUX/Portland Group Inc.) 3i2. PC_INTEL (LINUX/INTEL) 3j. MAC (OSX/xlf) 4. General commands 5. Options for making "./include/parame.incl" 6. Physics Options (memory related) 7. MPP Options (Set no options in section 3) 7a. IBM SP2 7a.1 IBM SP2 with SMP nodes 7b. Cray T3E 7c. SGI Origin 2000 7d. HP Exemplar 7e. Compaq ALPHA/MPI 7e.1 ALPHA Linux with MPI 7f. Fujitsu VPP 7g1. Network of Linux PCs with MPI (PGI) 7g2. Network of Linux PCs with MPI (INTEL) 7h. NEC SX/5 (under development) 7i. Sun MPI 7j. Cray X1
# 7k. Cray XD1, PGI Fortran # #----------------------------------------------------------------------------# 1. System Variables #----------------------------------------------------------------------------SHELL = /bin/sh RANLIB =echo .SUFFIXES: .F .i .o .f .c #----------------------------------------------------------------------------# 3. Fortran options # Uncomment the ones you need, including RUNTIME_SYSTEM #----------------------------------------------------------------------------LIBINCLUDE = $(DEVTOP)/include #----------------------------------------------------------------------------# 3a. Cray # Note: - imsl library is only needed if running Arakawa-Schubert cumulus scheme; # and the location of the library may be different on non-NCAR Crays. # - if you are using the new program environment on Cray, should set # CPP = /opt/ctl/bin/cpp # - select the right compilation option for Cray - you may use # f90 option on paiute # - -x omp is needed for f90 compiler version 3.0.2.6 and above. # Check man page. #-----------------------------------------------------------------------------
MM5 Tutorial
8-39
8: MM5
#RUNTIME_SYSTEM = "CRAY_IA" #FC = f90 #FCFLAGS = -D$(RUNTIME_SYSTEM) -I$(LIBINCLUDE) -O task1 -x omp #CFLAGS = #CPP = /opt/ctl/bin/cpp #CPPFLAGS = -I$(LIBINCLUDE) -C -P #LDOPTIONS = #LOCAL_LIBRARIES = -L /usr/local/lib -l imsl #MAKE = make -i -r #----------------------------------------------------------------------------# 3a2. Cray X1 Single Node OpenMP version #----------------------------------------------------------------------------#RUNTIME_SYSTEM = "crayx1" ## Use these for X1 cross compiler #X1_CROSS_COMP = "gcc" #X1_CROSS_CFLG = "" ## Use these for X1 native (trigger) compiler ##X1_CROSS_COMP = "cc" ##X1_CROSS_CFLG = "-hcommand" #FC = ftn ### OpenMP in SSP mode #FCFLAGS = -Ossp,task1,inline0 -xcsd,mic -sword_pointer -I$(LIBINCLUDE) D$(RUNTIME_SYSTEM) #LDOPTIONS = -Ossp,task1 ### Multi-streaming single MSP mode ###FCFLAGS = -O3 -Ogen_private_callee -xomp,mic -sword_pointer -I$(LIBINCLUDE) -D$(RUNTIME_SYSTEM) ### LDOPTIONS = #CFLAGS = #CPP = cpp #CPPFLAGS = -I$(LIBINCLUDE) -C -P #LOCAL_LIBRARIES = #MAKE = make -i -r #----------------------------------------------------------------------------# 3b. IRIX.6.X (SGI_Origin,SGI_R10000,SGI_R8000 which support OpenMP) # Use OpenMP directives for multi-processor runs. # - set RUNTIME_SYSTEM = SGI_Origin # - works with 7.2.1 and above compiler # - select appropriate XLOCAL0 macro for loader option # # - For parallel execution of MM5 set the following environment variables: # setenv OMP_NUM_THREADS # setenv _DSM_PLACEMENT ROUND_ROBIN # - For parallel execution on a processor set without contention: # setenv _DSM_WAIT SPIN # setenv OMP_DYNAMIC FALSE # setenv MPC_GANG OFF # - For parallel execution on a contented set of processors: # setenv _DSM_WAIT YEILD # setenv OMP_DYNAMIC TRUE # setenv MPC_GANG OFF #----------------------------------------------------------------------------#RUNTIME_SYSTEM = "SGI_Origin" #FC = f77 #ABI = -n32 # 2 GB address space ##ABI = -64 # For 64-bit address space #IO = -mpio #PREC = # default 32-bit floating-point presicion. ##PREC = -r8 # 64-bit floating-point precision. ##Conversion program between different precisions of mminput and bdyout available from
[email protected] #MP = -mp -MP:old_mp=OFF ##MP = -mp -MP:open_mp=OFF # Use SGI multiprocessing directives #OPT = -O3 -OPT:roundoff=3:IEEE_arithmetic=3 -OPT:reorg_common=OFF ##debugging#OPT = -g -DEBUG:div_check:subscript_check=ON:trap_uninitialized=ON ##select appropriate XLOCAL loader
8-40
MM5 Tutorial
8: MM5
#XLOCAL0 = ### Burk-Thompson PBL (IBLTYP=3) option mp directives ##XLOCAL0 = -Wl,-Xlocal,bt1_,-Xlocal,blk1_,-Xlocal,blk2_ ### Noah LSM (ISOIL=2) option mp directives ##XLOCAL0 = -Wl,-Xlocal,rite_,-Xlocal,abci_ ### Gayno-Seaman PBL (IBLTYP=6) option mp directives ##XLOCAL0 = -Wl,-Xlocal,fog1d_,-Xlocal,surface1_,-Xlocal,surface2_,-Xlocal,surface3_,-Xlocal,comsurfslab_ #FCFLAGS = -I$(LIBINCLUDE) -D$(RUNTIME_SYSTEM) $(ABI) $(IO) $(PREC) $(MP) $(OPT) #CFLAGS = #CPP = /usr/lib/cpp #CPPFLAGS = -I$(LIBINCLUDE) -C -P #LDOPTIONS = $(ABI) $(PREC) $(MP) $(OPT) $(XLOCAL0) #LOCAL_LIBRARIES = -lfastm #MAKE = make -i -r -P #----------------------------------------------------------------------------# 3b2. IRIX.6.X (SGI_Origin,SGI_R10000,SGI_R8000) # Use SGI directives for multi-processor runs. # - set RUNTIME_SYSTEM = SGI_R8000 # - use the appropriate LDOPTIONS if compiling Burk-Thompson PBL, # Gayno-Seaman PBL, or Noah land-surface module # - use 7.0 and above compiler # - do not use -lfastm for R10000 and Origin series for compiler # versions 7.0 and 7.1, unless patches are installed. For more # information please see MM5 Web page: # http://www.mmm.ucar.edu/mm5/mm5v2-sgi.html #----------------------------------------------------------------------------#RUNTIME_SYSTEM = "SGI_R8000" #FC = f77 #FCFLAGS = -I$(LIBINCLUDE) -O3 -n32 -mips4 -mp -OPT:roundoff=3:IEEE_arithmetic=3 #CFLAGS = #CPP = /usr/lib/cpp #CPPFLAGS = -I$(LIBINCLUDE) -C -P #LDOPTIONS = -n32 -mips4 -mp ###Burk-Thompson (IBLTYP=3) option mp directives ##LDOPTIONS = -n32 -mips4 -mp -Wl,-Xlocal,bt1_,-Xlocal,blk1_,-Xlocal,blk2_ ###Noah LSM (ISOIL=2) option mp directives ##LDOPTIONS = -n32 -mips4 -mp -Wl,-Xlocal,rite_,-Xlocal,abci_ ### Gayno-Seaman (IBLTYP=6) option mp directives ##LDOPTIONS = -n32 -mips4 -mp -Wl,-Xlocal,fog1d_,-Xlocal,surface1_,-Xlocal,surface2_,-Xlocal,surface3_,-Xlocal,comsurfslab_ #LOCAL_LIBRARIES = -lfastm ##LOCAL_LIBRARIES = #MAKE = make -i -r #----------------------------------------------------------------------------# 3c. IRIX.6.X (SGI_R4400/SGI_R4000/SGI_R5000) #----------------------------------------------------------------------------#RUNTIME_SYSTEM = "SGI_R4000" #FC = f77 #FCFLAGS = -I$(LIBINCLUDE) -mips2 -32 -O2 -Nn30000 -Olimit 1500 #CFLAGS = #CPP = /usr/lib/cpp #CPPFLAGS = -I$(LIBINCLUDE) -C -P #LDOPTIONS = #LOCAL_LIBRARIES = -lfastm #MAKE = make -i -r #----------------------------------------------------------------------------# 3d. SUN (solaris,SPARC20/SPARC64) #----------------------------------------------------------------------------#RUNTIME_SYSTEM = "SUN" #FC = f90 #FCFLAGS = -fast -O2 -I$(LIBINCLUDE) #CFLAGS = #LDOPTIONS = -fast -O2 #CPP = /usr/lib/cpp #CPPFLAGS = -I$(LIBINCLUDE) -C -P
MM5 Tutorial
8-41
8: MM5
#LOCAL_LIBRARIES = #MAKE = make -i -r #----------------------------------------------------------------------------# 3e. DEC_ALPHA (OSF/1) #----------------------------------------------------------------------------#RUNTIME_SYSTEM = "DEC_ALPHA" #FC = f90 #FCFLAGS = -cpp -D$(RUNTIME_SYSTEM) -I$(LIBINCLUDE) -c -O4 -Olimit 2000 -automatic \ # -fpe0 -align dcommons -align records -convert big_endian ###FCFLAGS = -cpp -D$(RUNTIME_SYSTEM) -DIBMopt -DvsLIB -I$(LIBINCLUDE) -c -O4 -Olimit 2000 -automatic \ ### -fpe0 -align dcommons -align records -convert big_endian #CFLAGS = #CPP = cpp #CPPFLAGS = -I$(LIBINCLUDE) -C -P #LDOPTIONS = -math_library accurate #LOCAL_LIBRARIES = #MAKE = make -i -r #----------------------------------------------------------------------------# 3e2. DEC_ALPHA (4100/8400 Series) # Use OpenMP directives for multi-processor runs. # - set RUNTIME_SYSTEM = DEC_ALPHA #----------------------------------------------------------------------------#RUNTIME_SYSTEM = "DEC_ALPHA" #FC = f90 #FCFLAGS = -omp -cpp -D$(RUNTIME_SYSTEM) -I$(LIBINCLUDE) -c -O4 -Olimit 2000 \ #-automatic -fpe0 -align dcommons -align records -convert big_endian #CFLAGS = #CPP = cpp #CPPFLAGS = -I$(LIBINCLUDE) -C -P #LDOPTIONS = -omp -math_library accurate #LOCAL_LIBRARIES = #MAKE = make -i -r #----------------------------------------------------------------------------# 3f. IBM (AIX) #----------------------------------------------------------------------------#RUNTIME_SYSTEM = "IBM" #FC = xlf #FCFLAGS = -I$(LIBINCLUDE) -O3 -qarch=auto -qmaxmem=-1 #CPP = /usr/lib/cpp #CFLAGS = #CPPFLAGS = -I$(LIBINCLUDE) -C -P -Drs6000 #LDOPTIONS = -qmaxmem=-1 -O3 -qarch=auto #LOCAL_LIBRARIES = -lmass #MAKE = make -i #----------------------------------------------------------------------------# 3f2. IBM (AIX) # - Depending on problem size and machine memory size, the settings # of maxstack and maxdata may need to be modified. # - If the newer thread-safe mass library is available, add # the -lmass_r option to LOCAL_LIBRARIES. #----------------------------------------------------------------------------#RUNTIME_SYSTEM = "IBM" #FC = xlf_r #FCFLAGS = -I$(LIBINCLUDE) -O2 -qarch=auto -qmaxmem=-1 -qsmp=omp:noauto qnosave -qstrict -qnocclines #CPP = /usr/lib/cpp #CFLAGS = #CPPFLAGS = -I$(LIBINCLUDE) -C -P -Drs6000 #LDOPTIONS = -qmaxmem=-1 -O2 -qarch=auto -bmaxstack:512000000 -bmaxdata:2000000000 #LOCAL_LIBRARIES = -lxlsmp -lmass_r #LOCAL_LIBRARIES = -lxlsmp #MAKE = make -i #-----------------------------------------------------------------------------
8-42
MM5 Tutorial
8: MM5
# 3g. HP (UX) #----------------------------------------------------------------------------#RUNTIME_SYSTEM = "HP" #FC = f77 #FCFLAGS = -I$(LIBINCLUDE) -O #CPP = /usr/lib/cpp #CFLAGS = -Aa #CPPFLAGS = -I$(LIBINCLUDE) -C -P #LDOPTIONS = #LOCAL_LIBRARIES = #MAKE = make -i -r #----------------------------------------------------------------------------# 3h. HP-SPP (SPP-UX), and HP-SPP_IA #----------------------------------------------------------------------------#RUNTIME_SYSTEM = "HP-SPP" #FC = f77 #PA8K = +DA2.0N +DS2.0a #ARCH = ${PA8K} #PROFILE = #INLINE = +Olimit +Oinline=_saxpy,vadv,hadv,sinty,sintx,slab,diffut #PARALLEL = +O3 +Oparallel +Onofail_safe +Onoautopar +Onodynsel # ## Use the following FCFLAGS to build single-threaded executable ##FCFLAGS = ${PROFILE} ${ARCH} -I$(LIBINCLUDE) +O3 +Oaggressive \ ## +Olibcalls ${INLINE} # ## Use the following FCFLAGS to build a parallel executable #FCFLAGS = ${PROFILE} ${ARCH} -I$(LIBINCLUDE) ${PARALLEL} \ # +O3 +Oaggressive +Olibcalls ${INLINE} # #CPP = /usr/lib/cpp #CFLAGS = ${PROFILE} -Aa #CPPFLAGS = -I$(LIBINCLUDE) -C -P #LDOPTIONS = ${FCFLAGS} -Wl,-aarchive_shared -Wl,+FPD #LOCAL_LIBRARIES = -Wl,/usr/lib/pa1.1/libm.a #MAKE = gmake -j 4 -i -r #----------------------------------------------------------------------------# 3i1. PC_PGF77 (LINUX/Portland Group Inc.) # pgf77 version 1.6 and above # May use pgf90 if the version is 3.1-4 #----------------------------------------------------------------------------#RUNTIME_SYSTEM = "linux" #FC = pgf90 #FCFLAGS = -I$(LIBINCLUDE) -O2 -Mcray=pointer -tp p6 -pc 32 -Mnoframe -byteswapio ##FCFLAGS = -I$(LIBINCLUDE) -O2 -Mcray=pointer -tp p6 -pc 32 -Mnoframe byteswapio -mp \ ##-Mnosgimp #CPP = /lib/cpp #CFLAGS = -O #CPPFLAGS = -I$(LIBINCLUDE) #LDOPTIONS = -O2 -Mcray=pointer -tp p6 -pc 32 -Mnoframe -byteswapio ##LDOPTIONS = -O2 -Mcray=pointer -tp p6 -pc 32 -Mnoframe -byteswapio -mp #LOCAL_LIBRARIES = #MAKE = make -i -r #----------------------------------------------------------------------------# 3i2. PC_INTEL (LINUX/INTEL) #----------------------------------------------------------------------------#RUNTIME_SYSTEM = "linux" #FC = ifort #FCFLAGS = -I$(LIBINCLUDE) -O2 -tp p6 -pc 32 -convert big_endian #CPP = /lib/cpp #CFLAGS = -O #CPPFLAGS = -I$(LIBINCLUDE) #LDOPTIONS = -O2 -tp p6 -pc 32 -convert big_endian #LOCAL_LIBRARIES = #MAKE = make -i -r #-----------------------------------------------------------------------------
MM5 Tutorial
8-43
8: MM5
# 3j. MAC (OSX/xlf) #----------------------------------------------------------------------------#RUNTIME_SYSTEM = "macxlf" #FC = xlf #FCFLAGS = -I$(LIBINCLUDE) -qarch=auto #CPP = /usr/bin/cpp #CFLAGS = -O -DNOUNDERSCORE #CPPFLAGS = -I$(LIBINCLUDE) -I. -C -P -DIBM -xassembler-with-cpp #LDOPTIONS = -Wl,-stack_size,10000000,-stack_addr,0xc0000000 #LOCAL_LIBRARIES = #MAKE = make -i -r #RANLIB = ranlib #----------------------------------------------------------------------------# 4. General commands #----------------------------------------------------------------------------AR = ar ru RM = rm -f RM_CMD = $(RM) *.CKP *.ln *.BAK *.bak *.o *.i core errs ,* *~ *.a \ .emacs_* tags TAGS make.log MakeOut *.f ! GREP = grep -s CC = cc #----------------------------------------------------------------------------# 5. Options for making ./include/parame.incl #----------------------------------------------------------------------------# # FDDAGD (integer) - "1" -> FDDA gridded run FDDAGD = 0 # # FDDAOBS (integer) - "1" -> FDDA obs run FDDAOBS = 0 # # MAXNES (integer) - Max Number of Domains in simulation MAXNES = 2 # # MIX,MJX (integer) - Maximum Dimensions of any Domain MIX = 49 MJX = 52 # MKX (integer) - Number of half sigma levels in model MKX = 23 #----------------------------------------------------------------------------# 6. Physics Options # The first MAXNES values in the list will be used for the corresponding # model nests; the rest in the list can be used to compile other options. # The exception is FRAD, of which only the first value is used in the model, # (i.e., only one radiation option is used for all nests). The rest allow # other options to be compiled. # Compilation of Arakawa-Schubert cumulus scheme requires imsl. #----------------------------------------------------------------------------# IMPHYS - for explicit moisture schemes (array,integer) IMPHYS = "4,4,1,1,1,1,1,1,1,1" # - Dry,stable,warm rain,simple ice,mix phase, # - 1 ,2 ,3 ,4 ,5 # - graupel(gsfc),graupel(reisner2),schultz # -,6 ,7 ,8 MPHYSTBL = 0 # - 0=do not use look-up tables for moist # physics # - 1=use look-up tables for moist physics # (currently only simple ice and mix phase # are available) # - 2=optimized exmoisr routine (need vslib, if not # available set -DvsLIB in compile flags) # # ICUPA - for cumulus schemes (array,integer)
8-44
MM5 Tutorial
8: MM5
# - None,Kuo,Grell,AS,FC,KF,BM,KF2 1,2,3,4,5,6,7,8 ICUPA = "3,3,1,1,1,1,1,1,1,1" # # IBLTYP - for planetary boundary layer (array,integer) # - 0=no PBL fluxes,1=bulk,2=Blackadar, # 3=Burk-Thompson,4=Eta M-Y,5=MRF, # 6=Gayno-Seaman,7=Pleim-Xiu IBLTYP = "5,5,0,0,0,0,0,0,0,0" # # FRAD - for atmospheric radiation (integer) # - Radiation cooling of atmosphere # 0=none,1=simple,2=cloud,3=ccm2,rrtm=4 FRAD = "2,0,0,0,0" # # IPOLAR - (integer) for polar model used only if ISOIL=1 # 0=not polar (5-layer soil model) # 1=polar (7-layer snow/soil model) IPOLAR = 0 # # ISOIL - for multi-layer soil temperature model (integer) # - 0=no,1=yes (only works with IBLTYP=2,4,5,6) # 2=Noah land-surface scheme (IBLTYP=4,5 only) # 3=Pleim-Xiu LSM (IBLTYP=7 only) ISOIL = 1 # # ISHALLO (array,integer) - Shallow Convection Option # 1=shallow convection,0=No shallow convection ISHALLO = "0,0,0,0,0,0,0,0,0,0" #----------------------------------------------------------------------------# 7. MPP options # # For general information and updated "helpdesk" information see # http://www.mmm.ucar.edu/mm5/mpp # http://www.mmm.ucar.edu/mm5/mpp/helpdesk # #----------------------------------------------------------------------------# # Presently, of the MPP platforms only the "sp2" # is supplied with the "make deck" capability. # # MPP Software Layer MPP_LAYER=RSL #MPP_LAYER=NNTSMS # # PROCMIN_NS - minimum number of processors allowed in N/S dim # PROCMIN_NS = 1 # # PROCMIN_EW - minimum number of processors allowed in E/W dim # PROCMIN_EW = 1 # # ASSUME_HOMOGENOUS_ENVIRONMENT - on a machine with a heterogeneous # mix of processors (different speeds) setting this compile time # constant to 0 (zero) allows the program to detect the speed of each # processor at the beginning of a run and then to attempt to come up with # an optimal (static) mapping. Set this to 0 for a heterogeneous # mix of processors, set it to 1 for a homogeneous mix. Unless you # are certain you have a heterogeneous mix of processors, leave this # set to 1. Currently, this option is ignored on platforms other # than the IBM SP. # ASSUME_HOMOGENEOUS_ENVIRONMENT = 1 # #----------------------------------------------------------------------------# 7a. IBM SP2 # type 'make mpp' for the SP2
MM5 Tutorial
8-45
8: MM5
#----------------------------------------------------------------------------#RUNTIME_SYSTEM = "sp2" #MPP_TARGET=$(RUNTIME_SYSTEM) #MFC = mpxlf_r #MCC = mpcc_r #MLD = mpxlf_r #FCFLAGS = -O2 -qmaxmem=-1 -qarch=auto -qfloat=hsflt #LDOPTIONS = -bmaxdata:0x70000000 #LOCAL_LIBRARIES = -lmassv ##LOCAL_LIBRARIES = -lmass ###LOCAL_LIBRARIES = -lessl #MAKE = make -i -r #AWK = awk #SED = sed #CAT = cat #CUT = cut #EXPAND = expand #M4 = m4 #CPP = /lib/cpp -C -P #CPPFLAGS = -DMPI -Drs6000 -DSYSTEM_CALL_OK -DIBMopt ##CPPFLAGS = -DMPI -Drs6000 -DSYSTEM_CALL_OK -DIBMopt -DvsLIB #CFLAGS = -DNOUNDERSCORE -DMPI #ARCH_OBJS = milliclock.o #IWORDSIZE = 4 #RWORDSIZE = 4 #LWORDSIZE = 4 #----------------------------------------------------------------------------# 7a.1 IBM SP with Silver or Winterhawk nodes # type 'make mpp' for the SP2 # - You must compile with XLF or MPXLF version 6.1 or greater. # - Check with your system admin before linking to lessl or lmass. # - Note for running on blue.llnl.gov: # newmpxlf_r is LLNL specific wrapper around HPF 6.1 w/ HPF off. # - If the newer thread-safe mass library is available, add # the -lmass_r option to LOCAL_LIBRARIES. # - For very large domains, use -bmaxdata:2000000000 -bmaxstack:268435456 # for load options (Peter Morreale/SCD) # - If you enable -O3 optimization, add -qstrict as well #----------------------------------------------------------------------------#RUNTIME_SYSTEM = "sp2" #MPP_TARGET=$(RUNTIME_SYSTEM) ## On llnl.blue.gov, (3/99) ##MFC = time newmpxlf_r ##MCC = mpcc_r ##MLD = newmpxlf_r ## On systems with R6.1 or greater of IBM Fortran. #MFC = time mpxlf_r #MCC = mpcc_r #MLD = mpxlf_r #FCFLAGS = -O2 -qarch=auto -qcache=auto -qzerosize -qsmp=noauto -qnosave qmaxmem=-1 \ # -qspillsize=2000 #LDOPTIONS = -qsmp=noauto -bmaxdata:0x70000000 ##LOCAL_LIBRARIES = -lmass_r ##LOCAL_LIBRARIES = -lessl #LOCAL_LIBRARIES = #MAKE = make -i -r #AWK = awk #SED = sed #CAT = cat #CUT = cut #EXPAND = expand #M4 = m4 #CPP = /lib/cpp -C -P #CPPFLAGS = -DMPI -Drs6000 -DSYSTEM_CALL_OK #CFLAGS = -DNOUNDERSCORE -DMPI
8-46
MM5 Tutorial
8: MM5
#ARCH_OBJS = milliclock.o #IWORDSIZE = 4 #RWORDSIZE = 4 #LWORDSIZE = 4 #----------------------------------------------------------------------------# 7b. T3E #----------------------------------------------------------------------------#RUNTIME_SYSTEM = "t3e" #MPP_TARGET=$(RUNTIME_SYSTEM) #MFC = f90 #MCC = cc #MLD = $(MFC) ##FCFLAGS = -g #FCFLAGS = -O2 #LDOPTIONS = #LOCAL_LIBRARIES = #MAKE = make -i -r #AWK = awk #SED = sed #CAT = cat #CUT = cut #EXPAND = expand #M4 = m4 #CPP = /opt/ctl/bin/cpp -C -P #CPPFLAGS = -DMPI -DT3E #CFLAGS = -DNOUNDERSCORE -Dt3e -DT3E -DMPI #ARCH_OBJS = error_dupt3d.o t3etraps.o set_to_nan.o milliclock.o #IWORDSIZE = 8 #RWORDSIZE = 8 #LWORDSIZE = 8 #----------------------------------------------------------------------------# 7c. Origin 2000 # Note that the MPP version of MM5 is not supported for compilation under # the "modules" environment. To see if you are using modules to control # compiler versions on your machine, type "module list". # # It may be necessary to modify the MPI run time environment on the # Origin as follows: # # setenv MPI_MSGS_PER_PROC 4096 # # See also http://www.mmm.ucar.edu/mm5/mpp/helpdesk/20000621.txt # #----------------------------------------------------------------------------#RUNTIME_SYSTEM = "o2k" #MPP_TARGET=$(RUNTIME_SYSTEM) #MFC = f90 -64 -mips4 -w #MCC = cc -64 -mips4 -w #MLD = f90 -64 -mips4 ##FCFLAGS = -g #FCFLAGS = -O3 -OPT:roundoff=3:IEEE_arithmetic=3 -OPT:fold_arith_limit=2001 #LDOPTIONS = #LOCAL_LIBRARIES = -lfastm -lmpi #MAKE = make -i -r #AWK = awk #SED = sed #CAT = cat #CUT = cut #EXPAND = expand #M4 = m4 #CPP = /lib/cpp -C -P #CPPFLAGS = -DMPI -DO2K -DDEC_ALPHA -DSYSTEM_CALL_OK #CFLAGS = -DO2K -DMPI -DDEC_ALPHA #ARCH_OBJS = milliclock.o #IWORDSIZE = 4 #RWORDSIZE = 4 #LWORDSIZE = 4 #-----------------------------------------------------------------------------
MM5 Tutorial
8-47
8: MM5
# 7d. HP Exemplar #----------------------------------------------------------------------------#RUNTIME_SYSTEM = "hp" #MPP_TARGET=$(RUNTIME_SYSTEM) #MFC = f77 #MCC = mpicc #MLD = mpif77 ##FCFLAGS = +DA2.0N +DS2.0a -g #FCFLAGS = +DA2.0N +DS2.0a +O3 #LDOPTIONS = #LOCAL_LIBRARIES = #MAKE = make -i -r #AWK = awk #SED = sed #CAT = cat #CUT = cut #EXPAND = expand #M4 = m4 #CPP = /lib/cpp -C -P #CPPFLAGS = -DMPI -DSYSTEM_CALL_OK #CFLAGS = -DNOUNDERSCORE -DMPI #ARCH_OBJS = milliclock.o #IWORDSIZE = 4 #RWORDSIZE = 4 #LWORDSIZE = 4 #----------------------------------------------------------------------------# 7e. Compaq ALPHA/MPI/OpenMP (Thanks to Dave Sherden) # - For multi-threaded MPI processes (useful on dm-clusters of SMP # nodes; such as fir.mmm.ucar.edu), uncomment the definition # of the macro: SPECIAL_OMP. # - If running with MPICH (public domain MPI) uncomment # first set of definitions for MFC, MCC, MLD and LDOPTIONS. If using # the Compaq/DEC MPI, uncomment the second set. # - On prospect.ucar.edu (ES40), add the -lelan option to LDOPTIONS. #----------------------------------------------------------------------------#RUNTIME_SYSTEM = "alpha" #MPP_TARGET=$(RUNTIME_SYSTEM) ###### If using OpenMP for SMP parallelism on each MPI process ### ##SPECIAL_OMP = -omp ###### If using MPICH ### #MFC = f77 #MCC = mpicc #MLD = mpif77 #LDOPTIONS = $(SPECIAL_OMP) ###### If using DEC MPI (e.g. on fir.mmm.ucar.edu) ### ###### Compaq ES40 Cluster (prospect.ucar.edu) requires -lelan for OpenMP ##MFC = f90 ##MCC = cc ##MLD = f90 ##LDOPTIONS = -lmpi -lelan $(SPECIAL_OMP) ##LDOPTIONS = -lmpi $(SPECIAL_OMP) ###### #FCFLAGS = -O4 -Olimit 2000 -fpe0 -align dcommons -align records \ # -convert big_endian $(SPECIAL_OMP) #LOCAL_LIBRARIES = #MAKE = make -i -r #AWK = awk #SED = sed #CAT = cat #CUT = cut #EXPAND = expand #M4 = m4 #CPP = cpp -C -P #CPPFLAGS = -DMPI -DDEC_ALPHA -DSYSTEM_CALL_OK #CFLAGS = -DMPI -DDEC_ALPHA #ARCH_OBJS = milliclock.o
8-48
MM5 Tutorial
8: MM5
#IWORDSIZE = 4 #RWORDSIZE = 4 #LWORDSIZE = 4 #----------------------------------------------------------------------------# 7e.1 ALPHA Linux with MPI (Thanks Greg Lindahl, HPTi) # (This has run on jet.fsl.noaa.gov) #----------------------------------------------------------------------------#RUNTIME_SYSTEM = "alpha" #MPP_TARGET=$(RUNTIME_SYSTEM) ####### If using OpenMP for SMP parallelism on each MPI process ### ##SPECIAL_OMP = -omp ####### #MFC = fort #MCC = mpicc #MLD = mpif77 #UNDERSCORE = -DF2CSTYLE #LDOPTIONS = $(SPECIAL_OMP) -static #FCFLAGS = -O5 -arch ev6 -tune ev6 -align dcommons -align records \ # -convert big_endian $(SPECIAL_OMP) #LOCAL_LIBRARIES = #MAKE = make -i -r #AWK = awk #SED = sed #CAT = cat #CUT = cut #EXPAND = expand #M4 = m4 #CPP = /lib/cpp -traditional -C -P #CPPFLAGS = -DMPI -DDEC_ALPHA $(UNDERSCORE) -DSYSTEM_CALL_OK #CFLAGS = -DMPI -DDEC_ALPHA $(UNDERSCORE) #ARCH_OBJS = milliclock.o #IWORDSIZE = 4 #RWORDSIZE = 4 #LWORDSIZE = 4 #----------------------------------------------------------------------------# 7f. Fujitsu VPP # # These options have been updated for the newer VPP5000 system. If you # find that you have trouble compiling on your system, try removing the # -KA32 and -Ka4 option from FCFLAGS, LDOPTIONS, CFLAGS and from # MPP/RSL/RSL/makefile.vpp. Note that to successfully compile the RSL # library (MPP/RSL/RSL) you need the following two environment variables # set (syntax may vary with shells other than csh): # # Older systems: # # setenv MPIINCDIR /usr/lang/mpi/include # setenv MPILIBS '-Wl,-P -L/usr/lang/mpi/lib -lmpi -lmp' # # Newer systems: # # setenv MPIINCDIR /usr/lang/mpi2/include32 # setenv MPILIBS '-Wl,-P -L/usr/lang/mpi2/lib32 -lmpi -lmp' # # Note for older systems. The configure.user is set up for VPP5000. # For older (VPP300/700) systems, it may be necessary to remove the # -KA32 and -Ka4 flags in the settings below. # # Note with v3.4: VECTOR=1 works only with IMPHYS=5, IBLTYP=5, and ICUPA=3. # Other IMPHYS options and ICUPA options will work but won't be vector # optimized. IBLTYP=2 will not compile with VECTOR=1. # # Debugging VECTOR=1 option on non-vector platforms: see MPP/README_VECDEBUG # #----------------------------------------------------------------------------#RUNTIME_SYSTEM = "vpp" #MPP_TARGET=$(RUNTIME_SYSTEM) #MFC = frt
MM5 Tutorial
8-49
8: MM5
#MCC = cc #MLD = frt ### debugging ### FCFLAGS = -Sw -g -Pdos -lmpi -lmp ### debugging; for debugging without MPI (also need to compile RSL with DSTUBS) ### FCFLAGS = -Sw -g -Pdos -Of,-P,-E #FCFLAGS = -Sw -Wv,-Of,-te,-ilfunc,-noalias,-m3,-P255 \ # -Oe,-P -Kfast -Pdos -lmpi -lmp -KA32 #FCVFLAGS = -Sw -Wv,-te,-noalias,-ilfunc,-Of,-m3,-P255 \ # -Of,-e,-P,-u -Kfast -Pdos -lmpi -lmp -KA32 #LDOPTIONS = -Wl,-P -L$(MPILIBS) -lmpi -J -lmp -KA32 #LOCAL_LIBRARIES = #MAKE = make -i -r #AWK = awk #SED = sed #CAT = cat #CUT = cut #EXPAND = $(CAT) #M4 = m4 #CPP = /lib/cpp -C -P ### Uncomment only for debugging without MPI ### CPPFLAGS = -DMPI -Dvpp -I$(MPIINCDIR) -DKMA -DSTUBS -DSYSTEM_CALL_OK ### CFLAGS = -DMPI -Dvpp -I$(MPIINCDIR) -KA32 -Ka4 -DSTUBS ### Normal settings for CPPFLAGS and CFLAGS #CPPFLAGS = -DMPI -Dvpp -I$(MPIINCDIR) -DKMA -DSYSTEM_CALL_OK #CFLAGS = -DMPI -Dvpp -I$(MPIINCDIR) -KA32 -Ka4 #ARCH_OBJS = milliclock.o #IWORDSIZE = 4 #RWORDSIZE = 4 #LWORDSIZE = 4 #FLIC_MACROS = LMvpp.m4 #VECTOR = 1 #----------------------------------------------------------------------------# 7g1. Linux PCs. Need Portland Group pgf77 and MPICH. # # The following information has been added to this file with MM5v3.2: # # This expects mpif77 and mpicc to be installed on your system in # $(LINUX_MPIHOME)/bin . These should be configured to use the Portland Group # pgf77 (v3 or higher) and gcc, respectively. For information on how to # download, install, and configure mpich on your system, see: # # http://www.mcs.anl.gov/mpi/mpich # # Information on Portland Group compiler: # # http://www.pgroup.com # # If using a different Fortran compiler, modify FCFLAGS and LDOPTIONS as # needed. The compiler should be capable of doing little- to big-endian # conversion and it should understand integer (Cray-style) pointers. It # is recommended that the same fortran compiler be used to compile # mpich. Edit the LINUX_MPIHOME macro, below, to point to the top level mpich # directory. See also: # # http://www.mmm.ucar.edu/mm5/mpp/linuxhelp.html (by Steve Webb, NCAR/RAP) # # Note for pgf77 on RedHat Linux6: patches available from Portland Group at: # # http://www.pgroup.com/downloads/rh6patches.html # #----------------------------------------------------------------------------#RUNTIME_SYSTEM = "linux" #MPP_TARGET=$(RUNTIME_SYSTEM) ## edit the following definition for your system
8-50
MM5 Tutorial
8: MM5
#LINUX_MPIHOME = /usr/local/mpich #MFC = $(LINUX_MPIHOME)/bin/mpif77 #MCC = $(LINUX_MPIHOME)/bin/mpicc #MLD = $(LINUX_MPIHOME)/bin/mpif77 #FCFLAGS = -O2 -Mcray=pointer -tp p6 -pc 32 -Mnoframe -byteswapio #LDOPTIONS = -O2 -Mcray=pointer -tp p6 -pc 32 -Mnoframe -byteswapio #LOCAL_LIBRARIES = -L$(LINUX_MPIHOME)/build/LINUX/ch_p4/lib -lfmpich -lmpich #MAKE = make -i -r #AWK = awk #SED = sed #CAT = cat #CUT = cut #EXPAND = expand #M4 = m4 #CPP = /lib/cpp -C -P -traditional #CPPFLAGS = -DMPI -Dlinux -DSYSTEM_CALL_OK #CFLAGS = -DMPI -I$(LINUX_MPIHOME)/include #ARCH_OBJS = milliclock.o #IWORDSIZE = 4 #RWORDSIZE = 4 #LWORDSIZE = 4 #----------------------------------------------------------------------------# 7g2. Linux PCs. Need INTEL and MPICH. #----------------------------------------------------------------------------#RUNTIME_SYSTEM = "linux" #MPP_TARGET=$(RUNTIME_SYSTEM) ### edit the following definition for your system #LINUX_MPIHOME = /usr/local/mpich-intel #MFC = $(LINUX_MPIHOME)/bin/mpif77 #MCC = $(LINUX_MPIHOME)/bin/mpicc #MLD = $(LINUX_MPIHOME)/bin/mpif77 #FCFLAGS = -O2 -convert big_endian -pc32 #LDOPTIONS = -O2 -convert big_endian -pc32 #LOCAL_LIBRARIES = -L$(LINUX_MPIHOME)/build/LINUX/ch_p4/lib -lfmpich -lmpich #MAKE = make -i -r #AWK = awk #SED = sed #CAT = cat #CUT = cut #EXPAND = /usr/bin/expand #M4 = m4 #CPP = /lib/cpp -C -P #CPPFLAGS = -traditional -DMPI -Dlinux #CFLAGS = -DMPI -I/usr/local/mpi/include #ARCH_OBJS = milliclock.o #IWORDSIZE = 4 #RWORDSIZE = 4 #LWORDSIZE = 4 #----------------------------------------------------------------------------# 7h. NEC SX-4 (under development) #----------------------------------------------------------------------------#RUNTIME_SYSTEM = sx #MPP_TARGET=$(RUNTIME_SYSTEM) #MFC = f90 #MCC = cc #MLD = $(MFC) #FCFLAGS = -V -E P -Wf"-init stack=zero heap=zero -O nooverlap" -USX -float0 \ # -D$(RUNTIME_SYSTEM) -I$(LIBINCLUDE) -Wf"-L transform fmtlist summary" -g #FCFLAGS = -V -E P -C vopt -Wf"-init stack=zero heap=zero -O nooverlap" \ # -ew -USX -float0 -D$(RUNTIME_SYSTEM) -I$(LIBINCLUDE) \ # -Wf"-L transform fmtlist summary" #LDOPTIONS = -float0 -lmpi -lmpiw -g #CFLAGS = #LOCAL_LIBRARIES = #MAKE = make -i -r #AWK = awk #SED = sed
MM5 Tutorial
8-51
8: MM5
#CAT = cat #CUT = cut #EXPAND = expand #M4 = m4 #CPP = /lib/cpp -C -P #CPPFLAGS = -DMPI -Dvpp -I$(LIBINCLUDE) -C -P -DDEC_ALPHA -DSYSTEM_CALL_OK #CFLAGS = -DMPI -Dvpp -DDEC_ALPHA #ARCH_OBJS = milliclock.o #IWORDSIZE = 4 #RWORDSIZE = 4 #LWORDSIZE = 4 #ASSUME_HOMOGENEOUS_ENVIRONMENT = 1 #FLIC_MACROS = LMvpp.m4 #VECTOR = 1 #----------------------------------------------------------------------------# 7i. Sun MPI (tested on k2.ucar.edu) #----------------------------------------------------------------------------#RUNTIME_SYSTEM = "sunmpi" #MPP_TARGET=$(RUNTIME_SYSTEM) ###### If using OpenMP for SMP parallelism on each MPI process ### ##SPECIAL_OMP = ?? #MFC = mpf90 #MCC = mpcc #MLD = mpf90 #LDOPTIONS = -fast -O2 -lmpi ####### #FCFLAGS = -fast -O2 $(SPECIAL_OMP) #LOCAL_LIBRARIES = #MAKE = make -i -r #AWK = awk #SED = sed #CAT = cat #CUT = cut #EXPAND = expand #M4 = m4 #CPP = cpp -C -P #CPPFLAGS = -DMPI -DSYSTEM_CALL_OK #CFLAGS = -DMPI #ARCH_OBJS = milliclock.o #IWORDSIZE = 4 #RWORDSIZE = 4 #LWORDSIZE = 4 #----------------------------------------------------------------------------# 7j. Cray X1 #----------------------------------------------------------------------------#RUNTIME_SYSTEM = "crayx1" #MPP_TARGET=$(RUNTIME_SYSTEM) #MFC = ftn #MCC = cc #MLD = $(MFC) ## Use these for X1 cross compiler #X1_CROSS_COMP = "gcc" #X1_CROSS_CFLG = "" ## Use these for X1 native (trigger) compiler ##X1_CROSS_COMP = "cc" ##X1_CROSS_CFLG = "-hcommand" # #FCFLAGS = -x omp,mic -O3 -Ofp3 -Ogen_private_callee -V -ra -sword_pointer D$(RUNTIME_SYSTEM) ##FCFLAGS = -x omp,mic -Oscalar2,stream3,vector3 -Ofp3 -Ogen_private_callee -V -ra -sword_pointer -D$(RUNTIME_SYSTEM) # #LDOPTIONS = #LOCAL_LIBRARIES = -lmalloc #MAKE = make -i -r #AWK = awk
8-52
MM5 Tutorial
8: MM5
#SED = sed #CAT = cat #CUT = cut #EXPAND = expand #M4 = m4 #CPP = cpp -C -P #CPPFLAGS = -DMPI -D$(RUNTIME_SYSTEM) -DKMA #CFLAGS = -V -O3 -h display_opt -h report=imsvf -DMPI -D$(RUNTIME_SYSTEM) #ARCH_OBJS = error_dupt3d.o set_to_nan.o milliclock.o #IWORDSIZE = 4 #RWORDSIZE = 4 #LWORDSIZE = 4 #----------------------------------------------------------------------------# 7k. Cray XD1, Linux Opteron. Need Portland Group pgf90. # # The following information has been added to this file with MM5v3.6.3: # # Information on Portland Group compiler: # # http://www.pgroup.com # # If using a different Fortran compiler, modify FCFLAGS and LDOPTIONS as # needed. The compiler should be capable of doing little- to big-endian # conversion and it should understand integer (Cray-style) pointers. It # is recommended that the same fortran compiler be used to compile # mpich. Edit the LINUX_MPIHOME macro, below, to point to the top level mpich # directory. See also: # # http://www.mmm.ucar.edu/mm5/mpp/linuxhelp.html (by Steve Webb, NCAR/RAP) # # Note for pgf77 on RedHat Linux6: patches available from Portland Group at: # # http://www.pgroup.com/downloads/rh6patches.html # #----------------------------------------------------------------------------#RUNTIME_SYSTEM = "linux" #MPP_TARGET=$(RUNTIME_SYSTEM) # edit the following definition for your system #LINUX_MPIHOME = /usr/mpich/mpich-1.2.5 ### mpif77, mpicc are not yet installed on XD1 #MFC = $(LINUX_MPIHOME)/bin/mpif77 #MCC = $(LINUX_MPIHOME)/bin/mpicc #MLD = $(LINUX_MPIHOME)/bin/mpif77 #MFC = pgf90 #MCC = pgcc #MLD = pgf90 #FCFLAGS = -DDEC_ALPHA -O3 -fastsse -Mnoreentrant -Mcray=pointer -Mnoframe byteswapio #LDOPTIONS = -DDEC_ALPHA -O3 -Mcray=pointer -Mnoframe -byteswapio # ### need to point to header and libs for mpich explicitly for XD1 #OBJS_PATH = /opt/benchmark/shome/CONTRIB #LOCAL_OBJS = $(OBJS_PATH)/if.o $(OBJS_PATH)/strdup.o $(OBJS_PATH)/farg.o #LIB_PATH = -L $(PGI)/linux86-64/5.1/lib -L $(LINUX_MPIHOME)/lib -L /lib64 #LOCAL_LIBRARIES = $(LIB_PATH) -lgcc -lmpich -lfmpich -lrapl -lmpichfsup lpthread $(LOCAL_OBJS) # #MAKE = make -i -r #AWK = awk #SED = sed #CAT = cat #CUT = cut #EXPAND = expand #M4 = m4 #CPP = /lib/cpp -C -P -traditional #CPPFLAGS = -DDEC_ALPHA -DMPI -Dlinux -DSYSTEM_CALL_OK #CFLAGS = -O3 -DDEC_ALPHA -DMPI -I$(LINUX_MPIHOME)/include #ARCH_OBJS = milliclock.o
MM5 Tutorial
8-53
8: MM5
#IWORDSIZE = 4 #RWORDSIZE = 4 #LWORDSIZE = 4 #----------------------------------------------------------------------------# Don't touch anything below this line #----------------------------------------------------------------------------.F.i: $(RM) $@ $(CPP) $(CPPFLAGS) $*.F > $@ mv $*.i $(DEVTOP)/pick/$*.f cp $*.F $(DEVTOP)/pick .c.o: $(RM) $@ && \ $(CC) -c $(CFLAGS) $*.c .F.o: $(RM) $@ $(FC) -c $(FCFLAGS) $*.F .F.f: $(RM) $@ $(CPP) $(CPPFLAGS) $*.F > $@ .f.o: $(RM) $@ $(FC) -c $(FCFLAGS) $*.f
8.18 mm5.deck This is a Bourne shell script. Slight variations may exist on different machines. (This file is included here for reference only. Use the most up-to-date one from MM5.TAR file.) #!/bin/sh # # Version 3 of mm5 job deck # # The mm5 executable (mm5.exe) expects to find the following files # in the Run/ directory: # MMINPUT_DOMAIN1 -| # BDYOUT_DOMAIN1 | --> output files from Interpf # LOWBDY_DOMAIN1 -| # TERRAIN_DOMAIN[2,3..] if running nests --> output from Terrain # # If it is a restart run: # RESTART_DOMAIN1[,2,3..] --> output from MM5 run: renamed from # SAVE_DOMAIN1[,2,3...] # # If it is gridded FDDA run with surface analysis nudging: # SFCFDDA_DOMAIN1[2,3,...] # # If it is observational nudging run: # MM5OBS_DOMAIN1[,2,3..] --> user-created observation files # # Output from a MM5 run: # If IFTAPE = 1
8-54
MM5 Tutorial
8: MM5
# MMOUT_DOMAIN1[,2,3...] --> one output for each domain # If IFSAVE = TRUE # SAVE_DOMAIN1[,2,3...] # # # temp files should be accessible umask 022 # # Select appropriate FDDAsw if doing gridded analysis FDDA # #FDDAsw=yes # gridded FDDA input switch FDDAsw=no # # Sections # 1. Options for namelist (“mmlif”) # 2. Running... # #----------------------------------------------------------------------------# 1. Options for namelist (“mmlif”) #----------------------------------------------------------------------------# # The first dimension (column) of the arrays denotes the domain # identifier. # Col 1 = Domain #1, Col 2 = Dom #2, etc. # cat > ./Run/oparam ./Run/lparam ./Run/nparam ./Run/pparam ./Run/fparam mmlif.tmp mv mmlif.tmp mmlif rm fparam lparam nparam oparam pparam # # copy gridded FDDA files # if [ $FDDAsw = yes ]; then echo “Copy grid fdda file” for i in MMINPUT_DOMAIN[1-9] do Num=`echo $i | grep [1-9]$ | sed ‘s/.*\(.\)/\1/’` cp $i MMINPUT2_DOMAIN$Num echo “cp $i MMINPUT2_DOMAIN$Num” done fi # #----------------------------------------------------------------# # run MM5 # date echo “timex mm5.exe >! mm5.print.out “ timex ./mm5.exe > mm5.print.out 2>&1
MM5 Tutorial
8-61
8: MM5
List of MM5 Fortran Files
MM5 FORTRAN FILES domain
physics
Run boundary: mm5.F
memory address addall.F addrx1c.F addrx1n.F
fdda grid: blbrgd.F blnudgd.F blw.F bufslgd.F bufvdgd.F conv3.F in4dgd.F intpsgd.F
nopro.F nudgd.F setupgd.F
qsatgd.F
obs: errob.F in4dob.F nudob.F util: fdaoff.F unity.F setfd.F
8-62
include addr0.incl addras.incl addrasn.incl addrcu.incl addrcun.incl addrfog.incl addrfogn.incl btblk1.incl btblk2.incl chardate.incl config.INCL dusolve1.incl fddagd.incl fddaob.incl fog1d.incl fogstuf.incl functb.INCL functb.incl hdrv3.incl hdtabl.incl jrg.incl landinp.incl landuse.incl navypb.incl nestl.incl nhcnst.incl nhtens.incl nncnst.incl nnnhyd.incl nnnhydb.incl nonhyd.incl nonhydb.incl parakcu.incl param2.incl param3.incl parame parbmcu.incl parccm2.incl pargrcu.incl parkfcu.incl pbltb.incl pbltke.incl pbltken.incl pmoist.incl pnavyn.incl point2d.incl point2dn.incl point3d.incl point3dn.incl pointbc.incl pointbcn.incl radccm2.incl radiat.incl rpstar.incl rpstarn.incl soil.incl soilcnst.incl soiln.incl soilp.incl soilpn.incl sum.incl surface.incl . surfslab.incl . uprad.incl varia.incl various.incl variousn.incl bucket.incl comicl.incl parpx.incl zdiff2.incl zdiffu.incl paramgen_LSM paramsoil_STAT paramveg_USGS
bdyin.F bdyrst.F bdyten.F nudge.F bdyval.F lbdyin.F drivers: nstlev1.F nstlev2.F nstlev3.F nstlev4.F nstlev5.F
initial: init.F param.F paramr.F initts.F io: conadv.F conmas.F initsav.F mapsmp.F outprt.F output.F outsav.F outtap.F rdinit.F savread.F shutdo.F tmass.F vtran.F rdter.F write_big_ header.F write_ fieldrec.F write_flag.F dm_io.F outts.F nest: bdyovl1.F chknst.F exaint.F exchani.F exchanj.F feedbk.F filslb.F initnest.F ovlchk.F sint.F sintx.F sinty.F stotndi.F stotndt.F subch.F nestlsm.F
util: couple.F date.F dots.F dcpl3d.F dcpl3dwnd.F decouple.F equate.F fill.F fillcrs.F skipf.F smt2.F smther.F xtdot.F
dynamics advection/simple: hadv.F vadv.F vad2.F cumulus/as: aramb.F araout.F arasch.F clodwd.F cloudw.F cupara4.F entr.F kerhel.F soundd.F zx4lp.F cumulus/bm: bmpara.F cupara7.F lutbl.F spline.F tpfc.F cumulus/fc: cupara5.F fcpara.F tp.F cumulus/grell: cup.F cupara3.F maximi.F minimi.F cumulus/kf: cupara6.F dtfrz.F dtfrznew.F kfpara.F tpdd.F tpmix.F cumulus/kuo: cupara2.F cumulus/shallow: araouts.F cloudws.F entrs.F kerhels.F shallcu.F shallow.F cumulus/kf2: cupara8.F kfdrive.F kfpara2.F dtfrz2.F lutab.F tp_cape.F tpmix2.F tpmix2dd.F cumulus/shared: kfbmdata.F heipre.F dtfrz.F maxim.F, minim.F moiene.F, precip.F zunc.F, condload.F envirtht.F prof5.F
explicit/nonconv: nconvp.F explicit/simple: exmoiss.F lexmoiss.F
pbl_sfc/noahlsm: surfce.F sflx.F
solve.F sound.F
explicit/reisner1: exmoisr.F lexmoisr.F zexmoisr.F
radiation/sfc: sfcrad.F trans.F transm.F
explicit/reisner2: exmoisg.F
radiation/simple: radcool.F
explicit/gsfc: falflux.F godmic.F satice.F
radiation/cloud: lwrad.F swrad.F
explicit/schultz: schultz.F schultz_mic.F explicit/shared: consat.F gamma.F settbl.F pbl_sfc/dry: cadjmx.F convad.F gauss.F pbl_sfc/bulk: blkpbl.F pbl_sfc/hirpbl: hirpbl.F pbl_sfc/myepbl: difcof.F mixleg.F myepbl.F prodq2.F sfcdif.F vdifh.F vdifq.F vdifv.F pbl_sfc/btpbl: bound.F erase.F esatpb.F hoskeep.F initpb.F navypb.F outpb.F uvcomp.F pbl_sfc/mrfpbl: mrfpbl.F tridi2.F pbl_sfc/gspbl: gspbl.F
nonhydro:
radiation/ccm2: cldems.F colmod.F fetchd.F getabe.F getdat.F putabe.F radabs.F radclr.F radclw.F radcsw.F radctl.F radded.F radems.F radini.F radinp.F radout.F radtpl.F resetr.F stored.F wheneq.F whenfgt.F zenitm.F radiation/rrtm: mm5atm.F rrtm.F rrtm_gasabs.F rrtm_init.F rrtm_k_g.F rrtm_rtrn.F rrtm_setscef.F rrtm_taumol.F radiation/util: solar1.F inirad.F o3data.F hzdiffu/simple: coef_diffu.F diffu.F diffint.F diffmoi.F diffth.F diffthd.F
pbl_sfc/util: slab.F
MM5 Tutorial
9: MAKE
MAKE AND MM5
9
make and MM5 9-3 Logical Subdivision of code 9-3 Minimize Portability Concerns 9-3 Conditional Compilation 9-4 Configure.user File 9-4 Makefiles 9-5 Example: Top-Level Makefile 9-5 Example: Mid-Level Makefile 9-8 Example: Low-Level Makefile 9-10 CPP 9-11 CPP “inclusion” 9-12 CPP “conditionals” 9-12
MM5 Tutorial
9-1
9: MAKE
9-2
MM5 tutorial
9: MAKE AND MM5
9
MAKE AND MM5
9.1 make and MM5 The use of make in the MM5 project is necessitated for a number of reasons. 9.1.1 Logical Subdivision of code MM5 is written in FORTRAN and organized with the goal of providing a logical structure for code development and to encourage modular development of new options and subroutines. In addition, it is desired to supply the user/developer with some “pointers” as to the location of routines of particular interest. So the hope is to create something that appeared simple to the casual user but allowed more convenient access for the power user. This structure is implemented implicitly by taking advantage of the Unix file system structure. Since directories are arranged as trees, the subroutines are subdivided into conceptual groups. The include directory contains the include files for the various subroutines. The domain, dynamics, fdda, physics, and memory directories contain the subroutines divided by function. The Run directory holds the main program source code. make is the glue that holds this complicated structure together. As you have seen, make executes commands by spawning shells. These shells can in turn run make in subdirectories. This ability to nest makefiles is very powerful, since it allows you to recursively build an entire directory. 9.1.2 Minimize Portability Concerns Writing portable code involves not only following language standards, but creating a development structure that is equally standard. Every time code moves to a new machine you not only need to worry about your code but compilers, the operating system and the system environment, available libraries, and options for all of the above. The answer to this problem is two-fold, namely, use only standard tools and minimize use of esoteric options. make is such a standard tool - you will find make on every working UNIX machine you encounter. While each vendor’s make may differ in significant way, they all support a core MM5 Tutorial
9-3
9: MAKE AND MM5
subset of functionality. This means that a basic makefile with no bells and whistles will work on the vast majority of machines available on the market. “All makes are equal, but some makes are more equal than others.” Every decent Unix box will have make and cpp. However, they may throw in non-standard options. The quotation above reminds us to keep to standard constructions whenver possible. 9.1.3 Conditional Compilation One of the stated goals is conditional compilation. This is done in two different ways. make keys off the user's options to skip compilation of those directories not required. When a source file is compiled, cpp is used to avoid including code that is not required. So make skips unnecessary compilation while cpp is used to modify compilation.
9.2 Configure.user File Since make needs rules and defined dependencies (sometimes not the default ones), and there are more than 65 makefiles in the MM5 V3 directory structure (more than 70 MM5 subdirectories, over 300 Fortran files, and more than 100 C files), it would be an enomous task to make any change to these makefiles. A simple solution to solve this problem is to define all the rules and dependencies in one file and pass this file to all makefiles when make is executed. These definitions constitute part of the configure.user file. This section explains the rules and dependencies as defined in the configure.user file. SHELL .SUFFIXES FC FCFLAGS CFLAGS CPP CPPFLAGS LDOPTIONS LOCAL_LIBRARIES
MAKE -I$(LIBINCLUDE) -C -P -i -r AR
9-4
Defines the shell under which the make is run. Defines the suffixes the makefiles use. Macro to define fortran compiler. Macro to define any FORTRAN compiler options. Macro to define any c compiler options. Macro to define where to locate c pre-processor on the machine. Macro to define any cpp options. Macro to define any loader options. Macro to define any local libraries that the compiler may access. Macro to define the make command. to search for include files when compiling cpp option: all comments (except those found on cpp directive lines) are passed along. cpp option: preprocess the input without producing the line control information used by the next pass of the C compiler. make option: ignore error codes returned by invoked commands. make option: to remove any default suffix rules. Macro to define archive options.
MM5 Tutorial
9: MAKE AND MM5
RM RM_CMD GREP CC
Macro to define remove options. Macro to define what to remove when RM is executed. Macro similar to grep. Macro to define c compiler.
The following, which appears at the end of the configure.user file, defines the suffix rules a makefile uses. For example, .F.o: defines the rules to go from .F to .o files. In this case, the make will first remove any existing out-of-date .o file, and compile the .F files. .F.i: $(RM) $@ $(CPP) $(CPPFLAGS) $*.F > $@ mv $*.i $(DEVTOP)/pick/$*.f cp $*.F $(DEVTOP)/pick .c.o: $(RM) $@ && \ $(CC) -c $(CFLAGS) $*.c .F.o: $(RM) $@ $(FC) -c $(FCFLAGS) $*.F .F.f: $(RM) $@ $(CPP) $(CPPFLAGS) $*.F > $@ .f.o: $(RM) $@ $(FC) -c $(FCFLAGS) $*.f
9.3 Makefiles make is a tool that executes "makefiles". Makefiles contain "targets" and "dependencies". A target is what you want to compile. A dependency is what needs to be done to compile the target. We use a 3-tiered makefile structure following the directory struture.
• Top-Level • Middle (branching) Level • Lowest (compilation) Level Examples of each makefile follow.
• Top Level hides everything. The casual user edits the parameters and then just types "make". We take care of the rest.
• Middle Level is where branching occurs. These would be modified for something like the addition of a new moist physics scheme.
• Lowest Level is where object files are made. Change this when adding files. In addition,
the power user will make in these lower directories to avoid remaking the whole structure.
9.3.1 Example: Top-Level Makefile # Makefile for top directory DEVTOP = . include ./configure.user
MM5 Tutorial
9-5
9: MAKE AND MM5
all: (cd Util; $(MAKE)); \ ./parseconfig; \ (cd include; $(MAKE)); \ (cd memory; $(MAKE)); \ (cd fdda; $(MAKE)); \ (cd domain; $(MAKE));\ (cd physics; $(MAKE));\ (cd dynamics; $(MAKE));\ (cd Run; $(MAKE)); code: find . -name \*.i -exec rm {} \; ; \ (cd Util; $(MAKE)); \ ./parseconfig; \ (cd include; $(MAKE)); \ (cd include; $(MAKE) code); \ (cd memory; $(MAKE) code); \ (cd fdda; $(MAKE) code); \ (cd domain; $(MAKE) code);\ (cd physics; $(MAKE) code);\ (cd dynamics; $(MAKE) code);\ (cd Run; $(MAKE) code); little_f: (cd Util; $(MAKE)); \ ./parseconfig; \ (cd include; $(MAKE)); \ (cd memory; $(MAKE) little_f); \ (cd fdda; $(MAKE) little_f); \ (cd domain; $(MAKE) little_f); \ (cd physics; $(MAKE) little_f); \ (cd dynamics; $(MAKE) little_f); \ (cd Run; $(MAKE) little_f); mm5.deck: ./Util/makedeck.csh $(RUNTIME_SYSTEM); clean: (cd Util; $(MAKE) clean); \ (cd include; $(MAKE) clean); \ (cd memory; $(MAKE) clean); \ (cd fdda; $(MAKE) clean); \ (cd physics; $(MAKE) clean);\ (cd domain; $(MAKE) clean);\ (cd dynamics; $(MAKE) clean);\ (cd Run; $(MAKE) clean); \ if [ -f libutil.a ]; then $(RM) libutil.a; fi; rm_obj: (cd Util; $(MAKE) clean); \ (cd include; $(MAKE) clean); \ (cd memory; $(MAKE) clean); \ (cd fdda; $(MAKE) clean); \ (cd physics; $(MAKE) clean);\ (cd domain; $(MAKE) clean);\ (cd dynamics; $(MAKE) clean);\ (cd Run; $(MAKE) rm_obj); \ if [ -f libutil.a ]; then $(RM) libutil.a; fi; LineNumberer: $(CC) -o ./LineNumberer Util/LineNumberer.c; mmlif: (cd Run; $(MAKE) mmlif); ###
9-6
Additions for MPP
MM5 Tutorial
9: MAKE AND MM5
# # # # #
To clean after changes to configure.user, type ‘make mpclean’. To uninstall everything relating to MPP option, ‘make uninstall’. To partially remake installation, remove MPP/mpp_install and ‘make mpp’.
mpclean: clean (cd MPP/build ; /bin/rm -fr *.o *.f *.dm *.b) mpp: MPP/mpp_install (cd Util; $(MAKE)) ./parseconfig (cd include; $(MAKE)) (cd include; $(MAKE) code) (sed ‘/t touch anything below this line/,$$d’ configure.user \ > ./MPP/conf.mpp) (cd MPP; $(MAKE) col_cutter) (cd MPP/build; \ /bin/rm -f .tmpobjs ; \ $(CPP) -I../../pick ../mpp_objects_all > .tmpobjs ; \ $(MAKE) -f Makefile.$(MPP_LAYER) ) MPP/mpp_install: (cd include; $(MAKE) code ) (cd MPP/RSL/RSL ; $(MAKE) $(MPP_TARGET) ) (cd MPP/FLIC ; $(MAKE) ; $(MAKE) clean ) (cd MPP/FLIC/FLIC ; $(MAKE) ; \ $(MAKE) clean ; \ /bin/rm -f flic ; \ sed s+INSTALL_STRING_FLICDIR+`pwd`+ flic.csh > flic ; \ chmod +x flic ) (csh MPP/Makelinks $(MPP_LAYER) $(MPP_TARGET) ) touch MPP/mpp_install uninstall: (cd include; $(MAKE) clean) (cd memory; $(MAKE) clean) (cd fdda; $(MAKE) clean) (cd physics; $(MAKE) clean) (cd domain; $(MAKE) clean) (cd dynamics; $(MAKE) clean) (cd Run; $(MAKE) clean) if [ -f libutil.a ]; then $(RM) libutil.a; fi (cd MPP/FLIC/FLIC; /bin/rm -f dm ; $(MAKE) clean ) (cd MPP/FLIC; $(MAKE) clean ; /bin/rm -fr bin ) (cd MPP/RSL/RSL; $(MAKE) clean ; /bin/rm -f librsl.a ) /bin/rm -f MPP/FLIC/h/*.h /bin/rm -fr MPP/build /bin/rm -f parseconfig /bin/rm -f MPP/col_cutter /bin/rm -f Run/mm5.exe /bin/rm -f Run/mm5.mpp /bin/rm -f pick/*.incl *.h /bin/rm -f MPP/mpp_install
Note: there are several targets in the top-level makefile: all, code, little_f (for IBM xlf compiler, or any fortran compiler that does not allow the use of cpp), mm5.deck, clean, LineNumberer, and mpclean, mpp, etc. for MPP extension. If a user does not specify a target, the makefile will use the first one it sees. In this case, it is the ‘all’ target. For any target that is not placed first, a user must explicitly specify the target. For example, we use ‘make mm5.deck’ to make a job deck. The command for the target ‘all’ is to cd to a particular directory and execute make (the macro $(MAKE) is defined in configure.user file).
MM5 Tutorial
9-7
9: MAKE AND MM5
9.3.2 Example: Mid-Level Makefile # Makefile for directory physics/pbl_sfc DEVTOP = ../.. include ../../configure.user # Makefile for directory physics/pbl_sfc lib: @tmpfile=’.tmpfile’; \ echo $(IBLTYP) > $$tmpfile; \ $(GREP) “0” $$tmpfile; \ if [ $$? = 0 ]; then \ echo “IBLTYP = 0”; \ (cd dry; $(MAKE) all); \ else \ echo “IBLTYP != 0”; \ fi; \ $(GREP) “1” $$tmpfile; \ if [ $$? = 0 ]; then \ echo “IBLTYP = 1”; \ (cd bulk; $(MAKE) all); \ (cd dry; $(MAKE) all); \ else \ echo “IBLTYP != 1”; \ fi; \ $(GREP) “2” $$tmpfile; \ if [ $$? = 0 ]; then \ echo “IBLTYP = 2”; \ (cd hirpbl; $(MAKE) all); \ else \ echo “IBLTYP != 2”; \ fi; \ $(GREP) “3” $$tmpfile; \ if [ $$? = 0 ]; then \ echo “IBLTYP = 3”; \ (cd btpbl; $(MAKE) all); \ else \ echo “IBLTYP != 3”; \ fi; \ $(GREP) “4” $$tmpfile; \ if [ $$? = 0 ]; then \ echo “IBLTYP = 4”; \ (cd btpbl; $(MAKE) all); \ else \ echo “IBLTYP != 4”; \ fi; \ $(GREP) “5” $$tmpfile; \ if [ $$? = 0 ]; then \ echo “IBLTYP = 5”; \ (cd mrfpbl; $(MAKE) all); \ else \ echo “IBLTYP != 5”; \ fi; \ $(GREP) “6” $$tmpfile; \ if [ $$? = 0 ]; then \ echo “IBLTYP = 6”; \ (cd btpbl; $(MAKE) all); \ else \ echo “IBLTYP != 6”; \ fi; \ (cd util; $(MAKE) all);
9-8
MM5 Tutorial
9: MAKE AND MM5
code: @tmpfile=’.tmpfile’; \ echo $(IBLTYP) > $$tmpfile; \ $(GREP) “1” $$tmpfile; \ if [ $$? = 0 ]; then \ echo “IBLTYP = 1”; \ (cd bulk; $(MAKE) code); \ (cd dry; $(MAKE) code); \ else \ echo “IBLTYP != 1”; \ fi; \ $(GREP) “0” $$tmpfile; \ if [ $$? = 0 ]; then \ echo “IBLTYP = 0”; \ (cd dry; $(MAKE) code); \ else \ echo “IBLTYP != 0”; \ fi; \ $(GREP) “2” $$tmpfile; \ if [ $$? = 0 ]; then \ echo “IBLTYP = 2”; \ (cd hirpbl; $(MAKE) code); \ else \ echo “IBLTYP != 2”; \ fi; \ $(GREP) “3” $$tmpfile; \ if [ $$? = 0 ]; then \ echo “IBLTYP = 3”; \ (cd btpbl; $(MAKE) code); \ else \ echo “IBLTYP != 3”; \ fi; \ $(GREP) “4” $$tmpfile; \ if [ $$? = 0 ]; then \ echo “IBLTYP = 4”; \ (cd btpbl; $(MAKE) code); \ else \ echo “IBLTYP != 4”; \ fi; \ $(GREP) “5” $$tmpfile; \ if [ $$? = 0 ]; then \ echo “IBLTYP = 5”; \ (cd mrfpbl; $(MAKE) code); \ else \ echo “IBLTYP != 5”; \ fi; \ $(GREP) “6” $$tmpfile; \ if [ $$? = 0 ]; then \ echo “IBLTYP = 6”; \ (cd btpbl; $(MAKE) code); \ else \ echo “IBLTYP != 6”; \ fi; \ (cd util; $(MAKE) code); little_f: @tmpfile=’.tmpfile’; \ echo $(IBLTYP) > $$tmpfile; \ $(GREP) “0” $$tmpfile; \ if [ $$? = 0 ]; then \ echo “IBLTYP = 0”; \ (cd dry; $(MAKE) little_f); \ else \ echo “IBLTYP != 0”; \ fi; \ $(GREP) “1” $$tmpfile; \
MM5 Tutorial
9-9
9: MAKE AND MM5
if [ $$? = 0 ]; then \ echo “IBLTYP = 1”; \ (cd bulk; $(MAKE) little_f); \ (cd dry; $(MAKE) little_f); \ else \ echo “IBLTYP != 1”; \ fi; \ $(GREP) “2” $$tmpfile; \ if [ $$? = 0 ]; then \ echo “IBLTYP = 2”; \ (cd hirpbl; $(MAKE) little_f); \ else \ echo “IBLTYP != 2”; \ fi; \ $(GREP) “3” $$tmpfile; \ if [ $$? = 0 ]; then \ echo “IBLTYP = 3”; \ (cd btpbl; $(MAKE) little_f); \ else \ echo “IBLTYP != 3”; \ fi; \ $(GREP) “4” $$tmpfile; \ if [ $$? = 0 ]; then \ echo “IBLTYP = 4”; \ (cd btpbl; $(MAKE) little_f); \ else \ echo “IBLTYP != 4”; \ fi; \ $(GREP) “5” $$tmpfile; \ if [ $$? = 0 ]; then \ echo “IBLTYP = 5”; \ (cd mrfpbl; $(MAKE) little_f); \ else \ echo “IBLTYP != 5”; \ fi; \ $(GREP) “6” $$tmpfile; \ if [ $$? = 0 ]; then \ echo “IBLTYP = 6”; \ (cd btpbl; $(MAKE) little_f); \ else \ echo “IBLTYP != 6”; \ fi; \ (cd util; $(MAKE) little_f); clean: (cd (cd (cd (cd (cd (cd
btpbl; $(MAKE) clean); \ bulk; $(MAKE) clean); \ dry; $(MAKE) clean); \ hirpbl; $(MAKE) clean); \ mrfpbl; $(MAKE) clean); \ util; $(MAKE) clean);
Note: This example shows how the branching is done with the mid-level makefile. The makefile first echos the string IBLTYP defined in configure.user file to a temporary file, .tmpfile. It then checks, using grep, to see if any of the options exist (in this case, IBLTYP may be 0,1,2,3, or 5). If any of them is defined, it will go to the directory that contains the subroutines for that option and execute the make command there. Again there are several targets in this mid-level makefile: lib, code, little_f, and clean. The default is the target lib. 9.3.3 Example: Low-Level Makefile # Makefile for directory physics/pbl_sfc/mrfpbl
9-10
MM5 Tutorial
9: MAKE AND MM5
DEVTOP = ../../.. include ../../../configure.user CURRENT_DIR = $(DEVTOP)/physics/pbl_sfc/mrfpbl OBJS =\ mrfpbl.o \ tridi2.o SRC =\ mrfpbl.i \ tridi2.i SRCF =\ mrfpbl.f \ tridi2.f LIBTARGET = util TARGETDIR = ../../../ all:: $(OBJS) $(AR) $(TARGETDIR)lib$(LIBTARGET).a $(OBJS) code:: $(SRC) little_f:: $(SRCF) $(OBJS) $(AR) $(TARGETDIR)lib$(LIBTARGET).a $(OBJS) # --------------------------------------------------------------# common rules for all Makefiles - do not edit emptyrule:: clean:: $(RM_CMD) “#”* # --------------------------------------------------------------# DO NOT DELETE THIS LINE -- make depend depends on it. mrfpbl.o: mrfpbl.o: mrfpbl.o: mrfpbl.o: mrfpbl.o: mrfpbl.o: mrfpbl.o: mrfpbl.o: tridi2.o:
../../../include/parame.inc ../../../include/rpstar.incl ../../../include/varia.incl ../../../include/dusolve1.incl ../../../include/param2.incl ../../../include/param3.incl ../../../include/pmoist.incl ../../../include/point3d.incl ../../../include/point2d.incl ../../../include/various.incl ../../../include/nonhyd.incl ../../../include/nhcnst.incl ../../../include/soil.incl ../../../include/soilcnst.incl ../../../include/addrcu.incl ../../../include/pbltb.incl ../../../include/parame.incl
Note: In this example, when make is executed (‘make -i -r’), it first looks for the target all, for example. It finds that the target ‘all’ depends on a group of object files (defined by the macro OBJS). The rules for making the object files are defined in configure.user file, i.e. the .F.o: rule. The makefile checks whether any .o files are out-of-date w.r.t. the .F files, or w.r.t. any of the include files used in the .F files. The dependencies on include files are at the end of the makefile. After the .o files are made, the command on the following line specifies how to archive them into libutil.a using macro AR defined in configure.user.
9.4 CPP The cpp pre-processor is about as old as Unix itself. A pre-processor scans a file and make modiMM5 Tutorial
9-11
9: MAKE AND MM5
fications according to user-supplied definitions. Typically this facility is used for global substitutions, conditional code inclusion, including files, and function templating. We only use the cpp "conditional code inclusion" and "including files" features. Because we use cpp, our Fortran codes are named .F, in contrast to .f. Many machines recognize .F files as the ones that need to be run through cpp first before being compiled. 9.4.1 CPP “inclusion” One cpp directive is "#include ". This directive indicates that filename should be included in the source prior to compilation. Example: SUBROUTINE SOLVE(IEXEC,INEST,NN) # include <parame.incl>
turns into SUBROUTINE SOLVE(IEXEC,INEST,NN) C PARAME C C--- ADDITIONAL MEMORY REQUIREMENTS FOR RUNS , C--- GRIDDED FDDA RUNS (IFDDAG=1) AND OBS FDDA RUNS (IFDDAO=1), C--- NONHYDROSTATIC RUNS (INHYD=1), HIGHER ORDER PBL RUNS (INAV=1), C--- EXPLICIT MOISTURE SCHEME (IEXMS=1), ARAKAWA-SCHUBERT C--- CONVECTIVE PARAMETERIZATION (IARASC=1), ATMOSPHERIC C--- RADIATION (IRDDIM=1), MIXED-PHASE ICE SCHEME (IICE=1). C--- GRAUPEL SCHEME (IICEG=1), KAIN-FRITSCH AND FRITSCH-CHAPPELL. C--- CONVECTIVE PARAMETERIZATIONS (IKFFC=1), AND GAYNO-SEAMAN PBL (IGSPBL=1). C--- INTEGER IARASC,IEXMS,IFDDAG,IFDDAO,IICE,IICEG,IKFFC,ILDDIM,INAV C--- 5-LAYER SOIL (ISLDIM=1,MLX=6), OSU LAND SFC (ILDDIM=1,MLX=4). C C INTEGER IARASC,IEXMS,IFDDAG,IFDDAO,IICE,IICEG,IKFFC,ILDDIM,INAV INTEGER INAV2,INAV3,IGSPBL,INHYD,IRDDIM,ISLDIM,MLX PARAMETER (IFDDAG=1,IFDDAO=1,INHYD=1,INAV=0,INAV2=0,INAV3=0, 1 IICE=0,IICEG=0,IEXMS=1,IKFFC=0,IARASC=0,IRDDIM=1, 2 IGSPBL=0,ISLDIM=1,ILDDIM=0,MLX=6)
9.4.2 CPP “conditionals” cpp also recognizes conditional directives. You define a macro in your source code using the "define" directive - you can then use the "#ifdef" test on this macro to selectively include code. Example: In defines.incl, there are statements such as: #define #define #define #define
IMPHYS4 1 IMPHYS1 1 ICUPA3 1 IBLT2 1
In the SOLVE, the .F file has #ifdef ICUPA3 C C--- ICUPA=3: GRELL C
9-12
MM5 Tutorial
9: MAKE AND MM5
IF(ICUPA(INEST).EQ.3)THEN DO J=JBNES,JENES-1 DO K=1,KL DO I=IBNES,IENES-1 CLDFRA(I,K) = 0.0 END DO END DO CALL CUPARA3(T3D,QV3D,PSB,T3DTEN,QV3DTEN,RAINC,CLDFRA,HT,U3D, + V3D,PP3D,INEST,J,IBNES,IENES-1) DO K=1,KL DO I=IBNES,IENES-1 CLDFRA3D(I,J,K)=CLDFRA(I,K) ENDDO ENDDO ENDDO ENDIF #endif
................... and so on. In this example only ICUPA3 is defined (#define ICUPA3 1 in defines.incl), so the call to CUPARA3 will be kept in the final source code. Other cumulus schemes are not selected, so the calls to these schemes won’t be included in the source code to be compiled.
MM5 Tutorial
9-13
9: MAKE AND MM5
9-14
MM5 Tutorial
10: NESTDOWN
NESTDOWN
10
Purpose 10-3 NESTDOWN Procedure 10-3 Base State Computation 10-5 Shell Variables (for IBM job deck only) 10-5 Parameter Statements 10-5 FORTRAN Namelist Input File 10-5 Horizontal Interpolation 10-7 Vertical Corrections after Horizontal Interpolation 10-8 Temperature correction 10-8 Horizontal-wind correction 10-9 How to Run NESTDOWN 10-10 NESTDOWN didn’t Work! What Went Wrong? 10-10 File I/O 10-11 NESTDOWN tar File 10-12
MM5 Tutorial
10-1
10: NESTDOWN
10-2
MM5 tutorial
10: NESTDOWN
10
NESTDOWN
10.1 Purpose The NESTDOWN program horizontally interpolates σ−coordinate data, from a coarse grid to a fine grid. Modifying the number of vertical levels or their spatial distribution is permitted, usually for the purpose of increasing vertical resolution to complement a finer horizontal grid. The input data is on a σ-coordinate, either output from the mesoscale model or the initial condition file for model input. The output remains on the σ−coordinate. The program requires that the fine grid TERRAIN data be made available as input. Optionally, the coarse-grid lower boundary file may be required. If this program is being used to produce a higher resolution model run from a coarse grid, there are several advantages: 1) the model has lateral boundary conditions that use consistent physics with the coarse grid model; 2) the lateral boundary conditions are available at a relatively high temporal frequency; 3) the vertical structure of the atmosphere is not significantly modified through vertical interpolation. Without the inclusion of observations, though, the model is able to drift. The NESTDOWN program runs on the following platforms: Compaq/Alpha, Cray, DEC, HP, IBM, SGI, Sun, PCs running Linux (Fedora with PGI or Intel compilers), and MAC (OSX with xlf). The NESTDOWN code is written in FORTRAN 90.
10.2 NESTDOWN Procedure • ingest model input or model output (must be σ levels) and TERRAIN data • horizontally interpolate data from coarse grid to the fine grid for 3d data • horizontally interpolate 2d data that is not a subset of the TERRAIN file • horizontally interpolate 2d masked fields • compute base state for coarse grid and fine grid, base state for vertical nesting • adjust 3d fine grid temperature from base state differences MM5 Tutorial
10-3
10: NESTDOWN
• fine grid: Qv -> RH, recompute Qv with new fine grid temperature • if vertical nesting, vertically interpolate all 3d arrays linear in Z • save output for daily mean for lower boundary file • output current data for boundary file • output interpolated data for initial conditions • output data for lower boundary
INTERPF
NESTDOWN
MM5
NESTDOWN
Fig. 10.1 A schematic diagram of different NESTDOWN jobs. The NESTDOWN program is able to ingest a coarse grid file which is output from INTERPF. The NESTDOWN program is also able to ingest model output. Both NESTDOWN jobs send output to the mesoscale model.
10-4
MM5 Tutorial
10: NESTDOWN
10.3 Base State Computation The base state computation is handled identically to that described in Chapter 7 INTERPF. However, two base states are computed: one for the coarse grid and one for the fine grid. The only difference between the two is the terrain elevation, as all of the other constants use the same values (P00, Ts0, A, PTOP, TISO). If vertical nesting is requested, then the base state for the new sigma level distribution is also computed, but only for the fine grid.
10.4 Shell Variables (for NCAR IBM job deck only) All of the MM5 system job decks for NCAR IBMs are written as C-shell executables. Strict adherence to C-shell syntax is required in this section. Table 10.1: NESTDOWN IBM deck shell variables. C-shell Variable Name
Options and Use
ExpName
location of MSS files, keep same as used for deck generating input file for this program
InName
directory location of LOWBDY and TERRAIN files on MSS
RetPd
time in days to retain data on MSS after last access
InData
local names of the MM5 output, the LOWBDY, and the fine grid TERRAIN files
10.5 Parameter Statements Guess what? No domain-specific FORTRAN PARAMETER statements required.
10.6 FORTRAN Namelist Input File Most of the available options for the NESTDOWN code are handled through the namelist input file. Since this is a FORTRAN namelist (a FORTRAN 90 standard), syntax is very strict. There are five namelist records for NESTDOWN. There are no default values, the entire namelist must be correctly modified for each program execution. However, there are a few values that do not often need to be changed.
MM5 Tutorial
10-5
10: NESTDOWN
Table 10.2: NESTDOWN namelist values: RECORD0. Namelist Record
Namelist Variable
RECORD0
INPUT_FILE
CHARACTER string, coarse grid input file from INTERPF or MM5, complete with directory structure
RECORD0
INPUT_LOWBDY_FILE
CHARACTER string, LOWBDY file from coarse grid INTERPF, complete with directory structure (OPTIONAL, if USE_MM5_LOWBDY = .FALSE., this file is not necessary)
RECORD0
INPUT_TERRAIN_FILE
CHARACTER string, fine grid input file from TERRAIN, complete with directory structure
Description
Table 10.3: NESTDOWN namelist values: RECORD1. Namelist Record
Namelist Variable
Description
RECORD1
START_YEAR
starting time, 4 digit INTEGER of the year
RECORD1
START_MONTH
starting time, 2 digit INTEGER of the month
RECORD1
START_DAY
starting time, 2 digit INTEGER of the day
RECORD1
START_HOUR
starting time, 2 digit INTEGER of the hour
RECORD1
END_YEAR
ending time, 4 digit INTEGER of the year
RECORD1
END_MONTH
ending time, 2 digit INTEGER of the month
RECORD1
END_DAY
ending time, 2 digit INTEGER of the day
RECORD1
END_HOUR
ending time, 2 digit INTEGER of the hour
RECORD1
INTERVAL
time interval in seconds between analysis/forecast periods
RECORD1
LESS_THAN_24H
T/F flag of whether to force less than 24 h in the analysis (FALSE by default)
10-6
MM5 Tutorial
10: NESTDOWN
Table 10.4: NESTDOWN namelist values: RECORD2. Namelist Record
Namelist Variable
RECORD2
SIGMA_F_BU
REAL array, new sigma distribution, full-levels, bottom-up (only required for vertical nesting)
RECORD 2
SST_TO_ICE_THRESHO LD
REAL, temperature at which SST is cold enough to turn the “water” category into an “ice” category (not advised for LSM or polar physics in MM5)
Description
Table 10.5: NESTDOWN namelist values: RECORD4, 5 and 6. Namelist Record
Namelist Variable
RECORD4
WRTH2O
T/F flag, saturation is with respect to liquid water (inoperative currently)
RECORD 5
IFDATIM
INTEGER, number of time periods of initial condition output required (only 1 is necessary if not doing analysis nudging), “-1” is the magic choice for selecting all time periods are to be output
RECORD6
INTERP_METHOD
INTEGER; horizontal interpolation choice: 1 = overlapping parabolic, BINT (fast), 2 = positive definite, SINT (slow)
RECORD6
USE_MM5_LOWBDY
T/F flag, use the information inside the input file to build the LOWBDY file; TRUE implies that the user provides the INPUT_LOWBDY_FILE from the coarse grid as input
Description
10.7 Horizontal Interpolation There are several horizontal interpolation options used inside NESTDOWN, though the user is only allowed to control the selection of positive definite (slow) vs. overlapping parabolic (faster). If the user selects a 3:1 ratio in the TERRAIN program, a tailored 3:1 interpolator is employed. Other ratios require the BINT function. For masked fields, a linear 4-point interpolation is selected if all four surrounding points are valid. If at least one of the points is inappropriate for a masked interpolation and at least one of the points is valid, then an average of the possible data MM5 Tutorial
10-7
10: NESTDOWN
points (of the four surrounding values) is computed. Masked fields with no valid surrounding points have various default values based on the field name.
10.8 Vertical Corrections after Horizontal Interpolation The horizontal interpolation takes place on σ coordinates. With the introduction of the fine grid terrain elevation data, there are locations with a significant extent of orographic change. The 3D temperature, 3D mixing ratio, 2D ground temperature, and the 2D soil temperatures are slightly modified to reduce the initial imbalance the model will feel with these fields.
10.8.1 Temperature correction The air temperature and ground temperature adjustments are based upon the difference in the reference temperature change at the particular (i,j,k) location. The “F” subscript is the new variable with fine grid terrain elevation, the “C” subscript denotes the coarse terrain values, and the “R” refers to the reference temperature. Other than a few constants, the reference temperature differences are a function of terrain elevation differences only. For the ground temperature and soil temperature adjustments, the lowest σ level value of the reference temperature difference is used as the correction.
TF
ijk
= TC + ( TR – TR ) ijk C F
(10.1)
The original fine grid mixing ratio, computed with the original fine grid temperature, is converted to relative humidity. This is re-diagnosed as mixing ratio, but using the adjusted fine grid temperature. Essentially, RH is conserved.
10-8
MM5 Tutorial
10: NESTDOWN
10.8.2 Horizontal-wind correction PFU K-1
New Level K
New Level K
PF
K
PFL K+1
GROUND
GROUND
Fig. 10.2 With the introduction of new terrain elevation data in NESTDOWN, the σ level locations (fixed in height) are consequently modified. To keep surface winds on the new domain from inappropriately picking up characteristics from the free atmosphere, a limit on the depth the vertical gradient is enforced. The option to modify the horizontal winds based on the elevation differences from the horizontally interpolated terrain elevation and the fine grid input terrain is currently commented out, which matches the treatment given to fine grid domains initialized within MM5. 1. restrict the vertical extrapolation to only 1 level at most
∆P = max ( min ( ( P F – P F ), ( P FL – P F ) ), ( P FU – P F ) ) N
(10.2)
2. vertical gradient of horizontal wind components
FK + 1 – FK – 1 δF ------ = ----------------------------------P FL – P FU δP
(10.3)
δF F N = F + ∆P -----δP
(10.4)
3. new wind component
MM5 Tutorial
10-9
10: NESTDOWN
10.9 How to Run NESTDOWN 1) Obtain the source code tar file from one of the following places: Anonymous ftp: ftp://ftp.ucar.edu/mesouser/MM5V3/NESTDOWN.TAR.gz On NCAR MSS: /MESOUSER/MM5V3/NESTDOWN.TAR.gz 2) gunzip and untar the file. 3) Type ‘make’ to create an executable for your platform. 4) On the NCAR IBMs, edit nestdown.deck.ibm (located in ~mesouser/MM5V3/IBM) to select script options and to select namelist options. On a workstation, edit the namelist.input file for the namelist options. 5) On the NCAR IBMs, type nestdown.deck.ibm to compile and execute the program. It is usually a good practice to redirect the output to a file so that if the program fails, you can take a look at the log file. To do so, type: nestdown.deck.ibm >& nestdown.log, for example. On a workstation, or on a IBM running interactively, run the executable directly (nestdown >& nestdown.log). NESTDOWN input files: Either MMINPUT_DOMAINn or MMOUT_DOMAINn TERRAIN_DOMAINm LOWBDY_DOMAINn (optional) where n is the coarse grid domain identifier on input and m is the fine grid domain identifier. The location of the input files (directory information) is provided in the namelist.input file. NESTDOWN output files: MMINPUT_DOMAINm LOWBDY_DOMAINm BDYOUT_DOMAINm where m is the fine grid domain identifier on output. These files are created in the current working directory. The user has no control over the naming convention.
10.10 NESTDOWN didn’t Work! What Went Wrong? • Most of the errors from NESTDOWN that do not end with a "segmentation fault", "core dump", or "floating point error" are accompanied with a simple print statement. Though the message itself may not contain enough substance to correct the problem, it will lead you to the section of the code that failed, which should provide more diagnostic information. The last statement that NESTDOWN prints during a controlled failed run is the diagnostic error.
• To see if NESTDOWN completed successfully, first check to see if the "STOP 99999"
statement appears. Also check to see that NESTDOWN processed each of the requested times from the namelist. The initial condition file should be written-to after each analysis
10-10
MM5 Tutorial
10: NESTDOWN
time (up to the number of time periods requested in the namelist file). The boundary condition file is written-to after each analysis time, beginning with the second time period. The LOWBDY file is only written once (either the end of the NESTDOWN program if the LOWBDYfile is computed, or at the beginning of the program if the LOWBDY file is directly interpolated).
• Remember that to generate a single boundary condition file, you must have at least two
time periods, so that a lateral boundary tendency may be computed. Even if you are not going to run a long forecast, it is advantageous to provide a full day for the lateral boundary condition file, as this file contains the daily mean of the surface air temperature and thedaily mean of the SST. Users may mitigate this situation by providing the coarse grid’s LOWBDY file as input, which contains the previous analysis’ daily mean fields.
10.11 File I/O The NESTDOWN program has input and output files that are ingested and created during the program execution. The gridded input files and all of the output files are unformatted FORTRAN (binary, sequential access). One of the input files is a human-readable namelist formatted file of run-time options. The following tables are lists of input and output units for the NESTDOWN program.
Table 10.6: NESTDOWN program input files. File Name
Description
namelist.input
namelist file containing run-time options
MMINPUT_DOMAINn MMOUT_DOMAINn
coarse grid input data on σ levels
LOWBDY_DOMAINn
optional input file, contains the coarse grid reservoir temperature and mean SST
TERRAIN_DOMAINm
the fine grid terrestial information
Table 10.7: NESTDOWN program output files. File Name
Description
MMINPUT_DOMAINm
fine grid initial condition for MM5
BDYOUT_DOMAINm
fine grid lateral boundary condition for MM5
LOWBDY_DOMAINm
fine grid lower boundary condition (reservoir temperature and mean SST)
MM5 Tutorial
10-11
10: NESTDOWN
10.12 NESTDOWN tar File The nestdown.tar file contains the following files and directories: CHANGES Makefile README namelist.input nestdown.deck src/
10-12
Description of changes to the NESTDOWN program Makefile to create NESTDOWN executable General information about the NESTDOWN directory Namelist file containing run-time options Job deck for usage on one of NCAR’s Crays NESTDOWN source code
MM5 Tutorial
11: INTERPB
INTERPB
11
Purpose 11-3 INTERPB Procedure 11-3 Sea Level Pressure Computation 11-4 Vertical Interpolation/Extrapolation 11-6 Interpolation (non-hydrostatic) 11-7 Parameter Statements 11-8 FORTRAN Namelist Input File 11-8 How to Run INTERPB 11-11 INTERPB didn’t Work! What Went Wrong? 11-12 File I/O 11-12 INTERPB tar File 11-13
MM5 Tutorial
11-1
11: INTERPB
11-2
MM5 tutorial
11: INTERPB
11
INTERPB
11.1 Purpose The INTERPB program handles the data transformation required to go from the mesoscale model on σ coordinates back to pressure levels. This program only handles vertical interpolation and a few diagnostics. The output from this program is suitable for input to REGRIDDER (to re-grid a model forecast), LITTLE_R (for pressure-level re-analysis), INTERPF (for pressure to σ interpolation for generating model input) and GRAPH (for visualization and diagnostic computation). In practice, much of the post-analysis performed with MM5 data is done interactively with diagnostic and visualization tools that can handle simple vertical coordinate transformations on-the-fly. The INTERPB program can run on the following platforms: Compaq/Alpha, Cray, DEC, HP, IBM, SGI, Sun, PCs running Linux (Fedora with PGI or Intel compilers), and MAC (OSX with xlf).
11.2 INTERPB Procedure • input model input or model output data (INTERPF, NESTDOWN, MM5) • compute total pressure on dot and cross points • compute RH and Z on σ levels • compute 2D fields on both staggerings: surface pressure, sea level pressure, latitude, longitude, “computationally expedient” surface pressure
• extrapolate below ground and above top σ surface
variables: u and v, temperature, moisture, height, pressure, and ELSE options: extrapolate or constant • interpolate to selected pressure levels options: linear in pressure, linear in ln pressure, linear in pκ • output interpolated data
MM5 Tutorial
11-3
11: INTERPB
MM5
NESTDOWN
INTERPF
INTERPB
RAWINS/ LITTLE_R
INTERPF
REGRIDDER
GRAPH
Fig. 11.1 All INTERPB jobs involve ingesting σ-level model output . This data is interpolated to requested isobaric surfaces by INTERPB. The output from INTERPB is suitable for use by the MM5 programs LITTLE_R, INTERPF, REGRIDDER, and GRAPH.
11.3 Sea Level Pressure Computation Please note that the “X” used in the following computations, and throughout this chapter, signifies an arithmetic multiplication, not a cross product. 1. Find two surrounding σ levels 100 hPa above the surface, compute T at this level
Pσ P T σ ln --------B- + T σ ln --------A B P Pσ T = ------------------------------------------------------APσ ln --------BPσ
(11.1)
A
11-4
MM5 Tutorial
11: INTERPB
Pa, Ta P, T 100 hPa Pb, Tb
GROUND
Fig.11.2 To minimize the diurnal effects on the sea-level pressure computation, a pressure and temperature 100 hPa above the surface is used to compute a “surface” pressure and “surface” temperature.
2. Find Ts (surface temperature), Tm (mean temperature in layer above ground), Z at level 100 hPa above surface, and Tslv (sea level temperature) Rγ S
P SFC ------g ⎛ ⎞ T S = T ------------⎝ P ⎠
(11.2)
TS + T --------------Tm = 2
(11.3)
R P Z = Z SFC – --- ln ------------- × T m g P
(11.4)
T SLV = T + γ S Z
(11.5)
SFC
3. Then sea level pressure is calculated as
MM5 Tutorial
11-5
11: INTERPB
( g )Z SFC P SLV = P SFC exp ---------------------------------( T S + T SLV ) R -----------------------------2
(11.6)
11.4 Vertical Interpolation/Extrapolation Extrapolation is required near the surface when *
p ij σ k = KX + P TOP + P' ijk < P int – bot
(11.7)
where Pint-bot is typically 1000 hPa. This is handled in a subroutine specifically to allow pipelining of expensive inner loops for the vertical interpolation scheme. Extrapolation is required near the top of the model when *
p ij σ k = 1 + P TOP + P' ijk > P int – top
(11.8)
where Pint-top is typically PTOP. Every column of σ level data has a fictitious level inserted in the column, below the 1000 hPa level (the chosen value is 1001 hPa).
σ = KX - 2 σ = KX - 1 σ = KX GROUND
P = 1001 hPa
Fig. 11.3 Extrapolation is required on INTERPB jobs when the requested pressure is below the lowest σ level. A fictitious level is generated (1001 hPa) so that the 1000 hPa level is always available without extrapolation.
11-6
MM5 Tutorial
11: INTERPB
11.4.1 Interpolation (non-hydrostatic) Similar to the front-end interpolation, the back-end interpolation is handled as either linear in pressure, linear in ln pressure, linear in pκ. The vertical interpolation on the back-end may not be entirely contained within the bounds of valid data, resulting in extrapolation. The non-hydrostatic pressure from the forecast data is given as
Pσ
′
*
ijk
= p ij σ k + P top + P ijk
(11.9)
• Pσijk : 3-D pressure at each (i,j,k) of the σ-level variable • p*ij : 2-D field of reference surface pressure minus a constant (Ptop) • σk : 1-D vertical coordinate • Ptop : reference pressure at model lid • P’ijk : 3-D pressure perturbation from reference state
PσA, ασA P, αp PσΒ, ασB
GROUND
Fig. 11.4 For INTERPB jobs, most of the data placed on the isobaric surface is interpolated between the nearest two surrounding σ levels.
ασ ( Pσ – P ) + ασ ( P – Pσ ) A B B A α P = -----------------------------------------------------------------------Pσ – Pσ B
MM5 Tutorial
(11.10)
A
11-7
11: INTERPB
11.5 Parameter Statements And again, no domain-specific FORTRAN PARAMETER statements.
11.6 FORTRAN Namelist Input File Most of the available options for the INTERPB code are handled through the namelist input file. Since this is a FORTRAN namelist (a FORTRAN 90 standard), syntax is very strict. There are three namelist records for INTERPB. There are no default values, the entire namelist must be correctly modified for each program execution. Table 11.1: INTERPB namelist values: RECORD0. Namelist Record
Namelist Variable
RECORD0
INPUT_FILE
Description CHARACTER string, σ-level input file (from MM5, INTERPF, or NESTDOWN), complete with directory structure
Table 11.2: INTERPB namelist values: RECORD1. Namelist Record
Namelist Variable
Description
RECORD1
START_YEAR
starting time, 4 digit INTEGER of the year
RECORD1
START_MONTH
starting time, 2 digit INTEGER of the month
RECORD1
START_DAY
starting time, 2 digit INTEGER of the day
RECORD1
START_HOUR
starting time, 2 digit INTEGER of the hour
RECORD1
END_YEAR
ending time, 4 digit INTEGER of the year
RECORD1
END_MONTH
ending time, 2 digit INTEGER of the month
RECORD1
END_DAY
ending time, 2 digit INTEGER of the day
RECORD1
END_HOUR
ending time, 2 digit INTEGER of the hour
RECORD1
INTERVAL
time interval in seconds between analysis/forecast periods
11-8
MM5 Tutorial
11: INTERPB
Table 11.3: INTERPB namelist values: RECORD2. Namelist Record
Namelist Variable
RECORD2
pressure_bu_no_sfc_Pa
Description array of REALs, pressure (Pa) from 100000 up to (but not necessarily including) PTOP, the surface pressure is NOT included
Table 11.4: INTERPB namelist values: RECORD3. Namelist Record
Namelist Variable
RECORD3
print_info
Description LOGICAL: TRUE = send extra printout to the standard out; FALSE = nah, don’t do that
The entries in the RECORD4 namelist record (described in the following three tables) are optional. Default values for each variable have been established to remain internally consistent with other interpolation assumptions made through out the modeling system. This record is not available from the standard namelist.input file in the INTERPB directory, but is located in the ./ INTERPB/.hidden/namelist.input file. This record is to allow the user access to differing methods for the vertical interpolation and the extrapolations which are performed above or below the model half σ levels.
Table 11.5: INTERPB namelist values: RECORD4 Namelist Record
Namelist Variable
RECORD4
uv_interp_method
CHARACTER, “linear in p”, linear in log p”, or “linear in p**kappa” for u and v
RECORD4
t_interp_method
CHARACTER, “linear in p”, linear in log p”, or “linear in p**kappa” for temperature
RECORD4
moist_interp_method
CHARACTER, “linear in p”, linear in log p”, or “linear in p**kappa” for all moisture species
RECORD4
height_interp_method
CHARACTER, “linear in p”, linear in log p”, or “linear in p**kappa” for height
MM5 Tutorial
Description
11-9
11: INTERPB
Table 11.5: INTERPB namelist values: RECORD4 Namelist Record
Namelist Variable
RECORD4
p_interp_method
CHARACTER, “linear in p”, linear in log p”, or “linear in p**kappa” for pressure
RECORD4
else_interp_method
CHARACTER, “linear in p”, linear in log p”, or “linear in p**kappa” for everything else
Description
Table 11.6: INTERPB namelist values: RECORD4 Namelist Record
Namelist Variable
RECORD4
uv_extrap_up
CHARACTER, "constant" or "extrapolate" for u and v
RECORD4
t_extrap_up
CHARACTER, "constant" or "extrapolate" for temperature
RECORD4
moist_extrap_up
CHARACTER, "constant" or "extrapolate" for all moisture species
RECORD4
height_extrap_up
CHARACTER, "constant" or "extrapolate" for height
RECORD4
p_extrap_up
CHARACTER, "constant" or "extrapolate" for pressure
RECORD4
else_extrap_up
CHARACTER, "constant" or "extrapolate" for everything else
Description
Table 11.7: INTERPB namelist values: RECORD4 Namelist Record
Namelist Variable
RECORD4
uv_extrap_low
11-10
Description CHARACTER, "constant" or "extrapolate" for u and v
MM5 Tutorial
11: INTERPB
Table 11.7: INTERPB namelist values: RECORD4 Namelist Record
Namelist Variable
RECORD4
t_extrap_low
CHARACTER, "constant" or "extrapolate" for temperature
RECORD4
moist_extrap_low
CHARACTER, "constant" or "extrapolate" for all moisture species
RECORD4
height_extrap_low
CHARACTER, "constant" or "extrapolate" for height
RECORD4
p_extrap_low
CHARACTER, "constant" or "extrapolate" for pressure
RECORD4
else_extrap_low
CHARACTER, "constant" or "extrapolate" for everything else
Description
11.7 How to Run INTERPB 1) Obtain the source code tar file from one of the following places: Anonymous ftp: ftp://ftp.ucar.edu/mesouser/MM5V3/INTERPB.TAR.gz On NCAR MSS: MESOUSER/MM5V3/INTERPB.TAR.gz 2) gunzip and untar the INTERPB.TAR.gz file. 3) Type ‘make’ to create an executable for your platform. Users may choose to run the interpb program with the available job deck on the NCAR IBMs. This file, interpb.deck.ibm, is located on the NCAR IBM blackforest machine at ~mesouser/MM5V3/IBM. As with other job decks for the IBMs, the proper NQS instructions are included at the top, and most of the namelist options are handled through shell variables. Files are read from and written to the NCAR MSS. 4) Edit the namelist.input file to select the run-time options. 5) Run the executable directly by typing ‘interpb >& interpb.log’. INTERPB expects an input file (such as MMOUT_DOMAINn or MMINPUT_DOMAINn, where n is the domain identifier of the input data) to be provided. This is specified in the namelist.input file.
MM5 Tutorial
11-11
11: INTERPB
INTERPB outputs the files: MMOUTP_DOMAINn, REGRID_DOMAINn, and FILE_MMOUTP:blah, where n is the domain identifier of the input data and blah is the date string typical of the intermediate format files. The user has no control over the output file naming convention.
11.8 INTERPB didn’t Work! What Went Wrong? • Most of the errors from INTERPB that do not end with a "segmentation fault", "core
dump", or "floating point error" are accompanied with a simple print statement. Though the message itself may not contain enough substance to correct the problem, it will lead you to the section of the code that failed, which should provide more diagnostic information. The last statement that INTERPB prints during a controlled failed run is the diagnostic error.
• To see if INTERPB completed successfully, first check to see if the "STOP 99999" state-
ment appears. Also check to see that INTERPB processed each of the requested times from the namelist.
• When INTERPB runs into an interpolation error that it did not expect (i.e. forced to do an extrapolation when none should be required), INTERPB will stop and print out the offending (I,J,K) and pressure values.
11.9 File I/O The interpolation program has input and output files that are ingested and created during an INTERPB run. The gridded input file and the output file are unformatted FORTRAN I/O (binary, sequential access). One of the input files is a human-readable namelist formatted file of run-time options. The following tables are for the input and output units.
Table 11.8: INTERPB program input files. File Name
Description
namelist.input
namelist file containing run-time options
MMOUT_DOMAINn
model output file on s coordinates, where n is the domain identifier
11-12
MM5 Tutorial
11: INTERPB
Table 11.9: INTERPB program output files. File Name
Description
MMOUTP_DOMAINn, REGRID_DOMAINn
pressure-level file suitable for input to LITTLE_R, INTERPF and GRAPH, where n is the domain identifier (MMOUTP has all model output 3d fields, REGRID has only the traditional 3d arrays: wind, temperature, moisture, height)
FILE_MMOUTP:blah
intermediate format file, suitable for input to the REGRIDDER program (as it would come from PREGRID), where blah is the 13-character date string
11.10 INTERPB tar File The INTERPB.tar file contains the following files and directories: .hidden/ Makefile README namelist.input src/
MM5 Tutorial
Special namelist.input file with interpolation and extrapolation options Makefile to create INTERPB executable General information about the INTERPB directory Namelist file containing run-time options INTERPB source code
11-13
11: INTERPB
11-14
MM5 Tutorial
12: GRAPH
GRAPH
12
Purpose 12-3 Typical GRAPH Jobs 12-4 Plotting Table File: g_plots.tbl 12-5 Default Option Settings File: g_defaults.nml 12-7 Map Options File: g_map.tbl 12-8 Plot Color Options File: g_color.tbl 12-10 How to Run GRAPH 12-11 Available 2-D Horizontal Fields 12-14 Available Cross-Section Only Fields 12-17 Available 3-D Fields (as 2-D Horizontal or Cross-Section) 12-17 Some Hints for Running GRAPH 12-20 Sample Graph Plot File 12-21 Graph tar file 12-22 Script file to run Graph job 12-22 An Alternative Plotting Packages RIP 12-25
MM5 Tutorial
12-1
12: GRAPH
12-2
MM5 tutorial
12: GRAPH
12
GRAPH
12.1 Purpose The GRAPH program generates simple diagnostics and plots for some standard meteorological variables. The GRAPH code will process multiple times and vertical levels, computing the same diagnostics for each time and level. The GRAPH code will provide simple vertical interpolation capability, cross-section figures, and skew-T plots. The GRAPH program can overlay two plots. The GRAPH code is written to be used as a batch processor, so that all graphical choices are made from tables. The GRAPH code can process data from TERRAIN, REGRID, little_r and RAWINS, INTERPF, MM5, NESTDOWN, LOWBDY, and INTERPB. But GRAPH code cannot plot boundary condition data. The GRAPH code does not produce any standard output for use by a subsequent program. The GRAPH code in MM5 system is built on NCAR Graphics library (which is a licensed software: http://ngwww.ucar.edu, but part of it has become free which is sufficient to be used by all MM5 modeling system programs that require NCAR Graphics). It can be run on IBMs, Crays, workstations, and PC running Linux where NCAR Graphics is installed. When working on an IBM, a user can run GRAPH in batch or interactive mode. Examples of the interactive GRAPH use are shown in the section 12.7. Note on compiling GRAPH on a PC: When compiling on a PC running Linux using Portland Group Fortran compiler, it may require a library called libf2c.a. This library is required because NCAR Graphics library is compiled with GNU f77, while the GRAPH program requires PGF77 (or PGF90 - in order to deal with pointers). This library may or may not be available on your system. If it isn’t, you may obtain it from the internet for free.
MM5 Tutorial
12-3
12: GRAPH
12.2 Typical GRAPH Jobs
TERRAIN
REGRID
little_r/ RAWINS
GRAPH
INTERPF/ NESTDOWN
MM5
Fig. 12.1 Schematic diagram showing GRAPH accepting data from outputs of MM5 modeling system.
12-4
MM5 Tutorial
12: GRAPH
12.3 Plotting Table File: g_plots.tbl This table is used to define times, levels and fields to be processed and plotted by Graph. An example is shown below: TIME LEVELS: FROM 1993-03-13_00:00:00 TO 1993-03-14_00:00:00 BY 21600 (A) PRESSURE LEVEL MANDATORY: FROM SFC TO PTOP (B) PRESSURE LEVEL NON STANDARD: FROM SFC TO PTOP BY 3 (C) SIGMA LEVEL: FROM 23 TO KMAX BY 5 (D) TITLE: MM5 Tutorial (E) -----------------------------------------------------------------------------PLOT | FIELD | UNITS | CONTOUR | SMOOTH || OVERLAY | UNITS |CONTOUR |SMOOTH T/F | | | INTERVAL | PASSES || FIELD | |INTERVAL|PASSES -----|-------|-------|----------|--------||---------|-------|--------|-----T | TER | m | 100 | 0 || | | | T | WIND | m/s | 5 | 0 || BARB | m/s | 2 | 0 TP500| HEIGHT| m | 30 | 0 || VOR |10**5/s| 0 | 0 TI305| PV | PVU | 1 | 0 || P | mb | 20 | 0 X | 5 | 5 | 23 | 8 || PSLV | mb | 2 | 0 X | THETA | K | 3 | 0 || CXW | m/s | 10 | 0 X | 5 | 18 | 23 | 5 || PSLV | mb | 2 | 0 X |THETA | K | 3 | 0 || CXW | m/s | 10 | 0 T |SKEWTLL|72469 DEN DENVER, CO |39.75 |-104.87 || | | | T |SKEWTXY|STATION IN (X,Y) | 19 | 30 || | | | ------------------------------------------------------------------------------
Description of Table Header Rows: (A)
TIME
with beginning and ending times given in YYYY-MMDD_HH:MM:SS, and time increment given in seconds defined by the number after BY. If one doesn’t use :SS, the increment should be in minutes, and if one doesn’t use :MM, then the increment should be in hours. ‘BY 0’ means to plot every output times.
(B)
MANDATORY
used for pressure level dataset (such as from DATAGRID and Rawins). Will plot every mandatory level from the maximum and minimum level requrested. ALL and NONE may also used to replace the entire string after the colon.
(C)
NON STANDARD
used for pressure level dataset. Will plot every mandatory level from the maximum and minimum level requrested. Optional use of BY n will make plots at every n levels. ALL and NONE may also be used to replace the entire string after the colon.
(D)
SIGMA
used for σ-level data. Will plot the levels specified by indexes (K=1 is at the top of the model). An increment is required, and defined by the number after BY. Can also use ALL or NONE.
(E)
TITLE
except for a colon (:), any alpha-numeric character can be used to make a simple 1 line, 80 character title
MM5 Tutorial
12-5
12: GRAPH
Description of Table Columns: PLOT T/F
True or False to plot this field. Removing the line from the table has the same effect as F. If the user requests a cross section plot, the letter is X. If the user requests a plot on pressure level, the first 2 characters are TP, followed by the pressure value (TP500 is 500 mb level); if the user requests a plot on isentropic surface, the first 2 characters are TI, followed by the potential temperature value (TI330 is 330 K level). The last two options only work with σ data.
FIELD
a field name to be plotted. See complete list in Tables 8.1, 8.2 and 8.3. If the field is a skew-T, the interpretation of the following columns is changed (see the explanation below).
UNITS
units used on a plot. For some fields, there are different standard units available. If you don’t know the unit, use ‘?’.
CONTOUR INTERVAL
real or integer values used to contour a plot. If you don’t know what contour interval to use, use ‘0’. For a vector field (e.g. BARB), this value specifies the grid interval. For streamline field (VESL), this value specifies how sparse or dense streamlines are drawn.
SMOOTH PASSES
number of passes of the smoother-desmoother used for each horizontal plot.
OVERLAY FIELD
a field name for the overlay plot. May be left blank.
To create pressure-level plot from sigma-level data: TP500| HEIGHT|
m
|
30
|
0
||
VOR
|10**5/s|
P
|
0
|
0
To create isentropic-level plot from sigma-level data: TI305| PV
|
PVU
|
1
|
0
||
mb
|
20 |
0
To plot skew-T: If the plot is a skew-T (SKEWTLL or SKEWTXY), the UNITS column is used to define location name, and lat/long or X/Y appear in the following two columns. e.g. T
|SKEWTLL|72469 DEN
DENVER, CO
|39.75
|-104.87
|| | | |
To plot a vertical cross-section: For a cross-section plot, the location is defined by the 4 numbers in the columns following ‘X’, and they are in the order of X1, Y1, X2, and Y2. e.g., X X
12-6
| 5 | | THETA |
5 K
| |
23 3
| |
8 0
|| PSLV || CXW
| mb | m/s
| |
2 10 |
|
0
0
MM5 Tutorial
12: GRAPH
12.4 Default Option Settings File: g_defaults.nml This is a namelist file and it is optional. If this file exists in the current working directory when the Graph program starts executing, the file’s contents replace the previously set defaults in the Fortran code. Since this is a namelist structured file, lines may be removed. Comments after ‘;’ are not allowed on most platforms, but are shown here for easy reference only. &JOEDEF ; defaults for graph ; ISTART=1, ; sub-domain plot beginning I location ; JSTART=1, ; sub-domain plot beginning J location ; IEND=37, ; sub-domain plot ending I location ; JEND=49, ; sub-domain plot ending J location LW1=2000, ; line width, 1000 is thinnest LW2=2000, ; line width for overlay plot DASH1=-682, ; dash pattern, standard NCAR GKS method DASH2=-682, ; 4092, 3640, 2730, -682 COLOR1=12, COLOR4=12, COLOR2=9, COLOR5=9, COLOR3=8, COLOR6=8, HDRINFO=F, ; true=print header and stop LOGP=0, ; cross section: 0=linear in p; 1=linear in ln p XPTOP=200., ; top of cross section plots (mb) LABLINE=1, ; 0: no contour line labels LABMESG=0, ; 1: no message below conrec plot NOZERO=0, ; 0: allow zero line; 1:no min/max zero line; ; 2: no zero whatsoever IHIRES=0, ; 1: use high resolution US county line/China coastline &END ;
Description of variables in the namelist: ISTART JSTART IEND JEND LW1 LW2 DASH1
integer integer integer integer integer integer integer
DASH2 COLOR1 COLOR2 COLOR3 COLOR4
integer integer integer integer integer
MM5 Tutorial
for a subdomain plot, this is the I-direction starting point for a subdomain plot, this is the J-direction starting point for a subdomain plot, this is the I-direction ending point for a subdomain plot, this is the J-direction ending point line width for the first plot; 1000 is the thinest line width for the overlay plot dash pattern for the first plot; standard NCAR GKS method. A ‘-’ before a number means contour of positive values is solid, negative values is dashed 682: shorter-dashed line 2730: short-dashed line 3640: medium-dashed line 4092: long-dashed line dash pattern for the overlay plot color index for the first contour plot, labeled lines color index for the overlay plot, labeled lines color index for a dot-point plot, labeled lines color index for the first contour plot, unlabeled lines 12-7
12: GRAPH
COLOR5 COLOR6 HDRINFO LOGP
integer integer logical integer
XPTOP LABLINE LABMESG NOZERO IHIRES
real integer integer integer integer
color index for the overlay plot, unlabeled lines color index for a dot-point plot, unlabeled lines T: will only print record header for cross section plots: whether the vertical coordinate is plotted in linear p (LOGP=0), or log p (LOGP=1) top of a cross section plot (in mb) =0: no contour line labels =1: no message below conrec plot =1: no min/max zero line; =2: no zero line whatsoever =1: use high resolution US county/Asia coastline
To use higher resolution US county lines or Asia coastline, set IHIRES=1, and name the outline file to be hipone.ascii. These files may be downloaded from ftp://ftp.ucar.edu/mesouser/Data/ GRAPH directory.
12.5 Map Options File: g_map.tbl This table is used to modify map background specifics for a Graph plot. -----------------------------------------------------------------------------MAP DETAILS LL | DASH | INT | LB | LSZ | LQL | P | TTL | TSZ | TQL | OUT | DOT | LW | SP -----------------------------------------------------------------------------A | PB | D | M | 12 | 00 | Y | Y | 8 | 00 | PS | N | D | -----------------------------------------------------------------------------MAP COLORS LL LINES | LABELS | TITLE | STATES | COUNTRIES | CONTINENTS | PERIMETER -----------------------------------------------------------------------------1 | 1 | 1 | 1 | 1 | 1 | 1 ------------------------------------------------------------------------------
Description of variables in g_plots.tbl: (Text is provided by Dr. Mark Stoelinga of University of Washington.)
LL DASH INT LB LSZ
12-8
lat/lon lines over land only (L), water only (W), none (N), or both land and water (D, A, or E) lat/lon lines are dashed large (L), medium (M), small (SM), tiny (T), solid (SO), publ. style (P), or default (D) [LL.ne.N] lat/lon grid interval in degrees, or D for default [LL.ne.N] M for only MAPDRV labels (lat/lon on perimeter), N for none, or D or A for both lat/lon label size, 1 to 25 [LB.ne.N]
MM5 Tutorial
12: GRAPH
LQL
P TTL TSZ and TQL OUT
DOT LW
SP
label quality: [LB.ne.N] 00 - Complex characters / High quality 01 - Complex characters / Medium quality 02 - Complex characters / Low quality 10 - Duplex characters / High quality 11 - Duplex characters / Medium quality 12 - Duplex characters / Low quality D - Default = 11 draw just a line perimeter (N) or a line perimeter with ticks (Y) [DASH.ne.P.or.LL.eq.N] title flag: read the next two title parameters (Y) or skip to outline parameter (N) the same as LSZ and LQL except they refer to the title [both TTL.eq.Y] determines which geo-political outlines will be drawn: NO - no outlines CO - continental outlines only US - U.S. State outlines only PS - Continental + International + State outlines PO - Continental + International outlines determines whether geo-political boundaries will be dotted (Y) or solid (N) [OUT.ne.NO] gives the line width, in multiples of default (which is 1000 “units”). D gives default line width. [OUT.ne.NO.and.DOT.eq.N] (LW=2 would double the line width for geographic boundaries) gives dot spacing. Default (D) is 12 [OUT.ne.NO.and.DOT.eq.Y]
With each parameter is given a conditional statement. If that conditional statement is not met, then that particular box should be made blank. The most common error that occurs when the routine attempts to read this table is “Too many entries on line”, which simply means that the routine expected a box to be blank, but it wasn’t. One can also do color-filled maps. To do so, add the following in the g_map.tbl: MAP FILL WATER | SIX COLOR INDICIES WITH WHICH TO COLOR IN THE MAP -----------------------------------------------------------------------1 | 2 | 2 | 2 | 2 | 2 | 2 ------------------------------------------------------------------------
In this example, the water will be colored white, and land light grey according to the color tabel described below.
MM5 Tutorial
12-9
12: GRAPH
12.6 Plot Color Options File: g_color.tbl This table is used to define the color codes referred in the Graph program. -----------------------------------------------------------------------------COLOR TABLE COLOR | RED | GREEN | BLUE | NUMBER -----------------------------------------------------------------------------WHITE | 1.00 | 1.00 | 1.00 | 1 LIGHT GRAY | 0.66 | 0.66 | 0.66 | 2 DARK GRAY | 0.40 | 0.40 | 0.40 | 3 BLACK | 0.00 | 0.00 | 0.00 | 4 SKY BLUE | 0.20 | 0.56 | 0.80 | 5 BLUE | 0.00 | 0.00 | 1.00 | 6 LIGHT YELLOW | 0.80 | 0.80 | 0.00 | 7 MAGENTA | 1.00 | 0.00 | 1.00 | 8 YELLOW | 1.00 | 1.00 | 0.00 | 9 GREEN | 0.00 | 1.00 | 0.00 | 10 FOREST GREEN | 0.14 | 0.25 | 0.14 | 11 CYAN | 0.00 | 1.00 | 1.00 | 12 TAN | 0.40 | 0.30 | 0.20 | 13 BROWN | 0.25 | 0.20 | 0.15 | 14 ORANGE | 1.00 | 0.50 | 0.00 | 15 RED | 1.00 | 0.00 | 0.00 | 16 MID-BLUE | 0.00 | 0.50 | 1.00 | 17 DULL MID-BLUE | 0.00 | 0.15 | 0.30 | 18 BRIGHT FOREST GREEN | 0.20 | 0.40 | 0.20 | 19 DULL ORANGE | 0.60 | 0.30 | 0.00 | 20 ------------------------------------------------------------------------------
To make a color contour plot, change the background color from black to white using the following g_color.tbl: -----------------------------------------------------------------------------COLOR TABLE COLOR | RED | GREEN | BLUE | NUMBER -----------------------------------------------------------------------------WHITE | 1.00 | 1.00 | 1.00 | 0 BLACK | 0.00 | 0.00 | 0.00 | 1 LIGHT GRAY | 0.66 | 0.66 | 0.66 | 2 DARK GRAY | 0.40 | 0.40 | 0.40 | 3 BLACK | 0.00 | 0.00 | 0.00 | 4
.... and change color used for maps in the MAP COLORS section of the g_map.tbl from 1 to a color code other than white for borders, tick marks, and map background.
12-10
MM5 Tutorial
12: GRAPH
12.7 How to Run GRAPH Obtaining Graph tar file To run GRAPH interactively, the first step is to obtain the GRAPH tar file. The GRAPH tar file, GRAPH.TAR.gz, can be otained from ~mesouser/MM5V3 (or /fs/othrorgs/home0/mesouser/ MM5V3) from NCAR’s IBM, /MESOUSER/MM5V3/GRAPH.TAR.gz on MSS, or from the anonymous site (ftp://ftp.ucar.edu:mesouser/MM5V3). This tar file contains the GRAPH source code, makefiles, as well as the table files required to produce plots. To get the tar file from the anonymous ftp site: 1) ftp ftp.ucar.edu 2) login as anonymous 3) use your full email address as the password 4) cd mesouser/MM5V3 5) set the transfer to binary (or image), usually this is just “bin” 6) get GRAPH.TAR.gz 7) quit Or to get the tar file on NCAR’s IBM: cd /ptmp/$USER msread GRAPH.TAR.gz /MESOUSER/MM5V3/GRAPH.TAR.gz or cp ~mesouser/MM5V3/GRAPH.TAR.gz . Compiling Graph code Once you have the GRAPH.TAR.gz on the IBM’s working directory or on the local workstation, the building process is to gunzip the file, untar the file and make the executable. 1) gunzip GRAPH.TAR.gz 2) tar -xvf GRAPH.TAR After untarring the file, you should find the GRAPH directory and the following in GRAPH directory among others: Makefile g_color.tbl g_defaults.nml g_map.tbl g_plots.tbl graph.csh 3) If your dataset dimensions are greater than 200x200x40, you need to edit two files in src/ directory: scratch.incl and data.incl 4) type “make”, and this will create a graph executable called graph.exe. (if working on NCAR’s IBM, a user can simply copy the graph-run-ibm.tar.gz file from
MM5 Tutorial
12-11
12: GRAPH
~mesouser/MM5V3/IBM, unzip and untar it. An executable is inside) 5) edit the g_plots.tbl and g_defaults.nml (if needed) files. 6) if a user is working on NCAR’s IBM, he/she needs to retrieve data from MSS by typing the following: msread MMOUT_DOMAIN1[_01 through _99] MSSfilename & The ‘&’ puts the msread command in the background. Running Graph Program Graph can only process output from one domain at a time. To run Graph, type “graph.csh 1 1 MMOUT_DOMAIN1”, or graph.csh 1 3 MMOUT_DOMAIN1 MM5 V3 format file name, or root (without suffix [_01, _02]) if multiple files Number of files to process Into how many pieces is the metacode to be split upon successful GRAPH completion (using “med”)
The graph.csh tries to figure out what options you have placed on the command line. For example, a) to run graph with one data file: graph.csh 1 1 MMOUT_DOMAIN1 b) to run graph with 3 files named MMOUT_DOMAIN1, MMOUT_DOMAIN1_01, MMOUT_DOMAIN1_02: graph.csh 1 3 MMOUT_DOMAIN1 c) to run graph with 3 files named MMOUT_DOMAIN1_00, MMOUT_DOMAIN1_01, MMOUT_DOMAIN1_02: graph.csh 1 3 MMOUT_DOMAIN1 d) to run graph with 3 files named MMOUT_DOMAIN1_00, MMOUT_DOMAIN1_01, MMOUT_DOMAIN1_02: graph.csh 1 3 MMOUT_DOMAIN1*
12-12
MM5 Tutorial
12: GRAPH
Viewing Graphic Output The plot files generated by Graph are metacode files called ‘gmeta’ (and gmeta.split1, gmeta.split2, etc. if you choose to split the file), which can be viewed by NCAR Graphics utility idt, and/or transformed to postscript files using ctrans (also an NCAR Graphics utility). For example, to transfer a gmeta file to postscript file, ctrans -d ps.mono gmeta > gmeta.ps (for black-white plot), or ctrans -d ps.color gmeta > gmeta.ps (for color plot) Or to view the output interactively using an interface, idt gmeta
MM5 Tutorial
12-13
12: GRAPH
12.8 Available 2-D Horizontal Fields Table 8.1 List of 2-D horizontal fields available for plotting. Field ID
Default Units
Description
Optional Units
Optional Units
CORIOLIS
Coriolis parameter
1/s
ICLW
integrated cloud water
cm
mm
in
IRNW
integrated rain water
cm
mm
in
LATITDOT
latitude
degrees
LI
lifted index
K
LNDUS
land use categories
(no units)
LHFLUX
surface latent heat flux
W/m2
LONGIDOT longitude
degrees
LWDOWN
W/m2
longwave downward radiation
Optional Units
C
MAPFACDT map scale factor
(no units)
PBL HGT7
PBL height
m
PRECIPT
total accumulated precipitation
mm
cm
in
PRECIPC
convective accumulated precip
mm
cm
in
PRECIPN
stable accumulated precip
mm
cm
in
PRECIPTT
total precip during time interval
mm
cm
in
PRECIPTN
stable precip during time interval
mm
cm
in
PRECIPTC
convective precip during interval
mm
cm
in
PRH2O
precipitable water
cm
mm
in
PSLV
sea level pressure
mb
hPa
Pa
inHg
PSFC
surface pressure
mb
hPa
Pa
inHg
PTEND
pressure change
mb
hPa
Pa
RAINT
total accumulated precipitation
mm
cm
in
RAINC
convective accumulated precip
mm
cm
in
RAINN
stable accumulated precip
mm
cm
in
12-14
MM5 Tutorial
12: GRAPH
Field ID
Default Units
Description
Optional Units
Optional Units
RTENDT
total precip during time interval
mm
cm
in
RTENDC
convective precip during interval
mm
cm
in
RTENDN
stable precip during time interval
mm
cm
in
REGIME
PBL regimes (values 1-4)
catagory
SHFLUX
surface sensible heat flux
W/m2
SOIL T 1-6
soil temp in 1/2/4/8/16 cm layer
K
SWDOWN
shortwave downward radiation
W/m2
TER
terrain elevation
m
ft
TGD
ground temperature
K
C
THK
thickness
m
TSEASFC
sea surface temperature
K
UST
frictional velocity
m/s
Optional Units
C
if IPOLAR = 1 SEAICEFR
Sea ice fraction
(no units)
if ISOIL = 2 SOIL T 1-4
soil temp in 10/40/100/200 cm layer K
SOIL M 1-4
soil moisture in above layers
m3/m3
SOIL W 1-4
soil water in above layers
m3/m3
SFCRNOFF surface runoff
mm
UGDRNOFF underground runoff
mm
CANOPYM
canopy moisture
m
SNODPTH
water-equivalent of snow depth
mm
SNOWH
physical snow depth
m
SEAICE
sea ice flag
(no units)
ALB
albedo
fraction
ALBSNOMX maximum snow albedo MM5 Tutorial
% 12-15
12: GRAPH
Field ID
Default Units
Description
Optional Units
Optional Units
Optional Units
if FRAD >= 2 SWOUT
top outgoing shortwave radiation
W/m2
LWOUT
top outgoing longwave radiation
W/m2
if IBLTYP = 5 T2M/T2
2 m temperature
K
C
F
TD2M
2 m dewpoint temperature
K
C
F
TDD2M
2 m dewpoint depression
K
C
F
Q2M/Q2
2 m mixing ratio
kg/kg
g/kg
U10
10 m model u wind component
m/sec
knots
V10
10 m model v wind component
m/sec
knots
WIND10M
10 m wind speed
m/sec
knots
BARB10M
10 m wind barb
m/sec
knots
VECT10M
10 m wind vector
m/sec
knots
VESL10M
10 m streamline if ISOIL=3 and IBLTYP=7
M-O LENG
Monin-Obukov Length
m
NET RAD
surface net radiation
W/m2
GRNFLX
ground heat flux
W/m2
ALBEDO
surface albedo
fraction
VEGFRG
vegetation coverage
fraction
LAI
leaf area index
area/area
RA
aerodynamic resistance
s/m
RS
surface resistance
s/m
ZNT
roughness length
m
ISLTYP
soil texture type
category
12-16
MM5 Tutorial
12: GRAPH
12.9 Available Cross-Section Only Fields Table 8.2 List of cross-section-only fields available for plotting. Field ID
Default Units
Description
AM
absolute momentum
AXW
wind speed tangential to the cross- m/s section
CUV
horizontal wind barb in plane
CXW
circulation vectors in cross-section m/s plane
XXW
wind speed normal to the cross-sec- m/s tion
Optional Units
Optional Units
Optional Units
m/s
m/s
12.10 Available 3-D Fields (as 2-D Horizontal or Cross-Section) Table 8.3 List of 3-D fields available for plotting. Field ID
Default Units
Description
Optional Units
Optional Units
AGL
above ground level
m
cm
Dm
BARB
wind barbs
m/s
kt
cm/s
CLB
cloud boundary
g/kg
kg/kg
mg/kg
CLW
cloud water
g/kg
kg/kg
mg/kg
DIV
divergence of horizontal wind
10**5/s
1/s
GRA
graupel
g/kg
kg/kg
mg/kg
H
geopotential height
m
HEIGHT
geopotential height
m
ICE
cloud ice
g/kg
kg/kg
mg/kg
MDIV
moisture divergence
10**7/s
1/s
MM5 Tutorial
Optional Units
12-17
12: GRAPH
Field ID
Default Units
Description
Optional Units
Optional Units
MSE
moist static energy
J/kg
MSS
saturated moist static energy
J/kg
NCI
number concentration of ice
number/m3
OMG
vertical motion (pressure level data ub/s only)
mb/s
hPa/s
P
pressure
mb
Pa
hPa
PP
pressure perturbation
mb
Pa
hPa
PV
potential vorticity
PVU
QDIV
q-vector divergence (p data only)
QV
mixing ratio
QVEC
q-vectors (p data only)
RDTEND
g/kg
kg/kg
atmospheric radiative tendency
K/day
K/h
RH
relative humidity
%
RNW
rain water
g/kg
kg/kg
mg/kg
SLW
super-cooled liquid water
g/kg
kg/kg
mg/kg
SNOW
snow
g/kg
kg/kg
mg/kg
T
temperature
K
C
F
TD
dew point temperature
K
C
F
TDD
dew point depression
K
C
F
THETA
potential temperature
K
C
F
THETAE
equivalent potential temperature
K
C
F
TKE
turbulent kinetic energy
J/kg
U
u-component of wind
m/s
kt
cm/s
V
v-component of wind
m/s
kt
cm/s
VAB
absolute vorticity
10**5/s
1/s
VECT
horizontal wind vectors
m/s
kt
12-18
Optional Units
cm/s
MM5 Tutorial
12: GRAPH
Field ID
Description
Default Units
Optional Units
VESL
horizontal wind streamlines
m/s
VOR
relative vorticity
10**5/s
1/s
W
w-component of wind
m/s
kt
WIND
wind speed
m/s
kt
MM5 Tutorial
Optional Units
Optional Units
cm/s
12-19
12: GRAPH
12.11 Some Hints for Running GRAPH • make sure the following line is included in your .cshrc file on NCAR’s IBM or your local computer: setenv NCARG_ROOT /usr/local or setenv NCARG_ROOT /usr/local/ncarg
• NCAR Graphics has recently been upgraded to include better country/poloitcal boundaries.
This is especially true over Europe. GRAPH’s default is to use NCAR Graphics version 4.1, but GRAPH can also run with older/newer versions. - If you have an older version, remove the “-DNCARG41” directive from the Makefile. - If you have NCAR Graphics version 4.2, change the “-DNCARG41” directive in the Makefile to “-DNCARG42”.
• The GRAPH program uses the information in the record header to define the size and location of the data. This limits the "wrong" data that the user can provide to be related to the requested fields and levels to be plotted.
• GRAPH prints out information to allow you to track the program's status. It should inform the user that it is processing each of the requested time periods, and for each of the requested variables and levels.
• If the GRAPH program is not processing the time that you have requested, and it should be based upon the intervals that you have set, ask GRAPH to plot every time by setting time increment to be 0.
• GRAPH only vertically interpolates data that is on a σ coordinate. • Contour intervals for precipitation are fixed for the RAIN and RTEND fields and user modifiable for the PRECIP fields.
• Do not request a subdomain and also process soundings. The GRAPH program may not place the sounding at the correct location for the large domain.
• Errors related to the NAMELIST or other temporary files are common when porting
GRAPH to a different architecture. Use the NAMELIST format in the architecture's FORTRAN manual. Make sure and remove all temporary files and links prior to each initiation of the GRAPH C-shell.
• When GRAPH is compiled on a different architecture, the length of the records for the
direct access files must be specified in bytes (4 or 8 per word) or words. This information is found in the include file word_length.incl.
• If you get the following, and Graph stops, NEED MORE DATA SPACE it means that you need to increase the dimensions in the data.incl and scratch.incl files.
• If you get error message related to ‘Direct Access Files’, it is usually an indication that the dimensions specified in data.incl and scratch.incl files are not large enough, or the running memory is not large enough, or the word length is not correct for your particular computer architecture.
12-20
MM5 Tutorial
12: GRAPH
12.12 Sample Graph Plot File For some horizontal plots, please refer to Chapter 15, page 15-9 and 15-10.
Figure 12.1 A NW-SE cross section of potential temperature (unit K and contour interval 4 K) and 2-D in-plane cir-
Figure 12.2 A skew-T plot from a 24-h simulation at Albany, New York.
MM5 Tutorial
12-21
12: GRAPH
12.13 Graph tar file The graph.tar file contains the following files and directories: CHANGES Diff/ Makefile README Templates/ g_color.tbl g_defaults.nml g_map.tbl g_plots.tbl graph.csh src/
Description of changes to the Graph program Will contain difference files between consecutive releases Makefile to create Graph executable General information about the Graph directory and how to run Graph Job deck directory: batch deck for Cray only Color table for Graph job NAMELIST file for Graph job Map table for Graph job Table for selecting plot variables C-shell script to run Graph interactively Graph source code and low-level Makefile
12.14 Script file to run Graph job #!/bin/csh -f #
this is INTERACTIVE or BATCH
if ( $?ENVIRONMENT ) then echo "environment variable defined as $ENVIRONMENT" else setenv ENVIRONMENT INTERACTIVE echo "environment variable defined as $ENVIRONMENT" endif #
initializations, no user modification required
set FILE_EXT = ( 00 10 20 30 40 50 60 #
01 11 21 31 41 51 61
02 12 22 32 42 52 62
03 13 23 33 43 53 63
04 14 24 34 44 54 64
05 15 25 35 45 55 65
06 16 26 36 46 56 66
07 17 27 37 47 57 67
08 18 28 38 48 58 68
09 19 29 39 49 59 69
\ \ \ \ \ \ )
is it color
# set Color = BW set Color = CO # #
If this is an HP-UX machine, the generic name for fortran files starts with "ftn" not "fort".
model >& /dev/null set OK = $status if ( $OK == 0 ) then set ForUnit = ftn # echo "This is an HP-UX" else set ForUnit = fort. # echo "This is not an HP-UX" endif if ( -e numsplit.tbl ) rm numsplit.tbl if ( -e med.input ) rm med.input
12-22
MM5 Tutorial
12: GRAPH
if ( ( `uname` == AIX ) || ( `uname` == SunOS ) || if ( -e ${ForUnit}20 ) rm ${ForUnit}2* if ( -e ${ForUnit}30 ) rm ${ForUnit}3* if ( -e ${ForUnit}40 ) rm ${ForUnit}4* if ( -e ${ForUnit}50 ) rm ${ForUnit}5* if ( -e ${ForUnit}60 ) rm ${ForUnit}6* if ( -e ${ForUnit}70 ) rm ${ForUnit}7* if ( -e ${ForUnit}80 ) rm ${ForUnit}8* else if ( ( -e ${ForUnit}20 ) || ( -l ${ForUnit}20 ) if ( ( -e ${ForUnit}30 ) || ( -l ${ForUnit}30 ) if ( ( -e ${ForUnit}40 ) || ( -l ${ForUnit}40 ) if ( ( -e ${ForUnit}50 ) || ( -l ${ForUnit}50 ) if ( ( -e ${ForUnit}60 ) || ( -l ${ForUnit}60 ) if ( ( -e ${ForUnit}70 ) || ( -l ${ForUnit}70 ) if ( ( -e ${ForUnit}80 ) || ( -l ${ForUnit}80 ) endif #
( `uname` == HP-UX ) ) then
) ) ) ) ) ) )
rm rm rm rm rm rm rm
${ForUnit}2* ${ForUnit}3* ${ForUnit}4* ${ForUnit}5* ${ForUnit}6* ${ForUnit}7* ${ForUnit}8*
simple error check on call
if (( $#argv == 0 ) && ( $ENVIRONMENT == INTERACTIVE )) then echo -n "into how many pieces is the metafile to be split (1) " set NumSplit = "$
