[Ncep.list.nems.announce] passing information between dynamics and physics in NEMS

Henry Juang - NOAA Federal henry.juang at noaa.gov
Mon Feb 1 20:33:39 UTC 2016

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!

On Mon, Feb 1, 2016 at 12:26 PM, Philip Pegion - NOAA Affiliate <
philip.pegion at noaa.gov> wrote:

> Hi everyone,
>   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.
> Any suggestions are greatly appreciated.
>  Thanks,
> Phil Pegion
> _______________________________________________
> Ncep.list.nems.announce mailing list
> Ncep.list.nems.announce at lstsrv.ncep.noaa.gov
> https://www.lstsrv.ncep.noaa.gov/mailman/listinfo/ncep.list.nems.announce
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://www.lstsrv.ncep.noaa.gov/pipermail/ncep.list.nems.announce/attachments/20160201/0f659184/attachment.html 

More information about the Ncep.list.nems.announce mailing list