Difference between revisions of "VEP"
Jump to navigation
Jump to search
Moskalenko (talk | contribs) m (Text replacement - "#uppercase" to "uc") |
|||
| Line 22: | Line 22: | ||
<!--Modules--> | <!--Modules--> | ||
| − | == | + | ==Environment Modules== |
| − | + | Run <code>module spider {{#var:app}}</code> to find out what environment modules are available for this application. | |
| − | |||
| − | < | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
==System Variables== | ==System Variables== | ||
* HPC_{{uc:{{#var:app}}}}_DIR - installation directory | * HPC_{{uc:{{#var:app}}}}_DIR - installation directory | ||
| Line 77: | Line 67: | ||
<!--Turn the Table of Contents and Edit paragraph links ON/OFF--> | <!--Turn the Table of Contents and Edit paragraph links ON/OFF--> | ||
__NOTOC____NOEDITSECTION__ | __NOTOC____NOEDITSECTION__ | ||
| − | |||
| − | |||
Revision as of 20:02, 10 June 2022
Description
Use Variant Effect Predictor (VEP) to analyse your variation data locally. No limits, powerful, fast and extendable. VEP is the best way to get the most out of the Ensembl.
Environment Modules
Run module spider vep to find out what environment modules are available for this application.
System Variables
- HPC_VEP_DIR - installation directory
Citation
If you publish research that uses vep you have to cite it as follows:
McLaren et. al. (doi:10.1093/bioinformatics/btq330)