-
Notifications
You must be signed in to change notification settings - Fork 129
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
augur tree modifying strain names without warning #1084
Comments
From looking into |
Thanks @anna-parker for tackling this and using the IQ-tree source code to make sure we're totally aligned! You actually linked to the old repo that's unfortunately not yet been archived. This is the currently maintained IQtree repo: https://github.com/iqtree/iqtree2/blob/3bbc304263cb2f85574a9163e8f2e5c5b597a147/utils/tools.cpp#L585 @jameshadfield why are you still on Augur 17.1.0 :) |
(relocating discussion from #769…)
Sorry if I'm being obtuse — I don't see the "upstream" part anywhere in this issue; maybe it's implicit that if It also looks like — unless I'm misunderstanding something, which is very possible — the name-munging is reversed and the resulting Bio.Phylo object ( I suspect maybe a trivial fix here is expanding the set of characters in |
I've run into error twice in the avian-flu data and ended up fixing the strain names in ingest. This is fine for our automated workflows, but can be an annoying gotcha for external users just doing ad-hoc analysis.
+1 for expanding the set of characters in the |
I'm about to submit a PR doing just this, however this approach won't be enough to close this issue. A Line 516 in 8920730
will be encoded as |
What's "upstream" in this context? Upstream in the ingest workflow or upstream in some non-Augur place? |
In this context I'm just saying that we should have alerted the user (or fixed the problem) before we get to |
Hmm, maybe we could add a warning for invalid characters in Augur's centralized I/O functions (e.g. |
+1 to the idea of centralizing the warning in the IO layer — would probably be nice to add something like |
Current Behavior
augur tree
modifies strain names in the output tree and does not notify the userExpected behavior
The strain names should be the same. If this is not possible (due to the newick schema) then we should throw an error (as downstream commands are inevitably going to fail).
How to reproduce
Steps to reproduce the current behavior:
Coted'Ivoire/IPCI-DVE-GR1901/2022
(which, BTW, comes from our nCoV provisioned files)augur tree --alignment aligned.fasta --tree-builder-args '-ninit 10 -n 4' --output tree_raw.nwk --nthreads 1
augur tree
Coted_Ivoire/IPCI-DVE-GR1901/2022
Your environment
augur 17.1.0
The text was updated successfully, but these errors were encountered: