Changes between Version 65 and Version 66 of Doc/Setup


Ignore:
Timestamp:
10/11/19 15:18:09 (4 years ago)
Author:
falletti
Comment:

Section about ensembles: link to a specific page.

Legend:

Unmodified
Added
Removed
Modified
  • Doc/Setup

    v65 v66  
    612612# Prepare ensembles with ins_job -e # 
    613613 
    614 To create an ensemble configuration you need to create an ensemble.card file. 
    615  
    616 '''NOTE''': If you want to do create ensemble with IPSLCM6 model, you need to create your own ensemble.card (no EXPERIMENT template is available yet). 
    617  
    618  
    619 When IPSLCM5_v5 is downloaded with ./model IPSLCM5_v5 it will offer the possibility to launch experiments of the decadal type. 
    620 To prepare an ensemble of simulations copy the [#Config.card config.card] and [#Ensemble.card ensemble.card] files from the directory: 
    621 {{{ 
    622 modipsl/config/IPSLCM5_v5/EXPERIMENTS/IPSLCM5/decadal/ 
    623 }}} 
    624 into the directory: 
    625 {{{ 
    626 modipsl/config/IPSLCM5_v5 
    627 }}} 
    628  
    629 Several types of ensemble simulations can be prepared by filling [#Config.card config.card] and more importantly [#Ensemble.card ensemble.card]. 
    630 All parameters for ensemble description are in [#Ensemble.card ensemble.card] and global simulation template is in the [#Config.card config.card]. 
    631  
    632 ## Usage ## 
    633  
    634 Check that COMP, POST, PARAM and DRIVER directories are present in the experiment folder. 
    635 Once [#Ensemble.card ensemble.card] and [#Config.card config.card] are correctly filled,  to create an ensemble simply type:  
    636        ../../libIGCM/ins_job -e 
    637 This will create all the directories of the ensemble and Qsub.xxx.sh, a shell file containing all command to submit all jobs (!PeriodNb=60 for all simulations). 
    638 The Q clean.PeriodLength/year.xxx.sh are bash files to use  clean_PeriodLength.job or clean_latestPackperiod.job script for all simulations.[[BR]][[BR]] 
    639 NOTE: If a directory exists, ins_job won't modify it. If only some directories of  the ensemble are presents, it will create the missing ones and complete Qsub.xxx.sh shell file. 
    640  
    641  
    642 ## Config.card ## 
    643  
    644 The file ''config.card'' is filled as a regular ''config.card'' ('''`ins_job`''' without the -e option). 
    645 It will be used as a template for all simulations that will be created. 
    646  
    647 The important lines for the ensemble set up are in the [!UserChoices] section. Make sure that !JobName and !ExperimentName are filled with proper values.[[BR]] 
    648 The variables !DateBegin and !DateEnd will be overidden by variables present in [#Ensemble.card ensemble.card]. 
    649 {{{ 
    650 #D-- UserChoices - 
    651 [UserChoices] 
    652 #============================ 
    653 JobName=v3h4testB 
    654 #----- Short Name of Experiment 
    655 ExperimentName=v3h4testB 
    656 #----- DEVT TEST PROD 
    657 SpaceName=DEVT 
    658 LongName="IPSLCM5A CMIP5 DEVT phase decadal example with limited outputs." 
    659 TagName=IPSLCM5A 
    660 #D- Choice of experiment in EXPERIEMENTS directory 
    661 ExpType=IPSLCM5/decadal 
    662 #============================ 
    663 #-- leap, noleap, 360d 
    664 CalendarType=noleap 
    665 #-- Experiment dates : Beginning and ending 
    666 #-- "YYYY-MM-DD" 
    667 DateBegin=2013-01-01 
    668 DateEnd=2022-12-31 
    669 #============================ 
    670 #-- 1Y, 1M, 5D, 1D Period Length of one trunk of simulation 
    671 PeriodLength=1M 
    672 #============================ 
    673 #-- Total Number of Processors (minimum is 2 for a coupled configuration) 
    674 #JobNumProcTot=4 
    675 JobNumProcTot=32 
    676 }}} 
    677  
    678 A section `[Ensemble]` should also be present. It contains the information that we want to prepare an ensemble simulation with variable !EnsembleRun set to y and three unset fields to be filled in the ''config.card'' of each member after ''''`ins_job -e`''' has run. 
    679 {{{ 
    680 [Ensemble] 
    681 #D- Ensemble run ? 'y' or 'n' 
    682 #D- If 'y', fill in ensemble.card !! 
    683 EnsembleRun=y 
    684 EnsembleName= 
    685 EnsembleDate= 
    686 EnsembleType= 
    687 }}} 
    688  
    689 ## Ensemble.card ## 
    690  
    691 There are several sections in ''ensemble.card'': 
    692 `[Ens_PARAMETRIC]`, `[Ens_DATE]` and `[Ens_PERTURB]`. 
    693  
    694 The choice of ensemble types is done by setting the variable `active` to ''y'' or ''n''. 
    695 {{{ 
    696 [Ens_PERTURB] 
    697 # active=y to use this ensemble type 
    698 active=y 
    699 }}} 
    700  
    701 There are 3 types of ensembles : 
    702 -       Parametric ensemble which is not implemented yet. 
    703 -       Date restart ensemble which allows to configure simulations starting from different restart dates. 
    704 -       Perturb ensemble which allows to generate members from an initial condition which is perturbed by different means. 
    705  
    706 ## Configure a Date Restart ensemble ## 
    707  
    708 We cover here the section which allows to generate identical simulations excepted the initial restart file. Indeed, the « Date Restart ensemble » was implemented to configure a set of simulations using several restart dates, generally chosen for a particular point (ex : randomly, particular climate oscillation phases, volcanic activity…).[[BR]] 
    709  
    710 In [#Ensemble.card ensemble.card] all configuration items of this ensemble are in `[Ens_DATE]` section.[[BR]] 
    711  
    712 There are 2 types of possible configurations to define restarts dates : a periodic one (give year start / stop and periodicity) or non periodic one (give a list of desired restarts). The second one is recommended because it allows more options.[[BR]] 
    713  
    714 In both cases you must fill the following options : `active`, `NAME`, `LENGTH`, `INITFROM` and `INITPATH`.[[BR]] 
    715  
    716 {{{ 
    717 [Ens_DATE] 
    718 # for using date ensemble, 'n' else. 
    719 active=y 
    720  
    721 # name of the ensemble (used to create root directory) 
    722 NAME= ENSTAMBORA 
    723  
    724 # default length of the simulation for non periodic and duration for all periodic (in Year or Month) 
    725 LENGTH=10Y 
    726  
    727 # Experiment name to find all restart files (and default one for non-periodic) 
    728 INITFROM=v3.historical6 
    729  
    730 # Restart root directory 
    731 INITPATH=/ccc/store/cont003/dsm/p86denv/dmf_import/IGCM_OUT/IPSLCM5A/PROD/historical 
    732 }}} 
    733  
    734 === Periodic start dates === 
    735  
    736 In [#Ensemble.card ensemble.card], it is possible to specify a periodic list of start dates. Restart files will be generated for each member at each date starting from `BEGIN_INIT` to `END_INIT` with a periodicity of `PERIODICITY`, using `BEGIN_RESTART` as first restart. Leave all ''NON_PERIODIC'' options empty (`NONPERIODIC`, `RESTART_NONPERIODIC`, `INITFROM_NONPERIODIC`,  `LENGTH_NONPERIODIC`).[[BR]] 
    737  
    738 The following part of [#Ensemble.card ensemble.card] sets 10 years simulations from 1990-01-01 to 2000-01-01 every 2 years each with a restarts starting from 1814-12-31 every 2 years: 
    739  
    740 {{{ 
    741 # start date of the first periodic simulation  
    742 BEGIN_INIT=19900101 
    743  
    744 # start date of the last periodic simulation 
    745 END_INIT=20000101 
    746  
    747 # duration between the start of 2 periodic simulations 
    748 PERIODICITY=2Y 
    749  
    750 # date for the first restart (next = first+periodicity). CAUTION of the calendar (use config.card one)! 
    751 BEGIN_RESTART=18141231 
    752 }}} 
    753  
    754 This will produce simulations starting at the dates : 1990-01-01, 1992-01-01, 1994-01-01, 1996-01-01, 1998-01-01, 2000-01-01. (`PERIODICITY` can be given in months for shorter periods).[[BR]] 
    755  
    756 The restart files are taken from `BEGIN_RESTART` every `PERIODICITY` step : 1814-12-31, 1816-12-31, 1818-12-31, etc...[[BR]] 
    757  
    758 The directory in which the start date is retrieved is given by `INITPATH` and `INITFROM`.[[BR]] 
    759  
    760 To restart from experiment ''v3.historical6'' in directory ''/ccc/store/cont003/dsm/p86denv/dmf_import/IGCM_OUT/IPSLCM5A/PROD/historical'' fill: 
    761  
    762 {{{ 
    763 # Restart name  
    764 INITFROM= v3.historical6  
    765  
    766 # Restart directory 
    767 /ccc/store/cont003/dsm/p86denv/dmf_import/IGCM_OUT/IPSLCM5A/PROD/historical 
    768 }}} 
    769  
    770 '''CAUTION''': The variable !CalendarType from ''config.card'' will be used to determine the next restart date. It should be consistent with the simulations from which you are initialising. 
    771  
    772  
    773  
    774 === Non-Periodic start dates === 
    775  
    776 In [#Ensemble.card ensemble.card], it is also possible to specify manually all simulations running and restart dates, length, experiment names and directories to get restart files.[[BR]] 
    777  
    778 First, you need to left empty the periodic attributes `BEGIN_INIT`, `END_INIT`, `PERIODICITY` and `BEGIN_RESTART` in [#Ensemble.card ensemble.card]. Then you can list the start date of all simulations with `NONPERIODIC` variable, all restart dates with `RESTART_NONPERIODIC` one, all experiments to get restart files in `INITFROM_NONPERIODIC`, all simulations restart path using `INITPATH_NONPERIODIC` and give the length of each simulation (`LENGTH_NONPERIODIC`).[[BR]] 
    779  
    780 Here is an example of a configuration : 
    781  
    782 {{{ 
    783 # list of start dates for all simulations 
    784 NONPERIODIC=(18150101 19910101 19990101) 
    785  
    786 # list of corresponding restart dates 
    787 RESTART_NONPERIODIC=(18141230 19901230 19981231) 
    788  
    789 # simulation name to restart for each simulation. IF empty all simulations will use INITFROM one. 
    790 INITFROM_NONPERIODIC=( v3.historical6 v3.historical6 v5.historical1) 
    791  
    792 # directory of the restart for each simulation. IF empty all simulations will use INITPATH one. 
    793 INITPATH_NONPERIODIC= ( path/to/1st path/to/2nd path/to/3rd ) 
    794  
    795 # length of each simulation. If empty all simulations duration will be the default LENGTH option. 
    796 LENGTH_NONPERIODIC=(10Y 10Y 50Y) 
    797 }}} 
    798  
    799 {{{ 
    800 #!html 
    801 <span style="border: solid 1px #000000; padding: 5px; font-weight: bold;"><span style="color: #ff0000">WARNING:</span> For list variables, use blank between values (no coma).</span> 
    802 }}} 
    803  
    804  
    805 This will produce 3 simulations which starting at the dates : 1815-01-01, 1990-01-01 and 1999-01-01using respectively restarts from 1814-12-30, 1990-12-30, 1998-12-31 (note that the calendar should be different from the [#Config.card config.card] one) taking into ''v3.historical6'' experiment for the 2 firsts and from ''v5.historical1'' for the last one (`INITFROM` is ignored when `INITFROM_NONPERIODIC` is filled). Restarts will be taken respectively in the 3 directories specified with `INITPATH_NONPERIODIC` (`INITPATH` is ignored when `INITPATH_NONPERIODIC` is filled). Simulations length will be 10 years for the 2 firsts and 50 years for the last one. All restart experiments should be in the directory ''/ccc/store/cont003/dsm/p86denv/dmf_import/IGCM_OUT/IPSLCM5A/PROD/historical.''[[BR]] 
    806  
    807 Notice that `INITFROM_NONPERIODIC`, `LENGTH_NONPERIODIC` and `INITPATH_NONPERIODIC` are not mandatory for non-periodic configuration. If you don’t fill one of them or all the `INITFROM` value and/or `LENGTH` value and/or `INITPATH` will be used for all simulations : 
    808  
    809 {{{ 
    810 # default length of the simulation for non periodic and duration for all periodic (in Year or Month) 
    811 LENGTH=10Y 
    812 […] 
    813  
    814 # list of start dates for all simulations 
    815 NONPERIODIC=(18150101 19910101 19990101) 
    816  
    817 # list of corresponding restart dates 
    818 RESTART_NONPERIODIC=(18141230 19901230 19901231) 
    819  
    820 # simulation name to restart for each simulation. IF empty all simulations will use INITFROM one. 
    821 INITFROM_NONPERIODIC= 
    822  
    823 # length of each simulation. IF left empty all simulations durations will be the default LENGTH option. 
    824 LENGTH_NONPERIODIC= 
    825  
    826 # directory of the restart for each simulation. IF empty all simulations will use INITPATH one. 
    827 INITPATH_NONPERIODIC= 
    828  
    829 # Restart name  
    830 INITFROM= v3.historical6  
    831  
    832 # Restart directory 
    833 /ccc/store/cont003/dsm/p86denv/dmf_import/IGCM_OUT/IPSLCM5A/PROD/historical 
    834 }}} 
    835  
    836 This will produce 3 simulations starting at the dates : 1815-01-01, 1990-01-01 and 1999-01-01 using respectively restarts from 1814-12-30, 1990-12-30, 1990-12-31.[[BR]] 
    837 All of them use ''v3.historical6'' experiment in `/ccc/store/cont003/dsm/p86denv/dmf_import/IGCM_OUT/IPSLCM5A/PROD/historical` directory to get restart files and their duration is 10 years. 
    838  
    839  
    840 ## Configure a Perturbed ensemble ## 
    841  
    842 We cover here the section which allows to generate members from an initial condition which is perturbed by different means.[[BR]] 
    843  
    844 There are two ways to perturb the initial condition: 
    845  * apply some random white noise of defined amplitude to the temperature field of the coupler component (CPL) restart file 
    846  * apply some previously generated 3D temperature perturbation map to the temperature field of the ocean component (OCE) restart file 
    847  
    848 Each method applies only to the relevant type of ensemble generation available inside [Ens_PERTURB] as will be explained later. 
    849  
    850 Before detailing the different functionalities available in [Ens_PERTURB] let us discuss the NAME variable.[[BR]] 
    851 This variable will be both the global name of the ensemble (ie directory name) and the prefix for each member: 
    852 {{{ 
    853 # ensemble name 
    854 NAME=v3h4testB 
    855 }}} 
    856  
    857 !JobName variable in `config.card` will be the name of the root directory that would be created containing all config and script files and the ensemble. 
    858  
    859 === Periodic start dates === 
    860  
    861 For this type of perturbed ensembles the following variables are left empty: 
    862 {{{ 
    863 # member list (apply list of pattern to initial state) 
    864 PERTU_MAP_LIST=() 
    865  
    866 # member list of names corresponding to each member 
    867 MEMBER_NAMESLIST=() 
    868  
    869 # member pattern global name 
    870 MEMBER_INITFROM= 
    871  
    872 # member pattern global directory for name 
    873 MEMBER_INITPATH= 
    874 ... 
    875 # start dates list 
    876 NONPERIODIC=() 
    877 # length list for non periodic simulation (NOTE: use length above if not fill) 
    878 LENGTH_NONPERIODIC=() 
    879 ... 
    880 # Path of Mask file 
    881 MASKPATH= 
    882 }}} 
    883  
    884 In [#Ensemble.card ensemble.card], it is possible to specify a periodic list of start dates.[[BR]]  
    885 Restart files will be generated for each member at each date starting from BEGIN_INIT to END_INIT with a periodicity of PERIODICITY.[[BR]] 
    886 The variable MEMBER sets the number of members for each start date. 
    887  
    888 The following part of [#Ensemble.card ensemble.card] sets 10 members from 19900101 to 20000101 every 2 years each lasting 10 years: 
    889 {{{ 
    890 # member nb (i.e nb of perturb initial restart for each date) 
    891 MEMBER=10 
    892 ... 
    893 # periodic and member list simulations length 
    894 LENGTH=10Y 
    895 # start date of the first ensemble 
    896 BEGIN_INIT=19900101 
    897 # start date of the last ensemble 
    898 END_INIT=20000101 
    899 # timestep between each periodic simulation 
    900 PERIODICITY=2Y 
    901 }}}  
    902  
    903 This will produce 10 members starting at the dates : 19900101, 19920101, 19940101, 19960101, 19980101, 20000101. (PERIODICITY can be given in months for shorter periods) 
    904  
    905 Each time the restart file to be perturbed in order to produce each member is taken from the previous day of the start date : 19893112, 19913112, etc... 
    906  
    907 The directory in which the start date is retrieved is given by INITPATH and INITFROM.[[BR]] 
    908 To restart from experiment v3h4BTxx in directory /ccc/store/cont003/gen2211/nguyens/IGCM_OUT/IPSLCM5A/PROD/historical fill: 
    909 {{{ 
    910 # Restart name 
    911 INITFROM=v3h4BTxx 
    912 # Restart directory 
    913 INITPATH=/ccc/store/cont003/gen2211/nguyens/IGCM_OUT/IPSLCM5A/PROD/historical 
    914 }}}  
    915  
    916 The way the perturbed member is generated depends on PERTURB_BIN array. 
    917 The first two elements are the most important. The first one is the executable to be used to produce the members, the second one is the component from which the restart is perturbed. 
    918  
    919 In the Periodic Case it is only possible to build the members by applying a randomly generated temperature pattern on the restart file of the coupler. 
    920 PERTURB_BIN should look like this: 
    921 {{{ 
    922 PERTURB_BIN=(AddNoise, CPL, sstoc, O_SSTSST, 0.1) 
    923 }}} 
    924 The list is interpreted as follows: 
    925  * the used executable is ''!AddNoise'',  
    926  * the component is the coupler (''CPL''),  
    927  * the restart file to perturb contains ''sstoc'' in its name,  
    928  * the variable to perturb in the restart file is ''O_SSTSST'', 
    929  * the randomly generated perturbation is in [-.05;+0.05] degrees 
    930  
    931 '''!!NOTA!! The perturbation is not applied to grid points located under the sea ice. This condition is "hard-written" in the !AddNoise code. Because of a change of the name of the sea ice cover variable from IPSL-CM5A (OIceFrac) and IPSL-CM6 (OIceFrc), a modification of the code has been made by Olivier Marti in June 2016 to allow the code to search for both names''' 
    932  
    933 For each member (in our example we have ten) a new restart file for the coupler will be generated using the executable ''addnoise'' to add some randomly generated temperature perturbation.[[BR]]  
    934 For the year 1990, the corresponding restart file of member 1 will be stored in  
    935 {{{ 
    936 $WORKDIR/IGCM_IN/v3h4testB190/v3h4testB190A/CPL/Restart/ 
    937 }}} 
    938  
    939 === Non-Periodic start dates === 
    940  
    941 For this type of perturbed ensembles the following variables are left empty: 
    942 {{{ 
    943 # member list (apply list of pattern to initial state) 
    944 PERTU_MAP_LIST=() 
    945  
    946 # member list of names corresponding to each member 
    947 MEMBER_NAMESLIST=() 
    948  
    949 # member pattern global name 
    950 MEMBER_INITFROM= 
    951  
    952 # member pattern global directory for name 
    953 MEMBER_INITPATH= 
    954 ... 
    955 # start dates list 
    956 NONPERIODIC=() 
    957 # length list for non periodic simulation (NOTE: use length above if not fill) 
    958 LENGTH_NONPERIODIC=() 
    959 ... 
    960 # start date of the first ensemble 
    961 BEGIN_INIT= 
    962 # start date of the last ensemble 
    963 END_INIT= 
    964 ... 
    965 # Path of Mask file 
    966 MASKPATH= 
    967 }}} 
    968  
    969 The variable LENGTH must be set to something but is not used, PERIODICITY must be set to NONE: 
    970 {{{ 
    971 # periodic and member list simulations length 
    972 LENGTH=10Y 
    973 ... 
    974 # timestep between each periodic simulation (NONE for nonperiodic) 
    975 PERIODICITY=NONE 
    976 }}} 
    977  
    978 To set 10 members for the starting dates 1990 and 1992 for a duration of 10 years, set MEMBER, NONPERIODIC and LENGTH_NONPERIODIC as follows: 
    979 {{{ 
    980 # member nb (i.e nb of perturb initial restart for each date) 
    981 MEMBER=10 
    982 ... 
    983 # start dates list 
    984 NONPERIODIC=(19900101 19920101) 
    985 # length list for non periodic simulation (NOTE: use length above if not fill) 
    986 LENGTH_NONPERIODIC=(10Y 10Y) 
    987 }}} 
    988 This results in 20 simulations in total. 
    989  
    990  
    991 The restart files to be perturbed to produce each member are sought in directory INITFROM which PATH is INITPATH. 
    992 {{{ 
    993 # Restart name 
    994 INITFROM=v3h4BT00 
    995 # Restart directory 
    996 INITPATH=/ccc/store/cont003/gen0826/labetoul/dmf_import/IGCM_OUT/IPSLCM5A/PROD/historical 
    997 }}} 
    998 This will result in using restarts from experiment ''v3h4BT00'' located in directory ''/ccc/store/cont003/gen0826/labetoul/dmf_import/IGCM_OUT/IPSLCM5A/PROD/historical''. 
    999  
    1000 The perturbation executable must be ''!AddNoise''. 
    1001 {{{ 
    1002 PERTURB_BIN=(AddNoise, CPL, sstoc, O_SSTSST, 0.1) 
    1003 }}} 
    1004  
    1005 === List of members for a single start date === 
    1006  
    1007 For this type of perturbed ensembles the following variables are left empty: 
    1008 {{{ 
    1009 # member nb (i.e nb of perturb initial restart for each date) 
    1010 MEMBER= 
    1011 # timestep between each periodic simulation (NONE for nonperiodic) 
    1012 PERIODICITY=NONE 
    1013 # start dates list 
    1014 NONPERIODIC=() 
    1015 # length list for non periodic simulation (NOTE: use length above if not fill) 
    1016 LENGTH_NONPERIODIC=() 
    1017 }}} 
    1018 It is important to leave PERIODICITY set to NONE and LENGTH_NONPERIODIC as an empty list: the list of member method only works for a single start date and neither with periodic start dates nor with non periodic start dates. 
    1019  
    1020 The variables BEGIN_INIT and END_INIT are set to the same date, only BEGIN_INIT will be used to provide the start date of the simulation for each member. 
    1021 {{{ 
    1022 # start date of the first ensemble 
    1023 BEGIN_INIT=20560101 
    1024 # start date of the last ensemble 
    1025 END_INIT=20560101 
    1026 }}} 
    1027  
    1028 The variable LENGTH is the computation time which is the same for all members. 
    1029 {{{ 
    1030 # periodic and member list simulations length 
    1031 LENGTH=10Y 
    1032 }}} 
    1033  
    1034 MEMBER_NAMESLIST is the list of names given to each member. It gives the names of the subdirectories from which the Job is submitted for each member as well as the subdirectories in which the results are stored for each member.  
    1035  
    1036 PERTU_MAP_LIST (previously named as ''MEMBER_LIST'') is the list of perturbation maps files names prefix to apply to the restart file. It is implied that the files are named ''prefix.nc''. 
    1037  
    1038 MEMBER_INITFROM is the directory in which the perturbations maps are stored. 
    1039  
    1040 MEMBER_INITPATH is the path to this directory. 
    1041  
    1042 {{{ 
    1043 # member list of names corresponding to each member 
    1044 MEMBER_NAMESLIST=(OWN3DTA, OWN3DTB, OWN3DTC, OWN3DTD) 
    1045  
    1046 # member list (apply list of pattern to initial state) 
    1047 PERTU_MAP_LIST=(OWN3DT_A, OWN3DT_B, OWN3DT_C, OWN3DT_D) 
    1048  
    1049 # member pattern global directory name 
    1050 MEMBER_INITFROM=OWN3DTpf 
    1051  
    1052 # member pattern global directory for name 
    1053 MEMBER_INITPATH=/ccc/work/cont003/gen2211/nguyens/PERTU/VECTORS 
    1054 }}} 
    1055  
    1056 The variables INITFROM and INITPATH are still used to point to the directory where the restart files including the one to be perturbed are available. 
    1057  
    1058 {{{ 
    1059 # Restart name 
    1060 INITFROM=piControl2 
    1061  
    1062 # Restart directory 
    1063 INITPATH=/ccc/store/cont003/dsm/p86caub/dmf_import/IGCM_OUT/IPSLCM5A/PROD/piControl 
    1064 }}} 
    1065  
    1066 For the member list perturbation type we use the executable AddPertu3DOCE and set PERTURB_BIN this way: 
    1067 {{{ 
    1068 # perturbation type 
    1069 PERTURB_BIN=(AddPertu3DOCE, OCE, restart, tn, ORCA2_mesh_mask.nc) 
    1070 }}} 
    1071 The elements of the list mean: 
    1072  * the executable to be called to generate the perturbation is ''AddPertu3DOCE'' 
    1073  * the component is the Ocean (''OCE'') 
    1074  * the restart file to perturb is ''*restart*.nc'' 
    1075  * the field to perturb in the restart file is ''tn'' 
    1076  * the meshmask file to tell if the gridcell is land or sea is ''ORCA2_mesh_mask.nc'' 
    1077  
    1078 The path to the mesh mask file is given in MASKPATH. 
    1079 {{{ 
    1080 # Path of Mask file 
    1081 MASKPATH=/ccc/cont003/home/gen2211/nguyens/addpertu 
    1082 }}} 
    1083  
    1084 Once [#Config.card config.card] and [#Ensemble.card ensemble.card] properly filled the directories containing the jobs to launch the simulations are created by issuing the command: 
    1085 {{{ 
    1086 ins_job -e # Check and complet job's header 
    1087 }}} 
     614For details about how to generate/use ensemble simulation, please go to its [wiki:Doc/Setup/Ensemble specific page].