[MITgcm-support] Keeping track of the amount of tracer removed by sponge layers

Fri Apr 10 07:02:16 EDT 2015

Hi Dan,

I never tried this, but I assume that your error is related to my suspicion that it may not work.

M.

> On 10 Apr 2015, at 12:57, Dan Jones <dcjones.work at gmail.com> wrote:
> 
> Hi Martin,
> 
> Thank you for your reply!  This archived post may be relevant (thanks, Renske):
> 
> http://mitgcm.org/pipermail/mitgcm-support/2014-August/009433.html
> 
> I could use the rbcs tracer tendency to get an estimate of the average amount of tracer removed.  I've just tried implementing this, and I've unfortunately been greeted by the error:
> (PID.TID 0000.0001) *** ERROR *** DIAGNOSTICS_SET_POINTERS: kLev= 16800 >  1680 =numLevels
> 
> (PID.TID 0000.0001) *** ERROR *** DIAGNOSTICS_SET_POINTERS: in setting levs of list l=   2, fnames=ForcTrac
> 
> Martin, does this error relate to the filling issue that you mentioned below, or do I simply have a parameter set incorrectly somewhere?
> 
> Thanks,
> Dan
> 
> 
> On Thu, Apr 9, 2015 at 5:00 PM, <mitgcm-support-request at mitgcm.org> wrote:
> Send MITgcm-support mailing list submissions to
>         mitgcm-support at mitgcm.org
> 
> To subscribe or unsubscribe via the World Wide Web, visit
>         http://mitgcm.org/mailman/listinfo/mitgcm-support
> or, via email, send a message with subject or body 'help' to
>         mitgcm-support-request at mitgcm.org
> 
> You can reach the person managing the list at
>         mitgcm-support-owner at mitgcm.org
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of MITgcm-support digest..."
> 
> 
> Today's Topics:
> 
>    1. Keeping track of the amount of tracer removed by  sponge
>       layers (Dan Jones)
>    2. Re: Keeping track of the amount of tracer removed by sponge
>       layers (Martin Losch)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Thu, 9 Apr 2015 09:18:22 +0100
> From: Dan Jones <dcjones.work at gmail.com>
> To: mitgcm-support at mitgcm.org
> Subject: [MITgcm-support] Keeping track of the amount of tracer
>         removed by      sponge layers
> Message-ID:
>         <CAPj3iHRcaY9K4Yp-O=odX36s9KT4KELUvKC+w++53kGJEosUMQ at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
> 
> Hi all,
> 
> I am using the rbcs package to implement a tracer-absorbing sponge layer in
> both (i.) the northern edge of my Southern Ocean model domain and (ii.) in
> the top 150 m.
> 
> Does anyone know of a good way to keep track of the amount of tracer
> removed at each grid cell by the sponge layers?  Ideally, I'd like to use
> the diagnostics package for consistency with my other output, but I didn't
> see an obvious choice in the available diagnostics log.
> 
> Thanks,
> Dan
> 
> ---------------------------------------------------------
> 
> Dr Dan Jones
> British Antarctic Survey, NERC
> Cambridge, UK
> 
> Phone: +44 (0)1223 221505
> Fax: +44 (0)1223 362616
> Skype:  dcjones.work
> 
> ---------------------------------------------------------
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://mitgcm.org/pipermail/mitgcm-support/attachments/20150409/f8662562/attachment.html>
> 
> ------------------------------
> 
> Message: 2
> Date: Thu, 9 Apr 2015 10:54:54 +0200
> From: Martin Losch <Martin.Losch at awi.de>
> To: MITgcm Support <mitgcm-support at mitgcm.org>
> Subject: Re: [MITgcm-support] Keeping track of the amount of tracer
>         removed by sponge layers
> Message-ID: <2BF587C7-7E9C-4367-A954-0D00BBCEFBA3 at awi.de>
> Content-Type: text/plain; charset="utf-8"
> 
> Hi Dan,
> 
> I don?t think that there is a predefined diagnostic that does that for you. But implementing your own diagnostics is really not so hard. You need to define it somewhere (I would do it in rbcs_init_fixed) and then compute the diagostics and ?fill? it by calling diagnostics_fill in rbcs_add_tendency. There are examples in almost every package of the model, often the diagnostics are defined in $pkg_diagnostics_init.F
> 
> There is one complication that I didn?t think off initially: rbcs_add_tendency is called per vertical level and diagnostics_fill may or may not be able to fill one vertical level at a time for a 3D diagnostic (never tried this but it may work by setting klev=k and nlev=1 for a 3D diagnostic). If it does not work, you may have to define an extra global 3D field in RBCS_FIELDS.h that you fill level by level in rbcs_add_tendency and then call diagnostics_fill with this 3D field somewhere from do_statevars_diags.F (there are examples how this is realized in other packages).
> 
> Hope that helps,
> 
> Martin
> 
> 
> > On 09 Apr 2015, at 10:18, Dan Jones <dcjones.work at gmail.com> wrote:
> >
> > Hi all,
> >
> > I am using the rbcs package to implement a tracer-absorbing sponge layer in both (i.) the northern edge of my Southern Ocean model domain and (ii.) in the top 150 m.
> >
> > Does anyone know of a good way to keep track of the amount of tracer removed at each grid cell by the sponge layers?  Ideally, I'd like to use the diagnostics package for consistency with my other output, but I didn't see an obvious choice in the available diagnostics log.
> >
> > Thanks,
> > Dan
> >
> > ---------------------------------------------------------
> >
> > Dr Dan Jones
> > British Antarctic Survey, NERC
> > Cambridge, UK
> >
> > Phone: +44 (0)1223 221505
> > Fax: +44 (0)1223 362616
> > Skype:  dcjones.work
> >
> > ---------------------------------------------------------
> > _______________________________________________
> > MITgcm-support mailing list
> > MITgcm-support at mitgcm.org
> > http://mitgcm.org/mailman/listinfo/mitgcm-support
> 
> 
> 
> 
> ------------------------------
> 
> _______________________________________________
> MITgcm-support mailing list
> MITgcm-support at mitgcm.org
> http://mitgcm.org/mailman/listinfo/mitgcm-support
> 
> 
> End of MITgcm-support Digest, Vol 142, Issue 9
> **********************************************
> 
> _______________________________________________
> MITgcm-support mailing list
> MITgcm-support at mitgcm.org
> http://mitgcm.org/mailman/listinfo/mitgcm-support