-
Notifications
You must be signed in to change notification settings - Fork 6
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
Is B.1.355 a recombinant in sc2ts ARG? #304
Comments
They only have 3 mutations on the LHS, so wouldn't a recombination be unparsimonious according to our k=4 criterion. I guess we could run the B.1.355 samples again using k=3, just to check? |
Here's the match we get with k=3 for the first sample:
which is the same as the match from the ARG:
There's 15 "B.1.355" samples in the ARG which I think neatly inherit from 19560 (I haven't checked they're all B.1.355, though). So, I think the answer is "no" we don't think it's a recombinant. |
Interesting that in the k=3 case there are still 3 mismatches @ 1485 (not in theirs), 1495, and 7313 (not in theirs). We don't have their 7831 mutation in that match. Presumably we either don't have some of their recombinant parents, or we don't have their immediate recombinant child, otherwise we would have found their recombination event with k=3, right? |
Dunno, all seems pretty marginal. |
Turakhia et al. (2022) suggest that B.1.355 is a recombinant of B.1.595 and B.1.371. We should check if this is the case in our sc2ts ARG.
Copying/pasting Figure 3 from the paper here.
The text was updated successfully, but these errors were encountered: