Parameterize Nextclade dataset in config #1046
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of proposed changes
Prototypes an idea of allowing users to choose their own Nextclade dataset for the final alignment with Nextclade. Adds minimal logic and config to allow users to pull in immune escape and ACE2 binding scores to their builds by switching their default dataset.
As with the Nextclade web UI, users must understand that their trees and annotations on those trees will not make sense biologically if they use sequences that don't descend from BA.2 (Nextstrain clade 21L). This PR doesn't implement any checks or force any filters to ensure that input data are reasonable, unlike the RBD levels annotations in this workflow or the ncov-ingest logic to pull in the same phenotypic scores.
Testing
Tested with this minimal build config based on the CI build:
Run the build like so:
An example tree with immune escape scores from this build looked like this:
And ACE2 binding:
This tree is a good example where the input sequences should be limited to 21L descendants and haven't been fully.
Release checklist
If this pull request introduces new features, complete the following steps:
docs/src/reference/change_log.md
in this pull request to document these changes by the date they were added.