-
Notifications
You must be signed in to change notification settings - Fork 592
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
haplotypecaller ArrayIndexOutOfBoundsException : org.broadinstitute.hellbender.tools.walkers.annotator.TandemRepeat.getNumTandemRepeatUnits #8106
Comments
and here is a minimal example: with
|
I'm trying to explore this bug: my cmd is :
in : the variant is with so startIndex is lower than zero when = which rises a java.lang.ArrayIndexOutOfBoundsException with: so it looks like the ReferenceContext used by getNumTandemRepeatUnits was too narrow for the given variant. |
I think I see what's going on. Since the force calling allele is so huge (a deletion from 36957826 to 36958130) the GATK engine does not create an AssemblyRegion that spans it. Rather, it creates a big region from 36957826 to 36958125 and a tiny one from 36958125 to 36958130. This is silly and worth fixing but the bug hasn't occurred yet. The GATK goes through both assembly regions, the big one and the small one, and the force calling allele is genotyped in both. This happens because in I think the fix might be as simple as counting only force calling alleles that begin in an assembly region. A different solution might be to guarantee upstream that force calling alleles fit completely in a single assembly region, perhaps skipping them with a warning if they are too big for the GATK to handle. @droazen I can get my hands dirty and probably fix this reasonably quickly at this point, but could you weigh in on the two possible solutions? |
@davidbenjamin Counting only alleles that begin in an assembly region seems more consistent with our past solutions to problems of this nature. See also the PR #6388, which we might be able to use here. |
Great, in that case I am optimistic that this will be a quick fix. |
Instructions
Bug Report
Hi GATK team , I'm afraid I found an exception in gatk HC related to #6516
Affected tool(s) or class(es)
GATK HC v4.3.0.0
Affected version(s)
Description
the same command ran fin with another intervals.
The text was updated successfully, but these errors were encountered: