23B (XBB.1.16) is now available on CoVariants! It's visible as part of Per Country & Per Variant plots, on the shared mutation page - and of course, has a page of its own.
As I covered earlier, 23B (XBB.1.16) is descended from the recombinant 22F (XBB) variant, with some additional mutations. You can read more about how it evolved & acquired those mutations below 👇🏻.
On the 23B page, you can read about some initial 23B (XBB.1.16) work on neutralizing titres, see a list of defining mutations, a plot of the variant growth, link to Aquaria protein viz, & see a list of other mutations present in the variant.
On the Per Country page, 23B (XBB.1.16) is already clearly visible in India & Singapore, & is starting to appear in smaller numbers in other countries, like Australia & the US. Remember, sequencing data is always a few weeks behind.
Finally, on the Shared Mutations page, you can see how 23B's / XBB.1.16's Spike mutations compare to other VoC, including its Omicron family, 22F (XBB) parent, and its 'sibling' 23A / XBB.1.5.
More information on 23B (XBB.1.16) & its spread will become available in due course.
As always, CoVariants.org is open-source & we welcome your PRs & suggestions to add more studies & information to variant pages! (Or any error-catching!)
As before, I've created a file for 23B (XBB.1.16) mapping all defining mutations (relative to ancestral), including nuc->AA. This is available on the CoVaritants Github!
The eagle-eyed among you will have noticed that I've adjusted the 23A colour when adding 23B - the colours were probably always a bit too close together but this became even more obvious with 23B. I hope it doesn't cause any confusion! 🌈
10/10
• • •
Missing some Tweet in this thread? You can try to
force a refresh
Also from this article:
'Marion Koopmans ... says she has received multiple calls from Bogner“with a rather intimidating tone.” So have colleagues, she adds. “I have heard similar experiences from quite a few.”'
And:
"And Science heard many stories about researchers who saw their data curtailed, or cut off, without explanation. Some linked the actions to their being critical of GISAID or being seen as a potential threat."
If you're an early career researcher (yes even 'just' a PhD student!) 1 of my biggest pieces of advice would be:
Go claim/create your Google Scholar page!! 👈🏻✍️🏻
I put this off bc I thought I 'didn't have enough on it'. I also generally thought "nobody is looking for me".
1/4
Now that I'm (a little) on the other end, I see how wrong I was.
It's *just fine* to not have "much" in your Google Scholar profile - anyone worth their salt will be evaluating you relative to your career state.
Much more important: to be findable!
2/4
And alongside that: it's so useful to have an easy way for people to see what your field is & what you've been up to/who you work with/your expertise.
Google Scholar is also pretty easy to maintain (will vary depending on how unique your name is), as it auto-updates.
3/4
23A (XBB.1.5) is now available on CoVariants! It's visible as part of Per Country & Per Variant plots, on the shared mutation page - and of course, has a page of its own.
As I covered earlier, 23A (XBB.1.5) is descended from the recombinant 22F (XBB) variant, with some additional mutations. You can read more about how it evolved & acquired those mutations below 👇🏻.
The recombinant XBB is shown as having mutation S:F486S (inc on CoVariants.org), from parent BM.1.1.1 - but looking at BM.1.1.1* now, it seems to have mostly S:486P!
So did XBB really get 486S?
Looking at "Mutations over time", we can see really nicely that BM.1.1.1* was mostly S:486S earlier, then 486P later - likely a daughter lineage outgrowing 'original' BM.1.1.1!
2/5
Indeed, daughter lineage CJ.1 has 100% S:486P and has been growing since Oct 22, when we see that switch. cov-spectrum.org/explore/World/…
Similarly, looking at BM.1.1.1 (no star - so no descendants), show it has 96% S:486S & declined in Oct. cov-spectrum.org/explore/World/…
3/5
Wonderful to be back in #Wengen last night for the @ISPMBern#SwissEpiWinterSchool - to talk about Wengen! Specifically, the Alpha #SARSCoV2 outbreak in Dec 20 - Feb 21 - bringing together 3 different data sources! Alongside @nicolamlow Chris Kosok @JulRiou! 1/4
Thanks to tireless work of many, the #Wengen outbreak was swiftly identified & action was taken. Chris' field observations, cantonal teams of contact tracers, & of course testers & sequencers, mean we're able to bring together sequences, contacts, & observations for analysis! 2/4
The ability to overlay these three types of connections (an example shown below) means we are able to see how multiple layers can contribute to our understanding of the outbreak, & compare the strengths & shortcomings of different approaches! 3/4
Well, after almost 3 years of a dizzy dodging dance - #SARSCoV2 finally got me last week. 🦠🤒 Happy to say I'm on the road to recovery now! 🛣️
It seems many of us 'hold outs' have been caught out in the last few weeks - be safe out there this Xmas!
1/5
I've generally been quite careful, but with the resumption of in-person meetings (& all the activities that go along, like dinners & aperos!), there was always a risk - one I accepted knowingly. I think online working is great TBH, but in-person really is different.
2/5
To pre-empt some comments I know I'll get, I'm being open about getting #COVID19 because being open is something I've always tried to do! We're all trying to make the best decisions for ourselves, our risk levels, our health, & our lifestyles in a complex world.
3/5