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

HV.1 Spike Diversity Collection (UPDATED 2024-02-21) #957

Closed
46 of 63 tasks
krosa1910 opened this issue Oct 15, 2023 · 42 comments
Closed
46 of 63 tasks

HV.1 Spike Diversity Collection (UPDATED 2024-02-21) #957

krosa1910 opened this issue Oct 15, 2023 · 42 comments

Comments

@krosa1910
Copy link

krosa1910 commented Oct 15, 2023

HV.1* is a mystery to me, so I would like to create this colleciton of its Spike Diversity to see if there is an underlying reason behind its success in North America.

Standardized way of this search: C5835T,T22917G,T22930A for HV.1* parent.

Dead/Small/Proposed Observations

Preview Give feedback

Past Watches (I JUST DELETED THE STILL WATCHING ONES)

Preview Give feedback

Trees of current stuff

Now Watching Trees

Preview Give feedback

S:98F tree
https://nextstrain.org/fetch/genome.ucsc.edu/trash/ct/singleSubtreeAuspice_genome_17854_596060.json?f_userOrOld=uploaded%20sample&label=id:node_1022987
Screenshot 2024-02-21 at 2 31 27 PM

S:K147I+S:E619Q tree
https://nextstrain.org/fetch/genome.ucsc.edu/trash/ct/singleSubtreeAuspice_genome_93d8_5992c0.json?f_userOrOld=uploaded%20sample
Screenshot 2024-02-21 at 2 33 53 PM

S:N148 tree
https://nextstrain.org/fetch/genome.ucsc.edu/trash/ct/singleSubtreeAuspice_genome_b9a1_599cb0.json?f_userOrOld=uploaded%20sample
Screenshot 2024-02-21 at 2 40 33 PM

S:G184V tree
https://nextstrain.org/fetch/genome.ucsc.edu/trash/ct/singleSubtreeAuspice_genome_1390a_59b6d0.json?f_userOrOld=uploaded%20sample&label=id:node_1035383
Screenshot 2024-02-21 at 2 44 30 PM

S:G184S tree
https://nextstrain.org/fetch/genome.ucsc.edu/trash/ct/singleSubtreeAuspice_genome_3d18f_59c540.json?f_userOrOld=uploaded%20sample&label=id:node_1025408
Screenshot 2024-02-21 at 2 48 25 PM

S:S221L tree
https://nextstrain.org/fetch/genome.ucsc.edu/trash/ct/singleSubtreeAuspice_genome_42cf9_59d7a0.json?f_userOrOld=uploaded%20sample&label=id:node_1025408
Screenshot 2024-02-21 at 2 52 40 PM

S:D253E tree
https://nextstrain.org/fetch/genome.ucsc.edu/trash/ct/singleSubtreeAuspice_genome_20f8_59e350.json?f_userOrOld=uploaded%20sample&label=id:node_1025409
Screenshot 2024-02-21 at 2 55 24 PM

S:T307I tree
https://nextstrain.org/fetch/genome.ucsc.edu/trash/ct/singleSubtreeAuspice_genome_a558_59f860.json?f_userOrOld=uploaded%20sample
Screenshot 2024-02-21 at 3 02 16 PM

S:I410V+S:H1101Q tree
https://nextstrain.org/fetch/genome.ucsc.edu/trash/ct/singleSubtreeAuspice_genome_114a2_5a0b00.json?f_userOrOld=uploaded%20sample
Screenshot 2024-02-21 at 3 05 36 PM

S:L455F tree
https://nextstrain.org/fetch/genome.ucsc.edu/trash/ct/singleSubtreeAuspice_genome_12c20_5a11b0.json?f_userOrOld=uploaded%20sample
Screenshot 2024-02-21 at 3 15 35 PM

S:G482R tree
https://nextstrain.org/fetch/genome.ucsc.edu/trash/ct/singleSubtreeAuspice_genome_300bc_5a1450.json?f_userOrOld=uploaded%20sample&label=id:node_1025408
Screenshot 2024-02-21 at 3 09 28 PM

S:T573I tree
https://nextstrain.org/fetch/genome.ucsc.edu/trash/ct/singleSubtreeAuspice_genome_2530c_5a4ae0.json?f_userOrOld=uploaded%20sample&label=id:node_1027082
Screenshot 2024-02-21 at 3 47 55 PM

S:P681R tree
https://nextstrain.org/fetch/genome.ucsc.edu/trash/ct/singleSubtreeAuspice_genome_1ba0_5ab050.json?f_userOrOld=uploaded%20sample&gt=nuc.22930A,S.356K&label=id:node_1022987
Screenshot 2024-02-21 at 4 27 16 PM

