Closed NkRMnZr closed 11 months ago
Is it a single chronic patient?
Is it a single chronic patient?
Dunno, metadata only specified
Sampling strategy: | Surveillance
but it could be wrong
The shape of the tree makes me think it is a chronic infection, but having the FLip it has to be monitored closely: This is the picture of the last sample. @thomaspeacock do you think S:P681Y could still permit the furin cleavage? sequence: SYQTQTKSYRRARSVASQ
@thomasppeacock tagging the correct username
I think it would be less efficient - maybe even inhibited due to the bulky amino acid? might fit with it being a chronic?
I feel pretty certain these are from a single individual, both because of the shape of the Usher tree and because of the time distribution of the collection dates, which suggest a patient with a known chronic infection being sampled every few months. Below is an annotated Nextclade view of the ~400-520 residues of spike for the six sequences associated with this variant—all in chronological order.
There are a couple interesting things worth noting. First, unlike the FLip variants currently growing (and which, IMO, will become dominant if BA.2.86 doesn't steamroll them all), this one got L455F first, then F456L. We've seen L455F without F456L previously, so it's not surprising to learn that FLip can be acquired through both routes.
Second, this BA.4.6 traced two patterns that have become extremely common in recent BA.4/5 chronic-infection sequences: reversions at 484 and 486. In this particular case, after the A484E reversion, it moved on to E484V. It's common for chronic-infection variants to trace out patterns that are later repeated in circulating variants. Does the current incipient 484K comeback indicate the beginning, at a population level, of the same sort of unfavorable environment for E484A that we've seen in chronically infected individuals?
@thomasppeacock tagging the correct username
really is that? tagged him wrongly hundred of times.
I think it would be less efficient - maybe even inhibited due to the bulky amino acid? might fit with it being a chronic?
Thx Tom
@thomasppeacock tagging the correct username
really is that? tagged him wrongly hundred of times.
Afraid so! feel free to re-tag me in if theres any ongoing stuff thats relevent - finding it hard to keep on top of the github stuff these days!
@thomasppeacock tagging the correct username
really is that? tagged him wrongly hundred of times.
Afraid so! feel free to re-tag me in if theres any ongoing stuff thats relevent - finding it hard to keep on top of the github stuff these days!
Thx really i think sometimes i got it right copying&pasting from some issue u commented but then i went by memory and i missed the P insertion ;)
No new sequence.
Defining Mutations:
BA.4.6
>T23449C
>A13809C
>G625T(ORF1a:K120N)
>G521T(ORF1a:V86F), ins688_CAT(ORF1a:ins_141H), G22927T(S:L455F)
Query:G521T, G22927T,A13809C
Earliest seq:2022-09-14
(EPI_ISL_15118346) Latest seq:2023-08-08
(EPI_ISL_18129944) Sampled Countries: SwitzerlandGenomes:
`EPI_ISL_15118346, EPI_ISL_16669313, EPI_ISL_17475799, EPI_ISL_17831941, EPI_ISL_18129944`UShER: https://nextstrain.org/fetch/raw.githubusercontent.com/NkRMnZr/hSC2-Tracking-Log/main/JSON/EPI_ISL_18129944%20BA.4.6%2BL455F%2BF456L_Cluster_Switzerland.json?label=id%3Anode_8183846
view from
BA.4.6
polytomyT23449C
branch diversitydetails
Trivia:
S:L455F
first rather thanS:F456L
, on aBA.4
backbone with ACE2-binding affinity sacrificialS:F486V
, don't know how much binding affinity is left there, but it can still later gainS:F456L
and a reversion ofS:V486F
, which will largely improve it.