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
vcf corrupt #911
Comments
Daryl;
If we can get more of a sense of what exactly is going wrong we can try to look for it or work around the issues. Hope this helps some. |
Yup, it should be a separate issue. I wasn't sure if there was a common vcf validation step.
How's the vcf verification code? For fault tolerant-ness, this seems like a worthwhile effort. |
Daryl; |
Not sure what a reasonable solution is. However, I just ran into the same problem on a completely different cluster using freebayes instead of gatk. A single line in a single vcf is truncated and kills the whole pipeline at the catvariants step. My vote is for some vcf validating, maybe a fault tolerant mode. What about only running the vcf validation if catvariants errors out? |
Daryl; |
Thanks for re-opening, I'll rerun everything to see what pans out. I deleted all the problem vcfs so can't send much for diagnostics. What do you think... if I delete the vcf that was problematic in Thanks!!! |
Daryl; |
Thanks Daryl, closing this out for now since it seems like it might have been a one off issue and the actual files that were failing were deleted so we can't do much forensics. Feel free to reopen it if I'm wrong or there is still a problem going on. |
I'm using the gatk joint calling pipeline. Looks like some corrupt vcf's are sneaking through. Similar issue to #771
The text was updated successfully, but these errors were encountered: