Model Evaluation Tools (MET) | Download

Other Releases

Accordion section

Version Download Date
9.0.3 met-9.0.3.tar.gz METplus-3.0.3 METviewer 3.0 MET User's Guide 9.0.3 Existing Builds and Docker Online Tutorial (v8.0) Release Notes
9.0.2 met-9.0.2.tar.gz METplus-3.0.2 METviewer 3.0 MET User's Guide 9.0.2 Existing Builds and Docker Online Tutorial (v8.0) Release Notes
9.0.1 met-9.0.1.tar.gz METplus-3.0 METviewer 3.0 MET User's Guide 9.0.1 Existing Builds Online Tutorial (v8.0) Release Notes
9.0 met-9.0.tar.gz METplus-3.0 METviewer 3.0 MET User's Guide 9.0 Existing Builds Online Tutorial (v8.0) Release Notes
8.1.2 met-8.1.2.tar.gz METplus-2.1.1 METviewer 2.10 MET User's Guide 8.1.2 Existing Builds Online Tutorial Release Notes
8.1.1 met-8.1.1.tar.gz METplus-2.1.1 METviewer 2.10 MET User's Guide 8.1.1 Existing Builds Online Tutorial Release Notes
8.1 met-8.1.tar.gz METplus-2.1 METviewer 2.10 MET User's Guide 8.1 Docker Container Existing Builds Online Tutorial Release Notes
8.0 met-8.0.tar.gz met-8.0_bugfix.tar.gz METplus-2.0.4 MET User's Guide 8.0 Docker Container Existing Builds Online Tutorial Release Notes | Known Issues
7.0 met-7.0.tar.gz met-7.0_bugfix.tar.gz MET User's Guide 7.0 Docker Container Existing Builds Online Tutorial Release Notes | Known Issues
6.1 met-6.1.tar.gz met-6.1_bugfix.tar.gz MET User's Guide 6.1 Docker Container Existing Builds Online Tutorial Release Notes | Known Issues
6.0 met-6.0.tar.gz met-6.0_bugfix.tar.gz MET User's Guide 6.0 Docker Container Existing Builds Online Tutorial Release Notes | Known Issues
5.2 met-5.2.tar.gz met-5.2_bugfix.tar.gz MET User's Guide 5.2 Existing Builds Online Tutorial Release Notes | Known Issues
5.1 met-5.1.tar.gz met-5.1_bugfix.tar.gz MET User's Guide 5.1 Release Notes | Known Issues
5.0 met-5.0.tar.gz MET User’s Guide 5.0 Online Tutorial Release Notes | Known Issues
4.1 METv4.1.tar.gz MET User’s Guide 4.1 Online Tutorial Release Notes | Known Issues
4.0 METv4.0.tar.gz MET User’s Guide 4.0 Online Tutorial Release Notes | Known Issues
3.1 METv3.1.tar.gz MET User’s Guide 3.1 Online Tutorial Release Notes | Known Issues
3.0.1 METv3.0.1.tar.gz MET User’s Guide 3.0.1 Online Tutorial Release Notes | Known Issues
3.0 METv3.0.tar.gz MET User’s Guide 3.0 Online Tutorial Release Notes | Known Issues
2.0 METv2.0.tar.gz MET User’s Guide 2.0 Online Tutorial Release Notes | Known Issues
1.1 METv1.1.tar.gz MET User’s Guide 1.1 Online Tutorial Release Notes | Known Issues

MET Software

Refer to the MET Existing Builds page (includes NCAR RAL machines and NCAR machine cheyenne, and NOAA machines theia, jet, and WCOSS). Alternatively, skip installing and building and access MET that is up and running in a Docker container.

If compiling from scratch, please see the compile scripts below.

Sample Script for Compiling External Libraries and MET

  • compile_MET_all.sh.tgz
  • tar_files.tgz contains the necessary tar files (excluding the MET code) for building MET's dependent and optional libraries. Please get the tarball for MET and put in in the tar_files directory.

Download compile_MET_all.sh.tgz and tar_files.tgz and place them in the same directory, the directory where you would like to install MET (see TEST_BASE below).  Unpack compile_MET_all.sh.tgz by running tar -zxf compile_MET_all.sh.tgz.  Unpack tar_files.tgz by running tar -zxf tar_files.tgz. Change directories to enter the tar_files directory that was just created.  Download the latest MET release (e.g. met-9.0.2.20200522.tar.gz) from the Download page into the tar_files directory.  The script expects some environment variables to be set before running it.  An easy way to set these necessary environment variables is to set them in a file (for example, install_met_env.<machine_name>), put that file in the same directory as compile_MET_all.sh and tar_files, and pass that file as an argument to compile_MET_all.sh (e.g. ./compile_all_MET.sh install_met_env.kiowa).  You can find this script and environment config files for various machines in the MET GitHub repository in the scripts/installation directory.

A description of the variables used on a machine that does not use modulefiles is shown below (see install_met_env.kiowa for the values of these variables)

  • TEST_BASE - Installation Directory (e.g. /d1/met/9.0.2)

  • COMPILER - format is compiler_version (e.g. gnu_6.3.0) (For the GNU family of compilers, use “gnu”; For the Intel family of compilers, use “intel”, “ics”, “ips” or other depending on your system; For the PGI family of compilers, use “pgi”)

  • PYTHON_MODULE - format is the name of the Python module to load followed by an underscore and then the version number (e.g. python_3.6.3, The script will then run "module load python/3.6.3")

  • MET_SUBDIR - location where top level MET subdir (met-9.0.2) will be (e.g. ${TEST_BASE}/)

  • MET_TARBALL - name of MET tarball (e.g. met-9.0.2.2020522.tar.gz)

  • USE_MODULES - set to FALSE if you’re on a machine that does not use modulefiles; set to TRUE if you’re on a machine that does use modulefiles

  • MET_PYTHON - location containing the bin, include, lib and share directory for Python (e.g. /usr/local/python3)

  • MET_PYTHON_CC - -I followed by the directory containing Python includes (e.g. -I/usr/local/python3/include/python3.6m) (You may be able to get this information by running python3-config --cflags)

  • MET_PYTHON_LD - -L followed by the directory containing Python library file, then a space and -l followed by the necessary Python libraries to link to (e.g. -L/usr/local/python3/lib/\ -lpython3.6m\ -lpthread\ -ldl\ -lutil\ -lm). The backslashes are necessary in the example shown. (You may be able to get this information by running python3-config --ldflags)

  • SET_D64BIT - set to FALSE if your version of the GRIB2C library was not compiled with the -D__64BIT__ option; set to TRUE if your version of the GRIB2C library was compiled with the -D__64BIT__ option; The __64BIT__ option should either be used for both or neither.  By default, compile_MET_all.sh will install the GRIB2C library without the -D__64BIT__ option.

If you are compiling on a machine that does use modulefiles and you’d like to make use of the existing dependent libraries on your machine, there are more environment variables that you will need to set to let MET know where the library and header files are.  Take a look at the file install_met_env.venus file, which shows an example using modulefiles that were loaded for Python, NetCDF, HDF5, GRIB2 C-Library, BUFR, jasper, libpng, and zlib.

External Libraries Needed To Build MET

  • BUFRLIB for reading PrepBufr Observation files
  • NetCDF4 for intermediate and output file formats
  • HDF5 is required to support NetCDF 4. HDF5 should be built with zlib.
  • GSL GNU Scientific Library Developer's Version for computing confidence intervals (use GSL-1.11 for PGI compilers)
  • GRIB2C Library, if compiling GRIB2 support.
  • HDF4 Library, if compiling the MODIS-Regrid tool.
  • HDF-EOS2 Library, if compiling the MODIS-Regrid tool.
  • Cairo Library, if compiling the MODE-Graphics tool.
  • FreeType Library, if compiling the MODE-Graphics tool.
  • f2c Library for interfacing between Fortran and C (Not required for most compilers)

Compiling GRIB2C with the -D__64BIT__ option requires that MET also be configured with CFLAGS="-D__64BIT__".

External Utilities Suggested For Use With MET

Additional Data That May Be Of Use

Prior to running Plot-MODE-Field, users must first download Ghostscript font data and set the MET_FONT_DIR environment variable to point to the directory containing those fonts.

Please direct comments and questions regarding MET to met_help@ucar.edu.