Issue 756 in beast-mcmc: FEE with random local clock + codon position partitions + multiple threads

[beast...@googlecode.com]

Status: Accepted
Owner: mdhall272
Labels: Type-Defect Priority-Medium

New issue 756 by mdhall272: FEE with random local clock + codon position
partitions + multiple threads
https://code.google.com/p/beast-mcmc/issues/detail?id=756

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:
Dengue4_example.xml 39.5 KB

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[beast...@googlecode.com]

Updates:
Labels: beast v1.8.1 Milestone-Release1.8.2

Comment #1 on issue 756 by ramb...@gmail.com: FEE with random local clock +

codon position partitions + multiple threads
https://code.google.com/p/beast-mcmc/issues/detail?id=756

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

[beast...@googlecode.com]

Comment #2 on issue 756 by ramb...@gmail.com: FEE with random local clock +

codon position partitions + multiple threads
https://code.google.com/p/beast-mcmc/issues/detail?id=756

Issue 733 has been merged into this issue.

[beast...@googlecode.com]

Updates:
Status: Fixed

Comment #3 on issue 756 by ramb...@gmail.com: FEE with random local clock +

codon position partitions + multiple threads
https://code.google.com/p/beast-mcmc/issues/detail?id=756

This issue was closed by revision r6676.