Changes between Version 6 and Version 7 of 2011WP/2011Stream2/OpenBoundaries

Timestamp:

2011-03-29T10:53:03+02:00 (13 years ago)

Author:

davestorkey

Comment:

--

2011WP/2011Stream2/OpenBoundaries

@@ -49 +49 @@
 !-----------------------------------------------------------------------
    nb_obc         = 2       !  Number of open boundary sets
+   ln_read        = .false.,.true.
    cn_mask        = ''      !  name of mask file (ln_mask=T)
    nn_dyn         = 1, 0,   !  Choice of schemes for velocities
@@ -232 +233 @@
    END SUBROUTINE
 }}}
+
+== Boundary geometry and initialisation ==
+The internal code of the new module will use 1D unstructured arrays to specify the boundary as is currently done in BDY. For the T-points along the boundary these are '''nbit''', '''nbjt''' and '''nbrt''', which specify the (i,j) coordinates of each point and the discrete distance from the boundary. Each boundary set can be initialised using straight-line segments in '''obc_par.F90''' (ln_read=.false.) or read in from a '''coordinates_bdy.nc''' file (ln_read=.true.). If the boundary coordinates are read in from '''obc_par.F90''' then the '''nbi''', '''nbj''', '''nbr''' arrays will be generated internally (and if necessary a '''coordinates_bdy.nc''' file could be written out). 
+
+The '''obc_par.F90''' file will be the easiest way to define rectangular boundaries. More than one segment can be specified for each of the north, east, south and west boundaries as follows. Where there are more than one boundary set, the '''jpieob'''-type arrays are specified as 1D arrays and the '''nobcsege'''-type arrays are used to split the numbers between the different boundary sets. 
+{{{
+   MODULE obc_par
+
+   INTEGER, PARAMETER ::     & !: ! Number of open boundary segments
+      nobcsege = 2, 0 
+   INTEGER, PARAMETER, DIMENSION(nobcsege) ::     &  !:
+      ! First column: Med Sea; Second: Baltic
+      jpieob = (/ 1037 , jpiglo-2 /), & !: i-localization of the East open boundary
+      jpjedt = (/ 473  ,   1476   /), & !: j-starting indice of the East open boundary
+      jpjeft = (/ 855  ,   1548   /)    !: j-ending   indice of the East open boundary
+   !! * WEST open boundary
+   INTEGER, PARAMETER ::     &  !: ! Number of open boundary segments
+      nobcsegw = 1, 0
+   INTEGER, PARAMETER, DIMENSION(nobcsegw) ::     &
+      jpiwob = (/  2 /), &       !: i-localization of the West open boundary
+      jpjwdt = (/  2 /), &       !: j-starting indice of the West open boundary
+      jpjwft = (/1875/)       !: j-ending   indice of the West open boundary
+   ...
+}}}
+For unstructured boundaries, the easiest method will be to generate them offline and read in the boundary definition from the coordinates_bdy.nc file, which looks like this: 
+{{{
+netcdf coordinates_bdy {
+dimensions:
+        xbT = 8485 ;
+        xbU = 8436 ;
+        xbV = 8455 ;
+        xbF = 8062 ;
+        yb = 1 ;
+variables:
+        int nbit(yb, xbT) ;
+        int nbiu(yb, xbU) ;
+        int nbiv(yb, xbV) ;
+        int nbif(yb, xbF) ;
+        int nbjt(yb, xbT) ;
+        int nbju(yb, xbU) ;
+        int nbjv(yb, xbV) ;
+        int nbjf(yb, xbF) ;
+        int nbrt(yb, xbT) ;
+        int nbru(yb, xbU) ;
+        int nbrv(yb, xbV) ;
+        int nbrf(yb, xbF) ;
+        float glamt(yb, xbT) ;
+                glamt:units = "degrees_east" ;
+        float glamu(yb, xbU) ;
+                glamu:units = "degrees_east" ;
+        float glamv(yb, xbV) ;
+                glamv:units = "degrees_east" ;
+        float glamf(yb, xbF) ;
+                glamf:units = "degrees_east" ;
+}}}
+
+
+