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

Potential breaking change for brms 3.0: no special treatment for mu #1660

Open
venpopov opened this issue May 24, 2024 · 0 comments
Open

Potential breaking change for brms 3.0: no special treatment for mu #1660

venpopov opened this issue May 24, 2024 · 0 comments
Labels
Milestone

Comments

@venpopov
Copy link
Contributor

This is a summary of our recent discussions in person

Overview

General idea is to move away from treating the mu parameter in any special way. This would involve:

  • Do not require models to have a mu parameter
  • No distinction between mu and distributional parameters
  • For models that do have a mu parameter, do not redact mu anywhere (e.g., Intercept_mu, not Intercept, do not hide in priors, etc)

This would be a breaking change, so delegated to v3.0.

Additional context

Here are some relevant previous issues/PR requests. I have closed them as we discussed, and the current issue consolidates the info in one place.

#1610
#1596

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants