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.
user/ctlod/NVTKpage (diff) – NEMO

Changes between Version 18 and Version 19 of user/ctlod/NVTKpage


Ignore:
Timestamp:
2009-08-13T16:30:12+02:00 (15 years ago)
Author:
ctlod
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • user/ctlod/NVTKpage

    v18 v19  
    77The full documentation is attached at the end of this page.[[BR]] 
    88 
    9 Context: [[BR]] 
    10 the user made modifications in few modules of the NEMO code; he wants to check if these changes fit basic features such as the reproductibility, the restartability, or to check the global memory and/or the time consuming but also if results of the reference configurations ORCA2_LIM, GYRE and GYRE_LOBSTER are not modified.[[BR]] 
     9Context: NVTK can be usefull for 2 purposes slightly different[[BR]] 
     10 1- the user made modifications in few modules of the NEMO code; he wants to check if these changes fit basic features such as the reproductibility, the restartability, or to check the global memory and/or the time consuming but also if results of the reference configurations ORCA2_LIM, GYRE and GYRE_LOBSTER are not modified.[[BR]] 
     11#2 the user has to do sensitivity experiments (optimisation, physics parameters... ) with one configuration, he will be able to decline as many directories as he needs under ./config/NVTK directory. Each directory can be asociated with a specific namelist named with the directory name as extension (namelist_EXP1 for instance) 
    1112 
    1213The NEMO Validation Tool Kit (NVTK hereinafter) has been built to allow the user to perform a set of validation tests simply and quickly in using few commands.  
     
    1718The user has to refer to the associated paper documentation to get details about the general organisation and scripts. [[BR]] 
    1819 
    19 '''Note:''' Here we suppose platforms used are either the NEC-SX8 either the IBM-SP6 from the French computing center IDRIS, else the user will have to adapt some scripts (following instructions in part II-d Add a new target ?) once the NVTK environment will be downloaded. Furthermore it is also assumed that the code management environement is ''modipsl''.[[BR]] 
     20[[Color(grey, red, '''Note''')]]: Here we suppose platforms used are either the NEC-SX8 either the IBM-SP6 from the French computing center IDRIS, else the user will have to adapt some scripts (following instructions in part II-d Add a new target ?) once the NVTK environment will be downloaded. Furthermore it is also assumed that the code management environement is ''modipsl''. [[BR]] 
    2021 
    2122'''All remarks, suggestions to improve this tool are welcome,  you can write them here:''' [http://forge.ipsl.jussieu.fr/nemo/milestone/NEMO%20Validation%20Tool%20Kit] 
     
    7071# '''INPUTD'''  : directory where to get ORCA2_LIM_nemo_v3.tar (once downloaded here: [http://dodsp.idris.fr/reee512/NEMO/])[[BR]] 
    7172# '''REFDAT'''  : directory where to get results from reference tags[[BR]] 
    72 # '''DECOMP''' : total number of processors which will be used[[BR]] 
    7373# '''MAIL'''       : give your e-mail[[BR]] 
    7474# '''UAGRIF'''   : one of the standard configurations is based on AGRIF yes/no[[BR]] 
     
    7777INPUTD=[[BR]] 
    7878REFDAT=[[BR]] 
    79 DECOMP=[[BR]] 
    8079MAIL="your_email@xxxxxxx"[[BR]] 
    8180UAGRIF=no[[BR]] 
     
    8988> ./ins_nvtk.ksh 
    9089}}} 
    91  
    92 2. Set the appropriate domain decomposition values for jpni, jpnj & jpnij  parameters. To be done in par_oce.F90_keep file under each ./config/CONFIG_NAME/MY_SRC directory[[BR]] 
    93  
    94 {{{ 
    95 > cd  TEST/modipsl/config/CONFIG_NAME/MY_SRC/ 
    96 > vi par_oce.F90_keep 
    97 }}} 
    98 ....... 
    99    INTEGER, PUBLIC, PARAMETER ::    &  !:[[BR]] 
    100       jpni   = 2,            &  !: number of processors following i[[BR]] 
    101       jpnj   = 4,            &  !: number of processors following j[[BR]] 
    102       jpnij  = 8                 !: nb of local domain = nb of processors[[BR]] 
    103       !                             !  ( <= jpni x jpnj )[[BR]] 
    104 ....... 
    10590 
    10691== B - Compilation, Jobs submission and assessment report: == 
     
    116101}}} 
    117102 
    118 * '''NAM_V:''' name of the test (this information will be used in the assessment report at the end of all simulations) A directory using the same name must exist, the default one is 2TEST [[BR]] 
    119 * '''LISTE_CONF:''' '''''ORCA2_LIM''' or/and '''GYRE''' or/and '''GYRE_LOBSTER''''': name of standard configurations to be tested with modified routines under 2TEST directory[[BR]] 
     103* '''NAM_V:''' name of the experiment (associated to the same directory name) the default one is 2TEST [[BR]] 
     104* '''LISTE_CONF:''' ''ORCA2_LIM'' or/and ''GYRE'' or/and ''GYRE_LOBSTER'': name of standard configurations to be tested with modified routines under 2TEST directory[[BR]] 
    120105* '''JOBS_2LAUN:''' '''''nojob''' or '''all''' or '''long''' or '''short''' or '''gtime''''': choose the job type to launch[[BR]] 
    121 * '''BUILD_MAKE:''' '''''mon''' or/and '''mpi''' or/and '''omp''''': compilation type to perform:mono-processor (''mon'') and/or multi-processors MPI (''mpi'') and/or Open-MP (''omp'') (this list is applied to each configuration specified in the '''LISTE_CONF''' variable). If mpi is specified, the user must set the processor cutting (jpni, jpnj & jpnij parameters) in the par_oce.F90_keep module stored in each ./config/CONFIG_NAME/MY_SRC directory. This MPI decomposition must be the same for the 3 configurations[[BR]] 
     106* '''BUILD_MAKE:''' '''''mon''' or/and '''mpi''': compilation type to perform:mono-processor (''mon'') and/or multi-processors MPI (''mpi'') [[BR]] 
     107* '''MPI_I:''' number of processors along i- direction[[BR]] 
     108* '''MPI_J:''' number of processors along j- direction[[BR]] 
     109* '''MPIIJ:''' total number of processors [[BR]] 
    122110* '''MAK_TIME:''' '''''timing''' or '''notiming''''' to perform or not a timing check[[BR]] 
     111* '''USE_IOMPUT:''' use or not the new I/O interface[[BR]] 
     112* '''USE_IOSERVER:''' use the I/O interface using the server possibility[[BR]] 
     113* '''NB_PROCS_IOSERVER :''' number of processors dedicated to the I/O server[[BR]] 
    123114* '''MAK_MEMO:''' '''''memo''' or '''nomemo''''' to perform or not a memory check[[BR]] 
    124 * '''REF_TAGV:''' (optional) reference tag version to which compare results[[BR]] 
     115* '''REF_TAGV:''' (optional) tag/experience name to which compare results[[BR]] 
    125116 
    1261173. launch the whole process (compilation, jobs submission & assessment report) using gmake command from TEST/modipsl/config/NVTK[[BR]] 
     
    144135 
    145136== D - Paper documentation == 
    146  
     137Note: The paper documentation is not up-to-date yet with the last NEMO tag nemo_v3_2