Skip to content
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

Explore use of IQ-TREE's constraint tree option #79

Open
joverlee521 opened this issue Mar 23, 2022 · 1 comment
Open

Explore use of IQ-TREE's constraint tree option #79

joverlee521 opened this issue Mar 23, 2022 · 1 comment
Labels
enhancement New feature or request

Comments

@joverlee521
Copy link
Contributor

@corneliusroemer experimented with IQ-TREE's constraint tree option to prevent IQ-TREE from putting clades in the wrong place for NextClade reference trees. This seems like a good way to ensure correct trees especially in 6m builds that may be lacking context sequences.

One issue brought up in initial Slack thread:

One issue to sort out would be delimiter in sequence names, right now IQtree renames all / as some weird string

@joverlee521 joverlee521 added the enhancement New feature or request label Mar 23, 2022
@corneliusroemer
Copy link
Member

This is how it's used right now in the SC2 reference tree workflow:

Simply add constraint tree file path after -g to tree builder args:
https://github.com/neherlab/nextclade_data_workflows/blob/09be86c1718ffab2deed7060c3f7a70c135c530d/sars-cov-2/defaults/parameters.yaml#L22

And that's the hand coded tree: https://github.com/neherlab/nextclade_data_workflows/blob/feat/gisaid-v2/sars-cov-2/defaults/constraint.nwk

In the flu case, there are two options:

  1. Either you get (synthetic) prototypical sequences for each clade with constant names, like 2A, 2A.1 etc. (similar to the SC2 workflow) and hand code a short Newick tree with the right topology
  2. Or you generate a constraint tree using actual sequence names based on the topology as revealed through clade-hierarchies or handcoded in a newick tree that's read in by Biopython.Phylo

Both approaches should work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
No open projects
Status: Backlog
Development

No branches or pull requests

2 participants