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

[Jean-Michel Campin]

Hi Christoph,

Could you provide us the top of STDOUT.0000, down to:
(PID.TID 0000.0001) // Model current state
? will try to take a look at to figure out where the problem is.

Cheers,
Jean-Michel

On Fri, Sep 09, 2016 at 10:54:40AM +0200, Christoph Voelker wrote:
> 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
> 
> 
> _______________________________________________
> MITgcm-support mailing list
> MITgcm-support at mitgcm.org
> http://mitgcm.org/mailman/listinfo/mitgcm-support