Open kuaileshizuihao opened 2 months ago
Hi @kuaileshizuihao ,
Sorry to hear that you are facing issues. Can you please let us know if you are seeing these warnings even when you run VEP using the fasta file without the plugin? This may rule out the possibility of fasta index file being corrupted. Can you kindly provide us the input file (or test input from the file) in order to see if we can replicate the issue on our end?
Hi @kuaileshizuihao ,
Sorry to hear that you are facing issues. Can you please let us know if you are seeing these warnings even when you run VEP using the fasta file without the plugin? This may rule out the possibility of fasta index file being corrupted. Can you kindly provide us the input file (or test input from the file) in order to see if we can replicate the issue on our end?
Thank you for kindly offering help. This issue did not occur when I was not using the Downstream plugin. Here is the input I used for testing. Thanks! WesDemo.zip
Hi @kuaileshizuihao , Thank you for providing the file. We are able to replicate the issue on our end and are looking into it.
Hi @kuaileshizuihao , Thank you for providing the file. We are able to replicate the issue on our end and are looking into it.
Thank you very much!
Describe the issue
I encountered the same problem as shown in the figure when using the DownStream plugin (there is no such problem when using --hgvs). Following these three instructions, I updated BioPerl and re-downloaded the FASTA file, but it still did not solve the problem. I suspect that my vep did not index the FASTA file correctly, because I did not find the .index file, but I found the .fai file. I wonder if this is the reason why the error still occurs. It seems that I can use vep normally without dealing with this error. What impact will it have? Thank you for your help, thanks a lot.
System
Full VEP command line
Full error message