ABGC modules: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
m (<source> to <pre> to fix code blocks) |
||
| (18 intermediate revisions by 3 users not shown) | |||
| Line 3: | Line 3: | ||
/cm/shared/apps/WUR/ABGC/modulefiles | /cm/shared/apps/WUR/ABGC/modulefiles | ||
=== Adding a custom module directory to your environment | == Modules available for ABGC == | ||
* [[asreml_3.0 | asreml/3.0fl-64]] | |||
* [[asreml_4.0 | asreml/4.0kr]] | |||
* [[asreml_4.1 | asreml/4.1.0]] | |||
* [[Perl5.10_WUR_module | Perl/5.10.1_wur]] | |||
* [[R3.0.2_WUR_module | R/3.0.2_wur]] | |||
== Adding a custom module directory to your environment == | |||
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 | 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 24: | Line 32: | ||
bwa/0.5.9 bwa/0.7.5a | bwa/0.5.9 bwa/0.7.5a | ||
== See also == | |||
* [[Globally_installed_software | Globally installed software]] | |||
* [[ | * [[Domain_specific_software_on_B4Fcluster_installation_by_users | Installing domain specific software: installation by users]] | ||
* [[ | * [[Setting local variables]] | ||
* [[Installing_R_packages_locally | Installing R packages locally]] | |||
* [[ | * [[Setting_up_Python_virtualenv | Setting up and using a virtual environment for Python3 ]] | ||
* [[ | == External links == | ||
* [[ | |||
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