coriolis force

[redhat007]

i used uv-COR in header file for computing coriolis force. since ROMS out put are in x, y and sigma axes(Cartesian ordinate), so it seems that just f plane is definable for computing coriolis force in ROMS ( i am not sure ).
would you please tell me that in ROMS, coriolis force is computed in f plane or Beta plane?
cheers
redhat

[kate]

ROMS is flexible. Did you give it a NetCDF grid file or did you use ana_grid? If you provide a grid file, then f can be any function of lat/lon/x/y you like - ROMS will just read it. With ana_grid, it can also be anything, but f-plane or beta-plane are easiest to code (examples are provided).

[redhat007]

i give it a NetCDF grid file in lon/lat.

If you provide a grid file, then f can be any function of lat/lon/x/y you like

do you mean that coriolis force is variable and is function of lat/lon?
cheers
redhat

[kate]

I mean the grid file should provide the field "f":

Code: Select all

        double f(eta_rho, xi_rho) ;
                f:long_name = "Coriolis parameter at RHO-points" ;
                f:units = "second-1" ;
                f:coordinates = "lon_rho lat_rho" ;

I expect most grid-generation codes would create this as the appropriate function of latitude, in the "spherical" case where there is a latitude. ROMS only computes it's own "f" in the ana_grid case.

[redhat007]

thanks
how can choose coordinate system (Cartesian and spherical coordinates) in ROMS?
does it choose by options?
cheers
redhat

[kate]

Since you are providing a grid file, it's one of the variables in there. It's a scalar integer, zero (false) or one (true).