Skip to content

Commit

Permalink
Designate HZ.1 (XBB.1.5.68.1, S:K478R, USA, 150 seqs), HZ.2 (ORF1a:H3…
Browse files Browse the repository at this point in the history
…580Y), HZ.3 (ORF1a:I3693T)
  • Loading branch information
corneliusroemer committed Aug 4, 2023
1 parent 9326c3a commit bdb0eef
Show file tree
Hide file tree
Showing 3 changed files with 543 additions and 157 deletions.
3 changes: 3 additions & 0 deletions lineage_notes.txt
696 changes: 539 additions & 157 deletions lineages.csv
1 change: 1 addition & 0 deletions pango_designation/alias_key.json

4 comments on commit bdb0eef

@FedeGueli
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@FedeGueli
Copy link
Contributor

@FedeGueli FedeGueli commented on bdb0eef Aug 28, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

CC @corneliusroemer @AngieHinrichs the bottom branch of HZ.2 seems to come from a recombination with a sublineage of BA.5.3.1: there were 13K sequence of BA.5.3.1* with G28681T, T28693C

here is the tree:

Schermata 2023-08-28 alle 15 55 44

The recombination BP is likely after Orf8:G8* from XBB.1.5.68 and before A28108T - ORF8:Q72L (common to both HZ.1 and HZ.2 but absent in the HZ.2 putative recombinant)
Schermata 2023-08-28 alle 15 57 06

Should i propose it ? Do you think it is worth to get an X name ? althought quite big it is now decreasing and not expanding

Gisaid query : G28681T, T28693C, C11003T, T10721C

146 samples on Gisaid

@AngieHinrichs
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, great observation @FedeGueli! Yes, the loss of A28108T (ORF8:Q72L) on that branch is very confusing for UShER, and it was confusing me as well. 😄 At the moment UShER/matOptimize is placing HZ.1 as a child of HZ.2 with a reversion on 11003 (ORF1ab:3580), instead of as a sibling -- but it would be better if the tree had A28018T before the HZ.1/HZ.2 split and then C11003T only on HZ.2, with a reversion on 28018 for HZ.2's recombinant branch!

@FedeGueli
Copy link
Contributor

@FedeGueli FedeGueli commented on bdb0eef Aug 28, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, great observation @FedeGueli! Yes, the loss of A28108T (ORF8:Q72L) on that branch is very confusing for UShER, and it was confusing me as well. 😄 At the moment UShER/matOptimize is placing HZ.1 as a child of HZ.2 with a reversion on 11003 (ORF1ab:3580), instead of as a sibling -- but it would be better if the tree had A28018T before the HZ.1/HZ.2 split and then C11003T only on HZ.2, with a reversion on 28018 for HZ.2's recombinant branch!

Thank you Angie , (also my usher tree was unrelated sorry) that would be wonderful to get ( sincerely i didnt notice the HZ.1 reversion!).

cc @corneliusroemer should i open an issue or you or Angie will manage it directly if worth?

Please sign in to comment.