-
Notifications
You must be signed in to change notification settings - Fork 532
Nipype looks for node results in wrong folders #2689
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
Comments
so what are the paths of existing files? Can you share the code that leads to the error? any chances you run it in a container that you can share? |
Sorry, no docker. I can share the code if you think it would help, but I honestly doubt it. You can't run it without the data anyway. The correct paths should be the node working folder like
in the first example. But you can see from the paths in the error codes above that in the first example nipype looks for the file in the home folder, and in the second example, it looks for it in the batch folder, so it looks like the paths are not set properly somewhere. I did not have this error before but then I recently switched to python 2.7 and also updated to the last version of nipype (from 1.0.x). I see that there were similar issues raised in the past here on Github but they all seem to be resolved by the last updated. |
here's the code for mcflirt example node:
and here's meanBold node from the 2nd example:
|
This is consistent with a problem we saw in nipreps/fmriprep#2161. I was unable to reproduce it in a small workflow. Are you able to produce a small workflow that consistently produces this issue? Also, are all failing nodes |
Yes, it seems they are from
Look at the predicted outputs and outputs before the error - that's a printout from It seems that it expects the node to have some out_file. But if I'm reading this correctly it's actually the error when it tries to aggregate the outputs from If I look at the results pklz from this node at the subjects that passed without errors for some reason, I see:
|
Oh, I wonder if outputs are being saved as relative paths, which might lead to invalid population of the |
This is a |
OK, so here's my current workaround which seems to work so far. I've changed
So I basically switch the working directory to the node output directory before aggregating the results. It seems to work. The caveat is that I also had to clear the cache from previous runs, so maybe that was the important step and not the changes in the code. |
That looks reasonable to me. Also, FYI, we added a |
Will do! |
Please reopen if this is still occurring post 1.3.2. |
Summary
I get errors like this:
or this:
The files in question exist in node working directories. Apparently, nipype forgets to change the working directory to node directory somewhere, but I'm not able to find out where.
Platform details:
The text was updated successfully, but these errors were encountered: