<div dir="ltr"><div><div><div>Ruiyu,<br><br></div>It looks to me the executable names under NEMS/exe is the same as the one in the job script: <br><br>fv3_gfs_nh.prod.32bit.x<br><br></div>Would you please let me know what executable name you have in your test? Thanks.<br><br></div>Jun<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, May 15, 2017 at 3:03 PM, Ruiyu Sun - NOAA Affiliate <span dir="ltr"><<a href="mailto:ruiyu.sun@noaa.gov" target="_blank">ruiyu.sun@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"><div><div><div>Hi Jun,<br><br></div>I just did a test following your instruction at <a href="https://svnemc.ncep.noaa.gov/projects/nems/apps/NEMSfv3gfs/tags/fv3gfs.v0beta/release/v0/readme.txt" target="_blank">https://svnemc.ncep.noaa.gov/<wbr>projects/nems/apps/NEMSfv3gfs/<wbr>tags/fv3gfs.v0beta/release/v0/<wbr>readme.txt</a><br><br></div>But I got an error because the inconsistency in the executable names. In run script it asked for a different executable name from the ones in the .../NEMS/exe directory. <br><span class="HOEnZb"><font color="#888888"><br></font></span></div><span class="HOEnZb"><font color="#888888">Ruiyu <br></font></span></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Fri, May 12, 2017 at 5:05 PM, Eugene Mirvis <span dir="ltr"><<a href="mailto:eugene.mirvis@noaa.gov" target="_blank">eugene.mirvis@noaa.gov</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>> Dusan, Sam,<br>
><br>
> To generalize the answer, the application driven modulfiles can be<br>
> tracked by module variables ($LOADEDMODULES, and $MODULE PATH) and<br>
</span>> use entire dictionary of module operations, while scripts cannot.<br>
<span>> That's is not only unloaded or switched between applications env.,<br>
> but you can conduct environment analysis and make decisions on the<br>
> fly: switch versions, steps of the workflow, data based on the status.<br>
> You can see an example @ we made for the bufr use (different versions)<br>
> on the module nceplibs trac page:<br>
</span>> "*/How to Engage NCEPLIBS modules and Assign Yours New Variables?..."/*<br>
<span class="m_-1421702183025406081im m_-1421702183025406081HOEnZb">> <a href="https://svnemc.ncep.noaa.gov/trac/nceplibs/wiki/Assign" rel="noreferrer" target="_blank">https://svnemc.ncep.noaa.gov/t<wbr>rac/nceplibs/wiki/Assign</a><br>
><br>
> On LMOD systems (next level, on Theia, Yellowstone, and most likely<br>
> on the upcoming system) there are some new env. variables , like:<br>
> $LMOD_DEFAULT_MODULEPATH which gives additional module "families"<br>
> capability.<br>
><br>
> However, it is all about convenience and best practice.<br>
> Of course, you can write anything in low level scripts. The the<br>
> realities are we still have to use system, 3rd parties, nceplibs etc.<br>
> modules.<br>
><br>
> Cheers,<br>
> -Eugene<br>
<br>
</span><div class="m_-1421702183025406081HOEnZb"><div class="m_-1421702183025406081h5">______________________________<wbr>_________________<br>
Ncep.list.fv3-announce mailing list<br>
<a href="mailto:Ncep.list.fv3-announce@lstsrv.ncep.noaa.gov" target="_blank">Ncep.list.fv3-announce@lstsrv.<wbr>ncep.noaa.gov</a><br>
<a href="https://www.lstsrv.ncep.noaa.gov/mailman/listinfo/ncep.list.fv3-announce" rel="noreferrer" target="_blank">https://www.lstsrv.ncep.noaa.g<wbr>ov/mailman/listinfo/ncep.list.<wbr>fv3-announce</a><br>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>