Download, Configure & Compile, of the HWRF Components

2/25/10
Download,
Configure
&
Compile,
of
the
HWRF
Components
Donald
Stark
Na?onal
Center
for
Atmospheric
Research
(NCAR)
The
Developmental
Testbed
Center
(DTC)
24
February,
2010
1

Outline
• HWRF
system
components
• Where
to
get
the
codes
• User
directory
structure
• Component
directory
structure
• Unpacking,
setup,
&
build
2/25/10
2

GFS
forecast
NHC storm
message
Configure domain
HWRF
System
Components
WRF
Preprocessor
Ini6al
Vortex
Improvement
Previous
6
hr
forecast
(if
available)
Ocean
Ini6aliza6on
Ini6alize
Gulf
Stream,
wake,
loop
currents
and
eddies
Wind
stress
Heat
fluxes
Geo-static data
HWRF
ATMOSPHERE
HWRF
COUPLER
POM
OCEAN
SST
Post
Processing
Vortex
Tracker

HWRF
System
Components
• WRF:
Weather
Research
&
Forecast
Model
• WPS:
WRF
Preprocessor
• WPP:
WRF
Postprocessor
• HWRF
U?li?es:
HWRF
u?li?es
&
Vortex
Init
• POMTC:
Tropical
Cyclone
version
of
the
Princeton
Ocean
Model.
• NCEP
Coupler:
Couples
WRF
&
POMTC
• GFDL
Vortex
Tracker:
Storm
tracker
for
post
processing
2/25/10
4

Downloading
the
Source
Code
• WRF,
WPS,
&
WPP
source
code:
– hZp://www.dtcenter.org/wrf‐nmm/users/downloads/index.php
• Addi?onal
HWRF
source
code
obtained
from:
2/25/10
– hZp://www.dtcenter.org/HurrWRF/users/downloads/index.php
5

Unpacking
WRF
&
WRF
Tools
• Create
a
working
directory,
&
unpack
the
tarballs:
– mkdir


$(HOME)/HWRF/src/
– cd


$(HOME)/HWRF/src/
• The
WRF
source
code
consists
of
3
tar
files:
– WRFV3.tar.gz
– WPSV3.tar.gz
– WPPV3.tar.gz
• Unpack
the
source
inside
the
working
directory
– Unzip
the
files:
gunzip
*.tar.gz
– Untar
the
files
individually:
tar
–zxvf
file.tar
2/25/10
6

Unpacking
the
Addi?onal
Components
• Create
a
working
directory,
&
unpack
all
the
tarballs:
– mkdir


$(HOME)/HWRF/src/
– cd


$(HOME)/HWRF/src/
• The
HWRF
source
code
consists
of
4
tar
files:
– HWRF‐UTILITIES.tar.gz
– POMTC.tar.gz
– NCEP‐COUPLER.tar.gz
– GFDL‐VORTEXTRACKER.tar.gz
• Unpack
the
source
inside
the
working
directory
– Unzip
the
files:
gunzip
*.tar.gz
– Untar
the
files
individually:
tar
–xvf
file.tar
2/25/10
7

HWRF
Directory
Structure
• Seven
directories
(3
from
WRF,
4
from
HWRF)
2/25/10
– $(HOME)/HWRF/src/WRFV3
– $(HOME)/HWRF/src/WPS
– $(HOME)/HWRF/src/WPPV3
– $(HOME)/HWRF/src/hwrf‐u?li?es
– $(HOME)/HWRF/src/pomtc
– $(HOME)/HWRF/src/ncep‐coupler
– $(HOME)/HWRF/src/gfdl‐vortextracker
8

System
Requirements
• C
compiler
• Perl
• netCDF
V3
(for
WRF,
WPS,
WPP
&
hwrf‐u?li?es)
• MPI
V1+
• FORTRAN
90/95
compiler
• GrADS
(visualiza?on)
• wgrib
(decode
grib
files)
2/25/10
9

2/25/10
• IBM
AIX
xlf
Supported
Plagorms
• Linux
PGI
pgf90
V8
or
V9
• Linux
Intel
ifort
V9,
V10,
or
V11
10

Build
Infrastructure
• /arch
directory
containing
the
compile
rules.
– /arch/configure.defaults
default
plagorm
seings
• ./clean
script
to
clean
build.
• ./configure
script
to
create
configura?on
file
configure.xxx;
contains
info
on
compiler,
MPI,
&
paths.
• ./compile
script
to
compile
executable(s).
• See
WRF
or
HWRF
Users’
Guide
for
addi?onal
details.
2/25/10
11

HWRF
U?li?es
Directory
Structure
• /exec
–
hwrf‐u?li?es
executables
• /libs
–
support
libraries
• /parm
–
namelists
and
parameter
files
• /post
–
postprocessing
source
code
• /scripts
–
run
scripts
• /vortex_init
–
vortex
ini?aliza?on
source
code
• /tools
–
grbindex
source
2/25/10
12

