Skip to content
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

Fix an instance of non-determinism in HaplotypeCaller #6104

Merged
merged 3 commits into from
Aug 27, 2019

Conversation

lbergelson
Copy link
Member

  • Fixing a non-deterministic point in HaplotypeCaller's KBestHaplotypeFinder
  • It uses a priority queue to compare scores, if there are ties the tie breaking is arbitrary and seems to be different depending on circumstances of the run.
  • For some as of yet unknown reason reading from a gs path vs a local path can cause this to be triggered.
  • Adding a tie breaker which uses the entirety of the bases in the Path in cases where the score is tied, this is unique per path.

* Fixing a non-deterministic point in HaplotypeCaller's KBestHaplotypeFinder
 * It uses a priority queue to compare scores, if there are ties the tie breaking is arbitrary and seems to be different depending on circumstances of the run.
 * For some as of yet unknown reason reading from a gs path vs a local path can cause this to be triggered.
 * Adding a tie breaker which uses the entirety of the bases in the Path in cases where the score is tied, this is unique per path.

Co-authored-by: jamesemery <[email protected]>
Co-authored-by: Louis Bergelson <[email protected]>
@lbergelson lbergelson requested a review from jamesemery August 20, 2019 19:56
@lbergelson
Copy link
Member Author

Hopefully a fix for #6105

@jamesemery
Copy link
Collaborator

Uhhh... I'm not really sure how to write a test for non-deterministic behavior... especially that behavior that we don't fully understand. We certainly need to see if this actually fixes some of the larger scale jitter we have witnessed.

…otypecaller/graphs/KBestHaplotypeFinder.java
@lbergelson lbergelson changed the title Fix non-determinism in HaplotypeCaller Fix an instance of non-determinism in HaplotypeCaller Aug 23, 2019
Copy link
Collaborator

@jamesemery jamesemery left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I honestly don't think its very easy or really possible to test this branch properly. @droazen

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants