Changes between Version 13 and Version 14 of Working Groups/TOP/TOP-User Quick Guide


Ignore:
Timestamp:
2018-01-17T11:54:34+01:00 (3 years ago)
Author:
lovato
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Working Groups/TOP/TOP-User Quick Guide

    v13 v14  
    148148|| rn_age_kill_rate || Relaxation timescale (s) for age tracer shallower than age depth || 
    149149 
    150  
    151  
    152150Two main types of data structure are used within TOP interface to initialize tracer properties (1) and to provide related initial and boundary conditions (2). 
    153151 
    154152 1. TOP tracers initialization : sn_tracer (namtrc) 
    155153 
    156  
    157  
    158154Beside providing name and metadata for tracers, here are also defined the use of initial (sn_tracer%llinit) and boundary (sn_tracer%llsbc,sn_tracer%llcbc, sn_tracer%llobc) conditions. 
    159155 
    160156In the following, an example of the full structure definition is given for two idealized tracer both with initial conditions given and the first with surface boundary forcing prescribes, while the second has surface and coastal forcing: 
    161157 
    162 !                          !    name   !           title of the field            !   units    ! initial data ! sbc ! cbc ! obc !  
    163  
    164 sn_tracer(1)  = 'TRC1' , 'Tracer  1 Concentration                 ',   ' - '    ,  .true., .true., .false., .true. 
    165  
    166 sn_tracer(2)  = 'TRC2 ' , 'Tracer 2  Concentration                 ',   ' - '    ,  .true., .true., .true., .false. 
     158 
     159{{{ 
     160!                          !    name   !           title of the field            !   units    ! initial data ! sbc ! cbc ! obc ! 
     161sn_tracer(1)  = 'TRC1' , 'Tracer  1 Concentration                 ',   ' - '    ,  .true., .true., .false., .true. 
     162sn_tracer(2)  = 'TRC2 ' , 'Tracer 2  Concentration                 ',   ' - '    ,  .true., .true., .true., .false. 
     163}}} 
     164 
    167165 
    168166As tracers in BGC models are increasingly growing, the same structure can be written also in a more compact and readable way: 
    169167 
    170 !                          !    name   !           title of the field            !   units    ! initial data !  
    171  
    172 sn_tracer(1)  = 'TRC1' , 'Tracer  1 Concentration                 ',   ' - '    ,   .true. 
    173  
    174 sn_tracer(2)  = 'TRC2 ' , 'Tracer 2  Concentration                 ',   ' - '    ,   .true. 
    175  
     168 
     169{{{ 
     170!                          !    name   !           title of the field            !   units    ! initial data ! 
     171sn_tracer(1)  = 'TRC1' , 'Tracer  1 Concentration                 ',   ' - '    ,   .true. 
     172sn_tracer(2)  = 'TRC2 ' , 'Tracer 2  Concentration                 ',   ' - '    ,   .true. 
    176173! sbc 
    177  
    178174sn_tracer(1)%llsbc = .true. 
    179  
    180175sn_tracer(2)%llsbc = .true. 
    181  
    182176! cbc 
    183  
    184177sn_tracer(2)%llcbc = .true. 
     178}}} 
     179 
    185180 
    186181The data structure is internally initialized by code with dummy names and all initialization/forcing logical fields set to .false. . 
     
    188183 2. SBC structure to read input fields : sn_trcdta (namtrc_dta), sn_trcsbc sn_trccbc sn_trcobc (namtrc_bc) 
    189184 
    190  
    191  
    192185This data structure is based on the general one defined for NEMO core in the SBC component (see details in User Manual SBC Chapter on Input Data specification). 
    193186 
    194187The following example show the data structure in the case of a single tracer with initial conditions contained in the file named tracer_1_data.nc (.nc is implicitly assumed), with a doublef intial value, and located in the usr/work/model/inputdata/ folder: 
    195188 
    196 !          !  file name  ! frequency (hours) ! variable  ! time interp. !  clim  ! 'yearly'/ ! weights  ! rotation ! land/sea mask ! 
    197  
    198 !          !             !  (if <0  months)  !   name    !   (logical)  !  (T/F) ! 'monthly' ! filename ! pairing  ! filename      ! 
    199  
    200    sn_trcdta(1)  = !''tracer_1_data'        ,        -12        ,  'TRC1'     ,    .false.   , .true. , 'yearly'  , !''       , !''   , !'' 
    201  
    202 rf_trfac(1) = 2.0 
    203  
    204 cn_dir = “usr/work/model/inputdata/” 
     189 
     190{{{ 
     191!          !  file name  ! frequency (hours) ! variable  ! time interp. !  clim  ! 'yearly'/ ! weights  ! rotation ! land/sea mask ! 
     192!          !             !  (if <0  months)  !   name    !   (logical)  !  (T/F) ! 'monthly' ! filename ! pairing  ! filename      ! 
     193  sn_trcdta(1)  = !'' tracer_1_data'        ,        -12        ,  'TRC1'     ,    .false.   , .true. , 'yearly'  , !''        , !''    , !'' 
     194  rf_trfac(1) = 2.0 
     195  cn_dir = “usr/work/model/inputdata/” 
     196}}} 
     197 
    205198 
    206199The Lateral Open Boundaries conditions are applied to the segments defined for the physical core of NEMO (see BDY description in the User Manual). 
     200 
     201 
     202