Use Cases

The Applied Neuroimager

A student, post-doc, or faculty member mainly interested in solving a neuroscientific or a clinical question. They have learned how to use a few analysis packages. ReproNim will impact this user in the following ways:

  • When user will re-run any prior analysis in an exact fashion
  • When publishing, this user can facilitate the markup of the results, and the sharing of the raw and derived datasets increasing the reproducibility of the finding, and advancing the opportunities to replicate the study.

The Software Developer

A junior faculty member in a computer science department working on developing novel approaches to the assessment of neuroimaging datasets. This user has substantial computer programming and IT skills (Python and Linux) and is tasked with delivering their new tool to the broader neuroimaging community. ReproNim will impact this user in the following ways:

  • ReproNim provides a software library that the developer can use to markup of the results of the analysis in a standardized and sharable fashion
  • ReproNim provides a framework that will facilitate establishing a regression test suite to guarantee future robust and reproducible operation of the developed software.

The Power User

A faculty member in a hospital clinical psychiatry department working on integrating a collection of local data (N=100) with numerous community-based data collections (N=5000). This individual has excellent computing, programming and system administration skills and access to local high-performance computing infrastructure and has assembled a complex workflow comprised of software tools from many sources. ReproNim will impact this user in the following ways:

  • The user will have advanced tools for discovering and accessing relevant shared data resources for integration into their analysis
  • The user will have additional options regarding availability of cloud and local execution options
  • With the more precise markup of the results provenance, the user will be able to more systematically interrogate methodological sources of variation within the workflow (due to subject/source, analysis parameters, operating system/versioning, etc.).