pirl-unc / tsarina

70%

LAST BUILD ON BRANCH main

branch: SELECT

CHANGE BRANCH

x

Sync Branches

• No branch selected
• add-refs-format-20260420
• audit-hitlist-tsa-goal-20260420
• cache-kmer-enumeration-20260420
• close-tsarina-4-via-load-all-evidence
• codex/ctag-display-label
• codex/fix-xage-ms-counts
• codex/live-hitlist-ms-panel
• codex/mhcflurry-full-batch-progress
• consolidate-iedb-drop-netmhcpan-shim
• cta-exclusive-ms-counts
• cta-passes-filters-threshold-098
• deconvolve-multiallelic-ms-evidence
• delegate-to-hitlist-proteome-kmer-set-20260422
• docs/hitlist-data-and-viral-defaults
• drop-local-aggregate-refs-20260420
• feature/panel-cta-safety-and-nyeso-group
• feature/panel-ms-evidence-tiers
• feature/panel-progress-summary-table
• feature/panel-version-peptide-progress
• feature/spanning-alias-help-smoke-tests
• fix-mhcflurry-c1505-speed
• fix/curation-audit-fixes
• fix/ms-evidence-normalization
• fix/panel-healthy-ms-gene-veto
• fix/panel-ms-metrics
• fix/panel-vital-ntpm-threshold
• group-identical-cta-peptide-panels
• group-identical-cta-peptide-sets
• handle-peptide-attribution-provenance
• hitlist-1.15-pin-and-length-pushdown
• hitlist-1.6.0-integration
• main
• ms-curation
• panel-mage-safety-summary-sort
• refs-and-cache-integration-tests-20260421
• simplify-species-kwargs-for-hitlist-1.9
• sort-cta-coverage-first
• spanning-pmhc-set-20260420
• spanning-progress-20260421
• spanning-test-polish-20260421
• unify-kmer-enumeration-20260421
• warn-binding-assays-on-cached-path

Build # 25532665882

Build Type

push

github

Committed by web-flow

Commit Message

Sort CTA panel summary by estimated coverage first (#66)

* Sort CTA panel summary by estimated coverage first

The panel summary's per-CTA table was previously ordered by selected
peptide count, so high-coverage CTAs with few peptides (e.g. PIWIL1 at
98.9% with 2 peptides) sank below middling-coverage CTAs with many
peptides. Reorder the sort key to coverage-first, with peptide count
and HLA hit count as tiebreakers, so the table reads top-to-bottom by
the value users actually compare.

v1.2.23

* Drop redundant ordering test

The renamed test asserted HIGH > LOW > ZERO, which holds under both
the old peptide-count-first sort and the new coverage-first sort, so
it never actually verified the new ordering. The new
test_panel_summary_coverage_outranks_peptide_count test is the one
that discriminates the two orderings, and per-CTA coverage values
are already asserted in test_panel_summary_counts_ms_tiers_per_cta.

Coverage Stats

2294 of 3283 relevant lines covered (69.88%)

0.7 hits per line