[MITgcm-devel] recovering SEAICE_availHeatFrac behavior with McPhee parameters

[Martin Losch]

Interesting. what does "size mitgcmuv" say?
which compiler do you use? I have 
run> size ../build/mitgcmuv
__TEXT	__DATA	__OBJC	others	dec	hex
3407872	160079872	0	4295045120	4458532864	109bfd000
so more than 4GB. Where does that come from? Version of gfortran?
run> gfortran -v
Using built-in specs.
COLLECT_GCC=gfortran
COLLECT_LTO_WRAPPER=/usr/local/libexec/gcc/x86_64-apple-darwin10.4.0/4.6.0/lto-wrapper
Target: x86_64-apple-darwin10.4.0
Configured with: ../gcc-4.6-20101106/configure --enable-languages=c++,fortran
Thread model: posix
gcc version 4.6.0 20101106 (experimental) (GCC) 


M.

On Mar 13, 2012, at 4:53 PM, Menemenlis, Dimitris (3248) wrote:

> 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
> 
> 
> _______________________________________________
> MITgcm-devel mailing list
> MITgcm-devel at mitgcm.org
> http://mitgcm.org/mailman/listinfo/mitgcm-devel