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

Impossible to specify a contrast-specific error term in custom contrasts for within-subjects ANOVA (BUG) #1221

Closed
mservantufc opened this issue Mar 23, 2021 · 3 comments · Fixed by jasp-stats/jaspAnova#319

Comments

@mservantufc
Copy link

mservantufc commented Mar 23, 2021

Hi,
In within-subjects designs, it is usually recommended to use a contrast-specific error term, because any degree of violation of the sphericity assumption will make the error term too small or too large for some comparisons (e.g., Boik, 1981). However, it is currently (JASP 14.1) impossible to use a contrast-specific error term when specifying custom contrasts. Unchecking
"Assume equal variances" (it might be better to call this option "Pool error term", similar to the Simple Main Effects menu) returns "Unequal variances only available for main effects of within-subjects factors" (see attached file).

BlanchardprepJASP.zip

Best,
Mathieu

@mservantufc mservantufc changed the title Contrast-specific error term vs. pooled error term in within-subjects ANOVA Impossible to specify a contrast-specific error term in custom contrasts for within-subjects ANOVA (BUG) Mar 23, 2021
@bknakker
Copy link

bknakker commented Jun 23, 2023

I second this, this is still relevant! It's not a bug from a software engineering perspective, but rather a feature implementation that contradicts good pracitice (or a "stats bug"?). The error message comes up when a custom contrast involves more than one factor, for example. I don't know if reclassifying this as a feature request would give it a push, but maybe a comment does a little?

(I tested on JASP 0.17.2.1 on Windows)

@tomtomme
Copy link
Member

Tested with 0.18.3 - still relevant.

@tomtomme
Copy link
Member

closing as duplicate of #1642
Johnny is already working on a fix.
lets discuss there.

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

Successfully merging a pull request may close this issue.

5 participants