Skip to content

Add support for non-file outputs caching #2

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

Closed
chrisgorgo opened this issue Jul 29, 2010 · 0 comments
Closed

Add support for non-file outputs caching #2

chrisgorgo opened this issue Jul 29, 2010 · 0 comments

Comments

@chrisgorgo
Copy link
Member

When a non-file (i. e. integer, string, array etc) output is passed from one node to another it is not saved anywhere. Therefore upon rerunning a workflow things break.

satra pushed a commit that referenced this issue Nov 22, 2013
chrisgorgo pushed a commit that referenced this issue Jul 24, 2014
chrisgorgo pushed a commit that referenced this issue Sep 29, 2014
satra pushed a commit that referenced this issue Jul 6, 2015
Merge to update with master from nipy
chrisgorgo pushed a commit that referenced this issue Feb 3, 2016
Added md5 checking before uploading to S3
chrisgorgo pushed a commit that referenced this issue Feb 3, 2016
Merge fcp-indi nipype to mine
effigies pushed a commit that referenced this issue May 10, 2017
satra pushed a commit that referenced this issue Jun 7, 2017
a quick conflict resolution
rmarkello referenced this issue in rmarkello/nipype Jun 22, 2017
mvdoc pushed a commit to mvdoc/nipype that referenced this issue Jun 23, 2017
satra pushed a commit that referenced this issue Feb 15, 2018
akeshavan pushed a commit to akeshavan/nipype that referenced this issue Dec 19, 2018
fix: made the outputdir be mandatory and use the default val
This issue was closed.
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

1 participant