Next quarterly change
We offer, besides the currently supported versions, two categories of modules for new and legacy versions. Due to dependencies between compilers, libraries and applications, changes to the applications and the corresponding modules need to be synchronized and are done on a quarterly basis.
Life-cycle of an application
Modules for new or experimental versions of an application/library/compiler first appear in the new module category, where we provide a partial support matrix. Specific compiler/library combinations can be requested by shareholders. New modules are not visible by default. If you would like to see which new versions are available or try them out, you will need to load the new module first:
module load new
Applications that have passed all tests and are deemed ready for production (stable, bug-free, compatible with LSF, etc.) will be moved to the supported category in the next quarterly update.
Applications that have become obsolete (no longer supported by the vendor, superseded by new versions with more functionality, etc.) will be moved to the legacy category in the next quarterly update. For these modules the HPC group can only provide limited support. Legacy modules are not visible by default. If you still need to use them, you will need to load the legacy module first:
module load legacy
Applications that are known to be buggy, have become redundant or whose license have expired will be removed in the next quarterly update. If you still need to use them, please contact Cluster Support.
The HPC group updates the module categories on a quarterly basis (February, June, August, November). Therefore the Application life-cycle page contains a table listing all applications that are available on Brutus as well as the modifications that we plan to apply at the next quarterly change. The users will receive a reminder, one week prior to the update of the categories that will also contain information about the most important changes.