COVID-19 Records

Chat message

Slack / Private Message Drop, p.460 [SLACK_000674] · slack_pm:msg:04778

Page text: p.460 · original PDF

Date
2021-01-28 10:37
Type
chat message · slack
recipient
Kristian G. Andersen, Edward C. Holmes, Andrew Rambaut
speaker
Robert F. Garry
Topics
Furin cleavage site and molecular features

Recipients on this medium are inferred from channel membership, not per-message addressing.

Here's another look at the spike amino acid alignment. I've highlighted the RBD residues that make RBD contact according to PO1 and the Bloom mutagenesis paper. Somehow I think that Bloom2020 left out E484, but I'll double check that. PO1 predicted residues in green and Bloom contacts in blue highlights. One of the PO1 residues S494 isnot considered a contact residue in Bloom2020 but again needs double checking. GDpango leads with 17/19 similarto SC2 followed by Cambobatcov at a respectable 13/19 and RaTG13 12/19. There are some interesting things going on in the indels particularly tracking GX pango and RatG13 in the NTD. THaibatcov VERY similar to RmYN02. Japan batcov adds a bit more variability in the S1/S2 junction. [shared file(s): image.png]

In context

A single line often inverts meaning once you see what it answers, so neighbouring messages are always shown.

  1. 2021-01-28 10:37 Robert F. Garry
    Here's another look at the spike amino acid alignment. I've highlighted the RBD residues that make RBD contact according to PO1 and the Bloom mutagenesis paper. Somehow I think that Bloom2020 left out E484, but I'll double check that. PO1 predicted residues in green and Bloom contacts in blue highlights. One of the PO1 residues S494 isnot considered a contact residue in Bloom2020 but again needs double checking. GDpango leads with 17/19 similarto SC2 followed by Cambobatcov at a respectable 13/19 and RaTG13 12/19. There are some interesting things going on in the indels particularly tracking GX pango and RatG13 in the NTD. THaibatcov VERY similar to RmYN02. Japan batcov adds a bit more variability in the S1/S2 junction. [shared file(s): image.png]

Full conversation →