Support singletons in residual and outcome checks
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 52/100
Research direction
Read the implementations of check_dyad_residuals(), check_dyad_outcomes() and check_partner_dependence() in the package's R/ sources, plus prepare_dyad_data() to learn the planned singleton labeling (singleton_<role>, .is_singleton_<role>). Note the issue is blocked on that prep work landing on the mixed-dyad-vignette branch, so start there. Done means kept singletons render as their own panels and are counted separately (no 'incomplete dyads' warning) while omitted fitted rows in complete dyads keep their composition, covered by tests using prepared data with singletons and fitted-row omissions.
Written by the indexing model from the issue text.
Description
Follow-up once singleton support lands in prepare_dyad_data() (planned on mixed-dyad-vignette): singletons = c("error", "drop", "keep"), with kept singletons labeled singleton_<role> (or singleton without role) and indicators .is_singleton_<role>.
check_dyad_residuals() / check_dyad_outcomes() (#77)
- Show singleton groups as their own panels, next to the dyad roles.
- Keep each dyad's known composition and role when fitted rows are omitted (e.g., a member dropped for missing predictors). Such a member must not turn into a singleton panel.
check_partner_dependence() (#81)
- Singletons have no pairs, so they are correctly left out. But they are currently reported as "incomplete dyads" with a warning. Count them separately and without a warning when they were kept on purpose.
Tests: prepared data with singletons, plus fitted-row omissions in complete dyads.
- Dominant language
- R
- Stars
- 1
- Forks
- 2
- Avg merge
- 9h 28m
- Merged PRs (30d)
- 21
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Pascal-Kueng/dyadMLM
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Pascal-Kueng/dyadMLM#92 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
Pascal-Kueng/dyadMLM#83 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 1/5 Under an hour Newbie friendliness 72/100
Pascal-Kueng/dyadMLM#71 · 2 comments ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 1/5 Under an hour Newbie friendliness 86/100
Pascal-Kueng/dyadMLM#70 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 1/5 Under an hour Newbie friendliness 85/100
Pascal-Kueng/dyadMLM#69 ·
Maintainers usually reply within 1 day
All issues in Pascal-Kueng/dyadMLM
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
stan-dev/priorsense#150 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
bennettoxford/opencodecounts#170 ·
-
complexity::1-low effort::1-hours priority::3-could
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
jumpingrivers/audit.workbench#43 ·
Maintainers usually reply within 1 day
-
complexity::1-low effort::1-hours priority::3-could
Difficulty 1/5 Under an hour Newbie friendliness 85/100
jumpingrivers/audit.connect#71 ·
Maintainers usually reply within 1 day