Skip to content

Group publish paths by watchlist, blast, qc and aggregate - #30

Merged
jpalmer37 merged 1 commit into
mainfrom
refactor/simplify-publish-paths
Oct 21, 2026
Merged

jpalmer37 merged 1 commit into
mainfrom
refactor/simplify-publish-paths

Conversation

@jpalmer37

Copy link
Copy Markdown
Collaborator

Reorganises the output tree. Breaking for anything that reads the moved paths; auto-fluscan reads only the flat aggregate/*.tsv|csv files and <sample>/{paftools,nextclade}/*_final.vcf, which are unchanged.

  • Watchlist hits: <sample>/watchlist/<list>/<sample>_<SEG>_<list>_{pf,nc,sr}_watchlist_hits.tsv. The tag is needed because FASTA mode puts both branches in one list dir.
  • Run-level Nextclade output and the FluMut coordinate map: aggregate/nextclade/<db>/{<SEG>/,reference_remap/}.
  • Per sample: BLAST files in blast/, _qc_report.tsv in qc/. MultiQC report in aggregate/.
  • Docs updated; drops the never-published nextclade/status/<db>/ from them.

Where to look: modules/shared/mutation_watch.nf (relative <list>/ output path replaces saveAs) and the nc_output rename in modules/nextclade/nextclade.nf.

Tested with a FASTA-mode run (two bundles, two watchlists, --merge_flumut_mutations): 65/65 tasks succeeded and the tree matches the layout above. SHORT_READ was not run (broken on main since make_pileup.py was removed), so the sr tag and MultiQC move are untested. tests/test_run_snpeff.py has 5 failures that also fail on main.

🤖 Generated with Claude Code

Watchlist hits move to <sample>/watchlist/<list>/ with a pf/nc/sr tag; run-level
Nextclade output and reference_remap move under aggregate/nextclade/<db>/.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@jpalmer37
jpalmer37 marked this pull request as ready for review October 21, 2026 04:07
@jpalmer37
jpalmer37 merged commit 51d6953 into main Oct 21, 2026
1 check failed
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