Skip to content

Nipype 2.0 idea: interface assertions #2218

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
oesteban opened this issue Oct 6, 2017 · 1 comment
Open

Nipype 2.0 idea: interface assertions #2218

oesteban opened this issue Oct 6, 2017 · 1 comment
Milestone

Comments

@oesteban
Copy link
Contributor

oesteban commented Oct 6, 2017

Summary

Assertions are a good programming in general. What if nipype included a language for interface-level assertions that are checked when the interface finished running?

Actual behavior

Right now, interfaces include only one low-level assertion: do output files of this interface exist in the prescribed path?

Expected behavior

An easy means to tell nipype things like:

  • "is the output image empty?",
  • "expected dtypes for output image files",
  • "check that the x-forms matrices of the outputs.out_file output match the x-form matrices of inputs.reference_file".

These kind of checks would make debugging complex pipelines easier.

@satra satra added this to the Nipype 2.0 milestone Oct 6, 2017
@satra
Copy link
Member

satra commented Oct 6, 2017

@oesteban - as we improve the image handling traits classes, things like these can go into bothe input and output sides. added it to a 2.0 milestone.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants