-
Notifications
You must be signed in to change notification settings - Fork 738
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
ValueError: call_variants_outputs
did not pass sanity check.
#517
Comments
Hi @NagaComBio Sorry for the delay! I don't have a clear solution to this problem just from looking at the error message, but if you can share the data, e.g. with just a small slice of the bam, then I can try to reproduce the issue. If that's possible, you can email me at [email protected]. For now I can tell you that Thanks, |
Thanks for the offer, but it would be difficult to share the data without a DTA. So, I went back and reran the workflow (
Not sure how it's resolved. But, I will close this issue for now and will reopen it if a similar error pops up during the rerun of all the chrs. Thank you for looking into the issue, |
Have you checked the FAQ? https://github.com/google/deepvariant/blob/r1.3/docs/FAQ.md: Yes
Describe the issue:
The error arises during the "postprocess_variants" step. The quick-test and a run on chr22 from the same sample ran through without any issue. I tried to use
group_variants=false
as suggested here. But a similar error/crash occurs at a different variant/location. A similar problem was reported here, but the final fix is not provided.Setup
Steps to reproduce:
I have also tried postprocessing with
group_variants
, which also produces a similar error.Does the quick start test work on your system?
Please test with https://github.com/google/deepvariant/blob/r0.10/docs/deepvariant-quick-start.md.
Is there any way to reproduce the issue by using the quick start?
No, the quick start and also chr22 from the same sample ran through.
Any additional context:
The text was updated successfully, but these errors were encountered: