WRF-ARW用户指南：从安装到预处理系统详解

需积分: 9 84 浏览量更新于2024-07-16 1 收藏 37.7MB PDF 举报

"ARWUsersGuideV3.9.pdf 是一份关于 Weather Research & Forecast (WRF) 模式的用户指南，旨在帮助用户全面理解和使用这一先进的气象预报模型系统。该文档详细介绍了WRF的组成部分、软件安装过程、预处理系统（WPS）的功能和操作方法等关键知识点。" 在WRF模式中，它由多个组件组成，包括WRF-ARW（Advanced Research WRF），这是一个用于数值天气预报和环境模拟的高级研究模型。这份用户指南首先概述了WRF模型系统的各个部分，如物理过程、数据同化和输出处理等，让用户对WRF有一个基本的认识。在软件安装章节，文档详细列出了所需的编译器、脚本语言以及必须下载的库。这包括了构建WRF代码、WPS代码以及数据同化代码（针对3DVAR和4DVAR）所需的各种依赖。此外，还提到了设置UNIX环境变量的重要性，这对于正确编译和运行WRF程序至关重要。 WRF预处理系统（WPS）是WRF工作流程中的重要一环，负责将原始气象数据转化为模型可用的格式。用户指南详细讲解了每个WPS程序的功能，包括地理网格生成、地形处理、初始化数据的准备等。用户可以学习如何安装和运行WPS，以及创建嵌套区域、选择土地使用数据、设置重力波阻力方案的静态数据、整合多种气象数据源、处理非等压面气象数据集等。对于湖泊表面温度（SST）的初始化，指南提供了替代方法，允许用户根据特定需求定制。WPS的并行化处理能力也被详细介绍，使用户能利用多核处理器提高计算效率。最后，检查WPS输出的方法和一些实用程序的使用也被涵盖，帮助用户验证数据质量和进行中间格式的数据写入。 ARWUsersGuideV3.9.pdf是学习和操作WRF模式的宝贵资源，覆盖了从安装到实际运行的所有关键步骤，对于气象学研究人员、预报员以及任何对数值天气预报感兴趣的人来说，都是一个详尽且实用的教程。

SOFTWARE INSTALLATION

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

Post-Processing Utilities

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

• NCL !"#$%&'(%)'*+),-.)+#/*0#'+1

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

(http://www2.mmm.ucar.edu/wrf/OnLineTutorial/Graphics/NCL/NCL_examples.htm)

o raw WRF output can be input with the NCL scripts

o interactive or command-file driven

• GrADS (homepage and WRF download)

o download GrADS executable, build format converter

o programs (ARWpost) are available to convert the WRF output into an

input format suitable for GrADS

o simple to generate publication quality

o interactive or command-file driven

• RIP4 (homepage and WRF download)

o RIP4 written and maintained by Mark Stoelinga, UW

o interpolation to various surfaces, trajectories, hundreds of diagnostic

calculations

o Fortran source provided

o based on the NCAR Graphics package

o pre-processor converts WRF, WPS, and WRFDA data to RIP input format

o table driven

UNIX Environment Settings

There are only a few environmental settings that are WRF system related. Most of these

are not required, but when things start acting badly, test some out. In Cshell syntax:

• setenv WRF_EM_CORE 1

o explicitly defines which model core to build

• setenv WRF_NMM_CORE 0

o explicitly defines which model core NOT to build

• setenv WRF_DA_CORE 0

o explicitly defines no data assimilation

• setenv NETCDF /usr/local/netcdf)(or wherever you have it stored))

o '00)#2)3"%),-.)4#$&#*%*35)/'*3)6#3")3"%)076)'*+)3"%)7*408+%)

+79%43#97%5)

• setenv OMP_NUM_THREADS n)(where n is the number of procs to use))

SOFTWARE INSTALLATION

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

o if you have OpenMP on your system, this is how to specify the number of

threads

• setenv MP_STACK_SIZE 64000000

