Repository navigation
Preserve distinct original SAM payloads in SV record identity - #444
Merged
Merged
Conversation
This was referenced Oct 5, 2026
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.
The selected Sid TPST1::CRCP bulk input contains 32 pairs of original records with the same old
(QNAME, FLAG, RNAME, POS, CIGAR, RG)key but different SAM payloads. Default SV collection silently discarded one; dense mode refused the input. Hash the complete original SAM alignment text for collection and serialized record IDs so both payloads reach the existing placement and cell/UMI ambiguity logic. Exact repeated records still deduplicate, and fragment identities remain unchanged. Record and observation IDs change once. Version 1.44.2.Regressions cover mate fields, MAPQ, sequence, qualities and tags, repeated indexed fetches, default/dense ambiguous labels without extra fragments, and interrupted spool cleanup. The new identity regression fails on released code. The corrected engine scans all 8,148 records in the original bulk subset successfully. Lint and all 5,711 tests pass (97% coverage), including 25 focused tests. CI is running; merge and PyPI deployment follow only after it is green.
Fixes #438. Prerequisite for #433 / #437.