Custom Query (964 matches)
Results (628 - 630 of 964)
Ticket | Owner | Reporter | Resolution | Summary |
---|---|---|---|---|
#588 | Fixed | bug in load_s2d | ||
Description |
When faced with NFFILES == 2 ! number of forcing files FRCNAME == /center/w/kate/MERRA/MERRA_Uwind_3hours_2007.nc | /center/w/kate/MERRA/MERRA_Uwind_3hours_2008.nc \ /center/w/kate/MERRA/MERRA_Vwind_3hours_2007.nc | /center/w/kate/MERRA/MERRA_Vwind_3hours_2008.nc ROMS assigns the first three input files to the first file and the last to the second file. It then fails: GET_2DFLD - surface u-wind component, t = 39433 22:30:00 (Rec=0002824, Index=1, File: MERRA_Uwind_3hours_2007.nc) (Tmin= 39081.0625 Tmax= 39445.9375) (Min = -1.55921714E+01 Max = 1.67592775E+01) GET_CYCLE - starting time for variable: wind_time is greater than current model time. TMIN = 39446.0625 TDAYS = 39434.0000 I have attached a patch to fix this. |
|||
#589 | Fixed | Fixed logic in editmask | ||
Description |
Coded a generic logic in matlab/landmask/editmask.m to process the coastline data used to determine land/sea masking in realistic applications. The internal switch got_coast was not initialized when the coastline file was provided as a second argument. For the last few years, we have been adding the coastline data to the GRID NetCDF file into variables lon_coast and lat_coast: dimensions: xi_rho = 258 ; xi_u = 257 ; xi_v = 258 ; xi_psi = 257 ; eta_rho = 130 ; eta_u = 130 ; eta_v = 129 ; eta_psi = 129 ; bath = UNLIMITED ; // (1 currently) coast = 11908 ; variables: double lon_coast(coast) ; lon_coast:long_name = "Coastline longitude" ; lon_coast:units = "degree_east" ; double lat_coast(coast) ; lat_coast:long_name = "Coastline latitude" ; lat_coast:units = "degree_north" ; This is a very useful strategy: the coastline data used to compute the land/sea masking for an application is in its GRID NetCDF file. This data can be also used for plotting. Many thanks to Evridiki Chrisagi for reporting this. |
|||
#590 | Done | IMPORTANT: New lateral boundary conditions | ||
Description |
Two new open boundary conditions have been added: 1) Explicit Chapman boundary condition for free-surface, and 2) Shchepetkin boundary condition for 2D momentum. Now, in ROMS standard input script ocean_*.in we have: ! Set lateral boundary conditions keyword. Notice that a value is expected ! for each boundary segment per nested grid for each state variable. ! ! Each tracer variable requires [1:4,1:NAT+NPT,Ngrids] values. Otherwise, ! [1:4,1:Ngrids] values are expected for other variables. The boundary ! order is: 1=west, 2=south, 3=east, and 4=north. That is, anticlockwise ! starting at the western boundary. ! ! The keyword is case insensitive and usually has three characters. However, ! it is possible to have compound keywords, if applicable. For example, the ! keyword "RadNud" implies radiation boundary condition with nudging. This ! combination is usually used in active/passive radiation conditions. ! ! Keyword Lateral Boundary Condition Type ! ! Cha Chapman_implicit (free-surface) ! Che Chapman_explicit (free-surface) ! Cla Clamped ! Clo Closed ! Fla Flather (2D momentum) _____N_____ j=Mm ! Gra Gradient | 4 | ! Nes Nested (refinement) | | ! Nud Nudging 1 W E 3 ! Per Periodic | | ! Rad Radiation |_____S_____| ! Red Reduced Physics (2D momentum) 2 j=1 ! Shc Shchepetkin (2D momentum) i=1 i=Lm ! ! W S E N ! e o a o ! s u s r ! t t t t ! h h ! ! 1 2 3 4 LBC(isFsur) == Che Che Che Clo ! free-surface LBC(isUbar) == Shc Shc Shc Clo ! 2D U-momentum LBC(isVbar) == Shc Shc Shc Clo ! 2D V-momentum LBC(isUvel) == RadNud RadNud RadNud Clo ! 3D U-momentum LBC(isVvel) == RadNud RadNud RadNud Clo ! 3D V-momentum LBC(isMtke) == Gra Gra Gra Clo ! mixing TKE LBC(isTvar) == RadNud RadNud RadNud Clo \ ! temperature RadNud RadNud RadNud Clo ! salinity
I also coded the TLM, RPM, and ADM versions of these boundary conditions. We are currently testing them. References:
|