1 | README by Josefine Ghattas |
---|
2 | |
---|
3 | This directory contains configurations in the same family, having the same suffix v5. |
---|
4 | |
---|
5 | Each configuration contains files for compiling : AA_make, AA_make.ldef and for |
---|
6 | NEMO also the directory scripts. These files are different between the configurations |
---|
7 | depending on the different models to compile. |
---|
8 | |
---|
9 | Each configuration contains also a EXPERIMENTS and a GENERAL directory. All files in |
---|
10 | these directories, with the same name and path, are the same between all configurations. |
---|
11 | But all files are not available in all configurations. |
---|
12 | |
---|
13 | - In the GENERAL directory are found all files needed for all experiments for a |
---|
14 | specific configuration. The files are divided into sub-directories DRIVER, PARAM and POST. |
---|
15 | |
---|
16 | - In EXPERIMENTS directory are found sub-directories for each experiment. These directories |
---|
17 | contain the .card files which specifies all in- and output files for the experiment |
---|
18 | and some parameter set up. |
---|
19 | |
---|
20 | *** Some exemples |
---|
21 | * For a small configuration LMDZREPR_v5, only files concerning LMDZ and REPROBUS are |
---|
22 | available in the GENERAL directory. In EXPERIMENTS, only experiments possible with LMDZ |
---|
23 | and REPROBUS are found : LMDZREPR and LMDZ. |
---|
24 | |
---|
25 | * In a bigger configuration such as IPSLCM5CHS_v5, more files are found in GENERAL |
---|
26 | directory. In EXPERIMENTS, all experiments possible with the models included in |
---|
27 | IPSLCM5CHS_v5 are found : IPSLCM5CHS IPSLCM5 LMDZOR LMDZREPR and LMDZ. |
---|
28 | |
---|
29 | * All EXPERIMENTS/LMDZOR/amip experiments are the same in the different configurations BUT this |
---|
30 | experiment is not available for LMDZREPR_v5 configuration. |
---|
31 | |
---|
32 | * The GENERAL/DRIVER/orchidee.driver are the same in all configuration BUT this file does not |
---|
33 | exist in configuration LMDZREPR_v5. |
---|
34 | |
---|
35 | |
---|
36 | |
---|
37 | *** How to manage these configurations |
---|
38 | A user should extract only the configuration concerning what he/she want to simulate. If the |
---|
39 | user want to do both IPSLCM5 experiements and LMDZOR experiements with the same executable |
---|
40 | he/she can work with IPSLCM5_v5 configuration and choose different experiements in the |
---|
41 | EXPERIMENTS directory. Or he/she can extract IPSLCM5_v5 and LMDZOR_v5. |
---|
42 | |
---|
43 | An administrator that wants to check-in modifications in a configuration is supposed to |
---|
44 | extract this whole directory, v5. She/he is then supposed to modify all configurations in the |
---|
45 | same way and make a global commit in this directory. If there is dought about how a |
---|
46 | modification will function in the other configurations, the administrator should not do |
---|
47 | the check-in before verifications have been done. |
---|
48 | |
---|
49 | To extract directory v5 containg the corresponding configurations : |
---|
50 | svn co http://forge.ipsl.jussieu.fr/igcmg/svn/CONFIG/UNIFORM/v5 v5 |
---|
51 | |
---|
52 | In this directory some scripts are found to help managing the configurations, as well as |
---|
53 | this README : |
---|
54 | * diff_configurations.ksh |
---|
55 | This script can be used to check if all files are the same in the different configurations. |
---|
56 | Syntax : ./diff_configurations.ksh |
---|
57 | |
---|
58 | * propagate_master_config.ksh |
---|
59 | This script can be used to copy modifications done in one configuration to all other |
---|
60 | configurations. The files will be copied only if they exist in both configurations. |
---|
61 | Syntax : ./propagate_master_config config_to_copy |
---|