-
-
Notifications
You must be signed in to change notification settings - Fork 2
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
McNemar's statistical test addition: ard_mcnemartest
#51
Conversation
Signed-off-by: Davide Garolini <[email protected]>
Unit Tests Summary 1 files 14 suites 2s ⏱️ Results for commit 5781b8d. ♻️ This comment has been updated with latest results. |
Code Coverage Summary
Diff against main
Results for commit: 5781b8d Minimum allowed coverage is ♻️ This comment has been updated with latest results |
Unit Test Performance Difference
Additional test case details
Results for commit 462ffb7 ♻️ This comment has been updated with latest results. |
thanks @Melkiades !
Let's keep the same defaults as the the R function. To keep the API consistent with the other ard stat functions, we can still use
Very good point. A separate |
Co-authored-by: Abinaya Yogasekaram <[email protected]> Signed-off-by: Davide Garolini <[email protected]>
To me, it seems useful, but I do not know if it is necessarily a missing piece in {cards}' toolbox. I would add it to a group of related utils and export it if you think it would be used. For users, I would make by1 and by2 customizable and the paired values as defaults (also could it make sense to extend it beyond paired data?). |
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.
This looks great! Just a few comments to address.
…sengineering/cardx into 40_ard_mcnemar_test@main
Welcome to Codecov 🎉Once merged to your default branch, Codecov will compare your coverage reports and display the results in this comment. Thanks for integrating Codecov - We've got you covered ☂️ |
@ddsjoberg thank you for your review! Could you take another look at the changes? ;) |
Signed-off-by: Daniel Sjoberg <[email protected]>
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.
thanks @Melkiades !! looks great!!
What changes are proposed in this pull request?
ard_mcnemartest()
statistical test function.Closes #40
I am wondering if we need to have
ccorrect = TRUE
as default, following the default in stats, and if we should make this option more apparent in the case we change this default.Also, I do not know if it would be relevant but I used an utility function to find dichotomies in a data-set that could result useful as a tool if there is not one already doing this:
Created on 2024-02-14 with reprex v2.1.0
.paired_data_pivot_wider
is in the Wilcoxon test. Should we have it as a tool in a dedicated file? It looks general to me.Pre-review Checklist (if item does not apply, mark is as complete)
usethis::pr_merge_main()
devtools::test_coverage()
Reviewer Checklist (if item does not apply, mark is as complete)
pkgdown::build_site()
. Check the R console for errors, and review the rendered website.devtools::test_coverage()
When the branch is ready to be merged:
NEWS.md
with the changes from this pull request under the heading "# cards (development version)
". If there is an issue associated with the pull request, reference it in parentheses at the end update (seeNEWS.md
for examples).