[MITgcm-devel] timeave
Martin Losch
mlosch at awi-bremerhaven.de
Thu Mar 3 04:34:21 EST 2005
Hi,
something is fishy with the timeave-pkg. I can't quite figure out why
things go wrong, but here is what happens:
u/v/t/sFluxtave are not normalized by the averaging period, the reason
being that timeave_full is zero in timeave_stats_write, whereas
timeave_half is correct (as far as I can see).
timeave_full is computed in timeave_statvars, but if I set taveFreq=1.
it is never set (because timeave_stats_write is always called with
myiter=niter0, JMC's "dirty" trick, if I remember correctly). however,
at the end of timeave_statvars, DDTT = 0.5 deltaTclock, timeave_half =
deltaTclock, timeave_full = 0.5 deltaTclock.
I have no clue what's going on.
does anybody have an idea?
Martin
PS. is timeave still supported or should I learn to used diagnostics?
More information about the MITgcm-devel
mailing list