ABGC modules: Difference between revisions
| Line 7: | Line 7: | ||
* [[asreml_3.0 | asreml/3.0fl-64]] | * [[asreml_3.0 | asreml/3.0fl-64]] | ||
* [[asreml_4.0 | asreml/4.0kr]] | * [[asreml_4.0 | asreml/4.0kr]] | ||
* [[asreml_4.1 | asreml/4.1.0]] | |||
* [[Perl5.10_WUR_module | Perl/5.10.1_wur]] | * [[Perl5.10_WUR_module | Perl/5.10.1_wur]] | ||
* [[R3.0.2_WUR_module | R/3.0.2_wur]] | * [[R3.0.2_WUR_module | R/3.0.2_wur]] | ||
Revision as of 17:20, 23 January 2015
All ABGC modules can be found in:
/cm/shared/apps/WUR/ABGC/modulefiles
Modules available for ABGC
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
- Globally installed software
- Installing domain specific software: installation by users
- Setting local variables
- Installing R packages locally
- Setting up and using a virtual environment for Python3