...
| Warning |
|---|
Please keep in mind a "module" mechanism limitations: among the other, "module" doesn't allow to skip the begin or the middle of module name. Only the "tail" of module name can be skipped (defaulted) So, e.g.module load exampleModule/1.0/requiredLib/2.0 cannot be called like module load exampleModule/requiredLib/2.0, but module load example This feature influenced solutions described below. |
...
A) "Rolling module"
| Code Block | ||
|---|---|---|
| ||
module load imasenv/intel/3.19.1/ |
...
B) Descriptive but enormously long/strange module name
| Code Block | ||
|---|---|---|
| ||
module load imasenv/intel/17.0/libs/3.0/imas/3.19.1/ual/3.8.2/imaslibs/4.0 |
...
To overcome disadvantages of solutions presented above, and keep a desired level of flexibility, user working environment can be set by two (meta)modules 
Module imaslibs
| Code Block | ||
|---|---|---|
| ||
imaslibs/<compiler_vendor>/<compiler_version>/<version of this module> e.g. imaslibs[/intel/17.0/1.0] <= part in brackets can be skipped to use defaults |
...