AlphaMissense Plugin VEP
I've installed alphamissense plugin in VEP, but I can't use it. I've downloaded the requested files and launch the tabix command before use it.
Then I've launched the command but I got this error:
WARNING: Failed to instantiate plugin AlphaMissense:
ERROR: No file specified
Try using 'file=path/to/file.tsv.gz'
The command is:
./vep -i Sample1.hard-filtered.vcf.gz -o Test.txt --cache /home/aghiroldi/ensembl-vep/ --plugin Blosum62 --plugin AlphaMissense,AlphaMissense_hg19.tsv.gz.tbi --everything --offline --assembly GRCh37 --tab
Probably I'm wronging in indicating the file.
Thanks
0 answers
No answers yet.
Log in to answer this question.
More posts like this
-
VEP won't show symbols for all variants; SnpEff will, but won't for others
written by mary.v.volkova •
-
Subset VCF to exon region but still get intron_variant annotation
written by tomas4482 •
-
AlphaMissense_hg38.tsv.gz tabix indexing issue VEP
written by Katsiaryna •
-
VEP/ CADD error - ERROR: Assembly is GRCh38 but CADD file does not contain GRCh38 in header.
written by K.patel5 •
-
Issue running VEP with GTF due to Tabix error
written by jensen.416 •
-
Failed to instantiate plugin dbNSFP in VEP
written by yysu •
-
Keep values from VCF file into Ensembl VEP annotation
written by brunobsouzaa
-
DBD::SQLite::db prepare failed: no such table: phylocsf_summary
written by nikitavlassenko
-
Running VEP without --cache
written by nikitavlassenko
-
VCF to MAF conversion for ABSOLUTE
written by sgujja •
EDIT: See GenoMax's comment below, you need what they specify.
You're specifying the index file name. Try specifying the full path to the tsv.gz file instead like so:
--plugin AlphaMissense,/absolute/path/to/AlphaMissense_hg19.tsv.gzLooks like the software actually wants you to put the word
filein the command.Thank you, I missed that. I went with VEP's regular plugin specification format.
surprisingly I have problems with REVEL plugin with parsing "file" word in this context, when I remove it and simply type the path it works. I think it is prob related with VEP version?
That's a good catch - definitely worth a bug report.