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

Rename H3 proposed subclades #268

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Conversation

huddlej
Copy link
Contributor

@huddlej huddlej commented Feb 19, 2025

@huddlej huddlej temporarily deployed to refs/pull/268/merge February 19, 2025 17:56 — with GitHub Actions Inactive
Rename H3 subclade proposals for J.2 to use amino acid substitutions
instead of single-letter suffixes.
@huddlej huddlej force-pushed the rename-h3-proposed-subclades branch from 27000ba to 4eea770 Compare February 19, 2025 21:35
@huddlej huddlej deployed to refs/pull/268/merge February 19, 2025 21:35 — with GitHub Actions Active
@huddlej huddlej requested a review from rneher February 19, 2025 21:47
@rneher
Copy link
Member

rneher commented Feb 26, 2025

How useful is it to rename these now. when I was proposing to go with amino acid patterns, I was thinking to track haplotypes instead of clades. I'd suggest to revisit this in a few weeks and pick proper subclades.

@huddlej
Copy link
Contributor Author

huddlej commented Feb 26, 2025

It's probably not useful now. Generally, I just need a way to quickly annotate proposed subclade annotations through Nextclade for the two frequency estimation methods we're using now. In the current approach, I have to update influenza-clade-nomenclature, update-merge-release the Nextclade dataset, and rerun Nextclade annotations. If we're concerned about updating the official flu Nextclade datasets with PRs like this, I could maintain separate parallel datasets just for proposed subclades.

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.

3 participants