POM‐TC
Directory
Structure
• /ocean_exec
–
POMTC
executables
• /ocean_init
–
ocean
hurricane
init
rou?nes
• /ocean_main
–
POMTC
ocean
model
source
• /ocean_parm
–
namelists
and
parameter
files
• /ocean_plot
–
ocean
ploing
scripts
• /ocean_scripts
–
run
scripts
for
POMTC
2/25/10
13

NCEP
Coupler
Directory
Structure
• /cpl_exec
–
coupler
executable
• /hwrf_pwmc
–
coupler
source
code
2/25/10
14

Vortex
Tracker
Directory
Structure
• /trk_exec
–
vortex
tracker
executables
• /trk_plot
–
ATCF
Plot,
tracker
ploing
• /trk_src
–
vortex
tracker
source
code
2/25/10
– /hwrf_geZrk
–
source
code
15

Build
Process
• Based
on
the
WRF
build
system.
See
the
HWRF
Users’
Guide
for
full
details.
• Clean
the
component
directory
./clean
–a.
• Set
necessary
library
paths,
if
needed.
• Run
the
configure
script
./configure
&
select
any
plagorm
specific
op?ons.
Creates
a
component
specific
configura?on
file
configure.componentname.
• Run
the
compile
script
./compile.
2/25/10
16

Configura?on
File
• The
configura?on
file
configure.component
is
built
from
3
pieces
within
the
arch
directory.
2/25/10
1. preamble:
uniform
requirements
for
the
code,
such
as
word
size,
etc.
2. configure.defaults:
selec?on
of
compiler,
parallel,
communica?on
layer
3. postamble:
standard
make
rules
&
dependencies
17

Clean
Compila?on
• To
remove
all
object
files
and
executables,
type: 
clean
• To
remove
all
built
files,
including
the
configure
file,
type:
clean
–a
2/25/10
– strongly
suggested
if
• Compila?on
failed
• Want
to
change
configura?on
file
18

Building
WRF
Components
for
HWRF
• WRF
components
consist
of:
– WRF
– WPS
(WRF
preprocessor)
– WPP
(WRF
post
processor)
• WPS,
WPP,
&
HWRF
u?li?es
requires
WRF
I/O
object
files.
– For
WPS,
the
build
searches
the
directory
containing
the
WPS
directory
for
the
WRF
directory.
Therefore
the
WRF
&
WPS
directories
must
must
be
at
the
same
directory
level,
with
names
unchanged.
– WPP
&
HWRF
u?li?es
finds
the
object
files
by
looking
at
the
loca?on
defined
by
the
path
variable
WRF_DIR.
In
csh/
tcsh
type:
setenv
WRF_DIR
$(HOME)/HWRF/src/WRFV3
2/25/10
19

• WRF
– WPS
– WPP
HWRF
dependencies
– HWRF
U?li?es
• POM‐TC
• GFDL‐Tracker
• NCEP‐Coupler
2/25/10
20

Building
WRF
NMM
• Type
cd
./WRFV3
• Type
./clean
–a
• Set
library
paths
and
system
variables,
for
csh
– setenv
HWRF
1
– setenv
NETCDF
/path_to_netcdf_lib/
– setenv
WRF_NMM_CORE
1
– setenv
WRF_NMM_NEST
1
• For
full
details,
see
the
WRF‐NMM
Users’
Guide
– hZp://www.dtcenter.org/wrf‐nmm/users/downloads/
index.php
2/25/10
21

Building
WRF
NMM
(con?nued)
• Type
./configure
– 12
compiler
op?ons
for
Linux;
select
either
PGI
or
Intel
dmpar
op?on
– 4
for
IBM;
select
the
xlf
dmpar
op?on
– Select
op?on
(2)
preset
moves
for
nes?ng
– Creates
configura?on
file
configure.wrf
• For
csh
type
– ./compile
nmm_real
|&
tee
wrf.log
• Successful
compila?on
will
produce:
– Two
executables,
real_nmm.exe
&
wrf.exe,
in
/main
2/25/10
22

Building
the
remaining
Components
• HWRF
consists
of
WRF
components
&
the
remaining
HWRF
components:
– HWRF
U?li?es
– POMTC
– NCEP
Coupler
– GFDL
Vortex
Tracker
• HWRF‐U?li?es
requires
WRF‐NMM
to
build,
&
includes
the
support
libs
needed
by
the
other
3
components.
It
must
be
built
first.
• Remaining
components
can
be
built
in
any
order.
2/25/10
23

