Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement data estimated initialization points #42

Open
jeffreypullin opened this issue Feb 20, 2020 · 0 comments
Open

Implement data estimated initialization points #42

jeffreypullin opened this issue Feb 20, 2020 · 0 comments
Labels
enhancement New feature or request
Milestone

Comments

@jeffreypullin
Copy link
Owner

jeffreypullin commented Feb 20, 2020

Currently, we implement initialization points that are basically the same as the prior. These were taken from one of Bob Carpenter's posts on the Stan forums I think - I don't have a link handy.

The other option would be to implement the data driven initialization points from the original Dawid-Skene paper. Having not implemented them, I don't know if they would make an improvement. They were probably more important in the context of the EM algorithm, but they may help in cases where the data and priors don't match well.

@jeffreypullin jeffreypullin changed the title Double check inits Double check initialization point May 14, 2020
@jeffreypullin jeffreypullin changed the title Double check initialization point Check initialization points for MCMC May 14, 2020
@jeffreypullin jeffreypullin added this to the 0.2 milestone May 14, 2020
@jeffreypullin jeffreypullin changed the title Check initialization points for MCMC Implement data estimated initialization points Aug 11, 2020
@jeffreypullin jeffreypullin modified the milestones: 0.2, future Aug 11, 2020
@jeffreypullin jeffreypullin added the enhancement New feature or request label Feb 18, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant