-
Notifications
You must be signed in to change notification settings - Fork 28
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
Goals of StatCheck? #97
Comments
Sorry for the late reply, I missed that there were new issues opened. You're right that, ideally, statcheck would find everything, regardless of APA formatting. The reason that, right now, it sticks to APA only, is twofold:
The step where statcheck looks for p-values alone can give people somewhat of an indication what percentage of stats was retrieved. If a paper has an APA factor of .60, you can be quite sure that several tests were not picked up, and, vice versa, an APA factor of >.80 can increase your confidence that you checked most of the reported stats. |
Following up; the new version of statcheck will include an option to also look for non-APA formatting (see the branch feature-non-apa-new). I've opted for a modular approach that combines all kinds of small deviations from APA (square brackets; subscripts; semi-colons; etc.). So far, it's been a bit of a pain to make sure all combinations and deviations work well and don't break any existing code. Work in progress! |
I'm worried that some goals of StatCheck are in contradiction with each other. Here is my understanding of the goals:
While I understand the value of checking for APA formatting, it currently seems to be impeding finding and checking as many tests as possible. Maybe it's worth extracting tests in the broadest set of formats possible and then checking for APA formatting in an optional second pass rather than simply not reporting on incompliant tests at all?
@MicheleNuijten Thoughts?
The text was updated successfully, but these errors were encountered: