Difference between revisions of "Stacks"
Moskalenko (talk | contribs) |
Moskalenko (talk | contribs) |
||
| Line 34: | Line 34: | ||
To run stacks with database export: | To run stacks with database export: | ||
* Log into a test node and load the stacks module: | * Log into a test node and load the stacks module: | ||
| − | * Create a database with a name that | + | * Create a database with a name that starts with <code>"stacks_${USER}_" or "radtags_${USER}_" using the 'hpc_create_stacks_db' script |
| − | hpc_create_stacks_db | + | |
| + | For example: | ||
| + | hpc_create_stacks_db "stacks_${USER}_mytest1" | ||
| + | The $USER variable will be expaned to your username. This will help us determine who a database belongs to if there is an issue or when we're cleaning up the old databases. Make sure to use the double quotes. Of course, you can explicitly provide a database name like | ||
| + | hpc_create_stacks_db stacks_jdoe_project21 | ||
The script will produce an error and quit if the database already exists. | The script will produce an error and quit if the database already exists. | ||
| + | |||
| + | Use the <code>hpc_list_stacks_databases</code> command with or without a search keyword. If there is no keyword the command will list all stacks databases. If a search keyword is provided the command will list only databases containing that keyword in their name. | ||
| + | |||
| + | For example: | ||
| + | hpc_list_stacks_databases test | ||
* Log out of the test node. | * Log out of the test node. | ||
* Run 'denovo_map.pl' as usual via a batch job specifying the database name with "-B test1_radtags". | * Run 'denovo_map.pl' as usual via a batch job specifying the database name with "-B test1_radtags". | ||
Revision as of 15:56, 3 October 2014
Description
Stacks is a software pipeline for building loci out of a set of short-read sequenced samples. Stacks was developed for the purpose of building genetic maps from RAD-Tag Illumina sequence data, but can also be readily applied to population studies, and phylogeography.
Required Modules
Serial
- stacks
System Variables
- HPC_{{#uppercase:stacks}}_DIR - installation directory
Additional Information
The command line pipeline is available via the "stacks" module.
The web interface that can be used for visualizing genetic maps and correcting the analysis is being installed and tested as of Aug 21st, 2012.
To run stacks with database export:
- Log into a test node and load the stacks module:
- Create a database with a name that starts with
"stacks_${USER}_" or "radtags_${USER}_" using the 'hpc_create_stacks_db' script
For example:
hpc_create_stacks_db "stacks_${USER}_mytest1"
The $USER variable will be expaned to your username. This will help us determine who a database belongs to if there is an issue or when we're cleaning up the old databases. Make sure to use the double quotes. Of course, you can explicitly provide a database name like
hpc_create_stacks_db stacks_jdoe_project21
The script will produce an error and quit if the database already exists.
Use the hpc_list_stacks_databases command with or without a search keyword. If there is no keyword the command will list all stacks databases. If a search keyword is provided the command will list only databases containing that keyword in their name.
For example:
hpc_list_stacks_databases test
- Log out of the test node.
- Run 'denovo_map.pl' as usual via a batch job specifying the database name with "-B test1_radtags".
- Browse to stacks.hpc.ufl.edu and use your HPC credentials to log in and view the results. The exact URI is constructed as follows:
http://stacks.hpc.ufl.edu/stacks/index.php?db=DATABASE
Substitute your own database name for 'DATABASE' at the end of the URI. To see an example view - go to http://stacks.hpc.ufl.edu/index.php?db=tut_radtags for the output of a Stacks Tutorial.