-
Notifications
You must be signed in to change notification settings - Fork 97
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
KD.5 Retraction Request #2405
Comments
@AngieHinrichs suggest to put a branch-specific mask for XBC.1.3.1 |
and the note text of XBC.1.1.2 should also be modified. |
Thanks @Over-There-Is. I will mask the deleted range in all of XBC. (starting with 2023-12-22 build) |
Confirmed the UShER tree no longer has a KD.5 branch as of 2023-12-22, due to masking the deleted range in XBC. I agree with @Over-There-Is's comment above that the description of XBC.1.1.2 in lineage_notes.txt should be updated to no longer include S:L244F because that was an artefact. |
@corneliusroemer I am going to do a PR to remove KD.5 from lineages.csv and lineage_notes.txt unless you object soon. 🙂 |
…e of S:L244F as explained in cov-lineages#2405. The deleted range is now masked in XBC in the usher tree so there is no longer a branch for this lineage.
Fixed in #2443 |
22289-22294 sites of XBC is deleted, and it causes S:del243-244. As both S:242 and S:244 are Leucine residue, it is always also described as S:del242-243.
Sometimes, TT on 22287-22288 sites is duplicated and causes artefactual frameshift. These sequences are analyzed as having del22286-22289 and A22294T, and even got analyzed as "S:L244F" further.
In UShER, 55 sequences are assigned as KD.5. Some of its subbranches share mutations with other branches. The largest subbranch with 30 sequences has 2 private synonymous mutations: C4456T, A10621G, I do not consider this subbranch worth designated.
The text was updated successfully, but these errors were encountered: