fixed bug in tandem repeat annotation #6583
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@fleharty Here is a quick M2 and HC edge case bug for you.
In the edge case where an alt haplotype starts with an indel, and hence the variant context start is one base before the assembly region due to padding a leading matching base, there was a problem. The variant start was before the reference context window (since in this part of the code the reference context window is pegged to the assembly region, which caused problems in the lines
The fix is for
refBasesStartingAtVariantLocus
to exclude the padding base, which as you can see was done previously in the lineThat is, instead of taking a subarray of the reference bytes twice, once from the variant context start with padding and once more to remove the padding, we take a single subarray without the padding.
While I was at it, I replaced some slow conversions from
byte[]
toString
toString
back tobyte[]
with subarray operations.