Correct coverage and replicate handling in single-site DMR - #704
Open
SuhasSrinivasan wants to merge 6 commits into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #687.
Fixes #693.
Fixes #694.
Summary
Severity
Severity: Medium — scientific correctness, output validity, and reliability
Rationale: Accepted input could produce NaN or abort, impute no-observation replicates as canonical, or assign plausible matched statistics to the wrong pairs. Each changes scientific output silently within single-site DMR scoring.
Root cause
Count/cap boundaries allowed total zero, organizer data discarded sample IDs before pairing, and balanced aggregation converted undefined zero-total fractions into canonical pseudo-counts. These adjacent paths used inconsistent meanings for “no observation.”
Implementation
Preserved behavior
Non-goals
Behavior before and after
Testing
Environment: macOS 26.6 arm64; rustc/cargo 1.90.0; installed modkit 0.6.4 reference; samtools/bgzip/tabix 1.23.1; ignored test-only Cargo.lock SHA-256 78876ab4a98da30caad167744d1c8a0875c27edad7b0b3ad5f8a1891f78604ea resolving hts-sys 2.2.0. Cargo.lock is not in the diff.
Tests not performed
Scientific validation
Output and compatibility
Reviewer guide
Checklist