[MITgcm-devel] exf_check_range

[Dimitris Menemenlis]

Patrick, the check_range values are a compromise between useful and annoying 
and vary wildly depending on temporal and spatial scale of forcing.  
Nevertheless my vote would be for values that are more useful and hence more 
annoying than the ones that you have chosen, since it is always possible to 
disable check_range at runtime.  Perhaps start with values from exf_fields.h, 
including an asymetric hflux and for swdown and lwdown, then gradually relax 
these values as valid complaints start pouring in?

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