@MonaRahalkar @Daoyu15 @babarlelephant @Drinkwater5Reed @idomyownexpts @AntGDuarte @Rossana38510044 @jhouse678 @daoyu But we would know a few things:
- ancestor of Ra7896, so, before May-15
- very close to Ra4991, but not Ra4991 (has 5 mutations in 370)
- not the miner's virus
It could be what you mentioned long time ago: other samples. But not initially hidden, but detected very late. Maybe
@MonaRahalkar @Daoyu15 @babarlelephant @Drinkwater5Reed @idomyownexpts @AntGDuarte @Rossana38510044 @jhouse678 @daoyu OTOH, the RBD should come from the mine too. We already know there was one there in April 2012. They eventually found a descendant
@MonaRahalkar @Daoyu15 @babarlelephant @Drinkwater5Reed @idomyownexpts @AntGDuarte @Rossana38510044 @jhouse678 @daoyu A good candidate for WIV15 could be 1 of the 43 samples of Ra from the 3rd trip in April 2013
@MonaRahalkar @Daoyu15 @babarlelephant @Drinkwater5Reed @idomyownexpts @AntGDuarte @Rossana38510044 @jhouse678 @daoyu IIRC, there was a mismatch of 1 sample between the Table 1 and 2 of Ge et al. (2016). And could be due to that... Need to review this
@MonaRahalkar @Daoyu15 @babarlelephant @Drinkwater5Reed @idomyownexpts @AntGDuarte @Rossana38510044 @jhouse678 @daoyu Data provided by WIV is chaotic and inconsistent (as usual). I guess the correct thing is to assume there is 1 Ra missing in April 2013. I always thought it was due to the cheating of Ra3755, but it could be they wanted to hide an isolate (similar to 4991)
@MonaRahalkar @Daoyu15 @babarlelephant @Drinkwater5Reed @idomyownexpts @AntGDuarte @Rossana38510044 @jhouse678 @daoyu We always have the same problem: we need to separate genuine errors (a lot), academic cheating and cover ups. Everything superimposed. Not an easy task
@MonaRahalkar @Daoyu15 @babarlelephant @Drinkwater5Reed @idomyownexpts @AntGDuarte @Rossana38510044 @jhouse678 @daoyu You could be right according to this new theory. I did not see the point of hiding something with (almost) same sequence, but the point was instead that they may be hiding an isolate, which was useless due to a bad RBD, but that had an easy solution... :-(
@MonaRahalkar @Daoyu15 @babarlelephant @Drinkwater5Reed @idomyownexpts @AntGDuarte @Rossana38510044 @jhouse678 @daoyu Imagine my hypothesis is right: SARS-CoV-2 comes from an infectious clone, whose backbone is very close to Ra4991. What would you see in a simplot? Here a real example comparing with the exact backbone (based on Menachery et al. (2015) infectious clone) Image
@MonaRahalkar @Daoyu15 @babarlelephant @Drinkwater5Reed @idomyownexpts @AntGDuarte @Rossana38510044 @jhouse678 @daoyu After outbreak is known, they are forced to publish complete genome of Ra4991 (partial RdRp published in 2016). So, how to fabricate a Ra4991 distant enough and hiding recombination while credible?: they limit themselves to use only real aa seqs (due to protein folding problem?)
@MonaRahalkar @Daoyu15 @babarlelephant @Drinkwater5Reed @idomyownexpts @AntGDuarte @Rossana38510044 @jhouse678 @daoyu The RdRp, a well conserved part, can be solved using Ra7896. Although some Ra79XX are probably more distant, Ra7896 is not far enough to contrast with the 370 nt of Ra4991. The RBD could be a 3rd RBD between Ra4991 and Ra79XX
@MonaRahalkar @Daoyu15 @babarlelephant @Drinkwater5Reed @idomyownexpts @AntGDuarte @Rossana38510044 @jhouse678 @daoyu What else you can do to hide the recombination?
- swap other segments with similar viruses when possible
- smooth jumps adding noise with synonym mutations
And in the simplot?
- remove gridline to hide peaks near 100%
- increase window size of simplot
- smash & stretch the graph ImageImage
@MonaRahalkar @Daoyu15 @babarlelephant @Drinkwater5Reed @idomyownexpts @AntGDuarte @Rossana38510044 @jhouse678 @daoyu @quay_dr It would be great is someone can draw a kind of simplot of:
1. dN/dS
2. percentage of codon coincidence (when aa matches)
I am not sure if this kind of plots exists, but should not be difficult to draw

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with Francisco de Asis

Francisco de Asis Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @franciscodeasis

14 Feb
[Thread] Pangolin CoV... or Bat CoV in pangolins samples?
TLDR: A researcher of the team that sequenced the pangolins samples had taken samples in the mine of RaTG13 and in the place where RmYN02 was collected, also catched bats in Yunnan. Probably contaminated pangolin samples
@Daoyu15 was the first to note that the raw sequence reads of the pangolins “contained unexpected reads and was in serious risk of contamination” in early June 2020. But now we can explain how it was possible to happen this in Guangdong
zenodo.org/record/4450267…
Jin-Ping Chen, the corresponding author of the first paper of the pangolins, and LiBiao Zhang, who has been sampling the mine of RaTG13 and the place in Mengla where RmYN02 was collected, are close colleagues in GIABR & GIZ
ncbi.nlm.nih.gov/pmc/articles/P…
giz.gd.cn/yjdw_/yjy/
Read 10 tweets
14 Feb
[Thread] Unnoticed Lab contamination in the samples of first COVID-19 infected patients.
1/ Article: “There was a simultaneous undetected outbreak of Nipah in Wuhan”

Explanation:
2/ Article: “Non-SARS-CoV-2 genome sequences identified in clinical samples from COVID-19 infected patients”
peerj.com/articles/10246/

Explanation:
Read 4 tweets
4 Feb
Read 12 tweets
2 Feb
@Daoyu15 @Undergroundsar3 @Real_Adam_B @BillyBostickson @Rossana38510044 @luigi_warren @babarlelephant @AntGDuarte @MonaRahalkar @flavinkins @KevinMcH3 @DrAntoniSerraT1 @_coltseavers @rowanjacobsen @uacjess @RolandBakerIII @TheSeeker268 @still_a_nerd @jjcouey @Harvard2H @ydeigin @CarltheChippy @ico_dna @nerdhaspower @scottburke777 @JJ2000426 @BahulikarRahul @alimhaider @antonioregalado @Ayjchan @R_H_Ebright @BretWeinstein @sanchak74 @JCalvertST @PeterDaszak @TheSeeker @nature @threadreaderapp Max Genbank ID (GI) by Modification date in nuccore:
Jan 07th: 1,790,159,865
Jan 08th: 1,791,050,251
Jan 09th: 1,791,354,567
Jan 10th: 1,794,858,040
Jan 11th: 1,795,744,542
Jan 12th: 1,796,141,132

MN908947 (Wuhan-Hu-1): 1,791,269,088
So, created on Jan 9th, or even on Jan 8th
Read 7 tweets
27 Jan
@nature cc reviewer @c_drosten, this article must be corrected to acknowledge that SADSr-CoV 3755 was from the same mine of Mojiang (Yunnan) as RaTG13. Any reader of the paper thinks it came from Guangdong, and that is not true nature.com/articles/s4158…
As you see, its ID is in the middle of the IDs of the 1st trip of WIV to the mine (Ge et al, 2016).
Obviously, disclosing its full sequence is also a must, not only the N. Image
Wang et al. (2019) stated it was from Yunnan in their Fig 1.
Ra7347 most probably from the mine too. And 140351 too (they messed samples of May-14)
With so many errors, lack of info, cheatings and covers, the phylogenetic trees are totally useless! Shame
ncbi.nlm.nih.gov/pmc/articles/P… Image
Read 4 tweets
28 Nov 20
@Rossana38510044 @luigi_warren @babarlelephant @AntGDuarte @MonaRahalkar @BillyBostickson @flavinkins @KevinMcH3 @DrAntoniSerraT1 @_coltseavers @rowanjacobsen @uacjess @RolandBakerIII @TheSeeker268 @Daoyu15 @still_a_nerd @jjcouey @Harvard2H @ydeigin @CarltheChippy @ico_dna @Nomdeplumi1 @Real_Adam_B @nerdhaspower @scottburke777 @JJ2000426 @BahulikarRahul @alimhaider @antonioregalado @Ayjchan @R_H_Ebright @BretWeinstein @sanchak74 @JCalvertST [Thread] Addendum of WIV in Nature.
What we know about the samples and the visits to the mineshaft of TG?
TLDR: 7 trips: 4 already known (Ge et al., 2016), plus other 3 with massive sampling until 2015, including 7896-clade. All already in Latinne et al. (2020)
#originsofSARSCoV2
Read 38 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!

Follow Us on Twitter!