2018
DOI: 10.1371/journal.pcbi.1006561
|View full text |Cite
|
Sign up to set email alerts
|

Ten simple rules for documenting scientific software

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
4
1

Citation Types

3
53
0

Year Published

2019
2019
2024
2024

Publication Types

Select...
4
3
1

Relationship

0
8

Authors

Journals

citations
Cited by 56 publications
(58 citation statements)
references
References 9 publications
3
53
0
Order By: Relevance
“…In some ways, accessiblity or ability to gain access to the code means nothing if adequate documentation for the model, a description of its components, instructions on how to compile or run it, and basic examples are not provided. This is in line with recommendations contained in the literature (Lee, 2018).…”
Section: Resultssupporting
confidence: 91%
“…In some ways, accessiblity or ability to gain access to the code means nothing if adequate documentation for the model, a description of its components, instructions on how to compile or run it, and basic examples are not provided. This is in line with recommendations contained in the literature (Lee, 2018).…”
Section: Resultssupporting
confidence: 91%
“…We provide a standard command-line interface that follows modern Unix conventions [32, 33], including providing arguments for help and the program version [18, 34], and provision of single-dash notation for short argument names and double-dash notation for long argument names. Most importantly, the --help argument causes the program to display usage information, including a description of each argument and its expected parameters.…”
Section: Resultsmentioning
confidence: 99%
“…For user documentation we provide 2 critical components: a README file that appears at the top level of the repository, and comprehensive command-line usage output via the --help argument [18, 34, 38] as discussed above. The README file includes a program description, dependencies, installation instructions, inputs and outputs, example usage, and licensing information [12, 43].…”
Section: Resultsmentioning
confidence: 99%
See 1 more Smart Citation
“…MuMoT’s implementation, testing, and documentation seeks to adhere to the best standards for scientific software deployment [12, 13].…”
Section: Design and Implementationmentioning
confidence: 99%