Differences between revisions 7 and 10 (spanning 3 versions)
Revision 7 as of 2020-07-07 14:25:32
Size: 1947
Comment:
Revision 10 as of 2021-09-30 13:42:41
Size: 2162
Comment:
Deletions are marked like this. Additions are marked like this.
Line 25: Line 25:
 * On JURECA load the following modules:  * On JURECA/JUWELS load the following modules:
Line 52: Line 52:

 * In case of development, i,e, small changes in single routines re-compilation could also speeded up by switching off the version control:
 {{{
configure --disable-VCSTAG
make mbm target=clams
 }}}

MESSy/CLaMS: Installation

The MESSy development repository is located on the DKRZ server https://gitlab.dkrz.de/MESSy/MESSy

  • Download the source code:

    To download the MESSy source code from the DKRZ server, one needs an account on this server and access to the repository given by the maintainer Patrick Jöckel (Patrick.Joeckel@dlr.de). For that one needs to create first an account at DKRZ from https://luv.dkrz.de, then join the existing project "853 ESCIMo" and login once into the GitLab server https://gitlab.dkrz.de with the user id defined by the previous process. Then ask Patrick Jöckel to be added to the MESSy project group on the GitLab server. The ssh keys should be uploaded to this GitLab Server.

    Then the source code can be downloaded by:

    git clone git@gitlab.dkrz.de:MESSy/MESSy.git  [target-directory]

    Outgoing ssh communication from JURECA/JUWELS is currently blocked.
    The source code can be downloaded to these systems via https (with userid and password):

    git clone https://gitlab.dkrz.de/MESSy/MESSy.git [target-directory]
    If the MESSy code is already installed by ssh, it is possible to switch the gitlab server access to https by
    git remote set-url origin https://gitlab.dkrz.de/MESSy/MESSy.git
    For access, one needs to use the DKRZ user number and password.
  • On JURECA/JUWELS load the following modules:
    module load intel-para 
    module load netCDF-Fortran
  • On IEK-7-Cluster add the bin subdirectory of the installation directory of MPICH library to your path:
    PATH=/usr/nfs/software/icg1/local/mpich-3.2.1-ifort-18.0.3/bin:$PATH
    export PATH
  • Create and run configure file in messy main directory:

    autoconf
    configure
  • Compile all (in messy main directory):
    make
  • Compile only basemodel CLaMS (in messy main directory):
    make mbm target=clams
  • In case of development, i,e, small changes in single routines re-compilation could also speeded up by switching off the version control:
    configure --disable-VCSTAG
    make mbm target=clams  

messy/Install (last edited 2025-02-06 12:18:55 by NicoleThomas)