Skip to content
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

Map clades not in clade-legacy-mapping.yml to itself #414

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

corneliusroemer
Copy link
Member

When we add new clades, we need to add them to clade-legacy-mapping.yml in this repo.

This is easy to forget as all the other changes are in ncov directly.

If we don't add them to the mapping file, they end up as ? in metadata.tsv, which is bad.

This PR maps new clades not in clade-legacy-mapping.yml to itself, rather than to ?.

We may want to discontinue legacy mapping at some point and just report short clades

An alternative here is to error when we find this situation - so that we are directly aware of the issue and can fix the mapping. But the current state is worse than either of the two options.

Testing

Tested locally that new clades that are not in clade-legacy-mapping.yml end up mapped to itself.

Avoids those clades being mapped to `?`
We may want to discontinue legacy mapping at some point and just report short clades
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Development

Successfully merging this pull request may close these issues.

1 participant