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

Suggestion to broaden XDV.1.2 to include everything under S:R346T branch. #2789

Open
xz-keg opened this issue Sep 27, 2024 · 6 comments
Open

Comments

@xz-keg
Copy link
Contributor

xz-keg commented Sep 27, 2024

The only XDV.1+S:R346T seqs were the N:I292T branch when XDV.1.2 was designated.
However as more seqs are submitted there are many more branches now. Suggest to broaden XDV.1.2 accordingly. @AngieHinrichs @corneliusroemer

https://nextstrain.org/fetch/genome-test.gi.ucsc.edu/trash/ct/subtreeAuspice2_genome_test_5dd41_689d60.json?label=id:node_5496004
image

@FedeGueli
Copy link
Contributor

The only XDV.1+S:R346T seqs were the N:I292T branch when XDV.1.2 was designated. However there are many more branches now. Suggest to broaden XDV.1.2 accordingly. @AngieHinrichs @corneliusroemer

https://nextstrain.org/fetch/genome-test.gi.ucsc.edu/trash/ct/subtreeAuspice2_genome_test_5dd41_689d60.json?label=id:node_5496004 image

They doesnt seem related if not the orf1a:L3116F carrying ones.

@FedeGueli
Copy link
Contributor

Or you think they are all related being mostly by Shanxi?

@xz-keg
Copy link
Contributor Author

xz-keg commented Sep 27, 2024

They doesnt seem related if not the orf1a:L3116F carrying ones.

Like JN.1.16.1, they shall be assigned a name despite potential separate occurence.

@FedeGueli
Copy link
Contributor

They doesnt seem related if not the orf1a:L3116F carrying ones.

Like JN.1.16.1, they shall be assigned a name despite potential separate occurence.

Yeah but already assigned, it is very rare that a lineage has been broadened or tightened, classical example AY.41 that was designated too deep leavig out a lineage, sibling of AY.103, that was deadly in eastern Europe during summer 2021.

@xz-keg
Copy link
Contributor Author

xz-keg commented Sep 28, 2024

They doesnt seem related if not the orf1a:L3116F carrying ones.

Like JN.1.16.1, they shall be assigned a name despite potential separate occurence.

Yeah but already assigned, it is very rare that a lineage has been broadened or tightened, classical example AY.41 that was designated too deep leavig out a lineage, sibling of AY.103, that was deadly in eastern Europe during summer 2021.

They do not have a name and is under the general XDV.1, while XDV.1.2 now starts from N:I292T

@FedeGueli
Copy link
Contributor

They do not have a name and is under the general XDV.1, while XDV.1.2 now starts from N:I292T

i mean most of them are on XDV.1.2 with starting with 346T it would become the collector of XDV.1 +346T but likely already hard to think there will be new emergence of 346T directly from the politomy after many months around so likely worth broadening it.

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

No branches or pull requests

2 participants