Changes between Version 32 and Version 33 of Doc/ComputingCenters/TGCC/Irene


Ignore:
Timestamp:
07/05/18 16:31:15 (6 years ago)
Author:
jgipsl
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Doc/ComputingCenters/TGCC/Irene

    v32 v33  
    9595[[NoteBox(note, If you previously worked at curie and your directories were in /cont003/dsm/login you will now find your data in a specific new project file system "dsmipsl". We recommend to move your data in your genci project file system. The TGCC hotline can help you if you want. , 600px)]] 
    9696 
     97# How the storage project is set by libIGCM # 
     98When you use libIGCM it is recommended to dedicate one modipsl/libIGCM to one project allocation. By default, the output folders IGCM_OUT will be created in the directories $CCCSCRATCHDIR, $CCCWORKDIR and $CCCSTOREDIR corresponding to the project used in the main job. It is important that the same project is used in the post-processing jobs in libIGCM.  
     99 
     100If you need to use another project for the computing than the storage, it is possible to set the variable !DataProject in config.card !UserChoices section, for example !DataProject=gen6328, read more [wiki:DocEsetup#TheUserChoicessection here]. This project will be used for all output directories for the computing job and post-processing jobs even if they have another project for computing in the headers. The variable !DataProject can also be used if you work with different project allocations in the same modipsl. Only exception (harmless) is the first RUN_DIR folder which is always created in the $CCCSCRATCHDIR corresponding to the dfldatadir loaded in when submitting main job. When the job resumbits itself, the RUN_DIR will be in the same project space as the rest of the output.  
    97101 
    98102