[MITgcm-support] timephase() in data.diagnostics

[Christoph Voelker]

Dear all,

I regularly use timephase(n) in data.diagnostics to limit the amount of
data that some of my diagnostic output produces; e.g. I run for 5 years,
but have output of three-dimensional fiels only over the last year.
Usually that works well.

But in a recent set-up it didn't work, i.e. despite the following
content in my data.diagnostics (I copy the lines from my STDOUT,
checking that my settings did arrive)

(PID.TID 0000.0001) >  frequency(1) = 2628000.,
(PID.TID 0000.0001) >  timePhase(1) = 126144000.,
(PID.TID 0000.0001) >  filename(1) = 'diag3Dm',
(PID.TID 0000.0001) >  fields(1,1) = 'SALT    ','THETA   ','UVEL   
','VVEL    ',
(PID.TID 0000.0001) >                'UVELMASS','VVELMASS',

the model wrote out monthly fields starting from the first model year. I
have a suspicion (but not more) with what this could be related:
Firstly, in this run, due to queue limitations, I first integrated only
four years (instead of the five that I wanted), and then wanted to
restart from pickup for the last year. Could it be that having the
timephase at the end (or later) of the current run creates a problem,
and that then the model switches back to default behaviour, i.e. setting
internally timePhase=0?

Cheers, Christoph

-- 
Christoph Voelker
Alfred Wegener Institute for Polar and Marine Research
Am Handelshafen 12
27570 Bremerhaven, Germany
e: Christoph.Voelker at awi.de
t: +49 471 4831 1848