Changes between Version 4 and Version 5 of 2011WP/2011Stream2/OpenBoundaries
- Timestamp:
- 2011-03-11T17:07:00+01:00 (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
2011WP/2011Stream2/OpenBoundaries
v4 v5 121 121 SUBROUTINE obc_tra( kt ) 122 122 123 DO ib_s tream = 1, nb_stream124 125 SELECT CASE ( nn_tra(ib_s tream) )123 DO ib_set = 1, nb_set 124 125 SELECT CASE ( nn_tra(ib_set) ) 126 126 CASE(0) 127 127 CYCLE 128 128 CASE(1) 129 CALL obc_tra_frs( kt, ib_s tream)129 CALL obc_tra_frs( kt, ib_set ) 130 130 CASE(2) 131 CALL obc_tra_rad( kt, ib_s tream)131 CALL obc_tra_rad( kt, ib_set ) 132 132 END SELECT 133 133 … … 136 136 END SUBROUTINE 137 137 138 SUBROUTINE obc_tra_frs( kt, ib_s tream)138 SUBROUTINE obc_tra_frs( kt, ib_set ) 139 139 ... 140 140 }}} 141 142 This structure allows one to define different boundaries with different boundary143 conditions, eg. you might want to apply different algorithms on east144 and west boundaries, or you might want to apply boundary conditions from a large145 scale model for part of the boundary but apply climatological boundary conditons146 for another part of the boundary.147 141 148 142 The module to read in the boundary data from files would be rewritten to use