Submit a preprint

333

Percolation Package - From script sharing to package publicationuse asterix (*) to get italics
Sophie C Schmidt; Simon MaddisonPlease use the format "First name initials family name" as in "Marie S. Curie, Niels H. D. Bohr, Albert Einstein, John R. R. Tolkien, Donna T. Strickland"
2023
<p>In this paper we trace the development of an R-package starting with the adaptation of code from a different field, via scripts shared between colleagues, to a published package that is being successfully used by researchers world-wide. Our aim is to encourage researchers to prepare their custom analysis code in a way that is useful and easily reusable for others.</p> <p>The paper starts with a short background as to the scientific aims of the software package before relating the collaboration journey and the detailed processes involved. We then move to a review of code sharing in archaeology and the lessons we have learned in publishing code for others to use and share.</p>
https://doi.org/10.5281/zenodo.8307960You should fill this box only if you chose 'All or part of the results presented in this preprint are based on data'. URL must start with http:// or https://
You should fill this box only if you chose 'Scripts were used to obtain or analyze the results'. URL must start with http:// or https://
https://doi.org/10.5281/zenodo.8307960You should fill this box only if you chose 'Codes have been used in this study'. URL must start with http:// or https://
Code reuse; Code publication; archaeology
NonePlease indicate the methods that may require specialised expertise during the peer review process (use a comma to separate various required expertises).
Computational archaeology
James R. Allison, Brigham Young University, Florian Thiery M.Sc., Römisch-Germanisches Zentralmuseum, Department of Scientific Computing and Research Software Engineering, Mainz, Germany No need for them to be recommenders of PCIArchaeology. Please do not suggest reviewers for whom there might be a conflict of interest. Reviewers are not allowed to review preprints written by close colleagues (with whom they have published in the last four years, with whom they have received joint funding in the last four years, or with whom they are currently writing a manuscript, or submitting a grant proposal), or by family members, friends, or anyone for whom bias might affect the nature of the review - see the code of conduct
e.g. John Doe [john@doe.com]
2023-05-24 15:40:15
James Allison