-
Notifications
You must be signed in to change notification settings - Fork 10
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
The transition probability matrix in Lewis Mk model is incorrect #10
Comments
Could this have had an impact on analyses with symmetric transition probabilities? |
It has an impact on any analysis using Lewis Mk model without specified frequencies. I am not quite sure which model you mean. |
I was being confusingly specific. I just meant, would this likely have had an impact on previous analyses involving morphological datasets with BEAST2? Sounds like the answer is yes. |
Unfortunately yes. It should not be a big impact. I am checking my penguin analysis and so far there is only very little difference in morphological clock rate. |
Well, I've found bugs like this in paleotree before, and had to alert people via social media/R-Phylo. Once your penguin re-analysis is done, will you be notifying users via the beast-users group of the issue and how much of an impact it made on your own re-analysis, so anyone who did an analysis recently knows to rerun their study? |
Yeah, I will need to notify users somehow.
On Fri, 29 Jun 2018 at 21:51 David Bapst ***@***.***> wrote:
Well, I've found bugs like this in paleotree before, and had to alert
people via social media/R-Phylo. Once your penguin re-analysis is done,
will you be notifying users via the beast-users group of the issue and how
much of an impact it made on your own re-analysis, so anyone who did an
analysis recently knows to rerun their study?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#10 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AGJfciKPJcfA3q-3iTmrE5K2KX0reV_Iks5uBoVKgaJpZM4U5l7g>
.
--
Best regards,
Dr. Alexandra "Sasha" Gavryushkina
Postdoctoral fellow
Department of Biochemisty
University of Otago
New Zealand
|
Sorry to hear this, Sasha. The standard protocol is to make an announcement on beast-users forum detailing the bug and advising under what models and versions of the software people may have been affected.
I would recommend adding a unit test to check the transition probabilities for both equal and unequal frequencies. There should be some similar tests for the nucleotide models.
… On 30/06/2018, at 8:02 AM, Alexandra Gavryushkina ***@***.***> wrote:
Yeah, I will need to notify users somehow.
On Fri, 29 Jun 2018 at 21:51 David Bapst ***@***.***> wrote:
> Well, I've found bugs like this in paleotree before, and had to alert
> people via social media/R-Phylo. Once your penguin re-analysis is done,
> will you be notifying users via the beast-users group of the issue and how
> much of an impact it made on your own re-analysis, so anyone who did an
> analysis recently knows to rerun their study?
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <#10 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AGJfciKPJcfA3q-3iTmrE5K2KX0reV_Iks5uBoVKgaJpZM4U5l7g>
> .
>
--
Best regards,
Dr. Alexandra "Sasha" Gavryushkina
Postdoctoral fellow
Department of Biochemisty
University of Otago
New Zealand
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub <#10 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA3WSU0XHIMUDbfUz6Jzta_RGxz4uQYdks5uBofGgaJpZM4U5l7g>.
|
Thanks for sending the comment to beast-users, @gavryushkina! |
double should be used instead of integer for calculation line 108
The text was updated successfully, but these errors were encountered: