[MITgcm-support] Diagnostics have not been filled

Bertrand Louis Rene Delorme bdelorme at stanford.edu
Tue Jul 10 11:41:47 EDT 2018


Salut Pascal,

I am not sure about the “momVort3” diagnostic: have you tried to compute this term yourself with UVEL and VVEL to see what solution you get? For the “DFrI_TH” diagnostic, maybe your vertical diffusivity is just constant everywhere?

Cheers,
Bertrand


De : MITgcm-support <mitgcm-support-bounces at mitgcm.org> au nom de Pascal Bourgault <pascal.bourgault at gmail.com>
Répondre à : "mitgcm-support at mitgcm.org" <mitgcm-support at mitgcm.org>
Date : mardi 10 juillet 2018 à 8:07 AM
À : "mitgcm-support at mitgcm.org" <mitgcm-support at mitgcm.org>
Objet : [MITgcm-support] Diagnostics have not been filled

Hi,
In my data.diagnostics, I ask the model to output the "momVort3" and the "DFrI_TH" diagnostic, and many others. I am using mpi and the following packages are compiled in my mitgcmuv : gfp, flt, mnc, mdsio. Also, momVort3 and DFrI_TH both appear in the available_diagnostics.log file.

However, the output values for those are all zeros in the final files. For example, in my dynDiag*.nc files, where I save UVEL, VVEL, WVEL and momVort3, the three velocities look good, but momVort3 is only zeros.
In the STDERR.* of the model I have this
"""
(PID.TID 0000.0001) - WARNING - from DIAGNOSTICS_OUT at iter=     17286
(PID.TID 0000.0001) - WARNING -   diag.#   117 : DFrI_TH  (#   7 ) in outp.Stream: tempDiag
(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=     17286
(PID.TID 0000.0001) - WARNING -   diag.#   174 : momVort3 (#   4 ) in outp.Stream: dynDiag
(PID.TID 0000.0001) - WARNING -   has not been filled (ndiag=  0 )
 """
repeating numberous times.
Are there some options in some *_OPTIONS.h files I need to turn on to save those fields? I don't really understand the error...
I can provide any other config info needed, I just don't know what is useful in this case...
Thanks!

--
Pascal

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.mitgcm.org/pipermail/mitgcm-support/attachments/20180710/8c9de53f/attachment.html>


More information about the MITgcm-support mailing list