Proposed Standards for Peer‐Reviewed Publication of Computer Code. (1st September 2016)

• Record Type: Journal Article
• Authors: Timlin, Dennis; David, Olaf; Green, Timothy R.; Fleisher, David H.; Kim, Soo‐Hyung; Ahuja, Laj R.
• Is Part Of: Agronomy Journal. Volume 108:Number 5(2016)
• Page Start: 1782
• Page End: 1786
• Publication Date: 2016-09-01
• Subjects: Agronomy -- Periodicals; 630
• DOI: 10.2134/agronj2015.0481
• Languages: English
• ISSNs: 0002-1962

Abstract

Abstract : The use of computers in agricultural research has expanded rapidly in recent years. Such code can be considered a scientific product that has applications in both research and education. Usage of this code can be expanded to a wide range of potential end users. We propose that the Agronomy Journal peer review and publish software code in the form of small, self‐contained modules. To do this, it is critical that the software used in agricultural research be well documented and written in a clear, easily understandable format. Our objective is to outline consistent standards that can be used to publish peer‐reviewed computer code. The goal of documenting source code is to inform the reader of the logic, meaning of variable names, and purpose of the various components of the code. Users who are not familiar with the code should be able to easily comprehend and use it. The documentation should include test data and a driver such that users can run the model and compare output to published results. Parameters and other input and output variables should be described in detail and documented so their source in the literature can be identified. Use of models by members of the scientific community and other end users can increase the impact of the developer's research and reduce costs of research devoted to modeling efforts. This article discusses necessary requirements to document and publish code that facilitates the reuse and modification of code. Computer models are scientific products important for both reseach and education. The computer code is subject to change and may be used by a wide variety of people. Code for these models should be written in a clear, understandable format and be well documented. Well documented and well written code will increase the scientific value of the code.