[Ncep.list.fv3-announce] fv3gfs release beta test

[Eugene Mirvis]

> 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