Changes between Version 10 and Version 11 of IPSLCM5_v5


Ignore:
Timestamp:
03/13/12 11:36:15 (10 years ago)
Author:
jgipsl
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • IPSLCM5_v5

    v10 v11  
    1 New set up of the coupled model of IPSL. This configuration contains possibility to run IPSLCM5A, IPSLCM5B or IPSLCM5_C 
     1New set up of the coupled model of IPSL. This configuration contains possibility to run IPSLCM5A, IPSLCM5B or IPSLCM5_C and all smaller configurations such as LMDZOR. 
    22 
    33[[PageOutline]] 
    … …  
    66== Extract IPSLCM5_v4 configuration == 
    77To use the configuration IPSLCM5_v4, it is necessary to extract modipsl rev 1618 or later.  
    8 It is also necessary to have libIGCM/trunk rev 541 or later.  
     8It is also necessary to have libIGCM_v1_12 rev 576 or later.  
    99 
    10 Extract using modipsl, same as IPSLCM5A except the configuration name should be IPSLCM5_v4. Change also directory LMDZ4 to LMDZ. And change libIGCM.  
     10Extract using modipsl, same as IPSLCM5A except the configuration name should be IPSLCM5_v4. Change also directory LMDZ4 to LMDZ. 
    1111Add in mod.def : 
    1212{{{ 
    … …  
    2929#-C- IPSLCM5_v4  LMDZ4/branches/LMDZ4_AR5/     1602        11  LMDZ       modeles 
    3030#-C- IPSLCM5_v4  CONFIG/IPSLCM/IPSLCM5_v4      HEAD         8  IPSLCM5_v4 config 
    31 #-C- IPSLCM5_v4  trunk/libIGCM                  541        10  libIGCM    . 
     31#-C- IPSLCM5_v4  tags/libIGCM_v1_12            HEAD        10  libIGCM    . 
    3232#-C- IPSLCM5_v4  branches/CMIP5_IPSL/NEMO      3205         7  .          modeles 
    3333#-C- IPSLCM5_v4  branches/CMIP5_IPSL/UTIL      3205         7  .          modeles 
    … …  
    3838LMDZ5 can also be used, in that case change the line for extraction of LMDZ into : 
    3939{{{ 
    40 #-C- IPSLCM5_v4  LMDZ5/trunk        HEAD        11  LMDZ       modeles 
     40#-C- IPSLCM5_v4  LMDZ5/trunk        1575        11  LMDZ       modeles 
    4141}}} 
    4242 
    … …  
    4747AA_make.ldef 
    4848scripts 
    49 config.card 
    5049GENERAL 
    5150USER_SPEC 
    … …  
    5453The ''AA_make*'' files and the directory ''scripts'' are used for the compiling. These are the same as in IPSLCM5A. There are no differences in compiling compared to IPSLCM5A.[[BR]] 
    5554 
    56 For the running part, there are 2 directories USER_SPEC and GENERAL and one config.card. The directory GENERAL contains the sub-directories POST, PARAM and DRIVERS. The files in GENERAL are used for all types of experiments using this configuration.  
     55For the running part, there are 2 directories USER_SPEC and GENERAL. The directory GENERAL contains the sub-directories POST, PARAM and DRIVERS. The files in GENERAL are used for all types of experiments using this configuration.  
    5756USER_SPEC contains different sub-directories with all cards needed for 5 proposed experiments with IPSLCM5.  
    5857{{{ 
    5958> ls USER_SPEC 
     59LMDZ 
     60LMDZOR 
    6061IPSLCM5 
    6162 
    … …  
    8889 
    8990== How to create a job and run directory == 
    90 Combining the GENERAL directory with one of the sub-directories in USER_SPEC makes a complete run directory.[[BR]] 
    91 The ins_job now contains the creation of such a run directory. The config.card in the directory IPSLCM5_v4, beside the GENERAL and USER_SPEC directory has to be edited. A new variable !UserSpec in the section !UserChoices points to the COMP directory of the chosen experiment. For example !UserSpec=IPSLCM5/historical for a historical run. In each of the experiment directories in USER_SPEC/IPSLCM5, config.card are given as example and can be copied. Other variables in config.card are modified as usual. [[BR]] 
     91Combining the GENERAL directory with one of the sub-directories in USER_SPEC makes a complete run directory. The ins_job contains the creation of such a run directory. [[BR]] 
    9292 
    93 While running ins_job, if a config.card found beside a GENERAL and a USER_SPEC directory, then the creation of a new run directory will be done. The directory GENERAL will be copied into a directory with same name as !JobName in config.card. Then according to the variable !UserSpec, a specific COMP directory in USER_SPEC will be copied into the new run directory. Finally the config.card will be copied in the run directory.  [[BR]] 
     93Choose in USER_SPEC the experiment to be done and copy the corresponding config.card to modipsl/config/IPSLCM5_v4/. Modify the config.card as usual, for at least the !JobName. Apply ins_job and the creation of a new run directory will be done :[[BR]] 
     94 
     95 
     96- the run directory will be created with the same name as !JobName in config.card. If a directory with the same name already exists, nothing will be done.[[BR]] 
     97- the directory GENERAL will be copied into the new run directory[[BR]] 
     98- one of the COMP directories in USER_SPEC will be copied into the new run directory, according to the variable !UserSpec in config.card[[BR]] 
     99- the config.card will be copied into the run directory  [[BR]] 
     100- a job will be created in the run directory[[BR]] 
    94101 
    95102Once the run directory has been created with ins_job, this directory is used as a normal run directory. For example it is possible to remove the job, change the config.card inside the directory and re-create the job with ins_job. To create a second run directory, modify the upper config.card, in IPSLCM5_v4 directory, with at least the !JobName, and re-run ins_job. If a directory with the !JobName already exist, nothing will be done using this config.card. [[BR]]