Physics Template HOWTO
1. Monthly Data Fields Requested
| Field | Units | Horizontal Grid | Vertical Grid | Note(s) |
| Potential Temp | degrees C | Tracer | Tracer | (1) |
| Salinity | psu | Tracer | Tracer | (1) |
| Net Surface Heat Flux | W/m^2 | Tracer | --- | (2) |
| Net Surface Freshwater Flux | m/y | Tracer | --- | (2) |
| Eulerian Zonal Velocity | m/s | Eulerian U | Velocity | (3) |
| Zonal Wind Stress | N/m^2 | Eulerian U | --- | (3) |
| Eulerian Meridional Velocity | m/s | Eulerian V | Velocity | (3) |
| Meridional Wind Stress | N/m^2 | Eulerian V | --- | (3) |
| Eddy Induced Zonal Velocity | m/s | Eddy U | Velocity | (3),(4) |
| Eddy Induced Meridional Velocity | m/s | Eddy V | Velocity | (3),(4) |
- Temperature and Salinity are requested so that the velocity fields from this submitted data does not need to be coordinated with T and S fields from particular OCMIP runs.
- Heat and Freshwater fluxes are total combined fluxes. For instance, if the model includes climatological values and restoring, both terms should be included.
- The adjectives Zonal and Meridional are NOT to be taken literally. Velocity and Wind Stress fields should be aligned with the model's local grid. The direction of the vectors is specified in the grid description.
- Not all models will have eddy induced velocities.
2. Grids
Descriptions of the tracer grids for all of the models have already been
submitted with the subroutine write_nc_MaskAreaBathy.f.
Corresponding descriptions are necessary for the velocity grids.
The velocity grids are specified in a manner analogous to the tracer
grid specification in write_nc_MaskAreaBathy.f.
In order to be general, horizontal grids are independently specified for :
- Eulerian Zonal Velocity
- Eulerian Meridional Velocity
- Eddy Induced Zonal Velocity
- Eddy Induced Meridional Velocity
For each grid, the following quantities are specified :
| quantity | dimensions | description |
| imt | scalar | 'Zonal' dimension |
| jmt | scalar | 'Meridional' dimension |
| lon | (imt,jmt) | longitude of cell center |
| bounds_lon | (imt,jmt,2,2) | longitude boundaries of cell |
| lat | (imt,jmt) | latitude of cell center |
| bounds_lat | (imt,jmt,2,2) | latitude boundaries of cell |
| area | (imt,jmt) | surface area of cell |
| vector_angle | (imt,jmt) | Angle that the Local Vector makes with a Latitude Line |
The depth axes for all of the velocity grids are assumed to coincide, so
they are only specified once.
The bounds quantities follow the same conventions as the tracer grid cell bounds :
- bounds_lon(i,j,1,1) : lower left cell corner
- bounds_lon(i,j,2,1) : lower right cell corner
- bounds_lon(i,j,1,2) : upper left cell corner
- bounds_lon(i,j,2,2) : upper right cell corner
The quantity vector_angle is the counterclockwise angle that a
vector on the grid makes with a latitude line. Examples are
| Vector Direction | Corresponding Angle |
| Northeast | pi/4 |
| East | 0 |
| South | -pi/2 |
3. Conventions
The first 5 conventions are the same as those for write_nc_MaskAreaBathy.f
- Longitudes must be expressed in degrees as eastward positive (e.g.,
120W is to be expressed as -120; 120E is to be expressed as +120).
- Latitudes must be expressed in degrees as northward positive. (e.g.,
90S is to be expressed as -90; 90N is to be expressed as +90).
- Depth must be expressed in meters as positive downward (e.g.,
the depth of 1000 m is to be expressed as 1000).
- For irregular model grids which must be stored as a 1-D vector
instead of a 2-D array (e.g., model AWI), you must set jmt=1, and
not imt=1.
- You must provide model output on a grid without overlapping
boxes. For example, if for longitudes of your model
- i = 1 is the same as i = imt-1 and
- i = 2 is the same as i = imt,
then you must only provide model output for values from i=2 to
i=imt-1. Future reference to i during OCMIP-2 analysis will thus be
shifted by one, relative to that used in your model.
- As opposed to specifying a mask for each grid, values at
interior land points should be reported as the missing_value -1.E34.
4. Template Assumptions
The template is built on the following assumptions.
If these assumptions are not appropriate for your model, please inform me
via email at klindsay@cgd.ucar.edu
as soon as possible.
- Surface Heat and Freshwater fluxes are on the tracer grid specified by write_nc_MaskAreaBathy.f.
- All velocity fields, Eulerian and Eddy Induced, are on the same vertical grid.
- Zonal and Meridional Wind Stresses are on the same horizontal grids as the Eulerian Zonal and Meridional Velocities respectively.
5. Downloading the output routines
Fortran code for creating the NetCDF data file containing
ocean model physics data is in the files
6. Transfer of output
Executing the subroutines WRITE_NC_phys and WRITE_NC_vel_grid will produce
the NetCDF files group_phys.nc and group_vel_grid.nc. The most convenient
transfer method for me is for each group to make their results available
to me via ftp. If this is feasible for your group, notify me when your
output is available. I will download the data and notify you that I have
retrieved it.
If this method of transfer is not convient, please notify me.
Go back to OCMIP II at NCAR.
$Revision: 1.2 $, klindsay@cgd.ucar.edu