VEP setup instructions

The online Variant Effect Predictor uses the same script as the offline version, with the limitation that you can't use VEP plugins with the web tool.

Installation and setup

1. Ensure that you have the core, variation and regulation databases set up for all the relevant species.
2. In the same directory that contains your other Ensembl code, clone the ensembl-vep repository, which contains the VEP script.
3. Download the VEP cache files from our FTP site and unzip them in your vep data directory (see below).
4. Download the human toplevel DNA FASTA files from our FTP site. Go to https://ftp.ensembl.org/pub/grch37/current/fasta/homo_sapiens/dna/ and look for Homo_sapiens.GRCh37.dna.toplevel.fa.gz. Unzip this file into the same subdirectories as the cache files.

   Your completed data structure should look something like this:

   `-- /usr/local/ensembl/tools_data/vep
         |-- homo_sapiens
           |-- 1
           |-- 10
               ... (lots more chromosome/seq region directories)
           |-- Homo_sapiens.GRCh37.dna.toplevel.fa
           |-- Homo_sapiens.GRCh37.dna.toplevel.fa.index
           |-- info.txt
           |-- KI270442.1
               ... (lots more chromosome/seq region directories)
   

5. In public-plugins/mirror/SiteDefs.pm, configure the location for your cache and FASTA files, e.g.

       $SiteDefs::ENSEMBL_VEP_CACHE_DIR  = '/usr/local/ensembl/tools_data/vep';
   

6. The VEP checks the genomic databases for available options, so the following parameters need configuring with the location of your database server:

     $SiteDefs::ENSEMBL_VEP_FILTER_SCRIPT_OPTIONS = {
       '-host'         => 'mysqlhost',
       '-port'         => '3337',
       '-user'         => 'mysqluser',
       '-pass'         => 'password'
     };
     $SiteDefs::ENSEMBL_VEP_SCRIPT_DEFAULT_OPTIONS = {
       '--host'        => 'mysqlhost',
       '--port'        => '3337',
       '--user'        => 'mysqluser',
       '--pass'        => 'password',
       '--fork'        => 4,
     };
   

7. You should now restart -r your webserver to pick up the configuration changes.