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

[Ed Hill]

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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <http://mitgcm.org/pipermail/mitgcm-devel/attachments/20040319/85340dc0/attachment.sig>