[MITgcm-devel] global_ocean.cs32x15/input.icedyn

[Martin Losch]

Good morning Jean-Michel,

I am a little puzzled by your new experiment
1. I made a small change (bug fix, not yet checked in), that only  
affecteds metric terms in seaice_lsr.F (all involve tanPhiAtU), but  
still global_ocean.cs32x15/input.icedyn.
How is that possible, I thought that with usingCurvilinearGrid  
= .true., all tanPhiAtU/V = 0?

2. This experiment is extremely sensitive, right? This is what I get  
on my Apple with g77
Y Y Y Y 11 13 13 14 16 16 16 16 16 13 13 14 16 16 13 14 16 FAIL   
global_ocean.cs32x15
Y Y Y Y  2  2 13  7  7 13 14  9  6 10 10  4  6 10 10  5  6 FAIL   
global_ocean.cs32x15.icedyn
Y Y Y Y 11 16 16 16 16 16 16 16 16 13 13 14 16 13 13 14 16 FAIL   
global_ocean.cs32x15.thsice
Y Y Y Y 10 16 16 16 16 16 16 16 16 13 13 13 16 13 13 13 16 FAIL   
global_ocean.cs32x15.viscA4

3. Have made changes that affect lab_sea at the truncation level  
(rearrange a few terms), that is cg2d is accurated to 13 digits, but  
global_ocean.cs32x15.icedyn fails with 2!

I also found a serious bug in the LSR solver that will affect all LSR  
results dramatically. Now,
shall I just check in all of the above (small bug only affecting  
metric terms, big bug affecting everything, and rearrangement of  
terms affecting truncation, which really changes  
global_ocean.cs32x15.icedyn) at the same time, glossing over all  
subtelties?

Martin