-
Notifications
You must be signed in to change notification settings - Fork 219
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ERROR: Failed to run the VEP annotator! #204
Comments
Thanks for reporting this. It looks like a VEP runtime error. It was either not installed fully or had an un-handled exception. Let me know if you are still having this issue. And please provide a sample VCF to help debug. |
I've had this error as well. I include VCF which caused this error as well as the error message and script in the attached .tar.gz |
I have same issue no matter I use conda vep or github vep when I test maf2maf
Return:
It is okay for vcf2maf. Any suggestion? Best, |
I got similar error when using VEP perl $(which vep) --species homo_sapiens --input_file /dev/stdin --format vcf --output_file $path_AnoVcf --stats_text /path/to/vep_stats.txt --cache --dir_cache /path/to/VEP_cache --cache_version 91 --offline --everything --vcf --vcf_info_field ANN --fasta /path/to/Homo_sapiens.GRCh38.dna_sm.primary_assembly.add_chr.fa -custom /path/to/custom.bed.gz,custom,bed,overlap,0 Can't call method "db" on an undefined value at /path/to/ensembl-vep-96.0-0/Bio/EnsEMBL/Funcgen/BindingMatrix.pm line 241, <ANONIO> line 128506. I solve this error by change --cache-version 91 to 96 |
Same issue. Can't call method "db" on an undefined value at /opt/vep/src/ensembl-vep/Bio/EnsEMBL/Funcgen/BindingMatrix.pm line 237, <ANONIO> line 119860. I'll try tweaking --cache-version, but my error isn't exactly like the error of @henry410213028 (line 241 vs line 237 in BindingMatrix.pm). Any updates/solutions? @ckandoth I should also note that I'm running 26 samples. 14 run fine, but the rest crash. The jobs are iteratively submitted in a bash script, so things should be pretty standardized between them. |
Hi, I got the same error. ERROR: Failed to run the VEP annotator! Is there any one fix this problem? |
Same here, VEP crashes on most of my samples. I checked the vcf line suggested from line xxxx and it looks fine.. |
Ok for me worked updating the cache folder. Perhaps it got somehow corrupted |
perl vcf2maf.pl --input-vcf /path/to/somaticvariants.vcf --output-maf /path/to/out.maf --tumor-id s_MC7562_tumor --normal-id s_MC7562_germline --vep-path /path/to/vep/94/ --vep-data /path/to/vep91/cache/files -tmp-dir /tmp/dir --ncbi-build GRCh38 --ref-fasta /path/to/ref/fastq/seqs_for_alignment_pipelines.ucsc_ids/GCA_000001405.15_GRCh38_no_alt_short_headers_nonACTG_to_N.fa --cache-version 91
STATUS: Running VEP and writing to: /output/path/somaticvariants.vep.vcf
Can't call method "db" on an undefined value at /research/bsi/tools/biotools/vep/94/Bio/EnsEMBL/Funcgen/BindingMatrix.pm line 237, <ANONIO> line 158856.
Died in forked process 83328
ERROR: Failed to run the VEP annotator! Command:
The text was updated successfully, but these errors were encountered: