Skip to content

Commit 861423d

Browse files
committed
ENH: Add notes about transparency
This PR continues with the transfer of knowledge from *fMRIPrep* proper.
1 parent e69a0c7 commit 861423d

File tree

2 files changed

+49
-0
lines changed

2 files changed

+49
-0
lines changed

docs/intro/transparency.md

Lines changed: 48 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,48 @@
1+
*NiPreps* adopt *fMRIPrep*'s foundations, and particularly resonate with the transparency principles.
2+
As discussed in ([Esteban et al., 2019](https://doi.org/10.1038/s41592-018-0235-4) -- [preprint](https://doi.org/10.1101/306951)):
3+
4+
> The rapid increase in the volume and diversity of data, as well as the evolution of available techniques for processing and analysis, presents an opportunity for considerable advancement of research in neuroscience.
5+
> The drawback resides in the need for progres-sively more complex analysis workflows that rely on decreasingly interpretable models of the data.
6+
> Such context encourages ‘black-box’ solutions that efficiently perform a valuable service but do not provide insights into how the tool has transformed the data into the expected outputs.
7+
> Black boxes obscure important steps in the inductive process mediating between experimental measurements and reported findings.
8+
> This way of moving forward risks producing a future generation of cognitive neuroscientists who have become experts in sophisticated computational methods but have little to no working knowledge of how their data were transformed through processing.
9+
> Transparency is often identified as a remedy for these problems.
10+
> *fMRIPrep* ascribes to ‘glass-box’ principles, which are defined in opposition to the many different facets or levels at which black-box solutions are opaque.
11+
> The visual reports that *fMRIPrep* generates are a crucial aspect of the glass-box approach.
12+
> Their qual-ity control checkpoints represent the logical flow of preprocessing, allowing scientists to critically inspect and better understand the underlying mechanisms of the workflow.
13+
> A second transparency element is the citation boilerplate that formalizes all details of the workflow and provides the versions of all involved tools along with references to the corresponding scientific literature.
14+
> A third asset for transparency is thorough documentation that delivers addi-tional details on each of the building blocks represented in the visual reports and described in the boilerplate.
15+
> Further, *fMRIPrep* has been open-source since its inception: users have access to all of the incremental additions to the tool through the history of the version-control system.
16+
> The use of GitHub (https://github.com/poldracklab/fmriprep) grants access to the discussions held during development, allowing one to see how and why the main design decisions were made.
17+
> The modular design of *fMRIPrep* enhances its flexibility and improves transparency, as the main features of the software are more easily accessible to potential collaborators.
18+
> In combination with some coding style and contribution guidelines, this modularity has enabled multiple contributions by peers and the creation of a rapidly growing community that would be difficult to nurture behind closed doors.
19+
20+
## Visual reports beyond quality control
21+
22+
One foundational component of the *NiPreps* framework is the *Visual Report System*.
23+
**End-user applications** such as *fMRIPrep* or *dMRIPrep* generate individual reports after their preprocessing.
24+
Those visual reports have two fundamental purposes:
25+
26+
* **assessing the quality of the generated outputs**, permitting the user to take quality control actions to eliminate biases originated from inadequate processing; and
27+
* **understanding the workflow**, by sequentially presenting the main steps of processing, the user can access the why the tool in particular took these steps ando more geneally why standard preprocessing involves that step.
28+
29+
## Citation boilerplates
30+
31+
*NiPreps* leverage the wealth of existing neuroimaging software that is available to researchers.
32+
To give back for standing on the shoulders of giants, *NiPreps* aim at the most thorough reporting possible crediting all the pieces of the prior knowledge they leverage.
33+
With the execution of some particular *NiPreps*, the application runs some introspection code to formalize the computational graph the particular workflow executed and iterates over all the nodes to extract the relevant articles and communications that should be cited, as well as all software tools and their versions involved.
34+
Similarly, ancillary materials such as neuroimaging templates and atlases are reported and cited.
35+
36+
All these references and citations are finally collated in a natural language description of the workflow.
37+
This description is therefore generated automatically, and contains all the details that are necessary to replicate the processing, as well as the abovementioned references.
38+
The text is appended to the visual report, and provided in three formats (markdown, latex and html/plain-text) with an index of citations, so that the user is only required to "copy-and-paste" into the Methods section of their papers.
39+
40+
!!! important "Note for reviewers and editors"
41+
42+
The boilerplate text generated by some *NiPreps* is intended to allow for clear, consistent description of the preprocessing steps used, in order to improve the reproducibility of studies.
43+
We fully intend for it to be copied verbatim, and have released it under the [CC0 license](https://creativecommons.org/publicdomain/zero/1.0/), dedicating it to the public domain in jurisdictions that recognize the concept, and assert that we will take no action to enforce copyright in jurisdictions where we cannot disclaim it.
44+
45+
We firmly believe that requiring authors to modify this passage will serve **no legitimate scientific or literary purpose** and can, in fact, serve only to reduce the replicability of the analysis being described by making the preprocessing steps less clear.
46+
47+
We recognize that there may be automated plagiarism detection software that will flag the boilerplate text.
48+
We would be happy to discuss potential solutions for annotating boilerplate sections of documents to indicate automatic generation, and can update our software to make this annotation simpler for authors.

mkdocs.yml

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,7 @@ nav:
1515
- Home: index.md
1616
- NiPreps:
1717
- Framework: intro/nipreps.md
18+
- Transparency of workflows: intro/transparency.md
1819
- BIDS-Apps:
1920
- Introduction: apps/framework.md
2021
- Executing with Docker: apps/docker.md

0 commit comments

Comments
 (0)