[Ncep.list.fv3-announce] fv3gfs release beta test
Jun Wang - NOAA Affiliate
jun.wang at noaa.gov
Mon May 15 19:17:30 UTC 2017
It looks to me the executable names under NEMS/exe is the same as the one
in the job script:
Would you please let me know what executable name you have in your test?
On Mon, May 15, 2017 at 3:03 PM, Ruiyu Sun - NOAA Affiliate <
ruiyu.sun at noaa.gov> wrote:
> Hi Jun,
> I just did a test following your instruction at
> 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.
> On Fri, May 12, 2017 at 5:05 PM, Eugene Mirvis <eugene.mirvis at noaa.gov>
>> > Dusan, Sam,
>> > To generalize the answer, the application driven modulfiles can be
>> > tracked by module variables ($LOADEDMODULES, and $MODULE PATH) and
>> > use entire dictionary of module operations, while scripts cannot.
>> > That's is not only unloaded or switched between applications env.,
>> > but you can conduct environment analysis and make decisions on the
>> > fly: switch versions, steps of the workflow, data based on the status.
>> > You can see an example @ we made for the bufr use (different versions)
>> > on the module nceplibs trac page:
>> > "*/How to Engage NCEPLIBS modules and Assign Yours New Variables?..."/*
>> > https://svnemc.ncep.noaa.gov/trac/nceplibs/wiki/Assign
>> > On LMOD systems (next level, on Theia, Yellowstone, and most likely
>> > on the upcoming system) there are some new env. variables , like:
>> > $LMOD_DEFAULT_MODULEPATH which gives additional module "families"
>> > capability.
>> > However, it is all about convenience and best practice.
>> > Of course, you can write anything in low level scripts. The the
>> > realities are we still have to use system, 3rd parties, nceplibs etc.
>> > modules.
>> > Cheers,
>> > -Eugene
>> Ncep.list.fv3-announce mailing list
>> Ncep.list.fv3-announce at lstsrv.ncep.noaa.gov
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Ncep.list.fv3-announce