source: branches/2011/dev_r2784_INGV2_bulk/NEMOGCM/SETTE @ 2786

Name Size Rev Age Author Last Change
../
all_functions.sh 4.3 KB 2756   10 years flavoni add copy_original function in SETTE to solve pb during re-run tests,… it …
fcm_job.sh 8.9 KB 2687   10 years flavoni add input cfg file for POMME, and move ice_evolu in NEMO_VALIDATION_DIR, …
input_GYRE.cfg 1 bytes 2354   10 years flavoni first draft for SETTE (SET tests for NEMO), a new version of NVTK, see …
input_ORCA2_LIM.cfg 24 bytes 2732   10 years rblod Add a test with AGRIF in sette.sh, just because life is always much more …
input_ORCA2_LIM_PISCES.cfg 24 bytes 2732   10 years rblod Add a test with AGRIF in sette.sh, just because life is always much more …
input_POMME.cfg 20 bytes 2687   10 years flavoni add input cfg file for POMME, and move ice_evolu in NEMO_VALIDATION_DIR, …
param.cfg 364 bytes 2675   10 years flavoni commit sette.sh ready to test 3 reference configuration: GYRE_LOBSTER, …
README 3.6 KB 2757   10 years flavoni … doc follows , see ticket #819
SETTE.pdf 86.1 KB 2757   10 years flavoni … doc follows , see ticket #819
sette.sh 13.3 KB 2756   10 years flavoni add copy_original function in SETTE to solve pb during re-run tests,… it …
sette_beginner.sh 1.9 KB 2754   10 years flavoni small changes for SETTE tests, see ticket #752

README

usage of SETTE package:

principal script is sette.sh (usage: ./sette.sh) 

VERY IMPORTANT : for a verbose debug do:
./sette.sh 2>&1 | tee out.sette
this create out.sette file in ${SETTE_DIR}

USER MODIFICATIONS
 in sette.sh script :
               COMPILER    : compiler among those available in NEMOGCM/ARCH, needed for makenemo (see below)
                             can also be pass as an argument, e.g. ./sette.sh ifort_osx
               makenemo -m : machine (compilator); see ./makenemo -m help (in NEMOGCM/CONFIG directory)
                        -n : config name (in examples config_name_nproci_nprocj), see ./makenemo -n help
                        -r : reference configuration (if you don't give it you have to choise directories to install)
                        add_key : to add list of keys (for example to test reproductibility: add_key mpp_rep)
                        del_key : to del list of keys
               and for more details and options of makenemo see ./makenemo -h
          set_namelist : to set namelist values 
         (example : to set 75 time steps for one test : namelist nn_itend 75)
         (        : to change cn_icerst_in name : namelist_ice cn_icerst_in  \"test_00101231_restart_icemod\")
         (      : to activate control print : namelist ln_ctl false )
          copy_original : to namelist of reference configuration in configuration directory in which tests are done
               fcm_job.sh needs input: input_CONFIG_NAME TOTAL_NUMBER_OF_PROCS_used TEST_NAME
         (for example if you compile ORCA2_LIM with key_mpp_mpi 
         and only run short test ===> ./fcm_job input_ORCA2_LIM.cfg 4 SHORT)
 in param.cfg :
               EXE_DIR           : directory in which job s executed (by default CONFIG_DIR)
               FORCING_DIR       : directory in which will be found input.tar file (same name in input_CONFIG_NAME.cfg)
               INPUT_DIR         : directory in which store input files
               TMPDIR            : temporary directory NEEDED ONLY FOR IBM machines (put EXP00 directory)
               OUTPUT_DIR        : directory in which store output files
          NEMO_VALIDATION_DIR : directory in which create NEMO_VALIDATION tree, and store restart, solver.stat and ocean.output files in
                            tree NEMO_VALIDATION_DIR/WCONFIG_NAME/WCOMPILER_NAME/TEST_NAME/REVISION_NUMBER(or DATE)
 in fcm_job.sh :
               IMPORTANT : control that name of tar file in FORCING directory
               is the same of that in input_REF_CONFIG.cfg, if not change one.
               change in "RUN OPA" part the command line (some examples are already written)
          TEST_NAME by convention is LONG: 10 days run or SHORT: 5 days run
          so NEMO_VALIDATION tree is coherent,
          but user can choise a TEST_NAME that represent his own test.

NOTE:
in case of error you can remove you NEW_CONF directory and all files doing :
./makenemo -n MY_CONFIG clean_config

if you want recompile nemo but before you want to clean compiled code do :
./makenemo clean

and if you have already compiled you can re-run all sette.sh and compilation part will be by-passed.

NOTE 2: 
if you want a completly verbose makenemo you can uncomment "set -x" in makenemo script
and then launch ./sette.sh 2>&1 | tee out.sette

TO ADD NEW CONFIGURATION:
1. makenemo -n NEW_CONFIG (see makenemo -h for help) OR
2. makenemo -n NEW_CONFIG -r REF_CONFIG (if it is based on another reference configuration)
3. 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)

TO ADD NEW MACHINE:
1. add arch-compiler.fcm in NEMOGCM/ARCH directory
2. makenemo -m new_compiler  (see makenemo -h for help)
Note: See TracBrowser for help on using the repository browser.