Post

Code and data (both for the analyses and for the knit itself) are of course available and linked in the papers. For the paper on reproducibility, see here osf.io/ed8pj/overview For the paper on replicability, see here osf.io/g5sny/overview Code/data are CC0 1.0 Universal, enjoy!

osf.ioOSF

Reproducible manuscripts are useful for a few reasons: One of the best reasons is just practicality. The thing most of us do where we have to manually update every stat/figure etc in a manuscript every time something changes in the code or data is super error-prone and time consuming.

1/4/26, 4:10 pm0 reposts3 likes

Then there is rigor and accountability. Anyone can trace every stat and figure to *exactly* how it was estimated. If there's an error or a way you think things should have been done instead, it's super findable. As a bonus, that incentivizes code readability, since people might use it.

Reproducible manuscripts have been around since code existed, but they are still pretty rare and mostly written in scripting langauges (text and everything) like RMarkdown. For SCORE, the text is written collaboratively via Google Docs, enabling modern collaborative writing with a large team.

I hope y'all tear into it and find any lurking issues, questions, ideas for your own work, etc. Gotta say it's a bit terrifying to have the entire pipeline so fully exposed and accessible, particularly one as complicated and high profile as SCORE. But more importanty, I hope it's useful.

2 Apr

update: internal muffled scream

Darren Dahly

@statsepi.bsky.social