Software on Negishi¶
Software Catalog¶
A comprehensive list of centrally installed software applications can be found here:
Module system¶
The Negishi cluster uses Lmod to manage the user environment, so users have access to the necessary software packages and versions to conduct their research activities. The associated module command can be used to load applications and compilers, making the corresponding libraries and environment variables automatically available in the user environment.
Lmod is a hierarchical module system, meaning a module can only be loaded after loading the necessary compilers and MPI libraries that it depends on. This helps avoid conflicting libraries and dependencies being loaded at the same time. A list of all available modules on the system can be found with the module spider command:
The module spider command can also be used to search for specific module names.
When users log into Negishi, a default compiler (GCC), MPI libraries (OpenMPI), and runtime environments (e.g., Cuda on GPU-nodes) are automatically loaded into the user environment. It is recommended that users explicitly specify which modules and which versions are needed to run their codes in their job scripts via the module load command. Users are advised not to insert module load commands in their bash profiles, as this can cause issues during initialization of certain software (e.g. Thinlinc).
When users load a module, the module system will automatically replace or deactivate modules to ensure the packages you have loaded are compatible with each other. Following example shows that the module system automatically unload the default Intel compiler version to a user-specified version:
Most modules on Negishi include extensive help messages, so users can take advantage of the module help APPNAME command to find information about a particular application or module. Every module also contains two environment variables named $RCAC_APPNAME_ROOT and $RCAC_APPNAME_VERSION identifying its installation prefix and its version. This information can be found by module show APPNAME. Users are encouraged to use generic environment variables such as CC, CXX, FC, MPICC, MPICXX etc. available through the compiler and MPI modules while compiling their code.
Some other common module commands:
To unload a module
To unload all loaded modules and reset everything to original state.
To see all available modules that are compatible with current loaded modules
To display information about a specified module, including environment changes, dependencies, software version and path.
Running the Apps¶
Find available apps in the terminal¶
In addition to searching the software catalog for available applications, one can generate a list via the terminal:
View module prequisites and license information¶
After finding the module that you want to load, use 'module spider' to find any prerequisites or license information, if applicable:
Load the module¶
Use the command specified in the 'module spider' output to load your software module:
Running GUI versions of apps¶
If the app you want to use has a GUI, you can also login to negishi via Thinlinc. More information on this process can be found here.
ROCm Containers¶
Negishi's GPU sub-cluster (Sub-cluster G) is equipped with AMD MI210 GPUs. A selection of GPU-enabled ROCm application containers from the AMD Infinity Hub collection is installed.
Users can download additional ROCm containers from the AMD Infinity Hub and run them directly using Apptainer/Singularity. A subset of pre-downloaded ROCm containers wrapped into convenient software modules are also provided.
To see the lists of ROCm containers available as modules, use:
More information on pre-downloaded ROCm containers can be found here.
BioContainers¶
Pre-downloaded bioinformatics containers with module wrappers are available. You can load them as standard modules: