Skip to content

Preserve splice-ambiguous event hypotheses in dense discovery - #442

Merged
iskandr merged 1 commit into
masterfrom
fix/dense-splice-ambiguous-priority
Oct 5, 2026
Merged

iskandr merged 1 commit into
masterfrom
fix/dense-splice-ambiguous-priority

Conversation

@iskandr

@iskandr iskandr commented Oct 5, 2026 •

Copy link
Copy Markdown
Contributor

Dense discovery can spend its representative budget on other event context before
retaining splice-ambiguous event joins. In the Sid ::IGKC replay, none of the 487
original witness records for a previously retained short hypothesis reached the
dense discovery set; those joins were ranked as ordinary novel context.

Prioritize _join_class's deliberately deferred (lazy) event-compatible joins
alongside other placed event joins. Their existing splice-ambiguity classification
and full-input support counting remain intact. Bump to 1.44.1.

The regression fails on the released engine: abundant breakpoint clips exhaust
a two-record discovery budget before a splice-ambiguous candidate. With this fix,
the candidate survives and all seven original fragments/cells without qualities
are counted. Lint, all 14 dense regressions, and all 5,700 tests pass (97% coverage).
The original-engine regression fails and the corrected engine preserves the
splice-ambiguous hypothesis. GitHub CI must pass before merge/deploy.

Fixes #441. Required by the real-data #437 integration in #433; the initial and
corrected Sid replays will be kept separately.

@coveralls

Copy link
Copy Markdown

Coverage Status

coverage: 96.547%. remained the same — fix/dense-splice-ambiguous-priority into master

@iskandr
iskandr merged commit 500ee34 into master Oct 5, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Dense discovery can crowd out splice-ambiguous event hypotheses

2 participants