How to use the GRIM test to spot fake data
MethodologyComments
Suppose a researcher uses a legacy software package that applies a non-standard rounding algorithm. The resulting inconsistency would be a software artifact rather than a manual manipulation.
We don't see software artifacts in local reports. If the math is off, it's usually because someone just guessed a number to make the results look better.
This isn't a fraud detector; it's a typo detector. Are we really calling every rounding error fabrication now?
Crucial for auditing LLM-generated papers. AI often hallucinates means that look plausible but fail the GRIM test because it doesn't perform the actual summation.
The broader benefit is the push toward reporting raw data in supplementary files. This shift toward transparency inherently discourages the 'massaging' of means before publication.
it's basically a checksum for behavioral sciences.
Authors sometimes report weighted means. In those instances, the GRIM test is useless because the denominator is no longer a simple integer N.
Since weighted means complicate the math, is there a similar consistency check that works for those specific datasets?