Download
Note
The following instructions assume that you are working on a Linux machine.
Meso-NH package is developed and maintained using Git. It is strongly recommended, but not mandatory, to download Meso-NH package using Git repository, because:
It is easier for the Meso-NH’s support team to give you some assistance in case of trouble as Git allows us to know exactly what you have changed in the original package ;
It is easier for you to update to the last version or at least see the changes made for bug fix directly on your installation ;
Git is strongly recommended if you intend to modify the code.
A Tarball (from Zenodo) of Meso-NH package with an associated DOI is also available and can be use to cite Meso-NH in your publications.
Git repository
Prerequisites
To clone the Meso-NH Git repository the Git LFS extension, not included by default in the Git package, is required to handle binary (or large) files (LFS meaning Large File Storage). To install this extension:
either, install the Git LFS package on your system (you need root access) ;
or, if not possible, install it in your own environment. For that, you have to :
download the git-lfs archive from the link on the Git LFS web page ;
extract the archive and copy the git-lfs binary in a $HOME/bin directory by example (create this directory if it doesn’t exist) ;
execute the following commands :
export PATH=$PATH:$HOME/bin git lfs install
that will set up some filters under the name ‘lfs’ in the global Git config file $HOME/.gitconfig.
Cloning
Clone the Meso-NH Git repository from the development branch with the following command:
git clone https://src.koda.cnrs.fr/mesonh/mesonh-code.git -b MNH-60-branch MNH-V6-0-0
that will create the MNH-V6-0-0 directory containing a clone (copy) of the Meso-NH’s package corresponding to the developpement branch MNH-60-branch.
Warning
This version of Meso-NH doesn’t correspond to a stable version. By default, you are on the HEAD of the MNH-60-branch development branch containing modifications not yet tested. Please continue this documentation to check out a given version. However if you want to stay in this development branch you can go directly to Compile section.
Checking out a given version
Once the repository is cloned, it’s better for you to work on a stable version of Meso-NH. To go to the stable 6.0.0 version by example, you have to do:
cd MNH-V6-0-0
git checkout -b MYB-MNH-V6-0-0 PACK-MNH-V6-0-0
MYB-MNH-V-6-0-0 is the name of the local branch you created and PACK-MNH-V6-0-0 is the tag on which it is based.
Note
Each PACK-MNH-VX-Y-Z git tag corresponds to a stable MNH-VX-Y-Z version available in Tarball (from Zenodo). The different stable releases are visible here.
Tip
In the future you could check and update quickly differences with the new version of the package without having to download entirely the full package. Suppose that a new version, for example “PACK-MNH-V9-8-7”, is announced. To see the differences with your working copy, do:
git fetch
git diff HEAD PACK-MNH-V9-8-7
To go to the new version, you can, for example, create a new local branch:
git checkout -b MYB-MNH-V9-8-7 PACK-MNH-V9-8-7
At any time, you can also check the latest changes in the Git branch dedicated to the 6.0 version before the official release of the “bugN+1” bugfix version.
git fetch
git diff HEAD MNH-60-branch
And, test this development (not yet official) version by going to this branch:
git checkout --track origin/MNH-60-branch
Tip
The next step is to compile Meso-NH package.
Tarball (from Zenodo)
You can also download a compressed tarball containing the Meso-NH package from Meso-NH on Zenodo website . Then untar the file MNH-V 6-0-0.tar.gz where you want :
tar xvfz MNH-V6-0-0.tar.gz
Note
Each MNH-VX-Y-Z version available in Tarball (from Zenodo) corresponds to a PACK-MNH-VX-Y-Z git tag in the Git repository. The different stable releases are listed here.
Tip
The next step is to compile Meso-NH package.
What do you download ?
Meso-NH’s package contains sources, makefiles, pre-compiled executables, graphic tools and basic and advanced examples.
Hereafter is a quick description of Meso-NH’s tree :
MNH-V6-0-0/
bin/ : Miscellaneous scripts for compilation and execution
conf/ : Location of profile_mesonh files (Compile)
examples/ : Tests cases and benchmarks (Compile)
bench/
integration_cases/
test_cases/
tutorials/
exe/ : Links to binary compiled programs
pub/ : Public tools
src/
ACLIB/ : ACLIB’s source code
ARCH_SRC/ : Architecture-specific source code
LIB/ : External libraries (ECCODES, ECRAD, NETCDF, OASIS, …)
BITREP/
COMPRESS4LFI/
FOREFIRE/
HDF5Plugin-Zstandard/
ISORROPIA/
MEGAN/
MPIvide/
NEWLFI/
Python/
RAD/
s4py/
tensorproductmultigrid_Source/
eccodes-2.41.0-Source.tar.gz
hdf5-1.14.6.tar.gz
libaec-1.1.3.tar.gz
netcdf-c-4.9.3.tar.gz
netcdf-fortran-4.6.1.tar.gz
oasis3-mct_5.0.tar.gz
toy_2.0.tar.gz
zstd-1.5.7.tar.gz
MNH/ : Meso-NH’s source code
PHYEX/ : PHYEX’s source code
SURFEX/ : SURFEX’s source code
configure : Script to configure Meso-NH (Compile)
job_make_mesonh_* : Script to compile Meso-NH
job_make_examples_* : Script to launch examples on different computers
Makefile : Script for Compile
Makefile.MESONH.mk : Script for Compile
Rules.* : Compiled options for various compilers
README.md
README_MNH_CONDA : Instructions to install MNHPy
A-INSTALL : Historical instructions to install Meso-NH
Licence_CeCILL-C_V1-en.txt
Licence_CeCILL-C_V1-fr.txt
LICENSE
Note
MNHPy is a python library used to plot Meso-NH outputs.
ACLIB is the externalized chemistry and aerosols of Meso-NH and other models.
PHYEX is the externalized atmospheric physics common to AROME and HARMONIE-AROME.
SURFEX is the externalized surface physics (also used in AROME and ARPEGE).
Releases
Date |
Tarball |
Git tag |
Release note |
|---|---|---|---|
19/03/2026 |
|||
04/05/2026 |
|||
16/05/2025 |
|||
04/09/2024 |
|||
11/01/2024 |
Starting with version 6.0, minor versions will be maintained for two years from the release date of the next minor version. For example, version 5.7 will be maintained until March 19, 2028, two years after the release date of 6.0. Maintenance means that we will continue to release a version that only includes additional bugfix (the letter Z in the 5.7.Z version numbering).
A minimum of one new minor version (X.Y) and two bug fixes (X.Y.Z) will be released per year.