Closed weilinwu97 closed 9 months ago
Hi @weilinwu97,
Thank you for your interest in pVACtools and I apologize that you're running into errors with our software.
Can you please try upgrading to the latest version (4.0.4) and see if the error persists there? If the error still occurs under that version, can you please attach an example input VCF to this ticket to allow us to replicate this error on our end?
Kind regards, Susanna
Hi Susanna,
The same error presists with the latest docker version.
The input vcf is attached for you to replicate the issue. input.vcf.gz
Cheers, Weilin
Unfortunately, the attached VCF is not VEP-annotated. Can you please share the VEP-annotated VCF?
Sorry, here is the VEP version. input.vep.vcf.gz
thanks, Weilin
Hi @weilinwu97, unfortunately I'm unable to replicate this issue on my end. Would you be able to share your full output directory with me so I can compare what differences there might with the intermediate files that could possibly be causing this?
Hi Susanna,
There are a few more annotation steps after VEP in my pipeline. Here is the final vcf after all annotations input.vep.annotated.vcf.gz.
I ran this on CAVATICA which uses AWS cloud instances. Unfortunately I don't have access to the actual compute instance, so I can't share the output dir, I can only see the stderr which is attached in my first post.
Many thanks.
I also was not able to replicate this error with the second input VCF. My run finished successfully. I suspect that there was an error with one of the intermediate prediction files created by pVACtools. I suggest you rerun the affected samples from scratch to see if the issue persists for you. I'm sorry I'm unable to provide more help unless I can either replicate the issue or have access to these intermediate files to further investigate.
I tried to run this locally using the docker image. Unfortunately, I am using macOS with M1 chip and the tensorflow installed in the docker image was not happy about this. That being said, it did run from end to end WITHOUT issue using the non-neural-network prediction methods (PickPocket, SMM, etc). I re-tested this on the cloud and it worked fine as well, which made me suspect that the error must be coming from outputs from the neural-network prediction methods.
I need to find a way to run it in a linux env to test the neural-network prediction methods. At the mean time, I am happy to run using just the non-neural-network prediction methods.
You can close the ticket now. I will re-open this when I manage to replicate the behaviour locally as well. Thank you.
Installation Type
Docker
pVACtools Version / Docker Image
griffithlab/pvactools:4.0.1
Python Version
No response
Operating System
No response
Describe the bug
Encoutered this error while running pVACseq to predict neoepitope from VCFs. I am running a cohort analysis for 500-ish samples and this error came up for 10 samples.
How to reproduce this bug
Input files
No response
Log output
see description
Output files
No response