Versions Compared

Key

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

or CPT's wonderful journey through the installer towards getting IMAS on new platforms.


Disclaimer: all example steps given below are assuming BASH being your shell of choice. 


Installing main dependencies

Follow the list of requirements/dependencies as stored in https://git.iter.org/projects/IMAS/repos/access-layer/browse/README.md

Add modules to set them up in the environment.



IMAS

Getting the IMAS installer

Clone the installer using either master (recommended) or develop branch (at your own risk)

Code Block
languagebash
themeMidnight
git clone ssh://git@git.iter.org/imas/installer.git

Preparing the configuration

Create target directory where all IMAS related tools will be deployed (will be referenced as IMAS_HOME from now on).

Adapt site-config/Makefile.default to the local configuration and needs. Look at tools/imas-config.in to try to guess how to name your own site-config file, and/or check which files are being targeted by running 

Code Block
languagebash
themeMidnight
DEBUG=1 ./tools/imas-config.in

Check if configuration is generating the expected setting for the targeted DD and AL tags by running

Code Block
languagebash
themeMidnight
make cache
make help TAG_DD=a.b.c TAG_AL=x.y.z

Building and installing

After making sure that compile time required modules are loaded, simply run, for given DD and AL versions

Code Block
languagebash
themeMidnight
make install TAG_DD=a.b.c TAG_AL=x.y.z



IDStools

Getting the sources

Clone the idstools repo (from IMAS Core project, not from IMAS Extra...)

Code Block
languagebash
themeMidnight
ssh://git@git.iter.org/imas/idstools.git

Preparing the configuration

Create site-config file with same name used for the installer, and specify there the name of the IMAS module and the targeted idstools module name. 

Make sure you have IMAS module loaded before attempting the build (it sets required IMAS_HOME variable and imas-config-installer).

Check if configuration is well set by checking the result of 

Code Block
languagebash
themeMidnight
make help


Building and installing

Code Block
languagebash
themeMidnight
make all
make install




FC2K


XMLlib


Kepler





git clone https://g2bpalak@gforge6.eufus.eu/git/imasscripts





Example with real steps followed on IPP's tok cluster.






  • Updating tools/imas-config.in

    Code Block
    languagebash
    themeMidnight
    diff --git a/tools/imas-config.in b/tools/imas-config.in
    index 7d7cdc4..84c7f11 100755
    --- a/tools/imas-config.in
    +++ b/tools/imas-config.in
    @@ -126,6 +126,7 @@ getalias() {
       [[ "$1" =~ ^gpu(008|010).fusion.ccfe.ac.uk$ ]] && echo "UKAEA.GPU"
       [[ "$1" =~ ^ipp.mpg.de$ ]] && echo "IPP-Garching"
       [[ "$1" =~ ^mpcdf.mpg.de$ ]] && echo "IPP-Garching"
    +  [[ "$1" =~ ^bc.rzg.mpg.de$ ]] && echo "IPP-Garching"
       [[ "$1" =~ ^nakasvr17.naka.qst.go.jp ]] && echo "JT-60"


  • Creating site-config/Makefile.IPP-Garching.SLES-15

    Code Block
    languagebash
    themeMidnight
    Currently Loaded Modulefiles:
    1) git/2.16 3) blitz/1.0.2 5) texlive/2018 7) intel/18.0.5 9) matlab/2017b 11) autoconf/2.69 13) cmake/3.13
    2) saxon/9.9.1 4) doxygen/1.8 6) gcc/6 8) anaconda/3/2019.03 10) jdk/8 12) automake/1.15 14) pkg-config/0.29


  • Requires JAVA_HOME to be set so the Makefile can find JNI headers

    Code Block
    languagebash
    themeMidnight
    make -j4 install TAG_DD=3.24.0 TAG_AL=4.2.0 JAVA_HOME=${JDK_HOME}


  • Because the target install dir (/afs/.ipp/...) is not the final one (/afs/ipp/...) the generated module should be patched

    Code Block
    languagebash
    themeMidnight
    -  set imas_home /afs/.ipp/tok/soft/imas
    +  set imas_home /afs/ipp/tok/soft/imas