[MITgcm-devel] RE: [MITgcm-cvs] putting mnc init in fizhi (and land)
Chris Hill
cnh at mit.edu
Fri Jul 9 09:34:03 EDT 2004
mnc shouldn't know about fizhi. mnc is meant to be a general purpose utility
layer.
i.e. we should have things looking
for diagnostics
fizhi ==> diagnostics ===> write date ===> mnc
or
===> mdsio
for field I/O
fizhi ===> read/write data ===> mnc
or
===> mdsio
chris
> -----Original Message-----
> From: mitgcm-cvs-bounces at mitgcm.org
> [mailto:mitgcm-cvs-bounces at mitgcm.org] On Behalf Of Andrea Molod
> Sent: Friday, July 09, 2004 8:03 AM
> To: mitgcm-devel at mitgcm.org
> Cc: mitgcm-cvs at mitgcm.org
> Subject: [MITgcm-cvs] putting mnc init in fizhi (and land)
>
> hi ed,
> you asked to have this stuff sent to the devel list, you got it.
>
> my understanding of the conversation with JM and you and
> myself about where to initialize some of the package
> dependant mnc stuff is that we ended up seeing that it SHOULD
> NOT be done inside the package, but needs to be in mnc and/or
> the diagnostics if the mnc stuff is only for diagnostics.
> (JM, do you recall???)
>
> and structurally, i frankly can't see any reason why fizhi
> for instance has to know whether the diagnostics in the end
> will be output with mnc or mdsio. the same may go for the
> land. can you imagine putting mnc init stuff inside of every
> package that has its own size (or other) parameters that mnc
> has to know about?
> that to me seems to be part of the functionality inside mnc....
>
> so - maybe fizhi_mnc_init should be in mnc, with fizhi ifdefs
> around it.
>
> as for the land part, if the mnc init stuff MUST go in the
> land package, at a minimum shouldn't it be ifdef'd with mnc package?
>
> oh yeah - WHAT is FIZHI_OPTIONS.h doing?
>
> andrea
>
>
> On Thu, 8 Jul 2004, Ed Hill wrote:
>
> > Added Files:
> > FIZHI_OPTIONS.h fizhi_mnc_init.F
> > Log Message:
> > o remove the "Nphys"-related MNC grid type definitions from MNC
> > and place them in the fizhi package per the discussions
> > with AM and JMC
> > o the code compiles cleanly but has not been run o the two files
> > added to fizhi do not (yet) interact with any of the
> > other fizhi routines--no changes to existing fizhi code
>
> _______________________________________________
> MITgcm-cvs mailing list
> MITgcm-cvs at mitgcm.org
> http://dev.mitgcm.org/mailman/listinfo/mitgcm-cvs
>
More information about the MITgcm-devel
mailing list