Changes between Version 62 and Version 63 of Doc/ComputingCenters/TGCC/Irene
- Timestamp:
- 10/11/19 16:49:47 (5 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Doc/ComputingCenters/TGCC/Irene
v62 v63 6 6 [[PageOutline(1-3,Table of contents,,numbered)]] 7 7 8 Last update 05/07/20189 10 8 # Introduction # 11 9 * On-line users manual: https://www-tgcc.ccc.cea.fr/docs/irene.info.pdf (you will need a TGCC login and password) 12 * Irene computing nodes: the nodes of partition '''skylake''' have 48 cores each , which is 3 times more than the computing nodes from the standard partition of Curie.10 * Irene computing nodes: the nodes of partition '''skylake''' have 48 cores each. 13 11 * Skylake nodes for regular computation (coming from irene.info) 14 12 * Partition name: '''skylake''' … … 21 19 * When submitting a job through ccc_msub or ccc_mprun, you must specify -m work, -m scratch, -m store, or combine them like in -m work,scratch. This constraint has the advantage that your jobs won't be suspended if a file system you don't need becomes unavailable. This is done in all jobs in libIGCM. 22 20 * Compute nodes are diskless, meaning that /tmp is not hosted on a local hard drive anymore, but on system memory instead. It offers up to 16 GB (compared to 64 GB on Curie). Please note that any data written to it is reduces the size of the memory that remains available for computations. For libIGCM post-treatment jobs you might need to use more cores than used at curie or, preferably, use xlarge nodes. 23 * The default time limit for a job submission is 2 hours (7 200 s) contrary to 24 h (86 400 s) on curie21 * The default time limit for a job submission is 2 hours (7 200 s). 24 22 * Irene post-processing nodes : xlarge are free and useful for post-processing operations. Since 2018/10/17 and libIGCM 1470, xlarge is proposed as default post-processing node. 25 23 * Fat nodes for computation requiring a lot of shared memory (coming from irene.info) 26 * Partition name: '' Xlarge'''24 * Partition name: ''xlarge''' 27 25 * CPUs: 4x28-cores Intel Skylake@2.1GHz 28 26 * GPUs: 1x Nvidia Pascal P100 … … 47 45 Before working on Irene you need to prepare your environment. This is important to do before compilation to ensure the use of same modules as done by libIGCM running environment. We propose you 2 files which you can copy from the home igcmg. The first one called '''bashrc''' will source the second called '''bashrc_irene'''. Copy both files to your home, rename them by adding a dot as prefix. You can add personal settings in your .bashrc_irene. Do as follow: 48 46 {{{ 49 cp /ccc/cont003/home/igcmg/igcmg/MachineEnvironment/irene/bashrc ~/.bashrc50 cp /ccc/cont003/home/igcmg/igcmg/MachineEnvironment/irene/bashrc_irene ~/.bashrc_irene47 cp ~igcmg/MachineEnvironment/irene/bashrc ~/.bashrc 48 cp ~igcmg/MachineEnvironment/irene/bashrc_irene ~/.bashrc_irene 51 49 }}} 52 50 The .bashrc will source your own .bashrc_irene which must be in your home. … … 66 64 9) feature/mkl/sequential 18) mpi/openmpi/2.0.2 27) ferret/7.2(default) 67 65 }}} 68 The modules are specified in the file /ccc/cont003/home/igcmg/igcmg/MachineEnvironment/irene/env_irene which is sourced in bashrc_irene. The same file env_irene is sourced in libIGCM.66 The modules are specified in the file ~igcmg/MachineEnvironment/irene/env_irene which is sourced in bashrc_irene. The same file env_irene is sourced in libIGCM. 69 67 70 68 --> Be careful this environment can be update during next weeks according to TGCC recommendations … … 111 109 112 110 '''On the SCRATCH space any files that stays 60 days without being read or modified will be purged(deleted), as well as any directory that remains empty for 30 days.''' 113 114 115 111 116 112 After connexion to irene, load your project environment as default using the module dfldatadir. For example if you will work on the project gen2201, do following (we suggest you to add the command into your .bashrc_irene):
