[MITgcm-support] Forcing files in data.dic (biogeochemistry)

[Jonny Williams]

Hi there

I am currently trying to incorporate the GCHEM, PTRACERS and DIC packages
into my setup of the MITgcm. I already have it successfully working in
regional model using the OBCS and EXF forcing packages.

in the ~/MITgcm/verification/tutorial_global_oce_biogeo example, the
data.dic file calls for the following files in the DIC_FORCING namelist

&DIC_FORCING
  DIC_iceFile='fice.bin',
  DIC_windFile='tren_speed.bin',
  DIC_silicaFile='sillev1.bin',
 &

What I cannot work out however is what size these files should be in my
setup. From trial and error, I think the ice and wind files are monthly
climatologies (longitude x latitude x 12 months) and the sillev1 file
(silica data file, according to the manual
<http://mitgcm.org/public/r2_manual/latest/online_documents/manual.pdf>) is
of the form longitude x latitude x 15 levels.

Does anyone know what size they should be? Should they have the same number
of elements as the underlying grid, or is it staggered?

This raises a more generic issue in that clearly the binary input files are
not self-describing (like, say, NetCDF) and so having to reverse-engineer
what size forcing and boundary condition files should is not uncommon for
me.

I may well be going about this in the wrong way so any suggestions about
how to avoid this situation in future would be appreciated :)

Many thanks, as always

Jonny

-- 
Dr Jonny Williams
School of Geographical Sciences
University of Bristol
University Road
BS8 1SS

+44 (0)117 3318352
jonny.williams at bristol.ac.uk
bit.ly/jonnywilliams
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mitgcm.org/pipermail/mitgcm-support/attachments/20140730/f9f3a81c/attachment.htm>