[MITgcm-support] Re: problems with ptracer package

[Martin Losch]

Hi Dimitris,

this would probably explain my obvservations, but I am not sure right 
now, whether I set PTRACERS_diffK4 explicitly, or not, will try on 
Monday. I can't believe that I worked a full day on this, even after I 
had noticed that PTRACERS_diffK4 defaults to diffK4S! This is just 
typical of me ...

No, don't change back, I think it makes perfectly sense to use the 
horizontal diffusivities of salinity, since for variable KappaR (and 
for constant as well, right?), the vertical diffusivities are those of 
salinity as well. What do the code-czars think?

Is there a verification experiment that tests the passive tracers 
package? It might be useful to have one, probably in combination with 
the GCHEM-package.

Martin

On Friday, September 26, 2003, at 06:18 PM, Dimitris Menemenlis wrote:

> (oops, I didn't finish) ... using kappaRS.  There is no separate
> calc_diffusivity routine for the pkg/ptracers.  So I thought that
> reasonable initial values in ptracers_readparms would be:
>
>        PTRACERS_advScheme(iTracer)=saltAdvScheme
>        PTRACERS_diffKh(iTracer)=diffKhS
>        PTRACERS_diffK4(iTracer)=diffK4S
>        PTRACERS_diffKr(iTracer)=diffKrS
>
> rather than 0.  You can override these new default values by setting
> them explicitly in data.ptracers.  Or we can switch back to the old
> defaults in ptracers_readparms if these are causing you a headache?
>
> D.
>
>
> _______________________________________________
> MITgcm-support mailing list
> MITgcm-support at mitgcm.org
> http://dev.mitgcm.org/mailman/listinfo/mitgcm-support