-
Notifications
You must be signed in to change notification settings - Fork 532
Normalize12 does not accept an existing file as "apply_to_files" input #3030
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
After having restarted the python console and reinstalled nipype, it does accept the file as input, but it does not run, giving the following error
Which seems to me to be a similar problem, since it is complaining about not finding a file that it is absolutely there. |
For the As to why the file isn't being found, what kind of environment are you running in? Is the process running on the same machine and with the same permissions as your user? |
@fednem Can you confirm whether this persists with the current |
I have just tried again and the issue seems to be resolved.
Il giorno gio 19 set 2019 alle ore 22:22 Chris Markiewicz <
[email protected]> ha scritto:
… @fednem <https://github.com/fednem> Can you confirm whether this persists
with the current master?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3030?email_source=notifications&email_token=AFH4JCH2DGKE62XR46Y5EW3QKPNSFA5CNFSM4IXCCCLKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7EW3WQ#issuecomment-533294554>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFH4JCCBTL2XGXFU4OYWRL3QKPNSFANCNFSM4IXCCCLA>
.
--
Federico Nemmi, PhD
|
Great, thanks for the confirmation! |
Hi, I'm running into the same problem:
I'm running nipype with it's fsl and freesurfer interfaces in singularity/docker image:
The crazy thing is, I built the workflow on my Mac, which does not spit out this error, but when I run this on a remote linux machine in the containers i build with the same version of nipype, I get this error. The file does exist. Any suggestions? Thank you in advance. |
Hey !
Maybe a stupid suggestion: have you checked that a gunzipped nifti is a
valid input to the function interface you're calling?
Il giorno mer 27 mag 2020 alle ore 04:47 Xi He <[email protected]>
ha scritto:
… Hi, I'm running into the same problem:
traits.trait_errors.TraitError: Each element of the 'T1_files' trait of a ReconAllInputSpec instance must be a pathlike object or string representing an existing file, but a value of '/dwi_preproc/derivatives/pipetography/_subject_id_01/apply_warp/mapflow/_apply_warp1/acpc_t1.nii.gz' <class 'str'> was specified.
I'm running nipype with it's fsl and freesurfer interfaces in
singularity/docker image:
***@***.***:/# nipypecli version
1.5.0-rc1
The crazy thing is, I built the workflow on my Mac, which does not spit
out this error, but when I run this on a remote linux machine in the
containers i build with the same version of nipype, I get this error. The
file does exist. Any suggestions? Thank you in advance.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3030 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFH4JCGABUK6LKYMQVUFLYDRTR5NDANCNFSM4IXCCCLA>
.
--
Federico Nemmi, PhD
|
That is indeed a good suggestion, I changed the previous step's output to be
Just to be sure:
Additionally, another node in my workflow for mrtrix3's dwipreproc is also failing, i'm feeding in a |
Can you open a new issue? |
hi @effigies, After reading through more issues and documentations, I was able to solve the issue by configuring my workflow with SO I won't be opening a new issue. Thank you everyone for the help. |
Summary
When I try to provide the path towards the file to whom apply the deformation field it throws an error message
Actual behavior
When I provide the path towards the file to whom apply the deformation field as in
it throws the following error
Expected behavior
The expected behavior would be to accept the input, especially since it takes as
deformation_field
a file in the same directory and I have double checked that the files I am providing exist.Script/Workflow details
https://gist.github.com/fednem/e4725d8812af75a51d681214da3b401f
Platform details:
The text was updated successfully, but these errors were encountered: