Differences between revisions 3 and 24 (spanning 21 versions)

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 ICE4-Cluster machines with Ubuntu 24.04 set the Intel Compiler ifx and add the bin subdirectory of the installation directory of MPICH library to your path:
```
source /opt/intel/oneapi/setvars.sh

PATH=/usr/nfs/software/icg1/local/mpich-4.3.1-ifx-2024.2.0/bin:$PATH
export PATH
```
On ICE4 machines with Ubuntu 20.04 (icg1220) add the bin subdirectory of the installation directory of MPICH library to your path:
```
PATH=/usr/nfs/software/icg1/local/mpich-3.3.2-ifort-19.0.8/bin:$PATH
export PATH
```
Create and run configure file in messy main directory:
```
autoconf
configure
```
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
```
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
```

-  ⇤ ← Revision 3 as of 2019-08-19 11:01:44 → 
  Size: 1426
  Editor: JensUweGrooss
  Comment:
+   ← Revision 24 as of 2025-07-14 09:04:01 → ⇥
  Size: 3060
  Editor: NicoleThomas
  Comment:
-Deletions are marked like this.
+Additions are marked like this.
 Line 7:
- 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:
+ 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. <<BR>><<BR>>

 Then the source code can be downloaded by:
-Line 12:
+Line 14:
+ Outgoing ssh communication from JURECA/JUWELS is currently blocked. <<BR>> 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]
}}}
-Line 13:
+Line 19:
- * On JURECA load the following modules:
+ If the MESSy code is already installed by ssh, it is possible to switch the gitlab server access to https by
-Line 15:
+Line 21:
-module load intel-para
+git remote set-url origin https://gitlab.dkrz.de/MESSy/MESSy.git
}}} 
 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>>

 * On JURECA/JUWELS load the following modules:
 {{{
module load Intel
module load ParaStationMPI
-Line 19:
+Line 34:
- * On IEK-7-Cluster add the bin subdirectory of the installation directory of MPICH library to your path:
+ Information about module usage on '''JSC supercomputers''' can be found [[ https://apps.fz-juelich.de/jsc/hps/juwels/software-modules.html | here ]].

 * On ICE4-Cluster machines with Ubuntu 24.04 set the Intel Compiler ifx and add the bin subdirectory of the installation directory of MPICH library to your path:
-Line 21:
+Line 38:
-PATH=/usr/nfs/software/icg1/local/mpich-3.2.1-ifort-18.0.3/bin:$PATH
+source /opt/intel/oneapi/setvars.sh

PATH=/usr/nfs/software/icg1/local/mpich-4.3.1-ifx-2024.2.0/bin:$PATH
export PATH
}}}

 * On ICE4 machines with Ubuntu 20.04 (icg1220) add the bin subdirectory of the installation directory of MPICH library to your path: 
 {{{
PATH=/usr/nfs/software/icg1/local/mpich-3.3.2-ifort-19.0.8/bin:$PATH
-Line 31:
+Line 56:
- * Compile all (in messy main directory):
+ * 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 33:
+Line 58:
-make
+configure --disable-VCSTAG
 }}}

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


 * Compile all (in messy main directory), create executable '''bin/echam5.exe''':
 {{{
make [-j8]
-Line 36:
+Line 72:
- * Compile only basemodel CLaMS (in messy main directory):
+   * Compile only basemodel CLaMS (in messy main directory), create executable '''bin/clams.exe''' :
-Line 38:
+Line 75:
-make mbm target=clams
+make [-j8] mbm target=clams
-Line 40:
+Line 77: