Skip to content

Commit f7bb660

Browse files
committed
Clarify the branch-specific model
1 parent aa8df4f commit f7bb660

1 file changed

Lines changed: 2 additions & 0 deletions

File tree

doc/AliSim.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -367,6 +367,8 @@ Then, simulate an alignment by
367367
iqtree2 --alisim alignment_example_1 -t input_tree.nwk -m JC
368368

369369
Here, AliSim uses the [Juke-Cantor model](http://doi.org/10.1016/B978-1-4832-3211-9.50009-7) to simulate an alignment along the input tree. However, the `HKY` with random parameters is used to simulate the sequence of taxon C. Similarly, the `GTR` model with the specified parameters is used to generate the sequence of taxon E.
370+
371+
**NOTE:** A branch-specific model is only applied to a specific branch, meaning that it will not be inherited by descendant branches. To apply a new model to an entire subtree, one needs to specify that branch-specific model at all descendant branches.
370372

371373
To mimic heterotachy (rate heterogeneity across branches), users can supply a set of branch-lengths containing `n` lengths corresponding to the `n` categories of the model via `lengths=<length_1>,...,<length_n>`, for example:
372374

0 commit comments

Comments
 (0)