[Mitgcm-support] RE: kpp and ptracers

[mitgcm-support at dev.mitgcm.org]

Go for it - if it breaks anything we'll scream.

A.

> -----Original Message-----
> From: Martin Losch [mailto:mlosch at awi-bremerhaven.de]
> Sent: Tuesday, May 13, 2003 10:10 AM
> To: support at mitgcm.org
> Subject: Re: kpp and ptracers
> 
> 
> Here is what I can offer (appart from the first block):
> 
> o fix of ptracers_write_checkpoint.F (already checked in)
> o modify gad_calc_rhs so that it works with a passive tracer
> (add this 
> above the  Ooops! statement:
> #ifdef ALLOW_PTRACERS
>         ELSEIF (tracerIdentity.EQ.GAD_TR1) THEN
>          CALL KPP_TRANSPORT_PTR(
>       I     iMin,iMax,jMin,jMax,bi,bj,k,km1,
>       I     KappaRT,
>       U     df )
> #endif
> and add the routine KPP_TRANSPORT_PRT to the KPP-package
> 
> This will still use KappaRS as the the diffusivity for all passive
> tracers, but it will make the two packages work together.
> 
> If you prefer to keep the current state, that's fine with me.
> 
> Martin
> 
> support at mitgcm.org wrote:
> > Martin,
> > 
> > The first block seems fine.
> > 
> > KPP/ptracers are currently hacked to work together. The
> reason being
> > that each tracer needs it's own diffusivity and it's too
> cumbersome to
> > pass all these around through the ptracer code. We're using
> the salt
> > diffusivity for tracers. Part of the "tidy up" plan is to replace
> > these with a diffusivity by process which the ptracer 
> package can then
> > use properly. The tidy up is scheduled for September.
> > 
> > A.
> > 
> > 
> >>-----Original Message-----
> >>From: Martin Losch [mailto:mlosch at awi-bremerhaven.de]
> >>Sent: Monday, May 12, 2003 11:27 AM
> >>To: support at mitgcm.org
> >>Subject: kpp and ptracers
> >>
> >>
> >>Hi,
> >>
> >>I have a few small things to check in, and wanted to make
> sure that I
> >>don't interfere with anything:
> >>- kpp_do_diags.F: support multiple record files (analogous to 
> >>write_state.F, so far, only global files are written)
> >>- solve_for_pressure.F: reduce the output of cg3d-related
> >>stuff to the 
> >>monitor frequency, analogous to the cg2d-related output.
> >>
> >>- make kpp and ptracers work together, new routine and a few fixes.
> >>This is a little bigger and before I can do that I need to 
> understand
> >>the ptracers/kpp-code correctly:
> >>1) the vertical diffusivity PTRACERS_diffKr is never used, is it?
> >>2) instead gad_calc_rhs is called with KappaRS from
> >>thermodynamics via 
> >>ptracers_integrate (and for ALLOW_PASSIVE_TRACER, it is 
> KappaRT, very
> >>strange!)
> >>3) the countergradient velocity ghat is the same for all
> >>tracers (T,S,...)?
> >>4) has the ptracers package ever been tested? there is no real 
> >>verification experiment for that, global_ocean.90x40x15 
> >>doesn't count, 
> >>does it?
> >>
> >>Is there a reason for the missing checkpoint50c_post?
> >>
> >>Martin
> >>--
> >>Martin Losch
> >>Alfred Wegener Institute for Polar and Marine Research Postfach
> >>120161, 27515 Bremerhaven, Germany;
> >>Tel./Fax: ++49(0471)4831-1872/1797
> >>
> >>
> > 
> > 
> 
> 
> --
> Martin Losch
> Alfred Wegener Institute for Polar and Marine Research
> Postfach 120161, 27515 Bremerhaven, Germany;
> Tel./Fax: ++49(0471)4831-1872/1797
> 
>