-
Notifications
You must be signed in to change notification settings - Fork 11
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
Quick fix to precision recall #63
Conversation
Codecov Report
@@ Coverage Diff @@
## master #63 +/- ##
=======================================
Coverage 98.95% 98.95%
=======================================
Files 30 30
Lines 956 957 +1
=======================================
+ Hits 946 947 +1
Misses 10 10
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
@gwaygenomics Ready for your review :) |
@michaelbornholdt - can you resolve the merge conflict? Also, I feel like @FloHu is better equipped to review this PR than me. @FloHu, given your insights in #62, do you have availability to review within Michael's requested time frame? |
@FloHu. Everything is ready now. |
Sorry for my late answer, things have been very busy. Sure, I'll review it, give me time until tomorrow, it's on my list. :) |
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.
Everything seems to be correct and making the groupby explicit is definitely needed. I have to say that I still do not see how it solves the issue about counting twice vs. counting once (as discussed in the issue, see last comment) but I trust you on it. When I have some more time I can think into it further.
@gwaygenomics please Merge :) |
If you have unique groupings now, ie one group per sample. Then there will no bidirectional vertices since you are only looking at one node. If you group by several nodes, then yes we still have the counting twice thing |
See issue #62 .