Changes between Version 4 and Version 5 of 2011WP/2011Stream2/Open Boundaries


Ignore:
Timestamp:
2011-03-11T17:07:00+01:00 (10 years ago)
Author:
davestorkey
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • 2011WP/2011Stream2/Open Boundaries

    v4 v5  
    121121   SUBROUTINE obc_tra( kt )  
    122122    
    123    DO ib_stream = 1, nb_stream 
    124  
    125       SELECT CASE ( nn_tra(ib_stream) ) 
     123   DO ib_set = 1, nb_set 
     124 
     125      SELECT CASE ( nn_tra(ib_set) ) 
    126126      CASE(0) 
    127127         CYCLE 
    128128      CASE(1) 
    129          CALL obc_tra_frs( kt, ib_stream ) 
     129         CALL obc_tra_frs( kt, ib_set ) 
    130130      CASE(2)  
    131          CALL obc_tra_rad( kt, ib_stream )  
     131         CALL obc_tra_rad( kt, ib_set )  
    132132      END SELECT 
    133133   
     
    136136   END SUBROUTINE 
    137137    
    138    SUBROUTINE obc_tra_frs( kt, ib_stream ) 
     138   SUBROUTINE obc_tra_frs( kt, ib_set ) 
    139139   ... 
    140140}}} 
    141  
    142 This structure allows one to define different boundaries with different boundary 
    143 conditions, eg. you might want to apply different algorithms on east 
    144 and west boundaries, or you might want to apply boundary conditions from a large 
    145 scale model for part of the boundary but apply climatological boundary conditons 
    146 for another part of the boundary. 
    147141 
    148142The module to read in the boundary data from files would be rewritten to use