You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The new trees (currently just R_Recombination) all have euclidean distance 0 and are estimated from the node landed on so without displaying the uncertainties (should be attached to the new tree kinetics objects already) it's hard for a user to guess how good a new tree rate estimate is.
The text was updated successfully, but these errors were encountered:
@ Matt, Thanks for the advice. Below is an example of rate rule estimation from your tree estimation.
Do you suggest that add a new item (say under Temperature range) to indicate the uncertainty value? I agree that indicating the uncertainty value whenever it is available is beneficial. Let me know if it is what you mean.
The new trees (currently just R_Recombination) all have euclidean distance 0 and are estimated from the node landed on so without displaying the uncertainties (should be attached to the new tree kinetics objects already) it's hard for a user to guess how good a new tree rate estimate is.
The text was updated successfully, but these errors were encountered: