Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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)

 Please notice, that beside dependencies mentioned above, some other factors should be considered,

Factors defining user working environment

  1. Compiler, defined by:
    1. Vendor  (e.g. Intel, GNU, ....)
    2. Version (e.g.

...

    1. 17.0, 6.1.0 , ...)
  1. Versions of libraries that NOT depend on IMAS/Data dictionary
    1. For sake of simplicity, libraries are grouped in one "set"
    2. Set of libraries has its own version
  2. IMAS (UAL), defined by:
    1. Data Dictionary version (e.g. 3.19.1, 3.20.0,....)
    2. UAL engine version (e.g. 3.8.3, ...)
  3. Versions of libraries that depend on IMAS/Data dictionary
    1. For sake of simplicity, libraries are grouped in one "set"
    2. 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 exampleModule/1.0 or just module load exampleModule is OK

This feature influenced solutions described below.

...