-
Notifications
You must be signed in to change notification settings - Fork 12
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
Hybrid-selection metrics from alfred qc #18
Comments
I am not using picard but I would assume the bait intervals are the probes and the targets something like exons? Alfred only needs a single bed file of target regions. |
I think there is a difference between Alfred and Picard when the mean depth is greater than 65535(0xFFFF). |
The basepair level coverage uses a 16bit integer by default. You can change this code fragment to uint32_t and recompile to allow coverages up to 2^32. |
@tobiasrausch At first, I changed this code from uint16_t to uint32_t, but alfred unexpectedly stopped without any output files. |
Let me check, I probably forgot somewhere in the code to refer back to this type definition. |
You can specify now at compile time if you want to use 32bit integers for ultra-deep coverage. Just pull the last code and then use:
Can you please try again if that works for you? Thanks. |
It worked excellently! |
Hi there
I was curious about how Alfred worked with hybrid-selection metrics. The motivation was we were discussing the differences between Alfred and Picard/GATK4's "CollectHSMetrics" for WES samples:
https://software.broadinstitute.org/gatk/documentation/tooldocs/4.0.5.1/picard_analysis_directed_CollectHsMetrics.php
This requires both target and bait intervals.
It's not clear to what extent Alfred provides HS metrics, or whether the metrics output by e.g.
CollectHSMetrics
would differ that much from Alfred.Somewhat related to this issue: #17
Any insight on your part is appreciated. Thank you for the help
The text was updated successfully, but these errors were encountered: