-
Notifications
You must be signed in to change notification settings - Fork 3
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
Multiple JN.1* sub-lineages with S:S31- and S:R190S, 2 ongoing unproposed branches as of 2/5 #1771
Comments
@aviczhl2 LP.1.1 is not LP.1 + S:R190S , designation of #1664 is still pending. Please correct that! |
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
i ve added (lineage) for branches of other issues to make easier to identify them it should be all ok now. thanks for this important tracking issue. cc @DailyCovidCases please wait a bit before proposing them separately: at least wait them to reach 30 seqs |
br 6 edited to exclude the Bat viruses |
Br 8 jumped to 11 |
As said all branches are fastly growing. |
New 31del+190S branch this time from Russia and on JN.1.4 backbone: cc @aviczhl2 |
Shall be recombinant of JN.1.4.5 and branch 18 of #1502 ? Is C11020T convergent? No it has T18453C isn't it? That blocks chances of simple recombs with 1 or 2 BPs. |
I checked and C11020T is very convergent. So the Russian one is a new branch. |
Yeah i was thinking the same |
Br.6 to 13 |
@aviczhl2 i suggest to track all of them here not in #1502, i mean the count and the query here not there |
Add branch 12, LB.1+S:R190S direct branch |
Add branch 13 and 14. |
Branch 14 is very interesting it stems out of the Jn.1+C25566T branch that is the branch leading then to JN.1.7 so i suspect it is either old one or some sort of recombinant, it is also misplaced in a 28603T branch that got FLipFLopped then ah and it is 4 on Usher with a Uk Climb sample too |
@aviczhl2 please propose branch 6 and branch 8 |
Add branch 15-17. |
Not fast LB.1.9 (478T) branch got 335F and 190S: |
add branch 35, another KP.3.1.1+S:R190S from Poland |
3 recent in Ontario |
Add branch 36, NL.5+S:R190S |
Branch 35 is 16 now |
thx spreading in Colorado while Br.36 is now 7 with NJ |
Oman+2, without C3373T. |
make a separate issue |
maybe better to extrapolate br.36 |
branch 34 designated XEJ.2 via cov-lineages/pango-designation@5872a5a#diff-ead4244ff49c81bc758e9f068f5ef42156bd985b9c86de8fa4d6fcd7f2829090R1436 |
There could be a big LB.1.2.2 branch in Peru with 190S checking it |
branch 26 is 18 now also in Malaysia and New Zealand |
branch 26 +2 Canada. I'll propose it. |
a third apparently unrelated S:R190S branch of KP.2.3.12 apparently |
add it if it has some seqs |
Br.36 +1 England |
add branch 37, MC.24+S:R190S. |
Unfortunately mostly Ohio without collection date so growth advantage not reliable for this one |
Br.36 +2 |
Br.36 designated NL.5.2 via cov-lineages/pango-designation@7ac925e |
The only one remaining seems not advancing. Finally close this down. @FedeGueli pls make separate issues for future R190S branches. |
It seems that there is a new convergent mutation of S:R190S. It usually couples with S:S31del.
Cov-spectrum shows its growth is negative with S:S31S, but large growth advantage with S:S31-. It seems that like S:Q493E must be gained after S:F456L, this S:R190S must present under S:S31- variants.
Tasks
https://cov-spectrum.org/explore/World/AllSamples/Past2M/variants?variantQuery=S%3A31S&aaMutations1=S%3AR190S%2CS%3A31S&analysisMode=CompareToBaseline&


https://cov-spectrum.org/explore/World/AllSamples/Past2M/variants?variantQuery=S%3A31-&aaMutations1=S%3AR190S%2CS%3AS31-&analysisMode=CompareToBaseline&
The text was updated successfully, but these errors were encountered: