Frequently Asked Questions

Q: Why was the MET written largely in C++ instead of FORTRAN?
A: MET relies upon the object-oriented aspects of C++, particularly in using the MODE tool. Due to time and budget constraints, it also makes use of a pre-existing forecast verification library that was developed at NCAR.

Q: Why are VSDB and PREPBUFR used?
A: Mainly because the first goal was to initially replicate the capabilities of other existing verification packages and make these capabilities available to both the DTC and the public. VSDB was selected as one of the output types supported.

Q: Why is GRIB used?
A: Forecast data from both WRF cores can be processed into GRIB format, and it is a commonly accepted output format for many NWP models.

Q: Is GRIB2 supported?
A: Not as of version 1.0. We plan to add support for forecast output in GRIB2 format in the next version release.

Q: How does MET differ from the previously mentioned existing verification packages?
A: MET is an actively maintained, evolving software package that is being made freely available to the public through controlled version releases.

Q: How does the MODE tool differ from the Grid-Stat tool?
A: They offer different ways of viewing verification. The Grid-Stat tool provides traditional verification statistics, while MODE provides specialized spatial statistics.

Q: Will the MET work on data in native model coordinates?
A: No - it will not. In the future, we may add options to allow additional model grid coordinate systems.

Q: How do I get help if my questions are not answered in the User's Guide?
A: First, refer to the documentation on this website. If that doesn't answer your question, then email: met_help@ucar.edu.

Q: Where are the graphics?
A: Currently, very few graphics are included. Further graphics support will be made available in the future on the MET website.