WRF - Developmental Testbed Center

More documents

Recommendations

Info

User’s Guide for the NMM Core of theWeather Research and Forecast (WRF) ModelingSystem Version 3Chapter 6: WRF SoftwareTable of Contents• WRF Build Mechanism• Registry• I/O Applications Program Interface (I/O API)• Timekeeping• Software Documentation• PerformanceWRF Build MechanismThe WRF build mechanism provides a uniform apparatus for configuring and compilingthe WRF model and pre-processors over a range of platforms with a variety of options.This section describes the components and functioning of the build mechanism. Forinformation on building the WRF code, see Chapter 2.Required softwareThe WRF build relies on Perl version 5 or later and a number of UNIX utilities: Csh andBourne shell, make, M4, sed, awk, and the uname command. A C compiler is needed tocompile programs and libraries in the tools and external directories. The WRF code itselfis Fortran90. For distributed-memory, MPI and related tools and libraries should beinstalled.Build Mechanism ComponentsDirectory structure: The directory structure of WRF consists of the top-level directoryplus directories containing files related to the WRF software framework (frame), theWRF model (dyn_em, dyn_nmm, phys, share), configuration files (arch, Registry),helper programs (tools), and packages that are distributed with the WRF code (external).Scripts: The top-level directory contains three user-executable scripts: configure,compile, and clean. The configure script relies on a Perl script in arch/Config_new.pl.WRF-NMM V3: User’s Guide 6-1
Programs: A significant number of WRF lines of code are automatically generated atcompile time. The program that does this is tools/registry and it is distributed as sourcecode with the WRF model.Makefiles: The main makefile (input to the UNIX make utility) is in the top-leveldirectory. There are also makefiles in most of the subdirectories that come with WRF.Make is called recursively over the directory structure. Make is not used directly tocompile WRF; the compile script is provided for this purpose.Configuration files: The configure.wrf contains compiler, linker, and other buildsettings, as well as rules and macro definitions used by the make utility. Configure.wrf isincluded by the Makefiles in most of the WRF source distribution (Makefiles in tools andexternal directories do not include configure.wrf). The configure.wrf file in the top-leveldirectory is generated each time the configure script is invoked. It is also deleted by clean-a. Thus, configure.wrf is the place to make temporary changes: optimization levels,compiling with debugging, etc., but permanent changes should be made inarch/configure_new.defaults.The arch/configure_new.defaults file contains lists of compiler options for all thesupported platforms and configurations. Changes made to this file will be permanent.This file is used by the configure script to generate a temporary configure.wrf file in thetop-level directory. The arch directory also contains the files preamble_new andpostamble_new, which are the unchanging parts of the configure.wrf file that isgenerated by the configure script.The Registry directory contains files that control many compile-time aspects of the WRFcode (described elsewhere). The files are named Registry.core, where core is either EM(for builds using the Eulerian Mass (ARW) core), NMM (for builds using the NMMcore), or NMM_NEST (for builds using the NMM core with nesting capability). Theconfigure script copies one of these to Registry/Registry, which is the file thattools/registry will use as input. Changes to Registry/Registry will be lost; permanentchanges should be made to Registry.core.Environment variables: Certain aspects of the configuration and build are controlled byenvironment variables: the non-standard locations of NetCDF libraries or the PERLcommand, which dynamic core to compile, machine-specific options (e.g.OBJECT_MODE on the IBM systems), etc.In addition to WRF-related environment settings, there may also be settings specific toparticular compilers or libraries. For example, local installations may require setting avariable like MPICH_F90 to make sure the correct instance of the Fortran 90 compiler isused by the mpif90 command.How the WRF build worksThere are two steps in building WRF: configuration and compilation.WRF-NMM V3: User’s Guide 6-2
Page 1 and 2:
ForewordUser's Guide for the NMM Co
Page 3 and 4:
• WPP Directory Structure 7-3•
Page 5 and 6:
The WRF modeling system software is
Page 7 and 8:
WRF-NMM FLOW CHARTTerrestrialDataMo
Page 9 and 10:
Vendor Hardware OS CompilerCray X1
Page 11 and 12:
If all of these executables are def
Page 13 and 14:
Once the tar file is obtained, gunz
Page 15 and 16:
HWRF is set, then (3) will be autom
Page 17 and 18:
In addition to these three links, a
Page 19 and 20:
• Real-data simulations• Non-hy
Page 21 and 22:
k. Morrison double-moment scheme (1
Page 23 and 24:
g. GFDL surface layer (88): (This s
Page 25 and 26:
Other physics optionsa. gwd_opt: Gr
Page 27 and 28:
to the convergence of meridians app
Page 29 and 30:
Variable NamesValue(Example)Descrip
Page 31 and 32:
Page 33 and 34:
Page 35 and 36:
Page 37 and 38:
Page 39 and 40:
mpirun.lsf wrf.exeand for interacti
Page 41 and 42: The boundary conditions for the nes
Page 43 and 44: Examples:1. One nest and one level
Page 45 and 46: ottom_top_stag = 28 ;soil_layers_st
Page 47 and 48: float HLENSW(Time, south_north, wes
Page 49 and 50: float HBOTS(Time, south_north, west
Page 51 and 52: operational mesoscale Eta model. J.
Page 53 and 54: Mlawer, E. J., S. J. Taubman, P. D.
Page 55 and 56: NCEP WRF Postprocessor (WPP)WPP Int
Page 57 and 58: ./configureYou will be given a list
Page 59 and 60: equested output field. If the pre-r
Page 61 and 62: RAINCV SNOW HBOTRAINNCVSNOWCNote: F
Page 63 and 64: Running WPPFour scripts for running
Page 65 and 66: i. As the grid id of a pre-defined
Page 67 and 68: The GrADS package is available from
Page 69 and 70: Height on pressure surface HEIGHT O
Page 71 and 72: MELTPrecipitation type (4 types) -
Page 73 and 74: Press at tropopause PRESS AT TROPOP
Page 75 and 76: RIP4RIP IntroductionRIP (which stan
Page 77 and 78: A successful compilation will resul
Page 79 and 80: iinterp = 0v v v v vH V H V h h h h
Page 81 and 82: espectively, of the centered domain
Page 83 and 84: This can be either 'h' (for hours),
Page 85: eal variable expect values that are
Page 88 and 89: of all the requested trajectories a
Page 90 and 91: Creating Vis5D Dataset with RIPVis5
Page 94 and 95: Configuration: The configure script
Page 96 and 97: This program reads the contents of
Page 98 and 99: Period - Describes communications f
Page 100 and 101: fine grid), f (forcing, how the lat
Page 102 and 103: # halo HALO_NMM_K dyn_nmm8:q2;24:t
Page 104 and 105: (http://www.mmm.ucar.edu/wrf/WG2/Ti
Page 106 and 107: User's Guide for the NMM Core of th
Page 108 and 109: 2. Make sure the files listed below
Page 110 and 111: User's Guide for the NMM Core of th
Page 112 and 113: Program geogridThe purpose of geogr
Page 114 and 115: 1. Define a model coarse domain and
Page 116 and 117: to GEOGRID.TBL in the geogrid direc
Page 118 and 119: the GRIB data were downloaded to th
Page 120 and 121: By this point, there is generally n
Page 122 and 123: two nests are defined to have the s
Page 124 and 125: Note: For the WRF-NMM the variables
Page 126 and 127: simulations may use a constant SST
Page 128 and 129: entire simulation domain, and data
Page 130 and 131: that lists the variables and attrib
Page 132 and 133: http://www.ecmwf.int/products/data/
Page 134 and 135: intermediate formats (metgrid/src/r
Page 136 and 137: GRIB1| Level| From | To |Param| Typ
Page 138 and 139: corresponding source grid point. Gi
Page 140 and 141: tile_x = 1200tile_y = 1200tile_z =
Page 142 and 143:
1. PARENT_ID : A list of MAX_DOM in
Page 144 and 145:
V -DX- H| / |DY dx DY| / |H - DX- V
Page 146 and 147:
intermediate files if ungrib is to
Page 148 and 149:
the index and data tiles for the da
Page 150 and 151:
1. PROJECTION : A character string
Page 152 and 153:
25. SCALE_FACTOR : A real value tha
Page 154 and 155:
10. INTERP_MASK : The name of the f
Page 156 and 157:
1. four_pt : Four-point bi-linear i
Page 158 and 159:
8. search : Breadth-first search in
Page 160 and 161:
19 Mixed Tundra20 Barren TundraTabl
Page 162 and 163:
LU_INDEX:units = "category" ;LU_IND
Page 164 and 165:
netcdf met_em.d01.2009-01-05_12:00:
Page 166:
}:ISOILWATER = 14 ;:grid_id = 1 ;:p
show all

WRF - Developmental Testbed Center

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?