Please let interface calls fail, when the underlying command fails about nipype HOT 7 CLOSED

And that might be also a proper location where to dump at least stderr into the user's face for his entire delight

from nipype.

This still seems to be an issue and I don't necessarily agree with the 'enhancement' classification. Moreover, there is a related issue that worries me at least as much: When I specify mutually exclusive option for a node it will run just fine -- although what I asked for is clearly impossible. It will only say something like "UserWarning: blablabla ... Resetting $RANDOM_PARAMETER to ".

This is really sub-optimal. Unless I closely monitor the console output I might not even notice that something goes wrong. Depending on what parameter gets reset it might even perform something totally different from what was originally intended.

I'd consider this a proper bug.

from nipype.

michael: any chance of a small example?

from nipype.

michael: regarding the mutually exclusive inputs, we cannot raise an error. it's not a mistake. so what would you suggest we do?
and i think i've fixed the other bug.

from nipype.

Hey,
I'm a bit lost. Why is it not possible to raise an error? What example do you need: mutual exclusive options, or failing BET?

Michael

from nipype.

michael: here you go.

In [1]: from nipype.interfaces.fsl import BET
In [3]: bet = BET()
In [4]: bet.inputs.reduce_bias = True
In [5]: bet.inputs.functional = True
...
File "/software/nipy-repo/nipype/nipype/interfaces/base.py", line 343, in _xor_warn
raise IOError(msg)
IOError: Input "functional" is mutually exclusive with input "reduce_bias" which is already set

from nipype.

All interfaces throw an exception when runtime.returncode is not zero.
Closed by 04f7a7a.

from nipype.