HWRF System components - V3.8a

Release Date:

The HWRF System components - V3.8a was released on November 21, 2016.

Release Notes

Please note that only the source code provided from the above links will work with the HWRF system.

For information on setting up, building, and running the HWRF system, see the HWRF Users' Guide and tutorial slides in the Documentation section of this site.

Check the release notes and known issues file for the most current information on a particular release.

HWRF System Upgrades in v3.8a

  • Compatible with the 2016 operational HWRF.
  • WRF upgraded to v3.8, GSI to v3.5, and UPP to v3.1.
  • D02 and D03 domain size increased to 25x25 and 8.3x8.3 respectively.
  • Reduced time step from 38 4/7 s to 30 s.
  • Data Assimilation enabled by default for both Atlantic and Eastern North Pacific basins.
  • Initialization with RTOFS data in the Eastern North Pacific basin.
  • Atmosphere-ocean coupling enabled for all N. Hemispheric basins.
  • Miscellaneous upgrades and bug fixes in various physical parameterizations.
    • New Scale Aware Simplified Arakawa Shubert scheme for cumulus parameterization. Cumulus parameterization enabled by default for all 3 domains.
    • New GFS Hybrid-Eddy Diffusivity Mass Flux PBL scheme.
    • Updated momentum and enthalpy exchange coefficients (Cd/Ch).
    • Enhanced Idealized capability with landfall option (for GFDL slab scheme).
  • Enhanced products including simulated brightness temperatures for new satellite sensors in all basins


Known Issues and Fixes

GSI=YES and RELOCATE=NO does not work

Problem: Configuration not supported.
Solution: Use a different configuration, for example, employ both GSI and vortex relocation.

Restart function does not work for HWRF

Problem: HWRF cannot be restarted using the WRF restart feature.
Solution: Currently the WRF restart corrupts the model fields at the location of the nest boundaries. There is no impact with ordinary runs. This issue is currently under review. No work around exists.

Issue with NetCDF installation path: -lnetcdff lib missing

Problem: Error:
./WRFV3/external/io_netcdf/./wrf_io.f:1578: undefined reference to `nf_open_'
./WRFV3/external/io_netcdf/./wrf_io.f:1585: undefined reference to `nf_inq_varid_'
./WRFV3/external/io_netcdf/./wrf_io.f:1592: undefined reference to `nf_inq_var_'
The trailing "_" means it is looking for the Fortran versions of these and not finding them.
Solution: WRF has this code bit in it's "configure" script to handle this:
# for 3.6.2 and greater there might be a second library, libnetcdff.a . Check for this and use
# if available
if [ -f "$NETCDF/lib/libnetcdff.a" -o -f "$NETCDF/lib/libnetcdff.so" ] ; then
USENETCDFF="-lnetcdff"
fi
and then - USENETCDFF is used later to define the libs to include.

For using NetCDF v4 on jet, set environment variable NETCDF4=1 and environment variable NETCDF to the path of the NetCDF v4 library (for example, /apps/netcdf/4.2.1.1-intel)

In this example the dimension of the grid is 37x37. Thus, up to 1369 matched pairs are possible. However, if the forecast or observation contains bad data at a point, that matched pair is not included in the calculations. Use the ncview tool to look at an example netCDF file. If the forecast field contains missing data around the edge of the domain, then that is a reason there may be 992 matched pairs instead of 1369.