Versions Compared

Key

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

...

  1. System-wide: /software/setonix/current<DATE-TAG>
  2. Project-wide: /software/projects/<project-id>/setonix /<DATE-TAG>
  3. User-specific: /software/projects/<project-id>/<user-name>/setonix  /<DATE-TAG>

Note how the base path for the system-wide installation contains of installations contain the date tag (year and month) of the initial current stack build.

Within each level, there exist three key sub-directories:

...

As a practical example from a Spack installation, here is the path for the library OpenBLAS 0.3.15 24 as initially installed on Setonix for the Zen3 architecture with the compiler GCC 1112.2.0:

/software/setonix/current<DATE-TAG>/software/cray-sles15-zen3/gcc-1112.2.0/openblas-0.3.1524-<build-hash>/

And here is the corresponding modulefile:

/software/setonix/current<DATE-TAG>/modules/zen3/gcc/1112.2.0/libraries/openblas/0.3.1524.lua

Organisation of modulefiles

...

Considering the evolving status of this domain, new software that can benefit from running on a supercomputer will be regularly monitored for.

Licensed packages

Use of software covered by any license agreement is strictly bound by that agreement.

Pawsey does not purchase licensed software apart from compilers, profilers, debuggers and similar.

...

Some licensed software, such as Amber, Ansys, CPMD, NAMD and VASP, is not visible to the module avail command until you have been added to the relevant permission group for that software. In most cases it is quick and straightforward to add you to the permission group, depending on the terms of the specific software licence.

Users can install licensed software by themselves, provided this is in compliance with the software license agreement.

Levels of software service

...

Default package versions are disabled within the module system; in other words, when loading a module the software version must always be specified, otherwise an error will occur.

End of support for Magnus and Galaxy

At the time Setonix Phase 1 becomes operational and migration starts, support on system-wide installations on Magnus and Galaxy will cease.