-
Notifications
You must be signed in to change notification settings - Fork 32
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
nice() ANOVA table MSE report #21
Comments
I am not sure I understand. What would you prefer to see there? Can you perhaps show this in the example (i.e., what kind of values). |
Hello, I mean the mean square between estimate for each factor. I would get those from the afex object like this:
I think these values are also reported in JASP or SPSS; however it is of course not necessary to report them in the nice() table by default, and I can produce them for myself if I want to. I just wondered whether it was intentional that MSE is reported in the row for each between-subjects factor (and the mean squared between estimate would be an alternative). Best regards, |
Hmm, this is probably what I wanted to have there. No clue, why I do not have it there. Let me think about it. |
I've got the same issue - MSEs are all the same (it appears to be the MSE for the Error term). |
Hello,
first of all, thanks a lot for creating the afex package. I am using it a lot to compute
all of my ANOVAs or ANCOVAs. I have a question / suggestion with regard to the ANOVA
table that is produced when conducting an ANOVA with afex. When I compute a
multi-factorial ANOVA with several between-subjects factors, I get a table like this:
In this case, the column MSE contains the mean squared error three times. Is this
intended behavior? Maybe it would be more appropriate if the mean squared estimate
for each between-subject factor is reported in this column instead? I am asking because
when using rmarkdown I can directly use the nice() table in a pdf report, and
in this case I do not like to use the MSE column as it is currently implemented. But
maybe I am missing something and this is in fact intended behavior.
Best regards and thanks a lot,
Martin
The text was updated successfully, but these errors were encountered: