This is the README file for SPEM version 5.2. There is a SPEM User's Guide describing SPEM 3.9, available either via anonymous ftp (pub/kate/manual.ps.Z), the world wide web, or from kate@ahab.rutgers.edu. Anyone using SPEM 5.2 should obtain this manual. This file attempts to describe what has changed since the manual was written.
To run the spem examples:
The reason for this change is that finite differences are less sensitive than is a spectral expansion to rapid transitions which occur (e.g.) at the base of the wind mixed layer. Second-order (centered) finite difference approximations are used in the s- coordinate.
NOTE: the netCDF files get created with dimensions built in, so that you have to change output filenames or delete the old ones when going from one problem to another.
The scheme is implemented so that MIX_EN_TS and/or MIX_EN_UV can be defined. One does not require the other. The same applies for MIX_GP_*, but as before, MIX_EN_* requires MIX_GP_*.
MIX_EN_* does not require vertical diffusion. Explicit vertical diffusion is handled separately, and can still be treated implicitly if that spem5.1 option is enabled. Remember though, that isopycnal mixing automatically implies some vertical z mixing. The explicit vertical diffusivity (akt,akuv) is being interpreted as diapycnal under this arrangement.
About get_rhosxe.F:
This is a new routine that computes the density surface slopes. It is executed if either MIX_EN_TS or MIX_EN_UV is defined. It is only called once each timestep. During execution it is called *before* rhocal. This follows a suggestion from Anne-Marie Treguier that the slopes should be computed using rho values at the same time level as the linear mixing terms. The only trick here is that at initialisation the slopes can't be calculated before rhocal is called. This is why I separated get_rhosxe from rhocal. A Shapiro filter is applied to the slopes. Why? It seemed like a good idea a long time ago.
Some of the C preprocessor code in SPEM confuses these perl scripts, so some manual intervention is required after the fact.
![]()
|
Kate Hedstrom
Last changed on: 24 August 1999 |