[MITgcm-support] diagnostics at last timestep

[Jean-Michel Campin]

Hi,

Just for clarity:
The ability to write output at the last iteration
(setting dumpAtLast=True) is implemented for time
average diagnostic (positive frequency), with, among others,
the idea that if you stop the simulation between 2 write,
you don't loose the last (incomplete) time averaged.
It's not implemented for snap-shot (negative frequency),
relying on the assumption that the output frequency and phase
which the user selected represent accurately what he wanted.

An other reason (relevant for state variable like UVEL)
is that the final state is not available (because no filling
of the big diagnostics array is done at the end of a run),
so that it take out one of the potential advantages of
having a snap-shot diagnostics written at the end if
dumpAtLast=T. In other words, the pkg/diagnostics does
not replace snap-shot output of state variables (more efficient
to write it directly) and specially the last one (not
available with pkg/diagnostics).

Cheers,
Jean-Michel

On Thu, Mar 01, 2007 at 06:20:17PM +0100, Martin Losch wrote:
> Hi there,
> 
> I can't make the diagnostics package dump a snapshot of a diagnostics  
> variable, say UVEL, at the last time step. I have tried all sorts of  
> things:
> frequency(1) = -3600.,
> timePhase(1)= 0.,3600., nothing
> dumpAtLast = .true.,
> but nothing works and I don't get output for the last timestep (which  
> is at a multiple of 3600.sec of course). For time averaged quantities  
> (frequency>0) it seems to work.
> What have I overlooked?
> 
> Martin
> _______________________________________________
> MITgcm-support mailing list
> MITgcm-support at mitgcm.org
> http://mitgcm.org/mailman/listinfo/mitgcm-support