o OpenMP blows through the stack size, set it large

o However, if the model still crashes, it may be a problem of over-

specifying stack size. Set stack size sufficiently large, but not unlimited.

o On some systems, the equivalent parameter could be KMP_STACKSIZE,

or OMP_STACKSIZE

• unlimit

o especially if you are on a small system

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.

An instructional web site describes the sequence of steps required to build the WRF and

WPS codes (though the instructions are specifically given for tcsh and GNU compilers).

http://www2.mmm.ucar.edu/wrf/OnLineTutorial/compilation_tutorial.php

• Get the WRF zipped tar file for WRFV3 from

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

o Always get the latest version if you are not trying to continue a long

project, or duplicate previous work

• 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

SOFTWARE INSTALLATION

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

a domain to follow a vortex (typhoon tracking)

o A typical option that may be included on the ./configure command is

the flag “-d” (for debug). This option removes optimization, which is

useful when running a debugger (such as gdb or dbx)

o For bounds checking and some additional exception handling, the

debugging flag “-D” may be selected. Only PGI, Intel, and gfortran have

been set up to use this option.

• ./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

The WRF code supports a parallel build option, an option that compiles separate source

code files in the WRF directories at the same time on separate processors (though those

processors need to share memory) via a parallel make. The purpose of the parallel build

option is to be able to speed-up the time required to construct executables. In practice,

users typically see approximately a 2x speed-up, a limit imposed by the various

dependencies in the code due to modules and USE association. To enable the parallel

build option, the user sets an environment variable, J. In csh, to utilize two processors,

before the ./compile command, issue the following:

setenv J “-j 2”

Users may wish to only use a single processor for the build. In which case:

setenv J “-j 1”

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.

Building the WPS Code

Building WPS requires that WRFV3 be already built.

If you plan to use Grib2 data, additional libraries for zlib, png, and jasper are

required. Please see details in Chapter 3.

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

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

• Also download the geographical datasets from the same page. There are new data

sets for land cover for North America (NLCD), and high-resolution urban data

sets for select North American cities.

• Unzip and untar the source code file

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

SOFTWARE INSTALLATION

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

• cd WPS

• ./configure

o Choose one of the options

o Usually, serial builds are 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). Add the paths to these libraries and include files

using variables COMPRESSION_LIBS and COMPRESSION_INC in

configure.wps. Also inside the configure.wps file is the

location of the built WRFV3 directory, which needs to be modified. This

is how the WPS picks up all of the required IO pieces to build the

geogrid.exe and metgrid.exe files.

• ./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, the path to the

built WRFV3 directory structure is probably incorrect (found inside the

configure.wps file)

• If the ungrib.exe is missing, the Grib2 libraries are probably not linked or

built correctly

• If the plotfmt.exe or the plotgrids.exe programs is missing, the NCAR

Graphics path is probably set incorrectly

Building the WRFDA Code (for 3DVAR)

WRFDA uses the same build mechanism as WRF; thus, this mechanism must be

instructed to configure and build the code for WRFDA rather than WRF. Additionally,

the paths to libraries needed by WRFDA code must be set, as described in the steps

below.

剩余442页未读，继续阅读

Syamuel

粉丝: 0
资源: 1

WRF-ARW用户指南：从安装到预处理系统详解

ARWUsersGuideV3

netty-3.9.9.Final-API文档-中文版.zip

ehcache-3.9.9-API文档-中英对照版.zip

YeeCOM DTU连接阿里云物联网套件MQTT说明3.9.pdf

WeChatApi、wechat_api、微信3.9.11、微信3.9.10、微信HOOK、微信机器_WeChatApi.zip

poi-jar包：poi-3.8.jar、poi-3.9.jar、poi-3.16.jar、poi-ooxml-3.9.jar、poi-ooxml-3.16.j

Cracklock.3.9.44.rar

python3.9.10和python3.9.11的区别

最新资源