WRFV3.3模型系统用户指南：从安装到后处理

4星 · 超过85%的资源需积分: 26 117 浏览量更新于2024-07-30 2 收藏 3.78MB PDF 举报

"WRFV3.3手册是关于气象模式WRFV3.3的使用指南，涵盖了从安装到后处理的全过程。该手册由Mesoscale & Microscale Meteorology Division的National Center for Atmospheric Research发布，适用于2010年4月发布的WRFV3.2版本，并会随着ARW模型的进一步发展而不断更新和完善。用户可以通过发送反馈至wrfhelp@ucar.edu获取支持。手册与ARW技术注释相辅相成，后者深入介绍了模型的方程、数值方法、边界条件和嵌套等细节。WRFV3.2的主要更新包括： 1. 新的物理选项： - Milbrandt-Yau双矩微观物理：这是一种新的降水和云粒子的微观物理过程模型，更准确地模拟了水滴和冰晶的形成和演变。 - Building Energy Model (BEM)：这是一种新的城市物理选项，考虑了建筑物对气候和气象的影响，提高了城市环境的模拟精度。 - 植被高度依赖的热粗糙度长度：在MM5和MYJ表面层物理选项中，植被高度的变化会影响地面的热交换特性。 - 海冰考虑：在RUC和PXLSM模式中引入了海冰因素，增强了极地地区气候的模拟。 2. 斜坡/阴影效应扩展：所有短波辐射选项现在都考虑了地形的斜坡和阴影效应，使得地形对辐射的影响更精确。 3. 半拉格朗日下落项计算：在WSM和WDM方案中采用这种方法，改进了降水粒子下落速度的计算。 4. 浅对流选项与G3方案：新增了一种浅对流模式，使用G3方案，更适合模拟小尺度的对流天气事件。 5. Garratt热量通量公式：在热带风暴应用中采用了这种公式，以更好地模拟热带气旋的能量交换。 WRFV3.3手册为用户提供了全面的指导，以利用这些更新和改进进行气象模拟研究。对于需要理解和操作WRFV3.3模型的研究者和气象学家来说，这是一份极其宝贵的资源。"

SOFTWARE INSTALLATION

WRF-ARW V3: User’s Guide 2-2

IBM Power Series AIX vendor

SGI IA64 / Opteron Linux Intel

COTS* IA32 Linux

Intel / PGI /

gfortran / g95 /

PathScale

COTS IA64 / Opteron Linux

Intel / PGI /

gfortran /

PathScale

Mac Power Series Darwin xlf / g95 / PGI / Intel

Mac Intel Darwin

g95 / PGI / Intel

* Commercial Off The Shelf systems

The WRF model may be built to run on a single processor machine, a shared-memory

machine (that use the OpenMP API), a distributed memory machine (with the appropriate

MPI libraries), or on a distributed cluster (utilizing both OpenMP and MPI). The

WRFDA and WPS packages run on the above listed systems.

Required Compilers and Scripting Languages

The majority of the WRF model, WPS, and WRFDA codes are written in Fortran (what

many refer to as Fortran 90). The software layer, RSL, which sits between WRF and

WRFDA, and the MPI interface is written in C. WPS makes direct calls to the MPI

libraries for distributed memory message passing. There are also ancillary programs that

are written in C to perform file parsing and file construction, which are required for

default building of the WRF modeling code. Additionally, the WRF build mechanism

uses several scripting languages: including perl, Cshell and Bourne shell. The traditional

UNIX text/file processing utilities are used: make, m4, sed, and awk. See Chapter 8:

WRF Software (Required Software) for a more detailed listing of the necessary pieces for

the WRF build.

Required/Optional Libraries to Download

The only library that is almost always required is the netCDF package from Unidata

(login > Downloads > NetCDF). Most of the WRF post-processing packages assume that

the data from the WRF model, the WPS package, or the WRFDA program is using the

netCDF libraries. One may also need to add /path-to-netcdf/netcdf/bin to your path so

that one may execute netCDF utility commands, such as ncdump.

SOFTWARE INSTALLATION

Note 1: If one wants to compile WRF system components on a Linux system that has

access to multiple compilers, link the correct external libraries. For example, do not link

the libraries built with PathScale when compiling the WRF components with gfortran.

Even more, the same options when building the netCDF libraries must be used when

building the WRF code (32 vs 64 bit, assumptions about underscores in the symbol

names, etc.).

Note 2: If netCDF-4 is used, be sure that it is installed without activating the new

capabilities (such as parallel I/O based on HDF5). The WRF modeling system currently

only uses its classic data model supported in netCDF-4.

If you are going to be running distributed memory WRF jobs, you need a version of MPI.

You can pick up a version of mpich

, but you might want your system group to install the

code. A working installation of MPI is required prior to a build of WRF using distributed

memory. Either MPI-1 or MPI-2 are acceptable. Do you already have an MPI lying

around? Try

which mpicc

which mpif90

which mpirun

If these are all defined executables in your path, you are probably OK. Make sure your

paths are set up to point to the MPI lib, include, and bin directories. As with the

netCDF libraries, you must build MPI consistently with the WRF source code.

Note that to output WRF model data in Grib1 format, Todd Hutchinson (WSI) has

provided a complete source library that is included with the software release. However,

when trying to link the WPS, the WRF model, and the WRFDA data streams together,

always use the netCDF format.

Post-Processing Utilities

The more widely used (and therefore supported) WRF post-processing utilities are:

 NCL (homepage and WRF download)

o NCAR Command Language written by NCAR’s Computer Information

Systems Laboratory (formerly the Scientific Computing Division)

o NCL scripts written and maintained by WRF support

o many template scripts are provided that are tailored for specific real-data

and ideal-data cases

o raw WRF output can be input with the NCL scripts

o interactive or command-file driven

WRF-ARW V3: User’s Guide 2-3

SOFTWARE INSTALLATION

Building the WRF Code

The WRF code has a fairly complicated build mechanism. It tries to determine the

architecture that you are on, and then presents you with options to allow you to select the

preferred build method. For example, if you are on a Linux machine, it determines

whether this is a 32 or 64 bit machine, and then prompts you for the desired usage of

processors (such as serial, shared memory, or distributed memory). You select from

among the available compiling options in the build mechanism. For example, do not

choose a PGI build if you do not have PGI compilers installed on your system.

 Get the WRF zipped tar file from WRFV3 from

o http://www.mmm.ucar.edu/wrf/users/download/get_source.html

always get the latest version if you are not trying to continue a long project

 unzip and untar the file

o gzip -cd WRFV3.TAR.gz | tar -xf –

o alternatively tar –xzf WRFV3.TAR.gz on some systems

 cd WRFV3

 ./configure

o serial means single processor

o smpar means Symmetric Multi-Processing/Shared Memory Parallel

(OpenMP) – this does not reliably work on most non-IBM machines

o dmpar means Distributed Memory Parallel (MPI)

o dm+sm means Distributed Memory with Shared Memory (for example,

MPI across nodes with OpenMP within a node) – usually better

performance is through dmpar only

o the second option is for nesting: 0 = no nesting, 1 = standard static nesting,

2 = nesting with a prescribed set of moves, 3 = nesting that allows a

domain to follow a vortex (typhoon tracking)

 ./compile em_real (or any of the directory names in ./WRFV3/test

directory)

 ls -ls main/*.exe

o if you built a real-data case, you should see ndown.exe, real.exe, and

wrf.exe

o if you built an ideal-data case, you should see ideal.exe and wrf.exe

Users wishing to run the WRF chemistry code must first download the WRF model tar

file, and untar it. Then the chemistry code is untar’ed in the WRFV3 directory (this is the

chem directory structure). Once the source code from the tar files is combined, then

users may proceed with the WRF chemistry build.

WRF-ARW V3: User’s Guide 2-5

SOFTWARE INSTALLATION

WRF-ARW V3: User’s Guide 2-6

Building the WPS Code

Building WPS requires that WRFV3 is already built.

 Get the WPS zipped tar file WPSV3.TAR.gz from

o http://www.mmm.ucar.edu/wrf/users/download/get_source.html



Also download the geographical dataset from the same page, there are two

choices based on the dataset size

 unzip and untar the source code file

o gzip -cd WPSV3.TAR.gz | tar -xf -

 cd WPS

 ./configure

o choose one of the options

o usually, option "1" and option “2” are for serial builds, that is the best for

an initial test, most large domains work with a single processor for WPS

o WPS requires that you build for the appropriate Grib decoding, select an

option that is suitable for the data you will use with the ungrib program

(the Grib2 option will work for either Grib1 or Grib2 data)

o If you select a Grib2 option, you must have those libraries prepared and

built in advance (see the chapter on WPS for the location of these

compression libraries)

 ./compile

 ls -ls *.exe

o you should see geogrid.exe, ungrib.exe, and metgrid.exe (if

you are missing both geogrid.exe and metgrid.exe, you probably

need to fix where the path to WRF is pointing in the configure.wps

file; if you are missing ungrib.exe, try a Grib1-only build to further

isolate the problem)

 ls -ls util/*.exe

o you should see a number of utility executables: avg_tsfc.exe,

calc_ecmwf_p.exe, g1print.exe, g2print.exe,

height_ukmo.exe, mod_levs.exe, plotfmt.exe,

plotgrids.exe

, and rd_intermediate.exe (files requiring

NCAR Graphics are plotfmt.exe and plotgrids.exe)

 if geogrid.exe and metgrid.exe executables are missing, probably the

path to the WRFV3 directory structure is incorrect (found inside the

configure.wps file)

 if the ungrib.exe is missing, probably the Grib2 libraries are not linked or

built correctly

 if the plotfmt.exe or the plotgrids.exe programs are missing, probably

the NCAR Graphics path is set incorrectly

剩余353页未读，继续阅读

sunmin_angela

粉丝: 0
资源: 1

WRFV3.3模型系统用户指南：从安装到后处理

WRF模式运行及后处理简介

WRFDA_V3.6.1.tar.GZ

WPSV3.9.1.TAR.gz

WRFV3.3安装记录

WRFV3.6.1.TAR.gz

auto-install-WRFV4-master_自动安装wrf脚本_

WRF4.0官方手册

WRFv2.2中文安装运行入门与环境设置详解

新建domain-wrf：Linux下WRFV2.2.1模式安装指南

tar -xvf WRFV4.0.TAR.gz

最新资源