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

Ed Hill ed at eh3.com
Fri Mar 19 12:04:38 EST 2004


On Fri, 2004-03-19 at 11:39, Alistair Adcroft wrote:
> 
> 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?

Good!  I think this would be a real improvement.


> 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 vote that we control them from eedata.  And I'll check-in an
initialize_ee_packages() ASAP.


> 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.

Yeah, I agree that ee_pkg/ is unnecessary.

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/5613893f/attachment.sig>


More information about the MITgcm-devel mailing list