S:S939F tree
https://nextstrain.org/fetch/genome.ucsc.edu/trash/ct/singleSubtreeAuspice_genome_4c0f_5b47f0.json?f_userOrOld=uploaded%20sample&gt=S.252V
Screenshot 2024-02-21 at 4 39 30 PM

S:H1101Y tree
https://nextstrain.org/fetch/genome.ucsc.edu/trash/ct/singleSubtreeAuspice_genome_cf1_5b8850.json?f_userOrOld=uploaded%20sample
Screenshot 2024-02-21 at 4 51 25 PM

S:Q1201K tree
https://nextstrain.org/fetch/genome.ucsc.edu/trash/ct/singleSubtreeAuspice_genome_d481_5bb670.json?f_userOrOld=uploaded%20sample&label=id:node_1025408
Screenshot 2024-02-21 at 5 00 15 PM

S:V1264L tree
https://nextstrain.org/fetch/genome.ucsc.edu/trash/ct/singleSubtreeAuspice_genome_e352_5bbdb0.json?f_userOrOld=uploaded%20sample
Screenshot 2024-02-21 at 5 04 13 PM

@FedeGueli
Copy link

Thank you great work.

@krosa1910
Copy link
Author

krosa1910 commented Oct 18, 2023

K41E 4 to 6
S704L 21 to 26
V1264L 23 (22+1( to 37 (34+2+1)
V16F 9(8+1) to 11(10+1)
S94F 5(3+2) to 6 (4+2)
N148T 5 to 6
W152R 3 to 5
N185S 13 to 14
S221L 8(6+1+1) to 9(6+2+1)
I410V 9 to 10
L938F 3 to 4
L1265F 17 to 23
I would say S704L and S1265F is worthing a proposal, maybe also V1264L(with caution about Canadian cluster) and N185S

@FedeGueli
Copy link

FedeGueli commented Oct 18, 2023

Lets wait they hit 40 sequences before proposing them (704L, 1264L 1265F) . Great work @krosa1910

@RajLABN
Copy link

RajLABN commented Oct 24, 2023

HV.1 has picked S:494P too
5 sequences (NY, CA USA)
EPI_ISL_18316940, EPI_ISL_18379501, EPI_ISL_18404330,
EPI_ISL_18410315-18410316

@krosa1910
Copy link
Author

Yeah, I would update that sometime this week, also L452W is deserving tracking.

@FedeGueli
Copy link

@krosa1910 please propose the S:704L branch and the S:514F branch and the S:V1264L branch

@FedeGueli FedeGueli added the To be proposed Green light for proposal label Nov 20, 2023
@FedeGueli
Copy link

FedeGueli commented Nov 20, 2023

Please propose also the S:L1265F and the S:A1078S. while keeping 493L and 1162S monitored. thank you.

@FedeGueli
Copy link

You can also on Pango a multiple issue saying these are the spike mutated branches of HV.1 if any of them has interest to be diesignated and etc etc

@FedeGueli
Copy link

ping @corneliusroemer please take a look there is some interesting spike diversity in HV.1 that grew over the 100 seqs.

FedeGueli referenced this issue in cov-lineages/pango-designation Nov 24, 2023
@FedeGueli
Copy link

S:S514F has been designated HV.1.2 via cov-lineages/pango-designation@471889e

@FedeGueli FedeGueli added partially designated and removed To be proposed Green light for proposal labels Nov 24, 2023
@FedeGueli FedeGueli added this to the HV.1.2 milestone Nov 24, 2023
@FedeGueli
Copy link

@corneliusroemer the author cannot connect in this moment to internet so i updatted the issue flagging the ones you may want to evaluate for designation.
S:704L S:1078S S:493L and S:1265F are already big enough to be designated. please when u save a minute to look at these ones.

FedeGueli referenced this issue in cov-lineages/pango-designation Dec 2, 2023
@FedeGueli
Copy link

FedeGueli commented Dec 2, 2023

S:L1265F designated HV.1.5 via cov-lineages/pango-designation@4813e2f

@FedeGueli
Copy link

S:S704L designated HV.1.6.1 via cov-lineages/pango-designation@ffdf027

@FedeGueli
Copy link

S:S221L designated HV.1.7 via cov-lineages/pango-designation@57891f2

@NkRMnZr
Copy link

NkRMnZr commented Dec 3, 2023

S:S1265F designated HV.1.5 via cov-lineages/pango-designation@4813e2f

Should be L1265F not S

@FedeGueli
Copy link

S:S1265F designated HV.1.5 via cov-lineages/pango-designation@4813e2f

Should be L1265F not S

Thank you edited everywhere now.

FedeGueli referenced this issue in cov-lineages/pango-designation Dec 6, 2023
@FedeGueli
Copy link

@corneliusroemer S:Q493L maybe deserves a designation. around 100 sequences and widespread

@FedeGueli
Copy link

@corneliusroemer S:Q493L maybe deserves a designation. around 100 sequences and widespread

it has already been designated #924

Thank you missed that was the same here.

@krosa1910
Copy link
Author

Will try to update this issue, as I think HV.1* is still not over yet.

@krosa1910
Copy link
Author

krosa1910 commented Dec 22, 2023

HV.1* now is very big, at over 28k on Gisaid, yet it is starting to lose momentum, so something at levels of 3 seq seems less interesting now. Thus I decided to find some newer branches and replace old ones.
Basically, any old branch under 30 sequences/ about 0.1% total samples are shut, while I would open some new ones at 30+ seqs.
So in total, I am watching Q1208H, V16F, S98F, W152R, I410V/H1101Q, G1124S, P1162L, Q1201K and I think V1264L,N148T and T208M could be proposed. Others are shut down as they doesn't seem to show dominance over parent given time like two months.
I will now consider the following candidates (after bogging down some valid trees that is)
H49Y,T95I,M153I,G184V,V227I,D253E,L455F,T470I,T573I,E619Q,V642G,P/H681R(under T208M),Q836L,S939F, H1101Y, K1245R, S12F S31F(N148Q,K150V,E154V seemed to be related to deletions or frameshift in S protein and not very good qualities, which I am not familiar with and profound of, so I ignore those but encourage others to look at those), N185S,N211I+T1117I,A222S,T307I,R357K,L/R452W,F/S490P(under A1078S=HV.1.4*),T553I,T572I,V656I
Also 478 and 554 are weird, while H245Y and N450D seems to rise recently despite not reaching 30 yet, people could start investigating it if they want.

@FedeGueli
Copy link

HV.1* now is very big, at over 28k on Gisaid, yet it is starting to lose momentum, so something at levels of 3 seq seems less interesting now. Thus I decided to find some newer branches and replace old ones. Basically, any old branch under 30 sequences/ about 0.1% total samples are shut, while I would open some new ones at 30+ seqs. So in total, I am watching Q1208H, V16F, S98F, W152R, I410V/H1101Q, G1124S, P1162L, Q1201K and I think V1264L and T208M could be proposed. Others are shut down as they doesn't seem to show dominance over parent given time like two months. I will now consider the following candidates (after bogging down some valid trees that is) Y49H, T95I, M153I,M153K G184V, V227I, D253E , L455F,T470I , T573I, E619Q, V642G, P681R, Q836L, S939F, H1101Y, Q1208H, K1245R, S12F S31F, N148Q, K150V, E154V, N185S, N211I, Also 478 and 554 are weird, and people could start investigating it if they want. While N450D and L455F seems to rise recently.

Thank you great update! please track 148T too!

@FedeGueli
Copy link

Thanks @krosa1910 greeat work.
Please propose S:N148T and the S:t208M+681R one. thank you.

@FedeGueli
Copy link

S:L452W already proposed in #1044

@krosa1910
Copy link
Author

Thanks @krosa1910 greeat work. Please propose S:N148T and the S:t208M+681R one. thank you.

N148T seems too sparse and can be only proposed in the multiple trees manner, T208M+681R seems good enough though.

@FedeGueli
Copy link

Thanks @krosa1910 greeat work. Please propose S:N148T and the S:t208M+681R one. thank you.

N148T seems too sparse and can be only proposed in the multiple trees manner, T208M+681R seems good enough though.

Thx if not monophyletic better wait! Thx

@FedeGueli
Copy link

FedeGueli commented Jan 9, 2024

S:N211I, S:T1117I, New Zealand>

this has been designated HV.1.9 via cov-lineages/pango-designation@f6e4c4f

FedeGueli referenced this issue in cov-lineages/pango-designation Jan 9, 2024
@krosa1910 krosa1910 changed the title HV.1 Spike Diversity Collection HV.1 Spike Diversity Collection (UPDATED 2024-01-14) Jan 14, 2024
@FedeGueli
Copy link

S:T573I https://nextstrain.org/fetch/genome.ucsc.edu/trash/ct/singleSubtreeAuspice_genome_d962_fe34d0.json?f_userOrOld=uploaded%20sample Screenshot 2023-12-30 at 4 31 26 AM

This one with the query : C3924T, C12295A,C23280T counts 53, please propose it.

@krosa1910 krosa1910 changed the title HV.1 Spike Diversity Collection (UPDATED 2024-01-14) HV.1 Spike Diversity Collection (UPDATED 2024-01-25) Jan 25, 2024
@krosa1910
Copy link
Author

krosa1910 commented Jan 25, 2024

Sorry for my laptop crashing that inhibited this update, i will "reupdate" today.
Thinking about the JN.1* boom, I would consider a new rule now. Some HV.1* can have like a cluster of 70 seqs but if it does not show up lately I still consider it to lose the race ultimately, while for some "newer" faces can be at 30 seqs does not limit their potential.
Thus the new rule now would consider two parts, part 1 is for mutations that gains presence within the last 30 days (sequencing since 12-25) with some decent size (30+ seqs) while part 2 is for mutations that are large enough (50+ mono tree) despite not in the recent samples.

@FedeGueli
Copy link

Thanks @krosa1910

@FedeGueli
Copy link

Yesterday i proposed #1338 335S 403K in Aus.

@krosa1910
Copy link
Author

(Range:140-146)del is really weird. I have asked people things about it months ago yet I don't get a definitive answer so I would ignore them.

@FedeGueli
Copy link

(Range:140-146)del is really weird. I have asked people things about it months ago yet I don't get a definitive answer so I would ignore them.

yes it is. the 144del makes a mess in reading the sequence in that part. For a long while i suspected that also S:N148T was affected by something similar.

@krosa1910
Copy link
Author

krosa1910 commented Jan 26, 2024

A lot of E554X+HV.1*, maybe deserving a new issue (if not for the fact that HV.1* is now falling considerably, yet it is still like twice as large as BA.2.86* without L455S or thrice as large as JD.1.1*/JG.3*) If some more experienced individuals like @NkRMnZr NK can help me then probably I could sort it out.

@FedeGueli
Copy link

A lot of E554X+HV.1*, maybe deserving a new issue (if not for the fact that HV.1* is now falling considerably, yet it is still like twice as large as BA.2.86* without L455S or thrice as large as JD.1.1*/JG.3*) If some more experienced individuals like @NkRMnZr NK can help me then probably I could sort it out.

good idea lets wait next week to see how it goes in January

@FedeGueli
Copy link

i ve checked growing lineages, it seems to me very hard times for all of them in January.

@FedeGueli
Copy link

FedeGueli commented Feb 16, 2024

There is a HV.1 Flip lineage not listed here that managed to criculate in January:
Screenshot 2024-02-16 alle 23 17 31
https://nextstrain.org/fetch/genome-test.gi.ucsc.edu/trash/ct/subtreeAuspice1_genome_test_1bc88_fdd4c0.json?c=userOrOld&label=id:node_3597976

Defining mutations:
HV.1 > C10279T > Orf1a:A3688V (C11328T) > Orf1a:I1203T (T3873C), S:L455F (G22927T),N:G214S (G28913A)
Query: T3873C,G28913A
Samples: 13 as of 16/02/2024
Countries:
Screenshot 2024-02-16 alle 23 22 04

@krosa1910
Copy link
Author

krosa1910 commented Feb 20, 2024

Yep, I think I give up this mega lineage collection now. JN.1* sweep everything now, whileHV.1* is not even outcompeting EG.5.1* now( JG.3.2* and GE.1.2.1* seem to lead the last stand of XBB*). This would really be the last update if not for something not miraculous.
New Standard
A. >10seq from 01-01-2024, a arbitrary but self-explainatary threshold I chose for JN.1* total dominance
B. >5 seq from 01-01-2024 and >50seq overall
Things omitted: anything from 140-146del plus anything with Y144 and Y145, S5F, H/Q146K, mutations that seems to be more likely contaminated instead of true (such as V127F, F/L157S, R158G because of JN.1* contamination)

@FedeGueli
Copy link

Agree thanks great work by now

@krosa1910
Copy link
Author

krosa1910 commented Feb 21, 2024

There are 17 final candidates chosen here, I would update on their queries (a general query or a specific one if a main tree fits), T/K478X AND E554X ARE OMITTED BECAUSE THEY ARE TOO MESSY YET STILL HAVING SOME NUMBERS SO I WOULD PROBABLY OPEN TWO NEW ISSUES FOR THEM. I heard L/R452w is also complex due to polytomy plus pollution, maybe also one for it.

@krosa1910 krosa1910 changed the title HV.1 Spike Diversity Collection (UPDATED 2024-01-25) HV.1 Spike Diversity Collection (UPDATED 2024-02-21) Feb 21, 2024
@FedeGueli
Copy link

Thank you for your work here i m closing it now

@FedeGueli FedeGueli closed this as not planned Won't fix, can't repro, duplicate, stale Mar 19, 2024
@krosa1910
Copy link
Author

Thank you for your work here i m closing it now

Yeah, by a crude search XBB* total is only 893/27503, EG.5.1* is 513 and HV.1* is a mere 143, even lower than FLirt being 264. So I don't think this issue is very valuable now, I would turn my effort toward the Flirt one.

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