This document provides a short description of proposed solution. For a more detailed analysis look >>HERE<<

 

1. Quickstart

To fully configure your working IMAS environment you have to load two modules:

 

module load wpcdenv[/<compiler_vendor>/<compiler_version>/<version of this module>]
module load imasenv[/<imas_ver>/ual/<engine_ver>/<version of this module>]

part in brackets [] can be skipped to use defaults

2. Module wpcdenv

Loading libraries/tools not depending on IMAS/DD

Module wpcdenv
wpcdenv/<compiler_vendor>/<compiler_version>/<version of this module>
e.g. wpcdenv[/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, gathered together as a set of modules. Such set of modules will have its own version (e.g. 1.0 )

3. Module imasenv

Loading libraries/tools depending on IMAS/DD

Module imasenv
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, gathered together as a set of modules. Such set of modules will have its own version (e.g. 1.0 )

 

  • The end ("tail") of module name can be skipped to use default versions, so to use default versions is enough to write
    • module load wpcdenv; module load imasenv
  • If user doesn't load wpcdenv prior to imasenv, the default version of wpcdenv is loaded automatically
  • Full module names can be specified to use non-default versions of library sets

 

 

 

 

 

 

 

  • No labels