Running VEP on CREATE¶
Variant Effect Predictor (VEP) is a Ensembl provided tool and can be ran as a containerized application on CREATE HPC through Singularity.
Setting up your container¶
Take note
Singularity is only accessible from the compute nodes, to use VEP on the HPC, please either request an interactive session or submit the application as a batch job.
1 2 |
|
A Docker image is available for VEP, and this can be converted and used through Singularity:
1 |
|
This will create a new .sif container called: ensembl-vep_latest.sif
and can be called with instructions similar to the following:
1 |
|
Downloading and installing cache data¶
The following example, made applicable to CREATE HPC, is based on the corresponding FASTA for human GRCh38 outlined in the official Ensembl VEP documentation here.
Included in the image is the installer script that can be used to download and setup your required cache data, and before you action the download you must first setup a non-default HPC cache directory to avoid default storage issues, this requires the binding of your HPC directory to a Singularity bind variable so that HPC path is within the same context as your container and therefore in scope of your VEP application:
1 2 3 4 5 6 |
|
The required data will be installed to the container mounted directory: /opt/vep/.vep
, bound to example HPC path: /scratch/users/k1234567/vep-data
.
If you were to instead manually download the cache data, with reference to the Ensembl annotation sources, with available linux tools, such as: wget
or curl
, you will just need to make sure you direct and bind your Singularity container to the relevant path where your manual download is located.
To test your VEP container processes, the following examples are available:
1 2 3 4 |
|