Skip to content

Draft: Added JSC site-config.

With these settings, installation of 24.04 was successful on JUSUF and JURECA-DC.

The following additional site-specific changes/workarounds were needed:

JURECA-DC

  • py-elephant tests hang and have to be skipped by commenting out the whole install_test(self)-function in packages/py-elephant/package.py

JUSUF

  • py-elephant tests hang and have to be skipped by commenting out the whole install_test(self)-function in packages/py-elephant/package.py
  • Since JUSUF does not have GPUs on the login-nodes, py-snudda installation has to run on a compute node. (See #60)
  • For the same reason some arbor checks fail and have to be disabled. (See #59)

Testing

Currently, there is no EBRAINS module to load. In order to load the stack on both systems, the following commands have to be executed:

# Make sure $HOME does not get polluted (probably not necessary in "production")
export SPACK_DISABLE_LOCAL_CONFIG=true
export TEST_TMPDIR=/p/usersoftware/ebrains-sw-stack/ebrains-24.04/${SYSTEMNAME}/spack-user-cache/${USER}/bazel
export CARGO_HOME=/p/usersoftware/ebrains-sw-stack/ebrains-24.04/${SYSTEMNAME}/spack-user-cache/${USER}/cargo

# Load spack and activate the environment
module use /p/usersoftware/swmanage/deepu1/easybuild/stage2024/Spack/easybuild/${SYSTEMNAME}/modules/all/Compiler/GCCcore/12.3.0
ml spack/0.21.1_ebrains
. /p/usersoftware/swmanage/deepu1/easybuild/stage2024/Spack/easybuild/${SYSTEMNAME}/software/spack/0.21.1_ebrains-GCCcore-12.3.0/share/spack/setup-env.sh

spack env activate /p/usersoftware/ebrains-sw-stack/ebrains-24.04/${SYSTEMNAME}/ebrains-spack-builds
Edited by Andreas Müller

Merge request reports