-
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
HV.1 Spike Diversity Collection (UPDATED 2024-02-21) #957
Comments
Thank you great work. |
K41E 4 to 6 |
Lets wait they hit 40 sequences before proposing them (704L, 1264L 1265F) . Great work @krosa1910 |
HV.1 has picked S:494P too |
Yeah, I would update that sometime this week, also L452W is deserving tracking. |
@krosa1910 please propose the S:704L branch and the S:514F branch and the S:V1264L branch |
Please propose also the S:L1265F and the S:A1078S. while keeping 493L and 1162S monitored. thank you. |
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 |
ping @corneliusroemer please take a look there is some interesting spike diversity in HV.1 that grew over the 100 seqs. |
S:S514F has been designated HV.1.2 via cov-lineages/pango-designation@471889e |
@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:L1265F designated HV.1.5 via cov-lineages/pango-designation@4813e2f |
S:S704L designated HV.1.6.1 via cov-lineages/pango-designation@ffdf027 |
S:S221L designated HV.1.7 via cov-lineages/pango-designation@57891f2 |
Should be |
Thank you edited everywhere now. |
@corneliusroemer S:Q493L maybe deserves a designation. around 100 sequences and widespread |
Thank you missed that was the same here. |
Will try to update this issue, as I think HV.1* is still not over yet. |
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. |
Thank you great update! please track 148T too! |
Thanks @krosa1910 greeat work. |
S:L452W already proposed in #1044 |
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 |
this has been designated HV.1.9 via cov-lineages/pango-designation@f6e4c4f |
This one with the query : C3924T, C12295A,C23280T counts 53, please propose it. |
Sorry for my laptop crashing that inhibited this update, i will "reupdate" today. |
Thanks @krosa1910 |
Yesterday i proposed #1338 335S 403K in Aus. |
(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. |
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 |
i ve checked growing lineages, it seems to me very hard times for all of them in January. |
There is a HV.1 Flip lineage not listed here that managed to criculate in January: Defining mutations: |
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. |
Agree thanks great work by now |
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. |
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. |
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
Past Watches (I JUST DELETED THE STILL WATCHING ONES)
Trees of current stuff
Now Watching Trees
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
S:K147I+S:E619Q tree
https://nextstrain.org/fetch/genome.ucsc.edu/trash/ct/singleSubtreeAuspice_genome_93d8_5992c0.json?f_userOrOld=uploaded%20sample
S:N148 tree
https://nextstrain.org/fetch/genome.ucsc.edu/trash/ct/singleSubtreeAuspice_genome_b9a1_599cb0.json?f_userOrOld=uploaded%20sample
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
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
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
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
S:T307I tree
https://nextstrain.org/fetch/genome.ucsc.edu/trash/ct/singleSubtreeAuspice_genome_a558_59f860.json?f_userOrOld=uploaded%20sample
S:I410V+S:H1101Q tree
https://nextstrain.org/fetch/genome.ucsc.edu/trash/ct/singleSubtreeAuspice_genome_114a2_5a0b00.json?f_userOrOld=uploaded%20sample
S:L455F tree
https://nextstrain.org/fetch/genome.ucsc.edu/trash/ct/singleSubtreeAuspice_genome_12c20_5a11b0.json?f_userOrOld=uploaded%20sample
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
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
S:P681R tree
https://nextstrain.org/fetch/genome.ucsc.edu/trash/ct/singleSubtreeAuspice_genome_1ba0_5ab050.json?f_userOrOld=uploaded%20sample>=nuc.22930A,S.356K&label=id:node_1022987
S:S939F tree
https://nextstrain.org/fetch/genome.ucsc.edu/trash/ct/singleSubtreeAuspice_genome_4c0f_5b47f0.json?f_userOrOld=uploaded%20sample>=S.252V
S:H1101Y tree
https://nextstrain.org/fetch/genome.ucsc.edu/trash/ct/singleSubtreeAuspice_genome_cf1_5b8850.json?f_userOrOld=uploaded%20sample
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
S:V1264L tree
https://nextstrain.org/fetch/genome.ucsc.edu/trash/ct/singleSubtreeAuspice_genome_e352_5bbdb0.json?f_userOrOld=uploaded%20sample
The text was updated successfully, but these errors were encountered: