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

Pool SE across RM factors: toggle is mis-calibrated #307

Closed
R180 opened this issue Feb 17, 2019 · 5 comments
Closed

Pool SE across RM factors: toggle is mis-calibrated #307

R180 opened this issue Feb 17, 2019 · 5 comments
Assignees

Comments

@R180
Copy link

R180 commented Feb 17, 2019

For JASP 9.2.0. for Windows (Windows 7):

In Repeated-Measures ANOVA / Descriptive Plots, checking the box labeled "Pool SE across RM factors" causes the SE to be un-pooled in the plot, and un-checking that box causes the SE to be pooled. The behavior should be the opposite.

Pooled un-pooled check box.zip

@EJWagenmakers
Copy link
Collaborator

@JohnnyDoorn (?)

@JohnnyDoorn JohnnyDoorn self-assigned this Feb 19, 2019
@JohnnyDoorn
Copy link

Hi Richard,

Thanks for informing us about this. Something went wrong with how the pooled data are handled and I just fixed it.
However, the main issue here is that the text of the tick box is a little confusing: in the case of your data, there is no pooling across RM factors, because your data only has 1 factor. What is meant, is that when plotting a factor, the mean is taken across the unused RM factors that are still in the model. So if I have two RM factors with two levels in my model, A (1&2) and B (1&2), and I make a plot of the means of A, I first take the average of B across its levels (so when I plot the mean of A1, it is actually the average of A1B1 and A1B2). This procedure is discussed by Loftus and Masson in https://link.springer.com/article/10.3758/BF03210951
I will update the text accordingly, to hopefully make it more clear. Maybe something like "Average across unused RM factors."

Kind regards
Johnny

@R180
Copy link
Author

R180 commented Feb 20, 2019 via email

@JohnnyDoorn
Copy link

Hi Richard,
The default way of constructing confidence intervals in within subjects design that is in JASP is discussed in this paper by Richard Morey: pcl.missouri.edu/sites/default/files/morey.2008.pdf
This segment from the introduction is particularly enlightening:

[...] each observation reflects three sources of variance: the fixed effect of condition, the random ability of each participant, and random error.

In order to eliminate the participant effect, one can normalize the data:

normalize the data by subtracting the appropriate participantʹs mean performance from each observation, and then add the grand mean score to every observation.

The variances of the resulting normalized values in a condition, and thus the size of the CIs, no longer depend on the participant effects

It seems that in your data example, the participant effects have a very low variance in one condition, and higher in the other. The normalization corrects for this, in order to show the variance of the condition effect only. If you want to get insight into the variance simply per cell of your design, you can look at the descriptive table under "additional options" in the RM ANOVA menu.

If you want a little bit more insight into this, you can look at it from a t-test perspective. Basically the ANOVA you are doing is a paired-samples t-test, since you only have 1 factor with 2 levels. The paired samples t-test eliminates the participant effect by default, so if you were to conduct a paired samples t-test and get a descriptives plot with confidence intervals around the group means, you would get the exact same result as with the approach discussed above for the RM ANOVA.

We are currently working on communicating such information more clearly to JASP users by extending the help files, in order to make the software more transparent - especially with procedures that are not always very straightforward such as this one.

Kind regards,
Johnny

@AlexanderLyNL
Copy link
Contributor

I consider this issue clarified. Please reopen if it's unclear.

@MyrtheV As you're working on the ancova documentation, you might be interested in Johnny's post.

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

No branches or pull requests

4 participants