Skip to content

[phylogenetic] B.1 tree fails due to "export: has duplicate nodes or "treetime: nodes with name None" #310

@corneliusroemer

Description

@corneliusroemer

B.1 phylogenetic runs have failed 3 times in a row. 2 times because of treetime error, once because of export validation error. (@joverlee521 seems to have already started investigating, at least triggering a rerun yesterday)

Treetime error:

[batch] [2025-04-18T18:47:41+00:00] augur refine is using TreeTime version 0.11.4
[batch] [2025-04-18T18:47:41+00:00] ERROR: TreeAnc.optimal_branch_length: terminal node alignments required; sequence is missing for leaf: 'None'. Missing terminal sequences can be inferred from sister nodes by rerunning with `reconstruct_tip_states=True` or `--reconstruct-tip-states`
[batch] [2025-04-18T18:47:41+00:00] 380.89	***WARNING: TreeAnc._check_alignment_tree_gtr_consistency: NO SEQUENCE
[batch] [2025-04-18T18:47:41+00:00]       	FOR LEAF: 'None'
[batch] [2025-04-18T18:47:41+00:00] 380.90	***WARNING: TreeAnc: 1 nodes don't have a matching sequence in the
[batch] [2025-04-18T18:47:41+00:00]       	alignment. POSSIBLE ERROR.

https://github.com/nextstrain/mpox/actions/runs/14538944332/job/40792976872#step:5:676

Export error:

[batch] [2025-04-22T18:38:51+00:00] Validating that the JSON is internally consistent...
[batch] [2025-04-22T18:38:51+00:00] Node OP536796 appears multiple times in the tree.

https://github.com/nextstrain/mpox/actions/runs/14538944332/job/40954094434#step:5:763

Root cause is quite likely a bug in our tree-fix post-iqtree script.

Two possible solutions:

  • find and fix the bug in that script
  • switch B.1 build to cmaple (+ collapse polytomy post-process script) instead of iqtree + fix-tree.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions