Custom Query (964 matches)
Results (91 - 93 of 964)
Ticket | Owner | Reporter | Resolution | Summary |
---|---|---|---|---|
#267 | Fixed | boundary condition changes | ||
Description |
set_tides fails to compile because mod_boundary has tests on NORTH_FSOBC for the definition of zeta_north, but set_tides doesn't have this test. I have a NORTHERN_WALL, so get: PGF90-S-0142-zeta_north is not a member of this RECORD (set_tides.f90: 60) PGF90-S-0142-ubar_north is not a member of this RECORD (set_tides.f90: 60) PGF90-S-0142-vbar_north is not a member of this RECORD (set_tides.f90: 60) |
|||
#283 | Fixed | ana_srflux diurnal flux factor is wrong in high latitude endless daylight case | ||
Description |
Line 215 of ana_srflux.h should be cff=cff1 the factor of 2*pi is wrong. The comment about it should read: ! Normalization = (1/2*pi) INTEGRAL{ABS(a+b*COS(t)) dt} from 0 to 2*pi ! = (a*ARCCOS(-a/b)+SQRT(b**2-a**2))/pi for |a|<|b| |
|||
#285 | Done | CF-1.0 Compliance | ||
Description |
Some visualization softwares are only able to handle ROMS netcdf output files, when attributes for some variables are added. These attributes describe the relations between real world and model model coordinate systems and are in compliance with the CF-1.0 standard. I suggest to introduce the coordinates attribute, like
h:coordinates = "lon_rho lat_rho" ; I do not know if software packages in general can use the standard_name for the rho, u, v and psi points in parallel. Therefore, I would suggest to set this attribute only for the rho points, because most variables are defined on this points. lon_rho:standard_name = "longitude" ; In addition, I would like that the attribute positive is added to describe the orientation of vertical axes. h:positive = "down"; This attribute allows to interpret the orientation of an axis. In the example the software might realize, that the deep is getting deeper for higher numbers. Unfortunately, some software packets do not evaluated this attribute. To prevent problems by introducing the additional parameters, I suggest to introduce a FLAG, which is not set in the standard case. Since ferret, for example, gives a warning message when data containing the coordinates attribute are loaded, these might cause a flood of trouble tickets and long discussions in the wiki. This might be preventable by setting undef FLAG. |