.gitattributes

+*	text=auto
 *.tar	filter=lfs diff=lfs merge=lfs -crlf
 *.tar.gz	filter=lfs diff=lfs merge=lfs -crlf
 */ecmwf.OD*	filter=lfs diff=lfs merge=lfs -crlf

.gitignore

+conf/profile_mesonh
+conf/profile_mesonh-*
+exe/*
+MY_RUN/INTEGRATION_CASES/**/*.des
+MY_RUN/INTEGRATION_CASES/**/*.dir
+MY_RUN/INTEGRATION_CASES/**/*.hdr
+MY_RUN/INTEGRATION_CASES/**/*.nc
+MY_RUN/INTEGRATION_CASES/**/ecmwf.OD.????????.??
+MY_RUN/INTEGRATION_CASES/**/file_for_xtransfer
+MY_RUN/INTEGRATION_CASES/**/OUTPUT_LISTING*
+MY_RUN/INTEGRATION_CASES/**/PRESSURE
+MY_RUN/KTEST/*/*/*.des
+MY_RUN/KTEST/*/*/*.lfi
+MY_RUN/KTEST/*/*/*.nc
+MY_RUN/KTEST/*/*/dir.??????:??:??
+MY_RUN/KTEST/*/*/dir_save
+MY_RUN/KTEST/*/*/dirconv
+MY_RUN/KTEST/*/*/dirextract
+MY_RUN/KTEST/*/*/ecmwf.OD.????????.??
+MY_RUN/KTEST/*/*/file_for_xtransfer
+MY_RUN/KTEST/*/*/gmeta
+MY_RUN/KTEST/*/*/gtopo30.*
+MY_RUN/KTEST/*/*/CLAY_HWSD_MOY.*
+MY_RUN/KTEST/*/*/DATA?1
+MY_RUN/KTEST/*/*/ECOCLIMAP_v2.0.*
+MY_RUN/KTEST/*/*/FICJD
+MY_RUN/KTEST/*/*/LISTING_DIA
+MY_RUN/KTEST/*/*/OUT_DIA
+MY_RUN/KTEST/*/*/OUTPUT_LISTING*
+MY_RUN/KTEST/*/*/PRESSURE
+MY_RUN/KTEST/*/*/REMAP*FFT*
+MY_RUN/KTEST/*/*/SAND_HWSD_MOY.*
+MY_RUN/KTEST/*/*/output_save*
+MY_RUN/KTEST/*/*/pipe_name
+MY_RUN/KTEST/*/*/gshhs(?).rim
+MY_RUN/KTEST/*/*/gshhs(?).zip
+MY_RUN/KTEST/*/*/rangs(?).cat
+MY_RUN/KTEST/*/*/rangs(?).cel
+MY_RUN/KTEST/*/*/rangs(?).zip
+MY_RUN/KTEST/*/*/visu*.png
+MY_RUN/KTEST/*/*/zsection*.png
+MY_RUN/KTEST/007_16janvier/012_spectre/spectra_16JAN.1.12B18.001_*
+MY_RUN/KTEST/009_ICARTT/001_pgd1/*.asc
+MY_RUN/KTEST/009_ICARTT/002_arp2lfi/ecmwf.OD.20040810.18-V2
+MY_RUN/KTEST/009_ICARTT/002_arp2lfi/mocage.GLOB22.20040810.18
+MY_RUN/KTEST/9??_*
+pub/FILEPP/filepp*
+!pub/FILEPP/filepp*.tar.gz
+pub/FILEPP/FILEPP*
+pub/FILEPP/MNH_Expand_*
+!pub/FILEPP/MNH_EXPAND_*.tar.gz
+src/dir_obj-*
+src/LIB/eccodes*
+!src/LIB/eccodes*.tar.gz
+src/LIB/grib_api*
+!src/LIB/grib_api*.tar.gz
+src/LIB/hdf5*
+!src/LIB/hdf5*.tar.gz
+src/LIB/libaec*
+!src/LIB/libaec*.tar.gz
+src/LIB/netcdf*
+!src/LIB/netcdf*.tar.gz
+src/LIB/MEGAN*
+src/LIB/oasis3-mct*
+!src/LIB/oasis3-mct*.tar.gz
+src/LIB/toy*
+!src/LIB/toy*.tar.gz
+vscode_mod

A-INSTALL

 #
 # Version of PACKAGE MESONH "Open distribution"
-#              PACK-MNH-V5-1-3
-#              DATE : 20/11/2014
-#              VERSION : MESONH MASDEV5_1 + BUG-3 
+#              PACK-MNH-V5-7-1
+#              DATE : 04/09/2024
+#              VERSION : MESONH MASDEV5_7 + BUG-1
 #
 #  MAP
 #
 #        0) TWO WAYS OF DOWNLOADING MESONH
 #      I-A) DOWNLOAD VIA THE WEB MESONH HOME PAGE
-#      I-B) DOWNLOAD VIA CVS ANONYMOUS 
+#      I-B) DOWNLOAD VIA GIT ANONYMOUS 
 #       II) CONFIGURING THE MESONH PACKAGE
 #      III) COMPILING/INSTALLING THE MESONH PACKAGE ON YOUR LINUX COMPUTER 
 #       IV) RUN SOME "SMALL KTEST" EXAMPLES
 #        V) RECOMPILING YOUR 'OWN' SOURCES ONLY 
-#       VI) COMPILING/INSTALLING MESONH ON GENCI & ECMWF & METEO COMPUTERS
+#       VI) COMPILING/INSTALLING MESONH ON GENCI & ECMWF & METEO & CALMIP COMPUTERS
 #      VII) "SCANDOLLAR" = SCRIPTING YOUR OWN PROCEDURES 
 #
 #     VIII) TROUBLE-SHOOTING
@@ -21,19 +21,25 @@
 #           b) Compiler bug with "ifort 10.0.xxx" 
 #
 #       IX) OPTIONAL COMPILATION
-#           a) MNH_NCWRIT for netcdf graphic output file 
-#           b) MNH_FOREFIRE for forefire runs ( external package needed )
-#           c) MNH_RTTOV for optional radiative computation
-#           d) cleaning previous compiled version
+#           a) MNH_FOREFIRE for forefire runs ( external package needed )
+#           b) MNH_RTTOV for optional radiative computation
+#           c) MNH_ECRAD for optional compilation of new ECRAD radiative library from ECMWF
+#           d) MNH_MEGAN for optional compilation of MEGAN 
+#           e) cleaning previous compiled version
 #
 #
+# NEW since MNH-56X : For conda package for graphic output in test-case examples , read
+# the 'README_MNH_CONDA' file in this (root) directory
+#
+#
+^L
 #  0) TWO WAYS OF DOWNLOADING MESONH
 #  =================================
 #
 #  MESONH sources and executables 
 #  http://mesonh.aero.obs-mip.fr
 #  are developed and maintained with the
-#  CVS tools ( http://www.cvshome.org/ )
+#  Git tools ( https://git-scm.com/ )
 #
 #  There are two ways to download the package of
 #  MESONH containing :
@@ -47,22 +53,24 @@
 #  via a download of a "tar ball" in the WEB site of MESONH
 #
 #  The second way is for USER/DEVELOPER of MESONH
-#  via the use of the CVS tools and an access via anonymous
-#  connection with "ssh" to the CVS REPOSITORY of the MESONH package 
+#  via the use of Git and an anonymous ssh connection to the Git repository of
+#  the MESONH package 
 # 
 #
-# REM: It is now strongly recommended, but it's not an obligation, 
-#      for all users to use de CVS solution, because:
+# REM: It is now strongly recommended, but not mandatory, 
+#      for all users to use the Git solution, because:
 #
 #      * It's far more easy for us ( support team ) to give you some assistance
-#        in case of trouble ... as the CVS tool permits us to know exactly
+#        in case of trouble... as Git permits us to know exactly
 #         what you have changed in the original PACKAGE
 #
-#      * It's much more easy for you to update to the last version ...  
-#        or at least see the change made for BUGFIX directly on our installation .
+#      * It's much more easy for you to update to the last version...  
+#        or at least see the change made for BUGFIX directly on our
+#        installation.
 #
 #
-#  So here are explained the two ways <=> mutually exclusif 
+#  Following, are presented the two mutually exclusive ways to get the MesoNH
+#  package:
 #
 #
 ^L
@@ -70,194 +78,172 @@
 # ==========================================
 #
 # With your preferred web browser go to the MESONH WEB SITE
-# 
+#
 #  http://mesonh.aero.obs-mip.fr/mesonh
 #     ---> Download
-#           ---> CVS MESONH
 #
 # or directly
 #
-# http://mesonh.aero.obs-mip.fr/cgi-bin/mesonh_interne/viewcvs.cgi/MNH-VX-Y-Z
-#
-# in the field  "Show files using tag:" 
-#
-#    ---> select "PACK-MNH-V5-1-3"
-#
-# and then download the file "PACK-MNH-VX-Y-Z.tar.gz" by the link 
-#
-#    --> Download tarball
+# http://mesonh.aero.obs-mip.fr/mesonh/dir_open/dir_MESONH/MNH-V5-7-1.tar.gz
 #
-# Then untar the file "PACK-MNH-VX-Y-Z.tar.gz" where you want to,
-# in your home directory for example:
+# Then untar the file "MNH-V5-7-1.tar.gz" where you want to.
+# For example, in your home directory:
 #
- 
+
 cd ~
-tar xvfz PACK-MNH-VX-Y-Z.tar.gz
+tar xvfz MNH-V5-7-1.tar.gz
 
 #
-# As the directory did not reflect the last version name move it 
-# to the right one
-#
- 
-mv MNH-VX-Y-Z MNH-V5-1-3
-      
-#
-#  Process now to the chapter to configure the MesoNH 
+#  Process now to the chapter to configure the MesoNH package.
 #
 # => II) CONFIGURING THE MESONH PACKAGE
 #
 ^L
-# I-B) DOWNLOAD VIA CVS ANONYMOUS
+# I-B) DOWNLOAD VIA GIT ANONYMOUS
 # ===============================
 #
-#    a) download the ssh key file "anoncvs.key" for anonymous connection 
-#    -------------------------------------------------------------------
+#    a) Prerequisites
+#    ----------------
 #
-# With your preferred web browser go to the MESONH WEB SITE
-# 
-#  http://mesonh.aero.obs-mip.fr/mesonh
-#     ---> Download
-#           ---> CVS PACKAGE MESONH
+# In order to clone the Meso-NH git repository that contains sources, compiled
+# libraries and binary tools, the git LFS extension is required to handle
+# binary (or large) files. So before starting, be sure:
 #
-# or directly
-#
-#   http://mesonh.aero.obs-mip.fr/cgi-bin/mesonh_interne/viewcvs.cgi/MNH-VX-Y-Z
-#
-# in the field  "Show files using tag:" 
-#
-#    ---> select "PACK-MNH-V5-1-3"
-#
-#   download the file "anoncvs.key"
+#  * to have git v1.8.2 or higher installed on your workstation. You can run
+#    and check with:
+
+git --version
+
+#  * to install the git LFS extension (not included by default in the Git
+#    package):
+#    - get the linux git-lfs archive from the "Download v1.X.Y (Linux)" link on
+#      the web page https://git-lfs.github.com/
+#    - extract the archive and copy the git-lfs binary in your $HOME/bin (the
+#      provided install.sh script doesn't need to be executed)
+#    - from any directory, you can now execute:
+
+git lfs install
+
+#      that will set up some filters under the name "lfs" in the global Git
+#      config file ($HOME/.gitconfig)
 #
-#   by  :
-#         1) a  "left-click" in the "Rev." column 
-#       + 2) a  "right-click" on "download" 
-#                   ---> save link to disk
-#               (Warning :: don't copy the file content with  mouse copy/past 
-#               because it contains binary-encoded information !!!)
+#    b) Before cloning
+#    -----------------
 #
-#   then copy this file in your "${HOME}/.ssh/" directory
+#  * Download the private key to access the anonymous Meso-NH Git server (read-
+#    only access) by following the next link:
 #
-#   AND VERY IMPORTANT !!!
-#   Modify the "read/write" permission with:
-# 
 
-chmod 600 anoncvs.key
+http://mesonh.aero.obs-mip.fr/mesonh57/GitSources?action=AttachFile&do=get&target=anongitmesonh.key
 
 #
-#    b) download the config file "config.anoncvs_www"
-#    ------------------------------------------------ 
+#    and save the file in your $HOME/.ssh/ directory.
 #
-#    For METEO-FRANCE & IDRIS & CINES & Laboratoire d'Aerologie computers ( IP address filter )
-#    ==========================================================================================
+#  * Change the access permissions of the key with:
 #
-#    download the file
+
+chmod 600 $HOME/.ssh/anongitmesonh.key
+
 #
-#      -->  "config.anoncvs_www" 
+#  * Copy/paste the following lines and add them in your $HOME/.ssh/config file
+#    (create the file if it is missing):
 #
-#    Then concatened the file content with your "${HOME}/.ssh/config" file
-#    ( this will define the computer alias "mesonh_anoncvs_www" for future ssh 
-#      anonymous connections )
 
-cd ${HOME}/.ssh
-cat config.anoncvs_www >> config
+Host anongit_mesonh
+  User anongit
+  IdentityFile ~/.ssh/anongitmesonh.key
+  Hostname 195.83.22.22
+  Port 22222
 
 #
-#    FOR OTHER COMPUTERS USE special "config.anoncvs_www" 
-#    ===================================================
-#
-#    if the computer, from which you download the MESONH sources,
-#    is external to  METEO-FRANCE & IDRIS & CINES & Laboratoire d'Aerologie Laboratoire download this file 
+# Before cloning the repository, execute:
 #
-#      --> "config.anoncvs_www_ext" 
 
-cd ${HOME}/.ssh
-cat config.anoncvs_www_ext >> config
+git config --global http.sslverify false
 
 #
-#    OR for ECMWF computer ( cca ) download this config file 
-#    ( to bypass the gateway filter ) 
+# This is necessary to disable the certificate checks because a self-signed
+# certificate was used for the LFS server.
 #
-#      --> "config.anoncvs_www_ecmwf"
+#    c) Cloning the Meso-NH Source repository on the developpement branch MNH-57-branch
+#    ----------------------------------------------------------------------------------
+#
+# Finally you can clone the Meso-NH Git repository with the following command:
 #
 
-cd ${HOME}/.ssh
-cat config.anoncvs_www_ecmwf >> config
+git clone anongit@anongit_mesonh:/gitrepos/MNH-git_open_source-lfs.git -b MNH-57-branch MNH-V5-7-1
 
 #
-#    c) Setting CVS variables
-#    ------------------------
+# that will create the MNH-V5-7-1 directory containing a clone (copy) of the
+# Meso-NH package on the remote developpement branch MNH-57-branch
 #
-#    set the CVS_RSH et CVSROOT like this
-#    ( in your ".profile" or ".bashrc" file )
 #
-
-export CVS_RSH=ssh
-export CVSROOT=:ext:mesonh_anoncvs_www:/home/cvsroot
-
+#   d) Checking out a given version of MESONH
+#   -----------------------------------------
+#
+# Once the repository is cloned, it's better for you to checkout your own branch
+# (by default, you are on HEAD of the MNH-57-branch development branch  ).
 #
-#   c)  Checking out the "MESONH PACKAGE"  
-#   -------------------------------------
+# To create your local branch corresponding to the V5-7-1 version, type:
 #
-#   Now, from your "$HOME" directory for example 
-#   extract the version "PACK-MNH-V5-1-3"
-#   of the directory "MNH-VX-Y-Z" from the
-#   cvs repository : 
 
-cd ~
-cvs co -r PACK-MNH-V5-1-3 -d MNH-V5-1-3 MNH-VX-Y-Z
+cd MNH-V5-7-1
+git checkout -b MYB-MNH-V5-7-1 PACK-MNH-V5-7-1
 
 #
-# WARNING : don't use a sub-directory with dot "." in the name
-#            ---> you could have some trouble when compiling mesonh
+# MYB-MNH-V5-7-1 is the name of the local branch you created
+# and
+# PACK-MNH-V5-7-1 is the remote/origin tag on which it is based.
 #
-#  this will create in your "$HOME" a directory "MNH-V5-1-3" 
-#  which contains of the last revision named "PACK-MNH-V5-1-3" 
-#  of the MESONH PACKAGE 
+# The advantage of this way of downloading the package is that in the future
+# you could check/update quickly differences with the new version of the
+# package without having to download entirely the full package.
 #
-#  The advantage of this way of downloading 
-#  the package is that in the future you 
-#  could check/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-V5-7-1", is announced.
 #
-#  Suppose that a new version for example
-#  "PACK-MNH-V5-1-4" is announced ...
+#  To see the differences with your working copy, do:
 #
-#  To see the differences with your working copy
-#  do
+
+git fetch
+git diff HEAD PACK-MNH-V5-7-1
+
+#
+#  To go to the new version, you can, for example, create a new local branch:
 #
 
-cd ~/MNH-V5-1-3
-cvs diff -r PACK-MNH-V5-1-4
+git checkout -b MYB-MNH-V5-7-1 PACK-MNH-V5-7-1
 
 #
-#  And to upgrade your working copy
+# At any time, you can also check for "uptodate" changes in the Git branch
+# dedicated to the MNH57 version before the official release of the "bugN+1"
+# bugfix version.
 #
 
-cd ~/MNH-V5-1-3
-cvs update -r PACK-MNH-V5-1-4 -d -P
+git fetch
+git diff HEAD MNH-57-branch
 
 #
-# At any time you could also check for "uptodate" 
-# changes in the CVS "branch" dedicated to the MNH410 version
-# before the official release of the "bugN+1" bugfix
+# And, test this development (not yet official) version by going to this branch:
 #
 
-cvs diff -r MNH410-BUG-branch
-  
+git checkout --track origin/MNH-57-branch
 #
-# An at "your own risk" update to this
-# ( not yet official ) version by
+#    e) Cloning the Meso-NH Documentation repository
 #
+# In a similar fashion, you can clone the Meso-NH documentation Git repository
+# with the following command:
+#
+
+git clone anongit@anongit_mesonh:/gitrepos/MNH-DOC.git
 
-cd ~/MNH-V5-1-3
-cvs update -r MNH410-BUG-branch -d -P
+#
+# that will create the MNH-DOC directory containing the latest LaTeX sources of
+# the Meso-NH documentation.
 
 #
-#  Well, the use of CVS is not under the scope of this "INSTALL" document ...
+#  Well, the use of git is not under the scope of this "INSTALL" document...
 #
-#   Now go to then next chapter 
+#   Now, go to the next chapter 
 #
 #   => II) CONFIGURING THE MESONH PACKAGE
 #
@@ -271,7 +257,7 @@ cvs update -r MNH410-BUG-branch -d -P
 #    use the "./configure" script like this 
 #
 
-cd ~/MNH-V5-1-3/src
+cd ~/MNH-V5-7-1/src
 ./configure
 . ../conf/profile_mesonh
 
@@ -279,56 +265,62 @@ cd ~/MNH-V5-1-3/src
 #    this will create a configuration file "profile_mesonh" with
 #    an extension reflecting the different "choices" made automatically
 #    to match the computer on which you want to install MESONH
-#   
+# 
 #    WARNING :
 #    =========
-#    On GENCI & ECMWF & METEO/CNRM  computers, the './configure' is tuned to 
+#    On GENCI & ECMWF & METEO/CNRM & METEO/DSI  computers, the './configure' is tuned to 
 #    identify the computer on which the command is used
-#    so the good compiler,  mpi & cdf library , etc ... 
+#    so the good compiler, MPI & netCDF libraries,... 
 #    are automatically chosen
 # 
+#    To install this version on one of these machines, go to the chapter
+#
+#    => VI) COMPILING/INSTALLING ON GENCI & ECMWF & METEO COMPUTERS
+#
+#    else follow the guidelines below.
+#
 #    /!\ This is not the case in your "own" personal Linux computer ...
 #    So is up to you to set the ARCH variable correctly
 #    ARCH     = Fortran compiler to use,
-#    VER_MPI  = version of MPi to, use 
+#    VER_MPI  = version of MPI to use ,
 #    OPTLEVEL = 
 #    etc ...
-#    and all the other environnement variables . 
+#    and all the other environnement variables. 
 # 
-#    Be default, for an unknow computer, you will have  :
+#    Be default, for an unknown computer, you will have:
 #
 #   - the compiler choosen to be "gfortran" => ARCH=LXgfortran
-#   - the mpi library to be the MPIVIDE  => VER_MPI=MPIVIDE
-#     ( empty mpi library coming with MESONH package = no  parallel run possible )
-#   - the level compiler optimization   => OPTLEVEL=DEBUG
+#   - the MPI library to be the MPIVIDE  => VER_MPI=MPIVIDE
+#     ( empty MPI library coming with MESONH package = no parallel run possible )
+#   - the level of optimization for the compiler  => OPTLEVEL=DEBUG
 #     (  for development purpose ,fast compilation & debugging )   
 #       
 #    SO IF NEEDED:
 #    ============
-#    you could change the default FLAG compiler/mpi/optlevel
+#    you could change the default FLAG compiler/MPI/optlevel
 #    like this, for example 
 
 export ARCH=LXifort        # Use Intel "ifort" compiler on LX=linux Plateform 
 export VER_MPI=MPIAUTO     # Use MPI with compiler wrapper 'mpif90', for computer having this wrapper installed 
-export OPTLEVEL=O2         # Compile in O2 , 4 time faster then DEBUG, but least error check 
+export OPTLEVEL=O2         # Compile in O2, 4 times faster then DEBUG, but less error checks
 
 ./configure
 
 #    and then source/load the new generate file
 
-. ../conf/profile_mesonh.LXifort.MNH-V5-1-3.MPIAUTO.O2
+. ../conf/profile_mesonh.LXifort.MNH-V5-7-1.MPIAUTO.O2
 
 #
 #  REM: 
 #  ====
 #
-#  - Options specific to compile/architecture, like 'OPTLEVEL' are defined inside the "Rules.${ARCH}.mk" .
+#  - Options specific to compiling/architecture, like 'OPTLEVEL' are defined inside the "Rules.${ARCH}.mk" .
 #
 #  - Options specific to library like "mpi"="VER_MPI" or "cdf"="VER_CDF" are defined inside "Makefile.MESONH.mk"
 #
-#  - If need, for adaptation to your requirement, look inside the files and changes options for your needs .   
+#  - If needed, for adaptation to your requirements, look inside the files and changes options for your needs.
 #  
-#  - On PC-Linux, if needed , look in the "MesonhTEAM Wiki" to know how to compile the library MPI = OPEN-MPI , with MESONH
+#  - On PC-Linux, if needed, look at the "MesonhTEAM Wiki" to know how to compile the OpenMPI library with MESONH:
 #
 #    http://mesonh.aero.obs-mip.fr/teamwiki/MesonhTEAMFAQ/PC_Linux
 #      --> Compilation of OPEN-MPI
@@ -341,7 +333,7 @@ export OPTLEVEL=O2         # Compile in O2 , 4 time faster then DEBUG, but least
 # go to the directory  "src"
 #
 
-cd  ~/MNH-V5-1-3/src
+cd  ~/MNH-V5-7-1/src
 
 #
 # if you have not already configured your MESONH environment
@@ -362,9 +354,9 @@ cd  ~/MNH-V5-1-3/src
 # The compilation will take about 20 minutes on modern PC-Linux ...
 # 
 # If you have a multi-processor machine you can speedup
-# the compilation, for example, on two processors with:
+# the compilation, for example on four cores, with:
 
-(g)make -j 2
+(g)make -j 4
 
 #
 #
@@ -382,9 +374,9 @@ cd  ~/MNH-V5-1-3/src
 # The exact name of this "dir_obj..." depends on the different environnement
 # variables set by the "profile_mesonh...." which you have loaded before the compilation.
 #
-# This allow by loading different "profile_mesonh.." files to compile in the same
-# source/installation directory different version of MESONH , with different
-# compiler, different version of MPI , different USER sources , etc ...
+# This allows by loading different "profile_mesonh.." files to compile in the same
+# source/installation directory different versions of MESONH , with different
+# compilers, different versions of MPI, different USER sources...
 #
 #
 # To install the new compiled program in the "$SRC_MESONH/exe"
@@ -394,13 +386,13 @@ cd  ~/MNH-V5-1-3/src
 make installmaster
 
 #
-# The executable with their full name, including, $ARCH , compiler
-# and MPI , level of optimization, will be linked in the "../exe" directory
+# The executables with their full name, including $ARCH, compiler,
+# MPI and level of optimization, will be linked in the "../exe" directory
 # 
 # REM: 
 # ---
-#      The "make installmaster" need to be done only one time by "version" . 
-#      If you change/add source only you have to do "make" 
+#      The "make installmaster" need to be done only one time by "version". 
+#      If you only change/add source, you have to do "make" 
 
 make
  
@@ -408,7 +400,7 @@ make
 #  IV) RUN SOME "SMALL KTEST" EXAMPLES
 #  ===================================
 #
-#  After compilation & installation you could run
+#  After compilation & installation, you could run
 #  some basic "KTEST" examples from the "src" directory 
 #  by running:
 
@@ -459,13 +451,13 @@ make 004_Reunion_ncl2
 # Step-1 : prepare your source directory
 # ---------------------------------------
 #
-# Put your own source in a subdirectory of "${SRC_MESONH}/src" named 
+# Put your own sources in a subdirectory of "${SRC_MESONH}/src" named 
 #  
    
 ${SRC_MESONH}/src/MY_MODIF
 
 #
-#  All subdirectories in "MY_MODIF" will be scanned so if you want
+#  All subdirectories in "MY_MODIF" will be scanned. So if you want,
 #  you could make a subdirectory for each component of the MESONH
 #  Package
 #
@@ -476,24 +468,24 @@ cp .../isba.f90   MY_MODIF/SURFEX/.
 #
 #  /!\ WARNING :
 #  -------------
-#   - In this subdirectory put only fortran source you want to compile !!!
-#   Don't use it as a trash, with old sources file like 'my_source.f90.old'
+#   - In this subdirectory, put only fortran source you want to compile !!!
+#   Don't use it as a trash with old sources file like 'my_source.f90.old'
 #   or 'tar' files 'mysource.tar' . 
-#   - All 'spirituous' file will confuse the  'make' commande .   
+#   - All 'spirituous' file will confuse the 'make' command.
 #
 #   
 # Step-2 : configure/compiling with VER_USER=...
 # ----------------------------------------------
 # 
-# - Logout of the current session, to be sure to unset all the 
-#   environnement variables load with the your 'master 'profile_mesonh'   
+# - Logout of the current session to be sure to unset all the 
+#   environnement variables loaded with the your 'master 'profile_mesonh'
 #
-# - Login again and :
+# - Login again and:
 #
 #   - set the variable "VER_USER" with the name of your "USER VERSION",  
-#   - set also optionnal the , ARCH, VER_MPI ,etc... , you want to use 
+#   - set also the optional ARCH, VER_MPI... you want to use.
 #  
-# and run again the "./configure" commande  
+# and run again the "./configure" command
 
 #export ARCH=...
 #export VER_MPI=...
@@ -506,21 +498,21 @@ export VER_USER=MY_MODIF
 #
 # as before load it & and compile with the command "make user"
 
-. ../conf/profile_mesnh...${VER_USER}...
+. ../conf/profile_mesonh...${VER_USER}...
 
 make user
 
-# this will compilation Only your sources, and the files depending of your sources
-# and generate the new executables in your own directory 
+# this will compile only your sources and the files depending on your sources
+# and generate the new executables in your own directory
 #
 #   dir_obj-$(ARCH).../${VER_USER}
 #
 #
 # WARNING : 
 # ========
-#  before compiling your own sources be sure that these ones
-#  are younger than the "*.o" files of the MASTER directory
-#  if any doubt, at any time use the command 
+#  Before compiling your own sources be sure that these ones
+#  are younger than the "*.o" files of the MASTER directory.
+#  If any doubt, at any time use the command
 #
 #      touch *.f*
 #
@@ -531,25 +523,24 @@ make user
 # -----------------------------
 #
 #
-# Now if the compilatio is OK,  you could to test this new version with the "make examples"
+# Now if the compilation is OK, you could test this new version with the "make examples".
 #
-# First, install the new binaries in the '${SRC_MESONH}/exe' with 
+# First, install the new binaries in the '${SRC_MESONH}/exe' with
 
 make installuser
 
-#   The "make installuser" need to be done only one time by "version" . 
+#   The "make installuser" needs to be done only one time by "version".
 
 #
-# And run the examples, your Version should appear in the name of the executables
-# used .
+# And run the examples. Your version should appear in the name of the used executables.
 #
 
 make examples 
 
 ^L
 #
-#   VI) COMPILING/INSTALLING ON GENCI & ECMWF & METEO COMPUTERS
-#   ===========================================================
+#   VI) COMPILING/INSTALLING ON GENCI & ECMWF & METEO & CALMIP COMPUTERS
+#   ====================================================================
 #
 #   After downloading "exactly" like on "any standalone PC" 
 #   run the "./configure" command :
@@ -558,123 +549,197 @@ make examples
 ./configure
 
 #
-#  - If you do not have sufficient space in your "$HOME" directory
+#  - If you do not have sufficient space in your "$HOME" directory,
 #    install the whole package directly on the ${WORKDIR}
+#    /!\  the name of the WORKDIR differ in the differents computer center
+#    read the doc , most of them manage disk space throw 'multi-projet' with only one unique login . 
 #
 #   WARNING :
 #   ======== 
 #    - Think to do a backup of your installation 
-#    - This space is not more "purged" but a "crash disk" could/will
+#    - This space is no "purged" but a "crash disk" could/will
 #      probably occur !!!
 # 
 
 cd $WORKDIR
-cvs co -r PACK-MNH-V5-1-3 -d MNH-V5-1-3 MNH-VX-Y-Z
-cd MNH-V5-1-3/src
+cd MNH-V5-7-1/src
 
 ./configure
  
 #   
 #   Due to limitation in time & memory on interactive connection 
-#   then compile the MESONH PACKAGE in batch mode with the different "job_make_mesonh*" files
+#   in some computer you have to compile the MESONH PACKAGE in batch mode with the different "job_make_mesonh*" files
 #   
 #   at IDRIS :
 #   ---------
 #
 
-#   - On ADA ( IBM/x3750 ) with :
+#   - On JEAN-ZAY ( HPE ) the compilation is in interactive :
 
-llsubmit job_make_mesonh_IBM_ada
+cd MNH-V5-7-1/src
+. ../conf/profile_mesonh-LXifort-R8I4-MNH-V5-7-1-MPIINTEL-O2
+make -j16 |& tee error$XYZ
+make installmaster
 
-#
-#
-#   - On TURING (IBM BG/Q ) : 
+# You could also use the 'compil' partition
 
-llsubmit job_make_mesonh_BGQ
+sbatch job_make_mesonh_HPE_jeanzay
+
+#   - to run the test case examples  run
+
+sbatch -A {your_projet}@cpu job_make_examples_BullX_jeanzay
 
-#
-#
-#   BACKUP : /!\ backup your work on "ergon"
 #
 #   
-#   at CINES on JADE( SGI/ICE ) , OCCIGEN not tested yet  :
+#   at CINES on ADASTRA (BULLX)  :
 #   -------------------------------------------------------
 # 
-#   - install the PACKAGE in your "/store/${USER}" directory 
-#   - you could compile in interactive mode
+#   - install the PACKAGE in your $HOME ( default 50Go  of quota )
+#   - Compile in interactive mode ( see IDRIS )
 #
-#    BACKUP : /!\ backup your work on "/data/${USER}"
-# 
+#   - to run the test case examples  run
 
+sbatch job_make_examples_BullX_occigen
 
+#
+#   
+#   at TGCC on IRENE (BULLX)  :
+#   -------------------------------------------------------
+#
+#   At TGCC , you have two architectures accessible throw 2 differents frontals
+#   but with a commun disk space , connect to : 
+#
+#   - ssh irene-fr  : for Intel SkyLake processors
+#      On Intel processors the MPI use is OPENMPI/4.1.4
+#      the configure will generate a
+#      profile_mesonh-LXifort-R8I4-MNH-V5-7-1-MPIAUTO-O2
+#
+#   - ssh irene-amd : for AMD , processors
+#      On AMD processors the MPI use is OPENMPI/4.1.4
+#      the configure will generate a
+#      profile_mesonh-LXifort-R8I4-MNH-V5-7-1-AMD-MPIAUTO-O2
 # 
-#   at ECMWF on cca ( CRAY/XC30 ) :
-#   ----------------------------
 #
-#   - to install MESONH go to your $PERM directory
-#     if you need more disk space than allowed for 'standard' user 
-#     Ask to Dominique Lucas, look this email :
+#   At TGCC they use 'one login' for multi-project allocation .
+#   This induce 'strange' problem with the installation of eccodes
+#   resulting in file with the wrong default group and 'disk quota excedeed' error
 #
-#    http://mesonh.aero.obs-mip.fr/cgi-bin/mesonh_interne/mail2html.cgi?file=2009_09_24_15:31:54
+#   You could get your different project info by 'ccc_myproject'
 #
-#   - for the compilation use :
-
-qsub job_make_mesonh_CRAY_cca
+#   I recommand you first, supposing that the "Genci Allocation" you want to use
+#   as for projet group "genXXXX"
+#
+#   1) to add  in your "~/.bash_profile"
+#
+module switch dfldatadir dfldatadir/genXXXX
+newgrp genXXXX
 
+#   2) "logout & login" again
+#      and check that you have now the good default group
 #
-# REM : On CRAY computer cca , the default compiler is the CRAY one = crayftn .
-#      I you have trouble with this one , you could compile with the Intel/ifort one .
-#      Use the ifort one do :
+id -ng
+--> genXXXX
+echo $CCCHOME
+--> /ccc/.../home/genXXXX/{your_login}
 
-export ARCH=LXifort
+#  If all is OK, you can install the code interactively as usual
+#
+#   - install the PACKAGE in your ${CCCHOME} ( default 20Go  of quota )
+#  for example on Intel frontal
+cd ${CCCHOME}
+cd MNH-V5-7-1/src
 ./configure
+. ../conf/profile_mesonh-LXifort-R8I4-MNH-V5-7-1-MPIAUTO-O2
+make -j16 |& tee error$XYZ
+make installmaster
 
-...
+# REM: The eccode lib will be installed in your ${CCCWORKDIR}
+#      also for the quota problem ...
+#    
 
-création du fichier -->  ../conf/profile_mesonh-LXifortI4-MNH-V5-1-3-MPICRAY-O2
+#   - to run the test case examples  run
+#
+# On intel Skylake
+ccc_msub job_make_examples_BullX_irene
 
-# And for the compilation & example job , switch the ARCH variable to LXiort :
+# On intel AMD 
+ccc_msub job_make_examples_BullX_irene_AMD
 
-vi  job_make_mesonh_CRAY_cca(job_make_examples_CRAY_cca)
+# 
+#   at ECMWF on hpc-login ( ATos/HPCF ) :
+#   ------------------------------------------
+#
+#   - to install MESONH go to your $HPCPERM directory
+#
+#   - for the compilation :
+#   after the ./configure in the login node
+#
+#   connecte to an "interactive compute node"  via ( 16 core & 16GO of memory 
 
-ARCH=LXifort
-#ARCH=LXcray # this is the default one
-. ../conf/profile_mesonh-${ARCH}I4-MNH-V5-1-3-MPICRAY-O2
+ecinteractive -c16 -m 16G -t 12:00:00
+
+etc ...
 
 
+#   - to run the test case examples  run
+
+sbatch  job_make_examples_Atos_HPCF
 
 #
-#   EXAMPLES ON GENCI & ECMWF PLATFORMS
-#   ====================================
+#   - At Meteo-France DSI on belenos
 #
-#  - At IDRIS
+#  to install the whole package on your "$HOME" directory
+#  untar the file "MNH-V5-7-1.tar.gz" from its location :
+
+cd ~
+tar xvf $MESONH/MNH-V5-7-1.tar.gz
+
+#  run the "./configure" command :
+
+cd MNH-V5-7-1/src
+./configure
+
 #
+#   Due to limitation in time & memory on interactive connection
+#   then compile the MESONH PACKAGE in batch mode with the job_make_mesonh_BullX_belenos file :
 
-# on ADA
+sbatch   job_make_mesonh_BullX_belenos
 
-llsubmit job_make_examples_IBM_ada
+#   This job does : gmake -j 4
+#   then : make installmaster
 
-#on TURING
+#   To run basic KTEST examples :
 
-llsubmit job_make_examples_BGQ
+sbatch   job_make_examples_BullX_belenos
 
+#   Step-2 : configure/compiling with VER_USER=...
+# ----------------------------------------------
+#  In a new session set the variable "VER_USER" with the name of your "USER VERSION",
+#  and run again the "./configure" command
 #
-#   - At CINES on JADE( SGI/ICE ) :
+
+export VER_USER=MY_MODIF
+./configure
+
+# this will regenerate the "profile-mesonh" file and a copy
+# of this with the extent  "profile_mesonh...${VER_USER)..."
 #
-# load ".profile_mesonh..." & set the variables :
- 
-export MONORUN="mpirun -np 1"
-export MPIRUN="mpirun -np 4 " 
-  
-# and run with 
+#   in job_make_mesonh_user_BullX insert " export VER_USER=MY_MODIF "
+#   then submit in batch mode
 
-make examples
+sbatch  job_make_mesonh_user_BullX_belenos
 
 #
-#   - At ECMWF on cca
+#   
+#   at CALMIP on OLYMPE (BULLX)  :
+#   -------------------------------------------------------
+# 
+#   - install the PACKAGE in your /tmpdir/$USER
+#   - Compile in interactive mode 
 #
+#   - to run the test case examples  run
 
-llsubmit  job_make_examples_CRAY_cca
+sbatch job_make_examples_BullX_olympe
 
 #
 # That's all for the basic INSTALLATION of the "MESONH PACKAGE"
@@ -684,7 +749,7 @@ llsubmit  job_make_examples_CRAY_cca
 #  VII) "SCANDOLLAR" = SCRIPTING YOUR OWN PROCEDURES 
 #  ====================================================
 
-REM : not tested on 5-1-X version ...
+REM : not tested on 5-5-X version ...
 
 # A small script 'scandollar' is in test in this version of MESONH.
 # It will help you to build a complete chaining of an experiment. 
@@ -730,7 +795,7 @@ scandollar
 
 ## OUTPUT ::
 
->#  read default config file :: --->  CONF_DOLLAR=/home/escj/DEV64/PACK-MNH-V5-1-3/conf/post/confdollar_aeropc_default
+>#  read default config file :: --->  CONF_DOLLAR=/home/escj/DEV64/PACK-MNH-V5-7-1/conf/post/confdollar_aeropc_default
 >#
 >#  read    user config file :: --->  CONFIG=confdollar
 >#
@@ -752,7 +817,7 @@ scandollar 0*
 
 ## OUTPUT ::
 >#
->#  read default config file :: --->  CONF_DOLLAR=/home/escj/DEV64/PACK-MNH-V5-1-3/conf/post/confdollar_aeropc_default
+>#  read default config file :: --->  CONF_DOLLAR=/home/escj/DEV64/PACK-MNH-V5-7-1/conf/post/confdollar_aeropc_default
 >#
 >#  read    user config file :: --->  CONFIG=confdollar
 >#
@@ -826,22 +891,22 @@ cp -R  007_16janvier_scandollar /.../your_directory
 #
 # use this "profile_mesonh" :
 
-.  /home/rech/mnh/rmnh007/DEV/MNH-V5-1-3/conf/profile_mesonh-SX8-MNH-V5-1-3-MPIAUTO-O4
+.  /home/rech/mnh/rmnh007/DEV/MNH-V5-7-1/conf/profile_mesonh-SX8-MNH-V5-7-1-MPIAUTO-O4
 
 # And the examples are here ( link to my $WORKDIR in actually )  
 
-/home/rech/mnh/rmnh007/DEV/MNH-V5-1-3/MY_RUN/KTEST/007_16janvier_scandollar
+/home/rech/mnh/rmnh007/DEV/MNH-V5-7-1/MY_RUN/KTEST/007_16janvier_scandollar
 
 #
 #  On vargas
 #  ---------
 #  use this "profile_mesonh" :
 
-. /workgpfs/rech/mnh/rmnh007/DEV/MNH-V5-1-3/conf/profile_mesonh-AIX64-MNH-V5-1-3-MPIAUTO-O2
+. /workgpfs/rech/mnh/rmnh007/DEV/MNH-V5-7-1/conf/profile_mesonh-AIX64-MNH-V5-7-1-MPIAUTO-O2
 
 # and examples here :
 
-/workgpfs/rech/mnh/rmnh007/DEV/MNH-V5-1-3/MY_RUN/KTEST/007_16janvier_scandollar
+/workgpfs/rech/mnh/rmnh007/DEV/MNH-V5-7-1/MY_RUN/KTEST/007_16janvier_scandollar
 
 # 
 #  - At CINES on JADE :
@@ -849,11 +914,11 @@ cp -R  007_16janvier_scandollar /.../your_directory
 #
 # use 
 
-. /work/escobar/DEV/MNH-V5-1-3/conf/profile_mesonh-LXifort-MNH-V5-1-3-MPIICE-O2
+. /work/escobar/DEV/MNH-V5-7-1/conf/profile_mesonh-LXifort-MNH-V5-7-1-MPIICE-O2
 
 # and the exemples
 
-/work/escobar/DEV/MNH-V5-1-3/MY_RUN/KTEST/007_16janvier_scandollar
+/work/escobar/DEV/MNH-V5-7-1/MY_RUN/KTEST/007_16janvier_scandollar
 
 #
 #  - At ECMWF on cxa :
@@ -861,11 +926,11 @@ cp -R  007_16janvier_scandollar /.../your_directory
 #
 # use
 
-. /c1a/ms_perm/au5/MNH-V5-1-3/conf/profile_mesonh-AIX64-MNH-V5-1-3-MPIAUTO-O2
+. /c1a/ms_perm/au5/MNH-V5-7-1/conf/profile_mesonh-AIX64-MNH-V5-7-1-MPIAUTO-O2
 
 # and the examples
 
-/c1a/ms_perm/au5/MNH-V5-1-3/MY_RUN/KTEST/007_16janvier_scandollar
+/c1a/ms_perm/au5/MNH-V5-7-1/MY_RUN/KTEST/007_16janvier_scandollar
 
 
 #
@@ -920,34 +985,7 @@ ulimit -s unlimited
 #
 # IX) OPTIONAL COMPILATION
 ===========================
-#
-# a) MNH_NCWRIT for netcdf graphic output file 
-# --------------------------------------------
-#
-#  If you want to use the option of writing directly netcdf file for graphical 
-#  postprocessing ( no restart ) you could compile and use the package
-#  developped by Soline Bielli as exmplained in this mail
-#  http://mesonh.aero.obs-mip.fr/cgi-bin/mesonh_interne/mail2html.cgi?file=2012_12_19_18:35:16
-#  and on this wiki 
-#  http://mesonh.aero.obs-mip.fr/mesonh410/UseNCL
-# 
-# So before any compilation you have to set the MNH_NCWRIT variable
-export MNH_NCWRIT=MNH_NCWRIT
-#
-# and then the configure 
-
-./configure
-
-#
-# after this compile as usually
-#
-
-make
-etc ...
-
-# see d) for cleaning previously version if needed
-
-# b) MNH_FOREFIRE for forefire runs ( external package needed )
+# a) MNH_FOREFIRE for forefire runs ( external package needed )
 # -------------------------------------------------------------
 #
 #  If you want to use coupled(inline) run with FOREFIRE and MESONH
@@ -979,46 +1017,102 @@ git clone -b 2014.01 https://github.com/forefireAPI/firefront.git
 # or move/linked to the 'exe' directory of MesoNH
 #    
 
-
 # see d) for cleaning previously version if needed
 
-# c) MNH_RTTOV for optional radiative computation
+# b) MNH_RTTOV for optional radiative computation
 # --------------------------------------
 #
-# The RTTOV package was not included into the open source version of Meso-NH
-# because it needs a licence agrement .
+# The RTTOV 13.2 package was not included into the open source version of Meso-NH
+# because it needs a licence agrement.
 #
-# For already(old) licencied MesoNH users (MNH-4-X version with research licence see here: http://mesonh.aero.obs-mip.fr/mesonh410/UserInformation)
+# Run the 'configure' script preceded with the setting of the MNH_RTTOV variable:
 #
-# the package could be reloaded in this way  
+cd $SRC_MESONH/src/
+export MNH_RTTOV=1
+export VER_RTTOV=13.2
+#
+# Compile the HDF5 library
+#
+make cdf
+#
+# Download the RTTOV package rttov132.tar.xz by following the instructions given on https://nwpsaf.eu/site/software/rttov/
 #
-# - With cvs access
+# Install the RTTOV package rttov132.tar.xz
+cd $SRC_MESONH/src/LIB
+mkdir RTTOV-13.2
+cd RTTOV-13.2
+tar xJf rttov132.tar.xz
+cd build
+edit Makefile.local and set HDF5_PREFIX, FFLAGS_HDF5 and LDFLAGS_HDF5 as shown below
+"
+HDF5_PREFIX  = $(SRC_MESONH)/src/dir_obj${XYZ}/MASTER/NETCDF-${VERSION_CDFF}
+FFLAGS_HDF5  = -D_RTTOV_HDF $(FFLAG_MOD)$(HDF5_PREFIX)/include
+LDFLAGS_HDF5 = -L$(HDF5_PREFIX)/lib64 -lhdf5hl_fortran -lhdf5_hl -lhdf5_fortran -lhdf5 -lsz -laec -lz -ldl
+"
+cd ../src
+../build/Makefile.PL RTTOV_HDF=1
+make ARCH=ifort        # Use Intel "ifort" compiler; other options: gfortran, NAG, pgf90, IBM
 #
+# And then for the Meso-NH compilation, do
+#
+cd $SRC_MESONH/src/
+make
 
-cd MNH.../src/LIB
-cvs up -rPACK-MNH-V4-10-3 -d -P RTTOV
+# c) MNH_ECRAD for optional compilation of new ECRAD radiative library from ECMWF 
+# --------------------------------------
+#
+# The default version of ECRAD is 1.4.0 (open-source)
+#
+# Configure & Compilation
+export MNH_ECRAD=1
+./configure
 
+etc ...
+# The version of ECRAD is set by (by default):
+# export VER_ECRAD=140
 #
-# - With WEB access (with WEB login/pass as usually) the RTTOV package could also be retrieve in tarball with wget like this:
+# To use the previous version 1.0.1:
 #
+# The full ECRAD package 1.0.1  was not included into the open source version of Meso-NH
+# because it needs a licence agrement.
+#
+# See here to get the licence & full sources : https://software.ecmwf.int/wiki/display/ECRAD/ECMWF+Radiation+Scheme+Home
+# 
+# REM : some of the files modified for MNH are included in the directory ${SRC_MESONH}/src/LIB/RAD/ecrad-1.0.1_mnh
+# 
+# Install the ECRAD package ecrad-1.0.1.tar.gz in the MNH tree directory
+
+cd ${SRC_MESONH}/src/LIB/RAD
+tar xvfz ecrad-1.0.1.tar.gz
 
-cd MNH.../src/LIB
-wget --http-user=USER  --http-password=PASS 'http://mesonh.aero.obs-mip.fr/cgi-bin/mesonh_interne/viewcvs.cgi/MNH-VX-Y-Z/src/LIB/RTTOV/?view=tar&pathrev=PACK-MNH-V4-10-3' -O RTTOV.tar.gz
-tar xvfz RTTOV.tar.gz
+# Configure & Compilation
+export MNH_ECRAD=1
+export VER_ECRAD=101
+./configure
 
-# /!\ don't forget the ''.  Otherwise, this will not work!
+etc ...
 
 #
-# And then for the compilation, run the 'configure' script preceded with the setting of the MNH_RTTOV variable:
+# REM : the 'profile_mesonh...' file & the 'dir_obj...' directory will be suffixed with an ECRAD extension 
 #
-
-cd MNH.../src/
-export MNH_RTTOV=1
+#  Usage :
+#   1) In namelist replace RAD='ECMW' by RAD='ECRA' 
+#   2) Add link to all 'ecrad-1.X.X/data' files in your mesonh run directory
+ln -sf ${SRC_MESONH}/src/LIB/RAD/ecrad-1.X.X/data/* .
+#
+# REM : you can replace CDATADIR = "." by CDATADIR = "data" of ini_radiations_ecrad.f90 to link only the data folder instead of all the files one by one
+#
+# See 007_16janvier/008_run2 test case for example
+#
+# d) MNH_MEGAN for optional compilation of MEGAN code 
+# --------------------------------------
+#
+# Configure & Compilation
+export MNH_MEGAN=1
 ./configure
 
 etc ...
-
-# d) cleaning previous compiled version
+# e) cleaning previous compiled version
 # --------------------------------------
 #
 # If you have already compiled exactly the same version of MesoNH on this computer ( same $XYZ value )

LIBTOOLS/LIBTOOLS_CVS.TXT

+Libtools sources may be retrieved with the following commands.
+Choose a working directory to install the sources, then
+
+- To get the latest stable revision :
+
+         cvs co libtools
+
+- To get the latest development release :
+
+         cvs co -r LIBTOOLS-DEVEL-branch libtools
+
+- To get the latest CNRM development release :
+
+         cvs co -r LIBTOOLS-CNRM-branch libtools
+
+- to get the LIBTOOLS-DEVEL-1-0-2 release :
+   
+         cvs co -r LIBTOOLS-DEVEL-1-0-2 libtools
+
+
+
+
+Tags that may appear in this repository are explained below :
+
+       MAIN
+       ====
+        |               LIBTOOLS-DEVEL-branch              LIBTOOLS-CNRM-branch
+        |               =====================              ====================
+        |                         |                                 |
+        |                         |                                 |
+ LIBTOOLS-1-0-0 ------------------+---------------------------------+
+        |                         |                                 |
+        |                         |                                 |
+        |                         |                                 |
+        |                   DEV-SURC-7-4-1                          |
+        |                         |                                 |
+        |                         |                                 |
+        |                  DEV-SURC-7-4-1-1                         |
+        |                         |                                 |
+        |                         |                                 |
+        |                  DEV-SURC-7-4-1-2                         |
+        |                         |                                 |
+        |                         |                                 |
+        |                LIBTOOLS-DEVEL-1-0-1                       | 
+        |                         |                                 |
+        |                         |                                 |
+        |                         |                                 |
+        |                LIBTOOLS-DEVEL-1-0-2     merge             | 
+        |             merged_from_DEVEL_to_CNRM ---------> LIBTOOLS-CNRM-1-0-2
+        |                         |                                 |
+        .                         .                                 .
+        .                         .                                 .
+        .                         .                                 .
+
+
+
+Branch TAGS
+===========
+
+   MAIN : this branch contains official stable LibTools sources.
+  
+   LIBTOOLS-DEVEL-branch : this branch contains sources currently under 
+                           development that sooner or later are merged to
+                           main branch.
+
+   LIBTOOLS-CNRM-branch : this branch is reserved to CNRM development/tests.
+                          Sources may be merged to MAIN or LIBTOOLS-DEVEL-branch
+                          branch.
+
+
+Release TAGS
+============
+
+LIBTOOLS-x-y-z : this tag is applied to all sources of a stable LIBTOOLS release
+                 on the MAIN branch.
+
+LIBTOOLS-DEVEL-x-y-z : this tag is applied to all sources of a development LIBTOOLS 
+                       release on the LIBTOOLS-DEVEL-branch development branch.
+
+DEV-SURC-x-y... : this tag is only applied to the lib/SURCOUCHE sources on the
+                  LIBTOOLS-DEVEL-branch development branch.
+
+LIBTOOLS-CNRM-x-y... : this tag is applied to all sources of a development/test LIBTOOLS 
+                       release on the LIBTOOLS-CNRM-branch development branch.
+
+Note that all sources from LIBTOOLS-DEVEL-1-0-2 and LIBTOOLS-CNRM-1-0-2 release
+are strictly identical (except maybe for the README.TXT file).

LIBTOOLS/README.TXT

+Release tag : LIBTOOLS-CNRM-4-8-a  on September 24 2009
+
+Welcome to MESONH Libtools...
+
+Branch : LIBTOOLS-CNRM-branch
+TAG    : $Name$
+
+
+Support for gfortran ver > 4.3 and NCL/NCAR 5.1.1
+with :
+
+export ARCH=LXgfortran
+
+Documentation can be found in 'readme' directory.
+
+LaTeX sources of documentation can be found in 'readme/LATEX'
+directory : type make in the LATEX directory to build the 
+postscript documentation file : tools.ps
+
+
+How to compile ?
+
+ cd lib
+ export ARCH=LXgfortran
+ make COMPRESS
+ make NEWLFI
+ make SURCOUCHE
+ make MPIvide
+ make RAD2
+ make vis5d
+ cd gribex_1302b
+ export ARCH=linux
+ export CNAME=_gfortran
+ export A64=A64
+ make
+ 
+ cd ../../tools
+ cd diachro
+ export ARCH=LXgfortran
+ export MNH_LIBTOOLS= absolute path for libtools directory
+ make
+# The executables are in the directory LXgfortran_64 conv2dia and LXgfortran_32 for the others
+
+
+ cd ../fmmore
+ make
+
+# The executable is in the directory LXgfortran_64
+
+ cd ../lfiz
+ make
+
+# The executables ate in the directory LXgfortran
+

LIBTOOLS/conf/config.AIX32

+CPP = cc -C -E
+AR  = ar 
+F77 = xlf90 -q32 -qextname
+F90 = xlf90 -q32 -qextname
+F77FLAGS = -qfixed -O3 -qstrict
+F90FLAGS = -qfree=f90 -qsuffix=f=f90 -O3 -qstrict
+CPPFLAGS = 
+LDFLAGS = -bloadmap:map_ld

LIBTOOLS/conf/config.AIX64

+CPP = cc -C -E
+AR  = ar -X64
+F77 = xlf90_r -qarch=pwr4 -qzerosize -qautodbl=dbl4 -qmaxmem=-1
+F90 = xlf90_r -qarch=pwr4 -qzerosize -qautodbl=dbl4 -qmaxmem=-1
+F77FLAGS = -q64 -qfixed -O3 -qstrict
+F90FLAGS = -q64 -qfree=f90 -qsuffix=f=f90 -O3 -qstrict
+CFLAGS = -q64 
+CPPFLAGS = 
+LDFLAGS = -q64 -bloadmap:map_ld

LIBTOOLS/conf/config.HPNAGf95

+CPP = /usr/lib/cpp -P -C
+AR = ar
+CC = cc
+F77 = f95
+F90 = f95
+
+F90FLAGS = -f77 -kind=byte -w -mismatch_all
+F77FLAGS = -f77 -kind=byte -w -mismatch_all -dusty
+LDFLAGS  = -unsharedf95
+

LIBTOOLS/conf/config.HPf90

+CPP = /usr/lib/cpp -P -C
+AR  = ar
+F90 = f90 +DAportable
+F77 = f90 +DAportable
+
+CPPFLAGS = -DHP -DF90HP
+F90FLAGS = -w
+F77FLAGS = -w
+
+

LIBTOOLS/conf/config.LXNAGf95

+CPP = cpp -P -traditional -Wcomment
+AR = ar
+CC = cc
+F77 = f95
+F90 = f95
+
+CPPFLAGS = -DNAGf95
+#F90FLAGS = -kind=byte -w -C=all -gline
+F90FLAGS = -kind=byte -w -mismatch_all -gline
+F77FLAGS = -kind=byte -w -mismatch_all -dusty
+LDFLAGS = -unsharedf95 
+

LIBTOOLS/conf/config.LXg95

+CPP = cpp -P -traditional -Wcomment
+AR = ar
+CC = cc 
+F77 = g95
+F90 = g95
+
+CPPFLAGS = -DG95 
+F90FLAGS = -w -fno-second-underscore
+F77FLAGS = -w -fno-second-underscore
+
+LDFLAGS =  
+

LIBTOOLS/conf/config.LXgfortran

+CPP = cpp -P -traditional -Wcomment
+AR = ar
+CC = cc 
+F77 = gfortran
+F90 = gfortran
+
+CPPFLAGS = -DGFORTRAN
+F90FLAGS = -w -fno-second-underscore
+F77FLAGS = -w -fno-second-underscore
+
+LDFLAGS =  
+

LIBTOOLS/conf/config.LXifort

+CPP = cpp -P -traditional -Wcomment
+AR = ar
+CC = cc 
+F77 = ifort
+F90 = ifort
+
+CPPFLAGS = 
+F90FLAGS =
+F77FLAGS =
+
+LDFLAGS =
+

LIBTOOLS/conf/config.LXpgf90

+CPP = cpp -P -traditional -Wcomment
+AR = ar
+CC = cc
+F77 = pgf90
+F90 = pgf90
+
+CPPFLAGS = -Dpgf
+F90FLAGS = -w 
+F77FLAGS = -w 
+LDFLAGS = -Wl,-noinhibit-exec -Wl,-warn-once 
+

LIBTOOLS/conf/config.SGI32

+CPP = /usr/lib/cpp -P -C
+AR  = ar
+F90 = f90
+F77 = f90
+CC  = cc
+
+F90FLAGS = -n32 -w
+F77FLAGS = -n32 -w
+CFLAGS   = -c -O2
+CPPFLAGS =
+LDFLAGS  = -n32
+

LIBTOOLS/conf/config.SGI64

+CPP = /usr/lib/cpp -P -C
+AR  = ar
+F90 = f90
+F77 = f90
+
+F90FLAGS = -64 -w
+F77FLAGS = -64 -w
+CFLAGS   = -64
+CPPFLAGS =
+LDFLAGS  = -64
+

LIBTOOLS/conf/config.SP4Idris

+CPP = cc -C -E
+AR  = ar -X64
+F77 = xlf90_r -qarch=pwr4 -qzerosize -qautodbl=dbl4 -qmaxmem=-1
+F90 = xlf90_r -qarch=pwr4 -qzerosize -qautodbl=dbl4 -qmaxmem=-1
+F77FLAGS = -q64 -qfixed -qsave -O3 -qstrict
+F90FLAGS = -q64 -qfree=f90 -qsuffix=f=f90 -qsave -O3 -qstrict
+CPPFLAGS = 
+LDFLAGS = 

LIBTOOLS/conf/config.SX5

+CPP = /usr/lib/cpp -P -C 
+AR  = sxar
+F90 = sxf90
+F77 = sxf90
+CC  = sxcc
+
+F90FLAGS = -w -Cvsafe
+F77FLAGS = -w -Cvsafe
+
+LDFLAGS = 
+

LIBTOOLS/conf/config.SX8

+CPP = sxcpp -P -C 
+AR  = sxar
+F90 = sxf90
+F77 = sxf90
+CC  = sxcc
+
+F90FLAGS = -w -Cvsafe
+F77FLAGS = -w -Cvsafe
+
+LDFLAGS = 
+

LIBTOOLS/conf/config.VPP

+CPP = /usr/ccs/lib/cpp -P -C
+AR  = ar
+F90 = frt 
+F77 = frt
+F90FLAGS = -X9 -Am -Sw
+F77FLAGS = -Sw
+CPPFLAGS = -DFUJI
+LDFLAGS = 
+