Modules: Difference between revisions

From HPCwiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 2: Line 2:




Anunna uses modules via Lmod to provide software to their users. Basically, a module configures the environment of the user and/or their jobs to enable the desired application to run.
Anunna uses modules via Lmod to provide software to their users. A module configures the environment of the user and/or their jobs to enable the desired application to run.
The modules are organized in "buckets" for each year. We intend to keep threee buckets of software, one for the current year, one for the previous year and another for legacy software.  
These modules are organized in "buckets" for each year. We intend to keep three buckets of software, one for the current year, one for the previous year and another for legacy software. The legacy module should contain software that is older than two years and is still used or relevant.


The point is to have a conveyor belt of software and have more up-to-date software with more modern build tools (GCC, MPI, intel), which makes the software more maintainable. The conveyor belt also enables the use of more modern toolchains (foss, intel), which will enable software to run more efficiently.
The point is to have a conveyor belt of software and have more up-to-date software with more modern build tools (GCC, MPI, intel), which makes the software more maintainable. The conveyor belt also enables the use of more modern toolchains (foss, intel), which will enable software to run more efficiently.
Line 9: Line 9:
For each bucket we intend to keep one version of software.
For each bucket we intend to keep one version of software.


==Module Migration Status==
==Module Migration==
 
 


==Listing modules==
==Listing modules==

Revision as of 13:04, 12 August 2024

Modules in anunna

Anunna uses modules via Lmod to provide software to their users. A module configures the environment of the user and/or their jobs to enable the desired application to run. These modules are organized in "buckets" for each year. We intend to keep three buckets of software, one for the current year, one for the previous year and another for legacy software. The legacy module should contain software that is older than two years and is still used or relevant.

The point is to have a conveyor belt of software and have more up-to-date software with more modern build tools (GCC, MPI, intel), which makes the software more maintainable. The conveyor belt also enables the use of more modern toolchains (foss, intel), which will enable software to run more efficiently.

For each bucket we intend to keep one version of software.

Module Migration

Listing modules

Searching modules

Searching for keywords