Developer-Related Known Issues And Fixes
FOR A FULL LIST OF KNOWN ISSUES VISIT THE DOWNLOADS WEBSITE, HERE
NETCDF4 does not work on Jet
Problem: When loading the netcdf4 module on Jet it puts the path into the env var NETCDF4, however the WRF configure script is expecting the path to be in the var NETCDF and for NETCDF4 = 1.
Solution: Load the netcdf4 module and then manually set environment variable NETCDF=$NETCDF4.
GSI=YES and RELOCATE=NO does not work
Problem: Configuration not supported.
Solution: You may turn off the initialization procedure in the vortex initialization by using launcher configuration option relocate.initopt=1, however the relocation portion must be run (config.run_relocation=yes) in order to run GSI.
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. Thi s issue is currently under review. No work around exists.
Compiling HWRF on NCAR's Cheyenne with Grib2 Support
Problem : Runtime failure linking to the appropriate libraries.
Solution: Set the location of all three grib2 support libraries (these must be in the same location) and LD_LIBRARY_PATH. This is one option:
LIB_PNG_PATH=/glade/u/home/wrfhelp/UNGRIB_LIBRARIES/lib
LIB_Z_PATH=/glade/u/home/wrfhelp/UNGRIB_LIBRARIES/lib
LIB_JASPER_PATH=/glade/u/home/wrfhelp/UNGRIB_LIBRARIES/lib
LD_LIBRARY_PATH=/glade/u/home/wrfhelp/UNGRIB_LIBRARIES/lib
Problem accessing all input data on HPSS
Problem : Input task crashes due to missing/inaccessible files. Users that are not members of the rstprod linux group will be unable to retrieve all necessary files to initialize HWRF from the HPSS. Runs will only be possible if input data is pre-staged on disk.
Solution: Data should be stored on disk for desired runs. Real-time data is available on disk for the recent past, therefore rstprod issues should not cause problems for real-time applications.
