Skip to content
This repository has been archived by the owner on Dec 3, 2019. It is now read-only.

Possible bug with MPI and writing ancestral state trace #162

Open
ziad-khouri opened this issue Aug 13, 2019 · 1 comment
Open

Possible bug with MPI and writing ancestral state trace #162

ziad-khouri opened this issue Aug 13, 2019 · 1 comment

Comments

@ziad-khouri
Copy link

Hi,

I ran into a potential issue with how ancestral states are written with mnJointConditionalAncestralState() when using MPI: some sites/characters appear to be skipped like in the example below.

"1,1,1,1,1,1,0,1,1,0,1,0,0,1,0,0,0,1,0,1,1,1,1,0,1,0,1,1,1,1,0,1,1,1,1,1,0,1,1,0,,0,0,1,0,0,0,0,,0,1,1,1,0,,0,,1,0,0,1,0"

This does not occur when replicating the run without MPI. Additionally, when using MPI with this particular analysis, RevBayes freezes on or after the last MCMC iteration.

I'm attaching code to replicate the issue, as well as logs and output from two runs.

Environment:
OS: Ubuntu 18.04
GCC: 8.3.0
OpenMPI: 4.0.1
RevBayes: 59d42df
(development branch, Aug 7, 2019)

Best,

Ziad
mpi_bug_test.zip

@ziad-khouri
Copy link
Author

Update: The issue does not show up when doing power posterior runs with MPI. I suspect it is linked specifically with parallelization across sites.

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

No branches or pull requests

1 participant