Differences between revisions 10 and 21 (spanning 11 versions)
Revision 10 as of 2021-09-30 13:42:41
Size: 2162
Comment:
Revision 21 as of 2025-01-22 12:53:08
Size: 2730
Editor: NicoleThomas
Comment:
Deletions are marked like this. Additions are marked like this.
Line 23: Line 23:
 For access, one needs to use the DKRZ user number and password.  For access, one needs to use the DKRZ user number and password. <<BR>> <<BR>>

 On JUWELS there is '''only a small HOME disk quota'''. Please use the filesystem '''PROJECT''' for source code and applications.<<BR>><<BR>>
Line 27: Line 29:
module load intel-para  module load Intel
module load P
araStationMPI
Line 30: Line 33:

 Information about module usage on '''JSC supercomputers''' can be found [[ https://apps.fz-juelich.de/jsc/hps/juwels/software-modules.html | here ]].
Line 43: Line 48:
 * Compile all (in messy main directory):  * Compile all (in messy main directory), create executable '''bin/echam5.exe''':
Line 45: Line 50:
make make [-j8]
Line 48: Line 53:
 * Compile only basemodel CLaMS (in messy main directory):    * Compile only basemodel CLaMS (in messy main directory), create executable '''bin/clams.exe''' :
Line 50: Line 56:
make mbm target=clams make [-j8] mbm target=clams
Line 53: Line 59:
 * In case of development, i,e, small changes in single routines re-compilation could also speeded up by switching off the version control:     * In case of development, i.e. small changes in single routines, re-compilation could also speeded up significantly by switching off the version control in the configure before (once):
Line 56: Line 64:
make mbm target=clams
Line 58: Line 65:

 * For compilation with debug options run configure with RUNMODE=DEBUG:
 {{{
configure RUNMODE=DEBUG
 }}}

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 JUWELS there is only a small HOME disk quota. Please use the filesystem PROJECT for source code and applications.

  • On JURECA/JUWELS load the following modules:
    module load Intel
    module load ParaStationMPI
    module load netCDF-Fortran

    Information about module usage on JSC supercomputers can be found here.

  • 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), create executable bin/echam5.exe:

    make [-j8]
  • Compile only basemodel CLaMS (in messy main directory), create executable bin/clams.exe :

    make [-j8] mbm target=clams
  • In case of development, i.e. small changes in single routines, re-compilation could also speeded up significantly by switching off the version control in the configure before (once):
    configure --disable-VCSTAG
  • For compilation with debug options run configure with RUNMODE=DEBUG:
    configure RUNMODE=DEBUG

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