Repository navigation
Thin-evidence species: top-up to cap 700 prepared for after the HPCC shutdown (expand_runs --species-file, append_stage.py, runbook) - #328
Merged
Conversation
…ns --species-file, append_stage.py, runbook expand_runs.py --species-file limits a top-up to listed species. append_stage.py appends a stage's runs to a committed wave without touching existing rows and decides the species that gained runs again (thin-evidence cap kept). orchestration/thin_topup_2026-11-10/: the 17 thin-evidence species and run.sh (refresh, lists at cap 700, submit, check). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Follow-up to #327. This queues up the 17 thin-evidence species that have more runs to type, so the top-up can start as soon as the HPCC shutdown ends. Nothing was run on the HPCC: the code and runbook were written and tested on the laptop.
What
expand_runs.py --species-file(optional) limits a top-up to the species it lists. Comments are skipped, and a listed species with no untyped run is reported on stderr. Without the option, nothing changes.append_stage.py(new) appends a stage's runs to a committed wave.rescueandscreencolumns.merge_screen.mergerewrites every row's screen columns from the stage, which wiped them when I first used it for Reads gate: type thin-evidence species (one strain or 1-3 runs) as UNVALIDATED instead of holding them #327 (caught before commit).merge_screen.regate_species, so their curator rulings and thin-evidence tokens are kept. Changed rows go toappend_changes.tsv.orchestration/thin_topup_2026-11-10/:species.txt: the 17 species, with eligible and typed counts from the 2026-11-06 snapshot.run.sh refresh | lists | submit | check.README.md.CONTRACT.md: when to useappend_stage.pyand when to usemerge_screen.py.Expected size
About 340 new runs, going by the 2026-11-06 snapshot; the refresh decides the real numbers.
The
few_runsspecies, Pneumocystis among them, have only 4 to 9 eligible isolates.Choices to confirm
--per-study 700), as inexpand300b. This matters for F. sambucinum, whose isolates all come from one study; a 25-per-study limit would keep it at about 33 runs.Checks
tests/test_append_stage.py: existing rows untouched; a topped-up thin species stays capped; a species with no new runs is not decided again.tests/test_expand_runs_script.py: the species filter.run.shpassesbash -n. It has not been run.After the shutdown
Run
listsand readexpand_summary.tsvbeforesubmit.🤖 Generated with Claude Code