<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">Ah, I see PTRACERS_ref can be used for freshwater value depending on setup. You must have this on for your BLING setup. <div><br></div><div>I think the issue is that you are driving ALK close to zero but allowing silica to stay large, violating the assumptions in the model. </div><div><br></div><div>Either you could make the runoff have high alk (perhaps with PTRACERS_ref) or prescribe silica low there when there is significant runoff. Or perhaps try using SIBLING. Or perhaps use my caps but make them less stringent. Or, if DIC package is stable, just remove my caps and see what happens.</div><div><br></div><div>Matt</div><div><br></div><div><div><br></div><div><br><div><br><blockquote type="cite"><div>On Sep 25, 2023, at 8:19 AM, Matthew Mazloff <mmazloff@ucsd.edu> wrote:</div><br class="Apple-interchange-newline"><div><meta http-equiv="content-type" content="text/html; charset=utf-8"><div style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">Are you giving ICs in data.ptracers? If so PTRACERS_ref shouldn’t be being used, I think. <div><br></div><div>Matt</div><div><br><div><br><blockquote type="cite"><div>On Sep 25, 2023, at 8:43 AM, kunal madkaiker <kunal.madkaiker02@gmail.com> wrote:</div><br class="Apple-interchange-newline"><div><div dir="ltr"><div>Thanks Matt,</div><div><br></div><div>I tried with
#undef CARBONCHEM_SOLVESAPHE but the issue persists.</div><div><br></div><div>Just an observation, when I keep PTRACERS_ref=0 in data.dic, it doesn't impact the DIC and ALK at those runoff points (ref. using_dic.gif)</div><div>However, whether I keep PTRACERS_ref=0 or any other value, it impacts the conc. of those points (which keep on drifting as the run progresses, ref. using_bling.gif).</div><div><br></div><div>Kunal<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Sep 25, 2023 at 7:35 PM Matthew Mazloff <<a href="mailto:mmazloff@ucsd.edu">mmazloff@ucsd.edu</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi Kunal<br>
<br>
The default bling chemistry is the same as the DIC package. Is your run with the funny behavior using <br>
#undef CARBONCHEM_SOLVESAPHE<br>
If so, can you check that you get the desired outcome with this undefined.<br>
<br>
There may be a bug in the BLING SOLVESAPHE code.<br>
<br>
Matt<br>
<br>
<br>
<br>
> On Sep 25, 2023, at 6:58 AM, kunal madkaiker <<a href="mailto:kunal.madkaiker02@gmail.com" target="_blank">kunal.madkaiker02@gmail.com</a>> wrote:<br>
> <br>
> Hi all,<br>
> <br>
> I have some issues resolving the carbon chemistry using the BLING package. My domain has river runoff included as a point source. When using the 'DIC' package, DIC and ALK conc. get diluted causing pH to increase at those points (which is correct).<br>
> <br>
> However, when I use the same setup with the BLING package, the DIC and ALK conc. are getting diluted but the pH decreases rapidly (5-6 pH).<br>
> <br>
> Secondly, has the SOLVESAPHE algorithm been fully implemented in BLING or not yet? I tried defining 'CARBONCHEM_SOLVESAPHE' in BLING_OPTIONS.h and 'selectpHsolver=1' in data.bling but then I got the segmentation error. Otherwise, it works fine.<br>
> <br>
> Let me know what you think. I am attaching the required files and plots for your reference.<br>
> <br>
> Thanks,<br>
> Kunal<br>
> <BLING_OPTIONS.h><DIC_OPTIONS.h><data.dic><data.bling><sterr_file><using_bling.gif><using_dic.gif>_______________________________________________<br>
> MITgcm-support mailing list<br>
> <a href="mailto:MITgcm-support@mitgcm.org" target="_blank">MITgcm-support@mitgcm.org</a><br>
> <a href="https://urldefense.com/v3/__http://mailman.mitgcm.org/mailman/listinfo/mitgcm-support__;!!Mih3wA!DU6XPS0r_V-iBbpy1DoUX0ePkKRdvMrbR61lSsmKcyG9Zzh1h9aJz2ECIYMYIci2i2Dseq_pUBQUpbrrkaBMwp8yzH-6$" rel="noreferrer" target="_blank">https://urldefense.com/v3/__http://mailman.mitgcm.org/mailman/listinfo/mitgcm-support__;!!Mih3wA!DU6XPS0r_V-iBbpy1DoUX0ePkKRdvMrbR61lSsmKcyG9Zzh1h9aJz2ECIYMYIci2i2Dseq_pUBQUpbrrkaBMwp8yzH-6$</a> <br>
<br>
_______________________________________________<br>
MITgcm-support mailing list<br>
<a href="mailto:MITgcm-support@mitgcm.org" target="_blank">MITgcm-support@mitgcm.org</a><br>
<a href="https://urldefense.com/v3/__http://mailman.mitgcm.org/mailman/listinfo/mitgcm-support__;!!Mih3wA!G6DkxmOYF85FN3jomwPi4vliPg8Z4L_Z5zOGMMAAOaOrgFn_wRfAMOu2L7iHgrz6wMrNqKEULF8HTwv5ENaqyznlGaGr$" rel="noreferrer" target="_blank">http://mailman.mitgcm.org/mailman/listinfo/mitgcm-support</a><br>
</blockquote></div>
<span id="cid:f_lmz25qhz0"><using_dic.gif></span><span id="cid:f_lmz25qiz1"><using_bling.gif></span>_______________________________________________<br>MITgcm-support mailing list<br>MITgcm-support@mitgcm.org<br>https://urldefense.com/v3/__http://mailman.mitgcm.org/mailman/listinfo/mitgcm-support__;!!Mih3wA!G6DkxmOYF85FN3jomwPi4vliPg8Z4L_Z5zOGMMAAOaOrgFn_wRfAMOu2L7iHgrz6wMrNqKEULF8HTwv5ENaqyznlGaGr$ <br></div></blockquote></div><br></div></div></div></blockquote></div><br></div></div></body></html>