Replies: 3 comments 1 reply
-
|
If, at a given position, A and B differ, the outgroup C would allow inference of the branch on which state change occurs. Would you prefer that all such positions would be left as multistate characters in the ASR? |
Beta Was this translation helpful? Give feedback.
-
|
You are right that in the case of two sequences one has to have an outgroup, so my example was too simple, but in the case of many sequences this is not necessarily the case, and one can make inferences about the root without knowing the state of the outgroup. My dilemma is that if I have a large tree, with hundreds of sequences, but my outgroup is only a single sequence, than this sequence may have a disproportionally large effect on the reconstruction, and may introduce a significant bias. So maybe it is best not to use it at all (aside from specifying the root, i.e. the topology of the tree), and I wonder whether IQtree can do this. |
Beta Was this translation helpful? Give feedback.
-
|
I have 1st run iqtree2 on an alignment without an outgroup without requesting asr. Then opened the output treefile in FigTree, rooted it, and exported as output_rooted.nwk Help! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi everyone,
I would like to ask for some advice on the use of outgroups in ASR: is there a way of instructing IQtree to ignore the outgroup in ASR?
For example, if I have a tree (A,B,C), where C was specified as an outgoup (with the -o flag):
|--| (Node1)
| |-----B
|
|-------C
is there a way of telling IQtree to use only A and B in the reconstruction of the ancestral state of Node1? My understanding is that even if I specify C as an outgroup, it uses C in the reconstruction of the sequence of Node1, and one would need an additional node D to be able to avoid it:
|--| (Node1 - root)
| |-------C
|
|----------D
Thanks,
G.
Beta Was this translation helpful? Give feedback.
All reactions