[MITgcm-devel] another stop in seaice_check: mcPheePiston

[Gael Forget]

Hi Martin,
unless I am mistaken this a useful stability and sanity requirement. It may be 
easiest to see with the corresponding check for SEAICE_frazilFrac (adimensional).
Beyond 1. seaice_growth would overshoot the freezing point (go below it in the McPhee case).
I suppose < 2. (rather than <=1.) would be enough for strict stability, but I dont see why we would 
want to overshoot / bounce around the freezing point (as would happen for 1.< frac < 2. I think). 
Cheers,
there ;)


On Mar 9, 2012, at 9:27 AM, Martin Losch wrote:

> Hi there,
> 
> I just ran across another check that made the model stop in seaice_check:
> when the default
>      SEAICE_mcPheePiston  =
>     &      MCPHEE_TAPER_FAC * STANTON_NUMBER * USTAR_BASE
> = 8.4000e-04 m/s
> is larger than SEAICE_mcphee_max=dRf(kSurface)/SEAICE_deltaTtherm
> the model stops. This happens to me for my very coarse cs32 experiment (basically global_ocean.cs32 with seaice), when I use the default parameters, because in this configuration dz/dt =  50m/86400s = 5.7870e-04 m/s.
> 
> Is this a useful stop? Why shouldn't mcPheePiston be larger than dz/dt? Please advise and possibly correct seaice_check.F
> 
> Martin
> 
> 
> 
> 
> 
> _______________________________________________
> MITgcm-devel mailing list
> MITgcm-devel at mitgcm.org
> http://mitgcm.org/mailman/listinfo/mitgcm-devel