...
The sub pages of this page list the software packages that are installed on Argon. Note that combining our HPC systems, and making Argon "live forever", necessitated some changes in how the software is managed. Previously, the stack would be viable for the life of a cluster system but that is no longer feasible given the long lived nature of Argon. In the new HPC model there needs to be a way to update all levels of the software stack while maintaining a consistent set of dependencies, while still maintaining older versions of software should they be needed. This is accomplished by updating the entire stack of software but maintaining the previous stacks as well. These stacks are versioned so that they can be tracked and documented as a set. The software packages are managed via Environment Modules. One extra level of the environment module hierarchy was introduced to manage this, with a versioned "stack" module. The original set of packages will be maintained as the "legacy" stack. The sets of packages are made visible by loading a "stack" module. To set the default stack module, and possibly other environment modules to be loaded by default, set a default module set.
Concomitant with enabling this scheme, the package building framework was changed from an in-house developed system to a community project based framework. One of the effects of this was a change to the naming scheme. The Legacy modules were named as the upstream project named them, as much as possible, in terms of format. With the new framework everything is named with lowercase. For example, R becomes r.
...