The Module environment
The lilac and juno clusters make use of a module environment for managing software packages where it is important to provide users with several different versions. The module environment makes it easy to configure your software versions quickly and conveniently.
To see the various options available, type
To list currently loaded modules and versions:
module list Currently Loaded Modulefiles: 1) gcc/4.8.1 2) mpich2_eth/1.5 3) cuda/5.5 4) cmake/126.96.36.199
To list all available modules that can be loaded:
To add a new module, use module add:
module add cuda/5.5
The number that comes after the module name followed by a slash is the version number of the software. More information about available modules can be obtained with themodule show command:
module show cuda/5.5 ——————————————————————- /etc/modulefiles/cuda/5.5: module-whatis cuda module-whatis Version: 5.5 beta module-whatis Description: cuda toolkit prepend-path PATH /usr/local/cuda-5.5/bin prepend-path LD_LIBRARY_PATH /usr/local/cuda-5.5/lib:/opt/cuda-5.5/lib64 ——————————————————————-
Available additional shared software
The juno and luna clusters have additional shared software in the /opt/common directory. The juno cluster is CentOS_7. The luna cluster is CentOS_6 and in the process of being retired.
In an effort to keep track of frequently changing software versions, we are now using this path structure:
For example the latest bwa is at:
R-3.2.0 is at:
You can set these paths in your .bashrc or use the full path in your code. If you put paths in your .bashrc make sure that you source it or somehow add the path to your grid engine scripts.
If you need additional software, check with us to see if we already have it installed. We can install packages for you globally or help you with your own install. To request help installing the software, please use this form here: http://hpc.mskcc.org/software-installation-request/