README by Josefine Ghattas This directory contains configurations in the same family, having the same suffix v5. Each configuration contains files for compiling : AA_make, AA_make.ldef and for NEMO also the directory scripts. These files are different between the configurations depending on the different models to compile. Each configuration contains also a EXPERIMENTS and a GENERAL directory. All files in these directories, with the same name and path, are the same between all configurations. But all files are not available in all configurations. - In the GENERAL directory are found all files needed for all experiments for a specific configuration. The files are divided into sub-directories DRIVER, PARAM and POST. - In EXPERIMENTS directory are found sub-directories for each experiment. These directories contain the .card files which specifies all in- and output files for the experiment and some parameter set up. *** Some exemples * For a small configuration LMDZREPR_v5, only files concerning LMDZ and REPROBUS are available in the GENERAL directory. In EXPERIMENTS, only experiments possible with LMDZ and REPROBUS are found : LMDZREPR and LMDZ. * In a bigger configuration such as IPSLCM5CHS_v5, more files are found in GENERAL directory. In EXPERIMENTS, all experiments possible with the models included in IPSLCM5CHS_v5 are found : IPSLCM5CHS IPSLCM5 LMDZOR LMDZREPR and LMDZ. * All EXPERIMENTS/LMDZOR/amip experiments are the same in the different configurations BUT this experiment is not available for LMDZREPR_v5 configuration. * The GENERAL/DRIVER/orchidee.driver are the same in all configuration BUT this file does not exist in configuration LMDZREPR_v5. *** How to manage these configurations A user should extract only the configuration concerning what he/she want to simulate. If the user want to do both IPSLCM5 experiements and LMDZOR experiements with the same executable he/she can work with IPSLCM5_v5 configuration and choose different experiements in the EXPERIMENTS directory. Or he/she can extract IPSLCM5_v5 and LMDZOR_v5. An administrator that wants to check-in modifications in a configuration is supposed to extract this whole directory, v5. She/he is then supposed to modify all configurations in the same way and make a global commit in this directory. If there is dought about how a modification will function in the other configurations, the administrator should not do the check-in before verifications have been done. To extract directory v5 containg the corresponding configurations : svn co http://forge.ipsl.jussieu.fr/igcmg/svn/CONFIG/UNIFORM/v5 v5 In this directory some scripts are found to help managing the configurations, as well as this README : * diff_configurations.ksh This script can be used to check if all files are the same in the different configurations. Syntax : ./diff_configurations.ksh * propagate_master_config.ksh This script can be used to copy modifications done in one configuration to all other configurations. The files will be copied only if they exist in both configurations. Syntax : ./propagate_master_config config_to_copy