-
Notifications
You must be signed in to change notification settings - Fork 594
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
Prune assembly graph before checking for cycles #5562
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.
M2 is definitely more sensitive, so if you're happy I'm happy.
I'm also happy (and surprised) that none of the integration test outputs change, but I hate changing code without changing tests. Do you think the user would let us use a hundred or so bp of his/her data as a regression test?
Actually, what about Sarah's MT data instead? That should be fine to use. |
5531bfd
to
1200903
Compare
Codecov Report
@@ Coverage Diff @@
## master #5562 +/- ##
===============================================
- Coverage 87.062% 85.658% -1.404%
+ Complexity 31879 31243 -636
===============================================
Files 1940 1940
Lines 146799 146748 -51
Branches 16233 16227 -6
===============================================
- Hits 127806 125701 -2105
- Misses 13073 15050 +1977
- Partials 5920 5997 +77
|
@ldgauthier I put in a regression test from the user's data. |
7260473
to
1646c03
Compare
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.
Beautiful, thank you!
@ldgauthier This doesn't hurt M2 on our evaluations but should I do anything to check that it's okay for HaplotypeCaller?