# DIPY Coding Style Guideline¶

The main principles behind DIPY development are:

• Robustness: the results of a piece of code must be verified systematically, and hence stability and robustness of the code must be ensured, reducing code redundancies.
• Readability: the code is written and read by humans, and it is read much more frequently than it is written.
• Consistency: following these guidelines will ease reading the code, and will make it less error-prone.
• Documentation: document the code. Documentation is essential as it is one of the key points for the adoption of DIPY as the toolkit of choice in diffusion by the scientific community. Documenting helps clarifying certain choices, helps avoiding obscure places, and is a way to allow other members decode it with less effort.
• Language: the code must be written in English. Norms and spelling should be abided by.

## Coding style¶

DIPY uses the standard Python PEP8 style to ensure the readability and consistency across the toolkit. Conformance to the PEP8 syntax is checked automatically when requesting to push to DIPY. There are software systems that will check your code for PEP8 compliance, and most text editors can be configured to check the compliance of your code with PEP8. Beyond the aspects checked, as a contributor to DIPY, you should try to ensure that your code, including comments, conform to the above principles.

## Documentation¶

DIPY uses Sphinx to generate documentation. We welcome contributions of examples, and suggestions for changes in the documentation, but please make sure that changes that are introduced render properly into the HTML format that is used for the DIPY website.

DIPY follows the numpy docstring standard for documenting modules, classes, functions, and examples.

The documentation includes an extensive library of examples. These are Python files that are stored in the doc/examples folder and contain code to execute the example, interleaved with multi-line comments that contain explanations of the blocks of code. Examples demonstrate how to perform processing (segmentation, tracking, etc.) on diffusion files using the DIPY classes. The code is intermixed with generous comments that describe the former, and the rationale and aim of it. If you are contributing a new feature to DIPY, please provide an extended example, with explanations of this feature, and references to the relevant papers.

If the feature that you are working on integrates well into one of the existing examples, please edit the .py file of that example. Otherwise, create a new .py file in that directory. Please also add the name of this file into the doc/examples/valid_examples.txt file (which controls the rendering of these examples into the documentation).

Additionally, DIPY relies on a set of reStructuredText files (.rst) located in the doc folder. They contain information about theoretical backgrounds of DIPY, installation instructions, description of the contribution process, etc.

Again, both sets of files use the reStructuredText markup language for comments. Sphinx parses the files to produce the contents that are later rendered in the DIPY website.

The Python examples are compiled, output images produced, and corresponding .rst files produced so that the comments can be appropriately displayed in a web page enriched with images.

Particularly, in order to ease the contribution of examples and .rst files, and with the consistency criterion in mind, beyond the numpy docstring standard aspects, contributors are encouraged to observe the following guidelines:

• The acronym for the Diffusion Imaging in Python toolkit should be written as DIPY.
• The classes, objects, and any other construct referenced from the code should be written with inverted commas, such as in In DIPY, we use an object called GradientTable which holds all the acquisition specific parameters, e.g. b-values, b-vectors, timings and others.
• Cite the relevant papers. Use the [NameYear] convention for cross-referencing them, such as in [Garyfallidis2014], and put them under the References section.
• Cross-reference related examples and files. Use the .. _specific_filename: convention to label a file at the top of it. Thus, other pages will be able to reference the file using the standard Sphinx syntax :ref:specific_filename.
• Use an all-caps scheme for acronyms, and capitalize the first letters of the long names, such as in Constrained Spherical Deconvolution (CSD), except in those cases where the most common convention has been to use lowercase, such as in superior longitudinal fasciculus (SLF).
• As customary in Python, use lowercase and separate words with underscores for filenames, labels for references, etc.
• When including figures, use the regular font for captions (i.e. do not use bold faces), unless otherwise required for a specific text part (e.g. a DIPY object, etc.).
• When referring to relative paths, use the backquote inline markup convention, such as in doc/devel. Do not add the greater-than/less-than signs to enclose the path.

### References¶

 [Garyfallidis2014] Garyfallidis E, Brett M, Amirbekian B, Rokem A, van der Walt S, Descoteaux M, Nimmo-Smith I and Dipy Contributors (2014). Dipy, a library for the analysis of diffusion MRI data. Frontiers in Neuroinformatics, vol.8, no.8.