You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I open an issue to highlight it and to understand what was the intention here:
my guess @corneliusroemer merged for mistake two designations in one and he wanted to designate two lineages:
one with 253G (corresponding to sequences in lineages.csv and the other with 554D corresponding to lineage notes of HN.3.1)
Last night @corneliusroemer designated HN.3.1 :ffa4130
While the defining mutation is shown as S:E554D tha corresponds to an existent sublineage of FL.1.5.1 proposed here: sars-cov-2-variants/lineage-proposals#825
Instead the sequences added in lineages.csv correspond to another FL.1.5.1 sublineage with S:D253G , nproposed here :sars-cov-2-variants/lineage-proposals#383)
I open an issue to highlight it and to understand what was the intention here:
my guess @corneliusroemer merged for mistake two designations in one and he wanted to designate two lineages:
one with 253G (corresponding to sequences in lineages.csv and the other with 554D corresponding to lineage notes of HN.3.1)
cc @AngieHinrichs
Scratch everything it is just a defining mutation typo. sorry.
The text was updated successfully, but these errors were encountered: