Closed trvrb closed 3 days ago
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 own frequencies.smk file. Also, I chose to output to results/tip_frequencies.json and then copy this file to auspice/ under export.smk, but this copying could be thought of as extraneous.
The pathogen-repo-guide currently suggests augur frequencies
as part of the export.smk
with the thought that it can output directly to the exported auspice/
directory 😄
Ah! I missed this. This makes as much (if not more) sense to me as including it in annotate_phylogeny.smk
. I'll update the PR.
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.