Full irene documentation
=========================
https://www-tgcc.ccc.cea.fr/docs/

Environment
===========
* Current project name on irene: **gen7725**
To be mentionned in job scripts and for data modules
* Current Fortan compiler
* Current MPI librairy

File systems
============
4 file systems @TGCC:
* home: small, backed up => source,  software and small data
* work: large and performant, **no back up** => target file system for MW production
* store: huge and slow (tapes), archiving system => pack regularly run results in tarball to limit the number of files there in order to back up data
* scratch: very large and performant, periodic remove of non used files => not relevant for MW production   

```
module switch dfldatadir/gen7725
```
sets for each of these file systems, environment variables for private and shared spaces. For instance, for the work file system:
* ALL_CCCWORKDIR points to the shared space /ccc/work/cont003/gen7725/gen7725 associated to project gen7725
* CCCWORKDIR points to the private space /ccc/work/cont003/gen7725/haefemat of user haefemat associated to project gen7725
=> good practise to load the correct module and use these env variables in your scripts

Testing Metalwalls
==================
In MW git project root directory
```
make mw_tests # compiles the unitary tests 
cp -r tests $CCCWORKDIR 
cd $CCCWORKDIR/tests
ccc_msub $OLDPWD/computers/irene/job_check
```
Check ouptut and error files generated by the job scheduler to check if everything run fine

Job scripts
===========
* job_check: runs the MW tests suite 
* job_prod: typical production run job


