-
Notifications
You must be signed in to change notification settings - Fork 597
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
Clarify cryptic bitwise operations in Partiall-determined haplotype EventGroup subclass #8400
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 A few documentation requests and exactly one material comment that if the bitset object is going to be limited to 30 elements you should put more guardrails into the thing (unless you want to make it a private class) to protect against having to find out what an overflow does here...
I trust you can address those comments and merge without me blocking you again on this.
.../hellbender/tools/walkers/haplotypecaller/PartiallyDeterminedHaplotypeComputationEngine.java
Show resolved
Hide resolved
.../hellbender/tools/walkers/haplotypecaller/PartiallyDeterminedHaplotypeComputationEngine.java
Show resolved
Hide resolved
.../hellbender/tools/walkers/haplotypecaller/PartiallyDeterminedHaplotypeComputationEngine.java
Show resolved
Hide resolved
…ventGroup subclass (#8400)
@jamesemery Another DRAGEN PR for you. No change in output, but it lays some of the groundwork for having multiple determined events at one locus and will make addition of more features easier.
It runs just as fast as before -- the bit-twiddling is encapsulated, but it's still there.