Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix RBD level coloring and filter #1094

Merged
merged 6 commits into from
Jan 31, 2024
Merged

Fix RBD level coloring and filter #1094

merged 6 commits into from
Jan 31, 2024

Conversation

joverlee521
Copy link
Contributor

@joverlee521 joverlee521 commented Jan 29, 2024

Description of proposed changes

Came down this rabbit hole when I was thinking about augur export v2 and the filter footers. I noticed the ncov build had empty filter footers for level and rbd_level and investigated.

See commits for details.

Testing

Release checklist

If this pull request introduces backward incompatible changes, complete the following steps for a new release of the workflow:

  • Determine the version number for the new release by incrementing the most recent release (e.g., "v2" from "v1").
  • Update docs/src/reference/change_log.md in this pull request to document these changes and the new version number.
  • After merging, create a new GitHub release with the new version number as the tag and release title.

If this pull request introduces new features, complete the following steps:

  • Update docs/src/reference/change_log.md in this pull request to document these changes by the date they were added.

The filter `level` was originally added in
5a71d77
for RBD level but was the wrong field name.

The correct filter `rbd_level` was later added in
1b4846a.
@joverlee521 joverlee521 requested a review from a team January 29, 2024 20:45
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
The JSON output from `augur clades` was updated to separate `nodes`
and `branches` in nextstrain/augur#728 so now
the `assign_rbd_levels` script needs to parse the `branches` in order
to find the basal node.
@joverlee521
Copy link
Contributor Author

Waiting on internal discussion of whether we should update the RBD definitions or just drop them entirely.

joverlee521 added a commit that referenced this pull request Jan 31, 2024
Prompted by #1094, which led to
internal conversation¹ that determined we should just drop the RBD-levels.

¹ https://bedfordlab.slack.com/archives/CSKMU6YUC/p1706643360558109
@joverlee521
Copy link
Contributor Author

Closing in favor of #1097

@joverlee521 joverlee521 reopened this Jan 31, 2024
@joverlee521
Copy link
Contributor Author

Merging to get RBD-levels in a working state so we can easily reinstate the feature in the future.

@joverlee521 joverlee521 merged commit cec4fa0 into master Jan 31, 2024
18 of 19 checks passed
@joverlee521 joverlee521 deleted the fix-rbd branch January 31, 2024 21:24
joverlee521 added a commit that referenced this pull request Jan 31, 2024
Prompted by #1094, which led to
internal conversation¹ that determined we should just drop the RBD-levels.

¹ https://bedfordlab.slack.com/archives/CSKMU6YUC/p1706643360558109
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