Skip to content

Methods

Before You Trust a Study: the plans, code and results

Everything behind the numbers in the essay, so anyone can run them again. Each plan was fixed before its script was run on real outcomes.

The essay is Before You Trust a Study, Check How Strongly It Passed. Start with the README: it lists the public data each script needs, where to download it, and the sha256 of every file here. How each test placed and weighted results, and the prior work behind the cue, are in the notes on method.

01 · The tests

written down first

  1. SCORE: strong against narrow first passes

    In SCORE’s public data, first results at or below p = .001 held up 66% of the time (152 claims from 96 papers), and those exactly between .01 and .05 held up 34% (63 claims from 48 papers). Each paper weighted equally within a band; the gap is 32 points, interval 16 to 46.

    plan · code · result

  2. FReD: the same comparison on re-runs researchers chose to do

    58% against 38%. The outcome is the one each replication study reported, with mixed results counted as failures.

    plan · code · result

  3. The card on 27 earlier findings

    A look back: the outcomes, and lay readers’ judgements of them, were already published. Act 5 of 5 held, try small 9 of 18, wait 0 of 4; forced to call all 27, the card scores the same as the p-value alone.

    plan · code · result

  4. One reader’s doubt in place of the crowd’s

    Resampling the published ratings, about 3 in 10 “wait” findings then held. This plan was written after the look back above.

    plan · code · result

02 · Exploratory

run after the planned tests

  1. SCORE re-checks that collected new data

    67% against 32%.

    code · result

  2. The 273-claim subset closest to SCORE’s main report

    A gap of 34 points.

    code · result

03 · The data

public sources