-
Notifications
You must be signed in to change notification settings - Fork 1
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
Observation: The number of reticulations depends on the chosen brlen linkage mode (and maybe also on the likelihood model) #33
Comments
In LikelihoodModel.AVERAGE, the negative influence comes from the reticulation probabilities being always linked among all partitions. We would not have a negative influence here if each partition would have its own reticulation probabiities. |
Today I notice that I understand well the difference between LikelihoodModel.BEST and LikelihoodModel.AVERAGE but I am not sure I understand UNLINKED, LINKED and SCALED. When we have a tree and and we have LINKED, any gene of a partition has the same tree and the same branch lengths. @stamatak, am I right? Sorry to ask stupid things, but better safe than sorry. In my simulation we are in the LINKED case for now (we we could easily have SCALED for the next article), so I do not see why we should have UNLINKED in the reconstruction. Also, it would be good to add a step to the simulations, if you both agree: since branch lengths and inheritance probabilities are bothering us, how about running netRax on the true topology to see how good we are at estimating branch lengths and inheritance probabilities under the 6 combinations of BEST and AVERAGE x UNLINKED, LINKED and SCALED? |
That's all correct regarding the branch length flavors.
My rationale is that the br-lens have a substantial impact on the
likelihood score and that different displayed trees as defined by a
reticulation will also have pretty different optimal branch lengths,
hence my preference for unlinked.
Regarding the additional experiments, that's a very good idea, I totally
agree.
Alexis
…On 18.12.20 20:24, celinescornavacca wrote:
Today I notice that I understand well the difference between
LikelihoodModel.BEST and LikelihoodModel.AVERAGE but I am not sure I
understand UNLINKED, LINKED and SCALED.
When we have a tree and and we have LINKED, any gene of a partition has
the same tree and the same branch lengths.
When we have a tree and and we have SCALED, any gene of a partition has
the same tree and the same branch lengths, ignoring a multiplication
factor (the mutation rates vary among gene).
When we have a tree and and we have UNLINKED, any gene of a partition
has the same tree but the branch lengths can vary (mutation rates vary
among genes and branches).
@stamatak <https://github.com/stamatak>, am I right? Sorry to ask stupid
things, but better safe than sorry.
In my simulation we are in the LINKED case for now (we we could easily
have SCALED for the next article), so I do not see why we should have
UNLINKED in the reconstruction.
Also, it would be good to add a step to the simulations, if you both
agree: since branch lengths and inheritance probabilities are bothering
us, how about running netRax on the true topology to see how good we are
at estimating branch lengths and inheritance probabilities under the 6
combinations of BEST and AVERAGE x UNLINKED, LINKED and SCALED?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#33 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAGXB6QRRDC5J7VH7XWPI73SVOM65ANCNFSM4U7ZELGA>.
--
Alexandros (Alexis) Stamatakis
Research Group Leader, Heidelberg Institute for Theoretical Studies
Full Professor, Dept. of Informatics, Karlsruhe Institute of Technology
www.exelixis-lab.org
|
Here UNLINKED is applied to networks, not displayed trees right? |
I am not so sure, I believe that as we are doing computations via the
displayed trees, and different tree topologies need different sets of
branch lengths to have an optimal likelihood, branch lengths might need
to be estimated separately.
However, this really depends on how the networks are simulated, that is
for which parts of the displayed trees we simulated along branches of
the same length or where we do not.
So I'd say the key task here is to make sure that we simulate and infer
under the same model for the branch lengths.
…On 18.12.20 23:48, celinescornavacca wrote:
Here UNLINKED is applied to networks, not displayed trees right?
If so, my rationale is that having the same branch lengths for the same
network topology for all partitions will give us more power to infer
reticulations
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#33 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAGXB6SPXENJZ6TZGHH25D3SVPE3ZANCNFSM4U7ZELGA>.
--
Alexandros (Alexis) Stamatakis
Research Group Leader, Heidelberg Institute for Theoretical Studies
Full Professor, Dept. of Informatics, Karlsruhe Institute of Technology
www.exelixis-lab.org
|
Cool! Then we can do all experiments in LINKED mode! :-) This one also performed best in the anecdotal experience I had so far. I believe (from reading the simulator code) the network simulations are using LINKED branch lengths as well. |
This example network shows that the displayed trees of a network can have identical topology:
In here, only a single branch length can differ between the two displayed trees.
In unlinked brlens mode, each partition has its own branch lengths. Thus for the unlinked brlens mode it makes no sense to have a reticulation here. The reticulation makes sense in linked branch lengths mode (but there, mostly for LikelihoodModel.BEST, as the advantage of the variable branch length has some negative influences in LikelihoodModel.AVERAGE). For scaled branch lengths mode, it is still a bit unclear for me what should ideally happen in the inference.
The text was updated successfully, but these errors were encountered: