[MITgcm-devel] initialization of MNC -- where and when?

[Alistair Adcroft]

Concerning where MNC is initialized.  JMC and I were talking a few weeks ago
and it seems clear that there are two kinds of packages - equation related
packages (gmredi, kpp, exf, ...) and infra-structure related packages
(mdsio, mnc, exch2, ...).

I would be happy to introduce a different initialization procedure for *all*
the infrastructure related packages to deal with Ed's point about MNC
initialization. It also fixes the exch2 initialization.   Are there any
packages which would not be easily classified and cause a heated debate
about where it belongs?

We would have initialize_ee_packages() for MNC, MDSIO, EXCH2, ... called
from ee_boot() or where ever is appropriate. We would need to agree to
control these packages from eedata
Unless we read data.pkg twice.

I don't see a need to separate pkg into two directories although this could
be done also: e.g. ee_pkg/ and pkg/ or something like it.

A.
--
Dr Alistair Adcroft            http://www.mit.edu/~adcroft
MIT Climate Modeling Initiative        tel: (617) 253-5938
EAPS 54-1523,  77 Massachusetts Ave,  Cambridge,  MA,  USA

-----Original Message-----
From: mitgcm-devel-bounces at mitgcm.org
[mailto:mitgcm-devel-bounces at mitgcm.org] On Behalf Of Ed Hill
Sent: Friday, March 19, 2004 11:03 AM
To: MITgcm-devel
Subject: [MITgcm-devel] initialization of MNC -- where and when?



Hi folks,

I'm working on the to-do list from the last meeting:

  http://mitgcm.org/R2wiki/MeetingNotes20040317

and have two requests for clarification:

 1) (this is mostly for Alistair:)  I'm not sure I understand the 
    what you want in regards to splitting off the specification of 
    the unlimited dimension into a separate subroutine or global
    variable(s).  The problems as I see them are:

      (a) unlimited dim is intrinsically per-file, and
      (b) the mnc_cw_* functions are not per-file, they are 
          actually per-file-group.

    So would someone (Alistair?) please write some pseudo-code 
    (or even just a quick sketch on a white-board) to explain 
    what you want?

 2) Unlike almost every other package, MNC *must* be initialized
    very early in the startup sequence.  Initializing MNC in the 
    normal package locations:

      model/src/packages_boot.F
      model/src/packages_readparms.F

    is too late if you want to, for instance, use MNC to read grid 
    information in:

      model/src/initialise_fixed.F

    So I'd like to propose that MNC is initialized and reads its 
    runtime flags within:

      eesupp/src/eeset_parms.F

    Or can anyone suggest a better way?

thanks!
Ed

-- 
Edward H. Hill III, PhD
office:  MIT Dept. of EAPS;  Room 54-1424;  77 Massachusetts Ave.
            Cambridge, MA 02139-4307
email:   eh3 at mit.edu,  ed at eh3.com
URL:     http://web.mit.edu/eh3/
phone:   617-253-0098
fax:     617-253-4464