Skip to content

Conversation

@j23414
Copy link
Contributor

@j23414 j23414 commented Sep 19, 2025

Description of proposed changes

Since the genome Nextclade dataset has QC, initialized QC parameters for sh Nextclade dataset. However, I could use some help on picking thresholds...

Related issue(s)

Checklist

  • Checks pass
  • Update changelog

The Mumps Nextclade dataset had been reporting both a "Clade" and a "MuV_genotype" column.
This change only reports the "Clade" assignment as the second is redundant for the user.

This change also allows us to drop the hard coded nextclade_extension specification in the auspice_config files
since pathogen.json already has this information and having both would risk settings getting out of sync and confusion
during debugging.
Add documentation on where clade_membership is being spiked in or inferred from a fall back column.
Clearly use clade_membership during the genome filtering step, even though MuV_genotype should have equivalent behavior.
@j23414 j23414 force-pushed the nextclade-drop-extra-column branch from 603d383 to 8d3a839 Compare September 19, 2025 23:05
@j23414 j23414 force-pushed the nextclade-drop-extra-column branch from 3015ddb to 448c6b0 Compare November 4, 2025 01:11
Base automatically changed from nextclade-drop-extra-column to main November 5, 2025 02:12
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.

2 participants