Changes between Version 7 and Version 8 of DocUtilisateur/UtilisationAvancée

Timestamp:

05/07/09 10:42:19 (15 years ago)

Author:

mmaipsl

Comment:

--

DocUtilisateur/UtilisationAvancée

@@ -190 +190 @@
 }}}
 
+== Change libIGCM variables "on-the-fly" ==
+Since revision 120, you can change some libIGCM variables (or some of your configuration) during
+a run (and not only after the next submission).
+
+How to do that ? you must copy libIGCM.card from ${libIGCM} directory in you run ${SUBMIT_DIR} directory.
+
+Ater modifications of this '''${SUBMIT_DIR}/libIGCM.card''', variables define inside [User``Changes] will be modified 
+for next Period of libIGCM main loop. 
+Those variables will be updated in the next Period``End stage (see main loop in your job).
+
+Some variables have special treatment in libIGCM_config.ksh : 
+config_UserChoices_Date``End, config_Post_RebuildFrequency, config_Post_TimeSeriesFrequency, config_Post_SeasonalFrequency.
+But you can change other important variables as config_UserChoices_PeriodLength and most of all '''Period``Nb''' (to adapt your
+number of loop PBS options and your real execution duration.)
+
+If you want to change other variable, do it with care !
+
+'''After the first read''' of libIGCM.card, '''you should erase''' or rename it because you don't need to read it again each step. You 
+should change your config.card or job or other cards (depends of your modifications) 
+to have an homogeneous run after next submission.
+
 == Variables IGCM utilisables dans les fichiers pilote ==
 Par défaut les variables du shell ont une portée globale, les fichiers pilotes ont donc accès à l'ensemble des variables définies. Cependant le sous ensemble de variables suivant, non exhaustif, est nécessaire au fonctionnement typique d'un fichier pilote :