...
Prerequisites
The OpenIFS software will models run on a variety of Unix based systems: Unix/Linux, Mac OS X. There is no support for running OpenIFS under Windows.
Install separately:
grib-api - this is a library and set of commands for working with and manipulating GRIB files. GRIB is the file format used as input and output for OpenIFS. The grib-api software is available for download from the grib-api software pages. Please use the latest version. Although pre-compiled, binary packages are available, please download the source files and compile it. This is to ensure the same compiler and compiler version is used for OpenIFS and grib-api, otherwise errors from mismatching modules are likely. See the grib_api for OpenIFS install page for more details on how to build grib_api for OpenIFS.
OpenIFS requires
All models require:
OpenIFS, SCM and OSM (HTESSEL) all require the OpenIFS requires the following in order to build and run:
...
perl - is required for the bundled FCM software bundled with OpenIFS used to compile the model. Some additional perl modules may be required for FCM (see below).
python - is required to run some of the tools e.g. preparing ERA-Interim files for the model.mpi library - an implementation of MPI must be available on your system. It can either be vendor supplied or one of the freely available versions such as MPICH or OpenMPI.
fortran95 & C compilers - many Unix systems come with gfortran/gcc by default which work well with OpenIFS. High Performance Computer facilities may provide other compilers which achieve better performance. OpenIFS supports: GNU, Portland, Intel, AIX compilers and Cray compilers. The fortran compiler must support an auto-double (e.g. -r8) capability as some source code files are in fixed format fortran.
mpi library - an implementation of MPI must be available on your system. It can either be vendor supplied or one of the freely available versions such as MPICH or OpenMPI.
OpenMP - the OpenIFS model can make use of OpenMP if it is supported on your system (multicore) and compilers but this is optional. Note that if OpenMP is used then the version of MPI used should be thread-safe.
lapack & blas libraries - these are usually available on all flavours of Linux/Unix. Some systems, notably HPC installations will have special optimized versions of these libraries. These should be used instead (if a version exists for your choice of compiler) to achieve a better performance. You may need to modify the compile configuration to access these optimized libraries. If the lapack/blas libraries are not available or you choose not to use them, OpenIFS comes with the necessary lapack code. This is disabled by default. Contact openifs-support@ecmwf.int for details.
...
OpenIFS require:
OpenIFS requires the following in order to build and run:
grib-api - this is a library and set of commands for working with and manipulating GRIB files. GRIB is the file format used as input and output for OpenIFS. The grib-api software is available for download from the grib-api software pages. Please use the latest version. Although pre-compiled, binary packages are available, please download the source files and compile it. This is to ensure the same compiler and compiler version is used for OpenIFS and grib-api, otherwise errors from mismatching modules are likely. See the grib_api for OpenIFS install page for more details on how to build grib_api for OpenIFS.
Single column model / Offline surface model require:
netCDF - an implementation of netCDF must be available on the system as the models read/write netcdf format.
Perl modules required
Software called FCM is used to compile the model. FCM is provided with OpenIFS. However, note that it may need additional Perl modules installed. The most likely missing modules are: XML::ParserCheck and Time::Piece.
...