You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm currently writing an analysis script for a sequential Bayesian analysis. I will run the script every night to decide if I continue data collection. For obvious reasons I want to base this decision on precise estimates of the Bayes Factors, so I want to recompute the BayesFactor objects until a desired level of precision is reached, without having to manually fiddle with the number of iterations and recomputation attempts.
I think it would be helpful to offer this functionality within recompute(), e.g., by providing an option maxError. Additionally, an option such as attempts could provide the maximum number of recomputation attempts to satisfy the maxError condition.
Well, as to having it in the original call: there are cases where the Bayes factor is so large that it makes do difference. Consider a Bayes factor of 4e10 \pm 20%. Do we really want to have an algorithm get that under, say, 1%? Not really. The Bayes factor is so large that we would simply ignore the 20% error. Otherwise we're just wasting CPU cycles.
Perhaps what we need is iterative cycles of ignoring and zooming in on the models we want (or the best models), rather than simply going for a maxError.
Hi Richard,
I'm currently writing an analysis script for a sequential Bayesian analysis. I will run the script every night to decide if I continue data collection. For obvious reasons I want to base this decision on precise estimates of the Bayes Factors, so I want to recompute the BayesFactor objects until a desired level of precision is reached, without having to manually fiddle with the number of iterations and recomputation attempts.
My current approach to this is quite simply this:
I think it would be helpful to offer this functionality within
recompute()
, e.g., by providing an optionmaxError
. Additionally, an option such asattempts
could provide the maximum number of recomputation attempts to satisfy themaxError
condition.This, to me at least, would be quite helpful.
I'm happy to give this a shot myself and make a pull request, if you like the idea.
Best regards,
Frederik
The text was updated successfully, but these errors were encountered: