[MITgcm-support] Combining tracers for use in BLING
Matthew Mazloff
mmazloff at ucsd.edu
Mon May 28 11:41:56 EDT 2018
Hi Andrew
pkg/gchem/gchem_forcing_sep.F
passes tracers to
pkg/bling/bling_main.F
where they become BGC variables: bling_main sees the 6th passed tracer as Iron
Thus in
pkg/gchem/gchem_forcing_sep.F
I would
1) use a temporary local variable to combine your Fe ptracers.
2) Pass that temporary variable to bling_main instead of pTracer(1-OLx,1-OLy,1,bi,bj,6),
3) then decompose that variable and assign them back to your Fe ptracers.
With this method you only have to edit
pkg/gchem/gchem_forcing_sep.F
Haven’t tried this, so let me know if it doesn’t work, doesnt make sense, or doesn’t do what you wanted…
Matt
> On May 28, 2018, at 3:56 AM, Andrew Twelves <agt_94 at hotmail.co.uk> wrote:
>
> Hi all,
>
> I have a question to do with the interface between BLING and the PTRACERS package:
>
> I want to use two separate iron tracers in my model with different source terms but with the same chemistry. I know that by default BLING reads in eight(or nine with plankton advected) tracers and assumes these correspond to DIC, alkalinity etc. in that order; however I thought it might be possible to simply combine the two iron tracers together before sending the sum to BLING, and then take this output from BLING calculations and redistribute it between the pools before the next time step.
>
> As I try and work this out, is there anyone who has tried something similar or who could tell me where exactly the physical tracers from PTRACERS are assigned to the biogeochemical ones in BLING?
>
> Many thanks,
>
> Andrew Twelves
> University of Edinburgh
>
> _______________________________________________
> MITgcm-support mailing list
> MITgcm-support at mitgcm.org <mailto:MITgcm-support at mitgcm.org>
> http://mailman.mitgcm.org/mailman/listinfo/mitgcm-support <http://mailman.mitgcm.org/mailman/listinfo/mitgcm-support>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.mitgcm.org/pipermail/mitgcm-support/attachments/20180528/cb76d310/attachment.html>
More information about the MITgcm-support
mailing list