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
Currently, brmsfit objects store some information multiple times at different places to retain backwards compatibility with older versions of brms. In version 3.0 (still a long way to go), we should take the opportunity to clean that up. This will include the following changes:
Just a quick thought: Do you really want to remove ranef()? I think this is a convenient shortcut, and it helps other people writing generic functions that work for brms, lme4 or glmmTMB.
You may be right. I don't like updating it for old objects whenever I add a new multilevel feature, but I think this is acceptable if its helpful for users or developers.
@strengejacke Did you understood my OP as if I wanted to remove the ranef() method? That's not what I ment. Instead I talked about the $ranef element of brmsfit objects which contains information about the "random" effects structure not posterior samples for the corresponding parameters.
Currently, brmsfit objects store some information multiple times at different places to retain backwards compatibility with older versions of brms. In version 3.0 (still a long way to go), we should take the opportunity to clean that up. This will include the following changes:
formula
following the changes in Restructure brmsformula objects #476.family
andautocor
as they are natively stored inside theformula
element.ranef
as it can be easily computed fromformula
anddata
without much computational overhead.data.name
an attribute ofdata
.stan_funs
.The text was updated successfully, but these errors were encountered: