Changes between Version 2 and Version 3 of Working Groups/TOP/NEMO36_TOP_BDY


Ignore:
Timestamp:
2018-10-29T19:13:38+01:00 (19 months ago)
Author:
lovato
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Working Groups/TOP/NEMO36_TOP_BDY

    v2 v3  
    66Last edition: '''[[Wikinfo(changed_ts)]]''' by '''[[Wikinfo(changed_by)]]''' 
    77 
    8 '''BEFORE USE''' : this patch is meant to provide only the core functionality for TOP BDY.  
     8'''BEFORE USE''' : this patch is meant to provide only the core functionality for TOP BDY under NEMO v3.6.  
    99Official support for tracers BDY will be given only for versions after NEMO v4.0. 
    1010 
     
    1414Note that in this patch, routines that provide to initialization/reading of all Boundary conditions (trcbc.f90) were also updated. 
    1515 
    16 ''BDY schemes'' included in this version are the following (see trcbdy.F90):  
     16__BDY schemes__ included in this version are the following (see trcbdy.F90):  
    1717* '''frs''' : Flow Relaxation Scheme  
    1818* '''specified''' : Specified value 
     
    3333   cn_dir_obc        =  './'      !  root directory for the location of OPEN data files 
    3434/ 
     35 
    3536!---------------------------------------------------------------------- 
    3637!namtrc_bdy       !   Setup of tracer boundary conditions 
     
    5657These files have to be unpacked in the MY_SRC folder of your configuration in order to be used. 
    5758 
    58 ''REMINDER'': MY_SRC contains user modified versions of NEMO routines or new pieces of code that are used at compilation time to supersede at original ones. 
     59__REMINDER__: MY_SRC contains user modified versions of NEMO routines or new pieces of code that are used at compilation time to supersede at original ones. 
     60 
     61In the following example the user defined tracer module MY_TRC is used to setup a simple one passive tracer case (need to add ''key_my_trc'' in the configuration cpp file) 
     62and specific modified files are also available in the tarball. 
    5963 
    6064Note that '''namelist_top_ref''' has to be modified by the user in <NEMODIR>/NEMOGCM/CONFIG/SHARED according to the description above (or the sample file provided in the tarball). 
    6165 
    6266All boundary conditions are controlled within the namelist '''namtrc''' in namelist_top_(cfg/ref). 
    63 A modified fortran data structure of namtrc was here developed to set the different boundary conditions of passive tracers, as in the following example of namelist_top_cfg : 
     67A modified fortran data structure of namtrc was here developed to set the different boundary conditions of passive tracers, as in the following example of namelist_top_cfg for one tracer : 
    6468 
    6569{{{ 
     
    7781where the new options relates to the provision of SURFACE (sbc), COASTAL (cbc), or  OPEN lateral Boundaries (obc) data for  sn_tracer(1)  named TRACER1. 
    7882 
    79 In '''namtrc_bc''' are provided the different boundary conditions for passive tracers, see the example below of namelist_top_cfg 
    80  
     83In '''namtrc_bc''' are provided the different boundary conditions for passive tracers, see the example below of namelist_top_cfg: 
    8184 
    8285{{{ 
     
    99102}}} 
    100103 
    101 Input files are provided using the standard NEMO fldread structure and follow the convention sn_trcsbc = surface, sn_trccbc = coastal, sn_trcobc = open lateral, 
    102 with the correspondig scaling factors rn_trsfac = surface, rn_trcfac = coastal, rn_trofac = open lateral. 
     104Input files are provided using the standard NEMO fldread structure and it follows the convention sn_trcsbc = surface, sn_trccbc = coastal, sn_trcobc = open lateral, 
     105with the corresponding scaling factors rn_trsfac = surface, rn_trcfac = coastal, rn_trofac = open lateral. 
     106 
     107BDY schemes are setup in the namelist '''namtrc_bdy'''.  In the following example for 1 tracer, we set the use of orlanski_npo scheme and no tracer damping: 
     108 
     109{{{ 
     110!---------------------------------------------------------------------- 
     111!namtrc_bdy       !   Setup of tracer boundary conditions 
     112!----------------------------------------------------------------------- 
     113$namtrc_bdy 
     114   cn_trc_dflt     =  'neumann'    !  OBC applied by default to all tracers 
     115   cn_trc          =  'orlanski_npo'       !  Boundary conditions applied to the passive tracers (selected in namtrc) 
     116 
     117   nn_trcdmp_bdy   = 0     !  Use damping timescales defined in nambdy of namelist 
     118 / 
     119}}} 
    103120 
    104121 
    105  
    106  
    107 namtrc_bc : here are provided the different boundary conditions for passive tracers, namely surface, coastal, and open lateral boundaries (see the example below for usage). 
    108 namtrc_bdy : here set the BDY schemes to be used for those tracers that BDY inputs are provided (according to namtrc options) 
     122Here below a summary of available options 
     123|| cn_trc_dflt || Default BDY scheme for all passive tracers || 
     124|| cn_trc || Specific BDY scheme to be applied for tracers that are forced with external data files, setup via namtrc || 
     125||nn_trcdmp_bdy || tracer damping, with timescales defined in nambdy of namelist_(ref/cfg) || 
     126|| || 0 : NO damping of tracers at open boundaries  || 
     127|| || 1 : Only for tracers forced with external data || 
     128|| || 2 : Damping applied to all tracers ||