Keep values from VCF file into Ensembl VEP annotation
1
1
Entering edit mode
4.0 years ago
brunobsouzaa ▴ 840

Hi everyone. Does anyone knows how to keep VCF fields QUAL and FILTER when using tab output format from Ensembl VEP? I could just use bcftools to extract those values into another file them use awk to match POS, REF and ALT values and them print those values into another column from my vep output but, I'm wondering if there's an easier way to do this! My vep script looks like this:

$VEP -i ${i}.vcf --assembly GRCh37 --format vcf -o ${i}.vep --tab --fields "$FIELDS" --sift p --polyphen p --ccds --hgvs --symbol --numbers --regulatory --canonical --protein --biotype --gene_phenotype --af_gnomad --max_af --pubmed --variant_class --hgvs  --fasta $REF --dir $VEP_CACHE --no_stats --use_given_ref --force_overwrite --offline --cache --refseq --flag_pick --fork 20 --verbose --plugin $PLUGINS --custom $CUSTOM

I've searched Ensembl VEP website but found nothing regarding this task.

Appreciate any help. Thanks!

SNP • 3.3k views
ADD COMMENT
3
Entering edit mode
3.7 years ago
DareDevil ★ 4.3k

The VEP TSV format can only keep in its own specified columns. If you want to maintain the data from your original input, get your output in VCF. It will add the VEP annotation to the INFO column, and keep all the stuff you already have there.

ADD COMMENT
1
Entering edit mode

Thanks Man... I've wroten a simple awk command for this task! Everything is working fine.

ADD REPLY
1
Entering edit mode

it would be great and helpful to others if you share your answer here.

ADD REPLY
0
Entering edit mode

In case you choose to output a vcf, it may be parsed with SnpSift ExtractFields (https://pcingola.github.io/SnpEff/ss_extractfields/) for the standard vcf fields and VEP Annotation Reporter (https://vatools.readthedocs.io/en/latest/vep_annotation_reporter.html) for the VEP-specific CSQ field

ADD REPLY

Login before adding your answer.

Traffic: 2631 users visited in the last hour
Help About
FAQ
Access RSS
API
Stats

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.

Powered by the version 2.3.6