datagrabber should always run about nipype HOT 7 CLOSED

We can introduce some flexibility and add a boolean input "always_run" to BaseInterfaceInputSpec. In DataGrabber this would be set to True.

from nipype.

I strongly vote to have this issue resolved one way or another -- got burnt by it quite a few times.

from nipype.

I keep setting overwrite to True for most of my DataGrabbers...

from nipype.

see - the knowledge is the power!

unfortunately for dumb users (like me) it is hard to figure out the existence of such magic unless they read and memorize by heart the tutorial 102 since pe.Node? docstring doesn't reveal the existence of overwrite defined in the base class ;)

from nipype.

although i started this, i have no idea any more what situation this would lead to a problem. could somebody clarify for me please? or create a small test scenario?

from nipype.

I am generating some results using external tool which I might improve from time to time to provide more results. I am picking those up using a DataGrabber. I have a simple pipeline to reslice all the results across subjects into the MNI space using pre-crafted transformations. Now the pipeline doesn't "see" new results provided externally.

from nipype.

ah i see. it's because the input parameters don't change, but the files have changed. thanks. now its noted.

from nipype.