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.
This commit produces tip-frequencies JSON files for both N450 and genome analyses, but only displays frequencies panel for N450.
Start date of 2000 and end date of –6 months were chosen based on data availability. I increased bandwidth by about 2.5x to account for data quantity relative to temporal spread (compared to the 2y flu-like defaults).
Generally, I think it's quite useful to display frequencies once we have:
You can see output of running this PR here: https://nextstrain.org/staging/measles/frequencies/N450
There are some nice interactions, like seeing how restricted genotypes are in Africa vs Asia.
I've tagged @joverlee521 here as reviewer as well because I wasn't sure how frequencies should fit into the https://github.com/nextstrain/pathogen-repo-guide. I chose to add the rule to
annotate_phylogeny.smk
, which seems most suitable, but it's not really annotating the tree and could be it's ownfrequencies.smk
file. Also, I chose to output toresults/tip_frequencies.json
and then copy this file toauspice/
underexport.smk
, but this copying could be thought of as extraneous.