MET Version 8.1.1

Release Date:

The MET Version 8.1.1 was released on July 8, 2019.

Release Notes

Release notes are followed by the GitHub issue number which describes the bugfix:

https://github.com/NCAR/MET/milestone/60?closed=1

Bugfixes Included:

  • Fix MET to correctly handle the updated "V8.1.1" version number (#1153).
  • Interpret the NetCDF COARDS convention as being CF-compliant (#1155).
  • Update list of GRIB2 vertical level types (#1159).
  • Fix to handle GRIB2 PDS Template number 46 (#1160).
  • Bugfix for memory leak in vx_data2d_grib2 library (#1157).
  • Bugfix for uninitialized variables in pb2nc and regrid_data_plane (#1156).
  • Bugfix for swapped lat/lon dimensions in regrid_data_plane GOES-16 output (#1152).
  • Bugfix for time slicing of NetCDF files (#1147).
  • Bugfix for segfault in Grid-Stat when reading climo_mean data (#1146).
  • Bugfix for header array index when computing time summaries in PB2NC (#1137).
  • Bugfix for ALPHA=NA in the GRAD output line type from Grid-Stat (#1131).
  • Bugfix for the OBJECT_ID column in the 2D ASCII output files from MTD (#1128).
  • Fix compilation problems for GNU 6.3.0 and later versions (#1139).
  • Minor corrections to the user's guide (#1150).


Known Issues and Fixes

MET can read gridded data in GRIB1, GRIB2, or 3 different flavors of NetCDF: 

  • The "internal" NetCDF format that looks like the output of the pcp_combine tool. 
  • CF-compliant NetCDF3 files. 
  • The output of the wrf_interp utility.

If there are the NetCDF output from WRF, use UPP to post-process it. It does not need to be "lat-lon"... it can be post-processed to whatever projection is needed..

There is in general no easy way to convert NetCDF to GRIB. If the NetCDF data is self generated, make it look like the NetCDF output from pcp_combine, or preferably, make it CF-compliant.

Looking at the accumulation interval of the precipitation data in the WRF output files from UPP, use the "wgrib" utility to dump out that sort of information:

wgrib wrfprs_d01.02 

wgrib wrfprs_d01.03 

... and so on

The question is whether the output actually contains 1-hourly accumulated precip, or does it contain runtime accumulation. Runtime accumulation means that the 6-hour wrf file contains 0 to 6 hours of precip; the 7- hour file contains 0 to 7 hours of precip; and so on. The precip values just accumulate over the course of the entire model integration.

The default for WRF-ARW is runtime accumulation. So if WRF-ARW is running and the output bucket interval wasn’t specifically changed, then that's very likely.

If that is the case, you can change these values to interval accumulations. Use the pcp_combine "-subtract" option instead of "-sum". Suppose the 6 hours of precip between the 6hr and 12hr forecasts is wanted. Run the following:

pcp_combine -subtract wrfprs_d01.12 12 \

wrfprs_d01.06 06 apcp_06_to_12.nc

That says... get 12 hours of precip from the first file and 6 hours from the second file and subtract them.