dbabox/beast-mcmc

URGENT: Default prior review

Closed this issue · 3 comments

I think we urgently need to review the default priors for all parameters in 
BEAUti. In particular we 
should drop _ANY_ uniform bounds (other than illegal values such as rate<=0.0). 

Original issue reported on code.google.com by ramb...@gmail.com on 12 Nov 2009 at 2:08

solution code was checked in, but need to review 

Original comment by dong.w.xie@gmail.com on 19 Nov 2009 at 12:21

  • Changed state: Started
Reviewed code and highlighted that there still remains the issue that we need 
to decide on which parameters 
require explicit, proper, priors and what they should be by default. A wiki 
page exists to document this:

http://code.google.com/p/beast-mcmc/wiki/ParameterPriors

I think we start by listing every parameter, what it is, what its hard bounds 
are and a suggested default proper 
prior (1/x would be a possibility if justifiable).

Original comment by ramb...@gmail.com on 19 Nov 2009 at 1:14

Review of priors has begun and some have been implemented. Plus a warning box 
about 'defaults' has been 
added. I have closed this issue and will reopen another one to continue the 
process after the v1.5.3 has been 
released.

Original comment by ramb...@gmail.com on 25 Nov 2009 at 11:41

  • Changed state: Fixed
  • Added labels: BEAUti, v1.5.2
  • Removed labels: BEAUtiv1.5.2