WRF4.0用户指南：高级研究WRF模型详解

需积分: 19 154 浏览量更新于2024-07-15 收藏 10.83MB PDF 举报

身份认证购VIP最低享 7 折!

领优惠券(最高得80元）

资源详情

资源推荐

SOFTWARE INSTALLATION

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

Vendor

Hardware

Compiler

Cray

XC30 Intel

Linux

Intel

Cray

XE AMD

Linux

Intel

IBM

Power Series

AIX

vendor

IBM

Intel

Linux

Intel / PGI / gfortran

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

gfortran / PGI / Intel

NEC

Linux

vendor

Fujitsu

FX10 Intel

Linux

vendor

* Commercial Off-The-Shelf systems

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

machine (that uses 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.

SOFTWARE INSTALLATION

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

Required/Optional Libraries to Download

The only library that is 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 are using the netCDF

libraries. One may also need to add ‘/path-to-netcdf/netcdf/bin’ to their path so that they

may execute netCDF utility commands, such as ncdump. Use a netCDF version that is

3.6.1 or later. To utilize the compression capabilities, use netCDF 4.0 or later. Note that

compression will require the use of HDF5.

Note 1: If one wants to compile WRF system components on a Linux or Darwin 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 parallel I/O

based on HDF5. The WRF modeling system is able to use either the classic data model

from netCDF-3 or the compression options 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 mpif90

which mpicc

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.

Note 3: The entire step-by-step recipe for building the WRF and WPS packages is

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

This page includes complete turn-key directions, from tests of your machines’s utilities

all the way up through where to download real-time data.

SOFTWARE INSTALLATION

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

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))

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 WRFV4 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 WRFV4.0.TAR.gz | tar -xf –

o Alternatively tar –xzf WRFV4.0.TAR.gz on some systems

• cd WRF

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

SOFTWARE INSTALLATION

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

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)

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

剩余455页未读，继续阅读

unclekui

粉丝: 1
资源: 4

WRF4.0用户指南：高级研究WRF模型详解

WRF4.0官方手册

WRF3.9教程

WRF-ARW教程

Avatar_Utils-1.0.6-py3-none-any.whl.zip

“人力资源+大数据+薪酬报告+涨薪调薪”

2024-2030全球及中国聚硅氮烷行业研究及十五五规划分析报告 Sample-yb.pdf

用于目标检测的一个GUI程序界面.zip

使用笔记本电脑上的无线网卡，生成wifi热点，让设备连接_ShareVirtualWiFi.zip

基于springboot的名城小区物业管理系统设计与实现.docx

基于springboot校园资产管理设计与实现.docx

基于SpringBoot的某银行OA系统

采用 Mask R-CNN 算法模型进行目标检测，使用 Deep SORT 目标跟踪算法运动轨迹。.zip

yolo做行人检测+deep-sort做匹配，端对端做多目标跟踪.zip

elasticsearch-8.15.0-windows-x86-64.zip

Avatar_Utils-1.6.7-py3-none-any.whl.zip

Axelrod-3.7.0-py2.py3-none-any.whl.zip

model-smoke.tar

Axelrod-2.4.0-py2.py3-none-any.whl.zip

AwesomeTkinter-2021.10.2-py3-none-any.whl.zip

数据库课程设计.zip

最新资源