Run power posterior analyses stone-by-stone #397
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This branch provides a Rev interface to the
runStone()andsummarizeStones()methods of the classPowerPosteriorAnalysis, making it possible to analyze individual beta values / power posteriors (or "stones") one by one instead of all at once. This should come in handy for running computationally intensive marginal likelihood analyses on machines with a limited amount of memory and/or number of cores, since it means that analyses of a large number of stones can now be executed in batches instead of all at once.I have also updated the corresponding test suite, which now demonstrates that the run-all vs. run-stones-one-at-a-time implementations produce exactly the same marginal likelihoods when using the single-thread version of RevBayes. For the MPI version, the run-stones-one-at-a-time implementation still produces exactly the same marginal likelihood as with the single-thread version, but the run-all implementation deviates from its single-thread counterpart. This deviation is not new; it already existed in the previous version of the suite, and was actually much more drastic (reaching ~5,500 log units instead of the present ~25).