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

LB.1.3 second FULL QUAD ( DEFLiRT+ S:T572I) lineage (33 Isr, Us, UK, Spain) #1583

Closed
FedeGueli opened this issue May 29, 2024 · 14 comments
Closed

Comments

@FedeGueli
Copy link

FedeGueli commented May 29, 2024

Edited Intro:
This was tracked as Singlet 71 of #1089 (from Israel) then it became Branch 136 when the Uk sample came spotted also by @HynnSpylor and @ryhisner . Rediscovered from a downsampled tree that mistakenly showed this and #1582 together.

LB.1.3 [S:S31del ( Del21653-55) > Orf1b:T1555I (C18131T) ] > S:T572I (C23277T)
Query: Del21653,C23277T,C18131T
Samples: 3
Countries: Israel UK NYC
Tree:
Screenshot 2024-05-29 alle 19 07 43
https://nextstrain.org/fetch/genome-test.gi.ucsc.edu/trash/ct/subtreeAuspice1_genome_test_4c223_75ccd0.json?label=id:node_7128678

@FedeGueli FedeGueli changed the title LB.1 second FULL QUAD ( DEFLiRT+ S:T572I) lineaage (3 Isr,NYC LB.1 second FULL QUAD ( DEFLiRT+ S:T572I) lineaage (3 Isr, Us, UK) May 29, 2024
@FedeGueli FedeGueli changed the title LB.1 second FULL QUAD ( DEFLiRT+ S:T572I) lineaage (3 Isr, Us, UK) LB.1 second FULL QUAD ( DEFLiRT+ S:T572I) lineage (3 Isr, Us, UK) May 29, 2024
@HynnSpylor
Copy link

Yeah I also mentioned the English seq in X group several days ago(+S:V642G, S:P809S)

@FedeGueli
Copy link
Author

Yeah I also mentioned the English seq in X group several days ago(+S:V642G, S:P809S)

Ah thx is it that one? So it was tracked back in #1089 as singlet before the 642G came.let me see the branch so i could match it with this! (I ve found this casually from a s:31del downsampled tree that mistakenly showed this and the other you proposed together as LB.1 (and i cant see how it happened! ) so i didnt realize this was the same of the one that you mentioned on X ;) )

@FedeGueli
Copy link
Author

Ok mistery solved it was singlet 71 of #1089 (the isr.sample) that became branch 136 when the uk seq popped up then i closed the issue so i didnt see the third coming!
Thx both for the help.

But is this real or just multiple unrelated samples put together by Usher?

@HynnSpylor
Copy link

Yeah I also mentioned the English seq in X group several days ago(+S:V642G, S:P809S)

@FedeGueli FedeGueli changed the title LB.1 second FULL QUAD ( DEFLiRT+ S:T572I) lineage (3 Isr, Us, UK) LB.1 second FULL QUAD ( DEFLiRT+ S:T572I) lineage (4 Isr, Us, UK) Jun 3, 2024
@FedeGueli
Copy link
Author

+1 Scotland

@FedeGueli
Copy link
Author

Parent designated LB.1.3

@FedeGueli FedeGueli changed the title LB.1 second FULL QUAD ( DEFLiRT+ S:T572I) lineage (4 Isr, Us, UK) LB.1.3 second FULL QUAD ( DEFLiRT+ S:T572I) lineage (4 Isr, Us, UK) Jun 4, 2024
@FedeGueli FedeGueli changed the title LB.1.3 second FULL QUAD ( DEFLiRT+ S:T572I) lineage (4 Isr, Us, UK) LB.1.3 second FULL QUAD ( DEFLiRT+ S:T572I) lineage (5 Isr, Us, UK) Jun 6, 2024
@FedeGueli
Copy link
Author

FedeGueli commented Jun 6, 2024

5 now England with V642G

@FedeGueli FedeGueli changed the title LB.1.3 second FULL QUAD ( DEFLiRT+ S:T572I) lineage (5 Isr, Us, UK) LB.1.3 second FULL QUAD ( DEFLiRT+ S:T572I) lineage (6 Isr, Us, UK) Jun 10, 2024
@FedeGueli
Copy link
Author

+1 Israel

@FedeGueli FedeGueli changed the title LB.1.3 second FULL QUAD ( DEFLiRT+ S:T572I) lineage (6 Isr, Us, UK) LB.1.3 second FULL QUAD ( DEFLiRT+ S:T572I) lineage (11 Isr, Us, UK) Jun 17, 2024
@Memorablea
Copy link

PING

@FedeGueli FedeGueli changed the title LB.1.3 second FULL QUAD ( DEFLiRT+ S:T572I) lineage (11 Isr, Us, UK) LB.1.3 second FULL QUAD ( DEFLiRT+ S:T572I) lineage (20 Isr, Us, UK, Spain) Jun 30, 2024
@FedeGueli FedeGueli changed the title LB.1.3 second FULL QUAD ( DEFLiRT+ S:T572I) lineage (20 Isr, Us, UK, Spain) LB.1.3 second FULL QUAD ( DEFLiRT+ S:T572I) lineage (33 Isr, Us, UK, Spain) Jul 7, 2024
@FedeGueli
Copy link
Author

FedeGueli commented Jul 7, 2024

33 around 2% in Israel in Mid June @shay671

@xz-keg
Copy link
Contributor

xz-keg commented Jul 10, 2024

Is it MH.1? Does it have C25413T?

@xz-keg
Copy link
Contributor

xz-keg commented Jul 10, 2024

It seems that the designation of LB.1.3.2 and MH.1 are ambigious. They follow C24844T instead of C25413T. There is a large C24844T branch of LB.1.3 so MH.1 shall follow that branch.

For this proposal (Pure LB.1.3+S:T572I) I think we shall add -24844 to the query to separate from LB.1.3.2 and MH.1.
This gives only 3 seqs but sequenced very recently, worth keep it open.

@FedeGueli

image

@FedeGueli
Copy link
Author

i am checking too. i have some doubt also on LB.1.8 i will be back when finishing the analysis

@FedeGueli
Copy link
Author

No no @aviczhl2 this proposal is for the entire S:T572I branch not for one part of it i don't get why this had been designated so deep in the tree leaving out a big chunk of the lineage:
Screenshot 2024-07-10 alle 15 43 08
https://nextstrain.org/fetch/genome-test.gi.ucsc.edu/trash/ct/subtreeAuspice1_genome_test_5d24d_e8da00.json?c=gt-nuc_25413&gmax=26413&gmin=24413&label=id:node_7193672

consider there is no LB.1.3 branch otuside this with C25413T so it is hard to get why not designasting everything from S:T572I ahead or at least from C24844T cc @corneliusroemer @AngieHinrichs

FedeGueli referenced this issue in cov-lineages/pango-designation Jul 10, 2024
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

4 participants