-
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
lineage notes curation #2280
Comments
@RaphaelRaphael I just quickly created this branch to see the changes more easily. Having a standard format would be much easier! However, there were a few instances where replacing
Oh, and there are 2 separate repositories where the issues are located in. |
Might I pop in with a suggestion while you're at it? Most lineage aliases have "Alias of [full lineage]" in their descriptions, but I've stumbled over a handful of lineage aliases in the newest lineage notes (specifically HF.1 and sublineages) that just state the full designation of "XBB.1.16.13.1" (etc) with no "Alias of" - I don't think that's in your set yet, though? I think it'd be helpful to have a unified format for that - for example, I have a script that parses the notes and relies on the "alias" part to be there (to differentiate from lineages named in other contexts such as "recombinant of [lineage] and [lineage]"). What do you think? |
Thank you for bringing that up. Usually the missing "Alias of" does get fixed, but they can easily be missed for some time. This will have to be fixed, too. |
Please close this issue |
Proposition of curation of lineage_notes.txt file (formating issues etc... )
lineage_notes.txt
The text was updated successfully, but these errors were encountered: