New URL for NEMO forge!   http://forge.nemo-ocean.eu

Since March 2022 along with NEMO 4.2 release, the code development moved to a self-hosted GitLab.
This present forge is now archived and remained online for history.
README in trunk/NEMOGCM/SETTE – NEMO

source: trunk/NEMOGCM/SETTE/README @ 2665

Last change on this file since 2665 was 2665, checked in by flavoni, 12 years ago

add new functionality in SETTE, creating validation tree, and updated doc, see ticket #752

File size: 3.3 KB
Line 
1usage of SETTE package:
2
3principal script is sette.sh (usage: ./sette.sh)
4
5VERY IMPORTANT : for a verbose debug do:
6./sette.sh 2>&1 | tee out.sette
7this create out.sette file in ${SETTE_DIR}
8
9USER MODIFICATIONS
10 in sette.sh script :
11               SETTE_DIR : base directory for SETTE
12               makenemo -m : machine (compilator); see ./makenemo -m help (in NEMOGCM/CONFIG directory)
13                        -n : config name (in examples config_name_nproci_nprocj), see ./makenemo -n help
14                        -r : reference configuration (if you don't give it you have to choise directories to install)
15                        add_key : to add list of keys (for example to test reproductibility: add_key mpp_rep)
16                        del_key : to del list of keys
17               and for more details and options of makenemo see ./makenemo -h
18          set_namelist : to set namelist values
19         (example : to set 75 time steps for one test : namelist nn_itend 75)
20      (      : to change cn_icerst_in name : namelist_ice cn_icerst_in  \"test_00101231_restart_icemod.nc\")
21         (      : to activate control print : namelist ln_ctl \".false.\" )
22               fcm_job.sh needs input: input_CONFIG_NAME TOTAL_NUMBER_OF_PROCS_used TEST_NAME
23         (for example if you compile ORCA2_LIM with nproci=2 and nprocj=2
24         and only run short test ===> ./fcm_job input_ORCA2_LIM.cfg 4 SHORT)
25 in param.cfg :
26               EXE_DIR           : directory in which execute jobs (by default CONFIG_DIR)
27               FORCING_DIR       : directory where to get input tar file
28               INPUT_DIR         : directory in which store input files
29               TMPDIR            : temporary directory NEEDED ONLY FOR IBM machines (put EXP00 directory)
30               OUTPUT_DIR        : directory in which store output files
31          NEMO_VALIDATION_DIR : directory in which create NEMO_VALIDATION tree, and store restart and solver.stat files in
32                            tree NEMO_VALIDATION_DIR/WCONFIG_NAME/WCOMPILER_NAME/TEST_NAME/REVISION_NUMBER(or DATE)
33 in fcm_job.sh :
34               IMPORTANT : control that name of tar file in FORCING directory
35               is the same of that in input_REF_CONFIG.cfg, if not change one.
36               change in "RUN OPA" part the command line (some examples are already written)
37          TEST_NAME iby convention is LONG: 10 days run or SHORT: 5 days run
38          so NEMO_VALIDATION tree is coherent,
39          but user can choise a TEST_NAME that represent his own test.
40
41NOTE:
42in case of error you can remove you NEW_CONF directory and all files doing :
43./makenemo -n MY_CONFIG clean_config
44
45if you want recompile nemo but before you want to clean compiled code do :
46./makenemo clean
47
48and if you have already compiled you can re-run all sette.sh and compilation part will be by-passed.
49
50NOTE 2:
51if you want a completly verbose makenemo you can uncomment "set -x" in makenemo script
52and then launch ./sette.sh 2>&1 | tee out.sette
53
54TO ADD NEW CONFIGURATION:
551. makenemo -n NEW_CONFIG (see makenemo -h for help) OR
562. makenemo -n NEW_CONFIG -r REF_CONFIG (if it is based on another reference configuration)
573. for fcm_job.sh creates a new input_NEW_CONFIG.cfg if you need tar file (if you use same tar file of GYRE, ORCA2_LIM or ORCA2_LIM_PISCES you can use it)
58
59TO ADD NEW MACHINE:
601. add arch-compiler.fcm in NEMOGCM/ARCH directory
612. makenemo -m new_compiler  (see makenemo -h for help)
Note: See TracBrowser for help on using the repository browser.