[MITgcm-devel] exf_check_range

Dimitris Menemenlis menemenlis at jpl.nasa.gov
Fri Nov 19 14:54:09 EST 2004


On Friday 19 November 2004 11:38 am, mlosch at awi-bremerhaven.de wrote:
> I like Patrick's choice because all they do is make sure the units 
> are about right (so prevents you from using cm instead of m, 
> degC instead of K etc...)

They're definitely a vast improvement over status quo ... but they don't
check for, e.g., sign of hflux, and cannot discriminate between N/m^2
and dynes/cm^2.  One compromise would be to add a "strict_check"
flag, which is .FALSE. by default, and which carries out more stringent
tests.  I can take care of second strict flag (if Patrick is about to cut my 
futton length to 0.85 m after this discussion ;-)

D.

-- 
Dimitris Menemenlis <menemenlis at jpl.nasa.gov>
Jet Propulsion Lab, California Institute of Technology
MS 300-323, 4800 Oak Grove Dr, Pasadena CA 91109-8099
tel: 818-354-1656;  fax: 818-393-6720



More information about the MITgcm-devel mailing list