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
I've written a visual programming interface to Nipype, Porcupine. It is in part meant to make MRI analysis a lot easier for the novice user, but there is one big problem: Nipype nodes (or a)
At the moment, all Nipype nodes are available, but they have the same untransparent names (e.g., fsl.BET) of the original function. It would be great if instead, the nodes could be organised by functionality instead.
Primary goals:
Find a way to collect relevant metadata from Nipype nodes. [Relevant to Nipype]
List the nodes in an 'order by category' panel in Porcupine. [Relevant to Porcupine]
Secondary goals:
An annotation of this kind would be equally useful for the Nipype documentation. Some 'browse by category' functionality would be a welcome addition to the docs.
Stretch goals (or separate project):
Include snippets of text for some functions in order to automatically generate methods sections
Type
pipeline_development
Development status
2_releases_existing
Topic
other
Tools
Nipype
Programming language
Python
Modalities
not_applicable
Git skills
2_branches_PRs
The text was updated successfully, but these errors were encountered:
Project leader
Name: Tim Van Mourik
Github username: @TimVanMourik
Project Description
I've written a visual programming interface to Nipype, Porcupine. It is in part meant to make MRI analysis a lot easier for the novice user, but there is one big problem: Nipype nodes (or a)
At the moment, all Nipype nodes are available, but they have the same untransparent names (e.g.,
fsl.BET
) of the original function. It would be great if instead, the nodes could be organised by functionality instead.Type
pipeline_development
Development status
2_releases_existing
Topic
other
Tools
Nipype
Programming language
Python
Modalities
not_applicable
Git skills
2_branches_PRs
The text was updated successfully, but these errors were encountered: