-
Notifications
You must be signed in to change notification settings - Fork 9
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 setting DHD in VCF when annotating #2
Comments
H Brad, thanks for finding this. This was a bad bug that only happens when run on > 1 sample since I was always testing on a single sample. I have made a fix locally. I already have a change in smoove that incorporates duphold automatically (well, with an optional flag) so I'd hold off for a bit. I also stumbled on several improvements to duphold that make it even better. Those changes will be out this week. Thanks again for the full test-case. It enabled the discovery of the silly bug quickly. |
Brent; |
I have made a new release. Your testing is much appreciated: I think you had this for testing purposes, but note that:
is preferable to:
and that duphold |
Brent;
Thanks for duphold, this is a brilliant idea to help improve SV filtering and I'm working to incorporate into bcbio right now.
When running validation cases I'm hitting an issue that I'm not sure how to fix/work around. It complains with:
and exits with a
1
error code before producing any variants.I put togther a small test case that has this issue. It's self-contained, except you need to edit
REF
to point at a GRCh37 fasta file (I couldn't figure out how to make it work with a reduced fasta file to include). I'm running with the v0.0.2 pre-built binary packaged up into conda.https://s3.amazonaws.com/chapmanb/testcases/duphold_setting_DHD.tar.gz
The command is fairly vanilla:
and I get the same error whether using a bgzipped/tabix VCF or bcf input.
Do you have any clues about what I'm doing wrong? I can see the error message and check in the code (
duphold/src/duphold.nim
Line 204 in 5e5e9de
The text was updated successfully, but these errors were encountered: