-
Notifications
You must be signed in to change notification settings - Fork 48
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
Does the response need to be stored as an FeMat? #250
Comments
I think changing the response to Should we warn when constructing a model with constant response? Or perhaps warn when fitting a model with constant response? I'm a strong believer in garbage-in, garbage out, but this type of basic error checking might still be useful. |
With #253, you can now handle a rank-zero |
I think the conclusion we came to was "this is too much effort and FeMat now works for zero-rank matrices", right? |
Multivariate extension of LMM was one of Harald Baayen's goals for the Cooperation Group. Linked linear mixed models also come to mind. Just saying ... |
Closed by #464 |
Currently the response is stored as an
FeMat
in theallterms
field of aLinearMixedModel
. That was done for convenience back in the days when the random-effects terms were in a separatereterms
field from thefeterms
. By making the response look like a fixed-effects term thefeterms
had a concrete type ofVector{FeMat{T}}
.This approach has the disadvantage that a model cannot be constructed from a response that is initialized to zeros. There is a check on the rank of an FeMat during its construction and a column of zeros has rank zero. The reason for such a model is for simulations. The
simulate!
function overwrites the values of the response vector.It may make more sense make the type of the
allterms
fieldVector{Union{ReMat{T},FeMat{T},Vector{T}}}
and skip that check on the rank.The text was updated successfully, but these errors were encountered: