Changes between Version 13 and Version 14 of WorkingGroups/TOP/TOP-UserQuickGuide

Timestamp:

2018-01-17T11:54:34+01:00 (6 years ago)

Author:

lovato

Comment:

--

WorkingGroups/TOP/TOP-UserQuickGuide

@@ -148 +148 @@
 || rn_age_kill_rate || Relaxation timescale (s) for age tracer shallower than age depth ||
 
-
-
 Two main types of data structure are used within TOP interface to initialize tracer properties (1) and to provide related initial and boundary conditions (2).
 
  1. TOP tracers initialization : sn_tracer (namtrc)
 
-
-
 Beside 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.
 
 In 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:
 
-!                          !    name   !           title of the field            !   units    ! initial data ! sbc ! cbc ! obc ! 
-
-sn_tracer(1)  = 'TRC1' , 'Tracer  1 Concentration                 ',   ' - '    ,  .true., .true., .false., .true.
-
-sn_tracer(2)  = 'TRC2 ' , 'Tracer 2  Concentration                 ',   ' - '    ,  .true., .true., .true., .false.
+
+{{{
+!                          !    name   !           title of the field            !   units    ! initial data ! sbc ! cbc ! obc !
+sn_tracer(1)  = 'TRC1' , 'Tracer  1 Concentration                 ',   ' - '    ,  .true., .true., .false., .true.
+sn_tracer(2)  = 'TRC2 ' , 'Tracer 2  Concentration                 ',   ' - '    ,  .true., .true., .true., .false.
+}}}
+
 
 As tracers in BGC models are increasingly growing, the same structure can be written also in a more compact and readable way:
 
-!                          !    name   !           title of the field            !   units    ! initial data ! 
-
-sn_tracer(1)  = 'TRC1' , 'Tracer  1 Concentration                 ',   ' - '    ,   .true.
-
-sn_tracer(2)  = 'TRC2 ' , 'Tracer 2  Concentration                 ',   ' - '    ,   .true.
-
+
+{{{
+!                          !    name   !           title of the field            !   units    ! initial data !
+sn_tracer(1)  = 'TRC1' , 'Tracer  1 Concentration                 ',   ' - '    ,   .true.
+sn_tracer(2)  = 'TRC2 ' , 'Tracer 2  Concentration                 ',   ' - '    ,   .true.
 ! sbc
-
 sn_tracer(1)%llsbc = .true.
-
 sn_tracer(2)%llsbc = .true.
-
 ! cbc
-
 sn_tracer(2)%llcbc = .true.
+}}}
+
 
 The data structure is internally initialized by code with dummy names and all initialization/forcing logical fields set to .false. .
@@ -188 +183 @@
  2. SBC structure to read input fields : sn_trcdta (namtrc_dta), sn_trcsbc sn_trccbc sn_trcobc (namtrc_bc)
 
-
-
 This 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).
 
 The 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:
 
-!          !  file name  ! frequency (hours) ! variable  ! time interp. !  clim  ! 'yearly'/ ! weights  ! rotation ! land/sea mask !
-
-!          !             !  (if <0  months)  !   name    !   (logical)  !  (T/F) ! 'monthly' ! filename ! pairing  ! filename      !
-
-   sn_trcdta(1)  = !''tracer_1_data'        ,        -12        ,  'TRC1'     ,    .false.   , .true. , 'yearly'  , !''       , !''   , !''
-
-rf_trfac(1) = 2.0
-
-cn_dir = “usr/work/model/inputdata/”
+
+{{{
+!          !  file name  ! frequency (hours) ! variable  ! time interp. !  clim  ! 'yearly'/ ! weights  ! rotation ! land/sea mask !
+!          !             !  (if <0  months)  !   name    !   (logical)  !  (T/F) ! 'monthly' ! filename ! pairing  ! filename      !
+  sn_trcdta(1)  = !'' tracer_1_data'        ,        -12        ,  'TRC1'     ,    .false.   , .true. , 'yearly'  , !''        , !''    , !''
+  rf_trfac(1) = 2.0
+  cn_dir = “usr/work/model/inputdata/”
+}}}
+
 
 The Lateral Open Boundaries conditions are applied to the segments defined for the physical core of NEMO (see BDY description in the User Manual).
+
+
+