Telcon: 2023 11 15

Wednesday November 15th, 9am PT (UTC -8:00)

Attendees

• Peter Scheibel (host)
• Tammy Dahlgren
• Chris Green
• Yang Liu

Agenda

This meeting is for Q&A: there are no pre-planned general topics.

• Yang: external modules
  • packages.yaml has a number of externals
  • spack find is not showing them
  • Note: the package has to be installed (via spack install)
  • Note: there also has to be a package.py
  • Side note: appending "s" to external versions
• Yang: heterogenous cluster with Intel and AMD nodes
  • The spack installation installs multiple versions of packages (e.g. one for Intel, and one for AMD)
  • spack load <a package> hits an ambiguity
    • Peter: IIRC there was a plan to get spack load to load the appropriate module for whatever arch you are on
    • Another option is creating an environment for each arch, then spack load will work
  • For module load, it might be possible to customize the hierarchy: https://spack-tutorial.readthedocs.io/en/latest/tutorial_modules.html#hierarchical-module-files
  • See: https://github.com/spack/spack/issues/39993
    • And https://github.com/spack/spack/pull/32960
• Yang: have team of people
  • How can they all install packages together?
• Yang: setup-env.sh is taking 6-14 seconds sometimes
  • How to make it faster?
• Chris: ping on https://github.com/spack/spack/pull/35975
• Chris: "Warning: setting compiler, target or provider preferences in a package specific section of packages.yaml is deprecated, and will be removed in v0.22."
  • Hard to know where this is being done (i.e. how to fix the config to resolve this warning)
  • Only one warning gets printed regardless of how many times this happens
• Chris: have external pythons that use their own PYTHONPATH
  • When spack runs with python we don't want to use that
  • Should we have SPACK_PYTHON_HOME/SPACK_PYTHON_PATH