[Mitgcm-support] Re: Top level arrays

[mitgcm-support at dev.mitgcm.org]

Hi Jean-Michel,

Quoting Jean-Michel Campin <jmc at gulf.mit.edu>:

> Hi patrick,
> 
> > means that theses arrays are always there even when
> > customized versions of load_external_fields.F change the
> > shape/size of those 0/1 arrays. J-M is upset because the size
> > of his runs increased dramatically when you put this in. He
> > has customized versions of that routine. 
> 
> Just to make things clear:
> I am not really "upset". I understand that 
> it's difficult to make things working with so many 
> options and pkg and so on.
> But it's also good to known what part of the code is meant 
> to be customized ; and to stick to this general idea.
> And all thoses arrays are a little misleading when 
> running atmosphere config (because there are already 
> SST arrays (0/1) defined for the atmosphere: aim_sst0,1 
> that are, of course, different from SST0 & SST1).
> 
> BTW, I really want to see checkpoint48 done soon.
> (because I would like to start to change the results and break
> of lot of test-exp. hoops, I was not supposed to tell it !).
> And FFIELDS.h can be changed after, if a better solution can
> be found.

Maybe all that is needed is a customized FFIELDS.h
to go along with its customized external_fields_load.F

> So, if no objection, I will go for checkpoint48 tomorrow morning.
> 
> Is it OK for you Patrick ?

OK with me.

-Patrick