Closed strengejacke closed 3 years ago
Thanks for the note @strengejacke, I really appreciate it!
This is a super neat feature, but shouldn't the default be "all"
? AFAICT, the basic summary
method does print random components by default, so as long as their not too expensive to compute that would seem natural.
Also, if I call parameters(x, effects = "all")
on a model that doesn't support the argument, will effects
be ignored and sunk in the ellipsis black hole? (Desirable, I think.)
Also, if I call parameters(x, effects = "all") on a model that doesn't support the argument, will effects be ignored and sunk in the ellipsis black hole? (Desirable, I think.)
Yes. That's why the behaviour for model_summary()
now seems to have changed, because model_parameters()
for mixed models did not have an effects
argument before.
This is a super neat feature, but shouldn't the default be "all"?
That might be the better default, and it's not time consuming to compute. @IndrajeetPatil @DominiqueMakowski what do you say?
Yes! I would also vote for parameters(x, effects = "all")
being the default.
Commit https://github.com/vincentarelbundock/modelsummary/commit/ef9a398ed6faf31aabc17f96d99a16f13476b824 ensures compatibility with the future version of parameters
.
I also see that a new commit has made "all" the default (great!!), so I'm closing this issue.
Thanks again for the note!
Yes, there were a lot of commits the past days, mainly fixing print issues (and adding related tests) and fixing minor issues. Now all local and GitHub checks pass, I just need to fix a revdep issue.
I cannot resolve the revdep issues. Changing the default to effects = "all"
at the moment would break effectsize (which had two updates in the past three weeks, so I would rather wait with this breaking change until the next release cycle).
Thus, I would suggest you set effects
explicitly, as the default will probably be effects = "fixed"
for this update of parameters.
No worries. I made the change you recommend and wrote a test to sniff out any problems if/when you move to "all" as default on your end.
thanks again
Hi, I'm planning to submit an update of parameters to CRAN very soon. Some things have changed (see https://github.com/easystats/parameters/blob/main/NEWS.md), of which some points might be breaking changes. In particular the behaviour for mixed models changed in
model_parameters()
(there's now aneffects
argument, to include random parameters).Can you please check if your package is affected?
Created on 2021-04-07 by the reprex package (v2.0.0)