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

Custom families #101

Open
1 of 6 tasks
lindeloev opened this issue Jan 14, 2021 · 0 comments
Open
1 of 6 tasks

Custom families #101

lindeloev opened this issue Jan 14, 2021 · 0 comments
Labels
enhancement New feature or request

Comments

@lindeloev
Copy link
Owner

Family-specific functions are currently scattered over several locations in the code and dealt with in an if-else like fashion. This hard-coding of response families makes it harder to implement new ones and maintain existing ones.

I propose storing all of this in an mcpfamily() object which extends gaussian(), etc.

  • Move priors to mcpfamily()
  • Move the JAGS likelihood code to mcpfamily()
  • Move R random generator code to mcpfamily() (used in fit$simulate()).
  • Assign a list of distributional parameters (dpar) for each family, e.g., c("mu", "sigma") for gaussian() and build regression models for each of these. Use intercept-models for all that are not explicitly included in the formulas.
  • Also somehow code whether it supports ar(), weight(), etc.
  • Document it in a vignette.

This is relevant for #89. Once implemented, support for stan will also be easier (#100).

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