ABGC modules: Difference between revisions
Jump to navigation
Jump to search
m (<source> to <pre> to fix code blocks) |
|||
| (One intermediate revision by one other user not shown) | |||
| Line 14: | Line 14: | ||
To allow the <code>module</code> program to find the custom module directory, the location of that directory has to be added to <code>MODULEPATH</code> variable. | To allow the <code>module</code> program to find the custom module directory, the location of that directory has to be added to <code>MODULEPATH</code> variable. | ||
< | <pre> | ||
export MODULEPATH=$MODULEPATH:/cm/shared/apps/WUR/ABGC/modulefiles | export MODULEPATH=$MODULEPATH:/cm/shared/apps/WUR/ABGC/modulefiles | ||
</ | </pre> | ||
This can be made permanent by adding this line of code to the <code>.bash_profile</code> file in the root of your home folder. To then load the modified <code>MODULEPATH</code> variable you have to load <code>.bash_profile</code> again: | This can be made permanent by adding this line of code to the <code>.bash_profile</code> file in the root of your home folder. To then load the modified <code>MODULEPATH</code> variable you have to load <code>.bash_profile</code> again: | ||
< | <pre> | ||
source .bash_profile | source .bash_profile | ||
</ | </pre> | ||
This needs to be done only for terminals that are already open. Next time you login, <code>.bash_profile</code> will be loaded automatically. | This needs to be done only for terminals that are already open. Next time you login, <code>.bash_profile</code> will be loaded automatically. | ||
You can check if the modules are found. | You can check if the modules are found. | ||
< | <pre> | ||
module avail | module avail | ||
</ | </pre> | ||
This should give output that includes something similar to this: | This should give output that includes something similar to this: | ||
| Line 33: | Line 33: | ||
== See also == | == See also == | ||
* [[Globally_installed_software | Globally installed software]] | * [[Globally_installed_software | Globally installed software]] | ||
* [[Domain_specific_software_on_B4Fcluster_installation_by_users | Installing domain specific software: installation by users]] | * [[Domain_specific_software_on_B4Fcluster_installation_by_users | Installing domain specific software: installation by users]] | ||
Latest revision as of 15:43, 15 June 2023
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.
export MODULEPATH=$MODULEPATH:/cm/shared/apps/WUR/ABGC/modulefiles
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 .bash_profile
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.
module avail
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
- 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