Citing pilotr
If you use pilotr in published work, please cite it.
Bernabeu, P. (2026). pilotr: Simulate experimental and behavioural data from a portable design specification (R package version 0.3.1). Comprehensive R Archive Network (CRAN). https://doi.org/10.32614/CRAN.package.pilotr
@Manual{pilotr,
title = {{pilotr}: Simulate experimental and behavioural data from a portable design specification},
author = {Pablo Bernabeu},
year = {2026},
publisher = {Comprehensive R Archive Network (CRAN)},
note = {R package version 0.3.1},
doi = {10.32614/CRAN.package.pilotr},
url = {https://CRAN.R-project.org/package=pilotr},
}In R, citation("pilotr") returns the same reference.
The developer
pilotr is developed by Pablo Bernabeu, a researcher in the Department of Education at the University of Oxford. His work spans cognitive psychology, neuroscience, linguistics, education and research methods, with hands-on experience of behavioural experiments, EEG, corpus analysis, computational modelling and statistics. He develops open, reproducible research software in R and Python, and is a Fellow of the Software Sustainability Institute. His ORCID record lists his other work. pilotr and its Python twin are part of that work, keeping a design specification reproducible and its simulated data identical across both languages.
Licence
pilotr is released under the MIT licence. The licence covers the R and Python packages, the no-code app and the design specification alike.
Versioning and archival
CRAN assigned the package the DOI https://doi.org/10.32614/CRAN.package.pilotr on publication. It names the R package across all its versions, so the version in the citation identifies the release used. Releases of the repository, which carry the Python package as well, are tagged on GitHub and archived on Zenodo, where the concept DOI https://doi.org/10.5281/zenodo.21266313 resolves to the latest archived release and each release has a DOI of its own. The changelog records what changed in each release.
Contributing and support
Bugs and feature requests are best raised on the GitHub issues page. The contributing guide describes the development setup and the conventions the repository follows, including the cross-language random-number contract that any change to the generative core must keep intact.