-
Notifications
You must be signed in to change notification settings - Fork 98
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
Update lineage_notes.txt #2325
Update lineage_notes.txt #2325
Conversation
Thanks for the corrections. Is there consensus from the group about removing the "from" allele (like T or K in T478R or K478R) and keeping only the "to" allele (R)? I guess missing information can't be incorrect, but sometimes it is interesting to keep track of multiple successive changes. @corneliusroemer @FedeGueli @aviczhl2 @ciscorucinski @Over-There-Is @HynnSpylor @Memorablea ? |
I prefer always wild type to actual mutation as S:G339 S:V445A it leaves without doubt. I spoke with Ryan many months ago but we didnt end with a way or another. |
I think this should be related/addition to the Lineage Notes Standardization PR #2283 to keep multi-step mutations well informed and in a unified manner. There are a few options:
I had a chat with @HynnSpylor on this topic on another PR before ( #2139 , obsoleted so retracted) and I have no problem with it then, but now we are having lineages like sars-cov-2-variants/lineage-proposals#961 and potentially even more with multi-step mutations in the future, so maybe it's time to regulate it to a proper format. |
agree |
Sorry for a late reply! |
FL*/EG* corrections; replace further mutations like
T478R
orK478R
to unified/most common478R