Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Updated to say NETCDF4_PATH instead of NETCDF_PATH

...

To produce plots, Magics must be installed:

  • Magics++ (2.22 24.0 or higher is required)

    • should be configured with the -DENABLE_METVIEW=ON option

    • for a 'pure batch' installation of Metview with no user interface, it is possible to supply Magics with the option -DENABLE_METVIEW_NO_QT=ON

The following two libraries need to be installed (both are required, even if you will not handle GRIB or BUFR data):

  • GRIB_API (1.9.9 or higher is required)

    • see the Installation FAQ for details of building GRIB_API for Metview, as this contains some important information

  • Emoslib

    • version 392:

      • compiled with double floating point precision (answer “y” to “Do you want 64-bit reals? [y,n]”)

      • must be built with GRIB_API support

      • 64-bit versions should be built with -fPIC compilation flag

      • Remember to set the ARCH environment variable before building Emoslib, e.g. export ARCH=linux.
    • OR
    • version 400 or above:
      • compiled with double floating point precision (this is the default)

...

  • Qt (4.6.2 or later) if building the user interface (default=yes)
    note that on some systems it is also necessary to install the libQtWebKit-devel development package (it may have different names on different systems)

  • NetCDF library with C++ interface
    (http://www.unidata.ucar.edu/software/netcdf/)

  • OpenMotif (if  if enabling the old user interface with -DENABLE_MOTIF=ON, but OFF is the default)

  • gdbm

  • ImageMagick (Metview uses the convert command during the build process)
  • ksh - the Korn Shell is used by Metview's startup script and some other internal scripts

...

CMake option
Description
Default
CMAKE_INSTALL_PREFIXwhere you want to install Metview /usr/local
CMAKE_BUILD_TYPE

to select the type of compilation:

  • Debug
  • RelWithDebInfo
  • Release
  • Production

In most cases Release is preferable for an optimised version with no debug information

RelWithDebInfo
CMAKE_CXX_FLAGSadditional flags  for the C++ compiler, e.g. -DCMAKE_CXX_FLAGS="-O2 -march=native" 
CMAKE_C_FLAGSadditional flags  for the C compiler 
CMAKE_Fortran_FLAGSadditional flags  for the Fortran compiler 
ENABLE_UIenables the Qt-based user interfaceON
ENABLE_MOTIF

enables the deprecated Motif-based user interface

  • Metview can be started with option -old-ui
OFF
ENABLE_PLOTTINGenables plotting capabilities using MagicsON
ENABLE_OPERA_RADARenables the Opera Radar Filter module (requires the proj4 library and headers)OFF
ENABLE_MARSenables MARS access (not required if using through the Web API)OFF
MARS_LOCAL_HOMEsets the path to where local MARS is installed 
ENABLE_ODBenables processing and plotting of ODB dataOFF
ENABLE_MARS_ODBenables ODB capabilities in MARS clientOFF
ENABLE_USAGE_LOGenables logging of Metview startup callsOFF
LOG_DIRpath to where to log the Metview startup calls 
METVIEW_SCRIPTname of the generated Metview startup scriptmetview
EXTRA_CONFIG_PATHpath to optional directory containing metview_local* script files 
ENABLE_QT_DEBUGoutputs additional log messages from Qt-based modulesOFF
EXTRA_TITLEbuild-specific title to add to the log entries 
ENABLE_INPEenables INPE modulesON
Path options - only required when support libraries are not installed in default locations
CMake OptionDescriptionNotes
GRIB_API_PATHpath to where GRIB_API has been installed 
MAGICS_PATHpath to where Magics has been installedOnly required if plotting is enabled
NETCDFNETCDF4_PATHpath to where netCDF has been installed 
ODB_API_PATHpath to where ODB_API has been installedOnly required if ODB is enabled
ODB_PATHpath to where the original ODB has been installedOptional if ODB is enabled
EMOS_PATHpath to where Emoslib has been installedAlso set EMOS_LIB_NAME
FDB_PATHpath to where fdb has been installedOnly required if MARS is enabled
PROJ4_PATHpath to where proj4 has been installedOnly required if OPERA Radar is enabled
FLEXTRA_PATHpath to where the FLEXTRA executable has been installedSee Tutorials for more on FLEXTRA

...