This vignette describes the Workflow for Open Reproducible Code in Science, as introduced in Van Lissa et al. (2020). The paper describes the rationale and principled approach on which the workflow is based; this vignette describes the practical steps for R-users in greater detail.
https://
link to clipboard; this link should look something like https://[...].git
https://[...].git
renv
checked if you want to use dependency management (recommended)preregistration.Rmd
file, and optionally, planned analyses in a .R
file.prepare_data.R
file.open_data()
or closed_data()
Manuscript.Rmd
load_data()
[@essentialref2020]
, and non-essential references with a double at-symbol, [@@nonessential2020]
.renv
, you can save the state of the project library (all packages used) by calling renv::snapshot()
. This updates the lockfile, renv.lock
.check_worcs()
function to see whether your project adheres to the WORCS checklist (see worcs::checklist
)
knit: worcs::cite_all
to knit: worcs::cite_essential
Some researchers might want to share their work only once the paper is accepted for publication. In this case, we recommend creating a “Private” repository in Step 1, and completing Steps 13-18 upon acceptance by the journal.
References
Aalbersberg, IJsbrand Jan, Tom Appleyard, Sarah Brookhart, Todd Carpenter, Michael Clarke, Stephen Curry, Josh Dahl, et al. 2018. “Making Science Transparent by Default; Introducing the TOP Statement,” February. https://doi.org/10.31219/osf.io/sm78t.
Van Lissa, Caspar J., Andreas M. Brandmaier, Loek Brinkman, Anna-Lena Lamprecht, Aaron Peikert, Marijn E. Struiksma, and Barbara Vreede. 2020. “WORCS: A Workflow for Open Reproducible Code in Science,” May. https://doi.org/10.17605/OSF.IO/ZCVBS.