[MITgcm-devel] viscC4Leith on the cube

[Jean-Michel Campin]

Dimitri,

I checked that 
> useAreaViscLength=.TRUE.,
is really necessary.
The other one:
> sideDragFactor=0.,
is just to get the same results as before (but might be interesting 
to test).
And I've just seen that you made the "magic" conversion in
MITgcm_contrib/high_res_cube/input/data_hr
so this should be OK.

Baylor has also removed:
> useAnisotropicViscAgridMax
making it the default:
ini_parms.F:C     useAnisotropicViscAgridMax :: Changed to be default behavior.

See you,

Jean-Michel

On Tue, Dec 13, 2005 at 04:36:47PM -0800, Dimitris Menemenlis wrote:
> Jean-Michel and Baylor, here is part II of message regarding problem 
> with viscC4Leith on the cube.
> 
> You can reproduce the problem using the experiment in 
> verification/global_ocean.cs32x15/input
> by adding "viscC4Leith=1.0," to the data file.
> 
> For checkpoint57s_post, this works fine (after setting OLx=OLy=3).
> 
> For checkpoint57t_post, the integration bombs during the first time 
> step, even for deltat=1.
> 
> Dimitris
> 
> -- 
> Dimitris Menemenlis <menemenlis at jpl.nasa.gov>
> Jet Propulsion Lab, California Institute of Technology
> MS 300-323, 4800 Oak Grove Dr, Pasadena CA 91109-8099
> tel: 818-354-1656;  fax: 818-393-6720
> _______________________________________________
> MITgcm-devel mailing list
> MITgcm-devel at mitgcm.org
> http://mitgcm.org/mailman/listinfo/mitgcm-devel