<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.umiacs.umd.edu/cbcb/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Lmendelo</id>
	<title>Cbcb - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.umiacs.umd.edu/cbcb/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Lmendelo"/>
	<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/cbcb/index.php/Special:Contributions/Lmendelo"/>
	<updated>2026-05-04T07:23:01Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.43.7</generator>
	<entry>
		<id>https://wiki.umiacs.umd.edu/cbcb/index.php?title=CBCB_Software_Modules&amp;diff=9027</id>
		<title>CBCB Software Modules</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/cbcb/index.php?title=CBCB_Software_Modules&amp;diff=9027"/>
		<updated>2015-06-19T15:39:22Z</updated>

		<summary type="html">&lt;p&gt;Lmendelo: /* Listing All Modules */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Starting in the Spring of 2015, communal CBCB Bioinformatics Software has been installed using GNU Modules. &amp;lt;span style=&amp;quot;color: blue;&amp;quot;&amp;gt;Please note that the instructions below are for use with Red Hat 7 machines only.&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Common Modules ==&lt;br /&gt;
&lt;br /&gt;
CBCB Software modules are already configured for interactive shells on Red Hat 7 machines - no additional setup is required. The module files are installed in the following location:&lt;br /&gt;
 /cbcb/sw/RedHat-7-x86_64/common/modules/release/latest&lt;br /&gt;
&lt;br /&gt;
To see see what modules are available:&lt;br /&gt;
 $ module avail&lt;br /&gt;
&lt;br /&gt;
To add a module to your environment, use &amp;lt;code&amp;gt;module add&amp;lt;/code&amp;gt;:&lt;br /&gt;
 $ module add samtools/0.1.19&lt;br /&gt;
&lt;br /&gt;
Note that you can also specify the software name without the version:&lt;br /&gt;
 $ module add samtools&lt;br /&gt;
&lt;br /&gt;
Now samtools has been added to your environment:&lt;br /&gt;
 $ which samtools&lt;br /&gt;
 /cbcb/sw/RedHat-7-x86_64/common/local/samtools/0.1.19/bin/samtools&lt;br /&gt;
&lt;br /&gt;
== User Modules ==&lt;br /&gt;
&lt;br /&gt;
We have created some scripts to assist you with installing software and modules to your user directory in &amp;lt;code&amp;gt;/cbcb/sw&amp;lt;/code&amp;gt;. We recommend that you use these scripts because this will help us share installed software among other CBCB users.&lt;br /&gt;
&lt;br /&gt;
Run this initialization script to set up your directory structure:&lt;br /&gt;
 $ /cbcb/sw/RedHat-7-x86_64/common/scripts/init_cbcb_sw_user.sh&lt;br /&gt;
&lt;br /&gt;
This will create a directory for you:&lt;br /&gt;
 $ tree /cbcb/sw/RedHat-7-x86_64/users/&amp;lt;username&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
