[MITgcm-support] diagnostic errors

[Andrea Molod]

hi matt,

> I have used the diagnostics package many times before without problems, but my
> last run I recieved the errors:
>
> (PID.TID 0000.0001) WARNING DIAGNOSTICS_OUT  => write ZEROS instead
> (PID.TID 0000.0001) - WARNING - from DIAGNOSTICS_OUT at iter=      1460
> (PID.TID 0000.0001) - WARNING -   diag.#  23 : ETAN     (#  1 ) in outp.Stream:
> ETAN_bar
> (PID.TID 0000.0001) - WARNING -   has not been filled (ndiag= 0 )
> (PID.TID 0000.0001) WARNING DIAGNOSTICS_OUT  => write ZEROS instead
> (PID.TID 0000.0001) - WARNING - from DIAGNOSTICS_OUT at iter=      1460
> (PID.TID 0000.0001) - WARNING -   diag.#  30 : UVEL     (#  1 ) in outp.Stream:
> UVvelbar
> (PID.TID 0000.0001) - WARNING -   has not been filled (ndiag= 0 )
> (PID.TID 0000.0001) WARNING DIAGNOSTICS_OUT  => write ZEROS instead
> (PID.TID 0000.0001) - WARNING - from DIAGNOSTICS_OUT at iter=      1460
> (PID.TID 0000.0001) - WARNING -   diag.#  31 : VVEL     (#  2 ) in outp.Stream:
> UVvelbar
> (PID.TID 0000.0001) - WARNING -   has not been filled (ndiag= 0 )
> .....etc....

this error message is telling you that the diagnostic is 'turned on' 
properly, that is, the model has read your data.diagnostics and determined
that there is enough space, etc..., but that the call to fill it never
happened.


> I have changed a few things in my setup, but cannot determine where this error
> arises from.  Could someone please tell me how this may have happened...

hard (impossible for me) to even begin to think about what is the problem 
unless you let us know what your experiment config is and what things you 
have changed in your setup. even better - can you tell us where to find 
the STDOUT(s) from your run to see what's happening there?

> and in data.diagnostics I have
>
> &diagnostics_list
> #---
>  frequency(1) = 2628000.0,
>   levels(1,1) = 1.,
>   fields(1,1) = 'ETAN    ',
>   filename(1) = 'ETAN_bar',
> #---
>  frequency(2) = 2628000.0,
>   fields(1,2) = 'UVEL    ','VVEL    ',
>   filename(2) = 'UVvelbar',
> #---


this seems ok to me.

one more peice of info, if you could... how long ago did you 'update' your
code and recompile to make this run?

thanks, and hope i can be more help with more info.

andrea