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
Related to this issue, which we resolved by having an explicit alias for save_pars: #110
Since brms is the main workhorse behind the bmm package, should we make it so that it is loaded automatically when loading bmm? This can be done by including it in depends rather than imports. brms does this with Rcpp.
This will avoid having issues like the one above in the future (and we can actually just remove the save_pars alias if we do this).
If we do this, this is what happens when you load bmm:
What do you think?
The text was updated successfully, but these errors were encountered:
I have been thinking about this, too. And generally I think there are many reasons to do so, especially because most of the post-processing is still relying on brms functions and if brms were loaded automatically users do not have to worry about loading brms to use these functions.
Related to this issue, which we resolved by having an explicit alias for save_pars: #110
Since
brms
is the main workhorse behind thebmm
package, should we make it so that it is loaded automatically when loadingbmm
? This can be done by including it independs
rather thanimports
.brms
does this withRcpp
.This will avoid having issues like the one above in the future (and we can actually just remove the save_pars alias if we do this).
If we do this, this is what happens when you load
bmm
:What do you think?
The text was updated successfully, but these errors were encountered: