Skip to content
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

Single threads or Multitheads?? #253

Open
kuangtianhui opened this issue Sep 7, 2021 · 1 comment
Open

Single threads or Multitheads?? #253

kuangtianhui opened this issue Sep 7, 2021 · 1 comment
Labels

Comments

@kuangtianhui
Copy link

kuangtianhui commented Sep 7, 2021

Dear author,

The following are two scenarios using MrBayes. Only the Nchhains parameter and the number of running threads are modified. What impact will these two different operation modes have on the results? Which result is more credible?

1.Other parameters remain unchanged. Adjust Nchains to 4 and run MrBayes in a single thread.

2.When other parameters are consistent, only the Nchains parameter is changed, and then multiple threads run MrBayes.

Best wishes,
Tian-hui Kuang

$)Z@%7NWY)D$1A)X3(N1F

According this guidance of v3.2 it just for speeding up the calculation of big data set.

@nylander
Copy link
Collaborator

nylander commented Feb 2, 2024

Dear @kuangtianhui
Both the number of chains (i.e., number of "independent" starting points), and applying Metropolis-coupling (using "heated", helper chains) are means to more quickly reach the target distribution. After reaching the target, which can be more difficult and take more time for some data, especially larger, the additional samples are only gathered for increased precision. Given that you run your chain under the two scenarios outlined above, and that you access the convergence of the results, there is no reason that one should be more credible than the other. I's just a matter of waiting for chains to converge.
Yours
Johan

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants