ensembl-vep

• VEP (Variant Effect Predictor) predicts the functional effects of genomic variants.
• Haplosaurus uses phased genotype data to predict whole-transcript haplotype sequences.
• Variant Recoder translates between different variant encodings.

Table of contents

• Installation and requirements
• VEP
  • Usage
  • Differences to ensembl-tools version
• Haplosaurus
  • Usage
  • Output
  • Flags
  • Frequency data
• Variant Recoder
  • Usage

---

Installation and requirements

The VEP package requires Perl (>=5.10 recommended, tested on 5.10, 5.14, 5.18, 5.22) and the DBI package installed. The remaining dependencies can be installed using the included INSTALL.pl script. Basic instructions:

git clone https://github.com/Ensembl/ensembl-vep.git
cd ensembl-vep
perl INSTALL.pl

The installer may also be used to check for updates to this and co-dependent packages, simply re-run INSTALL.pl.

See documentation for full installation instructions.

Additional CPAN modules

The following modules are optional but most users will benefit from installing them. We recommend using cpanminus to install.

• DBD::mysql - required for database access (--database or --cache without --offline)
• Set::IntervalTree - required for Haplosaurus, also confers speed updates to VEP
• JSON - required for writing JSON output
• PerlIO::gzip - faster compressed file parsing
• Bio::DB::BigFile - required for reading custom annotation data from BigWig files

Docker

A docker image for VEP is available from DockerHub.

See documentation for the Docker installation instructions.

---

VEP

Usage

./vep -i input.vcf -o out.txt -offline

See documentation for full command line instructions.

Please report any bugs or issues by contacting Ensembl or creating a GitHub issue

Differences to ensembl-tools VEP

This ensembl-vep repo is a complete rewrite of the VEP code intended to make the software faster, more robust and more easily extensible. Almost all functionality of the ensembl-tools version has been replicated, with the command line flags remaining largely unchanged. A summary of changes follows:

• Tool name: For brevity and to distinguish the two versions, the new command line tool is named vep, with the version in ensembl-tools named variant_effect_predictor.pl.
• Speed: A typical individual human genome of 4 million variants can now be processed in around 30 minutes on a quad-core machine using under 1GB of RAM.
• Known/existing variants: The alleles of your input variant are now compared to any known variants when using --check_existing. Previously this would require you to enable this functionality manually with --check_alleles. The old functionality can be restored using --no_check_alleles.
• Allele frequencies: Allele frequencies are now reported for the input allele only e.g. as 0.023 instead of A:0.023,G:0.0005. To reflect this change, the allele frequency fields are now named e.g. AFR_AF instead of AFR_MAF. The command line flags reflect this also, so --gmaf is now --af and --maf_1kg is now --af_1kg. Using the old flags will produce a deprecation message.
• GFF and GTF files: GFF and GTF files may now be used directly as a source of transcript annotation in place of, or even alongside, a cache or database source. Previously this involved building a cache using gtf2vep, which is now redundant. The files must first be bgzipped and tabix-indexed, and a FASTA file containing genomic sequence is required:

grep -v "#" data.gff | sort -k1,1 -k4,4n -k5,5n -t$'\t' | bgzip -c > data.gff.gz
tabix -p gff data.gff.gz
./vep -i input.vcf -gff data.gff.gz -fasta genome.fa.gz

• VCF custom annotations: VCF files used as a source of custom annotation will now have allele-specific data added from INFO fields; previously the whole content of each requested KEY=VALUE pair was reported.
• New pick flags: New flags added to aid selecting amongst consequence output: --pick_allele_gene, --flag_pick_allele_gene
• Runtime status: vep produces no runtime progress messages.
• Deprecated:
  • GVF output: --gvf
  • HTML output: --html
  • format conversion: --convert
  • pileup input: --format pileup
  • MAF flags (replaced by AF flags): --gmaf (--af), --maf_1kg (--af_1kg), --maf_esp (--af_esp), --maf_exac (--af_exac)
  • known variant allele checking (on by default, use --no_check_alleles to restore old behaviour): --check_alleles
  • cache building flags (replaced by internal Ensembl pipeline): --build, --write_cache

---

Haplosaurus

haplo is a local tool implementation of the same functionality that powers the Ensembl transcript haplotypes view. It takes phased genotypes from a VCF and constructs a pair of haplotype sequences for each overlapped transcript; these sequences are also translated into predicted protein haplotype sequences. Each variant haplotype sequence is aligned and compared to the reference, and an HGVS-like name is constructed representing its differences to the reference.

This approach offers an advantage over VEP's analysis, which treats each input variant independently. By considering the combined change contributed by all the variant alleles across a transcript, the compound effects the variants may have are correctly accounted for.

haplo shares much of the same command line functionality with vep, and can use VEP caches, Ensembl databases, GFF and GTF files as sources of transcript data; all vep command line flags relating to this functionality work the same with haplo.

Usage

Input data must be a VCF containing phased genotype data for at least one individual; no other formats are currently supported.

When using a VEP cache as the source of transcript annotation, the first time you run haplo with a particular cache it will spend some time scanning transcript locations in the cache.

./haplo -i input.vcf -o out.txt -cache

Output

The default output format is a simple tab-delimited file reporting all observed non-reference haplotypes. It has the following fields:

1. Transcript stable ID
2. CDS haplotype name
3. Comma-separated list of flags for CDS haplotype
4. Protein haplotype name
5. Comma-separated list of flags for protein haplotype
6. Comma-separated list of frequency data for protein haplotype
7. Comma-separated list of contributing variants
8. Comma-separated list of sample:count that exhibit this haplotype

