[MITgcm-support] Re: Starting with MITgcm
Matthew Mazloff
mmazloff at MIT.EDU
Fri Aug 19 11:30:07 EDT 2005
Hi Matej,
As Ed said, the verification experiments have matlab scripts that
describe preperation of input files.
For example, in
MITgcm / verification / exp5 / input / gendata.m
a surface forcing file is made:
Q=Qo*(1+0.01*rand([nx,ny]));
it is size [nx,ny]
if it were 3-d (e.g. and initial theta file) it would be size [nx,ny,nz]
then it is written with
fid=fopen('Qnet.circle','w','b');
fwrite(fid,Q,'real*8');
fclose(fid);
The data is written by fwrite down the matrix columns.
it is written translated into real*8 because the mitgcm data file given
in the verification experiment has
readBinaryPrec=64,
it is read in as a surface heating file by putting
# Input datasets
&PARM05
surfQfile='Qnet.circle',
&
in the data file
other possible initial files you can give the model are (as seen in
MITgcm / model / src / ini_parms.F )
C-- Input files
NAMELIST /PARM05/
& bathyFile, topoFile,
& hydrogThetaFile, hydrogSaltFile,
& zonalWindFile, meridWindFile,
& thetaClimFile, saltClimFile,
& surfQfile, surfQnetFile, surfQswFile, EmPmRfile, saltFluxFile,
& lambdaThetaFile, lambdaSaltFile,
& uVelInitFile, vVelInitFile, pSurfInitFile,
& dQdTFile, ploadFile,tCylIn,tCylOut,
& eddyTauxFile, eddyTauyFile,
& mdsioLocalDir,
& the_run_name
CEOP
-matt
Ed Hill wrote:
>== Original message ==
>Hi!
>
>I'd like to compare couple of 3D models. I have a study case - an
>open box with inflow in one corner and outflow in diametral corner of
>that box. I've been makeing quite some reading through the MITgcm
>User Manual and web pages, tried also some verification cases,
>provided by CVS, but I still have a hard time figuring out how to
>prepare input data for my box. I'd be pleased if someone could give
>me some directions about where to search for the structure of input
>files. Maybe it's just well hidden in the User Manual, but I'd be
>very thankful for helping me through the first steps.
>
>Matej Brecelj
>== Original message ==
>
>
>Hi Matej,
>
>I think the above email was sent before you subscribed to this list, so
>our mailman software withheld it. In any case, its copied above.
>
>MITgcm input files are mostly raw binary files written at either 32bit
>(REAL*4) or 64-bit (REAL*8) precision. Some of the experiments in
>MITgcm/verification include matlab scripts that demonstrate how to read
>and write the necessary data:
>
> cd MITgcm/verification
> find . -name \*.m
>
>and people on this list can help you with formats for specific files.
>
>Ed
>
>
>
More information about the MITgcm-support
mailing list