Changes between Version 22 and Version 23 of IPSLCM5_v5
- Timestamp:
- 05/31/12 16:36:06 (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
IPSLCM5_v5
v22 v23 1 New 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. 1 = New configuration family v5 = 2 3 New set up of the coupled models of IPSL : IPSL-CM5, LMDZOR, LMDZORINCA. Available configurations are : 4 * IPSLCM5_v5 contains possibility to run IPSLCM5A, IPSLCM5B or IPSLCM5_C and all smaller configurations such as LMDZOR and LMDZ. 5 * LMDZORINCA_v5 contains possibility to run LMDZORINCA, LMDZOR or LMDZ (and maybe LMDZINCA later) 6 * LMDZOR_v5 contains possibility to run LMDZOR or LMDZ 7 * LMDZREPR_v5 contains possibility to run LMDZREPR or LMDZ 2 8 3 9 [[PageOutline]] … … 36 42 }}} 37 43 38 == Contents of the configuration directory IPSLCM5_v4 == 44 45 == Contents of the configuration directory (for exemple IPSLCM5_v5 or LMDZREPR_v5) == 39 46 {{{ 40 47 > ls 41 48 AA_make 42 49 AA_make.ldef 43 scripts 50 scripts - this directory exists only for configuration IPSLCM5_v5 containg NEMO 44 51 GENERAL 45 52 USER_SPEC 46 53 }}} 47 54 48 The '' 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]]55 The '''AA_make*''' files and the directory '''scripts''' are used for the compiling. These are the same as in the old configuration (for exemple IPSLCM5A). There are no differences in compiling compared to the old configurations.[[BR]] 49 56 50 For 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. 51 USER_SPEC contains different sub-directories with all cards needed for 5 proposed experiments with IPSLCM5. 57 For the running part, there are 2 directories : 58 * '''GENERAL'''[[BR]] 59 contains the sub-directories POST, PARAM and DRIVERS. The files in GENERAL are used for all types of experiments using this configuration. 60 * '''USER_SPEC'''[[BR]] 61 contains different sub-directories with all cards needed for all proposed experiments with the configuration. The possible experiments are divided into sub-configurations which contains different experiments. A configuration may contain several sub-configurations. Only sub-configurations and experiements that are possible with the extracted configuration are present in USER_SPEC. 62 63 For exemple for IPSLCM5_v5 : 52 64 {{{ 65 ! Available sub-configurations 53 66 > ls USER_SPEC 67 IPSLCM5 54 68 LMDZ 55 69 LMDZOR 56 IPSLCM557 70 58 > ls USER_SPEC/IPSLCM5 71 ! Available experiments 72 > ls USER_SPEC/* 73 USER_SPEC/IPSLCM5: 59 74 Chistorical 60 75 CpiControl … … 62 77 historical 63 78 piControl 79 80 USER_SPEC/LMDZ: 81 CREATE_amip 82 CREATE_clim 83 clim 84 85 USER_SPEC/LMDZOR: 86 amip 87 clim 64 88 }}} 65 89 … … 86 110 Combining 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]] 87 111 88 Choose in USER_SPEC the experiment to be done and copy the corresponding config.card to modipsl/config/IPSLCM5_v 4/. 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]]112 Choose in USER_SPEC the experiment to be done and copy the corresponding config.card to modipsl/config/IPSLCM5_v5/. 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]] 89 113 90 114 … … 95 119 - a job will be created in the run directory[[BR]] 96 120 97 Once 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_v 4directory, 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]]121 Once 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_v5 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]] 98 122 99 123 == DRIVER directory == … … 101 125 102 126 103 == Remaining questions==127 == PARAM directory == 104 128 How to make clear that a variable in a parameter file might be edited by the drivers ?[[BR]] 129 A new syntax in parameter .def files are used (only for LMDZ and ORCHIDEE for the moment). In .def parameter file set : 130 * varX = _AUTO_ [[BR]] 131 if the variable always is edited 132 * varX = _AUTO_ : DEFAULT=toto[[BR]] 133 if the variable is modified only in some cases, add the a default value 105 134 106 - If the variable always is edited, it is then possible to put in parameter file var=_AUTO_[[BR]] 107 108 - But if a variable only is some cases is modified, then a default value is needed. A possibility might be to decide a syntax for example var=_AUTO_:X where X is the default value. Then before starting the execution all variables that still keeps _AUTO_, the X value must be adapted... 109 135 The drivers must be consistent with the parameter files. The driver must not modify a parameter which is not set as _AUTO_. 110 136 == New functionnality == 111 137 … … 114 140 == To do list == 115 141 116 === Avant fin mai === 142 === Obligatoire avant ouverture et cours === 143 * Vérifier les configurations existant dans mod.def 144 * Choix des noms pour 145 * Changer pour OASIS sous SVN (Arnaud) 146 * VALIDATION : 147 * Validation entre IPSLCM5_v5 et IPSLCM5A 148 * Validation entre LMDZOR_v5 et LMDZOR_v4 149 * Validation de LMDZORINCA_v5 150 * Ajouter option pour modifier les reglages de LMDZ pour un configuration en particulier 151 * DOCUMENTATION dans modispslforBeginners1 et le cours 152 153 === Souhaitable avant le cours === 117 154 * Améliorer ins_job (Sébastien D.) 155 * pour prendre en compte le choix de config.card (pas de copie necessaire) 156 * pour laisser l'utilisateur modifier le JobName et d'autre parametre cle 118 157 * Ajouter dans ins_job option pour MPI/OpenMP (Arnaud) 119 158 * MPI/OpenMP : enlever les parametres obsolètes de config.card liés à l'execution. (Arnaud) 120 * Ajouter dans mod.def les nouveaux configurations 121 * Changer pour ORCHIDEE sous SVN (Josefine) 122 * Changer pour OASIS sous SVN (Arnaud) 159 123 160 * Moyenne résolution : 124 161 * Mettre les fichiers poids sur les comptes commune. Vérifier qu'on pointe sur les bons fichiers pour les différents résolutions. Documenter. (Olivier ?) … … 127 164 * Il faut aussi changer !TagName : IPSLCM5A-MR 128 165 * Il faut réduire les tailles des Chunck dans les POST 166 129 167 * Revoir les variables "auto" dans les namelist NEMO. Dans le driver, éventuellement utiliser le même type de _sed que dans orchidee.driver et lmdz.driver. 130 * Validation entre IPSLCM5_u1 et IPSLCM5A 131 * Documentation dans modispslforBeginners1 132 * Adapter libIGCM pour Curie. Fait dans tag libIGCM_v2_beta1 133 * Mettre le fichier Bands en restart. 168 169 === Plus tard === 170 * Mettre le fichier Bands en restart. Qui ? 134 171 * Avoir un fichier de sortie texte par processeur par défaut 135 172 * Séparer les environnements par défaut : calcul et post-traitement 136 173 * passage à netcdf4? 137 138 === Plus tard ===139 140 174 * Changer environnement de compilation pour NEMO : utiliser NEMO v3_4 avec fcm et allocation dynamique pour le nombre de processus 141 175 * Amélioration dans la gestion des diagnostiques: choix des fichiers, fréquences, time-series,..., simplification et documentation 142 176 * Déterminer si souhaitable d'ajouter NEMO et PISCES offline (Chrisitan) 143 * Ajoute IPSLCM5INCA_u1 (Anne) 177
