I submitted this bug in the emmeans package repo, but it seems some times the authors of packages implement emmeans functionality in their own packages.
I don't think that is the case with afex but I opening this report just in case there's something you can do on your end.
Cross-posted from the emmeans project repo:
Describe the bug
When I run emmeans(model, ~ Var, at = list(Var = c("levelx", "levely"))) the results get switched for afex_aovs if I place levelx and levely in a different order, but this doesn't happen for models of class afex_mixed, and it probably won't happen for other models.
I submitted this bug in the emmeans package repo, but it seems some times the authors of packages implement emmeans functionality in their own packages.
I don't think that is the case with afex but I opening this report just in case there's something you can do on your end.
Cross-posted from the emmeans project repo:
Describe the bug
When I run
emmeans(model, ~ Var, at = list(Var = c("levelx", "levely")))
the results get switched forafex_aov
s if I placelevelx
andlevely
in a different order, but this doesn't happen for models of classafex_mixed
, and it probably won't happen for other models.To reproduce
Expected behavior
If we list the factors in the order they appear we always get correct results.
If we reverse the names of the factors we get wrong values in for the model of class
afex_aov
.How can I help?
Please let me know if there's anything I can do about this matter.
Sincerely, J