-
Notifications
You must be signed in to change notification settings - Fork 29
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
Added Tests for Untangle.R #128
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #128 +/- ##
==========================================
+ Coverage 39.83% 41.77% +1.93%
==========================================
Files 50 50
Lines 4182 4182
==========================================
+ Hits 1666 1747 +81
+ Misses 2516 2435 -81 ☔ View full report in Codecov by Sentry. |
All sounds good to me. Thanks for the work! |
Amazing, I'm happy to go back and modify the function and tests if you'd like to use a dendlist. Won't be hard to modify it now that everything else is already set |
Thanks, yes, please do.
…On Wed, 30 Oct 2024, 8:51 Alec Buetow, ***@***.***> wrote:
Amazing, I'm happy to go back and modify the function and tests if you'd
like to use a dendlist. Won't be hard to modify it now that everything else
is already set
—
Reply to this email directly, view it on GitHub
<#128 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAHOJBXEIX55I2WZ7L443N3Z6DI4DAVCNFSM6AAAAABQ2YJPAWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINBXGA2DEOBQGE>
.
You are receiving this because you modified the open/close state.Message
ID: ***@***.***>
|
I tried to achieve full coverage but I don't think it will be possible for all_couple_rotations_at_k lines 523, 528-534. I believe neither k_cluster_leaves nor km1_cluster_leaves can be NA, since both variables depend on the function cutree() which has the default parameter NA_to_0L = TRUE, setting all NA values to 0 instead.
I also had to change untangle_intercourse to create a working test for untangle_evolution. I think the corrections make the function more logically consistent; as it currently stands, untangle_intercourse takes four dendrograms as its input, then untangles #1 and #4 together, then #2 and #3 together. When it returns your newly untangled dendrograms, they are in the order: 1, 4, 3, 2. The other comparable functions to this one all untangle #1 and #2 together, then #3 and #4 together, returning them in the order: 1, 2, 3, 4. My changes made untangle_intercourse do the same.