Open vanessazubach opened 2 months ago
Hi @vanessazubach,
ERROR: target '[MMR24-0424_MVs/Quebec.CAN/16.24_B3_8840_2024-04-15' is not in this tree
It looks like you have an extra [
in front of the sample name. Can you try re-running after removing the [
from the command?
Thank you. That did the trick. However the tree it did not work out how I was hoping for it to. Is there a way to define clades as monophyletic or define a common ancestor? I know epidemiologically that sample 353 is the ancestor to 424, 425, 440, 494 and 496, so why are those samples not branching off of that sample?
Hi @vanessazubach I've also gotten this error before and we should catch it and abort with a clear message to the user about their error.
You can pass a constraint tree to iqtree if you want to enforce a certain topology. But this might be overkill. I'd need more context to help with your question. Maybe you can post your general question re tree topology being different than expected ok discussion.nextstrain.org? The forum is better suited for that sort of broad question.
This should be handled by TreeTime. @corneliusroemer are you able to transfer this issue to neherlab/treetime?
No, it should be handled by Augur. Treetime can't do anything about a user error. The problem is that augur doesn't catch it.
Augur should catch and abort with an appropriate message but not throw an exception.
Would this not happen for users of TreeTime CLI? This is the error from TreeTime:
ERROR in TreeTime.run: An error occurred which was not properly handled in TreeTime. If this error persists, please let us know by filing a new issue including the original command and the error above at: https://github.com/neherlab/treetime/issues
A better explanation: right now it is throwing TreeTimeUnknownError
. There's no way to differentiate user error vs. code error with that exception class. Augur expects these to be handled by TreeTime throwing TreeTimeError
with a meaningful error message, for example:
raise TreeTimeError(f"Malformed VCF file {vcf_file!r} - all the meta-information (lines starting with ##) must appear at the top of the file.")
You're right @victorlin!
Thank you all for your quick attention to this! And thank you @corneliusroemer for your suggestion to provide more information about my scenario and put it in the discussion.nextrain.org, I will do that.
Current Behavior
Expected behavior
I am trying to run Augur refine. I have added the --root because I know sample 353 was the root to 424, 425,440, 494 and 496, but I am getting these errors saying sequence 424 is not in the tree. When I ran this previously without adding the root argument it was fine, however the cluster with these samples did not start at 353.