Skip to content

Conference notes for 2022 01 11

Lev Gorenstein edited this page Feb 1, 2022 · 1 revision

Agenda For Lmod Zoom Mtg 16:30 UTC 2022 01 11

  • Question and Answers
  • Presentation on How Lmod Collections work
  • Brief Discussion on module properties were added to the isVisible Hook (issue #552) -- This is likely to be a more detailed discussion for a later meeting.
  • Spider output when descriptions are not the same (Issue #551) (E.G. cpu vs. gpu descriptions

Attendees

  • Kenneth Hoste (HPC-UGent, Belgium)
  • Robert McLay (TACC)
  • Åke Sandgren (Umeå University, Sweden)
  • Kurt Lust (Univ of Antwerp, Belgium + LUMI User Support Team)
  • Joey Dumont (Government of Canada)

Notes

Lmod collections

  • Q: Would it make sense to add another feature to Lmod to take a "snapshot" of the current environment (controlled by Lmod), and ignore changes to module files?
    • Already possible by capture output of "lmod bash load" into a script
    • and using sh_to_modulefile you could easily create a module file to restore that environment

Module properties in isVisible hook

  • cfr. request by Ward to explain how this was supported in more detail
  • (will be discussed next time)

Spider output with different descriptions

  • support for "generic description" that's show in output of "module spider" if it's there?

  • suggestion by Åke: separate place to specify a single line of "feature" info for specific modules, that could be show next to or below each "hierarchy set"

  • line that says "load all modules on any of these lines" is often misinterpreted

    • maybe should be rephrased to say "one (and only one) of these lines"

Q&A

Next meeting

  • planned for Tue 8 Feb 2022 (15:30 UTC)
    • 2nd Tuesday rather than 1st Tuesday, by exception
  • future topics:
    • Lmod testing
    • How to pass module info to hooks
      • how support for properties was implemented in isVisible hook
    • More internals of Lmod
Clone this wiki locally