-
Notifications
You must be signed in to change notification settings - Fork 11
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
Use gene reference files to generate E gene trees #48
Changes from 1 commit
81eeef9
cba737f
e591a0b
1e48186
0cbdeb8
040d344
b827c09
6423792
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -42,7 +42,7 @@ rule prepare_auspice_config: | |
output: | ||
auspice_config="results/config/{gene}/auspice_config_{serotype}.json", | ||
params: | ||
replace_clade_key="clade_membership", | ||
replace_clade_key=lambda wildcard: r"clade_membership" if wildcard.gene in ['genome'] else r"nextclade_subtype", | ||
replace_clade_title=lambda wildcard: r"Serotype" if wildcard.serotype in ['all'] else r"DENV genotype", | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. To mirror the title There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Thank you for flagging! I'm considering renaming To recap:
This naming adjustment leaves space for a potential There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Ah, actually I think I'll merge this pull request as it is, and handle the renaming mentioned above in a later PR. That way, we can address it along with fixing this issue: #41. |
||
run: | ||
data = { | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Because the
clade_membership
is automatically used to create theclade
branch label inaugur export
, this change means the E gene build will not have the automaticclade
branch label.It's possible to create custom branch labels since nextstrain/augur#728, but this uses
augur clades
to create the labels and the workflow is skippingaugur clades
for the E gene build 😅There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since the
nextclade_subtype
field is being added throughaugur traits
, maybeaugur traits
should be updated to support adding branch labels as well...There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good to know! I'm currently planning to explore serotype and genotype-defining E mutations (which would create
clade_membership
for E gene builds) in a future PR.But if that doesn't work out, I'll explore "create custom branch labels ..." route you've referenced.