[MITgcm-support] Time variable and changing deltaT

[Jean-Michel Campin]

Hi Andrea,

There are few previous messages to the support list that discuss
this issue, for instance:
http://mitgcm.org/pipermail/mitgcm-support/2005-May/003040.html

I also agree that the default behavior of the code when you try  
to restart with a different deltaT is not always what one would expect,
but different users might expect different things. 
In short, we could have changed the default behavior (adjusting baseTime), 
but then some users would have found it annoying that what was working before 
does not work the same way anymore.

Note that if the time-step (deltaTclock) was stored in the netcdf pickup
file or in the pickup meta file, we would be in a better position to
set the default baseTime in a safe way.

Cheers,
Jean-Michel

On Fri, Nov 02, 2012 at 10:13:29AM +0000, cimatori wrote:
> Hi everybody,
> I just noticed a "funny" behaviour of MITgcm: basically, after
> spinning up the model for some time, I restarted it with a different
> time step (longer), using netcdf restart files. If I now look at the
> output of the new run, I see that while the number of iterations
> continues its count correctly, the time variable stored in the
> output is wrong, as it contains times that are just the (number of
> iterations) x (new time step), while it should obviously be (restart
> time) + (number of iterations - restart iteration) x (new time
> step). Put this way, this looks a lot like a bug, but maybe there is
> a reason for this behaviour. Any idea? I'm using netcdf output at
> the moment, if it makes any difference.
> Thanks,
> 
> -- 
> 
> Andrea Cimatoribus
> Royal Netherlands Meteorological Institute
> www.knmi.nl/~cimatori
> 
> 
> _______________________________________________
> MITgcm-support mailing list
> MITgcm-support at mitgcm.org
> http://mitgcm.org/mailman/listinfo/mitgcm-support