Skip to content
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

Explain model spec for Error in examples using Higgins1990Table5 #11

Open
mjskay opened this issue Apr 10, 2016 · 0 comments
Open

Explain model spec for Error in examples using Higgins1990Table5 #11

mjskay opened this issue Apr 10, 2016 · 0 comments
Assignees

Comments

@mjskay
Copy link
Owner

mjskay commented Apr 10, 2016

E.g., why Error(Tray) works instead of Error(Tray/Fertilizer)

short answer: there is only one observation per Tray.

*long answer (rough): *

For more on split-plot designs, see an explanation here: http://stats.stackexchange.com/a/13837. Relating that example to the ARTool example, Diet corresponds to Moisture, Time to Fertilizer, and Subject to Tray.

Strictly speaking, following a split-plot design, the model specification would be:

m <- art(DryMatter ~ Moisture*Fertilizer + Error(Tray/Fertilizer), data=Higgins1990Table5)

However, we can simplify the model specification for this particular dataset. Error(Tray/Fertilizer) is equivalent to Error(Tray + Tray:Fertilizer). Since there is only one observation per Tray * Fertilizer in the data, the within-Tray error cannot be distinguished from any interaction between Tray and Fertilizer. Thus, the Tray:Fertilizer error term can be dropped from the model specification, yielding:

m <- art(DryMatter ~ Moisture*Fertilizer + Error(Tray), data=Higgins1990Table5)

You can verify that both specifications yield the same results. If there were multiple observations for each Tray*Fertilizer, this would not be the case, and the first specification (with Error(Tray/Fertilizer)) would be preferred.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant