Table of Contents |
---|
Objectives
Info | ||||
---|---|---|---|---|
| ||||
Easy configuration of IMAS working environment through setting up a predefined set of IMAS libraries using simple call of the module module load imasenv/<compiler_vendor>
e.g: module load imasenv/intel |
Libraries / modules to be set:
Code Block |
---|
**********************************************
GROUP A
General purpose tools/libraries, compilers
Dependency: NONE
**********************************************
* intel
* gcc
* intelmpi
* g95
* java
* python
* matlab
* netbeans
* maven
* scripts
* itmtools
* totalview
* cmake
* mdsplus
* blitz
* jaxfront
**********************************************
GROUP B
General purpose tools/libraries
(plus EUROfusion/IMAS libs and tools that NOT DEPEND on Data Dictionary)
Dependency: compilers (group A)
**********************************************
* hdf5
* blas
* lapack
* fftw
* pspline
* slatec
* mkl
* matheval
* netcdf
**********************************************
GROUP C
IMAS (UAL) library
Dependency: compilers (group A), third parties libraries (group B)
Data Dictionary
**********************************************
* imas
**********************************************
GROUP D
EUROfusion/IMAS libs and tools that DEPEND on Data Dictionary/UAL
Dependency: compilers (group A), third parties libraries (group B)
Data Dictionary, imas (group C)
**********************************************
* interpos
* fc2k
* kepler
* idstools
* pyual
* libbds (imas dependency should be removed)
* xmllib (imas dependency should be removed)
* amns |
Factors defining user working environment
- Compiler, defined by:
- Vendor (e.g. Intel, GNU, ....)
- Version (e.g. 17.0, 6.1.0 , ...)
- Versions of libraries that NOT depend on IMAS/Data dictionary
- For sake of simplicity, libraries are grouped in one "set"
- Set of libraries has its own version
- IMAS (UAL), defined by:
- Data Dictionary version (e.g. 3.19.1, 3.20.0,....)
- UAL engine version (e.g. 3.8.3, ...)
- Versions of libraries that depend on IMAS/Data dictionary
- For sake of simplicity, libraries are grouped in one "set"
- Set of libraries has its own version
Analyzed solutions
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 This feature influenced solutions described below. |
A) "Rolling module"
Code Block | ||
---|---|---|
| ||
module load imasenv/intel/3.19.1/ |
Easy to remember and use syntax
Extreme inflexibility - no versions of compiler, UAL engine, etc can be specified (only defaults are used - it is not possible to set e.g. intel/12 instead 17, mdsplus 7.x instead 6.y, etc)
Problems with versioning - every upgrade of library will require manual change of module
User is not aware of changes of default versions ( potential errors: "it worked yesterday"
)
B) Descriptive but enormously long/strange module name
Code Block | ||
---|---|---|
| ||
module load imasenv/ń/libs/3.0/imas/3.19.1/ual/3.8.2/imaslibs/4.0 |
- Module
libs
will set up modules fromgroup A
andgroup B
- Module
imaslibs
will set up modules fromgroup D
Main disadvantage is rather obvious
It would be really annoying to use such long name... Potential simplifications (like parsing module name) are possible rather theoretically
Full flexibility of setting versions
C) Using two (meta)modules
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 |
Module will load:
- Compiler
(e.g. intel/17.0
) - All components independent from IMAS/Data Dictionary (group B) , gathered together as a set of modules. Such set of modules will have its own version (e.g.
1.0
)
Module imasenv
Code Block | ||
---|---|---|
| ||
imasenv/<imas_ver>/ual/<engine_ver>/<version of this module>
e.g.
imasenv[/3.19.1/ual/3.8.2/1.0] <= part in brackets can be skipped to use defaults |
Module will load:
- imas module
(e.g.
imasenv[/3.19.1/ual/3.8.2 ) - All components dependent on IMAS/Data Dictionary (group D), gathered together as a set of modules. Such set of modules will have its own version (e.g.
1.0
)
Presented solution:
Easy to use by users (to use default versions is enough to write
module load imaslibs
;module load imasenv)
Flexible: Full names can be specified to use non-default versions of library sets
Info | ||
---|---|---|
| ||
The end ("tail") of module name can be skipped to use default versions, so:
|