Changes between Version 14 and Version 15 of 2011WP/2011Stream2/OpenBoundaries

Timestamp:

2011-03-29T14:57:18+02:00 (12 years ago)

Author:

davestorkey

Comment:

--

2011WP/2011Stream2/OpenBoundaries

@@ -39 +39 @@
  * It will be possible to define more than one open boundary set. This will
    allow different boundary conditions to be applied on different boundaries.
-   
+
+== Questions ==
+
+ * For the timesplitting solution for the free surface (ln_dynspg_ts=.true.) boundary conditions 
+   are applied to the barotropic (nn_dyn2d) and baroclinic (nn_dyn3d) solutions separately. For 
+   the filtered free surface should we insist that we apply barotropic and baroclinic boundary conditions 
+   separately or do we allow boundary conditions to be applied to the full velocity field?
+
    
 == Control and coding structure ==
@@ -100 +107 @@
 
 For each open boundary set you define which conditions to apply to each set of
-variables using '''nn_dyn''', '''nn_tra''' etc. For example:
-
- * '''nn_tra''' = 0 : Apply no boundary condition (land boundary)
- * '''nn_tra''' = 1 : Clamped/relaxation boundary condition
- * '''nn_tra''' = 2 : Normal radiation condition
- * '''nn_tra''' = 3 : NPO radiation condition
- * etc.
+variables using '''nn_dyn3d''', '''nn_tra''' etc. For example:
+
+ * '''nn_dyn3d''' = 0 : Apply no boundary condition (land boundary)
+ * '''nn_dyn3d''' = 1 : Clamped/relaxation boundary condition
+ * '''nn_dyn3d''' = 2 : Orlanski NPO radiation condition
+ * '''nn_dyn3d''' = 3 : Orlanski fully 2d radiation condition
+ * ''etc.''
         
 There is a separate '''&namobc_dta''' namelist for each boundary set, which
@@ -113 +120 @@
 
 For each set of variables there is a module which applies the boundary
-conditions each timestep, eg. for T and S you have '''obctra.F90''' which looks
+conditions each timestep, eg. for T and S you have '''obcdyn3d.F90''' which looks
 like this:
 
 {{{
-   MODULE obctra
+   MODULE obcdyn3d
 
 CONTAINS
    
-   SUBROUTINE obc_tra( kt ) 
+   SUBROUTINE obc_dyn3d( kt ) 
    
    DO ib_set = 1, nb_set
 
-      SELECT CASE ( nn_tra(ib_set) )
+      IF ( using Orlanski radiation ) THEN 
+         CALL obc_rad( kt, ib_set )
+      ENDIF
+
+      SELECT CASE ( nn_dyn3d(ib_set) )
       CASE(0)
          CYCLE
       CASE(1)
-         CALL obc_tra_frs( kt, ib_set )
+         CALL obc_dyn3d_frs( kt, ib_set )
       CASE(2) 
-         CALL obc_tra_rad( kt, ib_set ) 
+         CALL obc_dyn3d_orl( kt, ib_set ) 
+      CASE(3) 
+         CALL obc_dyn3d_orl( kt, ib_set ) 
       END SELECT
   
@@ -138 +151 @@
    END SUBROUTINE
    
-   SUBROUTINE obc_tra_frs( kt, ib_set )
+   SUBROUTINE obc_dyn3d_frs( kt, ib_set )
    ...
+
+   SUBROUTINE obc_dyn3d_orl( kt, ib_set )
+   ...
+
 }}}
 
@@ -316 +333 @@
 }}}
 
-
-
+== Pseudo code for implementation of Orlanski radiation conditions using BDY-style arrays ==
+
+... To be done ...