Retrieve all of the recommended updates for METv5.0 in a tarfile:
Problem: Ensemble-Stat errors out when writing the output NetCDF ensemble summary file for GRIB2 probability fields. The segmentation fault happens when trying to write the "units" NetCDF variable attribute which is empty.
Solution: The fix is to use the probability units for the NetCDF variable attribute.
Problem: MET errors out when reading longitude values from gridded CF-compliant NetCDF files that cross the international date line:
ERROR: NcCfFile::get_grid_from_dimensions() -> MET can only process Latitude/Longitude files where the lon delta is constant
Solution: Update the logic when checking for equally spaced longitude values to handle the international date line.
Problem: Maximum Updraft Helicity (MXUPHL) is stored as an accumulation between 2000 and 5000 meters in GRIB2 files. However, MET can only handle accumulation intervals stored as time strings in HHMMSS format. MET is unable to extract that field from GRIB2 files.
Solution: The work-around is to specify MXUPHL using a generic level type, such as "L5000-2000". Update the GRIB2 filtering logic to explicitly check for generic level type matching prior to matching accumulation intervals.
Problem: Earlier versions of MET were checking that the GRIB record parameter table version number matched the one requested in the configuration file. Prior to METv3.1, that check was commented out. All GRIB records matching the requested GRIB code were selected regardless of their parameter table version number.
Solution: The fix is to uncomment that check.
Problem: A MET user reported compilation problems on Mac using Intel version 14 compilers due to name conflicts for the functions named "rank".
Solution: The fix is to rename two functions in the MET libraries named "rank".
Problem: A user reported problems with MET when checking for the equality of two numbers on their system. This revealed incorrect calls to the "abs" function rather than "fabs" when computing the absolute value of floating point numbers.
Solution: Simplify the logic of the library routine that checks for the numeric equality and switch "abs" to "fabs" in a handful of places in the MET code tree.
Problem: Using the -init_str option in the TC-Stat tool on track data containing no 0-hour forecast track point results in a segmentation fault.
Solution: Fix the logic to check for a bad initial track point before applying the initialization string filtering criteria.
Problem: The TC-Pairs tool was computing the track consensus location as a simple arithmetic mean of the latitude and longitudes of the members. When the longitudes of the members straddle the international date line, this method produces incorrect results.
Solution: Check the range of the member longitudes. If the range exceeds 180 degress assume that the international date line is being crossed. Add 360 to any longitude values less than 0 before computing the arithmetic mean. Rescale the average longitude back to the range of -180 to 180.
Problem: Attempting to write very large values of unixtime (+/- 2147483647) as NetCDF variable attributes results in integer overflow and a runtime error:
NetCDF: Numeric conversion not representable
Solution: Check for integer overflow prior to writing unixtime to NetCDF files and print a warning message.
This fix was updated on 10/15/2014 to remove references to NC_MAX_INT which is defined in NetCDF4 but not in NetCDF3.
Problem: Setting the latlon, raw, and diff options in the nc_pairs_flag section of the Grid-Stat configuration file to different values causes a segmetation fault due to memory not being properly allocated.
Solution: The fix is to properly allocate memory prior to accessing the array elements.
Problem: Executing "make clean" removes the file color_scanner.cc from the vx_color library. Subsequent calls to "make" result in calling flex to regenerate this file. The distributed code should cause no calls to flex.
Solution: The fix is to update the Makefiles for the vx_config and vx_color libraries and only remove the output of flex when in development mode.
Problem: When inferring the lat/lon grid definition from CF-compliant NetCDF files, MET quietly used the last lat/lon coordinate variable. Also, MET was assuming a single valid time for each file rather than determing the valid time for each field read.
Solution: Print a warning message when multiple lat/lon coordinate variables are found and use the first one. Rather than assuming a single valid time for each file, determine the valid time for each field read.
Problem: The MET library code was failing to parse timing information from GRIB2 table 4.48.
Solution: Update the logic to correctly parse the timing information.
Problem: The default configuration file for the Plot-MODE-Field was inadvertenetly omitted from the release.
Solution: Add the default configuration file for the Plot-MODE-Field tool.
Problem: The configuration example in the top-level README file was missing the --enable-modis option.
Solution: Update the configuration example in README.
Copyright © 2021. All rights reserved.