[MITgcm-support] Re: Restart after changing deltatT

[samar khatiwala]

Hi Jean-Michel

On Thu, 5 May 2005, Jean-Michel Campin wrote:

> If I understand correctly, you are starting from t=5000.y
> (nIter0=3600000, deltaT=1200, basetime=151200000000
>  => startTime=155520000000 = 5000.y) and you set the
> pChkptFreq to 15.y ;
> the 1rst multiple of 15.y after t=5000.y is t=5010.y,
> and it's what you get. Is it right ?

That is indeed correct, and I see what you are getting at, but its
obviously not the behavior I was expecting. Shouldn't model time
be measured relative to baseTime (or perhaps startTime). In which case
t=(5015-5000)=15 is a multiple of 15 y. Based on what you are saying, it
would appear that the correct dumps I now get is simply fortituous!
If I had picked a dump freq of 6 years as opposed to 5 years,
I'd be back to square one.

For now, I am going to fudge by setting nIter=0, renaming the pickup
files, and setting pickupsuff in data.

Samar

>
> If you want to check what are the values of those params,
> they are written out in the standard output.
>
> Jean-Michel
>
> On Thu, May 05, 2005 at 10:46:28AM -0400, samar khatiwala wrote:
> > Hi Jean-Michel
> >
> > Your fix to diff_base_multiple.F seems to have worked (but see below). The
> > dumps are now being written at the expected frequency (including the
> > initial iteration). So I have dumps at:
> > 0003600000 t=0
> > 0003729600 t=5 year
> > 0003859200 t=10 year
> > (and hopefully one final one at year 15)
> >
> > However, the pickup is still not right. I have pChkptFreq= 466560000.
> > (corresponding to 15 years), but instead I get a pickup at
> > iter = 0003859200 which is year 10.
> >
> > Since my run is only 15 years long (max I can do with the wall clock limit
> > on our cluster), I will probably not get the final pickup I wanted.
> >
> > Help!!
> >
> > Thanks, Samar
> >
> _______________________________________________
> MITgcm-support mailing list
> MITgcm-support at mitgcm.org
> http://mitgcm.org/mailman/listinfo/mitgcm-support
>