|
⇤ ← Revision 1 as of 2018-12-05 08:50:34
Size: 1089
Comment:
|
Size: 1112
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 13: | Line 13: |
| * When running a job script, you have to specify the project name to which the CPU hours are allocated ba adding the line '''#SBATCH --account=jicg11''' (or iek-7) | * When running a job script, you have to specify the project name to which the CPU hours are allocated ba adding the line '''#SBATCH --account=jicg11''' or '''#SBATCH --account=iek-7''' |
New useage model of JURECA
From December 2018 onwards, JURECA has a new usage model.
Details are explained here.
For the projects CLaMS and IEK-7 this means the following changes:
- There are no multiple accounts for the same user
The username for access to JURECA has been changed to <lastname><number> for both projects JICG11 and the ICG1
- the old ssh key should still work
- the old HOME filesystems are now located under /p/project/cjicg11/jicg11xx and /p/project/ciek-7/icg1yy
The ERA-Interim data are now located at /p/fastdata/slmet/slmet111/met_data/ecmwf/era_interim/nc/hybrid/. Note that the access rights still need to be worked out by Lars Hoffmann.
When running a job script, you have to specify the project name to which the CPU hours are allocated ba adding the line #SBATCH --account=jicg11 or #SBATCH --account=iek-7
- CLaMS programs that use e.g. the dynamic NetCDF library need to be re-compield with updated Makefiles / mkincl