The altered haplotype sequences can be obtained by switching to JSON output using --json which will display them by default. Each transcript analysed is summarised as a JSON object written to one line of the output file.

The JSON output structure matches the format of the transcript haplotype REST endpoint.

You may exclude fields in the JSON from being exported with --dont_export field1,field2. This may be used, for example, to exclude the full haplotype sequence and aligned sequences from the output with --dont_export seq,aligned_sequences.

Note JSON output does not currently include side-loaded frequency data.

Flags

Haplotypes may be flagged with one or more of the following:

• indel: haplotype contains an insertion or deletion (indel) relative to the reference.
• frameshift: haplotype contains at least one indel that disrupts the reading frame of the transcript.
• resolved_frameshift: haplotype contains two or more indels whose combined effect restores the reading frame of the transcript.
• stop_changed: indicates either a STOP codon is gained (protein truncating variant, PTV) or the existing reference STOP codon is lost.
• deleterious_sift_or_polyphen: haplotype contains at least one single amino acid substitution event flagged as deleterious (SIFT) or probably damaging (PolyPhen2).

Frequency data

Haplotype frequencies may be loaded and assigned to observed haplotypes using --haplotype_frequencies [file]. The following files may be used:

• 1000 genomes frequencies (GRCh37): protein_haplotype_freqs_1KG_e85_GRCh37.txt.gz
• 1000 genomes frequencies (GRCh38): protein_haplotype_freqs_1KG_e85_GRCh38.txt.gz

Note these files are temporarily hosted on 3rd party servers and may be subject to change or removal while the software remains in the development phase.

bioperl-ext

haplo can make use of a fast compiled alignment algorithm from the bioperl-ext package; this can speed up analysis, particularly in longer transcripts where insertions and/or deletions are introduced. The bioperl-ext package is no longer maintained and requires some tweaking to install. The following instructions install the package in $HOME/perl5; edit PREFIX=[path] to change this. You may also need to edit the export command to point to the path created for the architecture on your machine.

git clone https://github.com/bioperl/bioperl-ext.git
cd bioperl-ext/Bio/Ext/Align/
perl -pi -e"s|(cd libs.+)CFLAGS=\\\'|\$1CFLAGS=\\\'-fPIC |" Makefile.PL
perl Makefile.PL PREFIX=~/perl5
make
make install
cd -
export PERL5LIB=${PERL5LIB}:${HOME}/perl5/lib/x86_64-linux-gnu/perl/5.22.1/

If successful the following should print OK:

perl -MBio::Tools::dpAlign -e"print qq{OK\n}"

---

Variant Recoder

variant_recoder is a tool for translating between different variant encodings. It accepts as input any format supported by VEP (VCF, variant ID, HGVS), with extensions to allow for parsing of potentially ambiguous HGVS notations. For each input variant, variant_recoder reports all possible encodings including variant IDs from all sources imported into the Ensembl database and HGVS (genomic, transcript and protein), reported on Ensembl, RefSeq and LRG sequences.

Usage

variant_recoder depends on database access for identifier lookup, and cannot be used in offline mode as per VEP. The output format is JSON and the JSON perl module is required.

./variant_recoder --id [input_data_string]
./variant_recoder -i [input_file] --species [species]

Output

Output is a JSON array of objects, one per input variant, with the following keys:

• input: input string
• id: variant identifiers
• hgvsg: HGVS genomic nomenclature
• hgvsc: HGVS transcript nomenclature
• hgvsp: HGVS protein nomenclature
• warnings: Warnings generated e.g. for invalid HGVS

Use --pretty to pre-format and indent JSON output.

Example output:

./variant_recoder --id "AGT:p.Met268Thr" --pretty
[
   {
      "input" : "AGT:p.Met268Thr",
      "id" : [
         "rs699",
         "CM920010"
      ],
      "hgvsg" : [
         "NC_000001.11:g.230710048A>G"
      ],
      "hgvsc" : [
         "ENST00000366667.4:c.803T>C",
         "NM_000029.3:c.803T>C"
      ],
      "hgvsp" : [
         "ENSP00000355627.4:p.Met268Thr",
         "NP_000020.1:p.Met268Thr"
      ],
      "warnings" : [
         "Possible invalid use of gene name 'AGT' as HGVS reference; AGT:p.Met268Thr may resolve to multiple genomic locations"
      ]
   }
]

Options

variant_recoder shares many of the same command line flags as VEP. Others are unique to variant_recoder.

• -id|--input_data [input_string]: a single variant as a string.
• -i|--input_file [input_file]: input file containing one or more variants, one per line. Mixed formats disallowed.
• --species: species to use (default: homo_sapiens).
• --grch37: use GRCh37 assembly instead of GRCh38.
• --genomes: set database parameters for Ensembl Genomes species.
• --pretty: write pre-formatted indented JSON.
• --fields [field1,field2]: limit output fields. Comma-separated list, one or more of: id, hgvsg, hgvsc, hgvsp.
• --host [db_host]: change database host from default ensembldb.ensembl.org (UK); geographic mirrors are useastdb.ensembl.org (US East Coast) and asiadb.ensembl.org (Asia). --user, --port and --pass may also be set.
• --pick, --per_gene, --pick_allele, --pick_allele_gene, --pick_order: set and customise transcript selection process, see VEP documentation