[MITgcm-devel] Re: [MITgcm-cvs] MITgcm/pkg/diagnostics CVS Commit

[Jean-Michel Campin]

Hello Ed,

> For instance, Dimitris and I are trying to do monthly
> averages on his 510x510x6x50 cube setup and, if a run gets interrupted
> sometime during a month, then the monthly diagnostics average is wrong
> because the partial sums within qdiag aren't preserved.

I thought that each segment of this run was 6 month long
and then much longer than the 1 month time average period.

But anyway, it's checked-in. 
I don't know how it works (do you have at least one example
that restarts correctly the diagnosnostics ? I though the rule 
was to make sure it was working before checking in something) 
but I don't want to spend too much time on this.

I have other comments:
1) I just noticed that the efforts of making diagnostics "safer" 
(stopping when something was not set properly) are seriously 
back in question (It's in fact tricky to make sure that the
diagnostics restart correctly when you change data.diagnostics,
turn one package on/off, ... etc ...).
2) diagnostics_init_varia.F was 44 lines long, now has 171 lines.
Why not having a diagnostics_read_pickup.F (called within 
diagnostics_init_varia) ? (I remember we rise the same issue 
with CD-scheme pickup).

Jean-Michel