Reproduce reported results
Canonical datasets from textbooks, papers and R documentation are run end to end and compared with the reported statistics.
Statistical validation
Plotwright checks its numerical output against published examples, independent library implementations and closed-form identities. Each check names its dataset, expected value and tolerance.
How a result earns trust
A passing test is useful only when its reference is meaningfully independent of the implementation under test.
Canonical datasets from textbooks, papers and R documentation are run end to end and compared with the reported statistics.
Results are compared with established numerical libraries such as SciPy, statsmodels, lifelines and scikit-learn when an equivalent implementation exists.
Closed-form calculations and non-circular identities catch cases where two software implementations could share the same mistake.
Worked benchmarks
This readable subset combines published examples with explicitly labeled synthetic stress tests. Each entry identifies its source, expected result and numerical anchor.
t = −4.0621 · df = 9 ·
P = 0.002833
Welch P = 0.00684 · pooled P = 0.0751
n=5: SD 1.581 · SEM 0.707
n=20: SD 1.477 · SEM 0.330
U = 35 · exact P = 0.2544
r = 0.5712 · ρ = 0.6000
bias = −2.118 · LoA −78.096 to 73.861
χ² = 2.000 · Fisher P = 0.4857
F(2, 27) = 4.846 · P = 0.0159
slope = 0.500 · R² = 0.667 ·
r = 0.816
Finteraction = 4.107 · P = 0.02186
χ² = 16.79 · df = 1 ·
P = 4.17×10⁻⁵
AUC = 0.893 · n = 109
What this does—and does not—prove
A benchmark supports the exact statistic, options and numerical tolerance it exercises. It is not a blanket guarantee that every method is appropriate for every dataset. Researchers remain responsible for study design, assumptions, exclusions and interpretation.
When a result differs from its reference, the automated suite fails. New statistical features are expected to add an independent oracle before they ship.
Start with a published example or one of your lab's verified projects. Inspect the Results sheet, assumptions and generated methods text before adopting a workflow.