[MITgcm-devel] (not so) funny things happen in seaice_lsr and pickups

[Martin Losch]

Dimitris,

I like option 2 best. Especially, since my fixes to the metric terms  
will affect some of the experiments anyway (e.g. lab_sea).

Another thing is this parameter SEAICE_zetaMin, which defaults to zero  
right now. Originally there was a miniumum zeta (ZMIN=4e8), which I  
removed following Jinlun's advice (Jinlun: please correct me if I am  
wrong). I "feel" that this parameter may have an impact on my  
problems, too. As far as I remember, it should not be necessary for  
stability reasons, but the these large gradients of P/eta/zeta, it  
would actually help. I guess Jinlun will maintain, that I should keep  
looking for a bug in the code, right? (o:

Martin
On Mar 4, 2009, at 9:38 PM, Dimitris Menemenlis wrote:

> Martin and Jean-Michel, shall we:
>
> 1) make SEAICE_clipVelocities=.false. the default and change  
> verification output accordingly,
>
> 2) make SEAICE_clipVelocities=.false. the default but set to .true.  
> in the verification experiments for backward compatibility ... with  
> a warning that clipping should not be used, or
>
> 3) leave things as is?
>
> There are two verification experiments that are affected by  
> SEAICE_clipVelocities:
>
> SEAICE_clipVelocities=.true.
> Y Y Y Y>16<16 16 16 16 16 16 16 16 16 16 16 16 16 16 16 16 pass   
> global_ocean.cs32x15.icedyn
> Y Y Y Y> 6<12 12  9 10 16 14 10  9 10 10  7  6  8 10  7  6 FAIL   
> lab_sea.salt_plume
>
> SEAICE_clipVelocities=.false.
> Y Y Y Y> 8<14 16 13 14 16 16 14 13 13 16 12 13 13 13 11 13 FAIL   
> global_ocean.cs32x15.icedyn
> Y Y Y Y> 5<11 11  8  8 12 13 10  8  8  7  6  6  5  6  6  6 FAIL   
> lab_sea.salt_plume
>
> D.
>
> On Mar 4, 2009, at 11:55 AM, Martin Losch wrote:
>
>> we don't need to take it out, we just need to specify a flag  
>> (SEAICE_clipVelocities=.false.),
>
> _______________________________________________
> MITgcm-devel mailing list
> MITgcm-devel at mitgcm.org
> http://mitgcm.org/mailman/listinfo/mitgcm-devel