8000 F01: TRGT parental-allele candidate hypotheses by 1836405040 · Pull Request #5 · qinqian/minisv.py · GitHub
[go: up one dir, main page]

Skip to content

F01: TRGT parental-allele candidate hypotheses - #5

Open
1836405040 wants to merge 1 commit into
qinqian:mainfrom
1836405040:feature/01-trgt-candidates
Open

1836405040 wants to merge 1 commit into
qinqian:mainfrom
1836405040:feature/01-trgt-candidates

Conversation

@1836405040
@1836405040 1836405040 commented Oct 15, 2026 •
Copy link
Copy Markdown

TRGT records with unresolved origin or parent-relative allele changes can be lost before review. Preserve allele-length hypotheses, source labels and molecule names, and prepare caller inputs without consulting truth coordinates.

Dependencies and scope

Feature F01 in the ordered stack documented at https://github.com/1836405040/minisv-triofilter/blob/feature/reproducible-trio-workflow/docs/FEATURE_REVIEW.md . F01 targets upstream main; dependent PRs target preceding fork branches so their diffs contain only the next feature. Retarget/rebase subsequent features after predecessors are reviewed upstream.

This preserves upstream history and existing commands. The separate pipeline repository references a fixed tool commit; it does not copy algorithm source. Experimental centromere assembly modules and unpublished locus interpretations are outside these PRs.

Validation

tests/test_trgt_hypotheses.py and candidate-input tests; also included in the passing F06 stack.

The first upstream PR has no reported upstream Actions check yet. The assembled feature stack and downstream workflow have passing fork CI; these are software tests, not independent biological validation.

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.

1 participant

0