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 5095 for branches/2015/dev_r5092_CNRS_SETTE/NEMOGCM – NEMO

Ignore:
Timestamp:
2015-02-18T16:52:48+01:00 (9 years ago)
Author:
nicolasmartin
Message:

Global reorganisation of directory

Location:
branches/2015/dev_r5092_CNRS_SETTE/NEMOGCM/SETTE
Files:
23 added
17 deleted
1 edited
1 moved

Legend:

Unmodified
Added
Removed
  • branches/2015/dev_r5092_CNRS_SETTE/NEMOGCM/SETTE/README

    r3635 r5095  
    80802. create you own batch file like: batch-${COMPILER} 
    8181(note: sette.sh will copy it in job_batch_template if you run tests in INTERACT_FLAG="no") 
     82 
     83# Variables to be checked by user: 
     84# 
     85# COMPILER          : name of compiler as defined in NEMOGCM/ARCH directory  
     86# BATCH_COMMAND_PAR :  name of the command for submitting parallel batch jobs 
     87# BATCH_COMMAND_SEQ :  name of the command for submitting sequential batch jobs   
     88# INTERACT_FLAG     : flag to run in interactive mode "yes" 
     89#                           to run in batch mode "no" 
     90# MPIRUN_FLAG       : flag to run in parallel (MPI) "yes" 
     91#                           to run in sequential mode (NB_PROC = 1) "no" 
     92# USING_XIOS        : flag to control the activation of key_iomput 
     93#                      "yes" to compile using key_iomput and link to the external XIOS library 
     94#                      "no"  to compile without key_iomput and link to the old IOIPSL library 
     95# USING_MPMD        : flag to control the use of stand-alone IO servers 
     96#                     requires USING_XIOS="yes" 
     97#                      "yes" to run in MPMD (detached) mode with stand-alone IO servers 
     98#                      "no"  to run in SPMD (attached) mode without separate IO servers  
     99# NUM_XIOSERVERS    : number of stand-alone IO servers to employ 
     100#                     set to zero if USING_MPMD="no" 
     101# 
     102# Principal script is sette.sh, that calls  
     103# 
     104#  makenemo  : to create successive exectuables in ${CONFIG_NAME}/BLD/bin/nemo.exe  
     105#              and links to opa in ${CONFIG_NAME}/EXP00) 
     106# 
     107#  param.cfg : sets and loads following directories: 
     108# 
     109#   FORCING_DIR         : is the directory for forcing files (tarfile) 
     110#   INPUT_DIR           : is the directory for input files storing  
     111#   TMPDIR              : is the temporary directory (if needed) 
     112#   NEMO_VALIDATION_DIR : is the validation directory 
     113# 
     114#   (NOTE: this file is the same for all configrations to be tested with sette) 
     115# 
     116#   all_functions.sh : loads functions used by sette (note: new functions can be added here) 
     117#   set_namelist     : function declared in all_functions that sets namelist parameters  
     118#   post_test_tidyup : creates validation storage directory and copies required output files  
     119#                      (solver.stat and ocean.output) in it after execution of test. 
     120# 
     121#  VALIDATION tree is: 
     122# 
     123#   NEMO_VALIDATION_DIR/WCONFIG_NAME/WCOMPILER_NAME/TEST_NAME/REVISION_NUMBER(or DATE) 
     124# 
     125#  prepare_exe_dir.sh : defines and creates directory where the test is executed 
     126#                       execution directory takes name of TEST_NAME defined for every test  
     127#                       in sette.sh. (each test in executed in its own directory) 
     128# 
     129#  prepare_job.sh     : to generate the script run_job.sh 
     130# 
     131#  fcm_job.sh         : run in batch (INTERACT_FLAG="no") or interactive (INTERACT_FLAG="yes") 
     132#                        see sette.sh and BATCH_TEMPLATE directory 
     133# 
     134#  NOTE: jobs requiring initial or forcing data need to have an input_CONFIG.cfg in which  
     135#        can be found paths to the input tar file) 
     136#  NOTE: if job is not launched for any reason you have the executable ready in ${EXE_DIR}  
     137#        directory 
     138#  NOTE: the changed namelists are left in ${EXE_DIR} directory whereas original namelists  
     139#        remain in ${NEW_CONF}/EXP00 
     140#  
     141#  NOTE: a log file, output.sette, is created in ${SETTE_DIR} with the echoes of  
     142#        executed commands 
     143# 
     144#  NOTE: if sette.sh is stopped in output.sette there is written the last command  
     145#        executed by sette.sh 
Note: See TracChangeset for help on using the changeset viewer.