Export to GitHub

beast-mcmc - issue #756

FEE with random local clock + codon position partitions + multiple threads

Posted on Jan 30, 2015 by Swift Cat

Attached is a basic example. A full evaluation error occurs when a new clock rate is proposed. One of the partition likelihoods evaluates properly but the other does not. If you use only one thread (-threads 1) it doesn't happen.

You also get differing behaviour for multiple runs with the same seed.

 Attachments

Comment #1

Posted on Feb 3, 2015 by Quick Horse

This is also happening with multi-partitions and a local clock model.

Comment #2

Posted on Feb 3, 2015 by Quick Horse

Issue 733 has been merged into this issue.

Comment #3

Posted on Feb 3, 2015 by Quick Horse

This issue was closed by revision r6676.

Status: Fixed

Labels:
Type-Defect Priority-Medium beast v1.8.1 Milestone-Release1.8.2