[MITgcm-support] advection of passive AND active tracers

[Martin Losch]

Hi again,
I have made an interesting discovery while trying to turn off advection 
for the passive tracers package:
When I include a runtime flag, analogous to tempAdvection or 
saltAdvection, for passive tracers, the tracer model explodes after a 
few time steps. With advection turned on (the default) everything is 
okay. I couldn't find the place where the passive tracer gets corrupted 
(it doesn't happen in ptracers_integrate, ptracers_advection, nor in 
ptracers_forcing. cycle_tracer and timestep_tracer are not the source 
of error either.)
But now this:
I turned off tempAdvection and saltAdvection (linear equation of state 
so that salt is passive as well), and you know what, the model 
explodes, too.

advection schemes are 2 (cented 2nd order) for theta and salt and 33 
(DST3FL) for the passive tracer package, but that shouldn't matter, 
should it?

Any idea, what's going on?

Martin

Martin Losch // mailto:mlosch at awi-bremerhaven.de
Alfred-Wegener-Institut für Polar- und Meeresforschung
Postfach 120161, 27515 Bremerhaven, Germany
Tel./Fax: ++49(471)4831-1872