There are sound reasons to explicitly exclude the KF285 and KF293 strains from the phylogenetic build. If we manually exclude them, we no longer have any need to annotate the passage_type field, which makes it easier to port this repo to the new augur curate commands.
Context
Slack context
Description
There are sound reasons to explicitly exclude the KF285 and KF293 strains from the phylogenetic build. If we manually exclude them, we no longer have any need to annotate the
passage_typefield, which makes it easier to port this repo to the new augur curate commands.