You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Nipype has now been around for about 8 years now. Over the years we have learned of things that work well, are annoying, and are simply impossible to do. Our goal by end of summer is to release a draft of Nipype 2.0. This will involve:
a refactoring of Nipype into separate modular projects (interfaces, engine, workflows)
a fresh api for each component (with automatic updating of previous code when possible)
built in support for standards (BIDS, NIDM, CWL, Boutiques, etc.,.)
even more pythonic code style for people writing workflows
During the hackathon we will focus on the release of a new core engine and a new core API. We would love your input (comments/criticisms) and/or your coding skills.
The text was updated successfully, but these errors were encountered:
Submitted by Nipypers*
Nipype has now been around for about 8 years now. Over the years we have learned of things that work well, are annoying, and are simply impossible to do. Our goal by end of summer is to release a draft of Nipype 2.0. This will involve:
During the hackathon we will focus on the release of a new core engine and a new core API. We would love your input (comments/criticisms) and/or your coding skills.
The text was updated successfully, but these errors were encountered: