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

Subchain length problem #14

Open
MordorianGuy opened this issue Aug 25, 2022 · 2 comments
Open

Subchain length problem #14

MordorianGuy opened this issue Aug 25, 2022 · 2 comments

Comments

@MordorianGuy
Copy link

MordorianGuy commented Aug 25, 2022

It is stated in the FAQ that sufficient subchain length can be defined as chain length of usual MCMC run divided by ESS. However, nested sampling & usual MCMC are guided by different distributions, prior & posterior (joint) respectively. We can set BEAST analysis prior only. If we are trying to enforce the independence of sampling, should we use guided only by prior run for determining the sufficient criterion?

The second question about FAQ recommendations is how to define the consistency of the number of parallel runs more than two? Comparing them all in pairs does not sound like an elegant way. Is there any appropriate method?

@rbouckaert
Copy link
Collaborator

As far as I am aware, both questions are research questions.

The suggested subchain length makes for a good starting value, but as you already pointed out in #13, actual performance depends on operator settings, so running multiple analyses is the only way to get some confidence that the subchain length is sufficiently large.

I suppose some formal statistical test can be applied to compare results of more than two such runs. However, if it is not immediately clear from pairwise comparison that results are consistent and a formal test is required to confirm consistence, the subchain length is probably too short, resulting in dependent samples and thus biased results.

@pmat747
Copy link
Collaborator

pmat747 commented Aug 30, 2022

Just an idea: to avoid pairwise comparison, a principal component analysis could be used (PCA). A reduction to a one dimension would indicate consistency in the runs.

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

No branches or pull requests

3 participants