Globally installed software

Available as modules

• gcc/4.8.1
• python/2.7.6
• python/3.3.3
• R/3.0.2

Globally installed on all nodes

• Perl5.10
• pigz
• Python2.6
• BioPerl v1.61

Available as global SHARED modules

Modules can be found in:

 /cm/shared/modulefiles/SHARED/

• augustus/2.7
• bedtools/2.18.0
• BLAST+/2.2.28
• blat/v35
• bowtie/2-2.2.1
• bwa/0.5.9
• bwa/0.7.5a
• cegma/2.4
• exonerate/2.2.0-x86_64
• geneid/1.4.4
• genewise/2.2.3-rc7
• hmmer/3.1b1
• maker/2.28
• Plink/1.07
• provean/1.1.3
• RepeatMasker/4.0.3
• RepeatModeler/1.0.7
• samtools/0.1.12a
• samtools/0.1.19
• snap/2013-11-29
• SOAPdenovo2/r240

Adding a custom module directory to your environment

To allow the module program to find the custom module directory, the location of that directory has to be added to MODULEPATH variable.

<source lang='bash'> export MODULEPATH=$MODULEPATH:/cm/shared/apps/WUR/ABGC/modulefiles </source> This can be made permanent by adding this line of code to the .bash_profile file in the root of your home folder. To then load the modified MODULEPATH variable you have to load .bash_profile again: <source lang='bash'> source .bash_profile </source> This needs to be done only for terminals that are already open. Next time you login, .bash_profile will be loaded automatically.

You can check if the modules are found. <source lang='bash'> module avail </source> This should give output that includes something similar to this:

 ----------------------------------- /cm/shared/apps/WUR/ABGC/modulefiles -----------------------------------
 bwa/0.5.9  bwa/0.7.5a

See also

• Using the B4F Cluster
• Installing domain specific software: installation by users
• Setting local variables
• Installing R packages locally
• Setting up and using a virtual environment for Python3
• modules specific for ABGC