-
Notifications
You must be signed in to change notification settings - Fork 98
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
BA.2.75* diversity to watch and designate as soon as phylogeny is clear #961
Comments
Thx @corneliusroemer great work i think when epi-conditions change quickly this kind of multiple issues are very useful. |
@corneliusroemer many thanks! Maybe #963 could be added to the list? All the best! |
I built an UShER tree based around a few BA.2.75+ORF1a:3959A GenBank samples. UShER put that into 2 different branches from BA.2.75. But just in case others may find it helpful in finding BA.2.75 sublineages, here's the link to the interactive tree: https://nextstrain.org/fetch/github.com/alurqu/pango-designation-support-alurqu/raw/main/subtreeAuspice1_BA.2.75_20220818.json?c=gt-S_574&label=nuc%20mutations:C4586T,A22001G. I've set the initial coloring to highlight the BA.2.75.1 S:D574V mutation. Of course, as more data comes in the UShER tree may evolve and shift. Please note that I did include the date in the file name, so I plan for this tree should remain as a record of the UShER tree produced today. As the tree evolves with new data, it may be appropriate to post a new version of the tree. Edit: Corrected grammar. |
We've figured BA.2.75 out now, so this can be closed. |
There is quite a lot of relevant Spike diversity in BA.2.75* that we should try to get designated as soon as the phylogeny is clear.
I'm opening this issue to have one place to coordinate these and tick them off as we progress.
The following are known spike mutations of interest that have occurred multiple times in multiple countries in BA.2.75*
I'll try to link existing issues that discuss the above mutations above. These mutations may have already occurred multiple times independently and/or in a correlated fashion so it's not too easy to sort this out all at one unfortunately.
The text was updated successfully, but these errors were encountered: