Feat/clade display names by rneher · Pull Request #1065 · nextstrain/ncov (original) (raw)

added 4 commits

April 20, 2023 21:31

@rneher

@rneher

@rneher

@rneher

renaming if no clade mapping is defined.

@rneher

Previously, clade colors were restricted to terms in the metadata. This is now changed to using the metadata which ensures that final clades (after modification through renaming to display clades) are used for color selection. We previously relied here on metadata, but display names are not present there.

@rneher

@rneher

corneliusroemer

huddlej

@rneher

@rneher rneher deleted the feat/clade-display-names branch

May 12, 2023 13:34

corneliusroemer added a commit to neherlab/nextclade_data_workflows that referenced this pull request

May 22, 2023

@corneliusroemer

See nextstrain/ncov#1065 Clade legacy is hence deprecated We now have a new column "display clade name" which is a combination of Nextstrain clade and Pango lineage, e.g. "23B (XBB.1.16)"

corneliusroemer added a commit to nextstrain/ncov-ingest that referenced this pull request

Jun 20, 2023

@corneliusroemer

Starting with dataset release 2023-06-16 Nextclade no longer outputs a clades_legacy column into the tsv ( This was implemented in neherlab/nextclade_data_workflows#42 And triggered by a refactor in ncov of how we annotate clades nextstrain/ncov#1065 ) So as not to break downstream workflows that rely on ingest output metadata.tsv having clade_legacy, this PR adds a clade_legacy column to metadata.tsv The values are defined as a simple mapping from clade_nextstrain (year-letter, e.g. 22F) to clade_legacy in defaults/clade-legacy-mapping.yml This file lives in ingest for now to make this PR work without requiring changes to ncov.

corneliusroemer added a commit to nextstrain/ncov-ingest that referenced this pull request

Jun 20, 2023

@corneliusroemer

Starting with dataset release 2023-06-16 Nextclade no longer outputs a clades_legacy column into the tsv ( This was implemented in neherlab/nextclade_data_workflows#42 And triggered by a refactor in ncov of how we annotate clades nextstrain/ncov#1065 ) So as not to break downstream workflows that rely on ingest output metadata.tsv having clade_legacy, this PR adds a clade_legacy column to metadata.tsv The values are defined as a simple mapping from clade_nextstrain (year-letter, e.g. 22F) to clade_legacy in defaults/clade-legacy-mapping.yml This file lives in ingest for now to make this PR work without requiring changes to ncov.

joverlee521 added a commit that referenced this pull request

Jan 29, 2024

@joverlee521

The clade labels were updated in #1065. Update the clade label so that the assign_rbd_levels script can find the correct basal clade.

I had considered pulling this value out as a parameter in the config YAML, but the original commit message¹ implies that this shouldn't not be configurable.

¹ fb5f44e

joverlee521 added a commit that referenced this pull request

Jan 29, 2024

@joverlee521

The clade labels were updated in #1065. Update the clade label so that the assign_rbd_levels script can find the correct basal clade.

I had considered pulling this value out as a parameter in the config YAML, but the original commit message¹ implies that this shouldn't not be configurable.

¹ fb5f44e

joverlee521 added a commit that referenced this pull request

Jan 30, 2024

@joverlee521

The clade labels were updated in #1065. Update the clade label so that the assign_rbd_levels script can find the correct basal clade.

I had considered pulling this value out as a parameter in the config YAML, but the original commit message¹ implies that this should not be configurable.

¹ fb5f44e

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

[ Show hidden characters]({{ revealButtonHref }})