Page Comparison

old environment modules moved to "legacy" stack

The original set of environment modules on Argon have been available by default and their availability was not removed upon loading one of the newer stack modules. As the software stacks have grown, in size and complexity, that introduces more opportunities for module collisions in an environment. With this change, the old modules will be made available as a distinct stack, just like the newer stacks. Thus, it will no longer be possible to have the legacy modules available at the same time in a session as newer modules. The modules will still be available, they will just be swapped out with other stacks. For now, the legacy modules stack will be loaded by default if you do not have a default module set.

However, if you have a default module set that was generated prior to this change that consisted of legacy modules then you will need to regenerate the set. If you see the following message:

Lmod Warning:  You have no modules loaded because the collection "default" is empty!

then this applies to you. This is because that module set does not have the stack/legacy module in it because it did not exist at the time. Here is how to regenerate your old default module set.

module reset
module load $(module -t describe default |& xargs)
module save default

The same process can be applied to any other module set that you have. Just replace "default" with the name of your module set. Again, note that this only applies to module sets that were created prior to April 28, 2021 that contain legacy modules in the set.