Software Stack: Difference between revisions
No edit summary |
|||
| Line 3: | Line 3: | ||
=Overview= | =Overview= | ||
The software stack is a suit of software ACCRE builds for the users to use. In general the ACCRE has two types of software stack: binary software stack and compiler software stack. The binary software stack typically includes the stand-alone software which does not need to compile, and the compiler software stack contains the software that is compiled from a given version of compiler (for example, GCC 10.2), so | The software stack is a suit of software ACCRE builds for the users to use. In general the ACCRE has two types of software stack: binary software stack and compiler software stack. The binary software stack typically includes the stand-alone software which does not need to compile for installation, and the compiler software stack contains the software that is compiled for install from a given version of compiler (for example, GCC 10.2), so every software in the compiler software stack starts from the compiler. Usually we use the compiler and it's version to name the compiler software stack. | ||
Our current active compiler based software stack includes the followings: | |||
* GCC 2016b (based on GCC/5.4.0-2.26) and Intel 2016b (based on Intel/2016.3.210); | |||
* GCC 2017b (based on GCC/6.4.0-2.28) and Intel 2016b (based on Intel/2017.4.196); | |||
* GCC 2019a (based on GCC/8.2.0) and Intel 2019a (based on Intel/2019.1.144); | |||
Lmod is a tool for managing software modules within a shared high-performance computing environment (e.g. the ACCRE cluster). Lmod is designed to intelligently manage, negotiate, and enforce the complex dependencies between software and libraries in a HPC environment. This should lead to better usability of administrator-installed software modules and prevent conflicts between lower-level libraries that many modules depend on. | |||
For loading the software from the stack ACCRE provides the user of Lmod. Lmod is a tool for managing software modules within a shared high-performance computing environment (e.g. the ACCRE cluster). Lmod is designed to intelligently manage, negotiate, and enforce the complex dependencies between software and libraries in a HPC environment. This should lead to better usability of administrator-installed software modules and prevent conflicts between lower-level libraries that many modules depend on. | |||
For instructions on basic Lmod usage, please start with the excellent and concise User Guide for Lmod: [https://lmod.readthedocs.io/en/latest/010_user.html]. | For instructions on basic Lmod usage, please start with the excellent and concise User Guide for Lmod: [https://lmod.readthedocs.io/en/latest/010_user.html]. | ||
Revision as of 19:30, 5 September 2023
Overview
The software stack is a suit of software ACCRE builds for the users to use. In general the ACCRE has two types of software stack: binary software stack and compiler software stack. The binary software stack typically includes the stand-alone software which does not need to compile for installation, and the compiler software stack contains the software that is compiled for install from a given version of compiler (for example, GCC 10.2), so every software in the compiler software stack starts from the compiler. Usually we use the compiler and it's version to name the compiler software stack.
Our current active compiler based software stack includes the followings:
- GCC 2016b (based on GCC/5.4.0-2.26) and Intel 2016b (based on Intel/2016.3.210);
- GCC 2017b (based on GCC/6.4.0-2.28) and Intel 2016b (based on Intel/2017.4.196);
- GCC 2019a (based on GCC/8.2.0) and Intel 2019a (based on Intel/2019.1.144);
For loading the software from the stack ACCRE provides the user of Lmod. Lmod is a tool for managing software modules within a shared high-performance computing environment (e.g. the ACCRE cluster). Lmod is designed to intelligently manage, negotiate, and enforce the complex dependencies between software and libraries in a HPC environment. This should lead to better usability of administrator-installed software modules and prevent conflicts between lower-level libraries that many modules depend on.
For instructions on basic Lmod usage, please start with the excellent and concise User Guide for Lmod: [1].
