[MITgcm-devel] recovering SEAICE_availHeatFrac behavior with McPhee parameters

[Menemenlis, Dimitris (3248)]

Gael and Jean-Michel, thanks very much for replies.

I am experimenting with updated sea ice code on my baby-Beaufort set-up:
http://mitgcm.org/viewvc/MITgcm/MITgcm_contrib/MPMice/beaufort/

Incidentally (for Torge, Martin, and Patrick), I can run multiple copies
of the Beaufort experiment on my 4-yr-old, 4-GB Macbook Pro.
Each copy requires ~100 MB of memory.  Strange that it would
run out of memory on newer Mac hardware?

Dimitris Menemenlis

On Mar 13, 2012, at 6:47 AM, Jean-Michel Campin wrote:

> Hi Dimitris,
> 
> SEAICE_availHeatFrac has not been removed yet, so you can continue
> to put it in data.seaice and it will act as before.
> Note also that the old default for SEAICE_availHeatFracFrz has
> been maintained: if none of the 3 params: SEAICE_frazilFrac, 
> SEAICE_availHeatFracFrz, SEAICE_gamma_t_frz is specified,
> and SEAICE_availHeatFrac is set, then SEAICE_availHeatFrac
> is also used to set SEAICE_frazilFrac.
> 
> Cheers,
> Jean-Michel
> 
> On Mon, Mar 12, 2012 at 07:24:57PM -0700, Menemenlis, Dimitris (3248) wrote:
>> Gael or Martin, is there a way to recover SEAICE_availHeatFrac behavior with McPhee parameters?
>> 
>> I thought this was discussed at some point in time, maybe even in the devel list, but I can't find.
>> 
>> I know that SEAICE_availHeatFrac=1 is discussed in seaice_check.F, but what
>> about arbitrary values of SEAICE_availHeatFrac?
>> 
>> Thanks
>> 
>> Dimitris Menemenlis
>> 
>> 
>> _______________________________________________
>> MITgcm-devel mailing list
>> MITgcm-devel at mitgcm.org
>> http://mitgcm.org/mailman/listinfo/mitgcm-devel
> 
> _______________________________________________
> MITgcm-devel mailing list
> MITgcm-devel at mitgcm.org
> http://mitgcm.org/mailman/listinfo/mitgcm-devel