-
Notifications
You must be signed in to change notification settings - Fork 42
New user with many errors when running fMRI-prepped BOLD images through standard fc pipeline #358
Comments
there is problem with acess to image in the directory and all your command is good |
Thanks for your answer. Do you think it is a permissions issue? I just tried running again and double-checked. Everything is open for read, write, and execute access. Or by access do you mean it's not finding the right images? All that's needed is the BOLD file, right? |
I am experiencing virtually the same issue also running in Docker. I fixed the "read only" error for the cohort file by running Docker directly; however, this has not fixed the fact that the pipeline is not receiving my imaging files. I tried running the cbf_all pipeline as well with similar results. |
@bwinsto2 pls can you try singularity image or docker image pls. Sorry for late reply @daphneneuro17 that should be a permission issue at your end |
@a3sha2 thanks for the reply, but I'm not sure what else to try. I downloaded the newest docker image and ran with the same command. I've tried with other datasets, but I'm receiving the same errors. I'm not sure how this could be a permissions issue because I've made sure the design file, cohort file, and all data files are open for read, write, and execute access for all users. It sounds like @daphneneuro17 is experiencing the same problem. |
It looks like this is the same (unresolved?) problem in #199 and #204 I thought this might be associated with #268, but here is my command for running docker directly, and the error I get: Here is the analysis variables section of the design file: I have tried keeping the design analysis variable in the design file as the default from the repository. I have also tried changing the variable to the place on my disk where I keep the file (referring to itself). I get the same error. @a3sha2 or @mattcieslak any ideas? @a3sha2 you have noted previously that the issue is with "docker binding": is there anything more specific you could suggest to resolve this? Thank you. |
@bwinsto2 the problem is directory of the design file |
It looks like you have the order of your arguments reversed for the You can check by doing something like:
and this should show your files. Let us know if this works! |
@mattcieslak thanks for looking into this! I suppose I misunderstood docker binding in this scenario. I did what you suggested, and the pipeline is running! Funny that adding a single character ("2") made all the difference. Appreciate your help @a3sha2 and @mattcieslak |
Suppose it's worth mentioning that my issue using the wrapper is perhaps unrelated(?). I don't know if @daphneneuro17 has gotten it working by interacting with Docker directly, but it sounds like she had the same issue running w/ the wrapper. |
Thank you for making this pipeline! We are excited to try it out in our lab. We have already run fMRIprep on multi-session resting state data, and we are attempting to run (or at least test) one of the RSFC pipelines. We tried following the instructions to the letter, but the pipeline is failing very early and often; there must be a problem with how we're specifying the location of our files or the design file(?) Per the instructions, we are trying to run a functional pipeline without the structural one first.
Cohort file
Design File
To test things out, we're simply using an unaltered version of the following (from cloned Github repo):
Error message
I'm not sure exactly what to post here--there are hundreds of errors. Here are a few snippets (clearly the pipeline isn't really running)
Cohort file issue is the same as #268
Later, it's not finding the design file?
later,
later,
Runtime Information
Additional context
Is it the case that it is not locating the image files correctly? Is it b/c the cohort file is read-only? Might I have to edit the design file? Apologies for being a bit lost with this.
Many thanks,
Brian
The text was updated successfully, but these errors were encountered: