CODECHECK

Independent execution of computations underlying research articles

Stephen J Eglen
sje30@cam.ac.uk

University of Cambridge

Daniel Nüst

TU Dresden

February 10, 2026

Premise


We should be sharing material on the left, not the right.

“Paper as advert for Scholarship” (Buckheit & Donoho, 1995)

CODECHECK in one slide

  1. We take your paper, code and datasets.

  2. We run your code on your data.

  3. If our results match your results, go to step 5.

  4. Else we talk to you to find out where code broke. If you fix your code or data, we return to step 2 and try again.

  5. We write a report summarising that we could reproduce your finding.

  6. We work with you to freely share your paper, code, data and our reproduction.

Next steps

  1. Embedding into journal workflows.

  2. Training a community of codecheckers.

  3. Funding for a codecheck editor.

  4. Come and get involved

  5. Workshop in UK (Cambridge?) late 2026.

Further information: http://codecheck.org.uk and our research article.