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

FL.13 with S:K356T in China(26 seqs, 3 countries) #2073

Closed
aviczhl2 opened this issue Jun 28, 2023 · 7 comments
Closed

FL.13 with S:K356T in China(26 seqs, 3 countries) #2073

aviczhl2 opened this issue Jun 28, 2023 · 7 comments
Milestone

Comments

@aviczhl2
Copy link
Contributor

aviczhl2 commented Jun 28, 2023

From (sars-cov-2-variants/lineage-proposals#104)
FL.13+C21904T,T6334C,C7843T+A22629C(S:K356T)
GISAID query: C21904T,T6334C,C7843T,A22629C

No. of seqs: 26(China 24 Singapore 1(from China), South Korea 1(from China))
GISAID has 24, and also C_AA022306.1, C_AA024399.1 on GenBase.

First seq: EPI_ISL_17785084, Beijing, 2023-4-17
Latest: EPI_ISL_17850217, Fujian, 2023-6-15

usher
屏幕截图 2023-06-27 213504

@aviczhl2 aviczhl2 changed the title FL.13 with S:K356T in China(25 seqs, 3 countries) FL.13 with S:K356T in China(26 seqs, 3 countries) Jun 28, 2023
@corneliusroemer
Copy link
Contributor

Agree this is interesting. It looks a bit strange in that it for something quite recent it should be less ladder like. Maybe there is homoplasy or recombination involved? Or maybe sequencing errors. I'll designate anyways as one as there's no benefit in overcomplicating.

@Over-There-Is
Copy link
Contributor

Over-There-Is commented Jun 28, 2023

C_AA022306.1 and C_AA024399.1 are also on GISAID, they are EPI_ISL_17794209 and EPI_ISL_17811154, but they have T6334C and/or C7843T dropout.
Canada/ON-PHL-23-25722/2023|EPI_ISL_17814590|2023-06-08 have C21904T, C7843T, A22629C, C11956T, C12789T mutations, seems that it is a FL.13.2 / XBL.3+T967C, G3323A recombinant, the latter is also circulating in China.

@ryhisner
Copy link

ryhisner commented Aug 8, 2023

@corneliusroemer, the reason the Usher tree here looks weird is because there's a 66-nucleotide deletion in NSP3 in this lineage—∆3278-3343 / ORF1a:1005-1026del / NSP3_187-208del. This is misread in all the Chinese sequences, but seven different countries have registered it correctly. In fact, every non-Chinese FL.13.2 sequence has the deletion, with the sole exception of a Ginkgo Bozoworks sequence.
image
.

Some sequences have areas of missing coverage there, while others register multiple mutations, sometimes both preceding the deletion and sometimes on both sides of the deletion. Below are some of the different misreads, which make the Usher tree look so unusual.
image
image
image

@FedeGueli
Copy link
Contributor

FedeGueli commented Aug 9, 2023

Great finding @ryhisner . We should start to check every new lineage for this kind of things outside the spike. We usually are running out of time but i invite everyone to do that, me first ( @NkRMnZr, @aviczhl2 , @Fearuncle @HynnSpylor , @Memorablea, @BorisUitham). Also TRS thing when we notice a nuc mut at the end of a protein , we can tag @ryhisner that is the master of TRSes

@FedeGueli
Copy link
Contributor

oh sorry this is pango! pardon.

@Memorablea
Copy link
Contributor

Great finding @ryhisner . We should start to check every new lineage for this kind of things outside the spike. We usually are running out of time but i invite everyone to do that, me first ( @NkRMnZr, @aviczhl2 , @Fearuncle @HynnSpylor , @Memorablea, @BorisUitham). Also TRS thing when we notice a nuc mut at the end of a protein , we can tag @ryhisner that is the master of TRSes

Sorry, due to possible major issues with my network, GISAID cannot log in. Therefore, I cannot participate in your excellent work until the login page is restored. I'm very sorry!

@FedeGueli
Copy link
Contributor

Great finding @ryhisner . We should start to check every new lineage for this kind of things outside the spike. We usually are running out of time but i invite everyone to do that, me first ( @NkRMnZr, @aviczhl2 , @Fearuncle @HynnSpylor , @Memorablea, @BorisUitham). Also TRS thing when we notice a nuc mut at the end of a protein , we can tag @ryhisner that is the master of TRSes

Sorry, due to possible major issues with my network, GISAID cannot log in. Therefore, I cannot participate in your excellent work until the login page is restored. I'm very sorry!

Dont worry you and your page are doing a huge work! Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants