Workflows and interfaces for neuroimaging packages
effigies Merge pull request #2735 from leej3/master
ENH: Add tab completion for node and interface inputs properties
Latest commit eacd567 Oct 17, 2018
Failed to load latest commit information.
.circleci CI: Remove non-working Circle filters Aug 15, 2018
.github [skip ci] Install Release Drafter Aug 14, 2018
doc FIX: corrects readthedocs build error Oct 9, 2018
docker FIX: revert changes in Oct 10, 2018
examples after comments from Chris Feb 22, 2018
nipype pep errors and use sets for tab_completion comparisons Oct 17, 2018
tools Merge remote-tracking branch 'upstream/master' into rel/1.0.4 May 24, 2018
.coveragerc hopefully, final fix to the circle deployment Mar 17, 2017
.dockerignore STY: correct for tailing spaces and newline at end of file Jan 5, 2018
.gitattributes Update .gitattributes Mar 14, 2012
.gitignore MAINT: Update .gitignore May 25, 2018
.mailmap MAINT: A few more .mailmap entries Sep 19, 2018
.travis.yml Pin pybids 0.6.5 Oct 9, 2018
.zenodo.json MAINT: Update Zenodo with latest line counts Sep 19, 2018 styling Oct 15, 2017 resolving a conflict Mar 7, 2018
INSTALL fix: docs build without any sphinx errors or warnings Sep 11, 2011
LICENSE update: license info May 5, 2016 fix: removed matlabscripts from manifest template Aug 9, 2015
Makefile No more mentions of nose-tests Jul 27, 2018
README.rst Add gitter and slack channels Aug 28, 2018
THANKS.rst doc: cleanup doc building and updated funding info Apr 19, 2016
Vagrantfile No more mentions of nose-tests Jul 27, 2018 STY: correction of E501 - line too long (82 > 79 characters) - Part 1 Jan 6, 2018
codecov.yml COV: Drop examples, superfluous globs Feb 17, 2018
requirements.txt Revert "DEP: Update pytest dependency" Jul 27, 2018
rtd_requirements.txt DEP: Sync requirements with Feb 27, 2018
setup.cfg enh: test travis wheel deployment Nov 22, 2017 changing to RawConfigParser for consistency Apr 13, 2018


NIPYPE: Neuroimaging in Python: Pipelines and Interfaces Latest Version Supported Python versions Development Status License Chat

Current neuroimaging software offer users an incredible opportunity to analyze data using a variety of different algorithms. However, this has resulted in a heterogeneous collection of specialized applications without transparent interoperability or a uniform operating interface.

Nipype, an open-source, community-developed initiative under the umbrella of NiPy, is a Python project that provides a uniform interface to existing neuroimaging software and facilitates interaction between these packages within a single workflow. Nipype provides an environment that encourages interactive exploration of algorithms from different packages (e.g., SPM, FSL, FreeSurfer, AFNI, Slicer, ANTS), eases the design of workflows within and between packages, and reduces the learning curve necessary to use different packages. Nipype is creating a collaborative platform for neuroimaging software development in a high-level language and addressing limitations of existing pipeline systems.

Nipype allows you to:

  • easily interact with tools from different software packages
  • combine processing steps from different software packages
  • develop new workflows faster by reusing common steps from old ones
  • process data faster by running it in parallel on many cores/machines
  • make your research easily reproducible
  • share your processing workflows with the community


Please see the doc/README.txt document for information on our documentation.


Information specific to Nipype is located here:

Support and Communication

If you have a problem or would like to ask a question about how to do something in Nipype please open an issue to with a nipype tag. is a platform similar to StackOverflow but dedicated to neuroinformatics.

To participate in the Nipype development related discussions please use the following mailing list:

Please add [nipype] to the subject line when posting on the mailing list.

You can even hangout with the Nipype developers in their Gitter channel or in the BrainHack Slack channel. (Click here to join the Slack workspace.)

Contributing to the project

If you'd like to contribute to the project please read our guidelines. Please also read through our code of conduct.