/cbcb/sw/RedHat-7-x86_64/users/&amp;lt;username&amp;gt;&lt;br /&gt;
├── local&lt;br /&gt;
├── modules&lt;br /&gt;
│   └── &amp;lt;username&amp;gt;&lt;br /&gt;
│       └── env&lt;br /&gt;
├── module_template&lt;br /&gt;
├── README&lt;br /&gt;
├── scripts&lt;br /&gt;
│   ├── copy_module_template.sh&lt;br /&gt;
│   ├── init_install_vars.sh&lt;br /&gt;
│   └── install_package.sh&lt;br /&gt;
└── src&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Use the &amp;lt;code&amp;gt;src&amp;lt;/code&amp;gt; directory for storing and compiling source code.&lt;br /&gt;
* Use the &amp;lt;code&amp;gt;local&amp;lt;/code&amp;gt; directory as the installation prefix.&lt;br /&gt;
* Use the &amp;lt;code&amp;gt;modules&amp;lt;/code&amp;gt; directory to store your modulefiles.&lt;br /&gt;
&lt;br /&gt;
See [[#Installing Software]] below.&lt;br /&gt;
&lt;br /&gt;
To make use of your personal module file directory, add the following to your &amp;lt;code&amp;gt;~/.bashrc&amp;lt;/code&amp;gt;:&lt;br /&gt;
 module use /cbcb/sw/RedHat-7-x86_64/users/&amp;lt;username&amp;gt;/modules&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Installing Software ===&lt;br /&gt;
&lt;br /&gt;
Use the &amp;lt;code&amp;gt;install_package.sh&amp;lt;/code&amp;gt; script to automatically compile software that uses &amp;lt;code&amp;gt;./configure; make; make install&amp;lt;/code&amp;gt;. The advantage to using this install script is that it will:&lt;br /&gt;
* use the standardized directory structure for personal software installation, and&lt;br /&gt;
* &#039;&#039;&#039;&#039;&#039;automatically&#039;&#039;&#039;&#039;&#039; create a module file for the software in your &amp;lt;code&amp;gt;modules&amp;lt;/code&amp;gt; directory!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For full details, read the &amp;lt;code&amp;gt;README&amp;lt;/code&amp;gt; placed in your personal directory (&amp;lt;code&amp;gt;/cbcb/sw/RedHat-7-x86_64/users/&amp;lt;username&amp;gt;&amp;lt;/code&amp;gt;). It&#039;s also available in the [https://gitlab.umiacs.umd.edu/cbcb/cbcb-sw/blob/master/templates/user_readme.md  cbcb-sw Gitlab repository].&lt;br /&gt;
&lt;br /&gt;
=== Listing All Modules ===&lt;br /&gt;
&lt;br /&gt;
The command &amp;lt;code&amp;gt;module avail&amp;lt;/code&amp;gt; only lists modulefiles that appear in directories that have been added to your &amp;lt;code&amp;gt;$MODULEPATH&amp;lt;/code&amp;gt; environment variable (either by hand or via &amp;lt;code&amp;gt;module use&amp;lt;/code&amp;gt; command).&lt;br /&gt;
To see all modulefiles that are available for your use in both the Common Modules and the User Modules:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
cat /cbcb/sw/RedHat-7-x86_64/common/all_modules.txt&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
&lt;br /&gt;
or see [http://cbcb.umd.edu/~lmendelo/cbcb_modules/all_modules.txt here].&lt;br /&gt;
&lt;br /&gt;
== Setup for non-interactive shells ==&lt;br /&gt;
&lt;br /&gt;
Modules are already configured for interactive shells, but to use modules with non-interactive shells such as [[Torque]], add the following to your ~/.bashrc:&lt;br /&gt;
 . /usr/share/Modules/init/bash&lt;br /&gt;
 . /etc/profile.d/ummodules.sh&lt;br /&gt;
&lt;br /&gt;
For more information, see the [https://wiki.umiacs.umd.edu/umiacs/index.php/Modules UMIACS wiki].&lt;br /&gt;
&lt;br /&gt;
== GNU Modules Cheatsheet ==&lt;br /&gt;
&lt;br /&gt;
Ask for help:&lt;br /&gt;
 module --help&lt;br /&gt;
&lt;br /&gt;
List available modules:&lt;br /&gt;
 module avail&lt;br /&gt;
&lt;br /&gt;
Add a module to your environment:&lt;br /&gt;
 module add blast&lt;br /&gt;
&lt;br /&gt;
List loaded modules:&lt;br /&gt;
 module list&lt;br /&gt;
&lt;br /&gt;
Remove a module from your environment:&lt;br /&gt;
 module rm blast&lt;br /&gt;
&lt;br /&gt;
Remove all modules from your environment:&lt;br /&gt;
 module purge&lt;br /&gt;
&lt;br /&gt;
Add a path to search for available modules:&lt;br /&gt;
 module use /cbcb/sw/RedHat-7-x86_64/users/lmendelo/modules&lt;br /&gt;
&lt;br /&gt;
See what changes a module makes to your environment:&lt;br /&gt;
 module show Python2/common/2.7.9&lt;br /&gt;
&lt;br /&gt;
== Contact ==&lt;br /&gt;
&lt;br /&gt;
Brought to you by:&lt;br /&gt;
&lt;br /&gt;
* [mailto:abelew@umiacs.umd.edu Trey Belew]&lt;br /&gt;
* [mailto:keith@umiacs.umd.edu Keith Hughitt]&lt;br /&gt;
* [mailto:lmendelo@umiacs.umd.edu Lee Mendelowitz]&lt;br /&gt;
&lt;br /&gt;
== See Also ==&lt;br /&gt;
* [https://wiki.umiacs.umd.edu/umiacs/index.php/Modules UMIACS wiki]&lt;br /&gt;
* [https://gitlab.umiacs.umd.edu/cbcb/cbcb-sw Repository on GitLab]&lt;br /&gt;
* [https://docs.google.com/presentation/d/1UgKtnjcqHlpLZU79hGXfkgvNtse-ksMQ_gJMFCVLKRw/edit?usp=sharing CBCB Software slides on Google Drive]&lt;/div&gt;</summary>
		<author><name>Lmendelo</name></author>
	</entry>
	<entry>
		<id>https://wiki.umiacs.umd.edu/cbcb/index.php?title=CBCB_Software_Modules&amp;diff=9025</id>
		<title>CBCB Software Modules</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/cbcb/index.php?title=CBCB_Software_Modules&amp;diff=9025"/>
		<updated>2015-04-23T20:30:02Z</updated>

		<summary type="html">&lt;p&gt;Lmendelo: /* User Modules */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Starting in the Spring of 2015, communal CBCB Bioinformatics Software has been installed using GNU Modules. &amp;lt;span style=&amp;quot;color: blue;&amp;quot;&amp;gt;Please note that the instructions below are for use with Red Hat 7 machines only.&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Common Modules ==&lt;br /&gt;
&lt;br /&gt;
CBCB Software modules are already configured for interactive shells on Red Hat 7 machines - no additional setup is required. The module files are installed in the following location:&lt;br /&gt;
 /cbcb/sw/RedHat-7-x86_64/common/modules/release/latest&lt;br /&gt;
&lt;br /&gt;
To see see what modules are available:&lt;br /&gt;
 $ module avail&lt;br /&gt;
&lt;br /&gt;
To add a module to your environment, use &amp;lt;code&amp;gt;module add&amp;lt;/code&amp;gt;:&lt;br /&gt;
 $ module add samtools/0.1.19&lt;br /&gt;
&lt;br /&gt;
Note that you can also specify the software name without the version:&lt;br /&gt;
 $ module add samtools&lt;br /&gt;
&lt;br /&gt;
Now samtools has been added to your environment:&lt;br /&gt;
 $ which samtools&lt;br /&gt;
 /cbcb/sw/RedHat-7-x86_64/common/local/samtools/0.1.19/bin/samtools&lt;br /&gt;
&lt;br /&gt;
== User Modules ==&lt;br /&gt;
&lt;br /&gt;
We have created some scripts to assist you with installing software and modules to your user directory in &amp;lt;code&amp;gt;/cbcb/sw&amp;lt;/code&amp;gt;. We recommend that you use these scripts because this will help us share installed software among other CBCB users.&lt;br /&gt;
&lt;br /&gt;
Run this initialization script to set up your directory structure:&lt;br /&gt;
 $ /cbcb/sw/RedHat-7-x86_64/common/scripts/init_cbcb_sw_user.sh&lt;br /&gt;
&lt;br /&gt;
This will create a directory for you:&lt;br /&gt;
 $ tree /cbcb/sw/RedHat-7-x86_64/users/&amp;lt;username&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
/cbcb/sw/RedHat-7-x86_64/users/&amp;lt;username&amp;gt;&lt;br /&gt;
├── local&lt;br /&gt;
├── modules&lt;br /&gt;
│   └── &amp;lt;username&amp;gt;&lt;br /&gt;
│       └── env&lt;br /&gt;
├── module_template&lt;br /&gt;
├── README&lt;br /&gt;
├── scripts&lt;br /&gt;
│   ├── copy_module_template.sh&lt;br /&gt;
│   ├── init_install_vars.sh&lt;br /&gt;
│   └── install_package.sh&lt;br /&gt;
└── src&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Use the &amp;lt;code&amp;gt;src&amp;lt;/code&amp;gt; directory for storing and compiling source code.&lt;br /&gt;
* Use the &amp;lt;code&amp;gt;local&amp;lt;/code&amp;gt; directory as the installation prefix.&lt;br /&gt;
* Use the &amp;lt;code&amp;gt;modules&amp;lt;/code&amp;gt; directory to store your modulefiles.&lt;br /&gt;
&lt;br /&gt;
See [[#Installing Software]] below.&lt;br /&gt;
&lt;br /&gt;
To make use of your personal module file directory, add the following to your &amp;lt;code&amp;gt;~/.bashrc&amp;lt;/code&amp;gt;:&lt;br /&gt;
 module use /cbcb/sw/RedHat-7-x86_64/users/&amp;lt;username&amp;gt;/modules&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Installing Software ===&lt;br /&gt;
&lt;br /&gt;
Use the &amp;lt;code&amp;gt;install_package.sh&amp;lt;/code&amp;gt; script to automatically compile software that uses &amp;lt;code&amp;gt;./configure; make; make install&amp;lt;/code&amp;gt;. The advantage to using this install script is that it will:&lt;br /&gt;
* use the standardized directory structure for personal software installation, and&lt;br /&gt;
* &#039;&#039;&#039;&#039;&#039;automatically&#039;&#039;&#039;&#039;&#039; create a module file for the software in your &amp;lt;code&amp;gt;modules&amp;lt;/code&amp;gt; directory!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For full details, read the &amp;lt;code&amp;gt;README&amp;lt;/code&amp;gt; placed in your personal directory (&amp;lt;code&amp;gt;/cbcb/sw/RedHat-7-x86_64/users/&amp;lt;username&amp;gt;&amp;lt;/code&amp;gt;). It&#039;s also available in the [https://gitlab.umiacs.umd.edu/cbcb/cbcb-sw/blob/master/templates/user_readme.md  cbcb-sw Gitlab repository].&lt;br /&gt;
&lt;br /&gt;
=== Listing All Modules ===&lt;br /&gt;
&lt;br /&gt;
The command &amp;lt;code&amp;gt;module avail&amp;lt;/code&amp;gt; only lists modulefiles that appear in directories that have been added to your &amp;lt;code&amp;gt;$MODULEPATH&amp;lt;/code&amp;gt; environment variable (either by hand or via &amp;lt;code&amp;gt;module use&amp;lt;/code&amp;gt; command).&lt;br /&gt;
To see all modulefiles that are available for your use in both from the Common Modules and from the User Modules:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
cat /cbcb/sw/RedHat-7-x86_64/common/all_modules.txt&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
&lt;br /&gt;
or see [http://cbcb.umd.edu/~lmendelo/cbcb_modules/all_modules.txt here].&lt;br /&gt;
&lt;br /&gt;
== Setup for non-interactive shells ==&lt;br /&gt;
&lt;br /&gt;
Modules are already configured for interactive shells, but to use modules with non-interactive shells such as [[Torque]], add the following to your ~/.bashrc:&lt;br /&gt;
 . /usr/share/Modules/init/bash&lt;br /&gt;
 . /etc/profile.d/ummodules.sh&lt;br /&gt;
&lt;br /&gt;
For more information, see the [https://wiki.umiacs.umd.edu/umiacs/index.php/Modules UMIACS wiki].&lt;br /&gt;
&lt;br /&gt;
== GNU Modules Cheatsheet ==&lt;br /&gt;
&lt;br /&gt;
Ask for help:&lt;br /&gt;
 module --help&lt;br /&gt;
&lt;br /&gt;
List available modules:&lt;br /&gt;
 module avail&lt;br /&gt;
&lt;br /&gt;
Add a module to your environment:&lt;br /&gt;
 module add blast&lt;br /&gt;
&lt;br /&gt;
List loaded modules:&lt;br /&gt;
 module list&lt;br /&gt;
&lt;br /&gt;
Remove a module from your environment:&lt;br /&gt;
 module rm blast&lt;br /&gt;
&lt;br /&gt;
Remove all modules from your environment:&lt;br /&gt;
 module purge&lt;br /&gt;
&lt;br /&gt;
Add a path to search for available modules:&lt;br /&gt;
 module use /cbcb/sw/RedHat-7-x86_64/users/lmendelo/modules&lt;br /&gt;
&lt;br /&gt;
See what changes a module makes to your environment:&lt;br /&gt;
 module show Python2/common/2.7.9&lt;br /&gt;
&lt;br /&gt;
== Contact ==&lt;br /&gt;
&lt;br /&gt;
Brought to you by:&lt;br /&gt;
&lt;br /&gt;
* [mailto:abelew@umiacs.umd.edu Trey Belew]&lt;br /&gt;
* [mailto:keith@umiacs.umd.edu Keith Hughitt]&lt;br /&gt;
* [mailto:lmendelo@umiacs.umd.edu Lee Mendelowitz]&lt;br /&gt;
&lt;br /&gt;
== See Also ==&lt;br /&gt;
* [https://wiki.umiacs.umd.edu/umiacs/index.php/Modules UMIACS wiki]&lt;br /&gt;
* [https://gitlab.umiacs.umd.edu/cbcb/cbcb-sw Repository on GitLab]&lt;br /&gt;
* [https://docs.google.com/presentation/d/1UgKtnjcqHlpLZU79hGXfkgvNtse-ksMQ_gJMFCVLKRw/edit?usp=sharing CBCB Software slides on Google Drive]&lt;/div&gt;</summary>
		<author><name>Lmendelo</name></author>
	</entry>
	<entry>
		<id>https://wiki.umiacs.umd.edu/cbcb/index.php?title=CBCB_Software_Modules&amp;diff=9024</id>
		<title>CBCB Software Modules</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/cbcb/index.php?title=CBCB_Software_Modules&amp;diff=9024"/>
		<updated>2015-04-23T19:41:28Z</updated>

		<summary type="html">&lt;p&gt;Lmendelo: /* User Modules */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Starting in the Spring of 2015, communal CBCB Bioinformatics Software has been installed using GNU Modules. &amp;lt;span style=&amp;quot;color: blue;&amp;quot;&amp;gt;Please note that the instructions below are for use with Red Hat 7 machines only.&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Common Modules ==&lt;br /&gt;
&lt;br /&gt;
CBCB Software modules are already configured for interactive shells on Red Hat 7 machines - no additional setup is required. The module files are installed in the following location:&lt;br /&gt;
 /cbcb/sw/RedHat-7-x86_64/common/modules/release/latest&lt;br /&gt;
&lt;br /&gt;
To see see what modules are available:&lt;br /&gt;
 $ module avail&lt;br /&gt;
&lt;br /&gt;
To add a module to your environment, use &amp;lt;code&amp;gt;module add&amp;lt;/code&amp;gt;:&lt;br /&gt;
 $ module add samtools/0.1.19&lt;br /&gt;
&lt;br /&gt;
Note that you can also specify the software name without the version:&lt;br /&gt;
 $ module add samtools&lt;br /&gt;
&lt;br /&gt;
Now samtools has been added to your environment:&lt;br /&gt;
 $ which samtools&lt;br /&gt;
 /cbcb/sw/RedHat-7-x86_64/common/local/samtools/0.1.19/bin/samtools&lt;br /&gt;
&lt;br /&gt;
== User Modules ==&lt;br /&gt;
&lt;br /&gt;
We have created some scripts to assist you with installing software and modules to your user directory in &amp;lt;code&amp;gt;/cbcb/sw&amp;lt;/code&amp;gt;. We recommend that you use these scripts because this will help us share installed software among other CBCB users.&lt;br /&gt;
&lt;br /&gt;
Run this initialization script to set up your directory structure:&lt;br /&gt;
 $ /cbcb/sw/RedHat-7-x86_64/common/scripts/init_cbcb_sw_user.sh&lt;br /&gt;
&lt;br /&gt;
This will create a directory for you:&lt;br /&gt;
 $ tree /cbcb/sw/RedHat-7-x86_64/users/&amp;lt;username&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
/cbcb/sw/RedHat-7-x86_64/users/&amp;lt;username&amp;gt;&lt;br /&gt;
├── local&lt;br /&gt;
├── modules&lt;br /&gt;
│   └── &amp;lt;username&amp;gt;&lt;br /&gt;
│       └── env&lt;br /&gt;
├── module_template&lt;br /&gt;
├── README&lt;br /&gt;
├── scripts&lt;br /&gt;
│   ├── copy_module_template.sh&lt;br /&gt;
│   ├── init_install_vars.sh&lt;br /&gt;
│   └── install_package.sh&lt;br /&gt;
└── src&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Use the &amp;lt;code&amp;gt;src&amp;lt;/code&amp;gt; directory for storing and compiling source code.&lt;br /&gt;
* Use the &amp;lt;code&amp;gt;local&amp;lt;/code&amp;gt; directory as the installation prefix.&lt;br /&gt;
* Use the &amp;lt;code&amp;gt;modules&amp;lt;/code&amp;gt; directory to store your modulefiles.&lt;br /&gt;
&lt;br /&gt;
See [[#Installing Software]] below.&lt;br /&gt;
&lt;br /&gt;
To make use of your personal module file directory, add the following to your &amp;lt;code&amp;gt;~/.bashrc&amp;lt;/code&amp;gt;:&lt;br /&gt;
 module use /cbcb/sw/RedHat-7-x86_64/users/&amp;lt;username&amp;gt;/modules&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Installing Software ===&lt;br /&gt;
&lt;br /&gt;
Use the &amp;lt;code&amp;gt;install_package.sh&amp;lt;/code&amp;gt; script to automatically compile software that uses &amp;lt;code&amp;gt;./configure; make; make install&amp;lt;/code&amp;gt;. The advantage to using this install script is that it will:&lt;br /&gt;
* use the standardized directory structure for personal software installation, and&lt;br /&gt;
* &#039;&#039;&#039;&#039;&#039;automatically&#039;&#039;&#039;&#039;&#039; create a module file for the software in your &amp;lt;code&amp;gt;modules&amp;lt;/code&amp;gt; directory!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For full details, read the &amp;lt;code&amp;gt;README&amp;lt;/code&amp;gt; placed in your personal directory (&amp;lt;code&amp;gt;/cbcb/sw/RedHat-7-x86_64/users/&amp;lt;username&amp;gt;&amp;lt;/code&amp;gt;). It&#039;s also available in the [https://gitlab.umiacs.umd.edu/cbcb/cbcb-sw/blob/master/templates/user_readme.md  cbcb-sw Gitlab repository].&lt;br /&gt;
&lt;br /&gt;
== Setup for non-interactive shells ==&lt;br /&gt;
&lt;br /&gt;
Modules are already configured for interactive shells, but to use modules with non-interactive shells such as [[Torque]], add the following to your ~/.bashrc:&lt;br /&gt;
 . /usr/share/Modules/init/bash&lt;br /&gt;
 . /etc/profile.d/ummodules.sh&lt;br /&gt;
&lt;br /&gt;
For more information, see the [https://wiki.umiacs.umd.edu/umiacs/index.php/Modules UMIACS wiki].&lt;br /&gt;
&lt;br /&gt;
== GNU Modules Cheatsheet ==&lt;br /&gt;
&lt;br /&gt;
Ask for help:&lt;br /&gt;
 module --help&lt;br /&gt;
&lt;br /&gt;
List available modules:&lt;br /&gt;
 module avail&lt;br /&gt;
&lt;br /&gt;
Add a module to your environment:&lt;br /&gt;
 module add blast&lt;br /&gt;
&lt;br /&gt;
List loaded modules:&lt;br /&gt;
 module list&lt;br /&gt;
&lt;br /&gt;
Remove a module from your environment:&lt;br /&gt;
 module rm blast&lt;br /&gt;
&lt;br /&gt;
Remove all modules from your environment:&lt;br /&gt;
 module purge&lt;br /&gt;
&lt;br /&gt;
Add a path to search for available modules:&lt;br /&gt;
 module use /cbcb/sw/RedHat-7-x86_64/users/lmendelo/modules&lt;br /&gt;
&lt;br /&gt;
See what changes a module makes to your environment:&lt;br /&gt;
 module show Python2/common/2.7.9&lt;br /&gt;
&lt;br /&gt;
== Contact ==&lt;br /&gt;
&lt;br /&gt;
Brought to you by:&lt;br /&gt;
&lt;br /&gt;
* [mailto:abelew@umiacs.umd.edu Trey Belew]&lt;br /&gt;
* [mailto:keith@umiacs.umd.edu Keith Hughitt]&lt;br /&gt;
* [mailto:lmendelo@umiacs.umd.edu Lee Mendelowitz]&lt;br /&gt;
&lt;br /&gt;
== See Also ==&lt;br /&gt;
* [https://wiki.umiacs.umd.edu/umiacs/index.php/Modules UMIACS wiki]&lt;br /&gt;
* [https://gitlab.umiacs.umd.edu/cbcb/cbcb-sw Repository on GitLab]&lt;br /&gt;
* [https://docs.google.com/presentation/d/1UgKtnjcqHlpLZU79hGXfkgvNtse-ksMQ_gJMFCVLKRw/edit?usp=sharing CBCB Software slides on Google Drive]&lt;/div&gt;</summary>
		<author><name>Lmendelo</name></author>
	</entry>
	<entry>
		<id>https://wiki.umiacs.umd.edu/cbcb/index.php?title=Communal_Software&amp;diff=9023</id>
		<title>Communal Software</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/cbcb/index.php?title=Communal_Software&amp;diff=9023"/>
		<updated>2015-03-03T18:55:01Z</updated>

		<summary type="html">&lt;p&gt;Lmendelo: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= WARNING! =&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p style=&amp;quot;color: #e70000; font-weight: bold; font-size: medium;&amp;quot;&amp;gt;WARNING: &amp;lt;code&amp;gt;/fs/sz-user-supported/&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;/cbcb/software&amp;lt;/code&amp;gt; has been deprecated as of March 2015. Please move towards using Red Hat 7 machines and [[CBCB Software Modules]]. &amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Introduction ==&lt;br /&gt;
CBCB users do not have root access on their machines or the communal servers. Communal CBCB software is therefore typically installed in&lt;br /&gt;
 /fs/sz-user-supported/&lt;br /&gt;
There are two primary subdirectories which differ by architecture. For the most part, 32bit software is installed in&lt;br /&gt;
 /fs/sz-user-supported/Linux-i686/&lt;br /&gt;
while 64bit software is installed in&lt;br /&gt;
 /fs/sz-user-supported/Linux-x86_64/&lt;br /&gt;
The appropriate subdirectory is typically dynamically chosen by embedding&lt;br /&gt;
 /fs/sz-user-supported/`uname`-`uname -m`&lt;br /&gt;
in a user&#039;s path variables in their bashrc/tcshrc file.&lt;br /&gt;
&lt;br /&gt;
Installing software to these directories and updating a user&#039;s path can be tricky. For this reason, many users choose to maintain specialty software in personal directories.&lt;br /&gt;
&lt;br /&gt;
== Core Software ==&lt;br /&gt;
&lt;br /&gt;
The latest versions of the most frequently used CBCB software is installed under&lt;br /&gt;
  /fs/szdevel/core-cbcb-software/&lt;br /&gt;
and follows a directory structure similar to&lt;br /&gt;
  /fs/sz-user-supported/&lt;br /&gt;
The software is installed and maintained by the cbcb-staff group.&lt;br /&gt;
&lt;br /&gt;
Software list: &lt;br /&gt;
  &#039;&#039;&#039;Name                      version&#039;&#039;&#039;&lt;br /&gt;
  Bio::Perl &lt;br /&gt;
  Biopython&lt;br /&gt;
  Bowtie                    0.12.7&lt;br /&gt;
  Celera Assembler          6.1&lt;br /&gt;
  gcc                       4.5.1&lt;br /&gt;
  GMap,GSnap                2010-07-27&lt;br /&gt;
  Java (JRE only)           1.6.0_22&lt;br /&gt;
  NCBI blast&lt;br /&gt;
  Newbler                   2.5 &lt;br /&gt;
  R&lt;br /&gt;
  Samtools                  0.1.9&lt;br /&gt;
  SOAPdeNovo                1.04&lt;br /&gt;
  Velvet                    1.0.13&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Planned Maintenance (Summer 2012) ==&lt;br /&gt;
The Pop lab is currently planning to update much of the communal software installed in sz-user-supported over the Summer of 2012. So far this list includes:&lt;br /&gt;
* [http://sourceforge.net/apps/mediawiki/amos/index.php?title=AMOS AMOS] -- Already installed&lt;br /&gt;
* [http://www.ncbi.nlm.nih.gov/staff/tao/URLAPI/blastall/index.html blastall 2.2.23] -- May not be worth upgrading from 2.2.18. Will look at release notes.&lt;br /&gt;
* [http://hmmer.janelia.org/ HMMer3] -- Installed.&lt;br /&gt;
** [http://pfam.sanger.ac.uk/ Pfam 24.0]&lt;br /&gt;
* PERL -- May attempt to standardize default version across servers.&lt;br /&gt;
** [http://www.bioperl.org/wiki/Main_Page BioPERL]&lt;br /&gt;
* Python -- May attempt to standardize default version across servers.&lt;br /&gt;
** [http://biopython.org/wiki/Main_Page BioPython]&lt;br /&gt;
*** [http://numpy.scipy.org/ NumPy]&lt;br /&gt;
*** [http://www.reportlab.com/software/opensource/ ReportLab]&lt;br /&gt;
Please feel free to contact Ted Gibbons at tgibbons@umd.edu to make suggestions or express concerns about tampering with the communal software installations and the corresponding paths in the communal CBCB bashrc file.&lt;/div&gt;</summary>
		<author><name>Lmendelo</name></author>
	</entry>
	<entry>
		<id>https://wiki.umiacs.umd.edu/cbcb/index.php?title=Main_Page&amp;diff=9022</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/cbcb/index.php?title=Main_Page&amp;diff=9022"/>
		<updated>2015-03-03T18:44:47Z</updated>

		<summary type="html">&lt;p&gt;Lmendelo: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== IMPORTANT (Read First) ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color: green; font-size: medium; font-weight: bold;&amp;quot;&amp;gt;NEW!&amp;amp;nbsp;&amp;lt;/span&amp;gt;&amp;lt;span style=&amp;quot;font-weight: bold&amp;quot;&amp;gt;Read about the [[CBCB Software Modules]]&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The CBCB computational infrastructure is a shared resource and we all need to pitch in in order to make sure it works well for all of us.  Most importantly, we need to ensure that our disk space and computational resources are used responsibly.  The disk space, in particular, is a valuable commodity and thus it is important to pay attention to the following:&lt;br /&gt;
* There are three types of disk space available (a full list of volumes is available at [https://wiki.umiacs.umd.edu/cbcb-private/index.php/Storage CBCB Storage]) :&lt;br /&gt;
** Local harddrives (usually mounted as /scratch on the machines that have this resource).  These are not backed up, are quite fast (they live physically close to the processor), but can only be &#039;seen&#039; by the machine where they are mounted and, thus, require data staging in/out (which can take a while)&lt;br /&gt;
** Shared 3Par storage (/fs/szasmg*, /fs/szdata/*, etc.).  This is very fast and very expensive disk and thus a limited resource. Please only use this space to store data temporarily, while you are running some analyses on it.  As a rule of thumb, if a file or collection of files of any considerable size have lived on this space for more than 1-2 weeks, they should probably be moved to the attic space (see below)&lt;br /&gt;
** Attic storage (/fs/szattic*).  This is cheaper and ample, but slow and brittle storage.  Your data-sets should primarily live here.  Due to it&#039;s brittleness, the IT department do not recommend you run any analyses directly in this volume, rather you copy the files over to a local harddrive or the 3Par instead, and copy the results back when done.&lt;br /&gt;
* You should remove any temporary results you don&#039;t need in the long term as soon as you&#039;ve generated them, and compress all of the large files.  Bzip2 works better than gzip but either should dramatically improve the space requirements, especially for text files such as fasta or fastq.&lt;br /&gt;
* You should ensure that your files are owned by the cbcb group and that they have group write permissions for any file stored on the 3Par, especially for all those in /fs/szscratch.  This will allow your colleagues to remove files in case the disk runs out of space and you are, for example, on vacation (in which case you shouldn&#039;t have any major files sitting around on the 3Par).&lt;br /&gt;
&lt;br /&gt;
For more information on the CBCB resources see [[Getting Started in CBCB]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Seminars ==&lt;br /&gt;
* [http://www.cbcb.umd.edu/seminars Regular CBCB seminars (during academic year)] &amp;lt;br&amp;gt;&lt;br /&gt;
* [[Cbcb:Works-In-Progress]] - Works in progress seminar schedule (Summer 2008) &amp;lt;br&amp;gt;&lt;br /&gt;
* [[short_read_sequencing|Short read sequencing Meeting]] (Fridays at 3pm)&lt;br /&gt;
&lt;br /&gt;
== Projects ==&lt;br /&gt;
&lt;br /&gt;
* [[Project:Pop-Lab|Pop-Lab]]&lt;br /&gt;
* [[Project:Hcbravo-lab|HCBravo Lab]]&lt;br /&gt;
* [[Project:Cloud-Computing|Cloud Computing]]&lt;br /&gt;
* [[Project:SummerInternships|Summer Internship Projects]]&lt;br /&gt;
* [[Metagenomics Reading Group (Wed 2pm)]]&lt;br /&gt;
&lt;br /&gt;
== People ==&lt;br /&gt;
 &lt;br /&gt;
* [[User:ayres|Daniel Ayres]]&lt;br /&gt;
* [[User:pknut777|Adam Bazinet]] &lt;br /&gt;
* [[User:irina|Irina Astrovskaya]] &lt;br /&gt;
* [[User:jpaulson|Joseph Paulson]]  &lt;br /&gt;
* [[User:mpop|Mihai Pop]] &lt;br /&gt;
* [[User:nelsayed|Najib El-Sayed]]&lt;br /&gt;
&lt;br /&gt;
== Getting started ==&lt;br /&gt;
If you have just received a new umiacs account through CBCB, follow the instructions on this page to get the basic information you&#039;ll need to start working:&amp;lt;br&amp;gt;&lt;br /&gt;
*[[Getting Started in CBCB]]&lt;br /&gt;
*[[CBCB Software Modules]]&lt;br /&gt;
*[[Torque]]&lt;br /&gt;
*[https://wiki.umiacs.umd.edu/cbcb-private/index.php/Storage CBCB Storage]&lt;br /&gt;
*[https://wiki.umiacs.umd.edu/cbcb-private/index.php/Compute CBCB Computers]&lt;br /&gt;
*[[Communal Software]]&lt;/div&gt;</summary>
		<author><name>Lmendelo</name></author>
	</entry>
	<entry>
		<id>https://wiki.umiacs.umd.edu/cbcb/index.php?title=Main_Page&amp;diff=9021</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/cbcb/index.php?title=Main_Page&amp;diff=9021"/>
		<updated>2015-03-03T18:44:06Z</updated>

		<summary type="html">&lt;p&gt;Lmendelo: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== IMPORTANT (Read First) ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color: green; font-size: medium; font-weight: bold;&amp;quot;&amp;gt;NEW!&amp;amp;nbsp;&amp;lt;/span&amp;gt;Read about the [[CBCB Software Modules]]&lt;br /&gt;
&lt;br /&gt;
The CBCB computational infrastructure is a shared resource and we all need to pitch in in order to make sure it works well for all of us.  Most importantly, we need to ensure that our disk space and computational resources are used responsibly.  The disk space, in particular, is a valuable commodity and thus it is important to pay attention to the following:&lt;br /&gt;
* There are three types of disk space available (a full list of volumes is available at [https://wiki.umiacs.umd.edu/cbcb-private/index.php/Storage CBCB Storage]) :&lt;br /&gt;
** Local harddrives (usually mounted as /scratch on the machines that have this resource).  These are not backed up, are quite fast (they live physically close to the processor), but can only be &#039;seen&#039; by the machine where they are mounted and, thus, require data staging in/out (which can take a while)&lt;br /&gt;
** Shared 3Par storage (/fs/szasmg*, /fs/szdata/*, etc.).  This is very fast and very expensive disk and thus a limited resource. Please only use this space to store data temporarily, while you are running some analyses on it.  As a rule of thumb, if a file or collection of files of any considerable size have lived on this space for more than 1-2 weeks, they should probably be moved to the attic space (see below)&lt;br /&gt;
** Attic storage (/fs/szattic*).  This is cheaper and ample, but slow and brittle storage.  Your data-sets should primarily live here.  Due to it&#039;s brittleness, the IT department do not recommend you run any analyses directly in this volume, rather you copy the files over to a local harddrive or the 3Par instead, and copy the results back when done.&lt;br /&gt;
* You should remove any temporary results you don&#039;t need in the long term as soon as you&#039;ve generated them, and compress all of the large files.  Bzip2 works better than gzip but either should dramatically improve the space requirements, especially for text files such as fasta or fastq.&lt;br /&gt;
* You should ensure that your files are owned by the cbcb group and that they have group write permissions for any file stored on the 3Par, especially for all those in /fs/szscratch.  This will allow your colleagues to remove files in case the disk runs out of space and you are, for example, on vacation (in which case you shouldn&#039;t have any major files sitting around on the 3Par).&lt;br /&gt;
&lt;br /&gt;
For more information on the CBCB resources see [[Getting Started in CBCB]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Seminars ==&lt;br /&gt;
* [http://www.cbcb.umd.edu/seminars Regular CBCB seminars (during academic year)] &amp;lt;br&amp;gt;&lt;br /&gt;
* [[Cbcb:Works-In-Progress]] - Works in progress seminar schedule (Summer 2008) &amp;lt;br&amp;gt;&lt;br /&gt;
* [[short_read_sequencing|Short read sequencing Meeting]] (Fridays at 3pm)&lt;br /&gt;
&lt;br /&gt;
== Projects ==&lt;br /&gt;
&lt;br /&gt;
* [[Project:Pop-Lab|Pop-Lab]]&lt;br /&gt;
* [[Project:Hcbravo-lab|HCBravo Lab]]&lt;br /&gt;
* [[Project:Cloud-Computing|Cloud Computing]]&lt;br /&gt;
* [[Project:SummerInternships|Summer Internship Projects]]&lt;br /&gt;
* [[Metagenomics Reading Group (Wed 2pm)]]&lt;br /&gt;
&lt;br /&gt;
== People ==&lt;br /&gt;
 &lt;br /&gt;
* [[User:ayres|Daniel Ayres]]&lt;br /&gt;
* [[User:pknut777|Adam Bazinet]] &lt;br /&gt;
* [[User:irina|Irina Astrovskaya]] &lt;br /&gt;
* [[User:jpaulson|Joseph Paulson]]  &lt;br /&gt;
* [[User:mpop|Mihai Pop]] &lt;br /&gt;
* [[User:nelsayed|Najib El-Sayed]]&lt;br /&gt;
&lt;br /&gt;
== Getting started ==&lt;br /&gt;
If you have just received a new umiacs account through CBCB, follow the instructions on this page to get the basic information you&#039;ll need to start working:&amp;lt;br&amp;gt;&lt;br /&gt;
*[[Getting Started in CBCB]]&lt;br /&gt;
*[[CBCB Software Modules]]&lt;br /&gt;
*[[Torque]]&lt;br /&gt;
*[https://wiki.umiacs.umd.edu/cbcb-private/index.php/Storage CBCB Storage]&lt;br /&gt;
*[https://wiki.umiacs.umd.edu/cbcb-private/index.php/Compute CBCB Computers]&lt;br /&gt;
*[[Communal Software]]&lt;/div&gt;</summary>
		<author><name>Lmendelo</name></author>
	</entry>
	<entry>
		<id>https://wiki.umiacs.umd.edu/cbcb/index.php?title=Main_Page&amp;diff=9020</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/cbcb/index.php?title=Main_Page&amp;diff=9020"/>
		<updated>2015-03-03T18:20:20Z</updated>

		<summary type="html">&lt;p&gt;Lmendelo: /* Getting started */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== IMPORTANT (Read First) ==&lt;br /&gt;
The CBCB computational infrastructure is a shared resource and we all need to pitch in in order to make sure it works well for all of us.  Most importantly, we need to ensure that our disk space and computational resources are used responsibly.  The disk space, in particular, is a valuable commodity and thus it is important to pay attention to the following:&lt;br /&gt;
* There are three types of disk space available (a full list of volumes is available at [https://wiki.umiacs.umd.edu/cbcb-private/index.php/Storage CBCB Storage]) :&lt;br /&gt;
** Local harddrives (usually mounted as /scratch on the machines that have this resource).  These are not backed up, are quite fast (they live physically close to the processor), but can only be &#039;seen&#039; by the machine where they are mounted and, thus, require data staging in/out (which can take a while)&lt;br /&gt;
** Shared 3Par storage (/fs/szasmg*, /fs/szdata/*, etc.).  This is very fast and very expensive disk and thus a limited resource. Please only use this space to store data temporarily, while you are running some analyses on it.  As a rule of thumb, if a file or collection of files of any considerable size have lived on this space for more than 1-2 weeks, they should probably be moved to the attic space (see below)&lt;br /&gt;
** Attic storage (/fs/szattic*).  This is cheaper and ample, but slow and brittle storage.  Your data-sets should primarily live here.  Due to it&#039;s brittleness, the IT department do not recommend you run any analyses directly in this volume, rather you copy the files over to a local harddrive or the 3Par instead, and copy the results back when done.&lt;br /&gt;
* You should remove any temporary results you don&#039;t need in the long term as soon as you&#039;ve generated them, and compress all of the large files.  Bzip2 works better than gzip but either should dramatically improve the space requirements, especially for text files such as fasta or fastq.&lt;br /&gt;
* You should ensure that your files are owned by the cbcb group and that they have group write permissions for any file stored on the 3Par, especially for all those in /fs/szscratch.  This will allow your colleagues to remove files in case the disk runs out of space and you are, for example, on vacation (in which case you shouldn&#039;t have any major files sitting around on the 3Par).&lt;br /&gt;
&lt;br /&gt;
For more information on the CBCB resources see [[Getting Started in CBCB]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Seminars ==&lt;br /&gt;
* [http://www.cbcb.umd.edu/seminars Regular CBCB seminars (during academic year)] &amp;lt;br&amp;gt;&lt;br /&gt;
* [[Cbcb:Works-In-Progress]] - Works in progress seminar schedule (Summer 2008) &amp;lt;br&amp;gt;&lt;br /&gt;
* [[short_read_sequencing|Short read sequencing Meeting]] (Fridays at 3pm)&lt;br /&gt;
&lt;br /&gt;
== Projects ==&lt;br /&gt;
&lt;br /&gt;
* [[Project:Pop-Lab|Pop-Lab]]&lt;br /&gt;
* [[Project:Hcbravo-lab|HCBravo Lab]]&lt;br /&gt;
* [[Project:Cloud-Computing|Cloud Computing]]&lt;br /&gt;
* [[Project:SummerInternships|Summer Internship Projects]]&lt;br /&gt;
* [[Metagenomics Reading Group (Wed 2pm)]]&lt;br /&gt;
&lt;br /&gt;
== People ==&lt;br /&gt;
 &lt;br /&gt;
* [[User:ayres|Daniel Ayres]]&lt;br /&gt;
* [[User:pknut777|Adam Bazinet]] &lt;br /&gt;
* [[User:irina|Irina Astrovskaya]] &lt;br /&gt;
* [[User:jpaulson|Joseph Paulson]]  &lt;br /&gt;
* [[User:mpop|Mihai Pop]] &lt;br /&gt;
* [[User:nelsayed|Najib El-Sayed]]&lt;br /&gt;
&lt;br /&gt;
== Getting started ==&lt;br /&gt;
If you have just received a new umiacs account through CBCB, follow the instructions on this page to get the basic information you&#039;ll need to start working:&amp;lt;br&amp;gt;&lt;br /&gt;
*[[Getting Started in CBCB]]&lt;br /&gt;
*[[CBCB Software Modules]]&lt;br /&gt;
*[[Torque]]&lt;br /&gt;
*[https://wiki.umiacs.umd.edu/cbcb-private/index.php/Storage CBCB Storage]&lt;br /&gt;
*[https://wiki.umiacs.umd.edu/cbcb-private/index.php/Compute CBCB Computers]&lt;br /&gt;
*[[Communal Software]]&lt;/div&gt;</summary>
		<author><name>Lmendelo</name></author>
	</entry>
	<entry>
		<id>https://wiki.umiacs.umd.edu/cbcb/index.php?title=CBCB_Software_Modules&amp;diff=9019</id>
		<title>CBCB Software Modules</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/cbcb/index.php?title=CBCB_Software_Modules&amp;diff=9019"/>
		<updated>2015-03-03T18:19:12Z</updated>

		<summary type="html">&lt;p&gt;Lmendelo: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Starting in the Spring of 2015, communal CBCB Bioinformatics Software has been installed using GNU Modules. &amp;lt;span style=&amp;quot;color: blue;&amp;quot;&amp;gt;Please note that the instructions below are for use with Red Hat 7 machines only.&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Common Modules ==&lt;br /&gt;
&lt;br /&gt;
CBCB Software modules are already configured for interactive shells on Red Hat 7 machines - no additional setup is required. The module files are installed in the following location:&lt;br /&gt;
 /cbcb/sw/RedHat-7-x86_64/common/modules/release/latest&lt;br /&gt;
&lt;br /&gt;
To see see what modules are available:&lt;br /&gt;
 $ module avail&lt;br /&gt;
&lt;br /&gt;
To add a module to your environment, use &amp;lt;code&amp;gt;module add&amp;lt;/code&amp;gt;:&lt;br /&gt;
 $ module add samtools/0.1.19&lt;br /&gt;
&lt;br /&gt;
Note that you can also specify the software name without the version:&lt;br /&gt;
 $ module add samtools&lt;br /&gt;
&lt;br /&gt;
Now samtools has been added to your environment:&lt;br /&gt;
 $ which samtools&lt;br /&gt;
 /cbcb/sw/RedHat-7-x86_64/common/local/samtools/0.1.19/bin/samtools&lt;br /&gt;
&lt;br /&gt;
== Personal Modules ==&lt;br /&gt;
&lt;br /&gt;
We have created some scripts to assist you with installing software and modules to your personal directory in &amp;lt;code&amp;gt;/cbcb/sw&amp;lt;/code&amp;gt;. We recommend that you use these scripts because this will help us share installed software among other CBCB users.&lt;br /&gt;
&lt;br /&gt;
Run this initialization script to set up your directory structure:&lt;br /&gt;
 $ /cbcb/sw/RedHat-7-x86_64/common/scripts/init_cbcb_sw_user.sh&lt;br /&gt;
&lt;br /&gt;
This will create a directory for you:&lt;br /&gt;
 $ tree /cbcb/sw/RedHat-7-x86_64/users/&amp;lt;username&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
/cbcb/sw/RedHat-7-x86_64/users/&amp;lt;username&amp;gt;&lt;br /&gt;
├── local&lt;br /&gt;
├── modules&lt;br /&gt;
│   └── &amp;lt;username&amp;gt;&lt;br /&gt;
│       └── env&lt;br /&gt;
├── module_template&lt;br /&gt;
├── README&lt;br /&gt;
├── scripts&lt;br /&gt;
│   ├── copy_module_template.sh&lt;br /&gt;
│   ├── init_install_vars.sh&lt;br /&gt;
│   └── install_package.sh&lt;br /&gt;
└── src&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Use the &amp;lt;code&amp;gt;src&amp;lt;/code&amp;gt; directory for storing and compiling source code.&lt;br /&gt;
* Use the &amp;lt;code&amp;gt;local&amp;lt;/code&amp;gt; directory as the installation prefix.&lt;br /&gt;
* Use the &amp;lt;code&amp;gt;modules&amp;lt;/code&amp;gt; directory to store your modulefiles.&lt;br /&gt;
&lt;br /&gt;
See [[#Installing Software]] below.&lt;br /&gt;
&lt;br /&gt;
To make use of your personal module file directory, add the following to your &amp;lt;code&amp;gt;~/.bashrc&amp;lt;/code&amp;gt;:&lt;br /&gt;
 module use /cbcb/sw/RedHat-7-x86_64/users/&amp;lt;username&amp;gt;/modules&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Installing Software ===&lt;br /&gt;
&lt;br /&gt;
Use the &amp;lt;code&amp;gt;install_package.sh&amp;lt;/code&amp;gt; script to automatically compile software that uses &amp;lt;code&amp;gt;./configure; make; make install&amp;lt;/code&amp;gt;. The advantage to using this install script is that it will:&lt;br /&gt;
* use the standardized directory structure for personal software installation, and&lt;br /&gt;
* &#039;&#039;&#039;&#039;&#039;automatically&#039;&#039;&#039;&#039;&#039; create a module file for the software in your &amp;lt;code&amp;gt;modules&amp;lt;/code&amp;gt; directory!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For full details, read the &amp;lt;code&amp;gt;README&amp;lt;/code&amp;gt; placed in your personal directory (&amp;lt;code&amp;gt;/cbcb/sw/RedHat-7-x86_64/users/&amp;lt;username&amp;gt;&amp;lt;/code&amp;gt;). It&#039;s also available in the [https://gitlab.umiacs.umd.edu/cbcb/cbcb-sw/blob/master/templates/user_readme.md  cbcb-sw Gitlab repository].&lt;br /&gt;
&lt;br /&gt;
== Setup for non-interactive shells ==&lt;br /&gt;
&lt;br /&gt;
Modules are already configured for interactive shells, but to use modules with non-interactive shells such as [[Torque]], add the following to your ~/.bashrc:&lt;br /&gt;
 . /usr/share/Modules/init/bash&lt;br /&gt;
 . /etc/profile.d/ummodules.sh&lt;br /&gt;
&lt;br /&gt;
For more information, see the [https://wiki.umiacs.umd.edu/umiacs/index.php/Modules UMIACS wiki].&lt;br /&gt;
&lt;br /&gt;
== GNU Modules Cheatsheet ==&lt;br /&gt;
&lt;br /&gt;
Ask for help:&lt;br /&gt;
 module --help&lt;br /&gt;
&lt;br /&gt;
List available modules:&lt;br /&gt;
 module avail&lt;br /&gt;
&lt;br /&gt;
Add a module to your environment:&lt;br /&gt;
 module add blast&lt;br /&gt;
&lt;br /&gt;
List loaded modules:&lt;br /&gt;
 module list&lt;br /&gt;
&lt;br /&gt;
Remove a module from your environment:&lt;br /&gt;
 module rm blast&lt;br /&gt;
&lt;br /&gt;
Remove all modules from your environment:&lt;br /&gt;
 module purge&lt;br /&gt;
&lt;br /&gt;
Add a path to search for available modules:&lt;br /&gt;
 module use /cbcb/sw/RedHat-7-x86_64/users/lmendelo/modules&lt;br /&gt;
&lt;br /&gt;
See what changes a module makes to your environment:&lt;br /&gt;
 module show Python2/common/2.7.9&lt;br /&gt;
&lt;br /&gt;
== Contact ==&lt;br /&gt;
&lt;br /&gt;
Brought to you by:&lt;br /&gt;
&lt;br /&gt;
* [mailto:abelew@umiacs.umd.edu Trey Belew]&lt;br /&gt;
* [mailto:keith@umiacs.umd.edu Keith Hughitt]&lt;br /&gt;
* [mailto:lmendelo@umiacs.umd.edu Lee Mendelowitz]&lt;br /&gt;
&lt;br /&gt;
== See Also ==&lt;br /&gt;
* [https://wiki.umiacs.umd.edu/umiacs/index.php/Modules UMIACS wiki]&lt;br /&gt;
* [https://gitlab.umiacs.umd.edu/cbcb/cbcb-sw Repository on GitLab]&lt;br /&gt;
* [https://docs.google.com/presentation/d/1UgKtnjcqHlpLZU79hGXfkgvNtse-ksMQ_gJMFCVLKRw/edit?usp=sharing CBCB Software slides on Google Drive]&lt;/div&gt;</summary>
		<author><name>Lmendelo</name></author>
	</entry>
	<entry>
		<id>https://wiki.umiacs.umd.edu/cbcb/index.php?title=Getting_Started_in_CBCB&amp;diff=9018</id>
		<title>Getting Started in CBCB</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/cbcb/index.php?title=Getting_Started_in_CBCB&amp;diff=9018"/>
		<updated>2015-03-03T18:16:56Z</updated>

		<summary type="html">&lt;p&gt;Lmendelo: /* Configuring Your Home Directory and Shell */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;You may want to review the following:&lt;br /&gt;
&lt;br /&gt;
[[Media:CBCB-quick-guide.pdf]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Getting Building Access and Room Keys==&lt;br /&gt;
&lt;br /&gt;
CBCB is located on the 3rd floor of The Biomolecular Sciences Building identified on campus maps as Building #296.  The building is secure and access is gained by either using your UM ID card, guest card or entering the 3-digit code of the person you to visit at the call box on the right side of the front door.&lt;br /&gt;
&lt;br /&gt;
Contact the Center Coordinator, Christine Bogan, about gaining card access to the building.  She will need the following information:&lt;br /&gt;
*An notification email from your sponsor/adviser&lt;br /&gt;
*Your Name&lt;br /&gt;
*Your 9 Digit University ID number&lt;br /&gt;
*Your Contact email&lt;br /&gt;
&lt;br /&gt;
Along with your assigned space and phone numbers, the coordinator will send your information to UMIACS Coordinator Edna Walker who will contact campus security to add you into their system.  &#039;&#039;Note: clearance usually takes a number of days, so contact the coordinator as soon as possible.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
If you prefer not to send your information through email feel free to contact the coordinator in person.  &lt;br /&gt;
&lt;br /&gt;
You must get your key from the coordinator in person.&lt;br /&gt;
&lt;br /&gt;
Christine Bogan&amp;lt;br&amp;gt;&lt;br /&gt;
Room 3121&amp;lt;br&amp;gt;&lt;br /&gt;
Biomolecular Sciences Bldg #296&amp;lt;br&amp;gt;&lt;br /&gt;
301.405.5936&amp;lt;br&amp;gt;&lt;br /&gt;
cbogan[at]umd.edu&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Research In Progress Seminars==&lt;br /&gt;
&lt;br /&gt;
These seminars are held through the year.  For information go to [http://cbcb.umd.edu/node/18625 CBCB Research in Progress]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For a list of our Disk Storage and amount of available space left on each one, see [http://wiki.umiacs.umd.edu/cbcb-private/index.php/Storage wiki.umiacs.umd.edu/cbcb-private/index.php/Storage]&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Configuring Your Home Directory and Shell ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p style=&amp;quot;color: #e70000; font-weight: bold; font-size: medium;&amp;quot;&amp;gt;WARNING: &amp;lt;code&amp;gt;/fs/sz-user-supported/&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;/cbcb/software&amp;lt;/code&amp;gt; has been deprecated as of March 2015. Please move towards using Red Hat 7 machines and [[CBCB Software Modules]]. &amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
We import common settings files that set our path variables to include commonly shared software repositories.&lt;br /&gt;
&lt;br /&gt;
As a start, add the following line to the top of the file called &amp;quot;.bashrc&amp;quot; located in your home directory (/nfshomes/username/):&lt;br /&gt;
&lt;br /&gt;
 . /fs/sz-user-supported/share/dotfiles/bashrc.cbcb&lt;br /&gt;
&lt;br /&gt;
This will import the common bashrc.cbcb file into your own bashrc file every time you log in.&lt;br /&gt;
&lt;br /&gt;
Now add this line to your &amp;quot;.bash_profile&amp;quot; file, also located in your home directory:&lt;br /&gt;
&lt;br /&gt;
 . ~/.bashrc&lt;br /&gt;
&lt;br /&gt;
This will import your personal bashrc file every time you log in. Now you should have access to most of the locally installed software like &amp;quot;blastall&amp;quot; and &amp;quot;AMOS.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
If you want to add any addition commands to your bashrc file, such as setting your default text editor to &amp;quot;vim&amp;quot; or formatting the output of bash commands (eg. &amp;quot;ls&amp;quot;), add the appropriate commands after the imported common files as shown in this example:&lt;br /&gt;
&lt;br /&gt;
 . /fs/sz-user-supported/share/dotfiles/bashrc.cbcb&lt;br /&gt;
 &lt;br /&gt;
 alias vi=&#039;vim&#039;&lt;br /&gt;
&lt;br /&gt;
 alias ls=&#039;ls --color&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
If you decide you want to change the settings in the common bashrc.cbcb to better suit your personal needs, then please copy and paste its contents into your personal bashrc file. &#039;&#039;&#039;Do not modify the common bashrc.cbcb file as it will affect everyone&#039;s environment.&#039;&#039;&#039; Also check back periodically as people may add common paths for new software.&lt;br /&gt;
&lt;br /&gt;
If you have any other problems, contact staff [at] umiacs.umd.edu or your PI. &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
More resources can be found at [https://wiki.umiacs.umd.edu/umiacs/index.php/GettingStarted umiacs wiki]&lt;br /&gt;
&lt;br /&gt;
== CBCB Software Modules ==&lt;br /&gt;
To use CBCB Software Modules, see [[CBCB Software Modules]]&lt;br /&gt;
&lt;br /&gt;
== Printing ==&lt;br /&gt;
Go to the umiacs wiki to find [https://wiki.umiacs.umd.edu/umiacs/index.php/Printing system-specific guides for printing], and be sure to [https://wiki.umiacs.umd.edu/umiacs/index.php/PrinterQueueNaming add &#039;nb&#039; to the end of your print queue] to avoid wasting paper printing banners.&lt;br /&gt;
&lt;br /&gt;
== Using the Wiki ==&lt;br /&gt;
* [http://en.wikipedia.org/wiki/Wikipedia:Cheatsheet Wiki Formatting Cheatsheet]&lt;br /&gt;
* [http://www.mediawiki.org/wiki/Help:Configuration_settings Configuration settings list]&lt;br /&gt;
* [http://www.mediawiki.org/wiki/Help:FAQ MediaWiki FAQ]&lt;br /&gt;
* [http://mail.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]&lt;br /&gt;
&lt;br /&gt;
== When You Travel ==&lt;br /&gt;
&lt;br /&gt;
[[Media:CBCB_travel_request_form_oct_2014.pdf‎]] form to fill out to obtain information for travel reimbursement&lt;br /&gt;
&lt;br /&gt;
[[Media:Travel_101_cbcb_revised_4-2013.pdf]] for more detailed travel info&lt;/div&gt;</summary>
		<author><name>Lmendelo</name></author>
	</entry>
	<entry>
		<id>https://wiki.umiacs.umd.edu/cbcb/index.php?title=Communal_Software&amp;diff=9017</id>
		<title>Communal Software</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/cbcb/index.php?title=Communal_Software&amp;diff=9017"/>
		<updated>2015-03-03T18:09:47Z</updated>

		<summary type="html">&lt;p&gt;Lmendelo: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= WARNING! =&lt;br /&gt;
This information is outdated. See [[CBCB Software Modules]] for using CBCB Communal Software.&lt;br /&gt;
&lt;br /&gt;
== Introduction ==&lt;br /&gt;
CBCB users do not have root access on their machines or the communal servers. Communal CBCB software is therefore typically installed in&lt;br /&gt;
 /fs/sz-user-supported/&lt;br /&gt;
There are two primary subdirectories which differ by architecture. For the most part, 32bit software is installed in&lt;br /&gt;
 /fs/sz-user-supported/Linux-i686/&lt;br /&gt;
while 64bit software is installed in&lt;br /&gt;
 /fs/sz-user-supported/Linux-x86_64/&lt;br /&gt;
The appropriate subdirectory is typically dynamically chosen by embedding&lt;br /&gt;
 /fs/sz-user-supported/`uname`-`uname -m`&lt;br /&gt;
in a user&#039;s path variables in their bashrc/tcshrc file.&lt;br /&gt;
&lt;br /&gt;
Installing software to these directories and updating a user&#039;s path can be tricky. For this reason, many users choose to maintain specialty software in personal directories.&lt;br /&gt;
&lt;br /&gt;
== Core Software ==&lt;br /&gt;
&lt;br /&gt;
The latest versions of the most frequently used CBCB software is installed under&lt;br /&gt;
  /fs/szdevel/core-cbcb-software/&lt;br /&gt;
and follows a directory structure similar to&lt;br /&gt;
  /fs/sz-user-supported/&lt;br /&gt;
The software is installed and maintained by the cbcb-staff group.&lt;br /&gt;
&lt;br /&gt;
Software list: &lt;br /&gt;
  &#039;&#039;&#039;Name                      version&#039;&#039;&#039;&lt;br /&gt;
  Bio::Perl &lt;br /&gt;
  Biopython&lt;br /&gt;
  Bowtie                    0.12.7&lt;br /&gt;
  Celera Assembler          6.1&lt;br /&gt;
  gcc                       4.5.1&lt;br /&gt;
  GMap,GSnap                2010-07-27&lt;br /&gt;
  Java (JRE only)           1.6.0_22&lt;br /&gt;
  NCBI blast&lt;br /&gt;
  Newbler                   2.5 &lt;br /&gt;
  R&lt;br /&gt;
  Samtools                  0.1.9&lt;br /&gt;
  SOAPdeNovo                1.04&lt;br /&gt;
  Velvet                    1.0.13&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Planned Maintenance (Summer 2012) ==&lt;br /&gt;
The Pop lab is currently planning to update much of the communal software installed in sz-user-supported over the Summer of 2012. So far this list includes:&lt;br /&gt;
* [http://sourceforge.net/apps/mediawiki/amos/index.php?title=AMOS AMOS] -- Already installed&lt;br /&gt;
* [http://www.ncbi.nlm.nih.gov/staff/tao/URLAPI/blastall/index.html blastall 2.2.23] -- May not be worth upgrading from 2.2.18. Will look at release notes.&lt;br /&gt;
* [http://hmmer.janelia.org/ HMMer3] -- Installed.&lt;br /&gt;
** [http://pfam.sanger.ac.uk/ Pfam 24.0]&lt;br /&gt;
* PERL -- May attempt to standardize default version across servers.&lt;br /&gt;
** [http://www.bioperl.org/wiki/Main_Page BioPERL]&lt;br /&gt;
* Python -- May attempt to standardize default version across servers.&lt;br /&gt;
** [http://biopython.org/wiki/Main_Page BioPython]&lt;br /&gt;
*** [http://numpy.scipy.org/ NumPy]&lt;br /&gt;
*** [http://www.reportlab.com/software/opensource/ ReportLab]&lt;br /&gt;
Please feel free to contact Ted Gibbons at tgibbons@umd.edu to make suggestions or express concerns about tampering with the communal software installations and the corresponding paths in the communal CBCB bashrc file.&lt;/div&gt;</summary>
		<author><name>Lmendelo</name></author>
	</entry>
	<entry>
		<id>https://wiki.umiacs.umd.edu/cbcb/index.php?title=CBCB_Software_Modules&amp;diff=9016</id>
		<title>CBCB Software Modules</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/cbcb/index.php?title=CBCB_Software_Modules&amp;diff=9016"/>
		<updated>2015-03-03T18:08:06Z</updated>

		<summary type="html">&lt;p&gt;Lmendelo: /* Setup for non-interactive shells */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Starting in the Spring of 2015, communal CBCB Bioinformatics Software has been installed using GNU Modules.&lt;br /&gt;
&lt;br /&gt;
== Common Modules ==&lt;br /&gt;
&lt;br /&gt;
CBCB Software modules are already configured for interactive shells on Red Hat 7 machines - no additional setup is required. The module files are installed in the following location:&lt;br /&gt;
 /cbcb/sw/RedHat-7-x86_64/common/modules/release/latest&lt;br /&gt;
&lt;br /&gt;
To see see what modules are available:&lt;br /&gt;
 $ module avail&lt;br /&gt;
&lt;br /&gt;
To add a module to your environment, use &amp;lt;code&amp;gt;module add&amp;lt;/code&amp;gt;:&lt;br /&gt;
 $ module add samtools/0.1.19&lt;br /&gt;
&lt;br /&gt;
Note that you can also specify the software name without the version:&lt;br /&gt;
 $ module add samtools&lt;br /&gt;
&lt;br /&gt;
Now samtools has been added to your environment:&lt;br /&gt;
 $ which samtools&lt;br /&gt;
 /cbcb/sw/RedHat-7-x86_64/common/local/samtools/0.1.19/bin/samtools&lt;br /&gt;
&lt;br /&gt;
== Personal Modules ==&lt;br /&gt;
&lt;br /&gt;
We have created some scripts to assist you with installing software and modules to your personal directory in &amp;lt;code&amp;gt;/cbcb/sw&amp;lt;/code&amp;gt;. We recommend that you use these scripts because this will help us share installed software among other CBCB users.&lt;br /&gt;
&lt;br /&gt;
Run this initialization script to set up your directory structure:&lt;br /&gt;
 $ /cbcb/sw/RedHat-7-x86_64/common/scripts/init_cbcb_sw_user.sh&lt;br /&gt;
&lt;br /&gt;
This will create a directory for you:&lt;br /&gt;
 $ tree /cbcb/sw/RedHat-7-x86_64/users/&amp;lt;username&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
/cbcb/sw/RedHat-7-x86_64/users/&amp;lt;username&amp;gt;&lt;br /&gt;
├── local&lt;br /&gt;
├── modules&lt;br /&gt;
│   └── &amp;lt;username&amp;gt;&lt;br /&gt;
│       └── env&lt;br /&gt;
├── module_template&lt;br /&gt;
├── README&lt;br /&gt;
├── scripts&lt;br /&gt;
│   ├── copy_module_template.sh&lt;br /&gt;
│   ├── init_install_vars.sh&lt;br /&gt;
│   └── install_package.sh&lt;br /&gt;
└── src&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Use the &amp;lt;code&amp;gt;src&amp;lt;/code&amp;gt; directory for storing and compiling source code.&lt;br /&gt;
* Use the &amp;lt;code&amp;gt;local&amp;lt;/code&amp;gt; directory as the installation prefix.&lt;br /&gt;
* Use the &amp;lt;code&amp;gt;modules&amp;lt;/code&amp;gt; directory to store your modulefiles.&lt;br /&gt;
&lt;br /&gt;
See [[#Installing Software]] below.&lt;br /&gt;
&lt;br /&gt;
To make use of your personal module file directory, add the following to your &amp;lt;code&amp;gt;~/.bashrc&amp;lt;/code&amp;gt;:&lt;br /&gt;
 module use /cbcb/sw/RedHat-7-x86_64/users/&amp;lt;username&amp;gt;/modules&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Installing Software ===&lt;br /&gt;
&lt;br /&gt;
Use the &amp;lt;code&amp;gt;install_package.sh&amp;lt;/code&amp;gt; script to automatically compile software that uses &amp;lt;code&amp;gt;./configure; make; make install&amp;lt;/code&amp;gt;. The advantage to using this install script is that it will:&lt;br /&gt;
* use the standardized directory structure for personal software installation, and&lt;br /&gt;
* &#039;&#039;&#039;&#039;&#039;automatically&#039;&#039;&#039;&#039;&#039; create a module file for the software in your &amp;lt;code&amp;gt;modules&amp;lt;/code&amp;gt; directory!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For full details, read the &amp;lt;code&amp;gt;README&amp;lt;/code&amp;gt; placed in your personal directory (&amp;lt;code&amp;gt;/cbcb/sw/RedHat-7-x86_64/users/&amp;lt;username&amp;gt;&amp;lt;/code&amp;gt;). It&#039;s also available in the [https://gitlab.umiacs.umd.edu/cbcb/cbcb-sw/blob/master/templates/user_readme.md  cbcb-sw Gitlab repository].&lt;br /&gt;
&lt;br /&gt;
== Setup for non-interactive shells ==&lt;br /&gt;
&lt;br /&gt;
Modules are already configured for interactive shells, but to use modules with non-interactive shells such as [[Torque]], add the following to your ~/.bashrc:&lt;br /&gt;
 . /usr/share/Modules/init/bash&lt;br /&gt;
 . /etc/profile.d/ummodules.sh&lt;br /&gt;
&lt;br /&gt;
For more information, see the [https://wiki.umiacs.umd.edu/umiacs/index.php/Modules UMIACS wiki].&lt;br /&gt;
&lt;br /&gt;
== GNU Modules Cheatsheet ==&lt;br /&gt;
&lt;br /&gt;
Ask for help:&lt;br /&gt;
 module --help&lt;br /&gt;
&lt;br /&gt;
List available modules:&lt;br /&gt;
 module avail&lt;br /&gt;
&lt;br /&gt;
Add a module to your environment:&lt;br /&gt;
 module add blast&lt;br /&gt;
&lt;br /&gt;
List loaded modules:&lt;br /&gt;
 module list&lt;br /&gt;
&lt;br /&gt;
Remove a module from your environment:&lt;br /&gt;
 module rm blast&lt;br /&gt;
&lt;br /&gt;
Remove all modules from your environment:&lt;br /&gt;
 module purge&lt;br /&gt;
&lt;br /&gt;
Add a path to search for available modules:&lt;br /&gt;
 module use /cbcb/sw/RedHat-7-x86_64/users/lmendelo/modules&lt;br /&gt;
&lt;br /&gt;
See what changes a module makes to your environment:&lt;br /&gt;
 module show Python2/common/2.7.9&lt;br /&gt;
&lt;br /&gt;
== Contact ==&lt;br /&gt;
&lt;br /&gt;
Brought to you by:&lt;br /&gt;
&lt;br /&gt;
* [mailto:abelew@umiacs.umd.edu Trey Belew]&lt;br /&gt;
* [mailto:keith@umiacs.umd.edu Keith Hughitt]&lt;br /&gt;
* [mailto:lmendelo@umiacs.umd.edu Lee Mendelowitz]&lt;br /&gt;
&lt;br /&gt;
== See Also ==&lt;br /&gt;
* [https://wiki.umiacs.umd.edu/umiacs/index.php/Modules UMIACS wiki]&lt;br /&gt;
* [https://gitlab.umiacs.umd.edu/cbcb/cbcb-sw Repository on GitLab]&lt;br /&gt;
* [https://docs.google.com/presentation/d/1UgKtnjcqHlpLZU79hGXfkgvNtse-ksMQ_gJMFCVLKRw/edit?usp=sharing CBCB Software slides on Google Drive]&lt;/div&gt;</summary>
		<author><name>Lmendelo</name></author>
	</entry>
	<entry>
		<id>https://wiki.umiacs.umd.edu/cbcb/index.php?title=Torque&amp;diff=9015</id>
		<title>Torque</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/cbcb/index.php?title=Torque&amp;diff=9015"/>
		<updated>2015-03-03T18:07:30Z</updated>

		<summary type="html">&lt;p&gt;Lmendelo: /* Getting Started */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Getting Started==&lt;br /&gt;
&lt;br /&gt;
Torque is a resource manager that interacts with another program called Maui which provides the scheduling for the cluster.   To get started you will need to ensure that your [https://wiki.umiacs.umd.edu/umiacs/index.php/SSH#SSH_Keys_.28and_Passwordless_SSH.29 SSH keys] are setup for password-less SSH.  In our Torque environments this is critical to delivering the error and output of your jobs back to where the job was submitted from. Please note that [https://wiki.umiacs.umd.edu/umiacs/index.php/Fairshare Fair Share] is enabled in this setup, with a historical scope of 12 hours.&lt;br /&gt;
&lt;br /&gt;
The hosts that you can submit from are any CBCB Workstation and the &amp;lt;tt&amp;gt;ibissub00.umiacs.umd.edu&amp;lt;/tt&amp;gt;, &amp;lt;tt&amp;gt;ibissub01.umiacs.umd.edu&amp;lt;/tt&amp;gt;, and &amp;lt;tt&amp;gt;heronsub00.umiacs.umd.edu&amp;lt;/tt&amp;gt; nodes.&lt;br /&gt;
&lt;br /&gt;
Now that you have that setup here are the queues that are available to users. Use &amp;lt;code&amp;gt;qstat -Q -f&amp;lt;/code&amp;gt; to see the resource limits for each queue.&lt;br /&gt;
&lt;br /&gt;
=== Red Hat 5 Queues ===&lt;br /&gt;
&lt;br /&gt;
* default- default memory is 3GB (max 4GB), default walltime is 1 hour (max 1 hour), allows up to 16 jobs per user concurrently&lt;br /&gt;
* shell - interactive jobs only - default memory is 2GB (max 4GB), default walltime is 12 hours (max 2 wks), allows up to 4 jobs per user concurrently - restricted to nodes with &#039;&#039;&#039;shell&#039;&#039;&#039;* property&lt;br /&gt;
* workstation - default memory is 4GB (max 47GB), default walltime is 8 hours (max one week), allows up to 4 jobs per user concurrently&lt;br /&gt;
* throughput  - no interactive jobs - default memory is 4GB (max 36GB), default walltime is 4 hours (max 18 hours), allows up to 125 jobs per user concurrently - restricted to nodes with &#039;&#039;&#039;ibis&#039;&#039;&#039;* property&lt;br /&gt;
* high_throughput - no interactive jobs - default memory is 4gb (max 8GB), default walltime is 3 hours (max 6 hours), allows up to 300 jobs per user concurrently - restricted to nodes with &#039;&#039;&#039;ibis&#039;&#039;&#039;* property&lt;br /&gt;
* long - no interactive jobs - default memory is 12gb (max 12gb), default walltime is 8 hours (max 1 week), allows up to 16 jobs per user concurrently&lt;br /&gt;
* large - no interactive jobs -default memory is 32GB (max 120GB), default walltime is 24 hours (max 11 days), allows up to 3 jobs per user concurrently&lt;br /&gt;
* xlarge - default memory is 100GB (max is unlimited), default walltime is 1 week (max 3 weeks), allows 1 job per user at a time&lt;br /&gt;
** The xlarge queue is restricted to members of the group cbcbtorque. If you need to run large jobs please send mail to staff@umiacs.umd.edu&lt;br /&gt;
&lt;br /&gt;
=== Red Hat 7 Queues ===&lt;br /&gt;
&lt;br /&gt;
These queues submit jobs to the RHEL 7 heron* nodes.&lt;br /&gt;
&lt;br /&gt;
* new_workstation  - default memory is 4GB (max 47GB), default walltime is 8 hours (max one week), allows up to 4 jobs per user concurrently&lt;br /&gt;
* new_throughput - no interactive jobs - default memory is 4GB (max 36GB), default walltime is 4 hours (max 18 hours), allows up to 125 jobs per user concurrently &lt;br /&gt;
* new_hthroughput - no interactive jobs - default memory is 4gb (max 8GB), default walltime is 3 hours (max 6 hours), allows up to 300 jobs per user concurrently&lt;br /&gt;
* new_large - no interactive jobs -default memory is 32GB (max 120GB), default walltime is 24 hours (max 11 days), allows up to 3 jobs per user concurrently&lt;br /&gt;
&amp;lt;nowiki&amp;gt;*&amp;lt;/nowiki&amp;gt;You can list nodes with a specific property by running &amp;quot;pbsnodes :property&amp;quot; where property is the specific property you want to see&lt;br /&gt;
&lt;br /&gt;
===qsub===&lt;br /&gt;
&lt;br /&gt;
qsub is how you submit jobs into a Torque cluster.  A job is a shell script that is given as STDIN or as a file on the command line.  The -l (lower case L) option allows the user to specify some options for your job submission. While your jobs will not always be penalized for using more resources or fewer resources than you request, it is very important to request resources as accurately as possible so that torque knows how many resources each machine has available when new jobs are scheduled. If your job is using more resources than you request, another job may be scheduled on that same machine and could potentially run the machine out of resources and cause segfaults and eventually bring down the machine; likewise, if you request more resources than you need, it will slow down the execution of other users&#039; jobs because torque may think a machine is at capacity when it actually is not.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
To specify the queue that you would like to submit to, use the -q option,&lt;br /&gt;
&lt;br /&gt;
  qsub -q workstation&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Use these options with the -l (lower case L) option to request resources:&lt;br /&gt;
&lt;br /&gt;
* ncpus=4&lt;br /&gt;
* mem=32GB&lt;br /&gt;
* walltime=12:00:00&lt;br /&gt;
&lt;br /&gt;
You can find a full list of job submission arguments see here [http://docs.adaptivecomputing.com/torque/4-2-6/help.htm#topics/2-jobs/jobSubmission.htm Torque Job Submission Arguments].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
As an example, to run the perl script myscript.pl on 4 CPUs with 128GB of memory for 12 hours you could run the following,&lt;br /&gt;
&lt;br /&gt;
  qsub -q large -l ncpus=4,mem=128GB,walltime=12:00:00 myscript.pl&lt;br /&gt;
&lt;br /&gt;
Note that the large queue was used in the above example because 128GB is more memory than the max allowed in all of the other queues. By default, all of the other queues reserve approximately the maximum memory allowed for that queue, but you may set a lower reservation if you know you will not need the full amount.&lt;br /&gt;
&lt;br /&gt;
Once you have submitted your job for execution you will get something back in the form of,&lt;br /&gt;
&lt;br /&gt;
  &amp;lt;JOBID&amp;gt;.&amp;lt;PBSSERVER&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You can use that &amp;lt;JOBID&amp;gt; to delete or find your job later if there is a problem.&lt;br /&gt;
&lt;br /&gt;
When a job finishes, Torque/PBS deposits the standard output and standard error as&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;jobname&amp;gt;.o&amp;lt;number&amp;gt; &lt;br /&gt;
* &amp;lt;jobname&amp;gt;.e&amp;lt;number&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Where &amp;lt;jobname&amp;gt; is the name of the script you submitted (or STDIN if it came from qsub&#039;s standard in), and &amp;lt;number&amp;gt; is the leading number in the job id.&lt;br /&gt;
&lt;br /&gt;
====Interactive Jobs====&lt;br /&gt;
&lt;br /&gt;
Interactive jobs allow you to schedule interactive shell access on Torque-scheduled compute nodes. You can get an interactive session with the -I (upper case i) option,&lt;br /&gt;
&lt;br /&gt;
  qsub -I &lt;br /&gt;
&lt;br /&gt;
Please note that only the &amp;quot;workstation&amp;quot;, &amp;quot;shell&amp;quot;, and &amp;quot;default&amp;quot; queues allow interactive jobs. If you require larger resource allocations than the queue defaults, the -l (lower case L) flag still applies.&lt;br /&gt;
&lt;br /&gt;
====Array Jobs====&lt;br /&gt;
&lt;br /&gt;
Array jobs let you submit the same script multiple times, each with a different setting for the environment variable &amp;lt;code&amp;gt;PBS_ARRAYID&amp;lt;/code&amp;gt;:&lt;br /&gt;
&lt;br /&gt;
 qsub -q throughput -t 0-999 my_script.sh&lt;br /&gt;
&lt;br /&gt;
Torque will run 1000 instances of &amp;lt;code&amp;gt;my_script.sh&amp;lt;/code&amp;gt; with the environment variable &amp;lt;code&amp;gt;PBS_ARRAYID&amp;lt;/code&amp;gt; set to the range of values specified by the &amp;lt;code&amp;gt;-t&amp;lt;/code&amp;gt; argument. In this case &amp;lt;code&amp;gt;my_script.sh&amp;lt;/code&amp;gt; will be executed once with &amp;lt;code&amp;gt;PBS_ARRAYID=0&amp;lt;/code&amp;gt;, again with  &amp;lt;code&amp;gt;PBS_ARRAYID=1&amp;lt;/code&amp;gt;, etc.&lt;br /&gt;
&lt;br /&gt;
You can also specify comma separate values for &amp;lt;code&amp;gt;PBS_ARRAYID&amp;lt;/code&amp;gt;:&lt;br /&gt;
&lt;br /&gt;
 qsub -q throughput -t 0,3,9  my_script.sh&lt;br /&gt;
&lt;br /&gt;
===qstat===&lt;br /&gt;
&lt;br /&gt;
This will display if any jobs are in the queue for your Torque cluster.  It is normally run with out any arguments and if it returns nothing then there is nothing running in the Torque cluster.&lt;br /&gt;
&lt;br /&gt;
Here is an example of what qstat will look like,&lt;br /&gt;
&lt;br /&gt;
&amp;lt;blockquote&amp;gt;&amp;lt;pre&amp;gt;&lt;br /&gt;
$ qstat&lt;br /&gt;
Job id                    Name             User            Time Use S Queue&lt;br /&gt;
------------------------- ---------------- --------------- -------- - -----&lt;br /&gt;
135.cbcbtorque             STDIN            tgray26         00:00:00 R workstation&lt;br /&gt;
136.cbcbtorque             STDIN            tgray26         00:00:00 R default        &lt;br /&gt;
137.cbcbtorque             STDIN            tgray26         00:00:00 R default        &lt;br /&gt;
138.cbcbtorque             STDIN            tgray26                0 Q workstation&lt;br /&gt;
&amp;lt;/pre&amp;gt;&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For full information about the default settings and maximum resource limits for a queue, use &amp;lt;code&amp;gt;qstat -Q -f&amp;lt;/code&amp;gt;:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;blockquote&amp;gt;&amp;lt;pre&amp;gt;&lt;br /&gt;
$ qstat -Q -f throughput&lt;br /&gt;
Queue: throughput&lt;br /&gt;
    queue_type = Execution&lt;br /&gt;
    total_jobs = 0&lt;br /&gt;
    state_count = Transit:0 Queued:0 Held:0 Waiting:0 Running:0 Exiting:0 Comp&lt;br /&gt;
	lete:0&lt;br /&gt;
    resources_max.mem = 36gb&lt;br /&gt;
    resources_max.nodect = 1&lt;br /&gt;
    resources_max.walltime = 18:00:00&lt;br /&gt;
    resources_default.mem = 4gb&lt;br /&gt;
    resources_default.walltime = 04:00:00&lt;br /&gt;
    mtime = 1424395185&lt;br /&gt;
    disallowed_types = interactive&lt;br /&gt;
    resources_assigned.mem = 0b&lt;br /&gt;
    resources_assigned.ncpus = 0&lt;br /&gt;
    resources_assigned.nodect = 0&lt;br /&gt;
    max_user_run = 125&lt;br /&gt;
    enabled = True&lt;br /&gt;
    started = True&lt;br /&gt;
&amp;lt;/pre&amp;gt;&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===qdel===&lt;br /&gt;
&lt;br /&gt;
You can remove a running or stalled job with the qdel command.  It requires that you give it a &amp;lt;JOBID&amp;gt; that can be found by running qstat.&lt;br /&gt;
&lt;br /&gt;
===pbsnodes===&lt;br /&gt;
&lt;br /&gt;
To find out what resources and nodes are available in the Torque cluster you can run pbsnodes.  It will give you back a detailed list of the nodes and their current status.&lt;br /&gt;
&lt;br /&gt;
For example,&lt;br /&gt;
&lt;br /&gt;
&amp;lt;blockquote&amp;gt;&amp;lt;pre&amp;gt;&lt;br /&gt;
$ pbsnodes&lt;br /&gt;
redbud.umiacs.umd.edu&lt;br /&gt;
     state = free&lt;br /&gt;
     np = 32&lt;br /&gt;
     ntype = cluster&lt;br /&gt;
     status = rectime=1343744604,varattr=,jobs=,state=free,netload=384208495,gres=,loadave=0.02,ncpus=64,&lt;br /&gt;
              physmem=528633432kb,availmem=530365780kb,totmem=530730576kb,idletime=489899,nusers=0,nsessions=? 0,&lt;br /&gt;
              sessions=? 0,uname=Linux redbud.umiacs.umd.edu 2.6.18-308.11.1.el5 #1 SMP Fri Jun 15 15:41:53 EDT 2012 x86_64,opsys=linux&lt;br /&gt;
     gpus = 0&lt;br /&gt;
&lt;br /&gt;
beech.umiacs.umd.edu&lt;br /&gt;
     state = free&lt;br /&gt;
     np = 2&lt;br /&gt;
     ntype = cluster&lt;br /&gt;
     status = rectime=1343744577,varattr=,jobs=,state=free,netload=425438230,gres=,loadave=0.00,ncpus=2,&lt;br /&gt;
              physmem=7154944kb,availmem=8960412kb,totmem=9252088kb,idletime=49,nusers=0,nsessions=? 0,&lt;br /&gt;
              sessions=? 0,uname=Linux beech.umiacs.umd.edu 2.6.18-308.11.1.el5 #1 SMP Fri Jun 15 15:41:53 EDT 2012 x86_64,opsys=linux&lt;br /&gt;
     gpus = 0&lt;br /&gt;
&amp;lt;/pre&amp;gt;&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Using CBCB Modules with Torque==&lt;br /&gt;
&lt;br /&gt;
To use [[CBCB Software Modules]] with Torque, you will need to add these lines to your &amp;lt;code&amp;gt;~/.bashrc&amp;lt;/code&amp;gt;:&lt;br /&gt;
&lt;br /&gt;
 . /usr/share/Modules/init/bash&lt;br /&gt;
 . /etc/profile.d/ummodules.sh&lt;br /&gt;
 &lt;br /&gt;
==Host Monitoring==&lt;br /&gt;
http://ganglia.umiacs.umd.edu/ganglia/?c=cbcb_compute&amp;amp;m=load_one&amp;amp;r=hour&amp;amp;s=by%20name&amp;amp;hc=4&amp;amp;mc=2&lt;/div&gt;</summary>
		<author><name>Lmendelo</name></author>
	</entry>
	<entry>
		<id>https://wiki.umiacs.umd.edu/cbcb/index.php?title=Torque&amp;diff=9014</id>
		<title>Torque</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/cbcb/index.php?title=Torque&amp;diff=9014"/>
		<updated>2015-03-03T18:03:53Z</updated>

		<summary type="html">&lt;p&gt;Lmendelo: /* qsub */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Getting Started==&lt;br /&gt;
&lt;br /&gt;
Torque is a resource manager that interacts with another program called Maui which provides the scheduling for the cluster.   To get started you will need to ensure that your [https://wiki.umiacs.umd.edu/umiacs/index.php/SSH#SSH_Keys_.28and_Passwordless_SSH.29 SSH keys] are setup for password-less SSH.  In our Torque environments this is critical to delivering the error and output of your jobs back to where the job was submitted from. Please note that [https://wiki.umiacs.umd.edu/umiacs/index.php/Fairshare Fair Share] is enabled in this setup, with a historical scope of 12 hours.&lt;br /&gt;
&lt;br /&gt;
The hosts that you can submit from are any CBCB Workstation and the &amp;lt;tt&amp;gt;ibissub00.umiacs.umd.edu&amp;lt;/tt&amp;gt;, &amp;lt;tt&amp;gt;ibissub01.umiacs.umd.edu&amp;lt;/tt&amp;gt;, and &amp;lt;tt&amp;gt;heronsub00.umiacs.umd.edu&amp;lt;/tt&amp;gt; nodes.&lt;br /&gt;
&lt;br /&gt;
Now that you have that setup here are the queues that are available to users. Use &amp;lt;code&amp;gt;qstat -Q -f&amp;lt;/code&amp;gt; to see the resource limits for each queue.&lt;br /&gt;
&lt;br /&gt;
=== Red Hat 5 Queues ===&lt;br /&gt;
&lt;br /&gt;
* default- default memory is 3GB (max 4GB), default walltime is 1 hour (max 1 hour), allows up to 16 jobs per user concurrently&lt;br /&gt;
* shell - interactive jobs only - default memory is 2GB (max 4GB), default walltime is 12 hours (max 2 wks), allows up to 4 jobs per user concurrently - restricted to nodes with &#039;&#039;&#039;shell&#039;&#039;&#039;* property&lt;br /&gt;
* workstation - default memory is 4GB (max 47GB), default walltime is 8 hours (max one week), allows up to 4 jobs per user concurrently&lt;br /&gt;
* throughput  - no interactive jobs - default memory is 4GB (max 36GB), default walltime is 4 hours (max 18 hours), allows up to 125 jobs per user concurrently - restricted to nodes with &#039;&#039;&#039;ibis&#039;&#039;&#039;* property&lt;br /&gt;
* high_throughput - no interactive jobs - default memory is 4gb (max 8GB), default walltime is 3 hours (max 6 hours), allows up to 300 jobs per user concurrently - restricted to nodes with &#039;&#039;&#039;ibis&#039;&#039;&#039;* property&lt;br /&gt;
* long - no interactive jobs - default memory is 12gb (max 12gb), default walltime is 8 hours (max 1 week), allows up to 16 jobs per user concurrently&lt;br /&gt;
* large - no interactive jobs -default memory is 32GB (max 120GB), default walltime is 24 hours (max 11 days), allows up to 3 jobs per user concurrently&lt;br /&gt;
* xlarge - default memory is 100GB (max is unlimited), default walltime is 1 week (max 3 weeks), allows 1 job per user at a time&lt;br /&gt;
** The xlarge queue is restricted to members of the group cbcbtorque. If you need to run large jobs please send mail to staff@umiacs.umd.edu&lt;br /&gt;
&lt;br /&gt;
=== Red Hat 7 Queues ===&lt;br /&gt;
&lt;br /&gt;
These queues submit jobs to the RHEL 7 heron* nodes.&lt;br /&gt;
&lt;br /&gt;
* new_workstation  - default memory is 4GB (max 47GB), default walltime is 8 hours (max one week), allows up to 4 jobs per user concurrently&lt;br /&gt;
* new_throughput - no interactive jobs - default memory is 4GB (max 36GB), default walltime is 4 hours (max 18 hours), allows up to 125 jobs per user concurrently &lt;br /&gt;
* new_hthroughput - no interactive jobs - default memory is 4gb (max 8GB), default walltime is 3 hours (max 6 hours), allows up to 300 jobs per user concurrently&lt;br /&gt;
* new_large - no interactive jobs -default memory is 32GB (max 120GB), default walltime is 24 hours (max 11 days), allows up to 3 jobs per user concurrently&lt;br /&gt;
&amp;lt;nowiki&amp;gt;*&amp;lt;/nowiki&amp;gt;You can list nodes with a specific property by running &amp;quot;pbsnodes :property&amp;quot; where property is the specific property you want to see&lt;br /&gt;
&lt;br /&gt;
===qsub===&lt;br /&gt;
&lt;br /&gt;
qsub is how you submit jobs into a Torque cluster.  A job is a shell script that is given as STDIN or as a file on the command line.  The -l (lower case L) option allows the user to specify some options for your job submission. While your jobs will not always be penalized for using more resources or fewer resources than you request, it is very important to request resources as accurately as possible so that torque knows how many resources each machine has available when new jobs are scheduled. If your job is using more resources than you request, another job may be scheduled on that same machine and could potentially run the machine out of resources and cause segfaults and eventually bring down the machine; likewise, if you request more resources than you need, it will slow down the execution of other users&#039; jobs because torque may think a machine is at capacity when it actually is not.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
To specify the queue that you would like to submit to, use the -q option,&lt;br /&gt;
&lt;br /&gt;
  qsub -q workstation&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Use these options with the -l (lower case L) option to request resources:&lt;br /&gt;
&lt;br /&gt;
* ncpus=4&lt;br /&gt;
* mem=32GB&lt;br /&gt;
* walltime=12:00:00&lt;br /&gt;
&lt;br /&gt;
You can find a full list of job submission arguments see here [http://docs.adaptivecomputing.com/torque/4-2-6/help.htm#topics/2-jobs/jobSubmission.htm Torque Job Submission Arguments].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
As an example, to run the perl script myscript.pl on 4 CPUs with 128GB of memory for 12 hours you could run the following,&lt;br /&gt;
&lt;br /&gt;
  qsub -q large -l ncpus=4,mem=128GB,walltime=12:00:00 myscript.pl&lt;br /&gt;
&lt;br /&gt;
Note that the large queue was used in the above example because 128GB is more memory than the max allowed in all of the other queues. By default, all of the other queues reserve approximately the maximum memory allowed for that queue, but you may set a lower reservation if you know you will not need the full amount.&lt;br /&gt;
&lt;br /&gt;
Once you have submitted your job for execution you will get something back in the form of,&lt;br /&gt;
&lt;br /&gt;
  &amp;lt;JOBID&amp;gt;.&amp;lt;PBSSERVER&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You can use that &amp;lt;JOBID&amp;gt; to delete or find your job later if there is a problem.&lt;br /&gt;
&lt;br /&gt;
When a job finishes, Torque/PBS deposits the standard output and standard error as&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;jobname&amp;gt;.o&amp;lt;number&amp;gt; &lt;br /&gt;
* &amp;lt;jobname&amp;gt;.e&amp;lt;number&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Where &amp;lt;jobname&amp;gt; is the name of the script you submitted (or STDIN if it came from qsub&#039;s standard in), and &amp;lt;number&amp;gt; is the leading number in the job id.&lt;br /&gt;
&lt;br /&gt;
====Interactive Jobs====&lt;br /&gt;
&lt;br /&gt;
Interactive jobs allow you to schedule interactive shell access on Torque-scheduled compute nodes. You can get an interactive session with the -I (upper case i) option,&lt;br /&gt;
&lt;br /&gt;
  qsub -I &lt;br /&gt;
&lt;br /&gt;
Please note that only the &amp;quot;workstation&amp;quot;, &amp;quot;shell&amp;quot;, and &amp;quot;default&amp;quot; queues allow interactive jobs. If you require larger resource allocations than the queue defaults, the -l (lower case L) flag still applies.&lt;br /&gt;
&lt;br /&gt;
====Array Jobs====&lt;br /&gt;
&lt;br /&gt;
Array jobs let you submit the same script multiple times, each with a different setting for the environment variable &amp;lt;code&amp;gt;PBS_ARRAYID&amp;lt;/code&amp;gt;:&lt;br /&gt;
&lt;br /&gt;
 qsub -q throughput -t 0-999 my_script.sh&lt;br /&gt;
&lt;br /&gt;
Torque will run 1000 instances of &amp;lt;code&amp;gt;my_script.sh&amp;lt;/code&amp;gt; with the environment variable &amp;lt;code&amp;gt;PBS_ARRAYID&amp;lt;/code&amp;gt; set to the range of values specified by the &amp;lt;code&amp;gt;-t&amp;lt;/code&amp;gt; argument. In this case &amp;lt;code&amp;gt;my_script.sh&amp;lt;/code&amp;gt; will be executed once with &amp;lt;code&amp;gt;PBS_ARRAYID=0&amp;lt;/code&amp;gt;, again with  &amp;lt;code&amp;gt;PBS_ARRAYID=1&amp;lt;/code&amp;gt;, etc.&lt;br /&gt;
&lt;br /&gt;
You can also specify comma separate values for &amp;lt;code&amp;gt;PBS_ARRAYID&amp;lt;/code&amp;gt;:&lt;br /&gt;
&lt;br /&gt;
 qsub -q throughput -t 0,3,9  my_script.sh&lt;br /&gt;
&lt;br /&gt;
===qstat===&lt;br /&gt;
&lt;br /&gt;
This will display if any jobs are in the queue for your Torque cluster.  It is normally run with out any arguments and if it returns nothing then there is nothing running in the Torque cluster.&lt;br /&gt;
&lt;br /&gt;
Here is an example of what qstat will look like,&lt;br /&gt;
&lt;br /&gt;
&amp;lt;blockquote&amp;gt;&amp;lt;pre&amp;gt;&lt;br /&gt;
$ qstat&lt;br /&gt;
Job id                    Name             User            Time Use S Queue&lt;br /&gt;
------------------------- ---------------- --------------- -------- - -----&lt;br /&gt;
135.cbcbtorque             STDIN            tgray26         00:00:00 R workstation&lt;br /&gt;
136.cbcbtorque             STDIN            tgray26         00:00:00 R default        &lt;br /&gt;
137.cbcbtorque             STDIN            tgray26         00:00:00 R default        &lt;br /&gt;
138.cbcbtorque             STDIN            tgray26                0 Q workstation&lt;br /&gt;
&amp;lt;/pre&amp;gt;&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For full information about the default settings and maximum resource limits for a queue, use &amp;lt;code&amp;gt;qstat -Q -f&amp;lt;/code&amp;gt;:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;blockquote&amp;gt;&amp;lt;pre&amp;gt;&lt;br /&gt;
$ qstat -Q -f throughput&lt;br /&gt;
Queue: throughput&lt;br /&gt;
    queue_type = Execution&lt;br /&gt;
    total_jobs = 0&lt;br /&gt;
    state_count = Transit:0 Queued:0 Held:0 Waiting:0 Running:0 Exiting:0 Comp&lt;br /&gt;
	lete:0&lt;br /&gt;
    resources_max.mem = 36gb&lt;br /&gt;
    resources_max.nodect = 1&lt;br /&gt;
    resources_max.walltime = 18:00:00&lt;br /&gt;
    resources_default.mem = 4gb&lt;br /&gt;
    resources_default.walltime = 04:00:00&lt;br /&gt;
    mtime = 1424395185&lt;br /&gt;
    disallowed_types = interactive&lt;br /&gt;
    resources_assigned.mem = 0b&lt;br /&gt;
    resources_assigned.ncpus = 0&lt;br /&gt;
    resources_assigned.nodect = 0&lt;br /&gt;
    max_user_run = 125&lt;br /&gt;
    enabled = True&lt;br /&gt;
    started = True&lt;br /&gt;
&amp;lt;/pre&amp;gt;&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===qdel===&lt;br /&gt;
&lt;br /&gt;
You can remove a running or stalled job with the qdel command.  It requires that you give it a &amp;lt;JOBID&amp;gt; that can be found by running qstat.&lt;br /&gt;
&lt;br /&gt;
===pbsnodes===&lt;br /&gt;
&lt;br /&gt;
To find out what resources and nodes are available in the Torque cluster you can run pbsnodes.  It will give you back a detailed list of the nodes and their current status.&lt;br /&gt;
&lt;br /&gt;
For example,&lt;br /&gt;
&lt;br /&gt;
&amp;lt;blockquote&amp;gt;&amp;lt;pre&amp;gt;&lt;br /&gt;
$ pbsnodes&lt;br /&gt;
redbud.umiacs.umd.edu&lt;br /&gt;
     state = free&lt;br /&gt;
     np = 32&lt;br /&gt;
     ntype = cluster&lt;br /&gt;
     status = rectime=1343744604,varattr=,jobs=,state=free,netload=384208495,gres=,loadave=0.02,ncpus=64,&lt;br /&gt;
              physmem=528633432kb,availmem=530365780kb,totmem=530730576kb,idletime=489899,nusers=0,nsessions=? 0,&lt;br /&gt;
              sessions=? 0,uname=Linux redbud.umiacs.umd.edu 2.6.18-308.11.1.el5 #1 SMP Fri Jun 15 15:41:53 EDT 2012 x86_64,opsys=linux&lt;br /&gt;
     gpus = 0&lt;br /&gt;
&lt;br /&gt;
beech.umiacs.umd.edu&lt;br /&gt;
     state = free&lt;br /&gt;
     np = 2&lt;br /&gt;
     ntype = cluster&lt;br /&gt;
     status = rectime=1343744577,varattr=,jobs=,state=free,netload=425438230,gres=,loadave=0.00,ncpus=2,&lt;br /&gt;
              physmem=7154944kb,availmem=8960412kb,totmem=9252088kb,idletime=49,nusers=0,nsessions=? 0,&lt;br /&gt;
              sessions=? 0,uname=Linux beech.umiacs.umd.edu 2.6.18-308.11.1.el5 #1 SMP Fri Jun 15 15:41:53 EDT 2012 x86_64,opsys=linux&lt;br /&gt;
     gpus = 0&lt;br /&gt;
&amp;lt;/pre&amp;gt;&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
===Host Monitoring===&lt;br /&gt;
http://ganglia.umiacs.umd.edu/ganglia/?c=cbcb_compute&amp;amp;m=load_one&amp;amp;r=hour&amp;amp;s=by%20name&amp;amp;hc=4&amp;amp;mc=2&lt;/div&gt;</summary>
		<author><name>Lmendelo</name></author>
	</entry>
	<entry>
		<id>https://wiki.umiacs.umd.edu/cbcb/index.php?title=Torque&amp;diff=9013</id>
		<title>Torque</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/cbcb/index.php?title=Torque&amp;diff=9013"/>
		<updated>2015-03-03T17:57:19Z</updated>

		<summary type="html">&lt;p&gt;Lmendelo: /* Getting Started */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Getting Started==&lt;br /&gt;
&lt;br /&gt;
Torque is a resource manager that interacts with another program called Maui which provides the scheduling for the cluster.   To get started you will need to ensure that your [https://wiki.umiacs.umd.edu/umiacs/index.php/SSH#SSH_Keys_.28and_Passwordless_SSH.29 SSH keys] are setup for password-less SSH.  In our Torque environments this is critical to delivering the error and output of your jobs back to where the job was submitted from. Please note that [https://wiki.umiacs.umd.edu/umiacs/index.php/Fairshare Fair Share] is enabled in this setup, with a historical scope of 12 hours.&lt;br /&gt;
&lt;br /&gt;
The hosts that you can submit from are any CBCB Workstation and the &amp;lt;tt&amp;gt;ibissub00.umiacs.umd.edu&amp;lt;/tt&amp;gt;, &amp;lt;tt&amp;gt;ibissub01.umiacs.umd.edu&amp;lt;/tt&amp;gt;, and &amp;lt;tt&amp;gt;heronsub00.umiacs.umd.edu&amp;lt;/tt&amp;gt; nodes.&lt;br /&gt;
&lt;br /&gt;
Now that you have that setup here are the queues that are available to users. Use &amp;lt;code&amp;gt;qstat -Q -f&amp;lt;/code&amp;gt; to see the resource limits for each queue.&lt;br /&gt;
&lt;br /&gt;
=== Red Hat 5 Queues ===&lt;br /&gt;
&lt;br /&gt;
* default- default memory is 3GB (max 4GB), default walltime is 1 hour (max 1 hour), allows up to 16 jobs per user concurrently&lt;br /&gt;
* shell - interactive jobs only - default memory is 2GB (max 4GB), default walltime is 12 hours (max 2 wks), allows up to 4 jobs per user concurrently - restricted to nodes with &#039;&#039;&#039;shell&#039;&#039;&#039;* property&lt;br /&gt;
* workstation - default memory is 4GB (max 47GB), default walltime is 8 hours (max one week), allows up to 4 jobs per user concurrently&lt;br /&gt;
* throughput  - no interactive jobs - default memory is 4GB (max 36GB), default walltime is 4 hours (max 18 hours), allows up to 125 jobs per user concurrently - restricted to nodes with &#039;&#039;&#039;ibis&#039;&#039;&#039;* property&lt;br /&gt;
* high_throughput - no interactive jobs - default memory is 4gb (max 8GB), default walltime is 3 hours (max 6 hours), allows up to 300 jobs per user concurrently - restricted to nodes with &#039;&#039;&#039;ibis&#039;&#039;&#039;* property&lt;br /&gt;
* long - no interactive jobs - default memory is 12gb (max 12gb), default walltime is 8 hours (max 1 week), allows up to 16 jobs per user concurrently&lt;br /&gt;
* large - no interactive jobs -default memory is 32GB (max 120GB), default walltime is 24 hours (max 11 days), allows up to 3 jobs per user concurrently&lt;br /&gt;
* xlarge - default memory is 100GB (max is unlimited), default walltime is 1 week (max 3 weeks), allows 1 job per user at a time&lt;br /&gt;
** The xlarge queue is restricted to members of the group cbcbtorque. If you need to run large jobs please send mail to staff@umiacs.umd.edu&lt;br /&gt;
&lt;br /&gt;
=== Red Hat 7 Queues ===&lt;br /&gt;
&lt;br /&gt;
These queues submit jobs to the RHEL 7 heron* nodes.&lt;br /&gt;
&lt;br /&gt;
* new_workstation  - default memory is 4GB (max 47GB), default walltime is 8 hours (max one week), allows up to 4 jobs per user concurrently&lt;br /&gt;
* new_throughput - no interactive jobs - default memory is 4GB (max 36GB), default walltime is 4 hours (max 18 hours), allows up to 125 jobs per user concurrently &lt;br /&gt;
* new_hthroughput - no interactive jobs - default memory is 4gb (max 8GB), default walltime is 3 hours (max 6 hours), allows up to 300 jobs per user concurrently&lt;br /&gt;
* new_large - no interactive jobs -default memory is 32GB (max 120GB), default walltime is 24 hours (max 11 days), allows up to 3 jobs per user concurrently&lt;br /&gt;
&amp;lt;nowiki&amp;gt;*&amp;lt;/nowiki&amp;gt;You can list nodes with a specific property by running &amp;quot;pbsnodes :property&amp;quot; where property is the specific property you want to see&lt;br /&gt;
&lt;br /&gt;
===qsub===&lt;br /&gt;
&lt;br /&gt;
qsub is how you submit jobs into a Torque cluster.  A job is a shell script that is given as STDIN or as a file on the command line.  The -l (lower case L) option allows the user to specify some options for your job submission. While your jobs will not always be penalized for using more resources or fewer resources than you request, it is very important to request resources as accurately as possible so that torque knows how many resources each machine has available when new jobs are scheduled. If your job is using more resources than you request, another job may be scheduled on that same machine and could potentially run the machine out of resources and cause segfaults and eventually bring down the machine; likewise, if you request more resources than you need, it will slow down the execution of other users&#039; jobs because torque may think a machine is at capacity when it actually is not.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
To specify the queue that you would like to submit to, use the -q option,&lt;br /&gt;
&lt;br /&gt;
  qsub -q workstation&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Use these options with the -l (lower case L) option to request resources:&lt;br /&gt;
&lt;br /&gt;
* ncpus=4&lt;br /&gt;
* mem=32GB&lt;br /&gt;
* walltime=12:00:00&lt;br /&gt;
&lt;br /&gt;
You can find a full list of job submission arguments see here [http://docs.adaptivecomputing.com/torque/4-2-6/help.htm#topics/2-jobs/jobSubmission.htm Torque Job Submission Arguments].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
As an example, to run the perl script myscript.pl on 4 CPUs with 128GB of memory for 12 hours you could run the following,&lt;br /&gt;
&lt;br /&gt;
  qsub -q large -l ncpus=4,mem=128GB,walltime=12:00:00 myscript.pl&lt;br /&gt;
&lt;br /&gt;
Note that the large queue was used in the above example because 128GB is more memory than the max allowed in all of the other queues. By default, all of the other queues reserve approximately the maximum memory allowed for that queue, but you may set a lower reservation if you know you will not need the full amount.&lt;br /&gt;
&lt;br /&gt;
Once you have submitted your job for execution you will get something back in the form of,&lt;br /&gt;
&lt;br /&gt;
  &amp;lt;JOBID&amp;gt;.&amp;lt;PBSSERVER&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You can use that &amp;lt;JOBID&amp;gt; to delete or find your job later if there is a problem.&lt;br /&gt;
&lt;br /&gt;
When a job finishes, Torque/PBS deposits the standard output and standard error as&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;jobname&amp;gt;.o&amp;lt;number&amp;gt; &lt;br /&gt;
* &amp;lt;jobname&amp;gt;.e&amp;lt;number&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Where &amp;lt;jobname&amp;gt; is the name of the script you submitted (or STDIN if it came from qsub&#039;s standard in), and &amp;lt;number&amp;gt; is the leading number in the job id.&lt;br /&gt;
&lt;br /&gt;
====Interactive Jobs====&lt;br /&gt;
&lt;br /&gt;
Interactive jobs allow you to schedule interactive shell access on Torque-scheduled compute nodes. You can get an interactive session with the -I (upper case i) option,&lt;br /&gt;
&lt;br /&gt;
  qsub -I&lt;br /&gt;
&lt;br /&gt;
Please note that only the &amp;quot;workstation&amp;quot;, &amp;quot;shell&amp;quot;, and &amp;quot;default&amp;quot; queues allow interactive jobs. If you require larger resource allocations than the queue defaults, the -l (lower case L) flag still applies.&lt;br /&gt;
&lt;br /&gt;
===qstat===&lt;br /&gt;
&lt;br /&gt;
This will display if any jobs are in the queue for your Torque cluster.  It is normally run with out any arguments and if it returns nothing then there is nothing running in the Torque cluster.&lt;br /&gt;
&lt;br /&gt;
Here is an example of what qstat will look like,&lt;br /&gt;
&lt;br /&gt;
&amp;lt;blockquote&amp;gt;&amp;lt;pre&amp;gt;&lt;br /&gt;
$ qstat&lt;br /&gt;
Job id                    Name             User            Time Use S Queue&lt;br /&gt;
------------------------- ---------------- --------------- -------- - -----&lt;br /&gt;
135.cbcbtorque             STDIN            tgray26         00:00:00 R workstation&lt;br /&gt;
136.cbcbtorque             STDIN            tgray26         00:00:00 R default        &lt;br /&gt;
137.cbcbtorque             STDIN            tgray26         00:00:00 R default        &lt;br /&gt;
138.cbcbtorque             STDIN            tgray26                0 Q workstation&lt;br /&gt;
&amp;lt;/pre&amp;gt;&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For full information about the default settings and maximum resource limits for a queue, use &amp;lt;code&amp;gt;qstat -Q -f&amp;lt;/code&amp;gt;:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;blockquote&amp;gt;&amp;lt;pre&amp;gt;&lt;br /&gt;
$ qstat -Q -f throughput&lt;br /&gt;
Queue: throughput&lt;br /&gt;
    queue_type = Execution&lt;br /&gt;
    total_jobs = 0&lt;br /&gt;
    state_count = Transit:0 Queued:0 Held:0 Waiting:0 Running:0 Exiting:0 Comp&lt;br /&gt;
	lete:0&lt;br /&gt;
    resources_max.mem = 36gb&lt;br /&gt;
    resources_max.nodect = 1&lt;br /&gt;
    resources_max.walltime = 18:00:00&lt;br /&gt;
    resources_default.mem = 4gb&lt;br /&gt;
    resources_default.walltime = 04:00:00&lt;br /&gt;
    mtime = 1424395185&lt;br /&gt;
    disallowed_types = interactive&lt;br /&gt;
    resources_assigned.mem = 0b&lt;br /&gt;
    resources_assigned.ncpus = 0&lt;br /&gt;
    resources_assigned.nodect = 0&lt;br /&gt;
    max_user_run = 125&lt;br /&gt;
    enabled = True&lt;br /&gt;
    started = True&lt;br /&gt;
&amp;lt;/pre&amp;gt;&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===qdel===&lt;br /&gt;
&lt;br /&gt;
You can remove a running or stalled job with the qdel command.  It requires that you give it a &amp;lt;JOBID&amp;gt; that can be found by running qstat.&lt;br /&gt;
&lt;br /&gt;
===pbsnodes===&lt;br /&gt;
&lt;br /&gt;
To find out what resources and nodes are available in the Torque cluster you can run pbsnodes.  It will give you back a detailed list of the nodes and their current status.&lt;br /&gt;
&lt;br /&gt;
For example,&lt;br /&gt;
&lt;br /&gt;
&amp;lt;blockquote&amp;gt;&amp;lt;pre&amp;gt;&lt;br /&gt;
$ pbsnodes&lt;br /&gt;
redbud.umiacs.umd.edu&lt;br /&gt;
     state = free&lt;br /&gt;
     np = 32&lt;br /&gt;
     ntype = cluster&lt;br /&gt;
     status = rectime=1343744604,varattr=,jobs=,state=free,netload=384208495,gres=,loadave=0.02,ncpus=64,&lt;br /&gt;
              physmem=528633432kb,availmem=530365780kb,totmem=530730576kb,idletime=489899,nusers=0,nsessions=? 0,&lt;br /&gt;
              sessions=? 0,uname=Linux redbud.umiacs.umd.edu 2.6.18-308.11.1.el5 #1 SMP Fri Jun 15 15:41:53 EDT 2012 x86_64,opsys=linux&lt;br /&gt;
     gpus = 0&lt;br /&gt;
&lt;br /&gt;
beech.umiacs.umd.edu&lt;br /&gt;
     state = free&lt;br /&gt;
     np = 2&lt;br /&gt;
     ntype = cluster&lt;br /&gt;
     status = rectime=1343744577,varattr=,jobs=,state=free,netload=425438230,gres=,loadave=0.00,ncpus=2,&lt;br /&gt;
              physmem=7154944kb,availmem=8960412kb,totmem=9252088kb,idletime=49,nusers=0,nsessions=? 0,&lt;br /&gt;
              sessions=? 0,uname=Linux beech.umiacs.umd.edu 2.6.18-308.11.1.el5 #1 SMP Fri Jun 15 15:41:53 EDT 2012 x86_64,opsys=linux&lt;br /&gt;
     gpus = 0&lt;br /&gt;
&amp;lt;/pre&amp;gt;&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
===Host Monitoring===&lt;br /&gt;
http://ganglia.umiacs.umd.edu/ganglia/?c=cbcb_compute&amp;amp;m=load_one&amp;amp;r=hour&amp;amp;s=by%20name&amp;amp;hc=4&amp;amp;mc=2&lt;/div&gt;</summary>
		<author><name>Lmendelo</name></author>
	</entry>
	<entry>
		<id>https://wiki.umiacs.umd.edu/cbcb/index.php?title=Torque&amp;diff=9012</id>
		<title>Torque</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/cbcb/index.php?title=Torque&amp;diff=9012"/>
		<updated>2015-03-03T17:56:18Z</updated>

		<summary type="html">&lt;p&gt;Lmendelo: /* Getting Started */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Getting Started==&lt;br /&gt;
&lt;br /&gt;
Torque is a resource manager that interacts with another program called Maui which provides the scheduling for the cluster.   To get started you will need to ensure that your [https://wiki.umiacs.umd.edu/umiacs/index.php/SSH#SSH_Keys_.28and_Passwordless_SSH.29 SSH keys] are setup for password-less SSH.  In our Torque environments this is critical to delivering the error and output of your jobs back to where the job was submitted from. Please note that [https://wiki.umiacs.umd.edu/umiacs/index.php/Fairshare Fair Share] is enabled in this setup, with a historical scope of 12 hours.&lt;br /&gt;
&lt;br /&gt;
The hosts that you can submit from are any CBCB Workstation and the &amp;lt;tt&amp;gt;ibissub00.umiacs.umd.edu&amp;lt;/tt&amp;gt;, &amp;lt;tt&amp;gt;ibissub01.umiacs.umd.edu&amp;lt;/tt&amp;gt;, and &amp;lt;tt&amp;gt;heronsub00.umiacs.umd.edu&amp;lt;/tt&amp;gt; nodes.&lt;br /&gt;
&lt;br /&gt;
Now that you have that setup here are the queues that are available to users:&lt;br /&gt;
&lt;br /&gt;
=== Red Hat 5 Queues ===&lt;br /&gt;
&lt;br /&gt;
* default- default memory is 3GB (max 4GB), default walltime is 1 hour (max 1 hour), allows up to 16 jobs per user concurrently&lt;br /&gt;
* shell - interactive jobs only - default memory is 2GB (max 4GB), default walltime is 12 hours (max 2 wks), allows up to 4 jobs per user concurrently - restricted to nodes with &#039;&#039;&#039;shell&#039;&#039;&#039;* property&lt;br /&gt;
* workstation - default memory is 4GB (max 47GB), default walltime is 8 hours (max one week), allows up to 4 jobs per user concurrently&lt;br /&gt;
* throughput  - no interactive jobs - default memory is 4GB (max 36GB), default walltime is 4 hours (max 18 hours), allows up to 125 jobs per user concurrently - restricted to nodes with &#039;&#039;&#039;ibis&#039;&#039;&#039;* property&lt;br /&gt;
* high_throughput - no interactive jobs - default memory is 4gb (max 8GB), default walltime is 3 hours (max 6 hours), allows up to 300 jobs per user concurrently - restricted to nodes with &#039;&#039;&#039;ibis&#039;&#039;&#039;* property&lt;br /&gt;
* long - no interactive jobs - default memory is 12gb (max 12gb), default walltime is 8 hours (max 1 week), allows up to 16 jobs per user concurrently&lt;br /&gt;
* large - no interactive jobs -default memory is 32GB (max 120GB), default walltime is 24 hours (max 11 days), allows up to 3 jobs per user concurrently&lt;br /&gt;
* xlarge - default memory is 100GB (max is unlimited), default walltime is 1 week (max 3 weeks), allows 1 job per user at a time&lt;br /&gt;
** The xlarge queue is restricted to members of the group cbcbtorque. If you need to run large jobs please send mail to staff@umiacs.umd.edu&lt;br /&gt;
&lt;br /&gt;
=== Red Hat 7 Queues ===&lt;br /&gt;
&lt;br /&gt;
These queues submit jobs to the RHEL 7 heron* nodes.&lt;br /&gt;
&lt;br /&gt;
* new_workstation  - default memory is 4GB (max 47GB), default walltime is 8 hours (max one week), allows up to 4 jobs per user concurrently&lt;br /&gt;
* new_throughput - no interactive jobs - default memory is 4GB (max 36GB), default walltime is 4 hours (max 18 hours), allows up to 125 jobs per user concurrently &lt;br /&gt;
* new_hthroughput - no interactive jobs - default memory is 4gb (max 8GB), default walltime is 3 hours (max 6 hours), allows up to 300 jobs per user concurrently&lt;br /&gt;
* new_large - no interactive jobs -default memory is 32GB (max 120GB), default walltime is 24 hours (max 11 days), allows up to 3 jobs per user concurrently&lt;br /&gt;
&amp;lt;nowiki&amp;gt;*&amp;lt;/nowiki&amp;gt;You can list nodes with a specific property by running &amp;quot;pbsnodes :property&amp;quot; where property is the specific property you want to see&lt;br /&gt;
&lt;br /&gt;
===qsub===&lt;br /&gt;
&lt;br /&gt;
qsub is how you submit jobs into a Torque cluster.  A job is a shell script that is given as STDIN or as a file on the command line.  The -l (lower case L) option allows the user to specify some options for your job submission. While your jobs will not always be penalized for using more resources or fewer resources than you request, it is very important to request resources as accurately as possible so that torque knows how many resources each machine has available when new jobs are scheduled. If your job is using more resources than you request, another job may be scheduled on that same machine and could potentially run the machine out of resources and cause segfaults and eventually bring down the machine; likewise, if you request more resources than you need, it will slow down the execution of other users&#039; jobs because torque may think a machine is at capacity when it actually is not.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
To specify the queue that you would like to submit to, use the -q option,&lt;br /&gt;
&lt;br /&gt;
  qsub -q workstation&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Use these options with the -l (lower case L) option to request resources:&lt;br /&gt;
&lt;br /&gt;
* ncpus=4&lt;br /&gt;
* mem=32GB&lt;br /&gt;
* walltime=12:00:00&lt;br /&gt;
&lt;br /&gt;
You can find a full list of job submission arguments see here [http://docs.adaptivecomputing.com/torque/4-2-6/help.htm#topics/2-jobs/jobSubmission.htm Torque Job Submission Arguments].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
As an example, to run the perl script myscript.pl on 4 CPUs with 128GB of memory for 12 hours you could run the following,&lt;br /&gt;
&lt;br /&gt;
  qsub -q large -l ncpus=4,mem=128GB,walltime=12:00:00 myscript.pl&lt;br /&gt;
&lt;br /&gt;
Note that the large queue was used in the above example because 128GB is more memory than the max allowed in all of the other queues. By default, all of the other queues reserve approximately the maximum memory allowed for that queue, but you may set a lower reservation if you know you will not need the full amount.&lt;br /&gt;
&lt;br /&gt;
Once you have submitted your job for execution you will get something back in the form of,&lt;br /&gt;
&lt;br /&gt;
  &amp;lt;JOBID&amp;gt;.&amp;lt;PBSSERVER&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You can use that &amp;lt;JOBID&amp;gt; to delete or find your job later if there is a problem.&lt;br /&gt;
&lt;br /&gt;
When a job finishes, Torque/PBS deposits the standard output and standard error as&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;jobname&amp;gt;.o&amp;lt;number&amp;gt; &lt;br /&gt;
* &amp;lt;jobname&amp;gt;.e&amp;lt;number&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Where &amp;lt;jobname&amp;gt; is the name of the script you submitted (or STDIN if it came from qsub&#039;s standard in), and &amp;lt;number&amp;gt; is the leading number in the job id.&lt;br /&gt;
&lt;br /&gt;
====Interactive Jobs====&lt;br /&gt;
&lt;br /&gt;
Interactive jobs allow you to schedule interactive shell access on Torque-scheduled compute nodes. You can get an interactive session with the -I (upper case i) option,&lt;br /&gt;
&lt;br /&gt;
  qsub -I&lt;br /&gt;
&lt;br /&gt;
Please note that only the &amp;quot;workstation&amp;quot;, &amp;quot;shell&amp;quot;, and &amp;quot;default&amp;quot; queues allow interactive jobs. If you require larger resource allocations than the queue defaults, the -l (lower case L) flag still applies.&lt;br /&gt;
&lt;br /&gt;
===qstat===&lt;br /&gt;
&lt;br /&gt;
This will display if any jobs are in the queue for your Torque cluster.  It is normally run with out any arguments and if it returns nothing then there is nothing running in the Torque cluster.&lt;br /&gt;
&lt;br /&gt;
Here is an example of what qstat will look like,&lt;br /&gt;
&lt;br /&gt;
&amp;lt;blockquote&amp;gt;&amp;lt;pre&amp;gt;&lt;br /&gt;
$ qstat&lt;br /&gt;
Job id                    Name             User            Time Use S Queue&lt;br /&gt;
------------------------- ---------------- --------------- -------- - -----&lt;br /&gt;
135.cbcbtorque             STDIN            tgray26         00:00:00 R workstation&lt;br /&gt;
136.cbcbtorque             STDIN            tgray26         00:00:00 R default        &lt;br /&gt;
137.cbcbtorque             STDIN            tgray26         00:00:00 R default        &lt;br /&gt;
138.cbcbtorque             STDIN            tgray26                0 Q workstation&lt;br /&gt;
&amp;lt;/pre&amp;gt;&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For full information about the default settings and maximum resource limits for a queue, use &amp;lt;code&amp;gt;qstat -Q -f&amp;lt;/code&amp;gt;:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;blockquote&amp;gt;&amp;lt;pre&amp;gt;&lt;br /&gt;
$ qstat -Q -f throughput&lt;br /&gt;
Queue: throughput&lt;br /&gt;
    queue_type = Execution&lt;br /&gt;
    total_jobs = 0&lt;br /&gt;
    state_count = Transit:0 Queued:0 Held:0 Waiting:0 Running:0 Exiting:0 Comp&lt;br /&gt;
	lete:0&lt;br /&gt;
    resources_max.mem = 36gb&lt;br /&gt;
    resources_max.nodect = 1&lt;br /&gt;
    resources_max.walltime = 18:00:00&lt;br /&gt;
    resources_default.mem = 4gb&lt;br /&gt;
    resources_default.walltime = 04:00:00&lt;br /&gt;
    mtime = 1424395185&lt;br /&gt;
    disallowed_types = interactive&lt;br /&gt;
    resources_assigned.mem = 0b&lt;br /&gt;
    resources_assigned.ncpus = 0&lt;br /&gt;
    resources_assigned.nodect = 0&lt;br /&gt;
    max_user_run = 125&lt;br /&gt;
    enabled = True&lt;br /&gt;
    started = True&lt;br /&gt;
&amp;lt;/pre&amp;gt;&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===qdel===&lt;br /&gt;
&lt;br /&gt;
You can remove a running or stalled job with the qdel command.  It requires that you give it a &amp;lt;JOBID&amp;gt; that can be found by running qstat.&lt;br /&gt;
&lt;br /&gt;
===pbsnodes===&lt;br /&gt;
&lt;br /&gt;
To find out what resources and nodes are available in the Torque cluster you can run pbsnodes.  It will give you back a detailed list of the nodes and their current status.&lt;br /&gt;
&lt;br /&gt;
For example,&lt;br /&gt;
&lt;br /&gt;
&amp;lt;blockquote&amp;gt;&amp;lt;pre&amp;gt;&lt;br /&gt;
$ pbsnodes&lt;br /&gt;
redbud.umiacs.umd.edu&lt;br /&gt;
     state = free&lt;br /&gt;
     np = 32&lt;br /&gt;
     ntype = cluster&lt;br /&gt;
     status = rectime=1343744604,varattr=,jobs=,state=free,netload=384208495,gres=,loadave=0.02,ncpus=64,&lt;br /&gt;
              physmem=528633432kb,availmem=530365780kb,totmem=530730576kb,idletime=489899,nusers=0,nsessions=? 0,&lt;br /&gt;
              sessions=? 0,uname=Linux redbud.umiacs.umd.edu 2.6.18-308.11.1.el5 #1 SMP Fri Jun 15 15:41:53 EDT 2012 x86_64,opsys=linux&lt;br /&gt;
     gpus = 0&lt;br /&gt;
&lt;br /&gt;
beech.umiacs.umd.edu&lt;br /&gt;
     state = free&lt;br /&gt;
     np = 2&lt;br /&gt;
     ntype = cluster&lt;br /&gt;
     status = rectime=1343744577,varattr=,jobs=,state=free,netload=425438230,gres=,loadave=0.00,ncpus=2,&lt;br /&gt;
              physmem=7154944kb,availmem=8960412kb,totmem=9252088kb,idletime=49,nusers=0,nsessions=? 0,&lt;br /&gt;
              sessions=? 0,uname=Linux beech.umiacs.umd.edu 2.6.18-308.11.1.el5 #1 SMP Fri Jun 15 15:41:53 EDT 2012 x86_64,opsys=linux&lt;br /&gt;
     gpus = 0&lt;br /&gt;
&amp;lt;/pre&amp;gt;&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
===Host Monitoring===&lt;br /&gt;
http://ganglia.umiacs.umd.edu/ganglia/?c=cbcb_compute&amp;amp;m=load_one&amp;amp;r=hour&amp;amp;s=by%20name&amp;amp;hc=4&amp;amp;mc=2&lt;/div&gt;</summary>
		<author><name>Lmendelo</name></author>
	</entry>
	<entry>
		<id>https://wiki.umiacs.umd.edu/cbcb/index.php?title=Torque&amp;diff=9011</id>
		<title>Torque</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/cbcb/index.php?title=Torque&amp;diff=9011"/>
		<updated>2015-03-03T17:51:04Z</updated>

		<summary type="html">&lt;p&gt;Lmendelo: /* qstat */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Getting Started==&lt;br /&gt;
&lt;br /&gt;
Torque is a resource manager that interacts with another program called Maui which provides the scheduling for the cluster.   To get started you will need to ensure that your [https://wiki.umiacs.umd.edu/umiacs/index.php/SSH#SSH_Keys_.28and_Passwordless_SSH.29 SSH keys] are setup for password-less SSH.  In our Torque environments this is critical to delivering the error and output of your jobs back to where the job was submitted from. Please note that [https://wiki.umiacs.umd.edu/umiacs/index.php/Fairshare Fair Share] is enabled in this setup, with a historical scope of 12 hours.&lt;br /&gt;
&lt;br /&gt;
The hosts that you can submit from are any CBCB Workstation and the &amp;lt;tt&amp;gt;ibissub00.umiacs.umd.edu&amp;lt;/tt&amp;gt; and &amp;lt;tt&amp;gt;ibissub01.umiacs.umd.edu&amp;lt;/tt&amp;gt; nodes.&lt;br /&gt;
&lt;br /&gt;
Now that you have that setup here are the queues that are available to users,&lt;br /&gt;
&lt;br /&gt;
* default- default memory is 3GB (max 4GB), default walltime is 1 hour (max 1 hour), allows up to 16 jobs per user concurrently&lt;br /&gt;
* shell - interactive jobs only - default memory is 2GB (max 4GB), default walltime is 12 hours (max 2 wks), allows up to 4 jobs per user concurrently - restricted to nodes with &#039;&#039;&#039;shell&#039;&#039;&#039;* property&lt;br /&gt;
* workstation - default memory is 4GB (max 47GB), default walltime is 8 hours (max one week), allows up to 4 jobs per user concurrently&lt;br /&gt;
* throughput - no interactive jobs - default memory is 4GB (max 36GB), default walltime is 4 hours (max 18 hours), allows up to 125 jobs per user concurrently - restricted to nodes with &#039;&#039;&#039;ibis&#039;&#039;&#039;* property&lt;br /&gt;
* high_throughput - no interactive jobs - default memory is 4gb (max 8GB), default walltime is 3 hours (max 6 hours), allows up to 300 jobs per user concurrently - restricted to nodes with &#039;&#039;&#039;ibis&#039;&#039;&#039;* property&lt;br /&gt;
* long - no interactive jobs - default memory is 12gb (max 12gb), default walltime is 8 hours (max 1 week), allows up to 16 jobs per user concurrently&lt;br /&gt;
* large - no interactive jobs -default memory is 32GB (max 120GB), default walltime is 24 hours (max 11 days), allows up to 3 jobs per user concurrently&lt;br /&gt;
* xlarge - default memory is 100GB (max is unlimited), default walltime is 1 week (max 3 weeks), allows 1 job per user at a time&lt;br /&gt;
** The xlarge queue is restricted to members of the group cbcbtorque. If you need to run large jobs please send mail to staff@umiacs.umd.edu&lt;br /&gt;
&lt;br /&gt;
&amp;lt;nowiki&amp;gt;*&amp;lt;/nowiki&amp;gt;You can list nodes with a specific property by running &amp;quot;pbsnodes :property&amp;quot; where property is the specific property you want to see&lt;br /&gt;
===qsub===&lt;br /&gt;
&lt;br /&gt;
qsub is how you submit jobs into a Torque cluster.  A job is a shell script that is given as STDIN or as a file on the command line.  The -l (lower case L) option allows the user to specify some options for your job submission. While your jobs will not always be penalized for using more resources or fewer resources than you request, it is very important to request resources as accurately as possible so that torque knows how many resources each machine has available when new jobs are scheduled. If your job is using more resources than you request, another job may be scheduled on that same machine and could potentially run the machine out of resources and cause segfaults and eventually bring down the machine; likewise, if you request more resources than you need, it will slow down the execution of other users&#039; jobs because torque may think a machine is at capacity when it actually is not.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
To specify the queue that you would like to submit to, use the -q option,&lt;br /&gt;
&lt;br /&gt;
  qsub -q workstation&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Use these options with the -l (lower case L) option to request resources:&lt;br /&gt;
&lt;br /&gt;
* ncpus=4&lt;br /&gt;
* mem=32GB&lt;br /&gt;
* walltime=12:00:00&lt;br /&gt;
&lt;br /&gt;
You can find a full list of job submission arguments see here [http://docs.adaptivecomputing.com/torque/4-2-6/help.htm#topics/2-jobs/jobSubmission.htm Torque Job Submission Arguments].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
As an example, to run the perl script myscript.pl on 4 CPUs with 128GB of memory for 12 hours you could run the following,&lt;br /&gt;
&lt;br /&gt;
  qsub -q large -l ncpus=4,mem=128GB,walltime=12:00:00 myscript.pl&lt;br /&gt;
&lt;br /&gt;
Note that the large queue was used in the above example because 128GB is more memory than the max allowed in all of the other queues. By default, all of the other queues reserve approximately the maximum memory allowed for that queue, but you may set a lower reservation if you know you will not need the full amount.&lt;br /&gt;
&lt;br /&gt;
Once you have submitted your job for execution you will get something back in the form of,&lt;br /&gt;
&lt;br /&gt;
  &amp;lt;JOBID&amp;gt;.&amp;lt;PBSSERVER&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You can use that &amp;lt;JOBID&amp;gt; to delete or find your job later if there is a problem.&lt;br /&gt;
&lt;br /&gt;
When a job finishes, Torque/PBS deposits the standard output and standard error as&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;jobname&amp;gt;.o&amp;lt;number&amp;gt; &lt;br /&gt;
* &amp;lt;jobname&amp;gt;.e&amp;lt;number&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Where &amp;lt;jobname&amp;gt; is the name of the script you submitted (or STDIN if it came from qsub&#039;s standard in), and &amp;lt;number&amp;gt; is the leading number in the job id.&lt;br /&gt;
&lt;br /&gt;
====Interactive Jobs====&lt;br /&gt;
&lt;br /&gt;
Interactive jobs allow you to schedule interactive shell access on Torque-scheduled compute nodes. You can get an interactive session with the -I (upper case i) option,&lt;br /&gt;
&lt;br /&gt;
  qsub -I&lt;br /&gt;
&lt;br /&gt;
Please note that only the &amp;quot;workstation&amp;quot;, &amp;quot;shell&amp;quot;, and &amp;quot;default&amp;quot; queues allow interactive jobs. If you require larger resource allocations than the queue defaults, the -l (lower case L) flag still applies.&lt;br /&gt;
&lt;br /&gt;
===qstat===&lt;br /&gt;
&lt;br /&gt;
This will display if any jobs are in the queue for your Torque cluster.  It is normally run with out any arguments and if it returns nothing then there is nothing running in the Torque cluster.&lt;br /&gt;
&lt;br /&gt;
Here is an example of what qstat will look like,&lt;br /&gt;
&lt;br /&gt;
&amp;lt;blockquote&amp;gt;&amp;lt;pre&amp;gt;&lt;br /&gt;
$ qstat&lt;br /&gt;
Job id                    Name             User            Time Use S Queue&lt;br /&gt;
------------------------- ---------------- --------------- -------- - -----&lt;br /&gt;
135.cbcbtorque             STDIN            tgray26         00:00:00 R workstation&lt;br /&gt;
136.cbcbtorque             STDIN            tgray26         00:00:00 R default        &lt;br /&gt;
137.cbcbtorque             STDIN            tgray26         00:00:00 R default        &lt;br /&gt;
138.cbcbtorque             STDIN            tgray26                0 Q workstation&lt;br /&gt;
&amp;lt;/pre&amp;gt;&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For full information about the default settings and maximum resource limits for a queue, use &amp;lt;code&amp;gt;qstat -Q -f&amp;lt;/code&amp;gt;:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;blockquote&amp;gt;&amp;lt;pre&amp;gt;&lt;br /&gt;
$ qstat -Q -f throughput&lt;br /&gt;
Queue: throughput&lt;br /&gt;
    queue_type = Execution&lt;br /&gt;
    total_jobs = 0&lt;br /&gt;
    state_count = Transit:0 Queued:0 Held:0 Waiting:0 Running:0 Exiting:0 Comp&lt;br /&gt;
	lete:0&lt;br /&gt;
    resources_max.mem = 36gb&lt;br /&gt;
    resources_max.nodect = 1&lt;br /&gt;
    resources_max.walltime = 18:00:00&lt;br /&gt;
    resources_default.mem = 4gb&lt;br /&gt;
    resources_default.walltime = 04:00:00&lt;br /&gt;
    mtime = 1424395185&lt;br /&gt;
    disallowed_types = interactive&lt;br /&gt;
    resources_assigned.mem = 0b&lt;br /&gt;
    resources_assigned.ncpus = 0&lt;br /&gt;
    resources_assigned.nodect = 0&lt;br /&gt;
    max_user_run = 125&lt;br /&gt;
    enabled = True&lt;br /&gt;
    started = True&lt;br /&gt;
&amp;lt;/pre&amp;gt;&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===qdel===&lt;br /&gt;
&lt;br /&gt;
You can remove a running or stalled job with the qdel command.  It requires that you give it a &amp;lt;JOBID&amp;gt; that can be found by running qstat.&lt;br /&gt;
&lt;br /&gt;
===pbsnodes===&lt;br /&gt;
&lt;br /&gt;
To find out what resources and nodes are available in the Torque cluster you can run pbsnodes.  It will give you back a detailed list of the nodes and their current status.&lt;br /&gt;
&lt;br /&gt;
For example,&lt;br /&gt;
&lt;br /&gt;
&amp;lt;blockquote&amp;gt;&amp;lt;pre&amp;gt;&lt;br /&gt;
$ pbsnodes&lt;br /&gt;
redbud.umiacs.umd.edu&lt;br /&gt;
     state = free&lt;br /&gt;
     np = 32&lt;br /&gt;
     ntype = cluster&lt;br /&gt;
     status = rectime=1343744604,varattr=,jobs=,state=free,netload=384208495,gres=,loadave=0.02,ncpus=64,&lt;br /&gt;
              physmem=528633432kb,availmem=530365780kb,totmem=530730576kb,idletime=489899,nusers=0,nsessions=? 0,&lt;br /&gt;
              sessions=? 0,uname=Linux redbud.umiacs.umd.edu 2.6.18-308.11.1.el5 #1 SMP Fri Jun 15 15:41:53 EDT 2012 x86_64,opsys=linux&lt;br /&gt;
     gpus = 0&lt;br /&gt;
&lt;br /&gt;
beech.umiacs.umd.edu&lt;br /&gt;
     state = free&lt;br /&gt;
     np = 2&lt;br /&gt;
     ntype = cluster&lt;br /&gt;
     status = rectime=1343744577,varattr=,jobs=,state=free,netload=425438230,gres=,loadave=0.00,ncpus=2,&lt;br /&gt;
              physmem=7154944kb,availmem=8960412kb,totmem=9252088kb,idletime=49,nusers=0,nsessions=? 0,&lt;br /&gt;
              sessions=? 0,uname=Linux beech.umiacs.umd.edu 2.6.18-308.11.1.el5 #1 SMP Fri Jun 15 15:41:53 EDT 2012 x86_64,opsys=linux&lt;br /&gt;
     gpus = 0&lt;br /&gt;
&amp;lt;/pre&amp;gt;&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
===Host Monitoring===&lt;br /&gt;
http://ganglia.umiacs.umd.edu/ganglia/?c=cbcb_compute&amp;amp;m=load_one&amp;amp;r=hour&amp;amp;s=by%20name&amp;amp;hc=4&amp;amp;mc=2&lt;/div&gt;</summary>
		<author><name>Lmendelo</name></author>
	</entry>
	<entry>
		<id>https://wiki.umiacs.umd.edu/cbcb/index.php?title=CBCB_Software_Modules&amp;diff=9007</id>
		<title>CBCB Software Modules</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/cbcb/index.php?title=CBCB_Software_Modules&amp;diff=9007"/>
		<updated>2015-03-03T14:23:42Z</updated>

		<summary type="html">&lt;p&gt;Lmendelo: /* Personal Modules */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Starting in the Spring of 2015, communal CBCB Bioinformatics Software has been installed using GNU Modules.&lt;br /&gt;
&lt;br /&gt;
== Common Modules ==&lt;br /&gt;
&lt;br /&gt;
CBCB Software modules are already configured for interactive shells on Red Hat 7 machines - no additional setup is required. The module files are installed in the following location:&lt;br /&gt;
 /cbcb/sw/RedHat-7-x86_64/common/modules/release/latest&lt;br /&gt;
&lt;br /&gt;
To see see what modules are available:&lt;br /&gt;
 $ module avail&lt;br /&gt;
&lt;br /&gt;
To add a module to your environment, use &amp;lt;code&amp;gt;module add&amp;lt;/code&amp;gt;:&lt;br /&gt;
 $ module add samtools/0.1.19&lt;br /&gt;
&lt;br /&gt;
Note that you can also specify the software name without the version:&lt;br /&gt;
 $ module add samtools&lt;br /&gt;
&lt;br /&gt;
Now samtools has been added to your environment:&lt;br /&gt;
 $ which samtools&lt;br /&gt;
 /cbcb/sw/RedHat-7-x86_64/common/local/samtools/0.1.19/bin/samtools&lt;br /&gt;
&lt;br /&gt;
== Personal Modules ==&lt;br /&gt;
&lt;br /&gt;
We have created some scripts to assist you with installing software and modules to your personal directory in &amp;lt;code&amp;gt;/cbcb/sw&amp;lt;/code&amp;gt;. We recommend that you use these scripts because this will help us share installed software among other CBCB users.&lt;br /&gt;
&lt;br /&gt;
Run this initialization script to set up your directory structure:&lt;br /&gt;
 $ /cbcb/sw/RedHat-7-x86_64/common/scripts/init_cbcb_sw_user.sh&lt;br /&gt;
&lt;br /&gt;
This will create a directory for you:&lt;br /&gt;
 $ tree /cbcb/sw/RedHat-7-x86_64/users/&amp;lt;username&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
/cbcb/sw/RedHat-7-x86_64/users/&amp;lt;username&amp;gt;&lt;br /&gt;
├── local&lt;br /&gt;
├── modules&lt;br /&gt;
│   └── &amp;lt;username&amp;gt;&lt;br /&gt;
│       └── env&lt;br /&gt;
├── module_template&lt;br /&gt;
├── README&lt;br /&gt;
├── scripts&lt;br /&gt;
│   ├── copy_module_template.sh&lt;br /&gt;
│   ├── init_install_vars.sh&lt;br /&gt;
│   └── install_package.sh&lt;br /&gt;
└── src&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Use the &amp;lt;code&amp;gt;src&amp;lt;/code&amp;gt; directory for storing and compiling source code.&lt;br /&gt;
* Use the &amp;lt;code&amp;gt;local&amp;lt;/code&amp;gt; directory as the installation prefix.&lt;br /&gt;
* Use the &amp;lt;code&amp;gt;modules&amp;lt;/code&amp;gt; directory to store your modulefiles.&lt;br /&gt;
&lt;br /&gt;
See [[#Installing Software]] below.&lt;br /&gt;
&lt;br /&gt;
To make use of your personal module file directory, add the following to your &amp;lt;code&amp;gt;~/.bashrc&amp;lt;/code&amp;gt;:&lt;br /&gt;
 module use /cbcb/sw/RedHat-7-x86_64/users/&amp;lt;username&amp;gt;/modules&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Installing Software ===&lt;br /&gt;
&lt;br /&gt;
Use the &amp;lt;code&amp;gt;install_package.sh&amp;lt;/code&amp;gt; script to automatically compile software that uses &amp;lt;code&amp;gt;./configure; make; make install&amp;lt;/code&amp;gt;. The advantage to using this install script is that it will:&lt;br /&gt;
* use the standardized directory structure for personal software installation, and&lt;br /&gt;
* &#039;&#039;&#039;&#039;&#039;automatically&#039;&#039;&#039;&#039;&#039; create a module file for the software in your &amp;lt;code&amp;gt;modules&amp;lt;/code&amp;gt; directory!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For full details, read the &amp;lt;code&amp;gt;README&amp;lt;/code&amp;gt; placed in your personal directory (&amp;lt;code&amp;gt;/cbcb/sw/RedHat-7-x86_64/users/&amp;lt;username&amp;gt;&amp;lt;/code&amp;gt;). It&#039;s also available in the [https://gitlab.umiacs.umd.edu/cbcb/cbcb-sw/blob/master/templates/user_readme.md  cbcb-sw Gitlab repository].&lt;br /&gt;
&lt;br /&gt;
== Setup for non-interactive shells ==&lt;br /&gt;
&lt;br /&gt;
Modules are already configured for interactive shells, but to use modules with non-interactive shells, add the following to your ~/.bashrc:&lt;br /&gt;
 . /usr/share/Modules/init/bash&lt;br /&gt;
 . /etc/profile.d/ummodules.sh&lt;br /&gt;
&lt;br /&gt;
For more information, see the [https://wiki.umiacs.umd.edu/umiacs/index.php/Modules UMIACS wiki].&lt;br /&gt;
&lt;br /&gt;
== GNU Modules Cheatsheet ==&lt;br /&gt;
&lt;br /&gt;
Ask for help:&lt;br /&gt;
 module --help&lt;br /&gt;
&lt;br /&gt;
List available modules:&lt;br /&gt;
 module avail&lt;br /&gt;
&lt;br /&gt;
Add a module to your environment:&lt;br /&gt;
 module add blast&lt;br /&gt;
&lt;br /&gt;
List loaded modules:&lt;br /&gt;
 module list&lt;br /&gt;
&lt;br /&gt;
Remove a module from your environment:&lt;br /&gt;
 module rm blast&lt;br /&gt;
&lt;br /&gt;
Remove all modules from your environment:&lt;br /&gt;
 module purge&lt;br /&gt;
&lt;br /&gt;
Add a path to search for available modules:&lt;br /&gt;
 module use /cbcb/sw/RedHat-7-x86_64/users/lmendelo/modules&lt;br /&gt;
&lt;br /&gt;
See what changes a module makes to your environment:&lt;br /&gt;
 module show Python2/common/2.7.9&lt;br /&gt;
&lt;br /&gt;
== Contact ==&lt;br /&gt;
&lt;br /&gt;
Brought to you by:&lt;br /&gt;
&lt;br /&gt;
* [mailto:abelew@umiacs.umd.edu Trey Belew]&lt;br /&gt;
* [mailto:keith@umiacs.umd.edu Keith Hughitt]&lt;br /&gt;
* [mailto:lmendelo@umiacs.umd.edu Lee Mendelowitz]&lt;br /&gt;
&lt;br /&gt;
== See Also ==&lt;br /&gt;
* [https://wiki.umiacs.umd.edu/umiacs/index.php/Modules UMIACS wiki]&lt;br /&gt;
* [https://gitlab.umiacs.umd.edu/cbcb/cbcb-sw Repository on GitLab]&lt;br /&gt;
* [https://docs.google.com/presentation/d/1UgKtnjcqHlpLZU79hGXfkgvNtse-ksMQ_gJMFCVLKRw/edit?usp=sharing CBCB Software slides on Google Drive]&lt;/div&gt;</summary>
		<author><name>Lmendelo</name></author>
	</entry>
	<entry>
		<id>https://wiki.umiacs.umd.edu/cbcb/index.php?title=CBCB_Software_Modules&amp;diff=9006</id>
		<title>CBCB Software Modules</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/cbcb/index.php?title=CBCB_Software_Modules&amp;diff=9006"/>
		<updated>2015-03-03T05:10:17Z</updated>

		<summary type="html">&lt;p&gt;Lmendelo: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Starting in the Spring of 2015, communal CBCB Bioinformatics Software has been installed using GNU Modules.&lt;br /&gt;
&lt;br /&gt;
== Common Modules ==&lt;br /&gt;
&lt;br /&gt;
CBCB Software modules are already configured for interactive shells on Red Hat 7 machines - no additional setup is required. The module files are installed in the following location:&lt;br /&gt;
 /cbcb/sw/RedHat-7-x86_64/common/modules/release/latest&lt;br /&gt;
&lt;br /&gt;
To see see what modules are available:&lt;br /&gt;
 $ module avail&lt;br /&gt;
&lt;br /&gt;
To add a module to your environment, use &amp;lt;code&amp;gt;module add&amp;lt;/code&amp;gt;:&lt;br /&gt;
 $ module add samtools/0.1.19&lt;br /&gt;
&lt;br /&gt;
Note that you can also specify the software name without the version:&lt;br /&gt;
 $ module add samtools&lt;br /&gt;
&lt;br /&gt;
Now samtools has been added to your environment:&lt;br /&gt;
 $ which samtools&lt;br /&gt;
 /cbcb/sw/RedHat-7-x86_64/common/local/samtools/0.1.19/bin/samtools&lt;br /&gt;
&lt;br /&gt;
== Personal Modules ==&lt;br /&gt;
&lt;br /&gt;
We have created some scripts to assist you with installing software and modules to your personal directory in &amp;lt;code&amp;gt;/cbcb/sw&amp;lt;/code&amp;gt;. We recommend that you use these scripts because this will help us share installed software among other CBCB users.&lt;br /&gt;
&lt;br /&gt;
Run this initialization script to set up your directory structure:&lt;br /&gt;
 $ /cbcb/sw/RedHat-7-x86_64/common/scripts/init_cbcb_sw_user.sh&lt;br /&gt;
&lt;br /&gt;
This will create a directory for you:&lt;br /&gt;
 $ tree /cbcb/sw/RedHat-7-x86_64/users/&amp;lt;username&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
/cbcb/sw/RedHat-7-x86_64/users/&amp;lt;username&amp;gt;&lt;br /&gt;
├── local&lt;br /&gt;
├── modules&lt;br /&gt;
│   └── &amp;lt;username&amp;gt;&lt;br /&gt;
│       └── env&lt;br /&gt;
├── module_template&lt;br /&gt;
├── README&lt;br /&gt;
├── scripts&lt;br /&gt;
│   ├── copy_module_template.sh&lt;br /&gt;
│   ├── init_install_vars.sh&lt;br /&gt;
│   └── install_package.sh&lt;br /&gt;
└── src&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Use the &amp;lt;code&amp;gt;src&amp;lt;/code&amp;gt; directory for storing and compiling source code.&lt;br /&gt;
* Use the &amp;lt;code&amp;gt;local&amp;lt;/code&amp;gt; directory as the installation prefix.&lt;br /&gt;
* Use the &amp;lt;code&amp;gt;modules&amp;lt;/code&amp;gt; directory to store your modulefiles.&lt;br /&gt;
&lt;br /&gt;
See [[#Installing Software]] below.&lt;br /&gt;
&lt;br /&gt;
To make use of your personal module file directory, add the following to your &amp;lt;code&amp;gt;~/.bashrc&amp;lt;/code&amp;gt;:&lt;br /&gt;
 module use /cbcb/sw/RedHat-7-x86_64/users/&amp;lt;username&amp;gt;/modules&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Installing Software ===&lt;br /&gt;
&lt;br /&gt;
Use the &amp;lt;code&amp;gt;install_package.sh&amp;lt;/code&amp;gt; script to automatically compile software that uses &amp;lt;code&amp;gt;./configure; make; make install&amp;lt;/code&amp;gt;. The advantage to using this install script is that it will:&lt;br /&gt;
* use the standardized directory structure for personal software installation, and&lt;br /&gt;
* &#039;&#039;&#039;&#039;&#039;automatically&#039;&#039;&#039;&#039;&#039; create a module file for the software in your &amp;lt;code&amp;gt;modules&amp;lt;/code&amp;gt; directory!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For full details, read the &amp;lt;code&amp;gt;README&amp;lt;/code&amp;gt; placed in your home directory. It&#039;s also available in the [https://gitlab.umiacs.umd.edu/cbcb/cbcb-sw/blob/master/templates/user_readme.md  cbcb-sw Gitlab repository].&lt;br /&gt;
&lt;br /&gt;
== Setup for non-interactive shells ==&lt;br /&gt;
&lt;br /&gt;
Modules are already configured for interactive shells, but to use modules with non-interactive shells, add the following to your ~/.bashrc:&lt;br /&gt;
 . /usr/share/Modules/init/bash&lt;br /&gt;
 . /etc/profile.d/ummodules.sh&lt;br /&gt;
&lt;br /&gt;
For more information, see the [https://wiki.umiacs.umd.edu/umiacs/index.php/Modules UMIACS wiki].&lt;br /&gt;
&lt;br /&gt;
== GNU Modules Cheatsheet ==&lt;br /&gt;
&lt;br /&gt;
Ask for help:&lt;br /&gt;
 module --help&lt;br /&gt;
&lt;br /&gt;
List available modules:&lt;br /&gt;
 module avail&lt;br /&gt;
&lt;br /&gt;
Add a module to your environment:&lt;br /&gt;
 module add blast&lt;br /&gt;
&lt;br /&gt;
List loaded modules:&lt;br /&gt;
 module list&lt;br /&gt;
&lt;br /&gt;
Remove a module from your environment:&lt;br /&gt;
 module rm blast&lt;br /&gt;
&lt;br /&gt;
Remove all modules from your environment:&lt;br /&gt;
 module purge&lt;br /&gt;
&lt;br /&gt;
Add a path to search for available modules:&lt;br /&gt;
 module use /cbcb/sw/RedHat-7-x86_64/users/lmendelo/modules&lt;br /&gt;
&lt;br /&gt;
See what changes a module makes to your environment:&lt;br /&gt;
 module show Python2/common/2.7.9&lt;br /&gt;
&lt;br /&gt;
== Contact ==&lt;br /&gt;
&lt;br /&gt;
Brought to you by:&lt;br /&gt;
&lt;br /&gt;
* [mailto:abelew@umiacs.umd.edu Trey Belew]&lt;br /&gt;
* [mailto:keith@umiacs.umd.edu Keith Hughitt]&lt;br /&gt;
* [mailto:lmendelo@umiacs.umd.edu Lee Mendelowitz]&lt;br /&gt;
&lt;br /&gt;
== See Also ==&lt;br /&gt;
* [https://wiki.umiacs.umd.edu/umiacs/index.php/Modules UMIACS wiki]&lt;br /&gt;
* [https://gitlab.umiacs.umd.edu/cbcb/cbcb-sw Repository on GitLab]&lt;br /&gt;
* [https://docs.google.com/presentation/d/1UgKtnjcqHlpLZU79hGXfkgvNtse-ksMQ_gJMFCVLKRw/edit?usp=sharing CBCB Software slides on Google Drive]&lt;/div&gt;</summary>
		<author><name>Lmendelo</name></author>
	</entry>
	<entry>
		<id>https://wiki.umiacs.umd.edu/cbcb/index.php?title=CBCB_Software_Modules&amp;diff=9005</id>
		<title>CBCB Software Modules</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/cbcb/index.php?title=CBCB_Software_Modules&amp;diff=9005"/>
		<updated>2015-03-03T05:06:16Z</updated>

		<summary type="html">&lt;p&gt;Lmendelo: /* Installing Software */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Starting in the Spring of 2015, communal CBCB Bioinformatics Software has been installed using GNU Modules.&lt;br /&gt;
&lt;br /&gt;
== Common Modules ==&lt;br /&gt;
&lt;br /&gt;
CBCB Software modules are already configured for interactive shells on Red Hat 7 machines - no additional setup is required. The module files are installed in the following location:&lt;br /&gt;
 /cbcb/sw/RedHat-7-x86_64/common/modules/release/latest&lt;br /&gt;
&lt;br /&gt;
To see see what modules are available:&lt;br /&gt;
 $ module avail&lt;br /&gt;
&lt;br /&gt;
To add a module to your environment, use &amp;lt;code&amp;gt;module add&amp;lt;/code&amp;gt;:&lt;br /&gt;
 $ module add samtools/0.1.19&lt;br /&gt;
&lt;br /&gt;
Note that you can also specify the software name without the version:&lt;br /&gt;
 $ module add samtools&lt;br /&gt;
&lt;br /&gt;
Now samtools has been added to your environment:&lt;br /&gt;
 $ which samtools&lt;br /&gt;
 /cbcb/sw/RedHat-7-x86_64/common/local/samtools/0.1.19/bin/samtools&lt;br /&gt;
&lt;br /&gt;
== Personal Modules ==&lt;br /&gt;
&lt;br /&gt;
We have created some scripts to assist you with installing software and modules to your personal directory in &amp;lt;code&amp;gt;/cbcb/sw&amp;lt;/code&amp;gt;. We recommend that you use these scripts because this will help us share installed software among other CBCB users.&lt;br /&gt;
&lt;br /&gt;
Run this initialization script to set up your directory structure:&lt;br /&gt;
 $ /cbcb/sw/RedHat-7-x86_64/common/scripts/init_cbcb_sw_user.sh&lt;br /&gt;
&lt;br /&gt;
This will create a directory for you:&lt;br /&gt;
 $ tree /cbcb/sw/RedHat-7-x86_64/users/&amp;lt;username&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
/cbcb/sw/RedHat-7-x86_64/users/&amp;lt;username&amp;gt;&lt;br /&gt;
├── local&lt;br /&gt;
├── modules&lt;br /&gt;
│   └── &amp;lt;username&amp;gt;&lt;br /&gt;
│       └── env&lt;br /&gt;
├── module_template&lt;br /&gt;
├── README&lt;br /&gt;
├── scripts&lt;br /&gt;
│   ├── copy_module_template.sh&lt;br /&gt;
│   ├── init_install_vars.sh&lt;br /&gt;
│   └── install_package.sh&lt;br /&gt;
└── src&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Use the &amp;lt;code&amp;gt;src&amp;lt;/code&amp;gt; directory for storing and compiling source code.&lt;br /&gt;
* Use the &amp;lt;code&amp;gt;local&amp;lt;/code&amp;gt; directory as the installation prefix.&lt;br /&gt;
* Use the &amp;lt;code&amp;gt;modules&amp;lt;/code&amp;gt; directory to store your modulefiles.&lt;br /&gt;
&lt;br /&gt;
See [[#Installing Software]] below.&lt;br /&gt;
&lt;br /&gt;
To make use of your personal module file directory, add the following to your &amp;lt;code&amp;gt;~/.bashrc&amp;lt;/code&amp;gt;:&lt;br /&gt;
 module use /cbcb/sw/RedHat-7-x86_64/users/&amp;lt;username&amp;gt;/modules&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Installing Software ===&lt;br /&gt;
&lt;br /&gt;
Use the &amp;lt;code&amp;gt;install_package.sh&amp;lt;/code&amp;gt; script to automatically compile software that uses &amp;lt;code&amp;gt;./configure; make; make install&amp;lt;/code&amp;gt;. The advantage to using this install script is that it will:&lt;br /&gt;
* use the standardized directory structure for personal software installation, and&lt;br /&gt;
* &#039;&#039;&#039;&#039;&#039;automatically&#039;&#039;&#039;&#039;&#039; create a module file for the software in your &amp;lt;code&amp;gt;modules&amp;lt;/code&amp;gt; directory!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For full details, read the &amp;lt;code&amp;gt;README&amp;lt;/code&amp;gt; placed in your home directory. It&#039;s also available in the [https://gitlab.umiacs.umd.edu/cbcb/cbcb-sw/blob/master/templates/user_readme.md  cbcb-sw Gitlab repository].&lt;br /&gt;
&lt;br /&gt;
== Setup for non-interactive shells ==&lt;br /&gt;
&lt;br /&gt;
Modules are already configured for interactive shells, but to use modules with non-interactive shells, add the following to your ~/.bashrc:&lt;br /&gt;
 . /usr/share/Modules/init/bash&lt;br /&gt;
 . /etc/profile.d/ummodules.sh&lt;br /&gt;
&lt;br /&gt;
For more information, see the [https://wiki.umiacs.umd.edu/umiacs/index.php/Modules UMIACS wiki].&lt;br /&gt;
&lt;br /&gt;
== GNU Modules Cheatsheet ==&lt;br /&gt;
&lt;br /&gt;
Ask for help:&lt;br /&gt;
 module --help&lt;br /&gt;
&lt;br /&gt;
List available modules:&lt;br /&gt;
 module avail&lt;br /&gt;
&lt;br /&gt;
Add a module to your environment:&lt;br /&gt;
 module add blast&lt;br /&gt;
&lt;br /&gt;
List loaded modules:&lt;br /&gt;
 module list&lt;br /&gt;
&lt;br /&gt;
Remove a module from your environment:&lt;br /&gt;
 module rm blast&lt;br /&gt;
&lt;br /&gt;
Remove all modules from your environment:&lt;br /&gt;
 module purge&lt;br /&gt;
&lt;br /&gt;
Add a path to search for available modules:&lt;br /&gt;
 module use /cbcb/sw/RedHat-7-x86_64/users/lmendelo/modules&lt;br /&gt;
&lt;br /&gt;
See what changes a module makes to your environment:&lt;br /&gt;
 module show Python2/common/2.7.9&lt;br /&gt;
&lt;br /&gt;
== Contact ==&lt;br /&gt;
&lt;br /&gt;
Brought to you by:&lt;br /&gt;
&lt;br /&gt;
* [mailto:abelew@umiacs.umd.edu Trey Abelew]&lt;br /&gt;
* [mailto:keith@umiacs.umd.edu Keith Hughitt]&lt;br /&gt;
* [mailto:lmendelo@umiacs.umd.edu Lee Mendelowitz]&lt;br /&gt;
&lt;br /&gt;
== See Also ==&lt;br /&gt;
* [https://wiki.umiacs.umd.edu/umiacs/index.php/Modules UMIACS wiki]&lt;br /&gt;
* [https://gitlab.umiacs.umd.edu/cbcb/cbcb-sw Repository on GitLab]&lt;br /&gt;
* [https://docs.google.com/presentation/d/1UgKtnjcqHlpLZU79hGXfkgvNtse-ksMQ_gJMFCVLKRw/edit?usp=sharing CBCB Software slides on Google Drive]&lt;/div&gt;</summary>
		<author><name>Lmendelo</name></author>
	</entry>
	<entry>
		<id>https://wiki.umiacs.umd.edu/cbcb/index.php?title=CBCB_Software_Modules&amp;diff=9004</id>
		<title>CBCB Software Modules</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/cbcb/index.php?title=CBCB_Software_Modules&amp;diff=9004"/>
		<updated>2015-03-03T05:04:19Z</updated>

		<summary type="html">&lt;p&gt;Lmendelo: /* Personal Modules */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Starting in the Spring of 2015, communal CBCB Bioinformatics Software has been installed using GNU Modules.&lt;br /&gt;
&lt;br /&gt;
== Common Modules ==&lt;br /&gt;
&lt;br /&gt;
CBCB Software modules are already configured for interactive shells on Red Hat 7 machines - no additional setup is required. The module files are installed in the following location:&lt;br /&gt;
 /cbcb/sw/RedHat-7-x86_64/common/modules/release/latest&lt;br /&gt;
&lt;br /&gt;
To see see what modules are available:&lt;br /&gt;
 $ module avail&lt;br /&gt;
&lt;br /&gt;
To add a module to your environment, use &amp;lt;code&amp;gt;module add&amp;lt;/code&amp;gt;:&lt;br /&gt;
 $ module add samtools/0.1.19&lt;br /&gt;
&lt;br /&gt;
Note that you can also specify the software name without the version:&lt;br /&gt;
 $ module add samtools&lt;br /&gt;
&lt;br /&gt;
Now samtools has been added to your environment:&lt;br /&gt;
 $ which samtools&lt;br /&gt;
 /cbcb/sw/RedHat-7-x86_64/common/local/samtools/0.1.19/bin/samtools&lt;br /&gt;
&lt;br /&gt;
== Personal Modules ==&lt;br /&gt;
&lt;br /&gt;
We have created some scripts to assist you with installing software and modules to your personal directory in &amp;lt;code&amp;gt;/cbcb/sw&amp;lt;/code&amp;gt;. We recommend that you use these scripts because this will help us share installed software among other CBCB users.&lt;br /&gt;
&lt;br /&gt;
Run this initialization script to set up your directory structure:&lt;br /&gt;
 $ /cbcb/sw/RedHat-7-x86_64/common/scripts/init_cbcb_sw_user.sh&lt;br /&gt;
&lt;br /&gt;
This will create a directory for you:&lt;br /&gt;
 $ tree /cbcb/sw/RedHat-7-x86_64/users/&amp;lt;username&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
/cbcb/sw/RedHat-7-x86_64/users/&amp;lt;username&amp;gt;&lt;br /&gt;
├── local&lt;br /&gt;
├── modules&lt;br /&gt;
│   └── &amp;lt;username&amp;gt;&lt;br /&gt;
│       └── env&lt;br /&gt;
├── module_template&lt;br /&gt;
├── README&lt;br /&gt;
├── scripts&lt;br /&gt;
│   ├── copy_module_template.sh&lt;br /&gt;
│   ├── init_install_vars.sh&lt;br /&gt;
│   └── install_package.sh&lt;br /&gt;
└── src&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Use the &amp;lt;code&amp;gt;src&amp;lt;/code&amp;gt; directory for storing and compiling source code.&lt;br /&gt;
* Use the &amp;lt;code&amp;gt;local&amp;lt;/code&amp;gt; directory as the installation prefix.&lt;br /&gt;
* Use the &amp;lt;code&amp;gt;modules&amp;lt;/code&amp;gt; directory to store your modulefiles.&lt;br /&gt;
&lt;br /&gt;
See [[#Installing Software]] below.&lt;br /&gt;
&lt;br /&gt;
To make use of your personal module file directory, add the following to your &amp;lt;code&amp;gt;~/.bashrc&amp;lt;/code&amp;gt;:&lt;br /&gt;
 module use /cbcb/sw/RedHat-7-x86_64/users/&amp;lt;username&amp;gt;/modules&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Installing Software ===&lt;br /&gt;
&lt;br /&gt;
Use the &amp;lt;code&amp;gt;install_package.sh&amp;lt;/code&amp;gt; script to automatically compile software which uses &amp;lt;code&amp;gt;./configure; make; make install&amp;lt;/code&amp;gt;. The advantage to using this install script is that it will:&lt;br /&gt;
* use the standardized directory structure for personal software installation, and&lt;br /&gt;
* &#039;&#039;&#039;&#039;&#039;automatically&#039;&#039;&#039;&#039;&#039; create a module file for the software in your &amp;lt;code&amp;gt;modules&amp;lt;/code&amp;gt; directory!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For full details, read the &amp;lt;code&amp;gt;README&amp;lt;/code&amp;gt; placed in your home directory. It&#039;s also available in the [https://gitlab.umiacs.umd.edu/cbcb/cbcb-sw/blob/master/templates/user_readme.md  cbcb-sw Gitlab repository].&lt;br /&gt;
&lt;br /&gt;
== Setup for non-interactive shells ==&lt;br /&gt;
&lt;br /&gt;
Modules are already configured for interactive shells, but to use modules with non-interactive shells, add the following to your ~/.bashrc:&lt;br /&gt;
 . /usr/share/Modules/init/bash&lt;br /&gt;
 . /etc/profile.d/ummodules.sh&lt;br /&gt;
&lt;br /&gt;
For more information, see the [https://wiki.umiacs.umd.edu/umiacs/index.php/Modules UMIACS wiki].&lt;br /&gt;
&lt;br /&gt;
== GNU Modules Cheatsheet ==&lt;br /&gt;
&lt;br /&gt;
Ask for help:&lt;br /&gt;
 module --help&lt;br /&gt;
&lt;br /&gt;
List available modules:&lt;br /&gt;
 module avail&lt;br /&gt;
&lt;br /&gt;
Add a module to your environment:&lt;br /&gt;
 module add blast&lt;br /&gt;
&lt;br /&gt;
List loaded modules:&lt;br /&gt;
 module list&lt;br /&gt;
&lt;br /&gt;
Remove a module from your environment:&lt;br /&gt;
 module rm blast&lt;br /&gt;
&lt;br /&gt;
Remove all modules from your environment:&lt;br /&gt;
 module purge&lt;br /&gt;
&lt;br /&gt;
Add a path to search for available modules:&lt;br /&gt;
 module use /cbcb/sw/RedHat-7-x86_64/users/lmendelo/modules&lt;br /&gt;
&lt;br /&gt;
See what changes a module makes to your environment:&lt;br /&gt;
 module show Python2/common/2.7.9&lt;br /&gt;
&lt;br /&gt;
== Contact ==&lt;br /&gt;
&lt;br /&gt;
Brought to you by:&lt;br /&gt;
&lt;br /&gt;
* [mailto:abelew@umiacs.umd.edu Trey Abelew]&lt;br /&gt;
* [mailto:keith@umiacs.umd.edu Keith Hughitt]&lt;br /&gt;
* [mailto:lmendelo@umiacs.umd.edu Lee Mendelowitz]&lt;br /&gt;
&lt;br /&gt;
== See Also ==&lt;br /&gt;
* [https://wiki.umiacs.umd.edu/umiacs/index.php/Modules UMIACS wiki]&lt;br /&gt;
* [https://gitlab.umiacs.umd.edu/cbcb/cbcb-sw Repository on GitLab]&lt;br /&gt;
* [https://docs.google.com/presentation/d/1UgKtnjcqHlpLZU79hGXfkgvNtse-ksMQ_gJMFCVLKRw/edit?usp=sharing CBCB Software slides on Google Drive]&lt;/div&gt;</summary>
		<author><name>Lmendelo</name></author>
	</entry>
	<entry>
		<id>https://wiki.umiacs.umd.edu/cbcb/index.php?title=Getting_Started_in_CBCB&amp;diff=9003</id>
		<title>Getting Started in CBCB</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/cbcb/index.php?title=Getting_Started_in_CBCB&amp;diff=9003"/>
		<updated>2015-03-03T04:59:11Z</updated>

		<summary type="html">&lt;p&gt;Lmendelo: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;You may want to review the following:&lt;br /&gt;
&lt;br /&gt;
[[Media:CBCB-quick-guide.pdf]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Getting Building Access and Room Keys==&lt;br /&gt;
&lt;br /&gt;
CBCB is located on the 3rd floor of The Biomolecular Sciences Building identified on campus maps as Building #296.  The building is secure and access is gained by either using your UM ID card, guest card or entering the 3-digit code of the person you to visit at the call box on the right side of the front door.&lt;br /&gt;
&lt;br /&gt;
Contact the Center Coordinator, Christine Bogan, about gaining card access to the building.  She will need the following information:&lt;br /&gt;
*An notification email from your sponsor/adviser&lt;br /&gt;
*Your Name&lt;br /&gt;
*Your 9 Digit University ID number&lt;br /&gt;
*Your Contact email&lt;br /&gt;
&lt;br /&gt;
Along with your assigned space and phone numbers, the coordinator will send your information to UMIACS Coordinator Edna Walker who will contact campus security to add you into their system.  &#039;&#039;Note: clearance usually takes a number of days, so contact the coordinator as soon as possible.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
If you prefer not to send your information through email feel free to contact the coordinator in person.  &lt;br /&gt;
&lt;br /&gt;
You must get your key from the coordinator in person.&lt;br /&gt;
&lt;br /&gt;
Christine Bogan&amp;lt;br&amp;gt;&lt;br /&gt;
Room 3121&amp;lt;br&amp;gt;&lt;br /&gt;
Biomolecular Sciences Bldg #296&amp;lt;br&amp;gt;&lt;br /&gt;
301.405.5936&amp;lt;br&amp;gt;&lt;br /&gt;
cbogan[at]umd.edu&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Research In Progress Seminars==&lt;br /&gt;
&lt;br /&gt;
These seminars are held through the year.  For information go to [http://cbcb.umd.edu/node/18625 CBCB Research in Progress]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For a list of our Disk Storage and amount of available space left on each one, see [http://wiki.umiacs.umd.edu/cbcb-private/index.php/Storage wiki.umiacs.umd.edu/cbcb-private/index.php/Storage]&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Configuring Your Home Directory and Shell ==&lt;br /&gt;
&lt;br /&gt;
We import common settings files that set our path variables to include commonly shared software repositories.&lt;br /&gt;
&lt;br /&gt;
As a start, add the following line to the top of the file called &amp;quot;.bashrc&amp;quot; located in your home directory (/nfshomes/username/):&lt;br /&gt;
&lt;br /&gt;
 . /fs/sz-user-supported/share/dotfiles/bashrc.cbcb&lt;br /&gt;
&lt;br /&gt;
This will import the common bashrc.cbcb file into your own bashrc file every time you log in.&lt;br /&gt;
&lt;br /&gt;
Now add this line to your &amp;quot;.bash_profile&amp;quot; file, also located in your home directory:&lt;br /&gt;
&lt;br /&gt;
 . ~/.bashrc&lt;br /&gt;
&lt;br /&gt;
This will import your personal bashrc file every time you log in. Now you should have access to most of the locally installed software like &amp;quot;blastall&amp;quot; and &amp;quot;AMOS.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
If you want to add any addition commands to your bashrc file, such as setting your default text editor to &amp;quot;vim&amp;quot; or formatting the output of bash commands (eg. &amp;quot;ls&amp;quot;), add the appropriate commands after the imported common files as shown in this example:&lt;br /&gt;
&lt;br /&gt;
 . /fs/sz-user-supported/share/dotfiles/bashrc.cbcb&lt;br /&gt;
 &lt;br /&gt;
 alias vi=&#039;vim&#039;&lt;br /&gt;
&lt;br /&gt;
 alias ls=&#039;ls --color&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
If you decide you want to change the settings in the common bashrc.cbcb to better suit your personal needs, then please copy and paste its contents into your personal bashrc file. &#039;&#039;&#039;Do not modify the common bashrc.cbcb file as it will affect everyone&#039;s environment.&#039;&#039;&#039; Also check back periodically as people may add common paths for new software.&lt;br /&gt;
&lt;br /&gt;
If you have any other problems, contact staff [at] umiacs.umd.edu or your PI. &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
More resources can be found at [https://wiki.umiacs.umd.edu/umiacs/index.php/GettingStarted umiacs wiki]&lt;br /&gt;
&lt;br /&gt;
== CBCB Software Modules ==&lt;br /&gt;
To use CBCB Software Modules, see [[CBCB Software Modules]]&lt;br /&gt;
&lt;br /&gt;
== Printing ==&lt;br /&gt;
Go to the umiacs wiki to find [https://wiki.umiacs.umd.edu/umiacs/index.php/Printing system-specific guides for printing], and be sure to [https://wiki.umiacs.umd.edu/umiacs/index.php/PrinterQueueNaming add &#039;nb&#039; to the end of your print queue] to avoid wasting paper printing banners.&lt;br /&gt;
&lt;br /&gt;
== Using the Wiki ==&lt;br /&gt;
* [http://en.wikipedia.org/wiki/Wikipedia:Cheatsheet Wiki Formatting Cheatsheet]&lt;br /&gt;
* [http://www.mediawiki.org/wiki/Help:Configuration_settings Configuration settings list]&lt;br /&gt;
* [http://www.mediawiki.org/wiki/Help:FAQ MediaWiki FAQ]&lt;br /&gt;
* [http://mail.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]&lt;br /&gt;
&lt;br /&gt;
== When You Travel ==&lt;br /&gt;
&lt;br /&gt;
[[Media:CBCB_travel_request_form_oct_2014.pdf‎]] form to fill out to obtain information for travel reimbursement&lt;br /&gt;
&lt;br /&gt;
[[Media:Travel_101_cbcb_revised_4-2013.pdf]] for more detailed travel info&lt;/div&gt;</summary>
		<author><name>Lmendelo</name></author>
	</entry>
	<entry>
		<id>https://wiki.umiacs.umd.edu/cbcb/index.php?title=CBCB_Software_Modules&amp;diff=9002</id>
		<title>CBCB Software Modules</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/cbcb/index.php?title=CBCB_Software_Modules&amp;diff=9002"/>
		<updated>2015-03-03T04:53:19Z</updated>

		<summary type="html">&lt;p&gt;Lmendelo: /* See Also */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Starting in the Spring of 2015, communal CBCB Bioinformatics Software has been installed using GNU Modules.&lt;br /&gt;
&lt;br /&gt;
== Common Modules ==&lt;br /&gt;
&lt;br /&gt;
CBCB Software modules are already configured for interactive shells on Red Hat 7 machines - no additional setup is required. The module files are installed in the following location:&lt;br /&gt;
 /cbcb/sw/RedHat-7-x86_64/common/modules/release/latest&lt;br /&gt;
&lt;br /&gt;
To see see what modules are available:&lt;br /&gt;
 $ module avail&lt;br /&gt;
&lt;br /&gt;
To add a module to your environment, use &amp;lt;code&amp;gt;module add&amp;lt;/code&amp;gt;:&lt;br /&gt;
 $ module add samtools/0.1.19&lt;br /&gt;
&lt;br /&gt;
Note that you can also specify the software name without the version:&lt;br /&gt;
 $ module add samtools&lt;br /&gt;
&lt;br /&gt;
Now samtools has been added to your environment:&lt;br /&gt;
 $ which samtools&lt;br /&gt;
 /cbcb/sw/RedHat-7-x86_64/common/local/samtools/0.1.19/bin/samtools&lt;br /&gt;
&lt;br /&gt;
== Personal Modules ==&lt;br /&gt;
&lt;br /&gt;
We have created some scripts to assist you with installing software and modules to your personal directory in &amp;lt;code&amp;gt;/cbcb/sw.&amp;lt;/code&amp;gt;. We recommend that you use these scripts because this will help us share installed software among other CBCB users.&lt;br /&gt;
&lt;br /&gt;
Run this initialization script to set up your directory structure:&lt;br /&gt;
 $ /cbcb/sw/RedHat-7-x86_64/common/scripts/init_cbcb_sw_user.sh&lt;br /&gt;
&lt;br /&gt;
This will create a directory for you:&lt;br /&gt;
 $ tree /cbcb/sw/RedHat-7-x86_64/users/&amp;lt;username&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
/cbcb/sw/RedHat-7-x86_64/users/&amp;lt;username&amp;gt;&lt;br /&gt;
├── local&lt;br /&gt;
├── modules&lt;br /&gt;
│   └── &amp;lt;username&amp;gt;&lt;br /&gt;
│       └── env&lt;br /&gt;
├── module_template&lt;br /&gt;
├── README&lt;br /&gt;
├── scripts&lt;br /&gt;
│   ├── copy_module_template.sh&lt;br /&gt;
│   ├── init_install_vars.sh&lt;br /&gt;
│   └── install_package.sh&lt;br /&gt;
└── src&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Use the &amp;lt;code&amp;gt;src&amp;lt;/code&amp;gt; directory for storing and compiling source code.&lt;br /&gt;
* Use the &amp;lt;code&amp;gt;local&amp;lt;/code&amp;gt; directory as the installation prefix.&lt;br /&gt;
* Use the &amp;lt;code&amp;gt;modules&amp;lt;/code&amp;gt; directory to store your modulefiles.&lt;br /&gt;
&lt;br /&gt;
See [[#Installing Software]] below.&lt;br /&gt;
&lt;br /&gt;
To make use of your personal module file directory, add the following to your &amp;lt;code&amp;gt;~/.bashrc&amp;lt;/code&amp;gt;:&lt;br /&gt;
 module use /cbcb/sw/RedHat-7-x86_64/users/&amp;lt;username&amp;gt;/modules&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Installing Software ===&lt;br /&gt;
&lt;br /&gt;
Use the &amp;lt;code&amp;gt;install_package.sh&amp;lt;/code&amp;gt; script to automatically compile software which uses &amp;lt;code&amp;gt;./configure; make; make install&amp;lt;/code&amp;gt;. The advantage to using this install script is that it will:&lt;br /&gt;
* use the standardized directory structure for personal software installation, and&lt;br /&gt;
* &#039;&#039;&#039;&#039;&#039;automatically&#039;&#039;&#039;&#039;&#039; create a module file for the software in your &amp;lt;code&amp;gt;modules&amp;lt;/code&amp;gt; directory!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For full details, read the &amp;lt;code&amp;gt;README&amp;lt;/code&amp;gt; placed in your home directory. It&#039;s also available in the [https://gitlab.umiacs.umd.edu/cbcb/cbcb-sw/blob/master/templates/user_readme.md  cbcb-sw Gitlab repository].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Setup for non-interactive shells ==&lt;br /&gt;
&lt;br /&gt;
Modules are already configured for interactive shells, but to use modules with non-interactive shells, add the following to your ~/.bashrc:&lt;br /&gt;
 . /usr/share/Modules/init/bash&lt;br /&gt;
 . /etc/profile.d/ummodules.sh&lt;br /&gt;
&lt;br /&gt;
For more information, see the [https://wiki.umiacs.umd.edu/umiacs/index.php/Modules UMIACS wiki].&lt;br /&gt;
&lt;br /&gt;
== GNU Modules Cheatsheet ==&lt;br /&gt;
&lt;br /&gt;
Ask for help:&lt;br /&gt;
 module --help&lt;br /&gt;
&lt;br /&gt;
List available modules:&lt;br /&gt;
 module avail&lt;br /&gt;
&lt;br /&gt;
Add a module to your environment:&lt;br /&gt;
 module add blast&lt;br /&gt;
&lt;br /&gt;
List loaded modules:&lt;br /&gt;
 module list&lt;br /&gt;
&lt;br /&gt;
Remove a module from your environment:&lt;br /&gt;
 module rm blast&lt;br /&gt;
&lt;br /&gt;
Remove all modules from your environment:&lt;br /&gt;
 module purge&lt;br /&gt;
&lt;br /&gt;
Add a path to search for available modules:&lt;br /&gt;
 module use /cbcb/sw/RedHat-7-x86_64/users/lmendelo/modules&lt;br /&gt;
&lt;br /&gt;
See what changes a module makes to your environment:&lt;br /&gt;
 module show Python2/common/2.7.9&lt;br /&gt;
&lt;br /&gt;
== Contact ==&lt;br /&gt;
&lt;br /&gt;
Brought to you by:&lt;br /&gt;
&lt;br /&gt;
* [mailto:abelew@umiacs.umd.edu Trey Abelew]&lt;br /&gt;
* [mailto:keith@umiacs.umd.edu Keith Hughitt]&lt;br /&gt;
* [mailto:lmendelo@umiacs.umd.edu Lee Mendelowitz]&lt;br /&gt;
&lt;br /&gt;
== See Also ==&lt;br /&gt;
* [https://wiki.umiacs.umd.edu/umiacs/index.php/Modules UMIACS wiki]&lt;br /&gt;
* [https://gitlab.umiacs.umd.edu/cbcb/cbcb-sw Repository on GitLab]&lt;br /&gt;
* [https://docs.google.com/presentation/d/1UgKtnjcqHlpLZU79hGXfkgvNtse-ksMQ_gJMFCVLKRw/edit?usp=sharing CBCB Software slides on Google Drive]&lt;/div&gt;</summary>
		<author><name>Lmendelo</name></author>
	</entry>
	<entry>
		<id>https://wiki.umiacs.umd.edu/cbcb/index.php?title=CBCB_Software_Modules&amp;diff=9001</id>
		<title>CBCB Software Modules</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/cbcb/index.php?title=CBCB_Software_Modules&amp;diff=9001"/>
		<updated>2015-03-03T04:53:00Z</updated>

		<summary type="html">&lt;p&gt;Lmendelo: /* See Also */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Starting in the Spring of 2015, communal CBCB Bioinformatics Software has been installed using GNU Modules.&lt;br /&gt;
&lt;br /&gt;
== Common Modules ==&lt;br /&gt;
&lt;br /&gt;
CBCB Software modules are already configured for interactive shells on Red Hat 7 machines - no additional setup is required. The module files are installed in the following location:&lt;br /&gt;
 /cbcb/sw/RedHat-7-x86_64/common/modules/release/latest&lt;br /&gt;
&lt;br /&gt;
To see see what modules are available:&lt;br /&gt;
 $ module avail&lt;br /&gt;
&lt;br /&gt;
To add a module to your environment, use &amp;lt;code&amp;gt;module add&amp;lt;/code&amp;gt;:&lt;br /&gt;
 $ module add samtools/0.1.19&lt;br /&gt;
&lt;br /&gt;
Note that you can also specify the software name without the version:&lt;br /&gt;
 $ module add samtools&lt;br /&gt;
&lt;br /&gt;
Now samtools has been added to your environment:&lt;br /&gt;
 $ which samtools&lt;br /&gt;
 /cbcb/sw/RedHat-7-x86_64/common/local/samtools/0.1.19/bin/samtools&lt;br /&gt;
&lt;br /&gt;
== Personal Modules ==&lt;br /&gt;
&lt;br /&gt;
We have created some scripts to assist you with installing software and modules to your personal directory in &amp;lt;code&amp;gt;/cbcb/sw.&amp;lt;/code&amp;gt;. We recommend that you use these scripts because this will help us share installed software among other CBCB users.&lt;br /&gt;
&lt;br /&gt;
Run this initialization script to set up your directory structure:&lt;br /&gt;
 $ /cbcb/sw/RedHat-7-x86_64/common/scripts/init_cbcb_sw_user.sh&lt;br /&gt;
&lt;br /&gt;
This will create a directory for you:&lt;br /&gt;
 $ tree /cbcb/sw/RedHat-7-x86_64/users/&amp;lt;username&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
/cbcb/sw/RedHat-7-x86_64/users/&amp;lt;username&amp;gt;&lt;br /&gt;
├── local&lt;br /&gt;
├── modules&lt;br /&gt;
│   └── &amp;lt;username&amp;gt;&lt;br /&gt;
│       └── env&lt;br /&gt;
├── module_template&lt;br /&gt;
├── README&lt;br /&gt;
├── scripts&lt;br /&gt;
│   ├── copy_module_template.sh&lt;br /&gt;
│   ├── init_install_vars.sh&lt;br /&gt;
│   └── install_package.sh&lt;br /&gt;
└── src&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Use the &amp;lt;code&amp;gt;src&amp;lt;/code&amp;gt; directory for storing and compiling source code.&lt;br /&gt;
* Use the &amp;lt;code&amp;gt;local&amp;lt;/code&amp;gt; directory as the installation prefix.&lt;br /&gt;
* Use the &amp;lt;code&amp;gt;modules&amp;lt;/code&amp;gt; directory to store your modulefiles.&lt;br /&gt;
&lt;br /&gt;
See [[#Installing Software]] below.&lt;br /&gt;
&lt;br /&gt;
To make use of your personal module file directory, add the following to your &amp;lt;code&amp;gt;~/.bashrc&amp;lt;/code&amp;gt;:&lt;br /&gt;
 module use /cbcb/sw/RedHat-7-x86_64/users/&amp;lt;username&amp;gt;/modules&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Installing Software ===&lt;br /&gt;
&lt;br /&gt;
Use the &amp;lt;code&amp;gt;install_package.sh&amp;lt;/code&amp;gt; script to automatically compile software which uses &amp;lt;code&amp;gt;./configure; make; make install&amp;lt;/code&amp;gt;. The advantage to using this install script is that it will:&lt;br /&gt;
* use the standardized directory structure for personal software installation, and&lt;br /&gt;
* &#039;&#039;&#039;&#039;&#039;automatically&#039;&#039;&#039;&#039;&#039; create a module file for the software in your &amp;lt;code&amp;gt;modules&amp;lt;/code&amp;gt; directory!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For full details, read the &amp;lt;code&amp;gt;README&amp;lt;/code&amp;gt; placed in your home directory. It&#039;s also available in the [https://gitlab.umiacs.umd.edu/cbcb/cbcb-sw/blob/master/templates/user_readme.md  cbcb-sw Gitlab repository].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Setup for non-interactive shells ==&lt;br /&gt;
&lt;br /&gt;
Modules are already configured for interactive shells, but to use modules with non-interactive shells, add the following to your ~/.bashrc:&lt;br /&gt;
 . /usr/share/Modules/init/bash&lt;br /&gt;
 . /etc/profile.d/ummodules.sh&lt;br /&gt;
&lt;br /&gt;
For more information, see the [https://wiki.umiacs.umd.edu/umiacs/index.php/Modules UMIACS wiki].&lt;br /&gt;
&lt;br /&gt;
== GNU Modules Cheatsheet ==&lt;br /&gt;
&lt;br /&gt;
Ask for help:&lt;br /&gt;
 module --help&lt;br /&gt;
&lt;br /&gt;
List available modules:&lt;br /&gt;
 module avail&lt;br /&gt;
&lt;br /&gt;
Add a module to your environment:&lt;br /&gt;
 module add blast&lt;br /&gt;
&lt;br /&gt;
List loaded modules:&lt;br /&gt;
 module list&lt;br /&gt;
&lt;br /&gt;
Remove a module from your environment:&lt;br /&gt;
 module rm blast&lt;br /&gt;
&lt;br /&gt;
Remove all modules from your environment:&lt;br /&gt;
 module purge&lt;br /&gt;
&lt;br /&gt;
Add a path to search for available modules:&lt;br /&gt;
 module use /cbcb/sw/RedHat-7-x86_64/users/lmendelo/modules&lt;br /&gt;
&lt;br /&gt;
See what changes a module makes to your environment:&lt;br /&gt;
 module show Python2/common/2.7.9&lt;br /&gt;
&lt;br /&gt;
== Contact ==&lt;br /&gt;
&lt;br /&gt;
Brought to you by:&lt;br /&gt;
&lt;br /&gt;
* [mailto:abelew@umiacs.umd.edu Trey Abelew]&lt;br /&gt;
* [mailto:keith@umiacs.umd.edu Keith Hughitt]&lt;br /&gt;
* [mailto:lmendelo@umiacs.umd.edu Lee Mendelowitz]&lt;br /&gt;
&lt;br /&gt;
== See Also ==&lt;br /&gt;
* [https://wiki.umiacs.umd.edu/umiacs/index.php/Modules UMIACS wiki]&lt;br /&gt;
* [https://gitlab.umiacs.umd.edu/cbcb/cbcb-sw /Repository on GitLab]&lt;br /&gt;
* [https://docs.google.com/presentation/d/1UgKtnjcqHlpLZU79hGXfkgvNtse-ksMQ_gJMFCVLKRw/edit?usp=sharing CBCB Software slides on Google Drive]&lt;/div&gt;</summary>
		<author><name>Lmendelo</name></author>
	</entry>
	<entry>
		<id>https://wiki.umiacs.umd.edu/cbcb/index.php?title=CBCB_Software_Modules&amp;diff=9000</id>
		<title>CBCB Software Modules</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/cbcb/index.php?title=CBCB_Software_Modules&amp;diff=9000"/>
		<updated>2015-03-03T04:52:12Z</updated>

		<summary type="html">&lt;p&gt;Lmendelo: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Starting in the Spring of 2015, communal CBCB Bioinformatics Software has been installed using GNU Modules.&lt;br /&gt;
&lt;br /&gt;
== Common Modules ==&lt;br /&gt;
&lt;br /&gt;
CBCB Software modules are already configured for interactive shells on Red Hat 7 machines - no additional setup is required. The module files are installed in the following location:&lt;br /&gt;
 /cbcb/sw/RedHat-7-x86_64/common/modules/release/latest&lt;br /&gt;
&lt;br /&gt;
To see see what modules are available:&lt;br /&gt;
 $ module avail&lt;br /&gt;
&lt;br /&gt;
To add a module to your environment, use &amp;lt;code&amp;gt;module add&amp;lt;/code&amp;gt;:&lt;br /&gt;
 $ module add samtools/0.1.19&lt;br /&gt;
&lt;br /&gt;
Note that you can also specify the software name without the version:&lt;br /&gt;
 $ module add samtools&lt;br /&gt;
&lt;br /&gt;
Now samtools has been added to your environment:&lt;br /&gt;
 $ which samtools&lt;br /&gt;
 /cbcb/sw/RedHat-7-x86_64/common/local/samtools/0.1.19/bin/samtools&lt;br /&gt;
&lt;br /&gt;
== Personal Modules ==&lt;br /&gt;
&lt;br /&gt;
We have created some scripts to assist you with installing software and modules to your personal directory in &amp;lt;code&amp;gt;/cbcb/sw.&amp;lt;/code&amp;gt;. We recommend that you use these scripts because this will help us share installed software among other CBCB users.&lt;br /&gt;
&lt;br /&gt;
Run this initialization script to set up your directory structure:&lt;br /&gt;
 $ /cbcb/sw/RedHat-7-x86_64/common/scripts/init_cbcb_sw_user.sh&lt;br /&gt;
&lt;br /&gt;
This will create a directory for you:&lt;br /&gt;
 $ tree /cbcb/sw/RedHat-7-x86_64/users/&amp;lt;username&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
/cbcb/sw/RedHat-7-x86_64/users/&amp;lt;username&amp;gt;&lt;br /&gt;
├── local&lt;br /&gt;
├── modules&lt;br /&gt;
│   └── &amp;lt;username&amp;gt;&lt;br /&gt;
│       └── env&lt;br /&gt;
├── module_template&lt;br /&gt;
├── README&lt;br /&gt;
├── scripts&lt;br /&gt;
│   ├── copy_module_template.sh&lt;br /&gt;
│   ├── init_install_vars.sh&lt;br /&gt;
│   └── install_package.sh&lt;br /&gt;
└── src&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Use the &amp;lt;code&amp;gt;src&amp;lt;/code&amp;gt; directory for storing and compiling source code.&lt;br /&gt;
* Use the &amp;lt;code&amp;gt;local&amp;lt;/code&amp;gt; directory as the installation prefix.&lt;br /&gt;
* Use the &amp;lt;code&amp;gt;modules&amp;lt;/code&amp;gt; directory to store your modulefiles.&lt;br /&gt;
&lt;br /&gt;
See [[#Installing Software]] below.&lt;br /&gt;
&lt;br /&gt;
To make use of your personal module file directory, add the following to your &amp;lt;code&amp;gt;~/.bashrc&amp;lt;/code&amp;gt;:&lt;br /&gt;
 module use /cbcb/sw/RedHat-7-x86_64/users/&amp;lt;username&amp;gt;/modules&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Installing Software ===&lt;br /&gt;
&lt;br /&gt;
Use the &amp;lt;code&amp;gt;install_package.sh&amp;lt;/code&amp;gt; script to automatically compile software which uses &amp;lt;code&amp;gt;./configure; make; make install&amp;lt;/code&amp;gt;. The advantage to using this install script is that it will:&lt;br /&gt;
* use the standardized directory structure for personal software installation, and&lt;br /&gt;
* &#039;&#039;&#039;&#039;&#039;automatically&#039;&#039;&#039;&#039;&#039; create a module file for the software in your &amp;lt;code&amp;gt;modules&amp;lt;/code&amp;gt; directory!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For full details, read the &amp;lt;code&amp;gt;README&amp;lt;/code&amp;gt; placed in your home directory. It&#039;s also available in the [https://gitlab.umiacs.umd.edu/cbcb/cbcb-sw/blob/master/templates/user_readme.md  cbcb-sw Gitlab repository].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Setup for non-interactive shells ==&lt;br /&gt;
&lt;br /&gt;
Modules are already configured for interactive shells, but to use modules with non-interactive shells, add the following to your ~/.bashrc:&lt;br /&gt;
 . /usr/share/Modules/init/bash&lt;br /&gt;
 . /etc/profile.d/ummodules.sh&lt;br /&gt;
&lt;br /&gt;
For more information, see the [https://wiki.umiacs.umd.edu/umiacs/index.php/Modules UMIACS wiki].&lt;br /&gt;
&lt;br /&gt;
== GNU Modules Cheatsheet ==&lt;br /&gt;
&lt;br /&gt;
Ask for help:&lt;br /&gt;
 module --help&lt;br /&gt;
&lt;br /&gt;
List available modules:&lt;br /&gt;
 module avail&lt;br /&gt;
&lt;br /&gt;
Add a module to your environment:&lt;br /&gt;
 module add blast&lt;br /&gt;
&lt;br /&gt;
List loaded modules:&lt;br /&gt;
 module list&lt;br /&gt;
&lt;br /&gt;
Remove a module from your environment:&lt;br /&gt;
 module rm blast&lt;br /&gt;
&lt;br /&gt;
Remove all modules from your environment:&lt;br /&gt;
 module purge&lt;br /&gt;
&lt;br /&gt;
Add a path to search for available modules:&lt;br /&gt;
 module use /cbcb/sw/RedHat-7-x86_64/users/lmendelo/modules&lt;br /&gt;
&lt;br /&gt;
See what changes a module makes to your environment:&lt;br /&gt;
 module show Python2/common/2.7.9&lt;br /&gt;
&lt;br /&gt;
== Contact ==&lt;br /&gt;
&lt;br /&gt;
Brought to you by:&lt;br /&gt;
&lt;br /&gt;
* [mailto:abelew@umiacs.umd.edu Trey Abelew]&lt;br /&gt;
* [mailto:keith@umiacs.umd.edu Keith Hughitt]&lt;br /&gt;
* [mailto:lmendelo@umiacs.umd.edu Lee Mendelowitz]&lt;br /&gt;
&lt;br /&gt;
== See Also ==&lt;br /&gt;
* [https://wiki.umiacs.umd.edu/umiacs/index.php/Modules UMIACS wiki]&lt;br /&gt;
* [https://gitlab.umiacs.umd.edu/cbcb/cbcb-sw Project on GitLab]&lt;br /&gt;
* [https://docs.google.com/presentation/d/1UgKtnjcqHlpLZU79hGXfkgvNtse-ksMQ_gJMFCVLKRw/edit?usp=sharing Slides on Google Drive]&lt;/div&gt;</summary>
		<author><name>Lmendelo</name></author>
	</entry>
	<entry>
		<id>https://wiki.umiacs.umd.edu/cbcb/index.php?title=CBCB_Software_Modules&amp;diff=8999</id>
		<title>CBCB Software Modules</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/cbcb/index.php?title=CBCB_Software_Modules&amp;diff=8999"/>
		<updated>2015-03-03T04:51:24Z</updated>

		<summary type="html">&lt;p&gt;Lmendelo: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Starting in the Spring of 2015, communal CBCB Bioinformatics Software has been installed using GNU Modules.&lt;br /&gt;
&lt;br /&gt;
== Common Modules ==&lt;br /&gt;
&lt;br /&gt;
CBCB Software modules are already configured for interactive shells on Red Hat 7 machines - no additional setup is required. The module files are installed in the following location:&lt;br /&gt;
 /cbcb/sw/RedHat-7-x86_64/common/modules/release/latest&lt;br /&gt;
&lt;br /&gt;
To see see what modules are available:&lt;br /&gt;
 $ module avail&lt;br /&gt;
&lt;br /&gt;
To add a module to your environment, use &amp;lt;code&amp;gt;module add&amp;lt;/code&amp;gt;:&lt;br /&gt;
 $ module add samtools/0.1.19&lt;br /&gt;
&lt;br /&gt;
Note that you can also specify the software name without the version:&lt;br /&gt;
 $ module add samtools&lt;br /&gt;
&lt;br /&gt;
Now samtools has been added to your environment:&lt;br /&gt;
 $ which samtools&lt;br /&gt;
 /cbcb/sw/RedHat-7-x86_64/common/local/samtools/0.1.19/bin/samtools&lt;br /&gt;
&lt;br /&gt;
== Personal Modules ==&lt;br /&gt;
&lt;br /&gt;
We have created some scripts to assist you with installing software and modules to your personal directory in &amp;lt;code&amp;gt;/cbcb/sw.&amp;lt;/code&amp;gt;. We recommend that you use these scripts because this will help us share installed software among other CBCB users.&lt;br /&gt;
&lt;br /&gt;
Run this initialization script to set up your directory structure:&lt;br /&gt;
 $ /cbcb/sw/RedHat-7-x86_64/common/scripts/init_cbcb_sw_user.sh&lt;br /&gt;
&lt;br /&gt;
This will create a directory for you:&lt;br /&gt;
 $ tree /cbcb/sw/RedHat-7-x86_64/users/&amp;lt;username&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
/cbcb/sw/RedHat-7-x86_64/users/&amp;lt;username&amp;gt;&lt;br /&gt;
├── local&lt;br /&gt;
├── modules&lt;br /&gt;
│   └── &amp;lt;username&amp;gt;&lt;br /&gt;
│       └── env&lt;br /&gt;
├── module_template&lt;br /&gt;
├── README&lt;br /&gt;
├── scripts&lt;br /&gt;
│   ├── copy_module_template.sh&lt;br /&gt;
│   ├── init_install_vars.sh&lt;br /&gt;
│   └── install_package.sh&lt;br /&gt;
└── src&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Use the &amp;lt;code&amp;gt;src&amp;lt;/code&amp;gt; directory for storing and compiling source code.&lt;br /&gt;
* Use the &amp;lt;code&amp;gt;local&amp;lt;/code&amp;gt; directory as the installation prefix.&lt;br /&gt;
* Use the &amp;lt;code&amp;gt;modules&amp;lt;/code&amp;gt; directory to store your modulefiles.&lt;br /&gt;
&lt;br /&gt;
See [[#Installing Software]] below.&lt;br /&gt;
&lt;br /&gt;
To make use of your personal module file directory, add the following to your &amp;lt;code&amp;gt;~/.bashrc&amp;lt;/code&amp;gt;:&lt;br /&gt;
 module use /cbcb/sw/RedHat-7-x86_64/users/&amp;lt;username&amp;gt;/modules&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Installing Software ===&lt;br /&gt;
&lt;br /&gt;
Use the &amp;lt;code&amp;gt;install_package.sh&amp;lt;/code&amp;gt; script to automatically compile software which uses &amp;lt;code&amp;gt;./configure; make; make install&amp;lt;/code&amp;gt;. The advantage to using this install script is that it will:&lt;br /&gt;
* use the standardized directory structure for personal software installation, and&lt;br /&gt;
* &#039;&#039;&#039;&#039;&#039;automatically&#039;&#039;&#039;&#039;&#039; create a module file for the software in your &amp;lt;code&amp;gt;modules&amp;lt;/code&amp;gt; directory!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For full details, read the &amp;lt;code&amp;gt;README&amp;lt;/code&amp;gt; placed in your home directory. It&#039;s also available in the [https://gitlab.umiacs.umd.edu/cbcb/cbcb-sw/blob/master/templates/user_readme.md  cbcb-sw Gitlab repository].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Setup for non-interactive shells ==&lt;br /&gt;
&lt;br /&gt;
Modules are already configured for interactive shells, but to use modules with non-interactive shells, add the following to your ~/.bashrc:&lt;br /&gt;
 . /usr/share/Modules/init/bash&lt;br /&gt;
 . /etc/profile.d/ummodules.sh&lt;br /&gt;
&lt;br /&gt;
For more information, see the [https://wiki.umiacs.umd.edu/umiacs/index.php/Modules UMIACS wiki].&lt;br /&gt;
&lt;br /&gt;
== GNU Modules Cheatsheet ==&lt;br /&gt;
&lt;br /&gt;
Ask for help:&lt;br /&gt;
 module --help&lt;br /&gt;
&lt;br /&gt;
List available modules:&lt;br /&gt;
 module avail&lt;br /&gt;
&lt;br /&gt;
Add a module to your environment:&lt;br /&gt;
 module add blast&lt;br /&gt;
&lt;br /&gt;
List loaded modules:&lt;br /&gt;
 module list&lt;br /&gt;
&lt;br /&gt;
Remove a module from your environment:&lt;br /&gt;
 module rm blast&lt;br /&gt;
&lt;br /&gt;
Remove all modules from your environment:&lt;br /&gt;
 module purge&lt;br /&gt;
&lt;br /&gt;
Add a path to search for available modules:&lt;br /&gt;
 module use /cbcb/sw/RedHat-7-x86_64/users/lmendelo/modules&lt;br /&gt;
&lt;br /&gt;
See what changes a module makes to your environment:&lt;br /&gt;
 module show Python2/common/2.7.9&lt;br /&gt;
&lt;br /&gt;
== Contact ==&lt;br /&gt;
&lt;br /&gt;
Brought to you by:&lt;br /&gt;
&lt;br /&gt;
* [mailto:abelew@umiacs.umd.edu Trey Abelew]&lt;br /&gt;
* [mailto:keith@umiacs.umd.edu Keith Hughitt]&lt;br /&gt;
* [mailto:lmendelo@umiacs.umd.edu Lee Mendelowitz]&lt;br /&gt;
&lt;br /&gt;
== See Also ==&lt;br /&gt;
[https://wiki.umiacs.umd.edu/umiacs/index.php/Modules UMIACS wiki]&lt;br /&gt;
[https://gitlab.umiacs.umd.edu/cbcb/cbcb-sw Project on GitLab]&lt;br /&gt;
[https://docs.google.com/presentation/d/1UgKtnjcqHlpLZU79hGXfkgvNtse-ksMQ_gJMFCVLKRw/edit?usp=sharing Slides on Google Drive]&lt;/div&gt;</summary>
		<author><name>Lmendelo</name></author>
	</entry>
	<entry>
		<id>https://wiki.umiacs.umd.edu/cbcb/index.php?title=CBCB_Software_Modules&amp;diff=8998</id>
		<title>CBCB Software Modules</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/cbcb/index.php?title=CBCB_Software_Modules&amp;diff=8998"/>
		<updated>2015-03-03T04:46:57Z</updated>

		<summary type="html">&lt;p&gt;Lmendelo: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Starting in the Spring of 2015, communal CBCB Bioinformatics Software has been installed using GNU Modules.&lt;br /&gt;
&lt;br /&gt;
== Common Modules ==&lt;br /&gt;
&lt;br /&gt;
CBCB Software modules are already configured for interactive shells on Red Hat 7 machines - no additional setup is required. The module files are installed in the following location:&lt;br /&gt;
 /cbcb/sw/RedHat-7-x86_64/common/modules/release/latest&lt;br /&gt;
&lt;br /&gt;
To see see what modules are available:&lt;br /&gt;
 $ module avail&lt;br /&gt;
&lt;br /&gt;
To add a module to your environment, use &amp;lt;code&amp;gt;module add&amp;lt;/code&amp;gt;:&lt;br /&gt;
 $ module add samtools/0.1.19&lt;br /&gt;
&lt;br /&gt;
Note that you can also specify the software name without the version:&lt;br /&gt;
 $ module add samtools&lt;br /&gt;
&lt;br /&gt;
Now samtools has been added to your environment:&lt;br /&gt;
 $ which samtools&lt;br /&gt;
 /cbcb/sw/RedHat-7-x86_64/common/local/samtools/0.1.19/bin/samtools&lt;br /&gt;
&lt;br /&gt;
== Personal Modules ==&lt;br /&gt;
&lt;br /&gt;
We have created some scripts to assist you with installing software and modules to your personal directory in &amp;lt;code&amp;gt;/cbcb/sw.&amp;lt;/code&amp;gt;. We recommend that you use these scripts because this will help us share installed software among other CBCB users.&lt;br /&gt;
&lt;br /&gt;
Run this initialization script to set up your directory structure:&lt;br /&gt;
 $ /cbcb/sw/RedHat-7-x86_64/common/scripts/init_cbcb_sw_user.sh&lt;br /&gt;
&lt;br /&gt;
This will create a directory for you:&lt;br /&gt;
 $ tree /cbcb/sw/RedHat-7-x86_64/users/&amp;lt;username&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
/cbcb/sw/RedHat-7-x86_64/users/&amp;lt;username&amp;gt;&lt;br /&gt;
├── local&lt;br /&gt;
├── modules&lt;br /&gt;
│   └── &amp;lt;username&amp;gt;&lt;br /&gt;
│       └── env&lt;br /&gt;
├── module_template&lt;br /&gt;
├── README&lt;br /&gt;
├── scripts&lt;br /&gt;
│   ├── copy_module_template.sh&lt;br /&gt;
│   ├── init_install_vars.sh&lt;br /&gt;
│   └── install_package.sh&lt;br /&gt;
└── src&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Use the &amp;lt;code&amp;gt;src&amp;lt;/code&amp;gt; directory for storing and compiling source code.&lt;br /&gt;
* Use the &amp;lt;code&amp;gt;local&amp;lt;/code&amp;gt; directory as the installation prefix.&lt;br /&gt;
* Use the &amp;lt;code&amp;gt;modules&amp;lt;/code&amp;gt; directory to store your modulefiles.&lt;br /&gt;
&lt;br /&gt;
See [[#Installing Software]] below.&lt;br /&gt;
&lt;br /&gt;
To make use of your personal module file directory, add the following to your &amp;lt;code&amp;gt;~/.bashrc&amp;lt;/code&amp;gt;:&lt;br /&gt;
 module use /cbcb/sw/RedHat-7-x86_64/users/&amp;lt;username&amp;gt;/modules&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Installing Software ===&lt;br /&gt;
&lt;br /&gt;
Use the &amp;lt;code&amp;gt;install_package.sh&amp;lt;/code&amp;gt; script to automatically compile software which uses &amp;lt;code&amp;gt;./configure; make; make install&amp;lt;/code&amp;gt;. The advantage to using this install script is that it will:&lt;br /&gt;
* use the standardized directory structure for personal software installation, and&lt;br /&gt;
* &#039;&#039;&#039;&#039;&#039;automatically&#039;&#039;&#039;&#039;&#039; create a module file for the software in your &amp;lt;code&amp;gt;modules&amp;lt;/code&amp;gt; directory!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For full details, read the &amp;lt;code&amp;gt;README&amp;lt;/code&amp;gt; placed in your home directory. It&#039;s also available in the [https://gitlab.umiacs.umd.edu/cbcb/cbcb-sw/blob/master/templates/user_readme.md  cbcb-sw Gitlab repository].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Setup for non-interactive shells ==&lt;br /&gt;
&lt;br /&gt;
Modules are already configured for interactive shells, but to use modules with non-interactive shells, add the following to your ~/.bashrc:&lt;br /&gt;
 . /usr/share/Modules/init/bash&lt;br /&gt;
 . /etc/profile.d/ummodules.sh&lt;br /&gt;
&lt;br /&gt;
For more information, see the [https://wiki.umiacs.umd.edu/umiacs/index.php/Modules UMIACS wiki].&lt;br /&gt;
&lt;br /&gt;
== GNU Modules Cheatsheet ==&lt;br /&gt;
&lt;br /&gt;
Ask for help:&lt;br /&gt;
 module --help&lt;br /&gt;
&lt;br /&gt;
List available modules:&lt;br /&gt;
 module avail&lt;br /&gt;
&lt;br /&gt;
Add a module to your environment:&lt;br /&gt;
 module add blast&lt;br /&gt;
&lt;br /&gt;
List loaded modules:&lt;br /&gt;
 module list&lt;br /&gt;
&lt;br /&gt;
Remove a module from your environment:&lt;br /&gt;
 module rm blast&lt;br /&gt;
&lt;br /&gt;
Remove all modules from your environment:&lt;br /&gt;
 module purge&lt;br /&gt;
&lt;br /&gt;
Add a path to search for available modules:&lt;br /&gt;
 module use /cbcb/sw/RedHat-7-x86_64/users/lmendelo/modules&lt;br /&gt;
&lt;br /&gt;
See what changes a module makes to your environment:&lt;br /&gt;
 module show Python2/common/2.7.9&lt;/div&gt;</summary>
		<author><name>Lmendelo</name></author>
	</entry>
	<entry>
		<id>https://wiki.umiacs.umd.edu/cbcb/index.php?title=CBCB_Software_Modules&amp;diff=8997</id>
		<title>CBCB Software Modules</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/cbcb/index.php?title=CBCB_Software_Modules&amp;diff=8997"/>
		<updated>2015-03-03T04:41:50Z</updated>

		<summary type="html">&lt;p&gt;Lmendelo: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Starting in the Spring of 2015, communal CBCB Software has been installed using GNU Modules.&lt;br /&gt;
&lt;br /&gt;
== Common Modules ==&lt;br /&gt;
&lt;br /&gt;
CBCB Software modules are already configured for interactive shells on Red Hat 7 machines - no additional setup is required. The module files are installed in the following location:&lt;br /&gt;
 /cbcb/sw/RedHat-7-x86_64/common/modules/release/latest&lt;br /&gt;
&lt;br /&gt;
To see see what modules are available:&lt;br /&gt;
 $ module avail&lt;br /&gt;
&lt;br /&gt;
To add a module to your environment, use &amp;lt;code&amp;gt;module add&amp;lt;/code&amp;gt;:&lt;br /&gt;
 $ module add samtools/0.1.19&lt;br /&gt;
&lt;br /&gt;
Note that you can also specify the software name without the version:&lt;br /&gt;
 $ module add samtools&lt;br /&gt;
&lt;br /&gt;
Now samtools has been added to your environment:&lt;br /&gt;
 $ which samtools&lt;br /&gt;
 /cbcb/sw/RedHat-7-x86_64/common/local/samtools/0.1.19/bin/samtools&lt;br /&gt;
&lt;br /&gt;
== Personal Modules ==&lt;br /&gt;
&lt;br /&gt;
We have created some scripts to assist you with installing software and modules to your personal directory in &amp;lt;code&amp;gt;/cbcb/sw.&amp;lt;/code&amp;gt;. We recommend that you use these scripts because this will help us share installed software among other CBCB users.&lt;br /&gt;
&lt;br /&gt;
Run this initialization script to set up your directory structure:&lt;br /&gt;
 $ /cbcb/sw/RedHat-7-x86_64/common/scripts/init_cbcb_sw_user.sh&lt;br /&gt;
&lt;br /&gt;
This will create a directory for you:&lt;br /&gt;
 $ tree /cbcb/sw/RedHat-7-x86_64/users/&amp;lt;username&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
/cbcb/sw/RedHat-7-x86_64/users/&amp;lt;username&amp;gt;&lt;br /&gt;
├── local&lt;br /&gt;
├── modules&lt;br /&gt;
│   └── &amp;lt;username&amp;gt;&lt;br /&gt;
│       └── env&lt;br /&gt;
├── module_template&lt;br /&gt;
├── README&lt;br /&gt;
├── scripts&lt;br /&gt;
│   ├── copy_module_template.sh&lt;br /&gt;
│   ├── init_install_vars.sh&lt;br /&gt;
│   └── install_package.sh&lt;br /&gt;
└── src&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Use the &amp;lt;code&amp;gt;src&amp;lt;/code&amp;gt; directory for storing and compiling source code.&lt;br /&gt;
* Use the &amp;lt;code&amp;gt;local&amp;lt;/code&amp;gt; directory as the installation prefix.&lt;br /&gt;
* Use the &amp;lt;code&amp;gt;modules&amp;lt;/code&amp;gt; directory to store your modulefiles.&lt;br /&gt;
&lt;br /&gt;
See [[#Installing Software]] below.&lt;br /&gt;
&lt;br /&gt;
To make use of your personal module file directory, add the following to your &amp;lt;code&amp;gt;~/.bashrc&amp;lt;/code&amp;gt;:&lt;br /&gt;
 module use /cbcb/sw/RedHat-7-x86_64/users/&amp;lt;username&amp;gt;/modules&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Installing Software ===&lt;br /&gt;
&lt;br /&gt;
Use the &amp;lt;code&amp;gt;install_package.sh&amp;lt;/code&amp;gt; script to automatically compile software which uses &amp;lt;code&amp;gt;./configure; make; make install&amp;lt;/code&amp;gt;. The advantage to using this install script is that it will:&lt;br /&gt;
* use the standardized directory structure for personal software installation, and&lt;br /&gt;
* &#039;&#039;&#039;&#039;&#039;automatically&#039;&#039;&#039;&#039;&#039; create a module file for the software in your &amp;lt;code&amp;gt;modules&amp;lt;/code&amp;gt; directory!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For full details, read the &amp;lt;code&amp;gt;README&amp;lt;/code&amp;gt; placed in your home directory. It&#039;s also available in the [https://gitlab.umiacs.umd.edu/cbcb/cbcb-sw/blob/master/templates/user_readme.md  cbcb-sw Gitlab repository].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Setup for non-interactive shells ==&lt;br /&gt;
&lt;br /&gt;
Modules are already configured for interactive shells, but to use modules with non-interactive shells, add the following to your ~/.bashrc:&lt;br /&gt;
 . /usr/share/Modules/init/bash&lt;br /&gt;
 . /etc/profile.d/ummodules.sh&lt;br /&gt;
&lt;br /&gt;
For more information, see the [https://wiki.umiacs.umd.edu/umiacs/index.php/Modules UMIACS wiki].&lt;/div&gt;</summary>
		<author><name>Lmendelo</name></author>
	</entry>
	<entry>
		<id>https://wiki.umiacs.umd.edu/cbcb/index.php?title=CBCB_Software_Modules&amp;diff=8996</id>
		<title>CBCB Software Modules</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/cbcb/index.php?title=CBCB_Software_Modules&amp;diff=8996"/>
		<updated>2015-03-03T04:09:01Z</updated>

		<summary type="html">&lt;p&gt;Lmendelo: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Starting in the Spring of 2015, communal CBCB Software has been installed using GNU Modules.&lt;br /&gt;
&lt;br /&gt;
== Common Modules ==&lt;br /&gt;
&lt;br /&gt;
CBCB Software modules are already configured for interactive shells on Red Hat 7 machines - no additional setup is required. The module files are installed in the following location:&lt;br /&gt;
 /cbcb/sw/RedHat-7-x86_64/common/modules/release/latest&lt;br /&gt;
&lt;br /&gt;
To see see what modules are available:&lt;br /&gt;
 $ module avail&lt;br /&gt;
&lt;br /&gt;
To add a module to your environment, use &amp;lt;code&amp;gt;module add&amp;lt;/code&amp;gt;:&lt;br /&gt;
 $ module add samtools/0.1.19&lt;br /&gt;
&lt;br /&gt;
Note that you can also specify the software name without the version:&lt;br /&gt;
 $ module add samtools&lt;br /&gt;
&lt;br /&gt;
Now samtools has been added to your environment:&lt;br /&gt;
 $ which samtools&lt;br /&gt;
 /cbcb/sw/RedHat-7-x86_64/common/local/samtools/0.1.19/bin/samtools&lt;br /&gt;
&lt;br /&gt;
== Setup for non-interactive shells ==&lt;br /&gt;
&lt;br /&gt;
Modules are already configured for interactive shells, but to use modules with non-interactive shells, add the following to your ~/.bashrc:&lt;br /&gt;
 . /usr/share/Modules/init/bash&lt;br /&gt;
 . /etc/profile.d/ummodules.sh&lt;/div&gt;</summary>
		<author><name>Lmendelo</name></author>
	</entry>
	<entry>
		<id>https://wiki.umiacs.umd.edu/cbcb/index.php?title=Main_Page&amp;diff=8995</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/cbcb/index.php?title=Main_Page&amp;diff=8995"/>
		<updated>2015-03-03T03:57:25Z</updated>

		<summary type="html">&lt;p&gt;Lmendelo: /* Getting started */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== IMPORTANT (Read First) ==&lt;br /&gt;
The CBCB computational infrastructure is a shared resource and we all need to pitch in in order to make sure it works well for all of us.  Most importantly, we need to ensure that our disk space and computational resources are used responsibly.  The disk space, in particular, is a valuable commodity and thus it is important to pay attention to the following:&lt;br /&gt;
* There are three types of disk space available (a full list of volumes is available at [https://wiki.umiacs.umd.edu/cbcb-private/index.php/Storage CBCB Storage]) :&lt;br /&gt;
** Local harddrives (usually mounted as /scratch on the machines that have this resource).  These are not backed up, are quite fast (they live physically close to the processor), but can only be &#039;seen&#039; by the machine where they are mounted and, thus, require data staging in/out (which can take a while)&lt;br /&gt;
** Shared 3Par storage (/fs/szasmg*, /fs/szdata/*, etc.).  This is very fast and very expensive disk and thus a limited resource. Please only use this space to store data temporarily, while you are running some analyses on it.  As a rule of thumb, if a file or collection of files of any considerable size have lived on this space for more than 1-2 weeks, they should probably be moved to the attic space (see below)&lt;br /&gt;
** Attic storage (/fs/szattic*).  This is cheaper and ample, but slow and brittle storage.  Your data-sets should primarily live here.  Due to it&#039;s brittleness, the IT department do not recommend you run any analyses directly in this volume, rather you copy the files over to a local harddrive or the 3Par instead, and copy the results back when done.&lt;br /&gt;
* You should remove any temporary results you don&#039;t need in the long term as soon as you&#039;ve generated them, and compress all of the large files.  Bzip2 works better than gzip but either should dramatically improve the space requirements, especially for text files such as fasta or fastq.&lt;br /&gt;
* You should ensure that your files are owned by the cbcb group and that they have group write permissions for any file stored on the 3Par, especially for all those in /fs/szscratch.  This will allow your colleagues to remove files in case the disk runs out of space and you are, for example, on vacation (in which case you shouldn&#039;t have any major files sitting around on the 3Par).&lt;br /&gt;
&lt;br /&gt;
For more information on the CBCB resources see [[Getting Started in CBCB]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Seminars ==&lt;br /&gt;
* [http://www.cbcb.umd.edu/seminars Regular CBCB seminars (during academic year)] &amp;lt;br&amp;gt;&lt;br /&gt;
* [[Cbcb:Works-In-Progress]] - Works in progress seminar schedule (Summer 2008) &amp;lt;br&amp;gt;&lt;br /&gt;
* [[short_read_sequencing|Short read sequencing Meeting]] (Fridays at 3pm)&lt;br /&gt;
&lt;br /&gt;
== Projects ==&lt;br /&gt;
&lt;br /&gt;
* [[Project:Pop-Lab|Pop-Lab]]&lt;br /&gt;
* [[Project:Hcbravo-lab|HCBravo Lab]]&lt;br /&gt;
* [[Project:Cloud-Computing|Cloud Computing]]&lt;br /&gt;
* [[Project:SummerInternships|Summer Internship Projects]]&lt;br /&gt;
* [[Metagenomics Reading Group (Wed 2pm)]]&lt;br /&gt;
&lt;br /&gt;
== People ==&lt;br /&gt;
 &lt;br /&gt;
* [[User:ayres|Daniel Ayres]]&lt;br /&gt;
* [[User:pknut777|Adam Bazinet]] &lt;br /&gt;
* [[User:irina|Irina Astrovskaya]] &lt;br /&gt;
* [[User:jpaulson|Joseph Paulson]]  &lt;br /&gt;
* [[User:mpop|Mihai Pop]] &lt;br /&gt;
* [[User:nelsayed|Najib El-Sayed]]&lt;br /&gt;
&lt;br /&gt;
== Getting started ==&lt;br /&gt;
If you have just received a new umiacs account through CBCB, follow the instructions on this page to get the basic information you&#039;ll need to start working:&amp;lt;br&amp;gt;&lt;br /&gt;
*[[Getting Started in CBCB]]&lt;br /&gt;
*[[CBCB Software Modules]]&lt;br /&gt;
*[https://wiki.umiacs.umd.edu/cbcb-private/index.php/Storage CBCB Storage]&lt;br /&gt;
*[https://wiki.umiacs.umd.edu/cbcb-private/index.php/Compute CBCB Computers]&lt;br /&gt;
*[[Communal Software]]&lt;/div&gt;</summary>
		<author><name>Lmendelo</name></author>
	</entry>
	<entry>
		<id>https://wiki.umiacs.umd.edu/cbcb/index.php?title=CBCB_Software_Modules&amp;diff=8994</id>
		<title>CBCB Software Modules</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/cbcb/index.php?title=CBCB_Software_Modules&amp;diff=8994"/>
		<updated>2015-03-03T03:57:05Z</updated>

		<summary type="html">&lt;p&gt;Lmendelo: Created page with &amp;quot;Starting in the Spring of 2015, communal CBCB Software has been installed using GNU Modules.&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Starting in the Spring of 2015, communal CBCB Software has been installed using GNU Modules.&lt;/div&gt;</summary>
		<author><name>Lmendelo</name></author>
	</entry>
	<entry>
		<id>https://wiki.umiacs.umd.edu/cbcb/index.php?title=Getting_Started_in_CBCB&amp;diff=8993</id>
		<title>Getting Started in CBCB</title>
		<link rel="alternate" type="text/html" href="https://wiki.umiacs.umd.edu/cbcb/index.php?title=Getting_Started_in_CBCB&amp;diff=8993"/>
		<updated>2015-03-03T03:54:33Z</updated>

		<summary type="html">&lt;p&gt;Lmendelo: /* Configuring Your Home Directory and Shell */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Last update 9/11/13&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You may want to review the following:&lt;br /&gt;
&lt;br /&gt;
[[Media:CBCB-quick-guide.pdf]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Getting Building Access and Room Keys==&lt;br /&gt;
&lt;br /&gt;
CBCB is located on the 3rd floor of The Biomolecular Sciences Building identified on campus maps as Building #296.  The building is secure and access is gained by either using your UM ID card, guest card or entering the 3-digit code of the person you to visit at the call box on the right side of the front door.&lt;br /&gt;
&lt;br /&gt;
Contact the Center Coordinator, Christine Bogan, about gaining card access to the building.  She will need the following information:&lt;br /&gt;
*An notification email from your sponsor/adviser&lt;br /&gt;
*Your Name&lt;br /&gt;
*Your 9 Digit University ID number&lt;br /&gt;
*Your Contact email&lt;br /&gt;
&lt;br /&gt;
Along with your assigned space and phone numbers, the coordinator will send your information to UMIACS Coordinator Edna Walker who will contact campus security to add you into their system.  &#039;&#039;Note: clearance usually takes a number of days, so contact the coordinator as soon as possible.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
If you prefer not to send your information through email feel free to contact the coordinator in person.  &lt;br /&gt;
&lt;br /&gt;
You must get your key from the coordinator in person.&lt;br /&gt;
&lt;br /&gt;
Christine Bogan&amp;lt;br&amp;gt;&lt;br /&gt;
Room 3121&amp;lt;br&amp;gt;&lt;br /&gt;
Biomolecular Sciences Bldg #296&amp;lt;br&amp;gt;&lt;br /&gt;
301.405.5936&amp;lt;br&amp;gt;&lt;br /&gt;
cbogan[at]umd.edu&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Research In Progress Seminars==&lt;br /&gt;
&lt;br /&gt;
These seminars are held through the year.  For information go to [http://cbcb.umd.edu/node/18625 CBCB Research in Progress]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For a list of our Disk Storage and amount of available space left on each one, see [http://wiki.umiacs.umd.edu/cbcb-private/index.php/Storage wiki.umiacs.umd.edu/cbcb-private/index.php/Storage]&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Configuring Your Home Directory and Shell ==&lt;br /&gt;
&lt;br /&gt;
We import common settings files that set our path variables to include commonly shared software repositories.&lt;br /&gt;
&lt;br /&gt;
As a start, add the following line to the top of the file called &amp;quot;.bashrc&amp;quot; located in your home directory (/nfshomes/username/):&lt;br /&gt;
&lt;br /&gt;
 . /fs/sz-user-supported/share/dotfiles/bashrc.cbcb&lt;br /&gt;
&lt;br /&gt;
This will import the common bashrc.cbcb file into your own bashrc file every time you log in.&lt;br /&gt;
&lt;br /&gt;
Now add this line to your &amp;quot;.bash_profile&amp;quot; file, also located in your home directory:&lt;br /&gt;
&lt;br /&gt;
 . ~/.bashrc&lt;br /&gt;
&lt;br /&gt;
This will import your personal bashrc file every time you log in. Now you should have access to most of the locally installed software like &amp;quot;blastall&amp;quot; and &amp;quot;AMOS.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
If you want to add any addition commands to your bashrc file, such as setting your default text editor to &amp;quot;vim&amp;quot; or formatting the output of bash commands (eg. &amp;quot;ls&amp;quot;), add the appropriate commands after the imported common files as shown in this example:&lt;br /&gt;
&lt;br /&gt;
 . /fs/sz-user-supported/share/dotfiles/bashrc.cbcb&lt;br /&gt;
 &lt;br /&gt;
 alias vi=&#039;vim&#039;&lt;br /&gt;
&lt;br /&gt;
 alias ls=&#039;ls --color&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
If you decide you want to change the settings in the common bashrc.cbcb to better suit your personal needs, then please copy and paste its contents into your personal bashrc file. &#039;&#039;&#039;Do not modify the common bashrc.cbcb file as it will affect everyone&#039;s environment.&#039;&#039;&#039; Also check back periodically as people may add common paths for new software.&lt;br /&gt;
&lt;br /&gt;
To use CBCB Software Modules, see [[CBCB Software Modules]]&lt;br /&gt;
&lt;br /&gt;
If you have any other problems, contact staff [at] umiacs.umd.edu or your PI. &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
More resources can be found at [https://wiki.umiacs.umd.edu/umiacs/index.php/GettingStarted umiacs wiki]&lt;br /&gt;
&lt;br /&gt;
== Printing ==&lt;br /&gt;
Go to the umiacs wiki to find [https://wiki.umiacs.umd.edu/umiacs/index.php/Printing system-specific guides for printing], and be sure to [https://wiki.umiacs.umd.edu/umiacs/index.php/PrinterQueueNaming add &#039;nb&#039; to the end of your print queue] to avoid wasting paper printing banners.&lt;br /&gt;
&lt;br /&gt;
== Using the Wiki ==&lt;br /&gt;
* [http://en.wikipedia.org/wiki/Wikipedia:Cheatsheet Wiki Formatting Cheatsheet]&lt;br /&gt;
* [http://www.mediawiki.org/wiki/Help:Configuration_settings Configuration settings list]&lt;br /&gt;
* [http://www.mediawiki.org/wiki/Help:FAQ MediaWiki FAQ]&lt;br /&gt;
* [http://mail.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]&lt;br /&gt;
&lt;br /&gt;
== When You Travel ==&lt;br /&gt;
&lt;br /&gt;
[[Media:CBCB_travel_request_form_oct_2014.pdf‎]] form to fill out to obtain information for travel reimbursement&lt;br /&gt;
&lt;br /&gt;
[[Media:Travel_101_cbcb_revised_4-2013.pdf]] for more detailed travel info&lt;/div&gt;</summary>
		<author><name>Lmendelo</name></author>
	</entry>
</feed>