Building
HWRF
u?li?es
• Type
cd
./hwrf‐uVliVes
• Type
./clean
–a
• Set
path
to
WRF
(WRF_DIR)
&
check
that
netCDF
library
path
NETCDF
is
set.
• Type
./configure
– Two
compiler
op?ons
for
Linux,
one
for
IBM
– Creates
file
configure.hwrf
• For
csh
type
./compile
|&
tee
hwrf‐uVl.log
• Successful
compila?on
will
produce:
– 8
libraries;
ls
–l
hwrf‐uVliVes/libs/*.a
|
wc
– 22
executables;
ls
–l
hwrf‐uVliVes/exec/*.exe
|
wc
2/25/10
24

Building
the
remaining
Components
The
remaining
components
need
the
following
external
libraries
to
build:
• POMTC:
W3,
SP,
SFCIO,
&
BLAS
on
non‐IBM
plagorms.
• Coupler:
none
• Vortex
Tracker:
W3,
BACIO
These
five
libraries
are
provided
in
the
$(HOME)/HWRF/src/hwrf‐uVliVes/libs
directory.
2/25/10
25

Building
the
remaining
Components
• Set
the
following
library
path
variables
to
the
absolute
path
of
the
hwrf‐uVliVes/libs
directory.
2/25/10
– LIB_W3_PATH
– LIB_SP_PATH
– LIB_SFCIO_PATH
– LIB_BACIO_PATH
– LIB_BLAS_PATH
for
non‐IBM
AIX
plagorms.
In
csh,
the
syntax
to
set
a
path
is:
setenv
LIB_W3_PATH
$(HOME)/HWRF/src/hwrf‐uVliVes/libs/
26

Building
the
POM‐TC
Component
• Type
cd
./pomtc
• Type
./clean
–a
• Set
library
paths
for
W3,
SP,
SFCIO,
&
BLAS
for
Linux
• Type
./configure
– Three
op?ons
for
Linux,
one
for
IBM
– Creates
configure
file
configure.pom
• For
csh
type
./compile
|&
tee
pomtc.log
• Successful
compila?on
produces
6
executables:
– in
pomtc/ocean_exec.
2/25/10
27

Building
the
Coupler
Component
• Type
cd
./ncep‐coupler
• Type
./clean
–a
• Type
./configure
– Three
op?ons
for
Linux,
one
for
IBM
– Creates
configure
file
configure.cpl
• For
csh
type
./compile
|&
tee
cpl.log
• Successful
compila?on
produces:
2/25/10
– an
executable
hwrf_pwmc.exe
in
cpl_exec
28

Building
the
Tracker
Component
• Type
cd
./gfdl‐vortextracker
• Type
./clean
–a
• Set
library
paths
for
W3,
SP,
&
BACIO.
• Type
./configure
– Three
op?ons
for
Linux,
one
for
IBM
– Creates
configura?on
file
configure.trk
• Type
./compile
|&
tee
tracker.log
• Successful
compila?on
produces
one
executabe:
– hwrf_geZrk.exe
in
trk_exec.
2/25/10
29

Building
WPS
for
HWRF
• Requires
WRF‐NMM,
must
be
compiled
first.
• Type
cd
./WPSV3
• Type
./clean
–a
• Type
./configure
– 15
compiler
op?ons
for
Linux,
4
for
IBM
– Creates
configura?on
file
configure.wps
• For
csh
type
./compile
|&
tee
wps.log
• Successful
compila?on
produces
3
executables:
– In
WPS/
geogrid.exe,
ungrib.exe,
&
metgrid.exe
2/25/10
30

Building
WPP
for
HWRF
• Type
cd
./WPPV3
• Type
./clean
–a
• Set
library
paths
– setenv
WRF_DIR
/path_to_WRF_dir/
– setenv
HWRF
1
• Type
./configure
– 3
compile
op?ons
for
Linux,
1
for
IBM
– Creates
configura?on
file
configure.wpp
• For
csh
type
./compile
|&
tee
wpp.log
• Successful
compila?on
produces
3
executables:
– In
exec/
wrfpost.exe,
ndate.exe,
&
copygb.exe.
2/25/10
31

Support
• For
more
detailed
informa?on
on
installa?on,
please
see:
– NMM
Users’
Guide
– www.dtcenter.org/wrf‐nmm/users/downloads/
index.php
– HWRF
Users’
Guide
– www.dtcenter.org/HurrWRF/users
• For
further
assistance
contact:
– wroelp@ucar.edu
2/25/10
32

Summary
• Follow
the
steps
in
order.
• Download
the
latest
tarballs.
• Don’t
mix
and
match
components
from
different
releases.
• Build
components
in
proper
order
– i.e.
WRF
before
hwrf‐u?li?es.
– i.e.
hwrf‐u?li?es
before
pomtc,
coupler,
&
vortex
tracker.
– i.e.
WRF
before
WPS
&
WPP.
• Must
set
environment
paths
• When
all
else
fails,
read
the
Users’
Guide.
2/25/10
33