lmod can mark modules as deprecated, so users are warned. I think you
might also be able to get it to collect statistics on module usage or
something.
lmod also has the advantage of being much more complicated and much less
efficient if set up incorrectly.
On Sun, Nov 24, 2019 at 9:20 PM Brian
I never understood the benefit of lmod vs environment modules, although
I see a push to use lmod. Particularly for versioning, but I always
managed versions by using directory hierarchies. For instance, OpenMPI:
mpi/openmpi/3.2.3
mpi/openmpi/4.0.2
Then set a conflict on the top path
Quick question that I'm not sure how to find the answer to otherwise: do
array jobs have less impact on the scheduler in any way than a whole long
list of jobs run the more traditional way? Less startup overhead, anything
like that?
kinda sorta.
I think of array jobs as a bit like Python
We also use lmod here. Very useful when different versions are needed or
for any software installations outside the distribution.
However, our environment is heterogenous, and the software modules might
have different versions/paths on different nodes. This creates an issue
when users run 'module
