<div dir="ltr">If the variable will be back and forth between dynamic and physics components, then the reasonable way is to pass through export/import states as coupling. I suggest we make a reasonable length array in exp/imp states to carry options between two components through something like coupling.... a real array is more general to handle all options, such 1.0 for truth, 0,0 for false. In case of option with 0.5 for example, real array can handle it!<div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Feb 1, 2016 at 12:26 PM, Philip Pegion - NOAA Affiliate <span dir="ltr"><<a href="mailto:philip.pegion@noaa.gov" target="_blank">philip.pegion@noaa.gov</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi everyone,<div> I am finishing up adding IAU capability to the NEMS/GSM and I need to pass a logical variable that is defined in the dynamics to the physics (down to gloopb.f). Is there a recommended method to do this? I cannot use namelist_def because the logical variable will start and false, then switch to true, and back to false during an IAU run. </div><div><br></div><div>Any suggestions are greatly appreciated.</div><div> Thanks,</div><div>Phil Pegion</div></div>
<br>_______________________________________________<br>
Ncep.list.nems.announce mailing list<br>
<a href="mailto:Ncep.list.nems.announce@lstsrv.ncep.noaa.gov">Ncep.list.nems.announce@lstsrv.ncep.noaa.gov</a><br>
<a href="https://www.lstsrv.ncep.noaa.gov/mailman/listinfo/ncep.list.nems.announce" rel="noreferrer" target="_blank">https://www.lstsrv.ncep.noaa.gov/mailman/listinfo/ncep.list.nems.announce</a><br>
<br></blockquote></div><br></div>