[MITgcm-devel] diagnostics and OpenAD

[Daniel Goldberg]

Hello

Very recently I had a look at diagnostics output from an OpenAD-compiled
experiment and the output was wrong -- based on what I looked at, it was
wrong, as follows. If my diagnostics file contains 2D fields, and the name
is given by surfDiag.0000000001.*, then when i read and plot in matlab, the
commands

q = rdmds('surfDiag');
contourf(q(2:2:end,2:2:end,1));

seems to plot out the bottom left half of the field in question. The other
entries of the matlab array are zero.

In terms of OpenAD, the field being plotted is Active. It seems as though
every other entry in the binary file is zeroed out. When I look in
diagnostics_fill_field.F, the input array is declared

_RL inpFldRL(*)

so presumably the S/R can be called with an array of type(active) -- and
instead of writing only the inpFldRL%v entries, the S/R just writes
sequential values, which include the %d entries.

Has anyone been successfully using the diagnostic package along with
OpenAD, where some of the diagnostic arrays are active? I'm sure there are
several workarounds, but I'd be very interested in the easiest...

Many thanks
Dan

-- 

Daniel Goldberg, PhD
Lecturer in Glaciology
School of Geosciences, University of Edinburgh
Geography Building, Drummond Street, Edinburgh EH8 9XP


em: D <dgoldber at mit.edu>an.Goldberg at ed.ac.uk
web: http://ocean.mit.edu/~dgoldberg
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mitgcm.org/pipermail/mitgcm-devel/attachments/20150127/d8ec1f15/attachment.htm>