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.
Changeset 2665 for trunk/NEMOGCM/SETTE – NEMO

Changeset 2665 for trunk/NEMOGCM/SETTE


Ignore:
Timestamp:
2011-03-07T15:42:12+01:00 (13 years ago)
Author:
flavoni
Message:

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

Location:
trunk/NEMOGCM/SETTE
Files:
5 edited

Legend:

Unmodified
Added
Removed
  • trunk/NEMOGCM/SETTE/README

    r2545 r2665  
    11usage of SETTE package: 
    22 
    3 principal script is sette.sh (usage: ./sette.sh) 
     3principal script is sette.sh (usage: ./sette.sh)  
    44 
    55VERY IMPORTANT : for a verbose debug do: 
     
    1818          set_namelist : to set namelist values  
    1919         (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\") 
     20      (      : to change cn_icerst_in name : namelist_ice cn_icerst_in  \"test_00101231_restart_icemod.nc\") 
    2121         (      : to activate control print : namelist ln_ctl \".false.\" ) 
    22                fcm_job.sh needs input: input_CONFIG_NAME and TOTAL NUMBER OF PROCS used 
    23          (for example if you compile ORCA2_LIM with nproci=2 and nprocj=2 ===> ./fcm_job input_ORCA2_LIM.cfg 4) 
     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) 
    2425 in param.cfg : 
    25                EXE_DIR     : directory in which execute jobs (by default CONFIG_DIR) 
    26                FORCING_DIR : directory where to get input tar file 
    27                INPUT_DIR   : directory in which store input files 
    28                TMPDIR      : temporary directory NEEDED ONLY FOR IBM machines (put EXP00 directory) 
    29                OUTPUT_DIR  : directory in which store output files 
     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) 
    3033 in fcm_job.sh : 
    3134               IMPORTANT : control that name of tar file in FORCING directory 
    3235               is the same of that in input_REF_CONFIG.cfg, if not change one. 
    3336               change in "RUN OPA" part the command line (some examples are already written) 
    34  
     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. 
    3540 
    3641NOTE: 
  • trunk/NEMOGCM/SETTE/fcm_job.sh

    r2657 r2665  
    3434# Simple job for SET TESTS for NEMO (SETTE) 
    3535# 
     36# this job creates tree of validation in NEMO_VALIDATION_DIR (choosen in param.cfg) as follows :  
     37# 
     38# NEMO_VALIDATION_DIR/WCONFIG_NAME/WCOMPILER_NAME/TEST_NAME/REVISION_NUMBER(or DATE) 
     39#  
     40# NEMO_VALIDATION_DIR      : is choosen in param.cfg 
     41# 
     42# WCONFIG_NAME       : set by makenemo at the moment of compilation 
     43# 
     44# WCOMPILER_NAME     : set by makenemo at the moment of compilation 
     45# 
     46# TEST_NAME       : convention is LONG=10 days run, SHORT=5 days run 
     47# 
     48# REVISION_NUMBER(or DATE) : revision number by svn info, if problems with svn date is taken 
    3649# 
    3750# EXAMPLES 
     
    4053# :: 
    4154# 
    42 #  $ ./fcm_job.sh INPUT_FILE_CONFIG_NAME       NUMBER_PROC TEST_NAME 
    43 # 
    44 #  run a job of config GYRE with 1 processor          test REPRODUCTINILITY 
    45 #  $ ./fcm_job.sh input_GYRE.cfg                     1    SHORT 
    46 # 
    47 #  run a job of config ORCA2_LIM_PISCES with 8 processors test RESTARTABILITY 
    48 #  $ ./fcm_job.sh input_ORCA2_LIM_PISCES.cfg         8      LONG 
     55#  $ ./fcm_job.sh INPUT_FILE_CONFIG_NAME NUMBER_PROC TEST_NAME 
     56# 
     57#  run a job of config GYRE with 1 processor test REPRODUCTINILITY 
     58#  $ ./fcm_job.sh input_GYRE.cfg 1 SHORT 
     59# 
     60#  run a job of config ORCA2_LIM_PISCES   with 8 processors test RESTARTABILITY 
     61#  $ ./fcm_job.sh input_ORCA2_LIM_PISCES.cfg 8 LONG 
    4962# 
    5063# 
  • trunk/NEMOGCM/SETTE/sette.sh

    r2563 r2665  
    5252# 
    5353#   Temporary directory (if needed) (TMPDIR) 
    54 # 
    55 #   Output files storing (OUTPUT_DIR) 
     54#  
     55#   Validation directory (NEMO_VALIDATION_DIR) 
    5656# 
    5757#   (note: this file is the same for all configrations to be tested with sette) 
    5858# 
    59 #  all_functions.sh : loads functions used by sette (note: new functions can added here) 
     59#  all_functions.sh : loads functions used by sette (note: new functions can be added here) 
    6060# 
    6161#  set_namelist : function declared in all_functions that set namelist parameters for tests 
     
    6363#  fcm_job.sh  
    6464# 
    65 #   runs job and saves output files (ocean.output, solver.stat, grid_files, restart, ice_evolu, ftrace.out) 
     65#   runs job and saves output files (grid_files, restarts, ice_evolu, ftrace.out) 
     66# 
     67#   and it creates tree of VALIDATION, in which there are restart files, solver.stat and ocean.output 
     68# 
     69#   Tree of VALIDATION is: 
     70# 
     71#   NEMO_VALIDATION_DIR/WCONFIG_NAME/WCOMPILER_NAME/TEST_NAME/REVISION_NUMBER(or DATE) 
    6672#  
    67 #   (note this job needs to have an input_CONFIG.cfg in which found tar input file) 
     73#   (note this job needs to have an input_CONFIG.cfg in which can be found input tar file) 
    6874# 
    6975#   (note other files can be saved adding at the end of fcm_job list of saved files) 
     
    7177#  NOTE: if job is not launched for some problems you have executable ready in ${CONFIG_NAME}/EXP00 directory 
    7278# 
    73 #  at the end the directory ${CONFIG_NAME}/EXP00/VALIDATION is created 
    74 # 
    75 #  and output files, solver.stat, ocean.output are put in ${CONFIG_NAME}/EXP00/VALIDATION directory 
    76 # 
    77 #  and restart files and changed namelists are leaved in ${CONFIG_NAME}/EXP00 directory 
     79#  NOTE: the changed namelists are leaved in ${CONFIG_NAME}/EXP00 directory 
    7880#  
    7981#  in ${SETTE_DIR} is created output.sette with the echo of commands run 
  • trunk/NEMOGCM/SETTE/sette_beginner.sh

    r2657 r2665  
    1717#+ 
    1818# 
    19 # ================ 
    20 # sette.sh 
    21 # ================ 
     19# =================== 
     20# sette_beginner.sh 
     21# =================== 
    2222# 
    2323# ---------------------------------------------- 
    24 # Set of tests for NEMO 
     24# Set of tests for NEMO for beginners 
    2525# ---------------------------------------------- 
    2626# 
     
    3030# :: 
    3131# 
    32 #  $ ./sette.sh 
     32#  $ ./sette_beginner.sh 
    3333# 
    3434# DESCRIPTION 
    3535# =========== 
    36 SETTE_DIR=/Users/sflod/nuovo_sette/prova/NEMOGCM/SETTE 
     36# First simple example of how to use SETTE: create GYRE_SHORT configuration, compile it with 1 proc, and test it for a SHORT test: 5days 
     37#- 
     38# 
     39SETTE_DIR=/PATH/OF/SETTE 
    3740# Run for GYRE CONFIG 
    3841# small test to start 
Note: See TracChangeset for help on using the changeset viewer.